From 481f288f9e8891c58230bb6f8cd9bae71dc3bf19 Mon Sep 17 00:00:00 2001
From: Ryan Shea <ryan@shea.io>
Date: Wed, 12 Nov 2014 09:15:29 -0500
Subject: Fix a few minor typos in bip 0065

---
 bip-0065.mediawiki | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

(limited to 'bip-0065.mediawiki')

diff --git a/bip-0065.mediawiki b/bip-0065.mediawiki
index 9574374..fb22ace 100644
--- a/bip-0065.mediawiki
+++ b/bip-0065.mediawiki
@@ -16,9 +16,9 @@ some point in the future.
 
 ==Summary==
 
-CHECKLOCKTIMEVERIFY re-defines the existing NOP2 opcode. When executed it
+CHECKLOCKTIMEVERIFY redefines the existing NOP2 opcode. When executed it
 compares the top item on the stack to the nLockTime field of the transaction
-containing the scriptSig. If that top stack item is greater than the transation
+containing the scriptSig. If that top stack item is greater than the transaction
 nLockTime the script fails immediately, otherwise script evaluation continues
 as though a NOP was executed.
 
@@ -41,8 +41,8 @@ nLockTime field proves that should the receiver vanish the sender is guaranteed
 to get all their escrowed funds back when the nLockTime is reached.
 
 However the nLockTime field is insufficient if you wish to prove that
-transaction output ''can-not'' be spent until some time in the future, as there
-is no way to prove that the secret keys corresponding to the pubkeys controling
+transaction output ''cannot'' be spent until some time in the future, as there
+is no way to prove that the secret keys corresponding to the pubkeys controlling
 the funds have not been used to create a valid signature.
 
 
-- 
cgit v1.2.3

