diff --git a/UseCases/Collaborating.mdwn b/UseCases/Collaborating.mdwn
index 1092dfb..c2b51b9 100644
--- a/UseCases/Collaborating.mdwn
+++ b/UseCases/Collaborating.mdwn
@@ -1,7 +1,7 @@
 As an accountant that collaborates with other accountants I need:
 
-<a id="simultaneous-ledger-edits"/>
-- Simultaneous editing of the same ledger
+
+- <a id="simultaneous-ledger-edits">Simultaneous editing of the same ledger</a>
 - FIXME: this should probably be stated differently: In the case of decentralized ledgers, such as ledger-cli files shared via DVCS
   - Easy synchronization of entries from separate ledgers
 
diff --git a/UseCases/GeneratingReports.mdwn b/UseCases/GeneratingReports.mdwn
index 27ac344..32b0b56 100644
--- a/UseCases/GeneratingReports.mdwn
+++ b/UseCases/GeneratingReports.mdwn
@@ -5,13 +5,13 @@ As an US-based NPO I need a way to *generate reports* in order to:
 
 The usual reports an NPO is expected to generate, and all of these should be generatable for any given date period:
 
-- <a id="trial-balance"/> [Trial balance](http://en.wikipedia.org/wiki/Trial_balance)
-- <a id="bank-reconciliation"/> [Bank Reconciliation Report](http://en.wikipedia.org/wiki/Bank_reconciliation)
+- <a id="trial-balance"></a>[Trial balance](http://en.wikipedia.org/wiki/Trial_balance)
+- <a id="bank-reconciliation"></a> [Bank Reconciliation Report](http://en.wikipedia.org/wiki/Bank_reconciliation)
     + This report often needs to be generated with input from the user, since [the subset sum problem](http://en.wikipedia.org/wiki/Subset_sum_problem) is [NP-complete](http://en.wikipedia.org/wiki/NP-complete), human intervention is often needed to identify the specific transactions to show on this report.
--  <a id="chart-of-accounts"/> [Chart of accounts](http://en.wikipedia.org/wiki/Chart_of_accounts)
--  <a id="cash-disbursements"/> Cash Disbursements Journal
-- <a id="income-report"/> Income Report (just a list/sum of all Income accounts for a period)
-- <a id="expenses-report"/> Expenses Report  (just a list/sum of all Expenses accounts for a period)
+-  <a id="chart-of-accounts"></a> [Chart of accounts](http://en.wikipedia.org/wiki/Chart_of_accounts)
+-  <a id="cash-disbursements">Cash Disbursements Journal</a>
+- <a id="income-report">Income Report</a> (just a list/sum of all Income accounts for a period)
+- <a id="expenses-report">Expenses Report</a>  (just a list/sum of all Expenses accounts for a period)
 - [[Fund Report|UseCases/FundAccounting#FundReport]]
 
 Also, To handle [[UseCases/FundAccounting]] all of these reports should be generatable narrowed to specific funds.
diff --git a/UseCases/WorkFlow.mdwn b/UseCases/WorkFlow.mdwn
index 3ce6b5a..5d57d09 100644
--- a/UseCases/WorkFlow.mdwn
+++ b/UseCases/WorkFlow.mdwn
@@ -5,8 +5,8 @@ of uses.  While the ability to impose a specific workflow (e.g., for a
 bookkeeper who might make an error easily if the system doesn't require a
 workflow), the  workflow should not be dictated.
 
-## The "Unaccrued Invoice" Example
-<a id="unaccrued-invoice"/>
+## <a id="unaccrued-invoice">The "Unaccrued Invoice" Example</a>
+
 
 The easiest example I have of this relates to accruing income upon invoice
 generation.  Non-profits very typically generate invoices as part of a