--- a/ldp.html	Thu Apr 17 11:17:22 2014 -0400
+++ b/ldp.html	Mon Apr 21 08:38:28 2014 -0400
@@ -994,7 +994,7 @@
 	<p>
 	In the preceding example, there is a <code>rdf:type</code> of <code>o:NetWorth</code> indicating the
 	resource represents an instance of a person's net worth and a <code>o:netWorthOf</code> predicate indicating 
-	the associated person.  There are two sets of same-subject, same-predicate pairings; one for assets and
+	the associated person.  There are two sets of same-subject, same-predicate triples; one for assets and
 	one for liabilities.  Existing domain-specific applications exist that depend on those types and 
 	predicates, so changing them <em>incompatibly</em> would be frowned upon.
 	</p>
@@ -1009,9 +1009,9 @@
 	it would be helpful to be able to manage the assets and liabilities triples consistently, for example
 	by using LDP containers.
 	One way to do this is to create two containers, one to manage assets and another liabilities, 
-	as separate HTTP resources.  Existing clients would have no need to interact with those containers,
-	whereas LDP-enabled clients now have container URLs that they can interact with, and the existing
-	resource can remain unchanged so that existing clients continue to function normally.
+	as separate HTTP resources.  Existing clients have no need to interact with those containers,
+	whereas LDP-enabled clients now have container URLs that they can interact with.  The existing
+	resource remains unchanged so that existing clients continue to function normally.
 	This is illustrated in the set of related examples (one example per HTTP resource) below:
 	</p>
 
@@ -1068,7 +1068,7 @@
 	membership predicate is <code>o:asset</code>,
 	from the domain model. A POST of an asset representation to the asset container will create a new
 	asset and add it to net-worth's list of	assets by adding a new membership triple
-	to the resource and containment triple to the container. 
+	to the resource and a containment triple to the container. 
 	</p>
 
 	<p>The second container is a <a title="Linked Data Platform Direct Container">LDP Direct Container</a> to manage liabilities.  
@@ -1119,15 +1119,16 @@
 
 	<p>
 	You might wonder why we chose to create two new containers instead of making
-	<code>http://example.org/netWorth/nw1</code> itself a (single) container.
+	<code>http://example.org/netWorth/nw1</code> itself a container.
 	A single net worth container would be a fine design if <code>http://example.org/netWorth/nw1</code>
 	had only assets or only liabilities (basically: only a single predicate to manage), 
 	but since it has separate predicates for assets and liabilities an ambiguity arises:
-	it is unspecified to whether a client's creation request (POST)
+	it is unspecified whether a client's creation request (POST)
 	should add a new <code>o:asset</code> or <code>o:liability</code> triple. 
 	Having separate <code>http://example.org/netWorth/nw1/assets/</code> 
 	and <code>http://example.org/netWorth/nw1/liabilities/</code> containers
-	allows both assets and liabilities to be created.  Similar ambiguities arise
+	allows both assets and liabilities to be created 
+	and linked to the net-worth resource using the appropriate predicate.  Similar ambiguities arise
 	if the client wishes to list the members and/or contained resources.
 	</p>
 
@@ -1149,7 +1150,7 @@
    a o:NetWorth;
    o:netWorthOf &lt;http://example.org/users/JohnZSmith&gt;;
    o:advisor
-   	 &lt;advisors/bob#me&gt;,
+   	 &lt;advisors/bob#me&gt;,     # URI of a person
    	 &lt;advisors/marsha#me&gt;.
    	 
 &lt;advisors/&gt;
@@ -1159,8 +1160,8 @@
    ldp:hasMemberRelation o:advisor;
    ldp:insertedContentRelation foaf:primaryTopic;
    ldp:contains
-   	 &lt;bob&gt;,
-   	 &lt;marsha&gt;.
+   	 &lt;bob&gt;,     # URI of a document a.k.a. an information resource
+   	 &lt;marsha&gt;.  # describing a person
 </pre>	
 	
 	<p>To handle this type of indirection, the triple with predicate of <code>ldp:insertedContentRelation</code> and object of 
@@ -1171,8 +1172,10 @@
 	<p>This type of container is referred to as a <a title="Linked Data Platform Indirect Container">LDP Indirect Container</a>. 
 	It is similar to an <a title="Linked Data Platform Direct Container">LDP Direct Container</a> 
 	but it provides an indirection to add (via a create request) as a member any resource, 
-	such as a URI representing a real-world object,
-	that is different from the document that is created.</p>
+	including a URI representing a real-world object.  Create requests to 
+	<a title="Linked Data Platform Direct Container">LDP Direct Containers</a> 
+	can only add information resources [[WEBARCH]] - the documents they create - as members.
+	</p>
 
 	<p>
 	To add a another advisor, a client would POST something like this to the advisors container: