--- a/ldp.html	Fri Feb 07 11:44:00 2014 -0500
+++ b/ldp.html	Fri Feb 07 12:01:23 2014 -0500
@@ -1225,7 +1225,6 @@
    dcterms:title "The assets of JohnZSmith";
    ldp:containerResource <>;
    ldp:containsRelation o:asset;
-   ldp:insertedContentRelation ldp:MemberSubject;
    ldp:contains <a1>, <a2>.
 </pre>
 
@@ -1241,7 +1240,6 @@
    dcterms:title "The liabilities of JohnZSmith";
    ldp:containerResource &lt;&gt;;
    ldp:containsRelation o:liability;
-   ldp:insertedContentRelation ldp:MemberSubject;
    ldp:contains &lt;l1&gt;, &lt;l2&gt;, &lt;l3&gt;.
 </pre>
 
@@ -1313,13 +1311,13 @@
 </pre>	
 	
 	<p>To handle this type of indirection, the triple with predicate of <code>ldp:insertedContentRelation</code> and object of 
-	<code>foaf:primaryTopic</code> informs clients that when POSTing to this container, they will include a triple of the
+	<code>foaf:primaryTopic</code> informs clients that when POSTing to this container, they need to include a triple of the
 	form <code>(&lt;&gt;, foaf:primaryTopic, topic-URI)</code> to inform the server which URI to use 
 	(<code>topic-URI</code>) in the new membership triple.</p>
 	
 	<p>This type of container is also referred to as an <a title="Linked Data Platform Indirect Container">LDP Indirect Container</a>. 
 	It is similar to a an <a title="Linked Data Platform Direct Container">LDP Direct Container</a> 
-	but it allows an indirection with the ability to add (via a create request) as member any resource, 
+	but it provides an indirection to add (via a create request) as member any resource, 
 	such as a URI representing a real-world object,
 	that is different from the document that is created.</p>
 
@@ -1333,7 +1331,7 @@
     </figure>
 
 <div class="ldp-issue-pending">
-<p>Still editing for ACTION-120 -- table work in progress, fate unknown</p>
+<p>PENDING -- table work in progress, if found valuable...we'll keep.</p>
 	
 	<p>The following table illustrates some differences between <a title="membership">membership</a> and 
 	<a title="containment">containment</a> triples.  For details on the normative behavior, see appropriate sections
@@ -1342,7 +1340,7 @@
 	<table border="1" id="ldpc-mbrcntdiff">
 		<thead><tr><th rowspan="2">Completed Request</th><th colspan="2">Effects</th></tr>
 		       <tr><th>Membership</th><th>Containment</th></tr></thead>
-		<tr><td>LDPR created in LDPC</td><td>New triple based on type of container (see following rows)</td><td>New triple: 
+		<tr><td>LDPR created in LDPC (any subtype)</td><td>New triple based on type of container (see following rows)</td><td>New triple: 
 			(LDPC, ldp:contains, LDPR)</td></tr>
 		<tr><td>LDPR created in LDP-BC</td><td>New triple: (LDPC, ldp:contains, LDPR)</td><td>Same</td></tr>
 		<tr><td>LDPR created in LDP-DC</td><td>New triple links LDP-RR to created LDPR. LDP-RR URI may be same as LDP-DC</td>