--- a/TR/WD-ldp-primer-20140620/Overview.html	Wed Jun 18 12:00:01 2014 +0100
+++ b/TR/WD-ldp-primer-20140620/Overview.html	Wed Jun 18 12:59:10 2014 +0100
@@ -636,7 +636,7 @@
       
       <p>As her document storage was just created, it is an empty container. </p>
 
-      <div class="example"><div class="example-title"><span>Example 2</span>: Response - basic container retrieval</div><div class="example"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK 
+      <div class="example"><div class="example-title"><span>Example 2</span>: Response - basic container retrieval</div><div class="exxample"><div class="turtle" style="font-family: sans-serif;">Turtle:</div><div class="turtle"><pre>HTTP/1.1 200 OK 
 Content-Type: text/turtle; charset=UTF-8
 Link: &lt;http://www.w3.org/ns/ldp#BasicContainer&gt;; rel='type', &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel='type'
 Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
@@ -678,10 +678,13 @@
 		 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>
 
-      <div class="example"><div class="example-title"><span>Example 3</span>: Request - retreiving OPTIONS of a basic container</div><div class="exxample">OPTIONS /alice/ HTTP/1.1
-Host: example.org      </pre></div> 
+      <div class="example">
+        <div class="example-title"><span>Example 3</span>: Request - retreiving OPTIONS of a basic container</div>
+        <pre class="example">OPTIONS /alice/ HTTP/1.1
+Host: example.org      </pre>
+      </div> 
 
-      <div class="example"><div class="example-title"><span>Example 4</span>: Response - retreiving OPTIONS of a basic container</div><div class="exxample">HTTP/1.1 204 OK
+      <div class="example"><div class="example-title"><span>Example 4</span>: Response - retreiving OPTIONS of a basic container</div><pre class="example">HTTP/1.1 204 OK
 Allow: OPTIONS,HEAD,GET,POST,PUT,PATCH
 Accept-Post: text/turtle, application/ld+json, image/bmp, image/jpeg
 Accept-Patch: example/patch
@@ -743,14 +746,14 @@
 
     
 
-   <div class="example"><div class="example-title"><span>Example 6</span>: Response - creating a RDF resource</div><div class="exxample">HTTP/1.1 201 Created
+   <div class="example"><div class="example-title"><span>Example 6</span>: Response - creating a RDF resource</div><pre class="example">HTTP/1.1 201 Created
 Location: http://example.org/alice/foaf
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel='type'
 Content-Length: 0 </pre></div>
       <p> The response to the create request provides a Link to the newly created resource using the Location header. In this case, the server has honored the hint provided by the slug header and created the new resource in the URL http://example.org/alice/foaf. </p>
       <p>Knowing the URL of the newly created resource, Alice can check the container again to confirm that the container correctly contains the newly created resource.</p>
 
-      <div class="example"><div class="example-title"><span>Example 7</span>: Request - basic container retrieval after resource created</div><div class="exxample">GET /alice/ HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 7</span>: Request - basic container retrieval after resource created</div><pre class="example">GET /alice/ HTTP/1.1
 Host: example.org
 Accept: text/turtle, application/ld+json</pre></div>
 
@@ -788,7 +791,7 @@
 
       <p>Next, Alice wants to upload a photo of herself to the document storage. She can create an image by POSTing it in the same way she created the RDF document.</p>
 
-      <div class="example"><div class="example-title"><span>Example 9</span>: Request - creating a non-RDF resource</div><div class="exxample">POST /alice/ HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 9</span>: Request - creating a non-RDF resource</div><pre class="example">POST /alice/ HTTP/1.1
 Host: example.org
 Slug: avatar
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
@@ -797,7 +800,7 @@
 
 ### binary data ###</pre></div> 
 
-      <div class="example"><div class="example-title"><span>Example 10</span>: Response - creating a non-RDF resource</div><div class="exxample">HTTP/1.1 201 Created
+      <div class="example"><div class="example-title"><span>Example 10</span>: Response - creating a non-RDF resource</div><pre class="example">HTTP/1.1 201 Created
 Location: http://example.org/alice/avatar
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type"
 Link: &lt;http://example.org/alice/avatar/meta&gt;; rel="describedby"
@@ -859,7 +862,7 @@
   "dcterms:title": "Alice’s FOAF file"
 }</pre></div></div></div> 
 
