style fixes/typos/etc from PR review

docs/app-architecture.md

@@ -47,4 +47,4 @@ See the following for more extensive documentation:
 - [Tendermint RPC Docs](https://tendermint.github.io/slate/)
 - [Tendermint in Production](https://github.com/tendermint/tendermint/pull/1618)
 - [Tendermint Basics](https://tendermint.readthedocs.io/en/master/using-tendermint.html)
-- [ABCI spec](https://github.com/tendermint/abci/blob/master/specification.rst)
+- [ABCI spec](https://github.com/tendermint/abci/blob/develop/specification.md)

docs/app-development.md

@@ -332,6 +332,7 @@ In go:
     }
 
 In Java:
+
     /*
      * all types come from protobuf definition
      */

docs/indexing-transactions.md

@@ -61,7 +61,7 @@ Note, there are a few predefined tags:
 
 Tendermint will throw a warning if you try to use any of the above keys.
 
-## Quering transactions
+## Querying transactions
 
 You can query the transaction results by calling `/tx_search` RPC
 endpoint:

docs/terraform-and-ansible.md

@@ -22,8 +22,10 @@ node testnet. The script more or less does everything described below.
 -   Create SSH keys (`ssh-keygen`)
 -   Set environment variables:
 
-    export DO_API_TOKEN="abcdef01234567890abcdef01234567890"
-    export SSH_KEY_FILE="$HOME/.ssh/id_rsa.pub"
+```    
+export DO_API_TOKEN="abcdef01234567890abcdef01234567890"
+export SSH_KEY_FILE="$HOME/.ssh/id_rsa.pub"
+```
 
 These will be used by both `terraform` and `ansible`.
 

docs/using-tendermint.md

@@ -203,9 +203,6 @@ can take on the order of a second. For a quick result, use
 `broadcast_tx_sync`, but the transaction will not be committed until
 later, and by that point its effect on the state may change.
 
-Note: see the Transactions => Formatting section for details about
-transaction formating.
-
 ## Tendermint Networks
 
 When `tendermint init` is run, both a `genesis.json` and
@@ -377,7 +374,7 @@ They should start making blocks, and will only continue to do so as long
 as both of them are online.
 
 To make a Tendermint network that can tolerate one of the validators
-failing, you need at least four validator nodes (> 2/3).
+failing, you need at least four validator nodes (e.g., 2/3).
 
 Updating validators in a live network is supported but must be
 explicitly programmed by the application developer. See the [application