--- a/dcat/index.html	Thu May 30 14:18:49 2013 +0100
+++ b/dcat/index.html	Thu May 30 16:46:24 2013 +0100
@@ -200,7 +200,8 @@
 
 <pre>  &nbsp;:dataset-001 dcat:theme&nbsp;:accountability&nbsp; .
 </pre>
-<p>Notice that this dataset is classified under the domain represented by the relative URI&nbsp;:accountability. This should be part of the concepts scheme identified by the URI&nbsp;:themes that was used to describe the catalog domains. An example SKOS description
+<p>Notice that this dataset is classified under the domain represented by the relative URI&nbsp;:accountability. 
+It is recommended to define the concept as part of the concepts scheme identified by the URI&nbsp;:themes that was used to describe the catalog domains. An example SKOS description:
 </p>
 <pre>  &nbsp;:accountability 
        a skos:Concept&nbsp;;
@@ -961,7 +962,8 @@
   <thead><tr><th>RDF Class:</th><th><a href="http://www.w3.org/2004/02/skos/core#Concept">skos:Concept</a></th></tr></thead>
   <tbody>
     <tr><td  class="prop">Definition:</td><td>A category or a theme used to describe datasets in the catalog.</td></tr>
-    <tr><td class="prop">Usage note:</td><td>It is necessary to use either skos:inScheme or skos:topConceptOf on every skos:Concept otherwise it's not clear which concept scheme they belong to.</td></tr>
+    <tr><td class="prop">Usage note:</td><td>It is recommended to use either skos:inScheme or skos:topConceptOf on every skos:Concept 
+    used to classify datasets to link it to the concept scheme it belongs to. This concept scheme is typically associated with the catalog using dcat:themeTaxonomy</td></tr>
     <tr><td class="prop">See also:</td><td><a href="#Property:catalog_themes">catalog themes</a>, <a href="#Property:dataset_theme">dataset theme</a></td></tr>
   </tbody>
 </table>