--- a/ldp-ucr.html	Fri Aug 23 12:14:12 2013 +0100
+++ b/ldp-ucr.html	Fri Aug 23 12:53:27 2013 +0100
@@ -901,7 +901,7 @@
 		representation may include descriptions of related resources that
 		cannot be accessed directly. Depending upon the application, an
 		server may enrich the retrieved RDF with additional triples. Examples
-		include adding incoming links, sameAs closure and type closure.
+		include adding incoming links, <tt>owl:sameAs</tt> closure and <tt>rdf:type</tt> closure.
 		The HTTP response should also include versioning information (i.e.
 		last update or entity tag) so that subsequent updates can ensure
 		they are being applied to the correct version.</p>
@@ -914,7 +914,7 @@
 	</ul>
 	
 	<section id="s3.1">
-	<h3>Primary scenario</h3>
+	<h3>Primary scenario: retrieve resource description</h3>
 	<p>
 		The user story <a
 			href="#story-project_data"
@@ -965,16 +965,15 @@
 	</section>
 	
 	<section id="s3.2">
-	<h3>Alternative scenario: retrieve description of a non-document resource</h3>
+	<h3>Alternative scenario: retrieve description of a non-document resource (hash URI)</h3>
 	<p>In many cases, the things that are of interest are not
 		always the things that are resolvable. The example below
 		demonstrates how a FOAF profile may be used to distinguish between
 		the person and the profile; the former being the topic of the
-		latter. This begs the question as to what a client should do with
-		such non-document resources. In this case the HTTP protocol
+		latter. Where the fragment is defined relative to the base, as in this example, the URL including the fragment may be used to access the resource representing the containing document. The HTTP protocol
 		requires that the fragment part be stripped off before requesting
-		the URI from the server. The result is a resolvable URI for the
-		profile.</p>
+		the URI from the server. The client can then read properties of the hash URI <tt>&lt;#i&gt;</tt> from the retrieved description.
+	</p>
 	<pre class='example'>
 @base &lt;http://www.w3.org/People/Berners-Lee/card&gt;
 @prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt;.
@@ -1047,8 +1046,7 @@
 	</section>
 	
 	<section id="s4.2">
-	<h3>Alternative scenario: selective
-			update of a resource</h3>
+	<h3>Alternative scenario: selective update of a resource</h3>
 	<p>
 		This relates to user story <a>Data Catalogs</a>, based on the <a href="http://vocab.deri.ie/dcat"
 			title="http://vocab.deri.ie/dcat"
@@ -1444,7 +1442,7 @@
 		<dd>The system shall provide the ability to retrieve resource descriptions, from <a>UC3</a>.
 		</dd>
 		<dt><dfn>F3.2</dfn>:</dt>
-		<dd><strike>The system shall provide the ability to retrieve the description of a non-document resource, from <a>UC3</a></strike>.
+		<dd>The system shall enable the client to retrieve the description of a hash URI, from <a>UC3</a>.
 		</dd>
 		<dt><dfn>F4.1</dfn>:</dt>
 		<dd>The system shall provide the ability to update an existing resource by substitution, from <a>UC4</a>.