Missed a couple rackts. Derackted.

Author: timdorr

scripts/release.sh

@@ -47,7 +47,7 @@ node scripts/build.js
 # This is a workaround for a nasty npm bug. :'(
 # First, we need to uninstall the history package so
 # it's not included in the react-router npm package.
-# https://github.com/rackt/react-router/issues/2195
+# https://github.com/reactjs/react-router/issues/2195
 # https://github.com/npm/npm/issues/9894
 rm -rf node_modules/history
 

upgrade-guides/v1.0.0.md

@@ -52,7 +52,7 @@ render(<Router routes={routes}/>, el)
 ### Locations
 
 Locations are now called histories (that emit locations). You import
-them from the [`history` package](https://github.com/rackt/history), not react router.
+them from the [`history` package](https://github.com/reactjs/history), not react router.
 
 ```js
 // v0.13.x
@@ -68,7 +68,7 @@ render(<Router history={history}>{routes}</Router>, el)
 
 If you do not specify a history type (as in the example above) then you will notice some unusual behaviour after updating to 1.0.0. With the default hash based routing a querystring entry not defined by yourself will start appearing in your URLs called `_k`. An example of how it looks is this: `?_k=umhx1s`
 
-This is intended and part of [createHashHistory](https://github.com/rackt/react-router/blob/master/docs/guides/Histories.md#createhashhistory) (which is the default history approach used if one is not specified). You can read more about the feature [here](https://github.com/rackt/react-router/blob/master/docs/guides/Histories.md#what-is-that-_kckuvup-junk-in-the-url) and how to opt out [here](https://rackt.github.io/history/stable/HashHistoryCaveats.html).
+This is intended and part of [createHashHistory](/docs/guides/Histories.md#createhashhistory) (which is the default history approach used if one is not specified). You can read more about the feature [here](/docs/guides/Histories.md#what-is-that-_kckuvup-junk-in-the-url) and how to opt out [here](https://reactjs.org/history/stable/HashHistoryCaveats.html).
 
 ### Route Config
 
@@ -83,7 +83,7 @@ parents just like before but prop names have changed.
 <Route path="about" component={About}/>
 ```
 
-Named routes are gone (for now, [see discussion](https://github.com/rackt/react-router/issues/1840))
+Named routes are gone (for now, [see discussion](https://github.com/reactjs/react-router/issues/1840))
 
 ### NotFound route
 
@@ -240,7 +240,7 @@ var Assignment = React.createClass({
 var Assignment = React.createClass({
   mixins: [ History ],
   navigateAfterSomethingHappened () {
-    // the router is now built on rackt/history, and it is a first class
+    // the router is now built on reactjs/history, and it is a first class
     // API in the router for navigating
     this.history.pushState(null, `/users/${user.id}`, query);
     // this.history.replaceState(null, `/users/${user.id}`, query);
@@ -331,7 +331,7 @@ For example, `params` is not available via context.
 ### Scrolling
 
 We're developing scroll behaviors separately in the
-[`scroll-behavior`](https://github.com/rackt/scroll-behavior)
+[`scroll-behavior`](https://github.com/taion/scroll-behavior)
 library until we have a stable, robust implementation that we're happy with.
 Currently, scroll behaviors are exposed there as history enhancers:
 
@@ -370,4 +370,3 @@ To cancel a "transition from", please refer to the
 
 There's a lot of the old API we've missed, please give the [new
 docs](/docs) a read and help us fill this guide in. Thanks!
-

upgrade-guides/v2.0.0.md

@@ -4,7 +4,7 @@
 
 ### Goals
 
-You might enjoy reading this issue: https://github.com/rackt/react-router/issues/2646
+You might enjoy reading this issue: https://github.com/reactjs/react-router/issues/2646
 
 1. Clear up the coupling between History and Router with simpler APIs.
 
@@ -26,7 +26,7 @@ The deprecation warnings should also lead you to the relevant part of this docum
 
 ### Upgrade Automatically with Codemods
 
-Using a tool called [jscodeshift](https://github.com/facebook/jscodeshift), we have made available some codemods for upgrading your code to the new APIs automatically: https://github.com/rackt/rackt-codemod
+Using a tool called [jscodeshift](https://github.com/facebook/jscodeshift), we have made available some codemods for upgrading your code to the new APIs automatically: https://github.com/reactjs/rackt-codemod
 
 A codemod is much like Babel, but instead of converting your ES2015 code to ES5 compatible syntax, it does a limited set of transformations on function names, arguments, common patterns and more. One way to think of jscodeshift (the underlying tool) is "jQuery for code". These codemods aren't bulletproof, so be sure to test your code after you run them. But they can help with upgrading a large codebase to remove deprecation warnings you're now triggering.