Doc tweaks

Author: mjackson

docs/guides/basics/Histories.md

@@ -2,7 +2,7 @@
 
 React Router is built on [history](https://github.com/rackt/history).
 In a nutshell, a history knows how to listen to the browser's address
-bar for changes and parses the url into a `location` object that the
+bar for changes and parses the URL into a `location` object that the
 router can use to match routes and render the correct set of components.
 
 There are three types of histories you'll come across most often, but
@@ -23,42 +23,21 @@ const createBrowserHistory = require('history/lib/createBrowserHistory')
 ```
 
 ### `createHashHistory`
-This is the default history you'll get if you don't specify a history at
-all (i.e. `<Router>{/* your routes */}</Router>`). It uses the hash
-(`#`) portion of the url creating routes that look like
-`example.com/#/some/path`.
+This is the default history you'll get if you don't specify a history at all (i.e. `<Router>{/* your routes */}</Router>`). It uses the hash (`#`) portion of the URL creating routes that look like `example.com/#/some/path`.
 
 #### Should I use `createHashHistory`?
-Hash history is the default because it works without any setup on your
-server, and works in all evergreen browsers and IE8+. But, we don't
-recommend using it in production, every web app should aspire
-to use `createBrowserHistory`.
+Hash history is the default because it works without any setup on your server, and works in all evergreen browsers and IE8+. But, we don't recommend using it in production, every web app should aspire to use `createBrowserHistory`.
 
 #### What is that `?_k=ckuvup` junk in the URL?
-When a history transitions around your app with `pushState` or
-`replaceState`, it can store "location state" on the new location that
-doesn't show up in the URL, think of it a little bit like post data in
-an HTML form.
-
-The DOM API that hash history uses to transition around is simply
-`window.location.hash = newHash`, with no place to store location state.
-But, we want all histories to be able to use location state, so we shim
-it by creating a unique key for each location and then store that state
-in session storage. When the visitor clicks "back" and "forward" we now
-have a mechanism to restore the location state.
+When a history transitions around your app with `pushState` or `replaceState`, it can store "location state" on the new location that doesn't show up in the URL, think of it a little bit like post data in an HTML form.
+
+The DOM API that hash history uses to transition around is simply `window.location.hash = newHash`, with no place to store location state.  But, we want all histories to be able to use location state, so we shim it by creating a unique key for each location and then store that state in session storage. When the visitor clicks "back" and "forward" we now have a mechanism to restore the location state.
 
 ### `createBrowserHistory`
-Browser history is the recommended history for browser application with
-React Router. It uses the [History](https://developer.mozilla.org/en-US/docs/Web/API/History)
-API built into the browser to manipulate the url, creating real urls that
-look like `example.com/some/path`.
+Browser history is the recommended history for browser application with React Router. It uses the [History](https://developer.mozilla.org/en-US/docs/Web/API/History) API built into the browser to manipulate the URL, creating real URLs that look like `example.com/some/path`.
 
 #### Configuring Your Server
-Your server must be ready to handle real urls. When the app first loads
-at `/` it will probably work, but as the user navigates around and then
-hits refresh at `/accounts/23` your web server will get a request to
-`/accounts/23`. You will need it to handle that url and include your
-JavaScript application in the response.
+Your server must be ready to handle real URLs. When the app first loads at `/` it will probably work, but as the user navigates around and then hits refresh at `/accounts/23` your web server will get a request to `/accounts/23`. You will need it to handle that URL and include your JavaScript application in the response.
 
 A quick example with express:
 
@@ -82,31 +61,22 @@ console.log("server started on port " + port)
 ```
 
 #### IE8, IE9 Support
-We feature detect to see if we can use the browser's native `History`
-API, if not, any call to transition around the app will result in _a
-full page reload_, which allows you to build your app and have a better
-experience for newer browsers, but still support old ones.
+We feature detect to see if we can use the browser's native `window.history` API. If not, any call to transition around the app will result in _a full page reload_, which allows you to build your app and have a better experience for newer browsers, but still support old ones.
 
-You might wonder why we don't fall back to hash history; the problem is
-that urls become non-deterministic. If a visitor on hash history shares
-a url with a visitor on browser history, and then they share that back,
-we end up with a terrible cartesian product of infinite potential
-urls.
+You might wonder why we don't fall back to hash history; the problem is that URLs become non-deterministic. If a visitor on hash history shares a URL with a visitor on browser history, and then they share that back, we end up with a terrible cartesian product of infinite potential URLs.
 
 ### `createMemoryHistory`
-Memory history doesn't manipulate or read from the address bar. This is
-how we implement server rendering, its also useful for testing and other
-rendering environments (like React Native).
+Memory history doesn't manipulate or read from the address bar. This is how we implement server rendering. It's also useful for testing and other rendering environments (like React Native).
 
 ## Example implementation
 ```js
-import React from 'react';
-import createBrowserHistory from 'history/lib/createBrowserHistory';
-import {Router, Route, IndexRoute} from 'react-router';
-import App from '../components/App';
-import Home from '../components/Home';
-import About from '../components/About';
-import Features from '../components/Features';
+import React from 'react'
+import createBrowserHistory from 'history/lib/createBrowserHistory'
+import { Router, Route, IndexRoute } from 'react-router'
+import App from '../components/App'
+import Home from '../components/Home'
+import About from '../components/About'
+import Features from '../components/Features'
 
 React.render(
   <Router history={createBrowserHistory()}>
@@ -117,5 +87,5 @@ React.render(
     </Route>
   </Router>,
   document.getElementById('app')
-);
+)
 ```