--- a/bp/index.html	Wed Nov 20 21:21:52 2013 +0100
+++ b/bp/index.html	Wed Nov 20 21:26:54 2013 +0100
@@ -407,9 +407,9 @@
 
 
 <p><i>Let's consider a list of equipments where the codes used are: A101="Police", A206="Post Office" and A504="Restaurant". With SKOS, we could define the following structure:</i></p>
-<div class="example">
 
-<pre>
+
+<pre class="example">
 	&lt;http://example.org/codes/typeEquipment/A101> 
     rdf:type skos:Concept, ex:TypeEquipmentA ;
     skos:notation "A101"
@@ -434,7 +434,7 @@
     rdfs:label "Type d'equipements"@fr .
   </pre>
 
-</div>
+
 
 </section>
 
@@ -680,15 +680,15 @@
 
 <p class="note"><b>TAG advices on http issues</b><br>
 The TAG provides advice to the community that they may mint "http" URIs for any resource provided that they follow this simple rule for the sake of removing ambiguity as below:
-<div class="example">
-<pre >
+
+<pre class="example">
 <li> If an "http" resource responds to a GET request with a 2xx response, then the resource identified by that URI is an information resource;</li>
 <li> If an "http" resource responds to a GET request with a 303 (See Other) response, then the resource identified by that URI could be any resource;</li>
 <li> If an "http" resource responds to a GET request with a 4xx (error) response, then the nature of the resource is unknown.
 </li>
 </ul>
  </pre>
-</div>
+
 
 The practical implication of http-range-14 for Linked Data and Semantic Web implementors is the requirement to return an HTTP 303 (See Other) response when resolving HTTP URI identifiers for conceptual or physical resources (that is, for resources whose canonical content is non-informational in nature, c.f. [[Wood2007]]).  Current implementations of the Persistent URL (PURL) server provide support for 303 URIs [[Wood2010]]. Although the issue remains unsettled, and occasional attempts have been (and probably will be) made to revisit the TAG’s decision, however compliance with the http-range-14 decision until such time as it may be updated is recommended.
 </p>