--- a/nquads/index.html	Wed Oct 16 09:19:04 2013 -0700
+++ b/nquads/index.html	Wed Oct 16 09:22:54 2013 -0700
@@ -94,7 +94,7 @@
 </section>
 
       <section id='sotd'>
-<p>The N-Quads format has a similar flavour as N-Triples
+<p>The N-Quads format has a similar flavor as N-Triples
 [[n-triples]]. The main distinction is that N-Quads allows encoding
 multiple graphs. In a change from previous publication, this document is intended to become a W3C Recommendation.</p>  
       </section>
@@ -102,7 +102,7 @@
       <section id="sec-intro">
         <h2>Introduction</h2>
         <p>This document defines an easy to parse line-based language named N-Quads.</p>
-    <p>N-quads statments are a sequence of RDF terms representing the subject, predicate, object and graph label of an RDF Triple and the graph it is part of in a dataset. These may be separated by white space (spaces <code>#x20</code> or tabs <code>#x9</code>). This sequence is terminated by a '<code>.</code>' and a new line (optional at the end of a document).
+    <p>N-quads statements are a sequence of RDF terms representing the subject, predicate, object and graph label of an RDF Triple and the graph it is part of in a dataset. These may be separated by white space (spaces <code>#x20</code> or tabs <code>#x9</code>). This sequence is terminated by a '<code>.</code>' and a new line (optional at the end of a document).
     </p>
 
       <pre class="example"><script type="application/n-quads"><http://one.example/subject1> <http://one.example/predicate1> <http://one.example/object1> <http://example.org/graph3> . # comments here
@@ -193,7 +193,7 @@
         <section id="sec-grammar">
           <h3>Grammar</h3>
           <p>A N-Quads document is a Unicode[[!UNICODE]] character string encoded in UTF-8.
-          Unicode codepoints only in the range U+0 to U+10FFFF inclusive are allowed.</p>
+          Unicode code points only in the range U+0 to U+10FFFF inclusive are allowed.</p>
           <p>White space (tab <code>U+0009</code> or space <code>U+0020</code>) is used to separate two terminals which would otherwise be (mis-)recognized as one terminal. White space is significant in the production <a href="#grammar-production-STRING_LITERAL_QUOTE">STRING_LITERAL_QUOTE</a>.</p>
           <p>Comments in N-Quads take the form of '<code>#</code>', outside an <code>IRIREF</code> or <code>STRING_LITERAL_QUOTE</code>, and continue to the end of line (<code>EOL</code>) or end of file if there is no end of line after the comment marker. Comments are treated as white space.</p>
           <p>The <abbr title="Extended Backus–Naur Form">EBNF</abbr> used here is defined in XML 1.0
@@ -242,7 +242,9 @@
 
       <section id="sec-changes" class="appendix">
         <h2>Changes to this document<h2>
-        <h3>Changes since last publication as Note</h3>
+        <h3>Changes since last publication as Last Call Working Draft</h3>
+        <p>No substitutive changes.</p>
+        <h3>Changes since original publication as Note</h3>
         <ul>
           <li>White space rules defined outside of grammar, as in Turtle.
           <li>Comment processing defined.