--- a/spec/index-respec.html	Wed Oct 24 02:21:43 2012 -0400
+++ b/spec/index-respec.html	Wed Oct 24 02:26:01 2012 -0400
@@ -467,7 +467,7 @@
 <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 [[!XHTML-RDFA]] serialization format or in Turtle [[!TURTLE-TR]].
+The Server MUST publish the document in at least the XHTML+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>
@@ -621,7 +621,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="note">
-For reasons of interoperability, in order not to overburden the implementation and testing work of <tref>WebID Verifier</tref>s, and in order to provide a seamless experience for end users, of the many formats that can be publish at one location, it is established that at present publishers  SHOULD  publish their documents in at least one of RDFa [[!XHTML-RDFA]] or [[!TURTLE-TR]] as these MUST be understood by <tref>Verification Agent</tref>s.
+For reasons of interoperability, in order not to overburden the implementation and testing work of <tref>WebID Verifier</tref>s, and in order to provide a seamless experience for end users, of the many formats that can be publish at one location, it is established that at present publishers  SHOULD  publish their documents in at least one of RDFa [[!RDFA-CORE]] or [[!TURTLE-TR]] as these MUST be understood by <tref>Verification Agent</tref>s.
 If other formats grow in popularity, are implemented by verifiers, and gain community acceptance, these can be added to the list.
 </p>
 <p>