diff --git a/ch10_network.adoc b/ch10_network.adoc
index 10d82694..378a179f 100644
--- a/ch10_network.adoc
+++ b/ch10_network.adoc
@@ -1021,7 +1021,7 @@ block.  In other words, the output script being spent.
 
 This had several advantages.  First, it meant that wallets didn't need
 to track outpoints; they could instead just scan for the
-output scripts to which they expected to receive money. Second, any time a
+output scripts in which they expected to send money. Second, any time a
 later transaction in a block spends the output of an earlier
 transaction in the same block, they'll both reference the same
 output script.  More than one reference to the same output script is
diff --git a/ch11_blockchain.adoc b/ch11_blockchain.adoc
index 8ff7cd97..15d3c94b 100644
--- a/ch11_blockchain.adoc
+++ b/ch11_blockchain.adoc
@@ -527,7 +527,7 @@ The largest possible block can hold almost 16,000 transactions in 4,000,000
 bytes, but proving any particular one of those 16,000 transactions
 is a part of that block only requires a copy of the transaction, a copy
 of the 80-byte block header, and 448 bytes for the merkle proof.  That
-makes the largest possible proof almost 10,000 times smaller than the
+makes the largest possible proof almost 5,000 times smaller than the
 largest possible Bitcoin block.
 
 === Merkle Trees and Lightweight Clients