tec/org-mode
tec/org-mode
1
0
Fork 0
forked from mirrors/org-mode
Code Pull requests Releases Activity

org-manual: Fix typos

Browse source 
* doc/org-manual.org (Debugging formulas):
(Using third-party styles and templates):
(Publishing links): Fix typos.

Most of the suggestions have been incorporated.  A few missing are
added here.

Reported-by: TonyMc <afmcc@btinternet.com>
Link: https://orgmode.org/list/20171014123248.51568eec@Tourifreet
This commit is contained in:
Ihor Radchenko 2022-10-16 12:37:20 +08:00
parent 5fa66c7ffc
commit 3fc782e9b8
No known key found for this signature in database
GPG key ID: 6470762A7DA11D8B
1 changed files with 11 additions and 11 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

22
doc/org-manual.org
View file

@ -2664,11 +2664,11 @@ keyword.
#+cindex: debugging, of table formulas
When the evaluation of a formula leads to an error, the field content
becomes the string =#ERROR=. If you would like to see what is going
on during variable substitution and calculation in order to find
a bug, turn on formula debugging in the Tbl menu and repeat the
calculation, for example by pressing {{{kbd(C-u C-u C-c = RET)}}} in
a field. Detailed information are displayed.
becomes the string =#ERROR=. If you want to see what is going on
during variable substitution and calculation in order to find a bug,
turn on formula debugging in the Tbl menu and repeat the calculation,
for example by pressing {{{kbd(C-u C-u C-c = RET)}}} in a field.
Detailed information are displayed.
*** Updating the table
:PROPERTIES:
@ -14522,7 +14522,7 @@ The example here shows creating a style using LibreOffice.
The ODT export back-end relies on many templates and style names.
Using third-party styles and templates can lead to mismatches.
Templates derived from built in ODT templates and styles seem to have
Templates derived from built-in ODT templates and styles seem to have
fewer problems.
*** Links in ODT export
@ -16678,11 +16678,11 @@ configured Org to upload the related files, these links will work too.
See [[*Example: complex publishing configuration]], for an example of this
usage.
Eventually, links between published documents can contain some search
options (see [[*Search Options in File Links]]), which will be resolved to
the appropriate location in the linked file. For example, once
published to HTML, the following links all point to a dedicated anchor
in =foo.html=.
Links between published documents can contain some search options (see
[[*Search Options in File Links]]), which will be resolved to the
appropriate location in the linked file. For example, once published
to HTML, the following links all point to a dedicated anchor in
=foo.html=.
#+begin_example
[[file:foo.org::*heading]]