I ended up making the page singular rather than plural.

This commit is contained in:
Bradley M. Kuhn 2013-11-13 10:59:35 -05:00
parent 16d02e954c
commit c8439f10dd
2 changed files with 3 additions and 3 deletions

View file

@ -20,6 +20,6 @@ You should add your use case as a subpage of the [[UseCases]] page, to create a
- [[API|UseCases/API]]
- [[TrackingIncomeType|UseCases/TrackingIncomeType]]
- [[TrackingDocumentation|UseCases/TrackingDocumentation]]
- [[Handling expense reports and reimbursement requests|UseCases/ReimbursementRequests]]
- [[Handling expense reports and reimbursement requests|UseCases/ReimbursementRequest]]
- [[Handling contractors and contracts|UseCases/ContractorsAndContracts]]
- [[Handling multiple currencies|UseCases/MultiCurrency]]

View file

@ -8,7 +8,7 @@ backup documentation relate to a given accounting document.
An adequate accounting system should provide easy link-up between
double-entry accounting transactions and the documentation that relates to
the transactions. For example,
[[expense reports and reimbursement requests|UseCases/ReimbursementRequests]]
[[expense reports and reimbursement requests|UseCases/ReimbursementRequest]]
often have a myriad of receipts and invoices associated with them.
[[Handling contractors|UseCases/ContractorsAndContracts]] has similar types
of backup documentation.
@ -19,7 +19,7 @@ such as:
* I have this receipt/invoice from our document repository. Which
accounting transactions relate to this receipt? Has the transaction
been [[reimbursed|UseCases/ReimbursementRequests]]?
been [[reimbursed|UseCases/ReimbursementRequest]]?
* Looking at this invoice, can I see the transaction where it was accrued
and paid?