doc: update generated docs, fixing typos

This commit is contained in:
Simon Michael 2016-10-20 16:57:35 -07:00
parent 146ba133c6
commit bdf8f5ca88
6 changed files with 64 additions and 64 deletions

View File

@ -27,7 +27,7 @@ hledger is inspired by and largely compatible with ledger(1).
hledger\-api is a simple web API server, intended to support hledger\-api is a simple web API server, intended to support
client\-side web apps operating on hledger data. client\-side web apps operating on hledger data.
It comes with a series of simple client\-side app examples, which drive It comes with a series of simple client\-side app examples, which drive
it\[aq]s evolution. its evolution.
.PP .PP
Like hledger, it reads data from one or more files in hledger journal, Like hledger, it reads data from one or more files in hledger journal,
timeclock, timedot, or CSV format specified with \f[C]\-f\f[], or timeclock, timedot, or CSV format specified with \f[C]\-f\f[], or

View File

@ -9,7 +9,7 @@ hledger-api(1) hledger-api 0.28dev
hledger-api is a simple web API server, intended to support client-side hledger-api is a simple web API server, intended to support client-side
web apps operating on hledger data. It comes with a series of simple web apps operating on hledger data. It comes with a series of simple
client-side app examples, which drive it's evolution. client-side app examples, which drive its evolution.
Like hledger, it reads data from one or more files in hledger Like hledger, it reads data from one or more files in hledger
journal, timeclock, timedot, or CSV format specified with `-f', or journal, timeclock, timedot, or CSV format specified with `-f', or
@ -84,7 +84,7 @@ before options as shown above.
 
Tag Table: Tag Table:
Node: Top90 Node: Top90
Node: OPTIONS1064 Node: OPTIONS1063
Ref: #options1151 Ref: #options1150
 
End Tag Table End Tag Table

View File

@ -19,7 +19,7 @@ DESCRIPTION
hledger-api is a simple web API server, intended to support client-side hledger-api is a simple web API server, intended to support client-side
web apps operating on hledger data. It comes with a series of simple web apps operating on hledger data. It comes with a series of simple
client-side app examples, which drive it's evolution. client-side app examples, which drive its evolution.
Like hledger, it reads data from one or more files in hledger journal, Like hledger, it reads data from one or more files in hledger journal,
timeclock, timedot, or CSV format specified with -f, or $LEDGER_FILE, timeclock, timedot, or CSV format specified with -f, or $LEDGER_FILE,

View File

@ -104,7 +104,7 @@ Some examples: \f[C]2010/01/31\f[], \f[C]1/31\f[],
Real\-life transactions sometimes involve more than one date \- eg the Real\-life transactions sometimes involve more than one date \- eg the
date you write a cheque, and the date it clears in your bank. date you write a cheque, and the date it clears in your bank.
When you want to model this, eg for more accurate balances, you can When you want to model this, eg for more accurate balances, you can
specify individual #posting\-dates, which I recommend. specify individual posting dates, which I recommend.
Or, you can use the secondary dates (aka auxiliary/effective dates) Or, you can use the secondary dates (aka auxiliary/effective dates)
feature, supported for compatibility with Ledger. feature, supported for compatibility with Ledger.
.PP .PP

View File

