From 1aea3eae2324a282aee7341c57fc5b96028f8d11 Mon Sep 17 00:00:00 2001
From: ritikarawlani <38657562+ritikarawlani@users.noreply.github.com>
Date: Thu, 18 Jul 2024 16:13:19 +0530
Subject: [PATCH] fix remove as well as sha1

---
 Volume3/ch-5.10.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Volume3/ch-5.10.html b/Volume3/ch-5.10.html
index e822348..6f09eb1 100644
--- a/Volume3/ch-5.10.html
+++ b/Volume3/ch-5.10.html
@@ -217,7 +217,7 @@ <h3 id="5.10.5">5.10.5 JSON Signature Verification</h3>
         <li class="bullet-list1">The document may not be accessible to the user, for example authorization denied, so confirmation of valid signed content may be impossible.</li>
       </ul>
       <p>The decision on what degree of verification is needed is determined by the application and use case.</p>
-      <p>The Content Consumer SHALL be able to validate content that uses SHA256 as well as SHA1.</p>
+      <p>The Content Consumer SHALL be able to validate content that uses SHA256.</p>
       <h3 id="5.10.6">5.10.6 JSON Document Sharing Metadata</h3>
       <p>This section applies when the Content Creator or Content Consumer is utilizing a Document Sharing Profile for transport. This section defines the source for all required Document Sharing attributes and as many optional attributes as makes sense for implementers’ applications.</p>
       <h4 id="5.10.6.1">5.10.6.1 Document Sharing – DocumentEntry Metadata</h4>