Made changes to ch05.asciidoc

ch05.asciidoc

@@ -352,34 +352,34 @@ Check the source code of the Bitcoin Core client (the reference implementation)
 The five standard types of transaction scripts are Pay-to-Public-Key-Hash (P2PKH), Public-Key, Multi-Signature (limited to 15 keys), Pay-to-Script-Hash (P2SH), and Data Output (OP_RETURN), which are described in more detail in the following sections.
 
 [[p2pkh]]
-==== Pay to Public Key Hash (P2PKH)
+==== Pay-to-Public-Key-Hash (P2PKH)
 
 The vast majority of transactions processed on the bitcoin network are Pay-to-Public-Key-Hash, also known as P2PKH transactions. These contain a locking script that encumbers the output with a public key hash, more commonly known as a bitcoin address. Transactions that pay a bitcoin address contain P2PKH scripts. An output locked by a P2PKH script can be unlocked (spent) by presenting a public key and a digital signature created by the corresponding private key. 
 
-For example, let's look at Alice's payment to Bob's Cafe again. Alice made a payment of 0.015 bitcoin to the Cafe's bitcoin address. That transaction output would have a locking script of the form:
+For example, let's look at Alice's payment to Bob's Cafe again. Alice made a payment of 0.015 bitcoin to the cafe's bitcoin address. That transaction output would have a locking script of the form:
 
 ----
 OP_DUP OP_HASH160 <Cafe Public Key Hash> OP_EQUAL OP_CHECKSIG
 ----
 
-The +Cafe Public Key Hash+ is equivalent to the bitcoin address of the Cafe, without the Base58Check encoding. Most applications would show the Public Key Hash in hexadecimal encoding and not the familiar bitcoin address Base58Check format that begins with a "1". 
+The +Cafe Public Key Hash+ is equivalent to the bitcoin address of the cafe, without the Base58Check encoding. Most applications would show the _public key hash_ in hexadecimal encoding and not the familiar bitcoin address Base58Check format that begins with a "1". 
 
-The locking script above can be satisfied with an unlocking script of the form:
+The preceding locking script can be satisfied with an unlocking script of the form:
 
 ----
 <Cafe Signature> <Cafe Public Key>
 ----
 
-The two scripts together would form the combined validation script below:
+The two scripts together would form the following combined validation script:
 
 ----
 <Cafe Signature> <Cafe Public Key> OP_DUP OP_HASH160 \
 <Cafe Public Key Hash> OP_EQUAL OP_CHECKSIG
 ----
 
-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 which corresponds to the public key hash set as an encumbrance. 
+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. 
 
-Here's a step-by-step execution of the combined script, which will prove this is a valid transaction:
+<<P2PubKHash1>> and <<P2PubKHash2>> show (in two parts) a step-by-step execution of the combined script, which will prove this is a valid transaction.
 
 [[P2PubKHash1]]
 .Evaluating a script for a Pay-to-Public-Key-Hash transaction (Part 1 of 2)