--- a/ldp-ucr.html	Fri Aug 23 14:49:55 2013 +0100
+++ b/ldp-ucr.html	Fri Aug 23 15:05:48 2013 +0100
@@ -733,6 +733,7 @@
 	
 	<section id="s1.1">
 	<h3>Primary scenario: create a container</h3>
+	<div>(see functional requirement <a>F1.1</a>)</div>
 	<p>
 		Create a new container resource within the LDP server. In <a>Services Supporting the Process of Science</a>, 
 			<a
@@ -930,8 +931,7 @@
 			title="http://www.epimorphics.com/public/vocabulary/org.html"
 			rel="nofollow">organizational ontology</a>.
 	</p>
-	<p>Note that the example below defines two resources (shown as
-		Examples 4 and 5 below) that would be hosted on an LDP server based at
+	<p>Examples 4 and 5 below define two resources 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>
@@ -1400,9 +1400,9 @@
 		Clients submit a non-RDF representation to a container in a media
 		type accepted by that container. The container creates a URI to
 		represent this media resource, and creates a link from the
-		container to the new URI.The media resource may have an explicit
-		representation of the media type. It should be possible to find
-		the metadata about such a resource and to access and edit it in
+		container to the new URI. The media resource may be accompanied by an explicit RDF
+		description of the media. It should be possible to find the
+		metadata about such a resource and to access and edit it in
 		the usual ways.
 	</p>
 	<p>
@@ -1414,7 +1414,7 @@
 @prefix ma: &lt;http://www.w3.org/ns/ma-ont#&gt; .
 
 &lt;dataset&gt; a ma:Collection ;
-	:hasMember &lt;dataset/image1.jpg&gt;
+	ma:hasMember &lt;dataset/image1.jpg&gt;
 
 &lt;dataset/image1.jpg&gt; a ma:MediaResource ;
 	ma:hasFormat &quot;image/jpeg&quot; .
@@ -1424,7 +1424,7 @@
 	<section id="s9.2">
 	<h3>Alternative scenario: media-resource attachments</h3>
 	<p>
-		A resource may have multiple <i>renditions</i>; the idea that you
+		A resource may have multiple <i>renditions</i>. For example, you
 		can have a PDF and a JPEG representing the same thing. A user is
 		trying to create a work order along with an attached image showing
 		a faulty machine part. To the user and to the work order system,