--- a/ldp.html	Wed Feb 12 07:42:09 2014 -0500
+++ b/ldp.html	Wed Feb 12 08:03:05 2014 -0500
@@ -1209,7 +1209,7 @@
 	the associated person.  There are two sets of same-subject, same-predicate pairings; one for assets and
 	one for liabilities.  It would be helpful to be able to associate these multi-valued sets using a URL
 	for them to assist with managing these, this is done by associating containers with them as 
-	illustrated in the 3 examples below:
+	illustrated in the set of related examples (one example per HTTP resource) below:
 	</p>
 
 <pre class="example" id="ldpc-ex-membership-full"># The following is an elaborated representation of LDPR
@@ -1234,14 +1234,14 @@
 <pre class="example" id="ldpc-ex-membership-subj"># The following is an elaborated representation of LDPC
 #   http://example.org/netWorth/nw1/assetContainer/
 <!-- @base is here only so it's easier to paste into validators for checking -->
-# @base &lt;http://example.org/netWorth/nw1/assetContainer/&gt;
+# @base &lt;http://example.org/netWorth/nw1/assetContainer/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix o: &lt;http://example.org/ontology/&gt;.
 &lt;&gt;
    a ldp:Container, ldp:DirectContainer;
    dcterms:title "The assets of JohnZSmith";
-   ldp:containerResource &lt;&gt;;
+   ldp:containerResource &lt;http://example.org/netWorth/nw1/&gt;;
    ldp:containsRelation o:asset;
    ldp:contains &lt;a1&gt;, &lt;a2&gt;.
 </pre>
@@ -1249,20 +1249,21 @@
 <pre class="example" id="ldpc-ex-membership-full-liabcont"># The following is an elaborated representation of LDPC
 #   http://example.org/netWorth/nw1/liabilityContainer/
 <!-- @base is here only so it's easier to paste into validators for checking -->
-# @base &lt;http://example.org/netWorth/nw1/liabilityContainer/&gt;
+# @base &lt;http://example.org/netWorth/nw1/liabilityContainer/&gt;.
 @prefix ldp: &lt;http://www.w3.org/ns/ldp#&gt;.
 @prefix dcterms: &lt;http://purl.org/dc/terms/&gt;.
 @prefix o: &lt;http://example.org/ontology/&gt;.
 &lt;&gt;
    a ldp:Container, ldp:DirectContainer;
    dcterms:title "The liabilities of JohnZSmith";
-   ldp:containerResource &lt;&gt;;
+   ldp:containerResource &lt;http://example.org/netWorth/nw1/&gt;;
    ldp:containsRelation o:liability;
    ldp:contains &lt;l1&gt;, &lt;l2&gt;, &lt;l3&gt;.
 </pre>
 
 	<p>The essential structure of the container is
-	the same, but in this example, the consistent membership value (still in the subject position) is not the
+	the same, but in this example, the consistent membership value 
+	(<a title="Membership triples">membership-constant-URI</a>, still in the subject position) is not the
 	container itself – it is a separate net worth resource. The
 	membership predicates are <code>o:asset</code> and <code>o:liability</code> – predicates
 	from the domain model. A POST of an asset representation to the asset container will create a new
@@ -2573,6 +2574,7 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130730/">Last Call Draft</a></em></blockquote> -->
 <ul>
+	<li>2014-02-12 - Updated containerResource on examples 6 and 7, section 6.1, in resp to public-ldp email (JA)</li>
 	<li>2014-02-12 - Updated LDP-IC definition per email thread (JA)</li>
 	<li>2014-02-11 - Updated LDPC create ldp:contains (errant MAY to MUST, resolving conflicting statements) (JA)</li>
 	<li>2014-02-10 - Removed LDPR Paging HTTP OPTIONS section (no longer needed) and more cleanup of todos (SS)</li>