--- a/ldp-ucr.html	Fri Aug 23 13:39:20 2013 +0100
+++ b/ldp-ucr.html	Fri Aug 23 14:28:18 2013 +0100
@@ -1194,8 +1194,7 @@
 	</ul>
 	
 	<section id="s6.1">
-	<h3>Primary scenario: add a resource
-			to a collection</h3>
+	<h3>Primary scenario: add a resource to a collection</h3>
 	<p>
 		This example is from <a>Library Linked Data</a> and LLD-UC [[LLD-UC]], specifically <a
 			href="http://www.w3.org/2005/Incubator/lld/wiki/Use_Case_Subject_Search"
@@ -1205,15 +1204,18 @@
 	<p>There is an existing collection at
 		&lt;http://example.com/concept-scheme/subject-heading&gt; that
 		defines a collection of subject headings. This collection is
-		defined as a skos:ConceptScheme and the client wishes to insert a
+		defined as a <tt>skos:ConceptScheme</tt> and the client wishes to insert a
 		new concept into the scheme. which will be related to the
-		collection via a skos:inScheme link. The new subject-heading,
+		collection via a <tt>skos:inScheme</tt> link. The new subject-heading,
 		"outer space exploration", is not necessarily owned by a
 		container. The following RDF would be added to the (item-level)
-		description of the collection.</p>
+		description of the collection. </p>
+		<p>This example demonstrates that the relationship between the parent and child resources may run in a seemingly counter-intuitive direction, from child to parent.
+		</p>
 	<pre class='example'>
 @prefix scheme : &lt;http://example.com/concept-scheme/&gt;.
 @prefix concept : &lt;http://example.com/concept/&gt;.
+@prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt; .
 
 scheme:subject-heading a skos:ConceptScheme.
 
@@ -1222,11 +1224,10 @@
 	</section>
 	
 	<section id="s6.2">
-	<h3>Alternative scenario: add a
-			resource to multiple collections</h3>
+	<h3>Alternative scenario: add a resource to multiple collections</h3>
 	<p>
 		Logically, a resource should not be owned by more than one
-		container. however, it may be a member of multiple collections
+		container. However, it may be a member of multiple collections
 		which define a weaker form of <i>aggregation</i>. As this is
 		simply a manipulation of the RDF description of a collection, it
 		should be possible to add the same resource to multiple
@@ -1236,23 +1237,27 @@
 		As a machine-readable collection of medical terms, the <a
 			href="http://www.ihtsdo.org"
 			title="http://www.ihtsdo.org" rel="nofollow">SNOMED</a> ontology
-		is of key importance in user story,<a>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
-		uses skos:narrowerTransitive to elide intervening concepts.
+		is of key importance in user story, <a>Healthcare</a>. SNOMED CT allows concepts with more than one parent. In the example below, SNOMED concepts are treated as
+		collections (aggregations) of narrower concepts. We see that the 
+		concept <tt>:TissueSpecimenFromHeart</tt> belongs to two parent collections as it is both a  <tt>:TissueSpecimen</tt> and a <tt>:SpecimenFromHeart</tt>.
+		This example demonstrates how composition and aggregation support different scenarios, as the ability to have multiple parents should not be a possibility with composition.
 	</p>
 	<pre class='example'>
 @prefix : &lt;http://example.com/snomed/&gt;.
+@prefix skos: &lt;http://www.w3.org/2004/02/skos/core#&gt; .
 
-:_119376003 a skos:Concept ;
+:TissueSpecimen a skos:Concept ;
+	:conceptID "119376003";
 	skos:prefLabel &quot;Tissue specimen&quot;
 	skos:narrowerTransitive :TissueSpecimenFromHeart.
    
-:_127462005 a skos:Concept ;
+:SpecimenFromHeart a skos:Concept ;
+	:conceptID "127462005";
 	skos:prefLabel &quot;Specimen from heart&quot;
-   skos:narrowerTransitive :TissueSpecimenFromHeart.
+	skos:narrowerTransitive :TissueSpecimenFromHeart.
 
-:_128166000 a skos:Concept;
+:TissueSpecimenFromHeart a skos:Concept;
+	:conceptID "128166000";
 	rdfs:label &quot;Tissue specimen from heart&quot;.
 </pre>
 	</section>