From 8f506d8e2759fcf6970d0085fc70e702ace182ca Mon Sep 17 00:00:00 2001
From: Luis Miguel <ktecho@ktecho.com>
Date: Tue, 6 Jun 2023 15:47:37 +0200
Subject: Typos in bip-0119

---
 bip-0119.mediawiki | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'bip-0119.mediawiki')

diff --git a/bip-0119.mediawiki b/bip-0119.mediawiki
index aa226d0..86defa7 100644
--- a/bip-0119.mediawiki
+++ b/bip-0119.mediawiki
@@ -61,7 +61,7 @@ references.
 ==Detailed Specification==
 
 The below code is the main logic for verifying CHECKTEMPLATEVERIFY, described
-in pythonic pseduocode. The canonical specification for the semantics of
+in pythonic pseudocode. The canonical specification for the semantics of
 OP_CHECKTEMPLATEVERIFY as implemented in C++ in the context of Bitcoin Core can
 be seen in the reference implementation.
 
@@ -225,12 +225,12 @@ A recent commit hash in that PR including tests and vectors can be found here ht
 Once the PR is merged, this BIP should be updated to point to the specific code released.
 
 Test vectors are available in [/bip-0119/vectors the bip-0119/vectors
-directory] for checking compatibility with the refrence implementation and BIP.
+directory] for checking compatibility with the reference implementation and BIP.
 
 ==Rationale==
 
 The goal of CHECKTEMPLATEVERIFY is to be minimal impact on the existing codebase -- in the
-future, as we become aware of more complex but shown to be safe use cases new template types can be added.
+future, as we become aware of more complex but shown to be safe use cases, new template types can be added.
 
 Below we'll discuss the rules one-by-one:
 
@@ -250,7 +250,7 @@ Were these values not committed, it would be possible to delay the spending of
 an output arbitrarily as well as possible to change the TXID.
 
 Committing these values, rather than restricting them to specific values, is
-more flexible as it permits users of CHECKTEMPLATEVERIFY the set the version and
+more flexible as it permits users of CHECKTEMPLATEVERIFY to set the version and
 locktime as they please.
 
 =====Committing to the ScriptSigs Hash=====
@@ -258,7 +258,7 @@ locktime as they please.
 The scriptsig in a segwit transaction must be exactly empty, unless it is a P2SH
 segwit transaction in which case it must be only the exact redeemscript. P2SH is incompatible
 (unless the P2SH hash is broken) with CHECKTEMPLATEVERIFY because the template hash must commit
-to the  ScriptSig, which must contain the redeemscript, which is a hash cycle.
+to the ScriptSig, which must contain the redeemscript, which is a hash cycle.
 
 To prevent malleability when not using a segwit input, we also commit to the
 scriptsig. This makes it possible to use a 2 input CHECKTEMPLATEVERIFY with a legacy pre-signed
-- 
cgit v1.2.3

