diff --git a/UseCases/DraftTransactions.mdwn b/UseCases/DraftTransactions.mdwn
index 976aa4e5d9d25f8db22c7b6cff885019a36b8bc6..c7c37fcc39e399272d361527fcbfa77c3a5eeb32 100644
--- a/UseCases/DraftTransactions.mdwn
+++ b/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.
 
diff --git a/UseCases/FundAccounting.mdwn b/UseCases/FundAccounting.mdwn
index a70f4a652d3f46db7cccd0a34d4cedf34f75a921..5e472ffe5e1c1087f66d942e0a5db35c56308253 100644
--- a/UseCases/FundAccounting.mdwn
+++ b/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.
diff --git a/UseCases/MultiCurrency.mdwn b/UseCases/MultiCurrency.mdwn
index 7292918c17f9b46c78be716e304f38c0524a1de1..bee8b28ff43a6fdb6ff533fe7eb0b6fb090a3d4a 100644
--- a/UseCases/MultiCurrency.mdwn
+++ b/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
diff --git a/UseCases/TrackingDocumentation.mdwn b/UseCases/TrackingDocumentation.mdwn
index f2f3b6525533ff9bbc269a4a3c836ba89edcea6a..2bc3ce0ea822c68a86317470f376d62b53abc9ac 100644
--- a/UseCases/TrackingDocumentation.mdwn
+++ b/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