Merge pull request reduxjs#646 from existentialism/typo

Fix minor docs typos

Author: gaearon

docs/basics/UsageWithReact.md

@@ -56,7 +56,7 @@ In this todo app, we will only have a single “smart” component at the top of
 
 Remember how we [designed the shape of the root state object](Reducers.md)? It’s time we design the UI hierarchy to match it. This is not a Redux-specific task. [Thinking in React](https://facebook.github.io/react/docs/thinking-in-react.html) is a great tutorial that explains the process.
 
-Our design brief is simple. We want to show a list of todo items. On click, a todo item is crossed out as completed. We want to show a field where the user may add a new todo. In the footer, we want to show a toggle to show all / only completed / only incompleted todos.
+Our design brief is simple. We want to show a list of todo items. On click, a todo item is crossed out as completed. We want to show a field where the user may add a new todo. In the footer, we want to show a toggle to show all / only completed / only incomplete todos.
 
 I see the following components (and their props) emerge from this brief:
 

docs/recipes/ServerRendering.md

@@ -232,7 +232,7 @@ export function fetchCounter(callback) {
 
 Again, this is just a mock API, so we use `setTimeout` to simulate a network request that takes 500 milliseconds to respond (this should be much faster with a real world API). We pass in a callback that returns a random number asynchronously. If you’re using a Promise-based API client, then you would issue this callback in your `then` handler.
 
-On the server side, we simply wrap our existing code in the `fetchCounter` and recieve the result in the callback:
+On the server side, we simply wrap our existing code in the `fetchCounter` and receive the result in the callback:
 
 #### `server.js`