From 4d0570980ba1654154f4ec8162855d0c67565200 Mon Sep 17 00:00:00 2001
From: "myarbrough@oreilly.com" <myarbrough@oreilly.com>
Date: Tue, 18 Nov 2014 08:05:58 -0800
Subject: [PATCH] Made changes to ch05.asciidoc

---
 ch05.asciidoc | 18 ++++--------------
 1 file changed, 4 insertions(+), 14 deletions(-)

diff --git a/ch05.asciidoc b/ch05.asciidoc
index 8a9b20be..c06dd194 100644
--- a/ch05.asciidoc
+++ b/ch05.asciidoc
@@ -511,26 +511,16 @@ As you can see from the tables, with P2SH the complex script that details the co
 Let's look at Mohammed's company, the complex multi-signature script, and the resulting P2SH scripts. 
 
 First, the multi-signature script that Mohammed's company uses for all incoming payments from customers:
+
 ----
-2 <Mohammed's Public Key> <Partner1 Public Key> <Partner2 Public Key> 
-<Partner3 Public Key> <Attorney Public Key> 5 OP_CHECKMULTISIG
+2 <Mohammed's Public Key> <Partner1 Public Key> <Partner2 Public Key> <Partner3 Public Key> <Attorney Public Key> 5 OP_CHECKMULTISIG
 ----
 
 If the placeholders are replaced by actual public keys (shown here as 520-bit numbers starting with 04) you can see that this script becomes very long:
+
 ----
 2 
-04C16B8698A9ABF84250A7C3EA7EEDEF9897D1C8C6ADF47F06CF73370
-D74DCCA01CDCA79DCC5C395D7EEC6984D83F1F50C900A24DD47F569FD
-4193AF5DE762C58704A2192968D8655D6A935BEAF2CA23E3FB87A3495
-E7AF308EDF08DAC3C1FCBFC2C75B4B0F4D0B1B70CD2423657738C0C2B
-1D5CE65C97D78D0E34224858008E8B49047E63248B75DB7379BE9CDA8
-CE5751D16485F431E46117B9D0C1837C9D5737812F393DA7D4420D7E1
-A9162F0279CFC10F1E8E8F3020DECDBC3C0DD389D99779650421D65CB
-D7149B255382ED7F78E946580657EE6FDA162A187543A9D85BAAA93A4
-AB3A8F044DADA618D087227440645ABE8A35DA8C5B73997AD343BE5C2
-AFD94A5043752580AFA1ECED3C68D446BCAB69AC0BA7DF50D56231BE0
-AABF1FDEEC78A6A45E394BA29A1EDF518C022DD618DA774D207D137AA
-B59E0B000EB7ED238F4D800 5 OP_CHECKMULTISIG
+04C16B8698A9ABF84250A7C3EA7EEDEF9897D1C8C6ADF47F06CF73370D74DCCA01CDCA79DCC5C395D7EEC6984D83F1F50C900A24DD47F569FD4193AF5DE762C58704A2192968D8655D6A935BEAF2CA23E3FB87A3495E7AF308EDF08DAC3C1FCBFC2C75B4B0F4D0B1B70CD2423657738C0C2B1D5CE65C97D78D0E34224858008E8B49047E63248B75DB7379BE9CDA8CE5751D16485F431E46117B9D0C1837C9D5737812F393DA7D4420D7E1A9162F0279CFC10F1E8E8F3020DECDBC3C0DD389D99779650421D65CBD7149B255382ED7F78E946580657EE6FDA162A187543A9D85BAAA93A4AB3A8F044DADA618D087227440645ABE8A35DA8C5B73997AD343BE5C2AFD94A5043752580AFA1ECED3C68D446BCAB69AC0BA7DF50D56231BE0AABF1FDEEC78A6A45E394BA29A1EDF518C022DD618DA774D207D137AAB59E0B000EB7ED238F4D800 5 OP_CHECKMULTISIG
 ----
 
 This entire script can instead be represented by a 20-byte cryptographic hash, by first applying the SHA256 hashing algorithm and then applying the RIPEMD160 algorithm on the result. The 20-byte hash of the preceding script is: