--- a/bp/index.html	Thu Dec 05 09:45:56 2013 +0100
+++ b/bp/index.html	Thu Dec 05 09:58:11 2013 +0100
@@ -132,8 +132,13 @@
             			href: "https://www.gov.uk/government/publications/designing-uri-sets-for-the-uk-public-sector/" ,
             			authors: ["Cabinet Office GOV.UK"] ,
             			publisher: "Cabinet Office UK"
-            			}
-
+            			},
+            "Wood2010":{
+                        title: "Linking Enterprise Data",
+                        href: "http://download.e-bookshelf.de/download/0000/0067/81/L-G-0000006781-0002335618.pdf",
+                        authors: ["David Wood"] ,
+                        publisher: "Springer New York"
+                         }
             
             }
            
@@ -206,7 +211,7 @@
 
 <!--drop this suggested by Dave R. <p class='stmt'><a href="#NOMINATE">NOMINATE A PILOT:</a> <br>Nominate a pilot project on Linked Open Data.
 </p> -->
-<p class='stmt'><a href="#WROFLOW">CHOOSE A WORKFLOW:</a><br>Determine which workflow to use for your Linked Open Data use case.
+<p class='stmt'><a href="#WORKFLOW">CHOOSE A WORKFLOW:</a><br>Determine which workflow to use for your Linked Open Data use case.
  </p>
 
 <p class='stmt'><a href="#SELECT">SELECT A DATA SET:</a> <br>Select a data set that provides benefit to others for re-use.  Consider a data set that your organization collects unique information that when combined with other open data provides greater value.  For example, publishing facilities that can then be linked with geographic information including postal codes is a popular example.
@@ -256,7 +261,7 @@
 </section>
 
 <!-- Diagrams -->
-<section id='NOMINATE'>
+<section id='WORKFLOW'>
 <h2> Linked Open Data Lifecycle </h2>
 <!-- <p class='issue'>Does it make sense to base the GLD life cycle on one of the general LD life cycles? See <a href="https://www.w3.org/2011/gld/track/issues/15">ISSUE-15</a></p> -->
 <p>
@@ -722,16 +727,16 @@
 <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:
 
-<pre class="highlight">
+<ul class="highlight">
 <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>
+ 
 
 
-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.
+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.  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>
 
 </section>