incorporate suggestions

Author: LPardue

draft-ietf-httpbis-unencoded-digest.md

@@ -234,11 +234,13 @@ Since the digest is calculated on unencoded representation bytes, validation of
 a message with content codings (as described above) can only succeed where the
 decoded output produces the same byte sequence as the input. While {{Section
 8.4.1 of !HTTP=RFC9110}} describes content codings to operate "without loss of
-information", that doesn't necessarily mean a byte-for-byte equivalence. Many
-registered content codings do provide equivalence but there is no requirement
-for it; it remains a possibility that decoding could produce a different byte
-sequence. In order to avoid unintended validation failures, care is advised when
-selecting content coding for use with `Unencoded-Digest`.
+information", that doesn't necessarily mean a byte-for-byte equivalence. It's
+entirely possible for content codings to perform semantically-meaningless
+transformations that nevertheless result in a decoded byte sequence that does
+not exactly match the original unencoded representation. In order to avoid
+unintended validation failures, care is advised when selecting content codings
+for use with `Unencoded-Digest`; many registered content codings do provide
+byte-for-byte equivalence and are appropriate.
 
 
 # Integrity Fields are Complementary