diff --git a/index.html b/index.html
index c951eab..c13e7f3 100644
--- a/index.html
+++ b/index.html
@@ -1849,11 +1849,11 @@ <h3>DataIntegrityProof</h3>
         <p class="note" title="Design Patterns of Legacy Cryptographic Suites">
 One of the design patterns seen in Data Integrity cryptosuites from
 2012 to 2020 was use of the `type` property to establish a specific type for a
-cryptographic suite. For example, the
+cryptographic suite; the
 <a href="https://www.w3.org/TR/vc-di-eddsa/#the-ed25519signature2020-suite">
 Ed25519Signature2020 cryptographic suite</a> was one such specification. This
 led to a greater burden on cryptographic suite implementations, where every new
-cryptographic suite required a new JSON-LD Context to be specified, resulting
+cryptographic suite required specification of a new JSON-LD Context, resulting
 in a sub-optimal developer experience. A streamlined version of this design
 pattern emerged in 2020, such that a developer would only need to include a
 single JSON-LD Context to support all modern cryptographic suites. This
@@ -1881,7 +1881,7 @@ <h2>Algorithms</h2>
       <p>
 The algorithms defined below operate on documents represented as <dfn
 data-cite="RFC8259#section-4">JSON objects</dfn>. This specification follows the
-[[[JSON-LD11-API]]] specification in representing a JSON object as an [=map=].
+[[[JSON-LD11-API]]] specification in representing a JSON object as a [=map=].
 An <dfn class="export">unsecured data document</dfn> is a [=map=] that contains
 no proof values. An <dfn>input document</dfn> is an [=map=] that has not yet had
 the current proof added to it, but it MAY contain a proof value that was added
@@ -1923,7 +1923,7 @@ <h3>Processing Model</h3>
 disclosure, using acceptable cryptographic key material.
           </li>
           <li>
-The software uses the applicable algorithms in either Section [[[#add-proof]]]
+The software uses the applicable algorithm(s) provided in Section [[[#add-proof]]]
 or Section [[[#add-proof-set-chain]]] to add one or more proofs.
           </li>
         </ol>
@@ -1940,11 +1940,11 @@ <h3>Processing Model</h3>
 [[[#verify-proof-sets-and-chains]]].
           </li>
           <li>
-The software uses JSON Schema or equivalent mechanism to validate that the
+The software uses JSON Schema or an equivalent mechanism to validate that the
 incoming document follows an expected schema used by the application.
           </li>
           <li>
-The software uses the applicable algorithms provided in Section [[[#verify-proof]]]
+The software uses the applicable algorithm(s) provided in Section [[[#verify-proof]]]
 or Section [[[#verify-proof-sets-and-chains]]] to verify the integrity of the
 incoming document.
           </li>