--- a/ldp-ucr.html	Mon Jun 24 16:39:39 2013 +0100
+++ b/ldp-ucr.html	Mon Jun 24 16:56:30 2013 +0100
@@ -1477,16 +1477,13 @@
 	frbr:creator <#Vonnegut_Kurt>;
 	frbr:manifestation <ebook21279>.
 </pre>
-	<p>Collections are potentially very large, so some means may be
-		required to limit the size of RDF representation returned by the
-		LDP server (e.g. pagination).</p>
 	</section>
 	</section>
 	
 	<section>
 		<h2 id="uc-pagination">Use case: Retrieve a large resource description in multiple parts</h2>
 
-This use case addresses a problem with the “resource-centric” approach to interacting with RDF data. The problem is that some resources participate in a very large number of triples, and therefore a “resource-centric” granularity leads to resource descriptions that are too large to be practically processed in a single HTTP request. This use-case applies to all resources, not just containers.
+<p>This use case addresses a problem with the “resource-centric” approach to interacting with RDF data. The problem is that some resources participate in a very large number of triples, and therefore a “resource-centric” granularity leads to resource descriptions that are too large to be practically processed in a single HTTP request. This use-case applies to all resources, not just containers.</p>
 
 		<ul>
 			<li>It's not really the resource description that's being paginated, but the values of a particular property.</li>
@@ -1498,10 +1495,10 @@
 		<section>
 		<h3 id="scen-access_media_resources">Primary scenario: large numbers of contacts</h3>
 
-In user-story, <a href="#story-social" title="Social Contacts">Maintaining Social Contact Information</a>, it is not uncommon for users to have a very large number of contacts.
-This leads to a very large resource description, especially if some basic information about the contacts is included as well. The size of this representation may be so large that retrieval in a single HTTP request is impractical.
+<p>In user-story, <a href="#story-social" title="Social Contacts">Maintaining Social Contact Information</a>, it is not uncommon for users to have a very large number of contacts.
+This leads to a very large resource description, especially if some basic information about the contacts is included as well. The size of this representation may be so large that retrieval in a single HTTP request is impractical.</p>
 
-In this example the response to the first request includes a reference to the <i>next</i> resource in an ordered collection of resources. For the purposes of the example, we make use of the <i>next</i> property defined by the <a href="http://www.w3.org/1999/xhtml/vocab/">XHTML Metainformation Vocabulary</a>. There should be no presumption that the LDP specification will recommend the use of this vocabulary to support this use-case.
+<p>In this example the response to the first request includes a reference to the <i>next</i> resource in an ordered collection of resources. For the purposes of the example, we make use of the <i>next</i> property defined by the <a href="http://www.w3.org/1999/xhtml/vocab/">XHTML Metainformation Vocabulary</a>. There should be no presumption that the LDP specification will recommend the use of this vocabulary to support this use-case.</p>
 		<pre class='example'>
 @prefix : &lt;http://example.com/people/&gt;.
 @prefix xhv: &lt;http://www.w3.org/1999/xhtml/vocab#&gt;.
@@ -1513,9 +1510,9 @@
 <> xhv:next &lt;http://example.com/1234567890&gt;.
 		</pre>
 		
-		When the client requests the resource identified by <i>next</i>, the response includes additional content that can be merged with the earlier data to construct a more complete model of the originally requested resource. It may also contain further <i>next</i> links, which may be requested in turn. 
+<p>When the client requests the resource identified by <i>next</i>, the response includes additional content that can be merged with the earlier data to construct a more complete model of the originally requested resource. It may also contain further <i>next</i> links, which may be requested in turn.</p> 
 		
-		The following representation is the response to the resource identified by <i>next</i>, completing the contacts list.
+<p>The following representation is the response to the resource identified by <i>next</i>, completing the contacts list.</p>
 		
 		<pre class='example'>
 @prefix : &lt;http://example.com/people/&gt;.