--- a/dcat/index.html	Tue Jan 31 10:36:35 2012 -0500
+++ b/dcat/index.html	Tue Jan 31 11:12:17 2012 -0500
@@ -74,16 +74,18 @@
 <hr />
 <div id="abstract" class="introductory section">
   <h2>Abstract</h2>
-    <p>DCAT is an RDF vocabulary designed to facilitate interoperability between data catalogues published on the Web. DCAT emerged from the W3C <a href="http://www.w3.org/egov/">eGov</a> Interest Group and W3C <a href="http://www.w3.org/2011/gld/">Government Linked Data</a> (GLD) Working Group but can be used for any entity publishing catalogues of datasets.</p>
+    <p>DCAT is an RDF vocabulary designed to facilitate interoperability between data catalog published on the Web. DCAT emerged from the W3C <a href="http://www.w3.org/egov/">eGov</a> Interest Group and W3C <a href="http://www.w3.org/2011/gld/">Government Linked Data</a> (GLD) Working Group but can be used for any entity publishing catalog of datasets.</p>
     <p>DCAT was conceived with the following benefits in mind:
 <ul>
-<li>Embedded metadata in catalogue web pages increases data "findability, enables decentralised publishing of catalogues, and makes federated search</li>
-<li>Provides a basis for one-click download and installation of data packages</li>
-<li>Aggregated DCAT metadata serves as manifest file to faciliate digital preservation</li>
-<li>A uniform metadata model enables applications to be built once and work with multiple catalogues</li>
+<li>Embedded metadata in catalog web pages increases data "findability," enables decentralised publishing of catalogs, and facilitates federated dataset search across sites</li>
+<li>A uniform catalog vocabulary provides a basis for one-click download and installation of data packages
+<br /> @@@ TODO.jse: I don't understand why this point is important! @@@
+</li>
+<li>Aggregated DCAT metadata can serve as a manifest file to faciliate digital preservation</li>
+<li>A uniform metadata model enables applications to be built once and work with multiple catalog</li>
 </p>
     <p>This document defines the RDF schema for DCAT and provides examples for its use.</p>
-<p>@@@ TODO: clarify? @@@</p>
+<p>@@@ TODO.jse: Clarify? Anything more to add? @@@</p>
 </div>
 <div id="sotd" class="introductory section">
   <h2>Status of This Document</h2>
@@ -96,7 +98,7 @@
   signals its move to the Recommendations Track. DCAT was first
   developed and published by DERI and enjoys widespread use at the time of
   this publication. The <a href="http://vocab.deri.ie/dcat">original vocabulary</a>
-  was further developed on the @@@eGov Interest Group's wiki@@@ before being brought onto the
+  was further developed on the <a href="http://www.w3.org/egov/">eGov Interest Group's wiki</a> before being brought onto the
   Recommendation Track by the 
   <a href="http://www.w3.org/2011/gld/">Governmenet Linked Data Working Group</a>
   which intends for it to become a Recommendation.
@@ -194,15 +196,15 @@
 <p>This document does not prescribe any particular method of deploying data expressed in DCAT. DCAT is applicable in many contexts including RDF accessible via SPARQL endpoints, embedded in HTML pages as RDFa, or serialized as e.g. RDF/XML or Turtle. The examples in this document use Turtle simply because of Turtle's readability.</p>
 
 <h2 id="conformance">Conformance</h2>
-@@@TODO What goes here?@@@
+@@@ TODO.jse: What goes here? @@@
 
 <h2 id="terminology">Terminology</h2>
-@@@TODO What goes here?@@@
+@@@ TODO.jse: What goes here? @@@
 
 <h2 id="ns">Namespaces</h2>
 <p>The namespace for DCAT is <code>http://www.w3.org/ns/dcat#</code>. However,
 it should be noted that DCAT makes extensive use of terms from other vocabularies,
-in particular Dublin Core [@@@TODO Ref?@@@]. DCAT itself defines a minimal set of classes and
+in particular <a href="http://dublincore.org/documents/dcmi-terms/">Dublin Core</a>. DCAT itself defines a minimal set of classes and
 properties of its own. A full set of namespaces and prefixes used in this
 document is shown in the table below.</p>
 
@@ -327,7 +329,7 @@
 </table>
 
 <h3 id="Property:_publisher">Property: publisher</h3>
-<p>The entity responsible for making the catalogue online.</p>
+<p>The entity responsible for making the catalog online.</p>
 
 <table class="definition">
   <thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/publisher">dcterms:publisher</a></th></tr></thead>
@@ -337,7 +339,7 @@
 </table>
 
 <h3 id="Property:_spatial.2Fgeographic_coverage">Property: spatial/geographic coverage></h3>
-<p>The geographical area covered by the catalogue.</p>
+<p>The geographical area covered by the catalog.</p>
 <table class="definition">
   <thead><tr><th>RDF Property:</th><th><a href="http://purl.org/dc/terms/spatial">dcterms:spatial</a></th></tr></thead>
   <tbody>