Update CR-ready issue marker regarding controller doc spec.

CR/2023-11-07/index.html

@@ -1398,15 +1398,15 @@ <h1 id="title" class="title">Verifiable Credential Data Integrity 1.0</h1> <h2 i
         </p>
 
         <div class="issue atrisk" id="issue-container-generatedID-4"><div role="heading" class="issue-title marker" id="h-issue-2" aria-level="4"><span>(Feature at Risk) Issue</span><span class="issue-label">: Potential for stand-alone Controller Document specification</span></div><p class="atrisk">
-This section on Controller Documents has been identified as potentially useful
-for other securing mechanisms such as [<cite><a class="bibref" data-link-type="biblio" href="#bib-vc-jose-cose" title="Securing Verifiable Credentials using JOSE and COSE">VC-JOSE-COSE</a></cite>]. There is a possibility
-that this section will be moved to an independent Controller Document
-specification, which would then be normatively referenced by this specification.
-If this migration occurs, it is expected that there will be little to no
-impact on implementations as the normative statements that exist in this
-section will remain in the new document or be preserved in this document as
-an additional set of requirements on top of the base Controller Document
-specification.
+There are lots of commonalities between this section on Controller Documents and
+similar sections in other securing mechanisms such as [<cite><a class="bibref" data-link-type="biblio" href="#bib-vc-jose-cose" title="Securing Verifiable Credentials using JOSE and COSE">VC-JOSE-COSE</a></cite>], or
+similar concepts in specifications such as [<cite><a class="bibref" data-link-type="biblio" href="#bib-did-core" title="Decentralized Identifiers (DIDs) v1.0">DID-CORE</a></cite>]. The Working Group is
+currently discussing the possibility to move this section to an independent
+Controller Document specification that can be referenced normatively. If this
+migration occurs, it is expected that there will be little to no impact on
+implementations as the normative statements that exist in this section will
+remain in the new document or be preserved in this document as an additional set
+of requirements on top of the base Controller Document specification.
         </p></div>
 
         <div class="issue" id="issue-container-generatedID-5"><div role="heading" class="issue-title marker" id="h-issue-3" aria-level="4"><span>Issue</span></div><div class="">Add examples of common Controller documents, such as