--- a/spec/identity-respec.html Tue Nov 20 18:44:11 2012 -0500
+++ b/spec/identity-respec.html Wed Nov 21 08:42:46 2012 -0500
@@ -349,9 +349,9 @@
<h1>Introduction</h1>
<p>
-A WebID is an HTTP URI containing a URI fragment identifier (i.e. a # symbol) and which uniquely denotes an Agent (Person, Organisation, Group, Device, etc.). The URI without the fragment identifier denotes the WebID <tref>Profile Page</tref> document.</p>
+A WebID is an HTTP URI containing a URI fragment identifier (i.e. a # symbol) and which uniquely denotes an Agent (Person, Organization, Group, Device, etc.). The URI without the fragment identifier denotes the WebID <tref>Profile Page</tref> document.</p>
<p>
-A WebID Profile is a Web resource that MUST be available as Turtle [[!TURTLE-TR]], but MAY be available in other RDF serialisation formats (e.g. [[!RDFA-CORE]]) if so requested through content negotiation.
+A WebID Profile is a Web resource that MUST be available as Turtle [[!TURTLE-TR]], but MAY be available in other RDF serialization formats (e.g. [[!RDFA-CORE]]) if so requested through content negotiation.
</p>
<p>
WebIDs can be used to build a Web of trust using vocabularies such as FOAF [[!FOAF]] by allowing people to link together their profiles in a public or protected manner.
@@ -383,12 +383,12 @@
<dd>A Service is a an agent listening for requests at a given IP address on a given Server.</dd>
<dt><tdef>WebID</tdef></dt>
-<dd>A WebID is a URI with an HTTP or HTTPS scheme, containing a URI fragment identifier (i.e. a # symbol) and which uniquely denotes an Agent (Person, Organisation, Group, Device, etc.). The URI without the fragment identifier denotes the WebID <tref>Profile page</tref>.
+<dd>A WebID is a URI with an HTTP or HTTPS scheme, containing a URI fragment identifier (i.e. a # symbol) and which uniquely denotes an Agent (Person, Organization, Group, Device, etc.). The URI without the fragment identifier denotes the WebID <tref>Profile page</tref>.
</dd>
<dt><tdef>WebID Profile</tdef> or <tdef>Profile Page</tdef></dt>
<dd>
-A WebID Profile is an RDF document that MUST be available as Turtle [[!TURTLE-TR]]. The document MAY be available in other RDF serialisation formats, such as RDFa [[!RDFA-CORE]], RDF/XML [[!RDF-PRIMER]], or N3 [[!N3]] if so requested through content negotiation.
+A WebID Profile is an RDF document that MUST be available as Turtle [[!TURTLE-TR]]. The document MAY be available in other RDF serialization formats, such as RDFa [[!RDFA-CORE]], RDF/XML [[!RDF-PRIMER]], or N3 [[!N3]] if so requested through content negotiation.
Any other serializations that intend to be used by WebID MUST be transformable automatically and in a standard manner to an RDF Graph, using technologies such as GRDDL [[!GRDDL-PRIMER]].
</dd>
@@ -434,7 +434,7 @@
<p>The WebID URI - <em>http://www.w3.org/People/Berners-Lee/card<strong>#i</strong></em> - is an abstract representation which provides a reference to a person or to an agent.
<p>The WebID Profile URI - <em>http://www.w3.org/People/Berners-Lee/card</em> - denotes the document describing the person or agent to which the WebID URI refers.
-The document can publish many more relations than are of interest to the WebID profile, as shown in the above graph.
+The document can publish many more relations that are of interest to the WebID profile, as shown in the above graph.
For example a user can publish a depiction or logo, so that sites he authenticates to can personalize the user experience. He can post links to people he knows, who in turn have WebIDs published on other sites, in order to create a distributed Social Web.
He can also publish one or more relations to different authentication protocols. More information on WebID and other authentication protocols can be found on the <a href="http://www.w3.org/2005/Incubator/webid/wiki/Identity_Interoperability">WebID Identity Interoperability</a> page.
</p>
@@ -448,7 +448,7 @@
Technologies such as GRDDL [[!GRDDL-PRIMER]] for example permit any XML format to be transformed automatically to a graph of relations.
HTTP Content Negotiation can be employed to aid in publication and discovery of multiple distinct serializations of the same graph at the same URL, as explained by the working group note <a href="http://www.w3.org/TR/2008/NOTE-swbp-vocab-pub-20080828/">Best Practice Recipes for Publishing RDF Vocabularies</a> [[!SWBP-VOCAB-PUB]]</p>
-<p class="issue">HTTP 303 redirects should be avoided (needs further discussion). Since WebIDs contain a URI fragment identifier, there is no longer necessary to use HTTP 303 redirects in order to make the difference between the identifier and the document it points to; the relationship becomes obvious.</p>
+<p class="issue">HTTP 303 redirects should be avoided (needs further discussion). Since WebIDs contain a URI fragment identifier, it is no longer necessary to use HTTP 303 redirects in order to make the difference between the identifier and the document it points to; the relationship becomes obvious.</p>
<p>It is particularly useful to have one of the representations be in HTML
even if it is not marked up in RDFa as this allows people using a