Made changes to ch03.asciidoc

ch03.asciidoc

@@ -1212,12 +1212,12 @@ include::code/pycoin_example.py[]
 ----
 ====
 
-For many examples using the command-line utilities +ku+ and +tx+, see [XREF-appdx_pycoin].
+For many examples using the command-line utilities ku and tx, see [XREF-appdx_pycoin].
 
 ==== btcd
-btcd is a full node bitcoin implementation written in Go. It currently properly downloads, validates, and serves the block chain using the exact rules (including bugs) for block acceptance as the reference implementation, bitcoind. It also properly relays newly mined blocks, maintains a transaction pool, and relays individual transactions that have not yet made it into a block. It ensures all individual transactions admitted to the pool follow the rules required into the block chain and also includes the vast majority of the more strict checks which filter transactions based on miner requirements ("standard" transactions).
+btcd is a full-node bitcoin implementation written in Go. It currently properly downloads, validates, and serves the blockchain using the exact rules (including bugs) for block acceptance as the reference implementation, bitcoind. It also properly relays newly mined blocks, maintains a transaction pool, and relays individual transactions that have not yet made it into a block. It ensures all individual transactions admitted to the pool follow the rules required into the block chain and also includes the vast majority of the more strict checks that filter transactions based on miner requirements ("standard" transactions).
 
-One key difference between btcd and bitcoind is that btcd does not include wallet functionality and this was a very intentional design decision. This means you can't actually make or receive payments directly with btcd. That functionality is provided by the btcwallet and btcgui projects which are both under active development. Other notable differences are btcd support for both HTTP POST requests (such as bitcoind) and the preferred Websockets, and btcd's RPC connections are TLS-enabled by default.
+One key difference between btcd and bitcoind is that btcd does not include wallet functionality, and this was a very intentional design decision. This means you can't actually make or receive payments directly with btcd. That functionality is provided by the btcwallet and btcgui projects, which are both under active development. Other notable differences are btcd support for both HTTP POST requests (such as bitcoind) and the preferred Websockets, and btcd's RPC connections are TLS-enabled by default.
 
 ===== Installing btcd
 
@@ -1237,23 +1237,23 @@ $ go get -u -v github.com/conformal/btcd/...
 
 ===== Controlling btcd
 
-btcd has a number of configuration options, which can be viewed by running: 
+btcd has a number of configuration options, which you can view by running: 
 
 [source,bash]
 ----
 $ btcd --help
 ----
 
-btcd comes prepacked with some goodies such as btcctl, a command line utility that can be used to both control and query btcd via RPC. btcd does not enable its RPC server by default; you must configure at minimum both an RPC username and password:
+btcd comes prepacked with some goodies such as btcctl, which is a command-line utility that can be used to both control and query btcd via RPC. btcd does not enable its RPC server by default; you must configure at minimum both an RPC username and password in the following configuration files:
 
-* btcd.conf configuration file
+* _btcd.conf_:
 [source,ini]
 ----
 [Application Options]
 rpcuser=myuser
 rpcpass=SomeDecentp4ssw0rd
 ----
-* btcctl.conf configuration file
+* _btcctl.conf_:
 [source,ini]
 ----
 [Application Options]