--- a/ldp-ucr.html	Mon Aug 19 09:17:36 2013 -0400
+++ b/ldp-ucr.html	Wed Aug 21 10:19:08 2013 +0100
@@ -716,7 +716,7 @@
 		not be interpreted normatively.</p>
 		
 	<section>
-	<h2 id="uc-manage_containers">Use Case: Manage containers</h2>
+	<h2 id="uc-manage_containers">Use Case 1: Manage containers</h2>
 	<p>
 		A number of user stories introduce the idea of a <i>container</i>
 		as a mechanism for creating and managing resources within the
@@ -796,7 +796,7 @@
 	</section>
 	
 	<section>
-	<h2 id="uc-manage_resources">Use Case: Manage resources</h2>
+	<h2 id="uc-manage_resources">Use Case 2: Manage resources</h2>
 	<p>
 		This use case addresses the managed lifecycle of a resource and is
 		concerned with resource <i>ownership</i>. The responsibility for
@@ -910,8 +910,7 @@
 	</section>
 	
 	<section>
-	<h2 id="uc-retrieve_resource_description">Use Case: Retrieve resource
-			description</h2>
+	<h2 id="uc-retrieve_resource_description">Use Case 3: Retrieve resource description</h2>
 	<p>Access the current description of a resource, containing
 		properties of that resource and links to related resources. The
 		representation may include descriptions of related resources that
@@ -1010,7 +1009,7 @@
 	</section>
 	
 	<section>
-	<h2 id="uc-update_existing">Use Case: Update existing resource</h2>
+	<h2 id="uc-update_existing">Use Case 4: Update existing resource</h2>
 	<p>
 		Change the RDF description of a LDP resource, potentially removing
 		or overwriting existing data. This allows applications to <i>enrich</i>
@@ -1121,8 +1120,7 @@
 	</section>
 	
 	<section>
-	<h2 id="uc-has_resource_changed">Use Case: Determine if a resource has
-			changed</h2>
+	<h2 id="uc-has_resource_changed">Use Case 5: Determine if a resource has changed</h2>
 	<p>
 		It should be possible to retrieve versioning information about a
 		resource (e.g. last modified or entity tag) without having to
@@ -1185,7 +1183,7 @@
 	</section>
 	
 	<section>
-	<h2 id="uc-aggregate_resources">Use Case: Aggregate resources</h2>
+	<h2 id="uc-aggregate_resources">Use Case 6: Aggregate resources</h2>
 	<p>
 		There is a requirement to be able to manage <i>collections</i> of
 		resources. The concept of a collection overlaps with, but is
@@ -1280,7 +1278,7 @@
 	</section>
 	
 	<section>
-	<h2 id="uc-filter_resource_description">Use Case: Filter resource description</h2>
+	<h2 id="uc-filter_resource_description">Use Case 7: Filter resource description</h2>
 	<p>This use case extends the normal behaviour of retrieving an
 		RDF description of a resource, by dynamically excluding specific
 		(membership) properties. For containers, it is often desirable to
@@ -1403,7 +1401,7 @@
 	</section>
 	
 	<section>
-	<h2 id="uc-manage_media_resources">Use Case: Manage media resources</h2>
+	<h2 id="uc-manage_media_resources">Use Case 8: Manage media resources</h2>
 	<p>It should be possible to easily add non-RDF media resources
 		to containers that accept them. Media resources may be updated and
 		removed during the lifecycle of the container.</p>