From 9a57a86f599a10fa6c133958a4dcc6d40554cd14 Mon Sep 17 00:00:00 2001
From: Greg Tonoski <111286121+GregTonoski@users.noreply.github.com>
Date: Sun, 27 Oct 2024 21:10:30 +0100
Subject: [PATCH] better word

---
 Comments:BIP-0341.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Comments:BIP-0341.md b/Comments:BIP-0341.md
index 0c76ddf..4a52823 100644
--- a/Comments:BIP-0341.md
+++ b/Comments:BIP-0341.md
@@ -4,4 +4,4 @@ There is the should-type requirement of hardcoded constant "TapTweak" in derivat
 1. avoidance/minimisation of a number of hardcoded values (in accordance with commonly accepted best practices);
 2. keeping requirements specification consice and of high relevance to changes in protocol and consensus rules.
 
-Also it may be worth adding an explanatory/warning note that sometimes the described attack in MSDL-pop scenario is not averted by the proposed "TapTweak" mechanism which is excluded for TapTweaks (t) that exceed SECP256K1_ORDER (regarding the point 23 in Rationale section. i.e. https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki#cite_ref-23-0).
\ No newline at end of file
+Also it may be worth adding an explanatory/warning note that sometimes the described attack in MSDL-pop scenario is not prevented by the proposed "TapTweak" mechanism which is excluded for TapTweaks (t) that exceed SECP256K1_ORDER (regarding the point 23 in Rationale section. i.e. https://github.com/bitcoin/bips/blob/master/bip-0341.mediawiki#cite_ref-23-0).
\ No newline at end of file