From a33ceaadcce9fe4394f82ef21075b0eccae436ac Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Wed, 24 May 2017 14:34:58 -0700 Subject: [PATCH] Update 9_2_Using_CLTV_in_Scripts.md --- 9_2_Using_CLTV_in_Scripts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/9_2_Using_CLTV_in_Scripts.md b/9_2_Using_CLTV_in_Scripts.md index 5eded94..9921e09 100644 --- a/9_2_Using_CLTV_in_Scripts.md +++ b/9_2_Using_CLTV_in_Scripts.md @@ -101,7 +101,7 @@ We're not going to continuously show how all Bitcoin Scripts are abstracted into In order to spend a UTXO that is locked with a CLTV, you must set `nLockTime` on your new transaction. Usually, you just want to set it to the present time or the present block, as appropriate. As long the CLTV time or blockheight is in the past, and as long as you supply any other data required by the unlocking script, you'll be able to process the UTXO. -In the case of the above example, the following unlocking script would suffice, provided that `nLockTime` was set to somewhere in advance of the date, and provided it was indeed at least : +In the case of the above example, the following unlocking script would suffice, provided that `nLockTime` was set to somewhere in advance of the `` date, and provided it was indeed at least ``: ``` ``` @@ -113,7 +113,7 @@ To run the Script, you would first concatenate the unlocking and locking scripts Script: OP_CHECKLOCKTIMEVERIFY OP_DROP OP_DUP OP_HASH160 OP_EQUALVERIFY OP_CHECKSIG Stack: [ ] ``` -The sthree constants would be pushed onto the stack: +The three constants would be pushed onto the stack: ``` Script: OP_CHECKLOCKTIMEVERIFY OP_DROP OP_DUP OP_HASH160 OP_EQUALVERIFY OP_CHECKSIG Stack: [ ]