summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorJohn Wiegley <johnw@newartisans.com>2011-10-11 15:31:32 -0500
committerJohn Wiegley <johnw@newartisans.com>2011-10-11 15:31:32 -0500
commit0f47c0be9e44ff1b2d7deb52c5c2556d3bdbf8ca (patch)
tree9390cff9642743489dbad32338b67b8d54aa9e07 /doc
parentfc67484a21a32e0ffbf186e33db70e25497ccdf5 (diff)
downloadfork-ledger-0f47c0be9e44ff1b2d7deb52c5c2556d3bdbf8ca.tar.gz
fork-ledger-0f47c0be9e44ff1b2d7deb52c5c2556d3bdbf8ca.tar.bz2
fork-ledger-0f47c0be9e44ff1b2d7deb52c5c2556d3bdbf8ca.zip
Documentation fixes
Diffstat (limited to 'doc')
-rw-r--r--doc/ledger3.texi21
1 files changed, 10 insertions, 11 deletions
diff --git a/doc/ledger3.texi b/doc/ledger3.texi
index 1f875764..1d006498 100644
--- a/doc/ledger3.texi
+++ b/doc/ledger3.texi
@@ -188,7 +188,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{.,;:?!}
@@ -214,18 +214,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.