diff --git a/UseCases/DraftTransactions.mdwn b/UseCases/DraftTransactions.mdwn
index c7c37fcc39e399272d361527fcbfa77c3a5eeb32..feff92ca76be96b531b28b0969e2e993cfaaa875 100644
--- a/UseCases/DraftTransactions.mdwn
+++ b/UseCases/DraftTransactions.mdwn
@@ -1,6 +1,6 @@
 # Generating Draft Transactions
 
-<a id="draft-general"/>
+<a id="draft-general"></a>
 
 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/MultiCurrency.mdwn b/UseCases/MultiCurrency.mdwn
index bee8b28ff43a6fdb6ff533fe7eb0b6fb090a3d4a..3ecca9390922b826fa336f3558bd1048d6835bea 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"/>
+<a id="functional-currency"></a>
 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 2bc3ce0ea822c68a86317470f376d62b53abc9ac..cc14e8ad3517a5c7a7c9a5024b319245e7e3f726 100644
--- a/UseCases/TrackingDocumentation.mdwn
+++ b/UseCases/TrackingDocumentation.mdwn
@@ -16,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:<a id="document-link-explore"/>
+such as:<a id="document-link-explore"></a>
 
    * I have this receipt/invoice from our document repository.  Which
      accounting transactions relate to this receipt?  Has the transaction