--- a/spec/tls-respec.html	Wed Oct 16 19:16:29 2013 +0200
+++ b/spec/tls-respec.html	Wed Oct 16 19:19:56 2013 +0200
@@ -985,7 +985,7 @@
    To avoid potential deadlock problems, where one server needs to authenticate into a second server that itself requires authentication, etc... , <tref>WebID Profile</tref>'s MUST be public. 
  It follows that WebID Authenticating servers MUST not authenticate when fetching a <tref>WebID Profile</tref>.
    </p>
-   <p>Even though a <tref>WebID Profile</tref> document MUST be publicly accessible, the <tref>WebID Profile</tref> can be split among multiple resources that are linked and protected by <a href="http://www.w3.org/wiki/WebAccessControl">access control rules</a> (as explained in the privacy section of the WebID specification [[!WebID]]), in order to provide limited access to sensitive information.
+   <p>Even though a <tref>WebID Profile</tref> document MUST be publicly accessible, the <tref>WebID Profile</tref> can be split among multiple resources that are linked and protected by <a href="http://www.w3.org/wiki/WebAccessControl">access control rules</a> (as explained in the privacy section of the WebID specification [[!WEBID]]), in order to provide limited access to sensitive information.
    </p>
    <p>
    As a consequence of dereferencing the <tref>WebID Profile</tref> during authentication, identity providers such as the server hosting the profile document are able to track the IP addresses of incoming requests for the user's profile document, and potentially match them to a list of known servers and services.