From 67b267948a2f75932645e8955417e70bd8c40674 Mon Sep 17 00:00:00 2001
From: Jonathan Cross <jcross@gmail.com>
Date: Sun, 25 Sep 2016 01:36:00 +0200
Subject: Improving wording of "makes them consuming"...

---
 bip-0147.mediawiki | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

(limited to 'bip-0147.mediawiki')

diff --git a/bip-0147.mediawiki b/bip-0147.mediawiki
index 8b6fe1a..352f48d 100644
--- a/bip-0147.mediawiki
+++ b/bip-0147.mediawiki
@@ -9,14 +9,14 @@
 
 ==Abstract==
 
-This document specifies proposed changes to the Bitcoin transaction validity rules to fix the malleability of extra stack element for <code>OP_CHECKMULTISIG</code> and <code>OP_CHECKMULTISIGVERIFY</code>.
+This document specifies proposed changes to the Bitcoin transaction validity rules to fix a malleability vector in the extra stack element consumed by <code>OP_CHECKMULTISIG</code> and <code>OP_CHECKMULTISIGVERIFY</code>.
 
 
 ==Motivation==
 
 Signature malleability refers to the ability of any relay node on the network to transform the signature in transactions, with no access to the relevant private keys required. For non-segregated witness transactions, signature malleability will change the <code>txid</code> and invalidate any unconfirmed child transactions. Although the <code>txid</code> of segregated witness ([https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki BIP141]) transactions is not third party malleable, this malleability vector will change the <code>wtxid</code> and may reduce the efficiency of compact block relay ([https://github.com/bitcoin/bips/blob/master/bip-0152.mediawiki BIP152]).
 
-A design flaw in <code>OP_CHECKMULTISIG</code> and <code>OP_CHECKMULTISIGVERIFY</code> makes them consuming an extra stack element ("dummy element") after signature validation. The dummy element is not inspected in any manner, and could be replaced by any value without invalidating the script. This document specifies a new rule to fix this signature malleability.
+A design flaw in <code>OP_CHECKMULTISIG</code> and <code>OP_CHECKMULTISIGVERIFY</code> causes them to consume an extra stack element ("dummy element") after signature validation. The dummy element is not inspected in any manner, and could be replaced by any value without invalidating the script. This document specifies a new rule to fix this signature malleability.
 
 
 ==Specification==
-- 
cgit v1.2.3

