Fix table

danieljuhl · Feb 16, 2015 · 4a14a43 · 4a14a43
1 parent e195225
commit 4a14a43
Showing 1 changed file with 7 additions and 5 deletions.
diff --git a/docs/api/Location.md b/docs/api/Location.md
@@ -9,11 +9,13 @@ server, the location is the URL path that was used in the request.
 ReactRouter ships with several locations that make it convenient to
 use in many different scenarios. They are listed below.
 
-  | `HashLocation`      | Stores the current URL in `window.location.hash`. Use this if you need to support browsers that do not support the HTML5 history API |
-  | `HistoryLocation`   | Uses the HTML5 history API to store state in clean URLs |
-  | `RefreshLocation`   | A fallback for having clean URLs in browsers that do not support the HTML5 history API by updating `window.location` whenever the route changes. The router automatically falls back to this when you try to use `HistoryLocation` in old browsers |
-  | `StaticLocation`    | A location for stateless environments (like servers) where the URL is given once |
-  | `TestLocation`      | A location that allows you to easily stub out URL history when writing tests |
+Location            | Description
+------------------- | -----------
+`HashLocation`      | Stores the current URL in `window.location.hash`. Use this if you need to support browsers that don't support the HTML5 history API
+`HistoryLocation`   | Uses the HTML5 history API to store state in clean URLs
+`RefreshLocation`   | A fallback that uses clean URLs in browsers that do not support the HTML5 history API by updating `window.location` whenever the route changes. The router automatically falls back to this when you try to use `HistoryLocation` in old browsers
+`StaticLocation`    | A location for stateless environments (like servers) where the URL is given once
+`TestLocation`      | A location that allows you to easily stub out URL history when writing tests
 
 You can also supply the router with your own location implementation. The
 following methods must be implemented: