--- a/ldp-primer/ldp-primer.html	Sun Jun 01 13:37:15 2014 +0200
+++ b/ldp-primer/ldp-primer.html	Sun Jun 01 19:46:53 2014 +0200
@@ -310,10 +310,10 @@
     <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-RS) and those using other formats called LDP Non-RDF Source (LDP-NR) such as html files, images, other binary files, etc. 
+      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-RS) and those using other formats called LDP Non-RDF Source (LDP-NR) such as html files, images, other binary files, etc. 
 Resources respond to retrieval operations using HTTP GET. 
 A description conveyed in the response document will describe one or more entities: a Person, a Status, a Product, an Order, a Bug, a Concept, a Relation, etc. by linking it to other entities or literals.
- These descriptions can lead an agent to  discover and process other information resources, describing yet further entities.
+ These descriptions can lead an agent to  discover and process other information resources [[WEBARCH]], describing yet further entities.
  Those entities served by an LDP Server - a.k.a LDPRs - can themselves be described in this way, so as to enable a client to understand what consequences interacting with them entails.
  The description of LDPRs and their relations to entities specify what might be termed the API. 
     </p>
@@ -322,16 +322,18 @@
     </p>
     <p>
       The LDP protocols covers read and write interactions with Resources.
- Writable aspects include creation of new resources (using the POST HTTP verbs), updates (using PUT or PATCH), and deletion of resources (using DELETE ).
- Resource creation is an essential feature providing structured creation of resources.
- The server reveals these read/write abilities of resources by describing them.
- This common pattern is often seen in cases where one resource is be made up of a number of others, e.g.  a Document Store consists of Documents, a Bug Tracker consists of Bugs, a Photo Album consists of Photos, a Networth of a person consists of Assets and Liabilities.
- This special kind of Resource is a Container (LDPC), and this is able to respond to requests to create new resources. During creation the created resource is appended to its Container and a containment link between the Container and the new entry is made.
+ The server reveals these read/write abilities of LDP resources by describing the LDPR with sets of relations where the subject is the resource named using a URL - often a relative URL - and the relations describe various properties of the resource, such as its type, its capabilities, ...
+ These descriptions are returned in representations of the resource on making requests on them using the HTTP GET method. 
+ The writable aspects cover creation of new resources (using the POST HTTP verbs), updates (using PUT or PATCH), and deletion (using DELETE ).
+ Central to LDP is the Container (LDPC), which is able to respond to requests to create new resources, which it is then said to contain. 
+ Creating a resource can have additional consequences in addition to the created LDPR, such as the creation of new relation to objects described in other RDF Source's ( LDP-RS ).
+ An LDPC can be asked at any time to list all of its contained resources.
+ This allows for many types of applications: Document Stores containing Documents,  Bug Trackers containing Bug reports, Photo Albums containing Photos, a Networth of a person containing Assets and Liabilities documents.
     </p>
     <p>
-      Therefore a LDPC is a specialization of a LDP-RS representing a collection of links to LDPRs or information resources [[WEBARCH]] that responds to client requests for creation, modification, and/or enumeration of its linked members and documents.
  The simplest container is the Basic Container (LDP-BC).
- It defines the basic containment described using generic vocabularly. This can be used in a generic storage service to manage a containment hierarchy of arbitrary resources.
+ It allows the creation of new LDPRs, including new Containers, and a GET request on that resource lists its contained LDPRs. 
+ This can be used in a generic storage service to manage a containment hierarchy of arbitrary information resources.
     </p>
     <figure id="fig-bc">
       <img src="images/bc.png" alt=".." />
@@ -339,7 +341,8 @@
     </figure>
     <p>
       Such servers do not impose any restriction on LDPRs and generally act as storage systems without any domain specific application logic and vocabularies.
- The first scenarion in this document concerns a document storage system based on Basic Containers.
+    A client posting to such a container is not bound to any further consequences other than those that publishing that document may bind him to. 
+ The first scenario in this document concerns a document storage system based on Basic Containers.
     </p>
     <p>
       A Direct Container allows to use some domain specific vocabulary to relate the resources of the hierarchy. The additional assertion is called the membership property.