--- a/ldp.html	Mon Jul 21 13:33:24 2014 -0500
+++ b/ldp.html	Mon Jul 28 12:17:48 2014 -0400
@@ -1551,7 +1551,7 @@
 		<a href="#ldpr-gen-pubclireqs">must be advertised</a> to clients.
 	</p>
 		
-	<section id="ldpc-post-created201"><h2 class="normal">LDPC clients SHOULD create member resources by submitting a representation as
+	<section id="ldpc-post-created201"><h2 class="normal">LDP clients SHOULD create member resources by submitting a representation as
 		the entity body of the HTTP <code>POST</code> to a known LDPC. If the resource was created successfully, <a title="LDP server">LDP servers</a> MUST
 		respond with status code 201 (Created) and the <code>Location</code>
 		header set to the new resource’s URL. Clients shall not expect any representation in the response
@@ -1579,14 +1579,17 @@
 	</h2><!-- Was 5.4.4 / #ldpc-5_4_4 -->
 	<ul>
 	<li>If the request header specifies <a href="#ldpr-gen-linktypehdr">a LDPR interaction model</a>, then the server MUST handle subsequent 
-	requests to the newly created resource's URI as if it is a LDPR.
+	requests to the newly created resource's URI as if it is a LDPR
 	(even if the content contains an <code>rdf:type</code> triple indicating a type of LDPC).</li>
 	<li>If the request header specifies <a href="#ldpc-linktypehdr">a LDPC interaction model</a>, then the server MUST handle subsequent 
 	requests to the newly created resource's URI as if it is a LDPC.
 	</li>
 	<li>This specification does not constrain the server's behavior in other cases.</li>
 	</ul>
-	<p>Note: A consequence of this is that LDPCs can be used to create LDPCs, if the server supports doing so.</p>
+	<p>Clients use the same syntax, that is <code>HTTP Link</code> headers, to specify the desired interaction model
+		when creating a resource as servers use to advertise it on responses.
+	</p>
+	<p>Note: A consequence of <a href="#ldpc-post-createrdf">this</a> is that LDPCs can be used to create LDPCs, if the server supports doing so.</p>
 	</section>
 	
 	<section id="ldpc-post-turtle"><h2 class="normal"><a title="LDP server">LDP servers</a> MUST accept a request entity body with a request header
@@ -2573,6 +2576,7 @@
 
 <blockquote><em><a href="http://www.w3.org/TR/2014/CR-ldp-20140619">Candidate Recommendation Draft</a></em></blockquote> -->
 <ul>
+	<li>2014-07-28 - Clarified syntax used by clients to request specific interaction model (JA) </li>
 	<li>2014-06-16 - Updated examples in Prefer section to be in request/response format (SS) </li>
 	<li>2014-06-16 - Updated examples in container sections to be in request/response format (SS) </li>
 	<li>2014-06-10 - Use http-bis and Prefer RFC numbers, adjust BNF to match bis changes (JA) </li>