From 4ddaa62d22117ea4cdd42ca222c931918ca9c5dc Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Fri, 15 Dec 2023 13:55:57 -0500
Subject: [PATCH] Integrate input from @awoie. Align w/ verification section.

---
 index.html | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/index.html b/index.html
index cd94a55c1..53a98e47e 100644
--- a/index.html
+++ b/index.html
@@ -2043,14 +2043,15 @@ <h3>Securing Mechanisms</h3>
 
         <ul>
           <li>
-MUST document normative algorithms that can be used to secure and verify
-<a>verifiable credentials</a> and <a>verifiable presentations</a>.
+MUST document normative algorithms that provide content integrity protection
+for <a>conforming documents</a>. The algorithms MAY be general in nature and
+MAY be used to secure data other than <a>conforming documents</a>.
           </li>
           <li>
 MUST provide a verification mechanism that returns only the information in the
 <a>conforming document</a> that has been secured. It MAY provide an
 additional mechanism to receive other information that might be helpful
-to developers. The concrete interface that is
+during validation or for debugging purposes. The concrete interface that is
 expected to be provided is detailed in the
 <a href="#verify-securing-mechanism">securing mechanism verification
 algorithm</a> section.