@@ -34,20 +34,20 @@ and it's available through `bitcoin-cli` (which is why it's the only
3434timelock covered in this section). A parallel method, which locks a
3535transaction with a relative time, is defined in [ BIP
363668] ( https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki )
37- and covered in [ §11 .3: Using CSV in
38- Scripts] ( 11_3_Using_CSV_in_Scripts .md) .
37+ and covered in [ §13 .3: Using CSV in
38+ Scripts] ( 13_3_Using_CSV_in_Scripts .md) .
3939
40- > Bitcoin Script further empowers both sorts of timelocks, allowing
41- for the locking of individual outputs instead of entire
42- transactions. Absolute timelocks do so with the Script opcode
40+ > Bitcoin Script and its "opcodes" further empowers both sorts of
41+ timelocks, allowing for the locking of individual outputs instead of
42+ entire transactions. Absolute timelocks do so with the Script opcode
4343OP_CHECKLOCKTIMEVERIFY, which is defined in [ BIP
444465] ( https://github.com/bitcoin/bips/blob/master/bip-0065.mediawiki )
45- and covered in [ §11 .2: Using CLTV in
46- Scripts] ( 11_2_Using_CLTV_in_Scripts .md) , while relative timelocks aare
45+ and covered in [ §13 .2: Using CLTV in
46+ Scripts] ( 13_2_Using_CLTV_in_Scripts .md) , while relative timelocks aare
4747linked to the Script opcode OP_CHECKSEQUENCEVERIFY, which is defined
4848in [ BIP
4949112] ( https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki )
50- and also covered in [ §11 .3] ( 11_3_Using_CSV_in_Scripts .md) .
50+ and also covered in [ §13 .3] ( 13_3_Using_CSV_in_Scripts .md) .
5151
5252## Create a Locktime Transaction
5353
0 commit comments