more deprecation links

Author: ryanflorence

modules/Router.js

@@ -65,7 +65,7 @@ const Router = React.createClass({
     const { parseQueryString, stringifyQuery } = this.props
     warning(
       !(parseQueryString || stringifyQuery),
-      '`parseQueryString` and `stringifyQuery` are deprecated, please create a custom `history` as described in https://github.com/rackt/react-router/blob/v1.1.0/CHANGES.md#v110'
+      '`parseQueryString` and `stringifyQuery` are deprecated. Please create a custom history. See http://bit.ly/1NRMoPX for details.'
     )
 
     if (isDeprecatedHistory(history)) {
@@ -92,7 +92,7 @@ const Router = React.createClass({
 
     let createHistory
     if (history) {
-      warning(false, 'It appears you have provided a deprecated history object to `<Router/>`, please use a history provided by React Router with `import { browserHistory } from \'react-router\'` or `import { hashHistory } from \'react-router\'`. If you are using a custom, valid history please set `history.__v2_compatible__ = true`.')
+      warning(false, 'It appears you have provided a deprecated history object to `<Router/>`, please use a history provided by React Router with `import { browserHistory } from \'react-router\'` or `import { hashHistory } from \'react-router\'`. If you are using a custom, valid history please set `history.__v2_compatible__ = true`. See http://bit.ly/1Pxrl7E')
       createHistory = () => history
     } else {
       warning(false, 'the default hash history is deprecated; use the `hashHistory` singleton instead')

upgrade-guides/v2.0.0.md

@@ -50,17 +50,6 @@ import { browserHistory } from 'react-router'
 <Router history={browserHistory}/>
 ```
 
-## New Router render prop (`RoutingContext` prop replacement)
-
-You can now pass a `render` prop to `Router` for it to use for rendering. This allows you to create "middleware components" that participate in routing. Its critical for integrations with libraries like Relay, Redux, Resolver, Transmit, Async Props, etc.
-
-```js
-// the default is basically this:
-<Router render={props => <RouterContext {...props}/>}/>
-```
-
-`RoutingContext` was undocumented and therefore has no backwards compatibility.
-
 ## Changes to provided context and Mixins
 
 Only an object named `router` is added to context. Accessing `context.history`, `context.location`, and `context.route` are all deprecated.
@@ -270,3 +259,15 @@ const appHistory = useRouterHistory({
 <Router history={appHistory}/>
 ```
 
+## RoutingContext -> Router render prop
+
+You can now pass a `render` prop to `Router` for it to use for rendering. This allows you to create "middleware components" that participate in routing. Its critical for integrations with libraries like Relay, Redux, Resolver, Transmit, Async Props, etc.
+
+```js
+// the default is basically this:
+<Router render={props => <RouterContext {...props}/>}/>
+```
+
+`RoutingContext` was undocumented and therefore has no backwards compatibility.
+
+