diff --git a/dbz/draft-corrections/draft-irtf-cfrg-opaque.html b/dbz/draft-corrections/draft-irtf-cfrg-opaque.html
index 12c690fe..bf717918 100644
--- a/dbz/draft-corrections/draft-irtf-cfrg-opaque.html
+++ b/dbz/draft-corrections/draft-irtf-cfrg-opaque.html
@@ -3795,7 +3795,7 @@ <h3 id="name-protecting-the-registration">
 If the channel is only authenticated (this is a requirement for correct
 identification of the parties), a confidential channel can be established
 using public-key encryption, e.g., with HPKE <span>[<a href="#RFC9180" class="cite xref">RFC9180</a>]</span>. However, the details
-of this mechanism are out of the scope of this document.<a href="#section-10.11-1" class="pilcrow">¶</a></p>
+of this mechanism are out of scope for this document.<a href="#section-10.11-1" class="pilcrow">¶</a></p>
 </section>
 </div>
 <div id="password-salt-and-storage-implications">
diff --git a/dbz/draft-corrections/draft-irtf-cfrg-opaque.txt b/dbz/draft-corrections/draft-irtf-cfrg-opaque.txt
index 8897029e..0e315363 100644
--- a/dbz/draft-corrections/draft-irtf-cfrg-opaque.txt
+++ b/dbz/draft-corrections/draft-irtf-cfrg-opaque.txt
@@ -2250,7 +2250,7 @@ def AuthServerRespond(cleartext_credentials, server_private_key, client_public_k
    (this is a requirement for correct identification of the parties), a
    confidential channel can be established using public-key encryption,
    e.g., with HPKE [RFC9180].  However, the details of this mechanism
-   are out of the scope of this document.
+   are out of scope for this document.
 
 10.12.  Password Salt and Storage Implications