Fix: section 4 typos

04_2_Creating_a_Raw_Transaction.md

@@ -16,7 +16,7 @@ Here's the trick: _all of the UTXOs that you gather are spent in full!_ That mea
 
 ## List Your Unspent Transactions
 
-In order to create a new raw transaction, you must know what UTXOs you have on-hand to spent. You can determine this information with the `bitcoin-cli listunspent` command:
+In order to create a new raw transaction, you must know what UTXOs you have on-hand to spend. You can determine this information with the `bitcoin-cli listunspent` command:
 ```
 $ bitcoin-cli listunspent
 [

04_2__Interlude_Using_JQ.md

@@ -362,7 +362,7 @@ Whew!
 
 **Usage Example:** _Calculate the fee for a transaction._
 
-To figure out the complete transaction fee at this point just requires one more bit of math: determining how much money is going through the .vout. That's a simple use of JQ where you just use `awk` to sum up the `value` of all the `vout` information:
+Figuring out the complete transaction fee at this point just requires one more bit of math: determining how much money is going through the .vout. That's a simple use of JQ where you just use `awk` to sum up the `value` of all the `vout` information:
 ```
 $ bitcoin-cli decoderawtransaction $rawtxhex | jq -r '.vout  [] | .value' | awk '{s+=$1} END {print s}'
 1.045
@@ -386,7 +386,7 @@ For more JSON magic (and if any of this isn't clear), please read the [JSON Manu
 
 ## Make Some New Aliases
 
-JQ code can be a little unwieldly, so you should consider adding some longer and more interesting invocations to your ~/.bash_profile. 
+JQ code can be a little unwieldy, so you should consider adding some longer and more interesting invocations to your ~/.bash_profile. 
 
 Any time you're looking through a large mass of information in a JSON object output by a `bitcoin-cli` command, consider writing an alias to strip it down to just what you want to see.
 ```
@@ -435,5 +435,3 @@ You may also want to create an alias:
 ```
 alias btctxfee="~/txfee-calc.sh"
 ```
-
-

04_4_Sending_Coins_with_a_Raw_Transaction.md

@@ -84,7 +84,7 @@ Here's the example. Note the multiple inputs after the `inputs` arg and the mult
 ```
 $ rawtxhex2=$(bitcoin-cli -named createrawtransaction inputs='''[ { "txid": "'$utxo_txid_1'", "vout": '$utxo_vout_1' }, { "txid": "'$utxo_txid_2'", "vout": '$utxo_vout_2' } ]''' outputs='''{ "'$recipient'": 4.0, "'$changeaddress'": 1.8495 }''')
 ```
-We were _very_ careful figuring out our money math. These two UTXOs contain 5.85 BTC. After sending 4.0 BTC, we'll have 1.85 BTC left. We again chose .0005 BTC for the transaction fee. To accomodate that fee, we set our change to 1.8495 BTC. If we'd messed up our math and instead set our change to 1.7495 BTC, that additional .1 BTC would be lost. That's $100 gone to the miners! If we'd forgot to make change at all, then the whole 1.85 BTC ($2000!) would have disappeared. So, again, _be careful_. 
+We were _very_ careful figuring out our money math. These two UTXOs contain 5.85 BTC. After sending 4.0 BTC, we'll have 1.85 BTC left. We again chose .0005 BTC for the transaction fee. To accommodate that fee, we set our change to 1.8495 BTC. If we'd messed up our math and instead set our change to 1.7495 BTC, that additional .1 BTC would be lost. That's $100 gone to the miners! If we'd forgot to make change at all, then the whole 1.85 BTC ($2000!) would have disappeared. So, again, _be careful_. 
 
 Fortunately, we can triple-check with the `btctxfee` alias from the JQ Interlude:
 ```

04_4__Interlude_Using_Curl.md

@@ -41,7 +41,7 @@ And there's the `curl` command, at the end of the help screen! This somewhat len
 
 When you are working with `curl`, most of these arguments to `curl` will stay the same from command to command; only the `method` and `params` entries in the JSON array will typically change. However, you need to know how to fill in your username and your URL address in order to make it work in the first place!
 
-_Whenever you're unusure about how to curl an RPC command, just look at the bitcoin-cli help and go from there._
+_Whenever you're unsure about how to curl an RPC command, just look at the bitcoin-cli help and go from there._
 
 ### Know Your User Name
 
@@ -136,7 +136,7 @@ $ curl --user bitcoinrpc:73bd45ba60ab8f9ff9846b6404769487 --data-binary '{"jsonr
   "id": "curltest"
 }
 ```
-You'll see a bit of connectivity reporting as the data is downloaded, then when that data hits `jq`, everything will be output in a correctly indented form. (We'll be omiting the download information in future examples.)
+You'll see a bit of connectivity reporting as the data is downloaded, then when that data hits `jq`, everything will be output in a correctly indented form. (We'll be omitting the download information in future examples.)
 
 ## Manipulate Your Wallet
 
@@ -335,4 +335,3 @@ $ curl --user bitcoinrpc:73bd45ba60ab8f9ff9846b6404769487 --data-binary '{"jsonr
 Having finished this section, you may feel that accessing `bitcoind` via `curl` is very much like accessing it through `bitcoin-cli` ... but more cumbersome. And, you'd be right. `bitcoin-cli` has pretty complete RPC functionality, so anything that you do through `curl` you can probably do through `bitcoin-cli`.
 
 _What is the power of curl?_ Most obviously, `curl` takes out one level of indirection. Instead of working with `bitcoin-cli` which sends RPC commands to `bitcoind`, you're sending those RPC commands directly. This allows for more robust programming, because you don't have to worry about what unexpected things that `bitcoin-cli` might do or how it might change over time. However, you're also taking your first steps toward using a more comprehensive programming language than the poor options offered by a shell script. But for that, you'll need to use a `curl` library within a more familiar language like C. In other words, command-line `curl` was just the first step, the basis to better explain what you're doing as you move forward.
-