-      <div class="example"><div class="example-title"><span>Example 13</span>: Response - updating a RDF resource</div><div class="exxample">HTTP/1.1 204 No Content 
+      <div class="example"><div class="example-title"><span>Example 13</span>: Response - updating a RDF resource</div><pre class="example">HTTP/1.1 204 No Content 
 Link: &lt;http://www.w3.org/ns/ldp#Resource&gt;; rel="type" </pre></div>
 
       <p>If the operation is successful as shown above, the document will be updated with new information.</p>
@@ -876,11 +879,11 @@
       <p>Similar to the previous update operation, Alice uses the etag of the resource representation she retrieved with If-Match header to do a conditional delete to ensure that the resource state
       was not changed since she decided to delete it. </p>
 
-      <div class="example"><div class="example-title"><span>Example 14</span>: Request - deleting a RDF resource</div><div class="exxample">DELETE /alice/avatar HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 14</span>: Request - deleting a RDF resource</div><pre class="example">DELETE /alice/avatar HTTP/1.1
 Host: example.org
 If-Match: W/"123454322"        </pre></div> 
 
-      <div class="example"><div class="example-title"><span>Example 15</span>: Response - deleting a RDF resource</div><div class="exxample">HTTP/1.1 204 No Content </pre></div>
+      <div class="example"><div class="example-title"><span>Example 15</span>: Response - deleting a RDF resource</div><pre class="example">HTTP/1.1 204 No Content </pre></div>
    
      <p> As well as deleting the resource, the server removes the containment triple from the container. For example, a subsequent GET request on the container will return a graph isomorphic to the one shown in the following representation::</p>
      
@@ -901,11 +904,11 @@
 }</pre></div></div></div> 
      
      <p> For any subsequent request on the deleted resource, the server will respond with the appropriate HTTP response code. </p>
-      <div class="example"><div class="example-title"><span>Example 17</span>: Request - after deletion</div><div class="exxample">GET /alice/avatar HTTP/1.1
+      <div class="example"><div class="example-title"><span>Example 17</span>: Request - after deletion</div><pre class="example">GET /alice/avatar HTTP/1.1
 Host: example.org
 Accept: image/png</pre></div>
      
-      <div class="example"><div class="example-title"><span>Example 18</span>: Response - after deletion</div><div class="exxample">HTTP/1.1 410 Gone </pre></div>     
+      <div class="example"><div class="example-title"><span>Example 18</span>: Response - after deletion</div><pre class="example">HTTP/1.1 410 Gone </pre></div>     
     </section>
 
     <section typeof="bibo:Chapter" resource="#meta-structure" rel="bibo:Chapter" id="structural-manipulation-child-containers">
@@ -961,7 +964,7 @@
   "dcterms:description": "This container will contain photos of Alice."
 }</pre></div></div></div>  
       <p>If the create is successful, the server responds with location of the newly created container for the photos.</p>
-      <div class="example"><div class="example-title"><span>Example 21</span>: Response - creating the new container</div><div class="exxample">HTTP/1.1 201 Created
+      <div class="example"><div class="example-title"><span>Example 21</span>: Response - creating the new container</div><pre class="example">HTTP/1.1 201 Created
 Location: http://example.org/alice/photos/
 Content-Length: 0  </pre></div>  
 
@@ -1288,11 +1291,11 @@
       
      This example illustrates the behaviour of a Direct Container when a resource is deleted.
       
-      <div class="example"><div class="example-title"><span>Example 30</span></div><div class="exxample">DELETE /tracker/ldp-demo/bug3 HTTP/1.1 
+      <div class="example"><div class="example-title"><span>Example 30</span></div><pre class="example">DELETE /tracker/ldp-demo/bug3 HTTP/1.1 
 Host: example.org
 If-Match: W/"123454322"</pre></div>
       <p>If the  delete is successful, the server will respond with a success status code.</p>
-      <div class="example"><div class="example-title"><span>Example 31</span></div><div class="exxample">HTTP/1.1 204 No Content</pre></div>  
+      <div class="example"><div class="example-title"><span>Example 31</span></div><pre class="example">HTTP/1.1 204 No Content</pre></div>  
         
        <p> After the deletion, the representation of the container will look like the following</p>