Merge pull request #1 from w3c/koalie-patch-1

Tone down statement

index.html

@@ -626,7 +626,7 @@ <h4 class="heading settled" data-level="2.2.4" id="opportunities-and-threats"><s
     <li data-md>
      <p><strong>Privacy loss</strong> (<em>surveillance</em>): if this technology is not designed and implemented properly, it can lead to surveillance by state and non-state actors such as government and private technology providers. For example, centralized or federated models are more prone to these threats, while decentralized models are less so, but it depends on how they are implemented. Therefore, it is necessary to provide privacy-preserving technologies and implement them properly.</p>
    </ul>
-   <p class="note" role="note"><span class="marker">Note:</span> W3C is handling this issue with a <a href="#a5">Threat Model</a>.</p>
+   <p class="note" role="note"><span class="marker">Note:</span> W3C might consider handling this issue with a <a href="#a5">Threat Model</a>.</p>
    <h3 class="heading settled" data-level="2.3" id="digital-identity-management-models"><span class="secno">2.3. </span><span class="content">Digital identity management models</span><a class="self-link" href="#digital-identity-management-models"></a></h3>
    <p>With these assumptions, before proceeding, it is important to understand how digital identities are managed and how they have evolved over the years.</p>
    <p>Let us start with the example of a person’s identity, and break it down. We had:</p>