Further clarifications on JSON-only processing.

Co-authored-by: Mike Prorock <[email protected]>
Co-authored-by: Ted Thibodeau Jr <[email protected]>

index.html

@@ -3763,7 +3763,7 @@ <h2>JSON Processing</h2>
 
           <ul>
             <li>
-When using the JOSE or COSE specifications to secure a
+Prior to verification when using the JOSE or COSE specifications to secure a
 <a>verifiable credential</a> or <a>verifiable presentation</a>.
             </li>
             <li>
@@ -3776,7 +3776,8 @@ <h2>JSON Processing</h2>
             <li>
 When operating on <a>verifiable credentials</a> or <a>verifiable
 presentations</a> in a software application after verification or validation
-is performed.
+is performed for securing mechanisms that require an understanding of
+and processing of JSON-LD.
             </li>
             <li>
 When an application chooses to process the media type using the `+json`
@@ -3799,13 +3800,14 @@ <h2>JSON Processing</h2>
           </ul>
 
           <p>
-Using static context files and a JSON Schema to ensure proper URL values and
-order is one acceptable approach when implementing the rule above.
+Using static context files with a JSON Schema is one acceptable approach to
+implementing the rule above. This can ensure proper term identification,
+typing, and order, when a JSON document is processed as JSON-LD.
           </p>
 
           <p>
 The rule above guarantees semantic interoperability between JSON and JSON-LD for
-terms defined by the `@context` mechanism. While JSON-LD processors will use the
+literal JSON keys mapped to URIs by the `@context` mechanism. While JSON-LD processors will use the
 specific mechanism provided and can verify that all terms are correctly
 specified, JSON-based processors implicitly accept the same set of terms without
 testing that they are correct. In other words, the context in which the data