--- a/ldp-ucr.html	Thu Jul 25 13:01:31 2013 -0400
+++ b/ldp-ucr.html	Fri Jul 26 11:15:09 2013 +0100
@@ -154,11 +154,7 @@
 			capture statements about system requirements written from a user
 			or application perspective. They are typically lightweight and
 			informal and can run from one line to a paragraph or two
-			(sometimes described as an 'epic') <a
-			href="http://www.agilemodeling.com/artifacts/userStory.htm"
-			class="external autonumber"
-			title="http://www.agilemodeling.com/artifacts/userStory.htm"
-			rel="nofollow">[2]</a>. Analysis of each user story will reveal a
+			(sometimes described as an 'epic') [[COHN-2004]]. Analysis of each user story will reveal a
 			number of (functional) use cases and other non-functional
 			requirements. See <em>Device API Access Control Use Cases and Requirements</em> [[DAP-REQS]] for a good example
 			of user stories and their analysis.</li>
@@ -166,16 +162,9 @@
 	<ul>
 		<li><b><a href="#use cases" title="Use Cases">Use Cases</a></b> are
 			used to capture and model functional requirements. Use cases
-			describe the system’s behavior under various conditions <a
-			href="http://alistair.cockburn.us/get/2465"
-			class="external autonumber"
-			title="http://alistair.cockburn.us/get/2465" rel="nofollow">[3]</a>,
+			describe the system’s behavior under various conditions [[COCKBURN-2000]],
 			cataloging who does what with the system, for what purpose, but
-			without concern for system design or implementation <a
-			href="http://www.bredemeyer.com/pdf_files/functreq.pdf"
-			class="external autonumber"
-			title="http://www.bredemeyer.com/pdf_files/functreq.pdf"
-			rel="nofollow">[4]</a>. Each use case is identified by a
+			without concern for system design or implementation. Each use case is identified by a
 			reference number to aid cross-reference from other documentation;
 			use case indexing in this document is based on rdb2rdf
 			use cases [[RDB2RDF-UC]]. A variety of styles may be used to capture use cases,