--- a/rdf-primer/index.html	Wed Mar 12 21:54:17 2014 +0000
+++ b/rdf-primer/index.html	Wed Jun 04 14:43:35 2014 +0100
@@ -11,7 +11,7 @@
           localBiblio: localBibliography,
 
           // specification status (e.g. WD, LC, WG-NOTE, etc.). If in doubt use ED.
-          specStatus:           "ED",
+          specStatus:           "WG-NOTE",
           errata:               "http://www.w3.org/2014/rdf1.1-errata",
           // noRecTrack:           true,
 
@@ -103,7 +103,7 @@
           // from the dcterms, foaf, and bibo. The parameter defaults to false.
           doRDFa: "1.1",
 
-          // alternateFormats: [ { uri: "diff-20130723.html", label: "diff to previous version" } ]
+          /alternateFormats: [ { uri: "http://www.asahi-net.or.jp/~ax2s-kmtn/internet/rdf/NOTE-rdf11-primer-20140225.html", label: "Japanese translation" } ]
       };
     </script>
     <style type="text/css">
@@ -589,7 +589,7 @@
 </table>
 
 <p class="note">The syntactic form (second column) is in a prefix
-notation wich is discussed in more detail in 
+notation which is discussed in more detail in 
 <a href="#section-graph-syntax">Sec.&nbsp;5</a>.
 The fact that the constructs have two different prefixes
 (<code>rdf:</code> and <code>rdfs:</code>) is a somewhat annoying
@@ -689,8 +689,9 @@
 which are closely related. We start with N-Triples, as it provides
 basic syntax for writing down RDF triples. The Turtle syntax
 extends this basic syntax with various forms of syntactic sugar to improve
-readability. Subsequently we discuss TriG and N-Quads, which are extensions of Turtle
-respectively N-Triples to encode multiple graphs. Together, these four are
+readability. Subsequently we discuss TriG and N-Quads, which are
+extensions respectively of Turtle and
+N-Triples to encode multiple graphs. Together, these four are
 referred to as the "Turtle family of RDF languages".
 
 <section id="section-n-triples">
@@ -788,7 +789,7 @@
 writing down IRIs. Relative IRIs (such as <code>bob#me</code> on line 8) are 
 resolved against a base IRI, specified here in line 1.
 Lines 2-6 define IRI prefixes (such as <code>foaf:</code>), which  can
-be use for prefixed names (such as <code>foaf:Person</code>) instead of full IRIs.
+be used for prefixed names (such as <code>foaf:Person</code>) instead of full IRIs.
 The corresponding IRI is constructed by replacing the prefix with its
 corresponding IRI (in this example <code>foaf:Person</code> stands for
 <code>&lt;http://xmlns.com/foaf/0.1/Person&gt;</code>).</p>
@@ -1050,7 +1051,7 @@
       a schema.org property IRI and specify that its value can
       be mapped to an <code>xsd:date</code> datatype. </p>
 
-      <p>From line 16 to line 23 we describe how to map
+      <p>From line 14 to line 23 we describe how to map
       <code>title</code>, <code>creator</code> and <code>subject_of</code>
       to Dublin Core property IRIs. The <code>@reverse</code>
       keyword on line 21 is used to specify that, whenever we