--- a/spec/identity-respec.html	Tue Nov 20 16:32:19 2012 -0500
+++ b/spec/identity-respec.html	Tue Nov 20 18:44:11 2012 -0500
@@ -487,11 +487,13 @@
     The syntax is very similar to the <a href="http://www.w3.org/TR/rdf-sparql-query/">SPARQL</a> query language.
     Turtle profile documents should be served with the <code>text/turtle</code> content type.
 </p>
+<p>    
+Please take for example the WebID <em>https://bob.example/profile#me</em>, for which the WebID Profile document contains the following Turtle representation:
+</p>
 <pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
- @prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt; .
  @prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
 
- &lt;https://bob.example/profile#me&gt; rdf:type foaf:Person;
+ &lt;#me&gt; a foaf:Person;
    foaf:name "Bob";
    foaf:knows &lt;https://example.edu/p/Alice#MSc&gt;;
    foaf:weblog &lt;http://bob.example/blog&gt;.
@@ -530,27 +532,25 @@
 </section>
 
 <section class="informative">
-<h1>Protecting parts of a WebID Profile</h1>
-<p>A WebID Profile document does not need to be a public resource. 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>
+<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>
 
 <pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
- @prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt; .
  @prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
- @prefix s: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
+ @prefix rdfs: &lt;http://www.w3.org/2000/01/rdf-schema#&gt; .
  
- &lt;https://bob.example/profile#me&gt; rdf:type foaf:Person;
+ &lt;#me&gt; a foaf:Person;
    foaf:name "Bob";
-   <strong>s:seeAlso &lt;https://bob.example/friends&gt;;</strong>
+   <strong>rdfs:seeAlso &lt;https://bob.example/friends&gt;;</strong>
    foaf:weblog &lt;http://bob.example/blog&gt;.
 </pre>
 
 <p>Where https://bob.example/friends is a reference to an ACL protected document containing:</p>
 
 <pre class="example" style="word-wrap: break-word; white-space: pre-wrap;">
- @prefix rdf: &lt;http://www.w3.org/1999/02/22-rdf-syntax-ns#&gt; .
  @prefix foaf: &lt;http://xmlns.com/foaf/0.1/&gt; .
  
- &lt;https://bob.example/profile#me&gt; rdf:type foaf:Person;
+ &lt;https://bob.example/profile#me&gt; a foaf:Person;
    foaf:knows &lt;https://example.edu/p/Alice#MSc&gt;;
    foaf:knows &lt;https://example.com/people/Mary/card#me&gt;.
 </pre>
@@ -570,7 +570,7 @@
 </section>
 
 <section class='normative'>
-<h2>Processing the WebID Profile</h2>
+<h2>Processing the WebID Profile</h2>not valid Turtle.
 
 <p>The <tref>Requesting Agent</tref> needs to fetch the document, if it does not have a valid one in cache.  
 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]].