summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
Diffstat (limited to 'doc')
-rw-r--r--doc/ledger.texi5
-rw-r--r--doc/ledger3.texi21
2 files changed, 13 insertions, 13 deletions
diff --git a/doc/ledger.texi b/doc/ledger.texi
index ac7bfc5f..8389c383 100644
--- a/doc/ledger.texi
+++ b/doc/ledger.texi
@@ -1305,8 +1305,9 @@ The format of each following posting is:
ACCOUNT AMOUNT [; NOTE]
@end example
-The @samp{ACCOUNT} may be surrounded by parentheses if it is a virtual
-postings, or square brackets if it is a virtual postings that
+Note that there must be at least two spaces between @samp{ACCOUNT} and
+@samp{AMOUNT}. The @samp{ACCOUNT} may be surrounded by parentheses if it
+is a virtual posting or square brackets if it is a virtual posting that
must balance. The @samp{AMOUNT} can be followed by a per-unit
posting cost, by specifying @samp{@@ AMOUNT}, or a complete
posting cost with @samp{@@@@ AMOUNT}. Lastly, the @samp{NOTE} may
diff --git a/doc/ledger3.texi b/doc/ledger3.texi
index 3fce78e2..da63dd98 100644
--- a/doc/ledger3.texi
+++ b/doc/ledger3.texi
@@ -4223,7 +4223,7 @@ associated commodity. This commodity can appear before or after the
amount, and may or may not be separated from it by a space. Most
characters are allowed in a commodity name, except for the following:
-@itemize
+@itemize @bullet
@item Any kind of whitespace
@item Numerical digits
@item Punctuation: @samp{.,;:?!}
@@ -4249,18 +4249,17 @@ in the same form as parsed. If you specify dollar amounts using
@samp{$100.000}. You may even use decimal commas, such as
@samp{$100,00}, or thousand-marks, as in @samp{$10,000.00}.
-These display characteristics become associated with the commodity,
-with the result being that all amounts of the same commodity are
-reported consistently. Where this is most noticeable is the
-@dfn{display precision}, which is determined by the most precise value
-seen for a given commodity. In most cases.
+These display characteristics become associated with the commodity, with
+the result being that all amounts of the same commodity are reported
+consistently. Where this is most noticeable is the @dfn{display
+precision}, which is determined by the most precise value seen for a
+given commodity---in most cases.
-Ledger makes a distinction by @dfn{observed amounts} and unobserved
+Ledger makes a distinction between @dfn{observed amounts} and unobserved
amounts. An observed amount is critiqued by Ledger to determine how
-amounts using that commodity should be displayed; unobserved amounts
-are significant in their value only---no matter how they are
-specified, it does not change how other amounts in that commodity will
-be displayed.
+amounts using that commodity should be displayed; unobserved amounts are
+significant in their value only---no matter how they are specified, it
+does not change how other amounts in that commodity will be displayed.
An example of this is found in cost expressions, covered next.