Update Controller Document at risk marker.

Co-authored-by: Ivan Herman <[email protected]>

Author: msporny

index.html

@@ -962,15 +962,15 @@ <h3>Controller Documents</h3>
 
         <p class="issue atrisk"
           title="Potential for stand-alone Controller Document specification">
-This section on Controller Documents has been identified as potentially useful
-for other securing mechanisms such as [[?VC-JOSE-COSE]]. 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 [[?VC-JOSE-COSE]], or
+similar concepts in specifications such as [[?DID-CORE]]. 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 class="issue">Add examples of common Controller documents, such as