--- a/spec/identity-respec.html	Fri Apr 19 15:23:45 2013 +0200
+++ b/spec/identity-respec.html	Fri Apr 19 16:40:25 2013 +0200
@@ -539,7 +539,7 @@
 
 <section class="informative">
 <h1>Privacy</h1>
-<p>A WebID Profile document does not need to contain only public resources. A possible way of protecting its contents can be achieved by separating parts of the profile information into separate documents, each protected by access control policies. In the following example, Bob is limiting access to his list of friends, by placing all foaf:knows relations into a separate document.</p>
+<p>A WebID Profile document need not contain only public resources. A possible way of protecting its contents can be achieved by separating parts of the profile information into separate documents, each protected by access control policies. In the following example, Bob is limiting access to his list of friends, by placing all foaf:knows relations into a separate document.</p>
 
 <pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
  @prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
@@ -596,7 +596,9 @@
 The Agent requesting the WebID document MUST be able to parse documents in Turtle [[!TURTLE-TR]], but MAY also be able to parse documents in RDF/XML [[!RDF-SYNTAX-GRAMMAR]] and RDFa [[!RDFA-CORE]].
 The result of this processing should be a graph of RDF relations that is queryable, as explained in the next section.</p>
 <p class="note">
-It is important that the <tref>Requesting Agent</tref> should set the Accept-Header to request <code>text/turtle</code> with a higher priority than <code>application/xhtml+xml</code>(RDFa) and <code>application/rdf+xml</code> (RDF/XML). The reason is that it is quite likely that many sites will produce non marked up HTML and leave the graph in pure RDF formats.
+It is recommended that the <tref>Requesting Agent</tref>  set the HTTP <code>Accept-Header</code>'s  <code>text/turtle</code> qvalue with a higher priority than <code>application/xhtml+xml</code> or <code>text/html</code>, as sites may produce HTML without RDFa markup but with a link to graph encoded in a pure RDF format such as Turtle. 
+For example, an agent that can parse rdf/xml, Turtle and RDFa the following would be a reasonable Accept header:<br/>
+<code>Accept: application/rdf+xml,text/turtle,application/xhtml+xml;q=0.8,text/html;q=0.7</code>
 </p>
 <p>If the <tref>Requesting Agent</tref> wishes to have the most up-to-date Profile document for an HTTPS URL, it can use the HTTP cache control headers to get the latest versions.</p>
 </section>