--- a/spec/index-respec.html	Wed Oct 24 02:26:01 2012 -0400
+++ b/spec/index-respec.html	Wed Oct 24 02:28:56 2012 -0400
@@ -289,7 +289,7 @@
 
 <p>A global distributed Social Web requires that each person be able to control their identity, that this identity be linkable across sites -  placing each person in a Web of relationships - and that it be possible to authenticate globally with such identities. By making distributed authentication easy one can allow everybody to protect their resources and enable their preferred privacy settings.</p>
 <p>This specification outlines a simple universal identification mechanism that is distributed, openly extensible, improves privacy, security and control over how each person can identify themselves in order to allow fine grained  access control to their information on the Web.
-It does this by applying the best practices of Web Architecture whilst building on well established widely deployed protocols and standards including HTML, XHTML, URIs, HTTP, TLS, X.509 Certificates, and RDF Semantics.
+It does this by applying the best practices of Web Architecture whilst building on well established widely deployed protocols and standards including HTML, URIs, HTTP, TLS, X.509 Certificates, and RDF Semantics.
 </p>
 
 <section>
@@ -467,10 +467,10 @@
 <dd>
 A structured document asserting the relationship between the Subject (identified by his WebID) and his <tref>Public Key</tref>s using relationships as defined by the Resource Description Framework [[RDF-CONCEPTS]] and published at the URL location of the Subject's WebID. 
 Dereferencing the <tref>WebID</tref> should return the Profile Page in one of a number of formats. 
-The Server MUST publish the document in at least the XHTML+RDFa [[!RDFA-CORE]] serialization format or in Turtle [[!TURTLE-TR]].
+The Server MUST publish the document in at least the RDFa [[!RDFA-CORE]] serialization format or in Turtle [[!TURTLE-TR]].
 The document may be published in a number of other RDF serialization formats, such as RDF/XML [[!RDF-PRIMER]], or N3 [[!N3]].
 Any other serializations that intend to be used by the WebID Protocol MUST be transformable automatically and in a standard manner to an RDF Graph, using technologies such as GRDDL [[!GRDDL-PRIMER]].
-<p class="issue">Most profiles are currently written out in either of those formats. Whether or not XHTML+RDFa 1.1, both either serialization of RDF should be required serialization formats in the specification is currently under heavy debate and is open to change. </p>
+<p class="issue">Most profiles are currently written out in either of those formats. Whether or not RDFa 1.1, both either serialization of RDF should be required serialization formats in the specification is currently under heavy debate and is open to change. </p>
 </dd>
 
 </dl>
@@ -636,8 +636,8 @@
 ...
 &lt;/head&gt; ...
 </pre>
-<p>It is particularly useful to have one of the representations be in HTML or
-XHTML even if it is not marked up in RDFa as this allows people using a
+<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
 web browser to understand what the information at that URI represents.</p>
 <section class='normative'>
 <h2>WebID Profile Vocabulary</h2>
@@ -718,8 +718,8 @@
 </pre>
 </section>
 <section>
-<h1>RDFa XHTML notation</h1>
-<p>RDFa in XHTML [[!RDFA-CORE]] is a way to markup XHTML with relations that have a well defined semantics and
+<h1>RDFa HTML notation</h1>
+<p>RDFa in HTML [[!RDFA-CORE]] is a way to markup HTML with relations that have a well defined semantics and
     mapping to an RDF graph.  There are many ways of writing out the above graph using RDFa in
 HTML. Here is just one example of what a WebID profile could look like.
     It would have to be served with the mime type <code>application/xhtml+xml</code>.