--- a/ldp-primer/ldp-primer.html	Mon Apr 20 20:40:09 2015 +0200
+++ b/ldp-primer/ldp-primer.html	Mon May 11 15:43:28 2015 +0200
@@ -110,7 +110,7 @@
   <script class='remove'>
     var respecConfig = {
       // specification status (e.g. WD, LCWD, NOTE, etc.). If in doubt use ED.
-      specStatus: "WG-NOTE",
+      specStatus: "WD",
 
       // This is NOT a Rec Track document
       noRecTrack: "true",
@@ -124,7 +124,7 @@
       // subtitle   :  "an excellent document",
 
       // if you wish the publication date to be other than today, set this
-      publishDate:  "2015-04-21",
+      //publishDate:  "2015-04-21",
 
       // if the specification's copyright date is a range of years, specify
       // the start date here:
@@ -132,9 +132,9 @@
 
       // if there is a previously published draft, uncomment this and set its YYYY-MM-DD date
       // and its maturity status
-      previousPublishDate:  "2014-06-26",
-      previousMaturity:   "FPWD",
-      previousURI:      "http://www.w3.org/TR/2014/WD-ldp-primer-20140626/",
+      previousPublishDate:  "2015-04-23",
+      previousMaturity:   "NOTE",
+      previousURI:      "http://www.w3.org/TR/2015/NOTE-ldp-primer-20150423/",
 
       // if there a publicly available Editor's Draft, this is the link
       edDraftURI: "http://www.w3.org/2012/ldp/hg/ldp-primer/ldp-primer.html",
@@ -305,7 +305,7 @@
     <h2>LDP concepts in a glance</h2>
 
     <p>
-      A server hosting Linked Data Platform Resources (LDPRs) may manage two kinds of LDPRs: those resources whose state is represented using RDF (called LDP RDF Sources (LDP-RSs)), and those using other formats (called LDP Non-RDF Sources (LDP-NRs)) such as HTML files, images, other binary files, etc. Resoures respond to retrieval operations using HTTP GET. Often a description conveyed in the response document will describe a specific domain entity; Status, Friendship, Product, Order, Bug, etc. On the other hand, it might contain a description of a number of different concepts. The links contained in the descriptions lead to the subsequent discovery and processing of other resources. Affordances offered by the server make discoverable the forward paths in the application. Together the resources, links and associated affordances together specify what might be termed the API. 
+      A server hosting Linked Data Platform Resources (LDPRs) may manage two kinds of LDPRs: those resources whose state is represented using RDF (called LDP RDF Sources (LDP-RSs)), and those using other formats (called LDP Non-RDF Sources (LDP-NRs)) such as HTML files, images, other binary files, etc. Resources respond to retrieval operations using HTTP GET. Often a description conveyed in the response document will describe a specific domain entity; Status, Friendship, Product, Order, Bug, etc. On the other hand, it might contain a description of a number of different concepts. The links contained in the descriptions lead to the subsequent discovery and processing of other resources. Affordances offered by the server make discoverable the forward paths in the application. Together the resources, links and associated affordances together specify what might be termed the API. 
     </p>
 	<blockquote>
     <p>Types of LDPRs:
@@ -326,11 +326,11 @@
       Such servers do not impose any restriction on LDPRs and generally act as storage systems without any domain specific application logic and vocabularies. The <a href="#docstore">first scenario in this document</a> concerns a document storage system based on Basic Containers.
     </p>
     <p>
-      A Direct Container is a specialisation of a Basic Container. Additional assertions called membership triples which use a domain-specific vocabulary are made by a Direct Container as part of the creation process. The membership triples augment the containment triples maintained by all containers. For example, one aspect of a Product inventory system concerns the how a Direct Container is used for the management of a Product portfolio, where use of existing vocabularly is preferable.  
+      A Direct Container is a specialisation of a Basic Container. Additional assertions called membership triples which use a domain-specific vocabulary are made by a Direct Container as part of the creation process. The membership triples augment the containment triples maintained by all containers. For example, one aspect of a Product inventory system concerns the how a Direct Container is used for the management of a Product portfolio, where use of existing vocabulary is preferable.  
     </p>
     <figure id="fig-dc1">
       <img src="images/dc1.png" alt=".." />
-      <figcaption>Using domain vocabularly with a Direct container.</figcaption>
+      <figcaption>Using domain vocabulary with a Direct container.</figcaption>
     </figure>
     <p>
       Direct Container membership triples can be about subjects other than the Container resource. An example is a Photo management application where a Photo Container is used for the management of Photos, and where membership triples then express the relationship between a User and a Photo. 
@@ -465,12 +465,12 @@
 		 In the previous example, we saw that Alice can discover what operations are allowed on a resource by doing a GET request on the resource. As an alternative, she can use the OPTIONS operation to learn of the permitted operations on any given resource.
       </p>
 
-      <pre title="Request - retreiving OPTIONS of a basic container" class='example'>
+      <pre title="Request - retrieving OPTIONS of a basic container" class='example'>
  OPTIONS /alice/ HTTP/1.1
  Host: example.org      
       </pre> 
 
-      <pre title="Response - retreiving OPTIONS of a basic container" class='example'>
+      <pre title="Response - retrieving OPTIONS of a basic container" class='example'>
 HTTP/1.1 204 No Content
 Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
 Accept-Post: text/turtle, application/ld+json, image/bmp, image/jpeg