branch: externals/org
commit 9da248ccd2e2fb86a37009bb0e672cb8419dc30c
Author: Matthew Trzcinski <m...@excalamus.com>
Commit: Matthew Trzcinski <m...@excalamus.com>
doc/org-manual.org: Remove term "foreign buffer"
doc/org-manual.org: Change "Export in Foreign Buffers" to "Export
Region", replace phrase "foreign buffers" with"non-Org buffers",
clarify explanation of the export region functions.
---
doc/org-manual.org | 13 ++++++-------
1 file changed, 6 insertions(+), 7 deletions(-)
diff --git a/doc/org-manual.org b/doc/org-manual.org
index c479719144..e77809c90b 100644
--- a/doc/org-manual.org
+++ b/doc/org-manual.org
@@ -16391,15 +16391,14 @@ Further steps to consider would be an interactive
function,
self-installing an item in the export dispatcher menu, and other
user-friendly improvements.
-** Export in Foreign Buffers
+** Export Region
:PROPERTIES:
:DESCRIPTION: Author tables and lists in Org syntax.
:END:
-The export backends in Org often include commands to convert selected
-regions. A convenient feature of this in-place conversion is that the
-exported output replaces the original source. Here are such
-functions:
+Some export backends include commands to convert a region of Org
+formatted text to another format, such as HTML or LaTeX. The
+conversion replaces the original source. Here are such commands:
- ~org-ascii-convert-region-to-ascii~ ::
@@ -16431,8 +16430,8 @@ functions:
#+findex: org-md-convert-region-to-md
Convert the selected region into Markdown.
-In-place conversions are particularly handy for quick conversion of
-tables and lists in foreign buffers. For example, in an HTML buffer,
+The in-place conversion is particularly handy for quick conversion of
+tables and lists in non-Org buffers. For example, in an HTML buffer,
write a list in Org syntax, select it, and convert it to HTML with
{{{kbd(M-x org-html-convert-region-to-html)}}}.
