--- a/ldp-paging.html	Mon Oct 06 14:10:09 2014 -0400
+++ b/ldp-paging.html	Fri Oct 10 13:53:51 2014 -0400
@@ -308,7 +308,8 @@
 
 	<dt><dfn>LDP server</dfn></dt>
 	<dd>A conforming HTTP server [[RFC7230]] that follows the rules defined by [[LDP]]
-	    when it is serving LDPRs and LDPCs.
+	    when it is serving <abbr title="Linked Data Platform Resources">LDPRs</abbr> and 
+		<abbr title="Linked Data Platform Containers">LDPCs</abbr>.
 	<p></p></dd>	
 
 	<dt><dfn>LDP client</dfn></dt>
@@ -321,21 +322,21 @@
 		patterns and conventions in [[LDP]].<p></p></dd>
 		
 	<dt><dfn>Linked Data Platform RDF Source</dfn> (<abbr title="Linked Data Platform RDF Source">LDP-RS</abbr>)</dt>
-	<dd>An <a title="Linked Data Platform Resource">LDPR</a> whose state is fully represented in RDF.
+	<dd>An <a title="Linked Data Platform Resource">LDPR</a> whose state is fully represented in RDF [[LDP]].
 	<p></p></dd>	
 
 	<dt><dfn>Linked Data Platform Container</dfn> (<abbr title="Linked Data Platform Container">LDPC</abbr>)</dt>
 	<dd>A LDP-RS representing a collection of <a title="Linked Data Platform Resource">LDPRs</a> linked by
-	<a>membership triples</a> and <a>containment triples</a>.
+	<a>membership triples</a> and <a>containment triples</a> [[LDP]].
 	<p></p></dd>
 	
 	<dt><dfn>Membership triples</dfn></dt>
-	<dd>A set of triples that lists an <a title="Linked Data Platform Container">LDPC's</a> members.
+	<dd>A set of triples that lists an <a title="Linked Data Platform Container">LDPC's</a> members [[LDP]].
 	<p></p></dd>
 	
 	<dt><dfn>Containment triples</dfn></dt>
 	<dd>
-	A set of triples, maintained by an LDPC, that lists documents created by the LDPC but not yet deleted.
+	A set of triples, maintained by an LDPC, that lists documents created by the LDPC but not yet deleted [[LDP]].
 	<p></p></dd>
 
   </dl>
@@ -632,15 +633,15 @@
 		to "the first subset of all customer relations information".  This would require changes to
 		any existing clients whose code was built using the original definition however, so it's 
 		more likely that Example Co. would mint a new URI for "the first subset", define a way to 
-		find subsequent subsets, and have clients use this new protocol.
+		find subsequent subsets, and have clients use this new "first subset" URI approach.
 	</p>
 	<p>
-		The new protocol does not solve the problem of migrating existing clients from the old
+		The "first subset" URI approach does not solve the problem of migrating existing clients from the old
 		"all" to the new "first subset" semantic; neither would a <code>303 See Other</code> redirect
 		from the old to the new URI, given the 
 		<a href="http://www.w3.org/2001/tag/issues.html#httpRange-14">widespread historical client practice</a> of automatically
 		following <code>303</code> redirects and treating the redirected-to resource as equivalent
-		to the original.  The safe route is to have clients explicitly tell the server that they
+		to the original, contrary to HTTP.  The safe route is to have clients explicitly tell the server that they
 		are capable of handling the "first subset" semantic on the redirected-to URI; this is what
 		LDP Paging does.
 	</p>
@@ -1193,7 +1194,7 @@
 		<tr>
 		<td> <code>max-member-count</code> </td>
 		<td> The maximum decimal number of members the client wishes to appear on each page.
-				This parameter is only meaningful for paged containers.
+				This parameter is only meaningful for paged <a title="Linked Data Platform Container">LDPCs</a>.
 		</td>
 		</tr>
 		</table>
@@ -2239,6 +2240,7 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-paging-20140930/">Candidate Recommendation Draft</a></em></blockquote> wah -->
 
 <ul>
+	<li>2014-10-10 - Clarified "new protocol" in 4.2, hyper-linked max-member-count to LDPCs per 10/10 public comments email (JA) </li>
 	<li>2014-09-26 - Added non-norm items about extensions to supply client requested ordering (SS) </li>
 </ul>