@ -142,7 +142,7 @@ File: hledger_journal.5.info, Node: Secondary dates, Next: Posting dates, Pre
Real-life transactions sometimes involve more than one date - eg the Real-life transactions sometimes involve more than one date - eg the
date you write a cheque, and the date it clears in your bank. When you date you write a cheque, and the date it clears in your bank. When you
want to model this, eg for more accurate balances, you can specify want to model this, eg for more accurate balances, you can specify
individual #posting-dates, which I recommend. Or, you can use the individual posting dates, which I recommend. Or, you can use the
secondary dates (aka auxiliary/effective dates) feature, supported for secondary dates (aka auxiliary/effective dates) feature, supported for
compatibility with Ledger. compatibility with Ledger.
@ -935,61 +935,61 @@ Node: Simple dates3833
Ref: #simple-dates3961 Ref: #simple-dates3961
Node: Secondary dates4325 Node: Secondary dates4325
Ref: #secondary-dates4481 Ref: #secondary-dates4481
Node: Posting dates6042 Node: Posting dates6041
Ref: #posting-dates6173 Ref: #posting-dates6172
Node: Account names7544 Node: Account names7543
Ref: #account-names7683 Ref: #account-names7682
Node: Amounts8168 Node: Amounts8167
Ref: #amounts8306 Ref: #amounts8305
Node: Virtual Postings10304 Node: Virtual Postings10303
Ref: #virtual-postings10465 Ref: #virtual-postings10464
Node: Balance Assertions11685 Node: Balance Assertions11684
Ref: #balance-assertions11849 Ref: #balance-assertions11848
Node: Assertions and ordering12671 Node: Assertions and ordering12670
Ref: #assertions-and-ordering12856 Ref: #assertions-and-ordering12855
Node: Assertions and commodities13887 Node: Assertions and commodities13886
Ref: #assertions-and-commodities14113 Ref: #assertions-and-commodities14112
Node: Assertions and subaccounts14805 Node: Assertions and subaccounts14804
Ref: #assertions-and-subaccounts15039 Ref: #assertions-and-subaccounts15038
Node: Assertions and virtual postings15561 Node: Assertions and virtual postings15560
Ref: #assertions-and-virtual-postings15770 Ref: #assertions-and-virtual-postings15769
Node: Prices15911 Node: Prices15910
Ref: #prices16043 Ref: #prices16042
Node: Transaction prices16094 Node: Transaction prices16093
Ref: #transaction-prices16239 Ref: #transaction-prices16238
Node: Market prices17846 Node: Market prices17845
Ref: #market-prices17981 Ref: #market-prices17980
Node: Comments18869 Node: Comments18868
Ref: #comments18991 Ref: #comments18990
Node: Tags20103 Node: Tags20102
Ref: #tags20221 Ref: #tags20220
Node: Directives21144 Node: Directives21143
Ref: #directives21259 Ref: #directives21258
Node: Account aliases21452 Node: Account aliases21451
Ref: #account-aliases21598 Ref: #account-aliases21597
Node: Basic aliases22200 Node: Basic aliases22199
Ref: #basic-aliases22345 Ref: #basic-aliases22344
Node: Regex aliases23033 Node: Regex aliases23032
Ref: #regex-aliases23203 Ref: #regex-aliases23202
Node: Multiple aliases23973 Node: Multiple aliases23972
Ref: #multiple-aliases24147 Ref: #multiple-aliases24146
Node: end aliases24643 Node: end aliases24642
Ref: #end-aliases24785 Ref: #end-aliases24784
Node: account directive24887 Node: account directive24886
Ref: #account-directive25069 Ref: #account-directive25068
Node: apply account directive25365 Node: apply account directive25364
Ref: #apply-account-directive25563 Ref: #apply-account-directive25562
Node: Multi-line comments26224 Node: Multi-line comments26223
Ref: #multi-line-comments26416 Ref: #multi-line-comments26415
Node: commodity directive26543 Node: commodity directive26542
Ref: #commodity-directive26729 Ref: #commodity-directive26728
Node: Default commodity27602 Node: Default commodity27601
Ref: #default-commodity27777 Ref: #default-commodity27776
Node: Default year28313 Node: Default year28312
Ref: #default-year28480 Ref: #default-year28479
Node: Including other files28903 Node: Including other files28902
Ref: #including-other-files29062 Ref: #including-other-files29061
Node: EDITOR SUPPORT29458 Node: EDITOR SUPPORT29457
Ref: #editor-support29578 Ref: #editor-support29577
 
End Tag Table End Tag Table

View File

@ -93,7 +93,7 @@ FILE FORMAT
Real-life transactions sometimes involve more than one date - eg the Real-life transactions sometimes involve more than one date - eg the
date you write a cheque, and the date it clears in your bank. When you date you write a cheque, and the date it clears in your bank. When you
want to model this, eg for more accurate balances, you can specify want to model this, eg for more accurate balances, you can specify
individual #posting-dates, which I recommend. Or, you can use the sec- individual posting dates, which I recommend. Or, you can use the sec-
ondary dates (aka auxiliary/effective dates) feature, supported for ondary dates (aka auxiliary/effective dates) feature, supported for
compatibility with Ledger. compatibility with Ledger.