--- a/rdf-turtle/n-triples.html	Sun Dec 22 23:00:01 2013 +0100
+++ b/rdf-turtle/n-triples.html	Sun Dec 22 23:11:41 2013 +0100
@@ -21,7 +21,7 @@
           subtitle   :  "A line-based syntax for an RDF graph",
 
           // if you wish the publication date to be other than today, set this
-          publishDate:  "2014-01-07",
+          publishDate:  "2014-01-09",
 
           // if the specification's copyright date is a range of years, specify
           // the start date here:
@@ -39,7 +39,7 @@
           lcEnd: "2013-10-14",
 
           crEnd: "2013-11-26",
-          prEnd: "2014-02-04",
+          prEnd: "2014-02-09",
 
           // editors, add as many as you like
           // only "name" is required
@@ -111,7 +111,7 @@
         <h2>Introduction</h2>
         <p>
           This document defines N-Triples, a concrete syntax for 
-          <a href="http://www.w3.org/TR/rdf11-concepts/">RDF</a> [[!RDF11-CONCEPTS]].
+          RDF [[!RDF11-CONCEPTS]].
           N-Triples is an easy to parse line-based subset of
           Turtle [[!TURTLE]].
         </p>
@@ -390,8 +390,8 @@
           <dd>N-Triples is used to express arbitrary application data; security considerations will vary by domain of use. Security tools and protocols applicable to text (e.g. PGP encryption, MD5 sum validation, password-protected compression) may also be used on N-Triples documents. Security/privacy protocols must be imposed which reflect the sensitivity of the embedded information.</dd>
           <dd>N-Triples can express data which is presented to the user, for example, RDF Schema labels. Application rendering strings retrieved from untrusted N-Triples documents must ensure that malignant strings may not be used to mislead the reader. The security considerations in the media type registration for XML ([[!RFC3023]] section 10) provide additional guidance around the expression of arbitrary data and markup.</dd>
           <dd>N-Triples uses IRIs as term identifiers. Applications interpreting data expressed in N-Triples should address the security issues of
-      <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource Identifiers (IRIs)</a> [[!RFC3987]] Section 8, as well as
-      <a class="norm" href="http://www.ietf.org/rfc/rfc3986.txt">Uniform Resource Identifier (URI): Generic Syntax</a> [[!RFC3986]] Section 7.</dd>
+      <em>Internationalized Resource Identifiers (IRIs)</em> [[!RFC3987]] Section 8, as well as
+      <em>Uniform Resource Identifier (URI): Generic Syntax</em> [[!RFC3986]] Section 7.</dd>
 
           <dd>Multiple IRIs may have the same appearance. Characters in different scripts may
     look similar (a Cyrillic &quot;&#1086;&quot; may appear similar to a Latin &quot;o&quot;). A character followed
@@ -401,10 +401,8 @@
     <!-- (<code>foo:resum&#40751;code> and <code>f&#1086;&#1086;:resume&#769;</code>)-->
     Any person or application that is writing or interpreting data in Turtle must take care to use the IRI that matches the intended semantics, and avoid IRIs that make look similar.
     Further information about matching of similar characters can be found
-    in <a class="inform" href="http://www.unicode.org/reports/tr36/">Unicode Security
-    Considerations</a> [[UNICODE-SECURITY]] and
-    <a class="norm" href="http://www.ietf.org/rfc/rfc3987.txt">Internationalized Resource
-    Identifiers (IRIs)</a> [[RFC3987]] Section 8.
+    in <em>Unicode Security Considerations</em> [[UNICODE-SECURITY]] and
+    <em>Internationalized Resource Identifiers (IRIs)</em> [[RFC3987]] Section 8.
       </dd>
 
           <dt>Interoperability considerations:</dt>