--- a/ldp-ucr.html	Fri Aug 23 12:53:27 2013 +0100
+++ b/ldp-ucr.html	Fri Aug 23 13:39:20 2013 +0100
@@ -931,11 +931,16 @@
 			rel="nofollow">organizational ontology</a>.
 	</p>
 	<p>Note that the example below defines two resources (shown as
-		separate sections below) that will be hosted on an LDP server based at
-		http://example.com/. The representations of these resources may
+		Examples 4 and 5 below) that would be hosted on an LDP server based at
+		<http://example.com/>. The representation in Example 4 describes <http://example.com/member1>, while that of Example 5 describes <http://example.com/role>.
+		A client reading Example 4 would have to separately retrieve Example 5 in order to get role information such as its descriptive label.
+	</p>
+	<p>
+		Note that the representations of these resources may
 		include descriptions of related resources, such as
-		http://www.w3.org/, that that fall under a different authority and
-		therefore can't be served from the LDP server at this location.</p>
+		http://www.w3.org/, that that fall under a completely different authority and
+		therefore can't be served directly from the LDP server at this location.</p>
+	<div>
 	<pre class='example'>
 @prefix org: &lt;http://www.w3.org/ns/org#&gt; .
 @prefix owltime: &lt;http://www.w3.org/2006/time&gt; .
@@ -953,6 +958,8 @@
 	skos:prefLabel &quot;The World Wide Web Consortium&quot;@en ;
 	skos:altLabel &quot;W3C&quot; .
 </pre>
+</div>
+<div>
 <pre class='example'>
 @prefix org: &lt;http://www.w3.org/ns/org#&gt; .
 @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
@@ -962,6 +969,7 @@
 	rdfs:label &quot;Director&quot; .
  
 </pre>
+</div>
 	</section>
 	
 	<section id="s3.2">
@@ -1011,7 +1019,10 @@
 		provides a natural granularity for substituting, or overwriting a
 		resource and its data. The simplest kind of update would simply
 		replace what is currently known about a resource with a new
-		representation. There are two distinct resources in the example
+		representation. 
+	</p>
+	<p>
+		There are two distinct resources in the example
 		below; a sporting event and an associated award. The granularity
 		of the resource would allow a user to replace the information about the
 		award without disturbing the information about the event.
@@ -1026,7 +1037,7 @@
 
 &lt;#gold_medal&gt; a sport:Award .
 </pre>
-	<p>We can enrich the description as events unfold, linking to
+	<p>The description can be enriched as events unfold, adding a link to
 		the winner of the gold medal by substituting the above description
 		with the following.</p>
 	<pre class='example'>
@@ -1067,7 +1078,7 @@
 		just the new dataset links. For example, a <a
 			href="http://docs.api.talis.com/getting-started/changesets"
 			title="http://docs.api.talis.com/getting-started/changesets"
-			rel="nofollow">Talis changeset</a> might be used to add a new dc:title to the
+			rel="nofollow">Talis changeset</a> might be used to add a new <tt>dc:title</tt> to the
 		dataset. The following update would be directed to the catalogue
 		to add an additional dataset.
 	</p>
@@ -1106,7 +1117,7 @@
 	</p>
 	
 	<section id="s5.1">
-	<h3>Primary scenario</h3>
+	<h3>Primary scenario: determine if a resource has changed</h3>
 	<p>
 		Based on the user story, <a>Constrained Devices and Networks</a>, an LDP server could be configured to
 		act as a proxy for a CoAP [[COAP]] based <a
@@ -1127,6 +1138,8 @@
 	</p>
 	<pre class='example'>
 @prefix : &lt;http://example.com/energy-management/&gt;.
+@prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
+@prefix ssn: &lt;http://purl.oclc.org/NET/ssnx/ssn#&gt; .
 
 &lt;&gt; a :MainsFrequencySensor;
   rdfs:comment &quot;Sense grid load based on mains frequency&quot;;
@@ -1144,7 +1157,10 @@
 		change independently.
 	</p>
 	<pre class='example'>
-@prefix : &lt;http://example.com/energy-management/&gt;.
+@prefix : &lt;http://example.com/energy-management/&gt; .
+@prefix ssn: &lt;http://purl.oclc.org/NET/ssnx/ssn#&gt; .
+@prefix xsd: &lt;http://www.w3.org/2001/XMLSchema#&gt; .
+
 
 &lt;http://example.com/energy-management#property_1&gt; :hasMeasurementPropertyValue &lt;&gt; .
 &lt;&gt; a :FrequencyValue;