--- a/TR/ldp-ucr.html	Mon Jan 28 22:01:03 2013 +0100
+++ b/TR/ldp-ucr.html	Mon Jan 28 22:35:29 2013 +0100
@@ -623,7 +623,7 @@
 		</li>
 	</ul>
 	<ul>
-		<li>Browsing: &quot;<a title="" href="#uc-Filter_resource_description">Support end-user browsing through groups</a> and
+		<li>Browsing: &quot;<a title="" href="#uc-filter_resource_description">Support end-user browsing through groups</a> and
 			resources that belong to the groups.&quot;
 		</li>
 	</ul>
@@ -703,7 +703,7 @@
 	<h3 id="story-media"><span class="secno">3.7 </span>Metadata Enrichment in Broadcasting</h3>
 	<p>
 		There are many different use cases when broadcasters show interest
-		in metadata <a title="" href="#uc-pdate_existing">
+		in metadata <a title="" href="#uc-update_existing">
 			enrichment</a>:
 	</p>
 	<ul>
@@ -1481,8 +1481,8 @@
 		collections.
 	</p>
 	<p>
-		As a machine-readable collection of medical terms, the <a rel="nofollow" title="http://www.ihtsdo.org|" href="http://www.ihtsdo.org|">SNOMED</a> ontology
-		is of key importance in <a title="" href="#Healthcare">
+		As a machine-readable collection of medical terms, the <a rel="nofollow" title="http://www.ihtsdo.org/" href="http://www.ihtsdo.org/">SNOMED</a> ontology
+		is of key importance in <a title="" href="#healthcare">
 			healthcare</a>. SNOMED CT allows concepts with more than one parent
 		that don't fall into a lattice. In the example below, the same
 		concept may fall under two different parent concepts. The example
@@ -1515,8 +1515,8 @@
 	<h4 id="scen-retrieve_collection-level_description"><span class="secno">4.7.1 </span>Primary scenario: retrieve
 			collection-level description</h4>
 	<p>
-		This scenario, based on <a title="" href="#Library_Linked_Data">
-			Library Linked Data</a>, uses the Dublin Core Metadata Initiative <a rel="nofollow" title="http://dublincore.org/groups/collections/collection-application-profile/|" href="http://dublincore.org/groups/collections/collection-application-profile/|">Collection-Level</a> description. A collection can
+		This scenario, based on <a title="" href="#library-linked-data">
+			Library Linked Data</a>, uses the Dublin Core Metadata Initiative <a rel="nofollow" title="http://dublincore.org/groups/collections/collection-application-profile/" href="http://dublincore.org/groups/collections/collection-application-profile/">Collection-Level</a> description. A collection can
 		refer to any aggregation of physical or digital items. This
 		scenario covers the case whereby a client can request a
 		collection-level description as typified by the example below,
@@ -1582,7 +1582,7 @@
 	<h4 id="scen-access_media_resources"><span class="secno">4.8.1 </span>Primary scenario: access media
 			resources</h4>
 	<p>
-		From the User Story <a title="" href="#Sharing_Binary_Resources_and_Metadata">
+		From the User Story <a title="" href="#sharing-binary-resources-and-metadat">
 			Sharing Binary Resources and Metadata</a> it should be possible to
 		easily add non-RDF resources to containers that accept them.
 		Clients submit a non-RDF representation to a container in a media
@@ -1644,7 +1644,7 @@
 		</li>
 		<li>Creation of resources (within a container), from <a title="" href="#uc-manage_resources">Use Case: Manage resources</a>
 		</li>
-		<li>Deletion of resources, from <a title="" href="#uc-amnage_resources">Use Case: Manage resources</a>
+		<li>Deletion of resources, from <a title="" href="#uc-manage_resources">Use Case: Manage resources</a>
 		</li>
 		<li>Moving contained resources, from <a title="" href="#uc-manage_resources">Use Case: Manage resources</a>
 		</li>