--- a/data-cube/index.html	Sat Oct 06 18:10:07 2012 +0100
+++ b/data-cube/index.html	Thu Oct 11 16:32:33 2012 +0200
@@ -605,7 +605,7 @@
     <li><code>sdmx-concept</code>: SKOS Concepts for each COG defined concept;</li>
     <li><code>sdmx-code</code>: SKOS Concepts and ConceptSchemes for each COG defined code list;</li>
     <li><code>sdmx-dimension</code>: component properties corresponding to each COG concept that can be used as a dimension;</li>
-    <li><code>sdmx-attribute</code>: component properties corresponding to each COG concept that can be used as a attribute;</li>
+    <li><code>sdmx-attribute</code>: component properties corresponding to each COG concept that can be used as an attribute;</li>
     <li><code>sdmx-measure</code>: component properties corresponding to each COG concept that can be used as a measure.</li>
   </ul>
 
@@ -683,7 +683,7 @@
   The <code>qb:DataStuctureDefinition</code> will be reusable across other data sets with the same structure.</p>
 
 <p>In the simplest case the <code>qb:ComponentSpecification</code> simply references the
-  corresponding <code>qb:ComponentProperty</code> (ususally using one of the sub properties
+  corresponding <code>qb:ComponentProperty</code> (usually using one of the sub properties
   <code>qb:dimension</code>, <code>qb:measure</code> or <code>qb:attribute</code>). 
   However, it is also possible to qualify the
   component specification in several ways.</p>
@@ -708,7 +708,7 @@
 </ul>
 
 <p>In the case of our running example the dimensions can be usefully ordered. There is only one
-   attribute, the unit measure, and this is required. In the interests of illustrating the vocabulary
+   attribute, the unit measure, and this is required. In the interest of illustrating the vocabulary
    use we will declare that this attribute will be attached at the level of the data set, however 
   flattened representations are in general easier to query and combine.</p>
 
@@ -1210,7 +1210,7 @@
 (which do not use such a datatype).</p>
 
 <p>It is convenient and good practice when developing a code list to also 
-create an Class to denote all the codes within the code
+create a Class to denote all the codes within the code
 list, irrespective of hierarchical structure. This allows the range of an
 <code>qb:ComponentProperty</code> to be defined by using <code>rdfs:range</code>
 which then permits standard RDF closed-world checkers to validate use of the
@@ -1736,6 +1736,10 @@
 
 <p>The authors would also like to thank John Sheridan for his comments,
 suggestions and support for this work.</p>
+
+<p>Many individuals provided valuable comments on this specification
+as it made its way through the W3C process, including Curran Kelleher, …</p>
+
 </section>