--- a/ldp-primer/ldp-primer.html	Sun Jun 15 11:30:12 2014 +0200
+++ b/ldp-primer/ldp-primer.html	Mon Jun 16 10:43:42 2014 +0200
@@ -451,7 +451,9 @@
 
       <pre title="Response - basic container retrieval" class='example' data-include='getbc_res.txt' data-oninclude='fixCode'></pre> 
       
-      <p> As shown in the example, in addition to the RDF representation of the Basic Container using the requested media type the server provides an E-tag of the resource representation and Link headers advertising that the requested resource is indeed an LDP Basic Container and it will support the LDP interaction model. </p>
+      <p> As shown in the example, in addition to the RDF representation of the Basic Container using the requested media type the server provides an etag of the resource representation and Link headers advertising that the requested resource is indeed an LDP Basic Container and it will support the LDP interaction model. </p>
+      
+		<p> In addition, the response also contains "Allow" header which advertises which HTTP operations are supported by this LDP Basic Container resource. In this example, it supports OPTIONS,HEAD,GET,POST,PUT,PATCH HTTP verbs.</p>      
       
       <p class="note">The Linked Data Platform 1.0 specification [[LDP]] says that all LDP servers MUST support the Turtle media type for LDP-RS resources and SHOULD support JSON-LD media type.</p>
 
@@ -461,7 +463,7 @@
       <h2> Discovering the affordances (OPTIONS on an LDP-BC) </h2>
 
       <p>
-        Now, Alice wants to know what she can do in her document space. She can use the OPTIONS operation to learn of the permitted operations LDP-BC that she retrieved in the previous example.
+		 In the previous example, we saw that Alice can discover what operations are allowed on a resource by doing a GET request on the resource. As an alternative, she can use the OPTIONS operation to learn of the permitted operations on any given resource.
       </p>
 
       <pre title="Request - retreiving OPTIONS of a basic container" class='example'>
@@ -488,6 +490,11 @@
 
       <p>
         Alice can upload a social profile document to her store, by POSTing her FOAF personal profile document to her LDP-BC at the root of her document store. Note, the Slug header offers the server a hint about URL of the resource to be created.  
+      </p>
+      
+      <p> The FOAF document includes statements about the resource to be created and other resources relative to the resource to be created. According the LDP specification
+      Alice can use null relative URI (<>) in the request entity body to refer to resource to be created.
+      
       </p>
 
       <pre title="Request - creating a RDF resource" class='example' data-include='bccreate.txt' data-oninclude='fixCode'></pre> 
@@ -500,7 +507,7 @@
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel=&#39;type&#39;
 Content-Length: 0 
    </pre>
-      <p> The response to the create request provides a Link to the newly created resource using the Location header. In this case, the server has honored the hint provided by the Slug header and created the new resource in the URL http://example.org </p>
+      <p> The response to the create request provides a Link to the newly created resource using the Location header. In this case, the server has honored the hint provided by the slug header and created the new resource in the URL http://example.org/alice/foaf. </p>
       <p>Knowing the URL of the newly created resource, Alice can check the container again to confirm that the container correctly contains the newly created resource.</p>
 
       <pre title="Request - basic container retrieval after resource created" class="example">
@@ -773,6 +780,8 @@
     <section>
       <h3 id="BugCreate">Creation (POST a resource to an LDP-DC)</h3>
       <p>Continuing from the previous example, we can report a Bug against the "LDP Demo" product by creating a Bug report (an LDPR representing the bug) under the "LDP Demo" product description LDPC by posting a RDF representation of the Bug report to the LDPC associated with the product description.  </p>
+
+      <p> The bug report document includes statements about the resource to be created. According the LDP specification, a client can use null relative URI (<>) in the request entity body to refer to resource to be created.
 
       <pre title="A request for creating a bug" class='example' data-include='bug_create_req.txt' data-oninclude='fixCode'></pre> 
       <p>If the creation is successful, the server responds with location of the newly created resource.</p>
@@ -913,7 +922,8 @@
     <h1>Change History</h1>
     <p>The change history is up to the editors to insert a brief summary of changes, ordered by most recent changes first and with heading from which public draft it has been changed from.
     </p>
-    <ul>
+    <ul>
+      <li>2014-06-16 - Addressing the comments and feedback provided by Ashok, John, and Henry.</li>
       <li>2013-08-05 - Providing JSON-LD representations of the examples.</li>
       <li>2013-07-03 - Moving the content from the wiki to the note.</li>
     </ul>