From f6d32af20a90d52c7ef58cdb043f8de5db9174f1 Mon Sep 17 00:00:00 2001 From: "myarbrough@oreilly.com" Date: Tue, 25 Nov 2014 12:57:41 -0800 Subject: [PATCH] Made changes to ch05.asciidoc --- ch05.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/ch05.asciidoc b/ch05.asciidoc index 5886945e..da82aef8 100644 --- a/ch05.asciidoc +++ b/ch05.asciidoc @@ -376,7 +376,7 @@ The two scripts together would form the following combined validation script: When executed, this combined script will evaluate to TRUE if, and only if, the unlocking script matches the conditions set by the locking script. In other words, the result will be TRUE if the unlocking script has a valid signature from the cafe's private key that corresponds to the public key hash set as an encumbrance. -<> and <> show (in two parts) a step-by-step execution of the combined script, which will prove this is a valid transaction.(((range="endofrange", startref="ix_ch05-asciidoc16")))(((range="endofrange", startref="ix_ch05-asciidoc15"))) +Figures pass:[] and pass:[] show (in two parts) a step-by-step execution of the combined script, which will prove this is a valid transaction.(((range="endofrange", startref="ix_ch05-asciidoc16")))(((range="endofrange", startref="ix_ch05-asciidoc15"))) [[P2PubKHash1]] .Evaluating a script for a P2PKH transaction (Part 1 of 2)