diff --git a/ch04_keys.adoc b/ch04_keys.adoc
index be604b31..722f7b8b 100644
--- a/ch04_keys.adoc
+++ b/ch04_keys.adoc
@@ -890,7 +890,7 @@ communicate his public key to her.  Like that problem, where
 public keys can be fairly large, the constraints Bob uses can also be
 quite large—potentially thousands of bytes.  That's not only thousands
 of bytes that need to be communicated to Alice, but thousands of bytes
-for which she needs to pay transaction fees every time she wants to spend money to Bob.  However, the solution of using hash functions to create
+for which she needs to pay transaction fees every time she wants to send money to Bob.  However, the solution of using hash functions to create
 small commitments to large amounts of data also applies here.
 </p>
 ++++
diff --git a/ch05_wallets.adoc b/ch05_wallets.adoc
index 7a2ddc54..91d9fd68 100644
--- a/ch05_wallets.adoc
+++ b/ch05_wallets.adoc
@@ -218,7 +218,7 @@ network.
 
 Public child key derivation can produce a linear sequence of keys
 similar to the previously seen <<Type1_wallet>>, but modern wallet
-applications use one more trick to provide a tree of keys instead a
+applications use one more trick to provide a tree of keys instead of a
 single sequence, as described in the((("wallets", "key generation", "public child key derivation", startref="wallet-keygen-public-child")))((("key generation", "public child key derivation", startref="keygen-public-child")))((("public child key derivation", startref="public-child-derive")))((("child key pair derivation", startref="child-key-pair"))) following section.
 
 [[hd_wallets]]