diff --git a/UseCases/Collaborating.mdwn b/UseCases/Collaborating.mdwn
index f86ee6f29cf3d64369d68cd0c45c262c22fdd89b..6ba60ce737bc77ed698f9a998fa2dc8834bbc6a2 100644
--- a/UseCases/Collaborating.mdwn
+++ b/UseCases/Collaborating.mdwn
@@ -1,7 +1,7 @@
 As an accountant that collaborates with other accountants I need:
 
 
-- <a style="text-decoration: none" id="simultaneous-ledger-edits">Simultaneous editing of the same ledger</a>
+- <a class="idOnly" 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 e262e85bfe69f98e71bd5467485cfa9d264a73b6..03dbb13acbc12ea9fdfbfb1bb8c1d622568f850c 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 style="text-decoration: none" id="trial-balance"></a>[Trial balance](http://en.wikipedia.org/wiki/Trial_balance)
-- <a style="text-decoration: none" id="bank-reconciliation"></a> [Bank Reconciliation Report](http://en.wikipedia.org/wiki/Bank_reconciliation)
+- <a class="idOnly" id="trial-balance"></a>[Trial balance](http://en.wikipedia.org/wiki/Trial_balance)
+- <a class="idOnly" 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 style="text-decoration: none" id="chart-of-accounts"></a> [Chart of accounts](http://en.wikipedia.org/wiki/Chart_of_accounts)
--  <a style="text-decoration: none" id="cash-disbursements">Cash Disbursements Journal</a>
-- <a style="text-decoration: none" id="income-report">Income Report</a> (just a list/sum of all Income accounts for a period)
-- <a style="text-decoration: none" id="expenses-report">Expenses Report</a>  (just a list/sum of all Expenses accounts for a period)
+-  <a class="idOnly" id="chart-of-accounts"></a> [Chart of accounts](http://en.wikipedia.org/wiki/Chart_of_accounts)
+-  <a class="idOnly" id="cash-disbursements">Cash Disbursements Journal</a>
+- <a class="idOnly" id="income-report">Income Report</a> (just a list/sum of all Income accounts for a period)
+- <a class="idOnly" 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 5d57d09f2fe40fdec22c62d64f1adbc44a55580a..0cb559e9d4114913ed567235d78989ad01dfb258 100644
--- a/UseCases/WorkFlow.mdwn
+++ b/UseCases/WorkFlow.mdwn
@@ -5,7 +5,7 @@ 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.
 
-## <a id="unaccrued-invoice">The "Unaccrued Invoice" Example</a>
+## <a class="idOnly" id="unaccrued-invoice">The "Unaccrued Invoice" Example</a>
 
 
 The easiest example I have of this relates to accruing income upon invoice
diff --git a/local.css b/local.css
index 12010f18c1aed4147e5a6b586e76609757f85b6c..d2b1902cd8aa1aae3218c12a61d7d0582a6b7372 100644
--- a/local.css
+++ b/local.css
@@ -27,3 +27,6 @@ footer {
 .npoacct-navbar .createlink a {
   color: #ce1f1f;
 }
+a.idOnly {
+text-decoration: none !important;
+}
\ No newline at end of file