From 58a40b8559906f8335db96a32d0307bdf74bb54c Mon Sep 17 00:00:00 2001
From: namcios <82450345+namcios@users.noreply.github.com>
Date: Thu, 5 Aug 2021 12:06:08 -0300
Subject: [PATCH] Update 6_3 title

---
 10_6_Spending_a_P2SH_Transaction.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/10_6_Spending_a_P2SH_Transaction.md b/10_6_Spending_a_P2SH_Transaction.md
index 1a75de6..39d96c8 100644
--- a/10_6_Spending_a_P2SH_Transaction.md
+++ b/10_6_Spending_a_P2SH_Transaction.md
@@ -8,7 +8,7 @@ As we saw in [§6.2: Spending a Transaction with a Multisig](06_2_Spending_a_Tra
 
 ### Collect Your Variables
 
-Because P2SH addresses other than the special multisig and nested Segwit addresses aren't integrated into `bitcoin-cli` there will be no short-cuts for P2SH spending like you saw in [§6.3: Sending an Automated Multisig](6_3_Sending_an_Automated_Multisig.md). You're going to need to collect all the more complex variables on your own!
+Because P2SH addresses other than the special multisig and nested Segwit addresses aren't integrated into `bitcoin-cli` there will be no short-cuts for P2SH spending like you saw in [§6.3: Sending & Spending an Automated Multisig](6_3_Sending_an_Automated_Multisig.md). You're going to need to collect all the more complex variables on your own!
 
 This means that you need to collect: