--- a/ldp.html	Thu Jul 11 14:05:00 2013 -0400
+++ b/ldp.html	Thu Jul 11 14:26:05 2013 -0400
@@ -1174,8 +1174,6 @@
 	<p>While the same non-member resource could be used to update the non-member properties via PUT,
 		LDP recommends using PATCH for this purpose.</p>
 
-	<div id="ldpc-5.1.3" class="rule">5.1.3 <strike>Paging</strike> <em>Was paging, moved to section 4</em></div>
-
 	<div id="ldpc-ordering" class="rule">5.1.4 Ordering</div>
 	<em>This section is non-normative</em>
 	<p>
@@ -1399,27 +1397,6 @@
 		or MAY be another resource (as in the <a href="#ldpc-ex-membership-subj">example</a>).  See also
 		<a href="#ldpc-5_2_3">5.2.3</a>.
 	</div>
-
-	<div id="ldpc-5_3_2" class="rule">5.3.2  Empty after resolution of Issue-64,
-		left here for now to avoid renumbering all that follows.  Content moved to <a href="#ldpc-HTTP_HEAD">LDPC HEAD</a>.
-	</div>
-	
-	<div id="ldpc-5_3_3" class="rule">5.3.3 Empty after resolution of Issue-65, 
-		left here for now to avoid renumbering all that follows.
-		Used to be <blockquote><strike>
-		An LDPC server that does not support a request to retrieve the first
-		page resource representation from a known LDPC whose URL is “<code>&lt;containerURL&gt;</code>” by using
-		the Request-URI “<code>&lt;containerURL&gt;?firstPage</code>”, MUST return a HTTP status code 404 (Not
-		Found).
-		An LDPC server that supports that request using a different Request-URI than “<code>&lt;containerURL&gt;?firstPage</code>”,
-		MUST return a HTTP Redirection 3xx status code such as 301 (Moved Permanently) or 302 (Found).
-		</strike></blockquote>
-	</div>
-	
-	<div id="ldpc-5_3_4" class="rule">5.3.4 <strike>LDPC servers SHOULD allow clients to retrieve large LDPCs in
-		pages.</strike> Moved to section 4</div>
-	<div id="ldpc-5_3_5" class="rule">5.3.5 <strike>LDPC servers MAY split the response representation of any LDPC</strike> moved to section 4</div>
-	<div id="ldpc-5_3_6" class="rule">5.3.6 <strike>LDPC servers that support paging MUST include in the page</strike> moved to section 4</div>
 	
 	<div id="ldpc-5_3_7" class="rule">5.3.7 LDPC servers MAY represent the members of a paged LDPC in a sequential
 		order.  If the server does so, it MUST be specify the order using a triple 
@@ -1922,6 +1899,7 @@
 <blockquote><em><a href="http://www.w3.org/TR/2013/WD-ldp-20130701/">Third Public Working Draft</a></em></blockquote>
 -->
 <ul>
+	<li>2013-07-11 - Removed all stubbed out sections 5.1.3, 5.3.2-6 (SS)</li>
 	<li>2013-07-11 - Various editorial clean up items from editor todo list (SS)</li>
 	<li>2013-07-11 - Removed closed issues that required no new spec changes: 50, 56, 16, 19, 17 (SS)</li>
 	<li>2013-07-11 - ISSUE-51 Added how a LDPR can show which LDPC is it in (SS)</li>
@@ -2042,7 +2020,7 @@
 	</li>
 	<li>using respec section labeling consistently
 	</li>
-	<li>update ldpc's with all required props
+	<li>update ldpc samples with all required props
 	</li>
 </ul>
 	</li>