Update docs html

docs/www/index.html

@@ -48,8 +48,8 @@
 
                     <article id="content">
                       <h1 id="data-agreement-da-specification"><a class="toc-anchor" href="#data-agreement-da-specification" >§</a> Data Agreement (DA) Specification</h1>
-<p><strong>Specification Status:</strong> version 2.1.0</p>
-<p>Released and implemented.</p>
+<p><strong>Specification Status:</strong>
+version 2.1.0 (Released and implemented)</p>
 <p><strong>Latest Draft:</strong> <a path-0="da.igrant.io"href="https://da.igrant.io" >Avaialble here</a></p>
 <p><strong>Editors:</strong></p>
 <ul>
@@ -68,9 +68,10 @@ <h1 id="data-agreement-da-specification"><a class="toc-anchor" href="#data-agree
 <li><a path-0="github.com"path-1="decentralised-dataexchange"path-2="automated-data-agreements"href="https://github.com/decentralised-dataexchange/automated-data-agreements" >GitHub repo</a></li>
 <li><a path-0="github.com"path-1="decentralised-dataexchange"path-2="automated-data-agreements"path-3="issues"href="https://github.com/decentralised-dataexchange/automated-data-agreements/issues" >File a bug</a></li>
 </ul>
+<hr>
 <h2 id="abstract"><a class="toc-anchor" href="#abstract" >§</a> Abstract</h2>
 <p>A Data Agreement records the conditions for an organization to process personal data in accordance with privacy regulation (e.g. GDPR) captured in a signed receipt given to the individual. To automate creation of the record and increase the trust assurance a Data Protection Impact Assessment may be used to populate the record.</p>
-<h1 id="introduction"><a class="toc-anchor" href="#introduction" >§</a> Introduction</h1>
+<h2 id="introduction"><a class="toc-anchor" href="#introduction" >§</a> Introduction</h2>
 <p>This specification describes how a Data Agreement between an organisation and individual is managed in order to capture, in a receipt, the conditions of processing of personal data. The receipt acts as evidence and demonstrates a higher level of accountability and is based on standard schemas. The accountability is further enhanced by directly integrating the Data Agreement with the input from a risk assessment, e.g. Data Protection Impact Assessment.</p>
 <p>In order to create the Data Agreement, and the resulting receipt as proof, a number of steps are required from different actors. This document describes these steps involved and is described as part of a Data Agreement lifecycle.</p>
 <h2 id="abbreviations"><a class="toc-anchor" href="#abbreviations" >§</a> Abbreviations</h2>
@@ -392,11 +393,11 @@ <h4 id="termination"><a class="toc-anchor" href="#termination" >§</a> Terminati
 <h3 id="proof"><a class="toc-anchor" href="#proof" >§</a> Proof</h3>
 <p>In accordance with GDPR Art. 30, Records of processing activities, a Data Controller (Data Source and DUS) shall record processing activities under its responsibilities. The records shall be available to the individual to inspect in the form of a receipt and provide means of an audit. An audit can be initiated due to the following reasons:</p>
 <ol>
-<li>Complaint by Data Subject</li>
+<li>Complaint by Data Subject (Or Individual)</li>
 <li>Review of Data Source or Data Using Service record logs</li>
 </ol>
-<p>The complaint by Data Subject will include a copy of the Data Agreement receipt and explanation of the violation by Data Source or DUS.</p>
-<p>The following sequence is the approach taken when the auditor reviews implementation of Data Agreement capture and withdrawal. If the auditor lacks the software to perform the read then a dashboard access is provided by the Data Source or DUS. In case of a Data Subject complaint a reference to the original Data Agreement is shared with the Auditor so the Auditor can perform the same verification.</p>
+<p>The complaint by Data Subject (Or Individual) will include a copy of the Data Agreement receipt and explanation of the violation by Data Source or DUS.</p>
+<p>The following sequence is the approach taken when the auditor reviews implementation of Data Agreement capture and withdrawal. If the auditor lacks the software to perform the read then a dashboard access is provided by the Data Source or DUS. In case of a Data Subject complaint, a reference to the original Data Agreement is shared with the Auditor so the Auditor can perform the same verification.</p>
 <p><img src="sequences/data-agreement-audit.svg" alt="Data Agreement audit"></p>
 <h1 id="references"><a class="toc-anchor" href="#references" >§</a> References</h1>
 <p>[1]  <a path-0="github.com"path-1="decentralised-dataexchange"path-2="automated-data-agreements"path-3="blob"path-4="main"path-5="docs"path-6="interface_specification.md"href="https://github.com/decentralised-dataexchange/automated-data-agreements/blob/main/docs/interface_specification.md" >Data Agreement Interface Specification</a></p>
@@ -1222,6 +1223,7 @@ <h2 id="iso-standards"><a class="toc-anchor" href="#iso-standards" >§</a> ISO S
                       <div id="toc_list">
                         <ul class="toc">
 <li><a href="#abstract" >Abstract</a></li>
+<li><a href="#introduction" >Introduction</a></li>
 <li><a href="#abbreviations" >Abbreviations</a></li>
 <li><a href="#data-agreement-lifecycle-actors" >Data Agreement lifecycle actors</a></li>
 <li><a href="#data-exchange-agreements-landscape" >Data exchange agreements landscape</a>