From bb157014a9e0e359567f138ce957626461d82c3e Mon Sep 17 00:00:00 2001
From: Abu Shifrah <35174370+muaawiyahtucker@users.noreply.github.com>
Date: Thu, 10 Jul 2025 15:08:01 +0300
Subject: [PATCH] Edited the output to include the array brackets.

---
 08_1_Sending_a_Transaction_with_a_Locktime.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/08_1_Sending_a_Transaction_with_a_Locktime.md b/08_1_Sending_a_Transaction_with_a_Locktime.md
index 1db607c..beee885 100644
--- a/08_1_Sending_a_Transaction_with_a_Locktime.md
+++ b/08_1_Sending_a_Transaction_with_a_Locktime.md
@@ -42,7 +42,7 @@ Once you've figured out the current height, you can decide how far in the future
 
 Once you have figured out your locktime, all you need to do is write up a typical raw transaction, with a third variable for `locktime`:
 ```
-$ rawtxhex=$(bitcoin-cli -named createrawtransaction inputs='''[ { "txid": "'$utxo_txid'", "vout": '$utxo_vout' } ]''' outputs='''{ "'$recipient'": 0.001, "'$changeaddress'": 0.00095 }''' locktime=1774650)
+$ rawtxhex=$(bitcoin-cli -named createrawtransaction inputs='''[ { "txid": "'$utxo_txid'", "vout": '$utxo_vout' } ]''' outputs='''[{ "'$recipient'": 0.001, "'$changeaddress'": 0.00095 }]''' locktime=1774650)
 ```
 Note that this usage of `locktime` is under 500 million, which means that it defines a block height. In this case, it's just a few blocks past the current block height at the time of this writing, meant to exemplify how locktime works without sitting around for a long time to wait and see what happens.