--- a/ldp.html	Mon Oct 20 13:40:07 2014 -0400
+++ b/ldp.html	Mon Oct 20 13:56:02 2014 -0400
@@ -256,8 +256,6 @@
    <li>The <a href="#header-accept-post">HTTP Accept-Post header</a>, 
 		that allows clients to determine which media types a server accepts on POST requests.
 	</li>
-   <li>The requirement that LDP clients be <a href="#atrisk-paging">paging-aware</a>.
-	</li>
    <li>JSON-LD as a required <a href="#atrisk-ldpr-jsonld">response representation</a> and <a href="#atrisk-ldpc-jsonld">new member representation</a>.
 	</li>
    <li>Support for <a href="#atrisk-indirect-containers">indirect containers</a>.
@@ -897,17 +895,6 @@
 		including LDP-defined hints.
 	</h2></section>
 	
-	<div class="atrisk" id="atrisk-paging"><p class="atrisktext">Feature At Risk</p>
-	<p>The LDP Working Group proposes incorporation of the following clause to make LDP clients paging aware:</p>
-	</div>
-	<section id="ldpr-cli-paging"><h2 class="normal">
-		<a title="LDP client">LDP clients</a> SHOULD 
-		be capable of processing successful HTTP <code>GET</code> responses formed by a LDP server
-		that independently initiated paging, returning a page of representation instead of full resource
-		representation [[!LDP-PAGING]].
-	</h2>
-	</section> 
-	
 </section> <!-- ldprs-general -->
 
 <section id="ldprs-HTTP_GET">
@@ -2646,6 +2633,7 @@
 <!-- <blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619/">Candidate Recommendation Draft</a></em></blockquote> -->
 
 <ul>
+	<li>2014-10-20 - Removed at-risk feature that clients should be prepared to handle server-initiated paging (SS)</li>
 	<li>2014-10-20 - Define LDP-server-managed for Robert Sanderson thread (JA)</li>
 	<li>2014-10-20 - Update LDPC-Post adding non-normative note for Miguel thread (JA)</li>
 	<li>2014-10-20 - Update LDPC-Post bullet 1 with non-normative text for James Leigh thread (JA)</li>