book/testnet: fix some typos

doc/src/testnet/airdrop.md

@@ -12,11 +12,11 @@ $ ./drk airdrop 42.69
 
 There is a limit of 100 for testnet airdrops currently.
 
-Note: you have wait some minutes between airdrops since they're
+Note: you have to wait some minutes between airdrops since they're
 rate-limited.
 
 On success, you should see a transaction ID. If successful,
-the airdrop transactions will how be in the consensus' mempool,
+the airdrop transactions will now be in the consensus' mempool,
 waiting for inclusion in the next block. Depending on the network,
 finalization of the blocks could take some time. You'll have to wait
 for this to happen.  If your `drk subscribe blocks` is running, then after
@@ -34,7 +34,7 @@ $ ./drk wallet --balance
 
 To make our life easier, we can create token ID aliases, so when we
 are performing transactions with them, we can use that instead of the
-full token ID. Multiple aliases per token ID is supported.
+full token ID. Multiple aliases per token ID are supported.
 
 Example addition:
 
@@ -42,7 +42,7 @@ Example addition:
 $ ./drk alias add {ALIAS} {TOKEN}
 ```
 
-So lets add the native token as `DARK` by executing:
+So let's add the native token as `DARK` by executing:
 
 ```
 $ ./drk alias add DARK 12ea8e3KVuBhmSnr29iV34Zd2RsD1MEeGk9xJhcipUqx
@@ -57,8 +57,8 @@ We can also list all our aliases using:
 $ ./drk alias show
 ```
 
-Note: this aliases are only local to your machine. When exchanging
-with other users, always verify that your aliases token IDs match.
+Note: these aliases are only local to your machine. When exchanging
+with other users, always verify that your aliases' token IDs match.
 
 # Minting tokens
 
@@ -81,14 +81,14 @@ You can list your mint authorities with:
 $ ./drk token list
 ```
 
-Now lets add those two token IDs to our aliases:
+Now let's add those two token IDs to our aliases:
 
 ```
 $ ./drk alias add WCKD {TOKEN1}
 $ ./drk alias add MLDY {TOKEN2}
 ```
 
-Now let's mint some tokens to ourself. First grab your wallet address,
+Now let's mint some tokens for ourselves. First grab your wallet address,
 and then create the token mint transaction, and finally - broadcast it:
 
 ```

doc/src/testnet/atomic-swap.md

@@ -1,7 +1,7 @@
 # Atomic Swaps
 
 In order to do an atomic swap with someone, you will first have to come
-to consensus on what tokens you wish to swap. For example purposes,
+to a consensus on what tokens you wish to swap. For example purposes,
 let's say you want to swap `40` `WCKD` (which is the balance you
 should have left over after doing the payment from the previous page)
 for your counterparty's `20` `MLDY`. For this tutorial the counterparty
@@ -30,7 +30,7 @@ $ ./drk otc join < half_swap > full_swap
 ```
 
 They will sign the full_swap file and send it back to you. Finally,
-to make the swap transaction valid, you need so sign it as well,
+to make the swap transaction valid, you need to sign it as well,
 and broadcast it:
 
 ```

doc/src/testnet/dao.md

@@ -15,7 +15,7 @@ You can see what these parameters mean with the `help` command.
 $ ./drk help dao create
 ```
 
-Lets create our DAO.
+Let's create our DAO.
 
 ```
 $ ./drk dao create 20 10 0.67 MLDY > dao.dat
@@ -70,7 +70,7 @@ $ ./drk dao balance 1
 
 ## Creating a proposal
 
-Now that the DAO has something in their treasury, we can create a
+Now that the DAO has something in its treasury, we can create a
 proposal to send it somewhere. Let's send 5 of the 10 tokens to our
 address (we can find that with `drk wallet --address`):
 

doc/src/testnet/node.md

@@ -35,7 +35,7 @@ Config file created in "~/.config/darkfi/darkfid_config.toml". Please review it
 ## Running
 
 Once that's in place, you can run it again and `darkfid` will start,
-create necessary keys for validation of blocks and transactions, and
+create the necessary keys for validation of blocks and transactions, and
 begin syncing the blockchain. Keep it running, and you should see a
 `Blockchain is synced!` message after some time.