--- a/trig/index.html	Fri Apr 05 19:10:44 2013 +0200
+++ b/trig/index.html	Fri Apr 05 20:37:19 2013 +0200
@@ -61,7 +61,8 @@
 	  // editors, add as many as you like
 	  // only "name" is required
 	  editors:  [
-	      { name: "Gavin Carothers", url: "http://gavin.carothers.name/",
+	      { name: "Gavin Carothers",
+                        // link error, pls correct: url: "http://gavin.carothers.name/",
 			company: "Lex Machina", companyURL: "https://lexmachina.com/" },
 	  ],
 
@@ -70,7 +71,8 @@
 	  // only "name" is required. Same format as editors.
 
 	  authors:  [
-	      { name: "Chris Bizer", url: "http://www.bizer.de", 
+	      { name: "Chris Bizer",
+                // link error, pls correct: url: "http://www.bizer.de", 
 	      	company: "Freie Universität Berlin", companyURL: "http://www.fu-berlin.de/" },
   	      { name: "Richard Cyganiak", url: "http://richard.cyganiak.de", 
   	      	company: "Freie Universität Berlin", companyURL: "http://www.fu-berlin.de/" },
@@ -122,8 +124,8 @@
 		<section id="sec-intro">
 			<h2>Introduction</h2>
 			<p>This document defines TriG a concrete syntax for RDF as defined in the
-			<a href="../rdf-concepts/index.html">RDF Concepts and Abstract Syntax</a> 
-			([[!RDF11-CONCEPTS]]) W3C Recommendation. TriG is an extension of 
+			RDF Concepts and Abstract Syntax
+			([[!RDF11-CONCEPTS]]). TriG is an extension of 
 			Turtle ([[!TURTLE-TR]]), extended 
 			to support representing a complete RDF Dataset.
 		</section>
@@ -205,7 +207,7 @@
 				<h3>Other Terms</h3>
 				<p>All other terms and directives come from Turtle.</p>
 				<section id="terms-blanks-nodes">
-					<h4>Special Considerations for Blank Nodes</h4>
+					<h4>Sal Considerations for Blank Nodes</h4>
 					<p>BlankNodes sharing the same label in differently labeled graph statements MUST be considered to be the same BlankNode.</p>
 				</section>
 			</section>
@@ -260,9 +262,9 @@
           <section id="sec-iri-references">
           	<h3>IRI References</h3>
   					<p>
-					  Relative IRIs are resolved with base IRIs as per <a href="http://www.ietf.org/rfc/rfc3986.txt" class="norm">Uniform Resource Identifier (URI): Generic Syntax</a> [<a href="#rfc3986">RFC3986</a>] using only the basic algorithm in section 5.2.
+					  Relative IRIs are resolved with base IRIs as per <a href="http://www.ietf.org/rfc/rfc3986.txt" class="norm">Uniform Resource Identifier (URI): Generic Syntax</a> [[!RFC3986]] using only the basic algorithm in section 5.2.
 					  Neither Syntax-Based Normalization nor Scheme-Based Normalization (described in sections 6.2.2 and 6.2.3 of RFC3986) are performed.
-					  Characters additionally allowed in IRI references are treated in the same way that unreserved characters are treated in URI references, per section 6.5 of <a href="http://www.ietf.org/rfc/rfc3987.txt" class="norm">Internationalized Resource Identifiers (IRIs)</a> [<a href="#rfc3987">RFC3987</a>].
+					  Characters additionally allowed in IRI references are treated in the same way that unreserved characters are treated in URI references, per section 6.5 of <a href="http://www.ietf.org/rfc/rfc3987.txt" class="norm">Internationalized Resource Identifiers (IRIs)</a> [[!RFC3987]].
 					</p>
 					<p>
 					  The <code>@base</code> directive defines the Base IRI used to resolve relative IRIs per RFC3986 section 5.1.1, "Base URI Embedded in Content".