diff --git a/ch05.asciidoc b/ch05.asciidoc
index 9e4ee9eb..496e6c59 100644
--- a/ch05.asciidoc
+++ b/ch05.asciidoc
@@ -580,7 +580,7 @@ As of version 0.9.2 of the Bitcoin Core client, P2SH transactions can contain an
 
 Note that you are not able to put a P2SH inside a P2SH redeem script, because the P2SH specification is not recursive. You are also still not be able to use +OP_RETURN+ in a redeem script because +OP_RETURN+ cannot be redeemed by definition.
 
-Note that because the redeem script is not presented to the network until you attempt to spend a P2SH output, if you lock an output with the hash of an invalid transaction it will be processed regardless. However, you will not be able to spend it because the spending transaction, which includes the redeem script, will not be accepted because it is an invalid script. This creates a risk, because you can lock bitcoin in a P2SH which cannot be spent later. The network will accept the P2SH encumbrance even if it corresponds to an invalid redeem script, because the script hash gives no indication of the script it represents. 
+Note that because the redeem script is not presented to the network until you attempt to spend a P2SH output, if you lock an output with the hash of an invalid transaction it will be processed regardless. However, you will not be able to spend it because the spending transaction, which includes the redeem script, will not be accepted because it is an invalid script. This creates a risk, because you can lock bitcoin in a P2SH that cannot be spent later. The network will accept the P2SH encumbrance even if it corresponds to an invalid redeem script, because the script hash gives no indication of the script it represents. 
 
 [WARNING]
 ====