From ca406ce081e89d4980622c16dfbfb2eb86231b1b Mon Sep 17 00:00:00 2001
From: namcios <82450345+namcios@users.noreply.github.com>
Date: Thu, 5 Aug 2021 12:08:31 -0300
Subject: [PATCH] Fix summary 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 39d96c8..b7722e9 100644
--- a/10_6_Spending_a_P2SH_Transaction.md
+++ b/10_6_Spending_a_P2SH_Transaction.md
@@ -33,7 +33,7 @@ $ bitcoin-cli -named signrawtransactionwithkey hexstring=$rawtxhex prevtxs='''[
 ```
 With any other sort of P2SH you're going to be including a different `redeemscript`, but otherwise the practice is exactly the same. The only difference is that after two chapters of work on Scripts you now understand what the `scriptPubKey` is and what the `redeemScript` is, so hopefully what were mysterious elements four chapters ago are now old hat.
 
-## Summary: Spending a Transaction with a Bitcoin Script
+## Summary: Spending a P2SH Transaction
 
 You already spent a P2SH back in Chapter 6, when you resent a multsig transaction the hard way, which required lining up the `scriptPubKey` and `redeemScript` information. Now you know that the `scriptPubKey` is a standardized P2SH locking script, while the `redeemScript` matches a hash in that locking script and that you need to be able to run it with the proper variables to receive a `True` result. But other than knowing more, there's nothing new in spending a P2SH transaction, because you already did it!