Reword Authorization section based on @David-Chadwick's feedback.

Author: msporny

index.html

@@ -2047,14 +2047,18 @@ <h2>Disputes</h2>
         <h2>Authorization</h2>
 
         <p>
-It is arguable that <a>verifiable credentials</a> or
-<a>verifiable presentations</a> should be used as authorization mechanisms
-that a <a>holder</a> could use to access various
-systems. This specification does not contemplate such a usage of verifiable
-credentials and MUST NOT be considered an authorization framework on its own.
-The Working Group did consider authorization use cases
-during the creation of this specification and is pursuing that work as an
-architectural layer that is built on top of this specification.
+<a>Verifiable credentials</a> are intended as a means of reliably identifying
+subjects. Whilst it is recognized that Role Based Access Controls (RBAC) and
+Attribute Based Access Controls (ABAC) rely on this identification as a means
+of authorizing subjects to access resources, this specification
+MUST NOT be used for authorization purposes without an accompanying
+authorization framework.
+        </p>
+
+        <p>
+The Working Group did consider authorization use cases during the creation of
+this specification and is pursuing that work as an architectural layer that is
+built on top of this specification.
         </p>
 
       </section>