Add <a id> tags as needed for the EvaluationTemplate

UseCases/DraftTransactions.mdwn

@@ -1,5 +1,7 @@
 # Generating Draft Transactions
 
+<a id="draft-general"/>
+
 As a manager at a nonprofit, I need the ability to have staff propose draft
 transactions that are not added to the books official until approved.
 

UseCases/FundAccounting.mdwn

@@ -27,7 +27,7 @@ essence, the books of a fiscal sponsoring org are proper superset of all the
 books of its projects.
 
 Thus, an individual project contributor wants to:
-
+<a id="fund-view"></a>
 - View the books for that project as an independent set, unencumbered by
   transactions for other projects.
 
@@ -36,11 +36,13 @@ Thus, an individual project contributor wants to:
 
 The non-profit administrators want to:
 
+<a id="fundless-view"></a>
 - View the entire set of books for the organization, treating all income,
   expenses, and assets as belonging to the entire org, and only seeing the
   differences treating the project funds merely as "temporarily restricted
   assets".
 
+<a id="fundless-operation"></a>
 - Be able to perform operations that span the entire books, such as
   reconciling bank accounts that are contain funds temporarily restricted for
   different projects.

UseCases/MultiCurrency.mdwn

@@ -9,7 +9,7 @@ There are roughly two operating modes that I've observed in use by non-profit
 organizations.
 
 ## A "One Native Currency" Organization
-
+<a id="functional-currency"/>
 In the USA at least, and perhaps elsewhere, the native currency to the
 location of the entity is treated as the "one true currency" (which the USA
 IRS calls your "functional currency") of the organization.  Specifically in

UseCases/TrackingDocumentation.mdwn

@@ -5,6 +5,7 @@ are the heart of any accounting system, auditors and managers need the
 ability to dig down and determine what contracts, invoices, receipts or other
 backup documentation relate to a given accounting document.
 
+<a id="document-link-up"></a>
 An adequate accounting system should provide easy link-up between
 double-entry accounting transactions and the documentation that relates to
 the transactions.  For example,
@@ -15,7 +16,7 @@ of backup documentation.
 
 Ideally, the system should allow the exploration of and linkage to
 documentation in both directions.  It should be trivial to answer questions
-such as:
+such as:<a id="document-link-explore"/>
 
    * I have this receipt/invoice from our document repository.  Which
      accounting transactions relate to this receipt?  Has the transaction