Updates documentation of Switch, NavLink, Route (remix-run#5136)

* Updates documentation of Switch, missing prop location

* Updates documentation of NavLink, missing prop location

* Updates documentation of Route, missing prop location

* Updates documentation of Switch, location property override for matching child

* Updates documentation of Switch, NavLink, Route: reduce verbosity

* Updates documentation of NavLink: fix broken link

Author: SHIRSH ZIBBU

packages/react-router-dom/docs/api/NavLink.md

@@ -74,3 +74,8 @@ const oddEvent = (match, location) => {
   isActive={oddEvent}
 >Event 123</NavLink>
 ```
+
+## location: object
+
+The [`isActive`](#isactive-func) compares the current history location (usually the current browser URL).
+To compare to a different location, a [`location`](../../../react-router/docs/api/location.md) can be passed.

packages/react-router/docs/api/Route.md

@@ -148,10 +148,10 @@ When `true`, will only match if the path matches the `location.pathname` _exactl
 <Route exact path="/one" component={About}/>
 ```
 
-| path | location.pathname | exact | matches? |   
-| --- | --- | --- | --- |   
-| `/one`  | `/one/two`  | `true` | no |   
-| `/one`  | `/one/two`  | `false` | yes |   
+| path | location.pathname | exact | matches? |
+| --- | --- | --- | --- |
+| `/one`  | `/one/two`  | `true` | no |
+| `/one`  | `/one/two`  | `false` | yes |
 
 ## strict: bool
 
@@ -178,3 +178,12 @@ When `true`, a `path` that has a trailing slash will only match a `location.path
 | `/one` | `/one` | yes |
 | `/one` | `/one/` | no |
 | `/one` | `/one/two` | no |
+
+## location: object
+
+A `<Route>` element tries to match its `path` to the current history location (usually the current browser URL).
+However, a [`location`](location.md) with a different `pathname` can also be passed for matching.
+
+This is useful in cases when you need to match a `<Route>` to a location other than the current history location, as shown in the [Animated Transitions](https://reacttraining.com/react-router/web/example/animated-transitions) example.
+
+If a `<Route>` element is wrapped in a `<Switch>` and matches the location passed to the `<Switch>` (or the current history location), then the `location` prop passed to `<Route>` will be overridden by the one used by the `<Switch>` (given [here](https://github.com/ReactTraining/react-router/blob/master/packages/react-router/modules/Switch.js#L51)).

packages/react-router/docs/api/Switch.md

@@ -48,15 +48,22 @@ This is also useful for animated transitions since the matched `<Route>` is rend
       a bit more cumbersome to work out */}
 </Fade>
 ```
+## Switch props
 
-## children: node
+### location: object
+
+A [`location`](location.md) object to be used for matching children elements instead of the current history location (usually the current browser URL).
+
+### children: node
 
 All children of a `<Switch>` should be `<Route>` or `<Redirect>` elements. Only the first child to match the current location will be rendered.
 
 `<Route>` elements are matched using their `path` prop and `<Redirect>` elements are matched using their `from` prop. A `<Route>` with no `path` prop or a `<Redirect>` with no `from` prop will always match the current location.
 
 When you include a `<Redirect>` in a `<Switch>`, it can use any of the `<Route>`'s location matching props: `path`, `exact`, and `strict`. `from` is just an alias for the `path` prop.
 
+If a `location` prop is given to the `<Switch>`, it will override the `location` prop on the matching child element.
+
 ```js
 <Switch>
   <Route exact path="/" component={Home}/>