Fixing assorted typos (#112)

- Closes #105
- Thanks to @lizblockstack for the catches

Signed-off-by: Mary Anthony <mary@blockstack.com>

_core/naming/architecture.md

@@ -46,7 +46,7 @@ Figure 1: BNS architecture overview.  Clients talk to the BNS API module to
 resolve names, and generate and send blockchain transactions to register and
 modify names.   The API module talks to the indexer module and gives clients
 a stable, Web-accessible interface for resolving names.  The indexer module reads
-the blochchain via a blockchain peer, over the blockchain's peer network.
+the blockchain via a blockchain peer, over the blockchain's peer network.
 
 Blockstack Core currently implements the API module and indexer module as separate
 daemons (`blockstack api` and `blockstack-core`, respectively).  However, this

_core/naming/comparison.md

@@ -76,7 +76,7 @@ geared towards providing programmatic control over names with Turing-complete
 on-chain resolvers.
 
 BNS has a fundamentally different relationship with blockchains than ENS.
-WHereas ENS tries to use on-chain logic as much as possible, BNS
+Whereas ENS tries to use on-chain logic as much as possible, BNS
 tries to use the blockchain as little as possible.  BNS only uses it to store a
 database log for name operations (which are interpreted with an off-chain BNS
 node like Blockstack Core).  BNS name state and BNS subdomains reside entirely

_core/naming/search.md

@@ -15,7 +15,7 @@ Currently there are two types of indexes to handle search queries:
 * Substring search on usernames, full names, twitter_handle (powered by MongoDB)
 * Raw Lucene index which handles searching extended data e.g., bio.
 
-Search will currently return upto a max of 20 results (can be less depending on the query)
+Search will currently return up to a max of 20 results (can be less depending on the query)
 with data that follows structure of [blockstack IDs](https://github.com/blockstack/blockstack):
 
 In early 2017, the search subsystem was ported over to the new API system, where support for search is provided by the endpoint:

_develop/zero_to_dapp_2.md

@@ -322,6 +322,6 @@ blockstack backend. You also set up a typical development environment for
 developing a Blockstack web application.  Finally, you started and ran the
 Animal Kingdom application locally.
 
-In the next section, you explorer the application code and learn which recorded
+In the next section, you explore the application code and learn which recorded
 elements in a DApp make it eligible for App Mining. Continue to [Zero-to-DApp, 3
 of 4](zero_to_dapp_3.html).

_develop/zero_to_dapp_3.md

@@ -38,7 +38,7 @@ The Animal Kingdom application has two major components, React and Blockstack.
 React is used to build all the web components and interactions. You could
 replace React with any framework that you like; Blockstack is web framework
 agnostic. This section does not explain the React in any detail; The discussion
-focuses on the Blockstack Javascript library the DApp instead.
+focuses on the Blockstack Javascript library code instead.
 
 The <a href="https://blockstack.github.io/blockstack.js/"
 target="\_blank">Blockstack Javascript library is all a developer needs to