update links

Author: alxndr

09_middleware.js

@@ -161,7 +161,7 @@ function discardMiddleware ({ dispatch, getState }) {
 //     const finalCreateStore = applyMiddleware(discardMiddleware, thunkMiddleware)(createStore)
 // should make your actions never reach your thunkMiddleware and even less your reducers.
 
-// See http://rackt.org/redux/docs/introduction/Ecosystem.html, section Middleware, to
+// See http://redux.js.org/docs/introduction/Ecosystem.html#middleware, section Middleware, to
 // see other middleware examples.
 
 // Let's sum up what we've learned so far:

11_src/src/application.jsx

@@ -1,13 +1,11 @@
 // Tutorial 12 - Provider-and-connect.js
 
-// Now is the time to meet the first binding that redux-react (https://github.com/rackt/react-redux)
+// Now is the time to meet the first binding that redux-react (https://github.com/reactjs/react-redux)
 // brings to us: the Provider component.
 
 // Provider is a React Component designed to be used as a wrapper of your application's root component. Its
-// purpose is to provide your redux instance to all of your application's components. How it does that does not
-// really matter to us but just to let you know, it's using React's context feature (it's undocumented so you
-// don't have to know about it, but if you're curious:
-// https://www.tildedave.com/2014/11/15/introduction-to-contexts-in-react-js.html).
+// purpose is to provide your Redux instance to all of your application's components. Documentation is here:
+// https://github.com/reactjs/react-redux/blob/3.x/docs/api.md#provider-store
 
 import React from 'react'
 import Home from './home'

12_final-words.js

@@ -2,14 +2,14 @@
 
 // There is actually more to Redux and react-redux than what we showed you with this tutorial. For example,
 // concerning Redux, you may be interested in bindActionCreators (to produce a hash of action creators
-// already bound to dispatch - http://rackt.org/redux/docs/api/bindActionCreators.html).
+// already bound to dispatch - http://redux.js.org/docs/api/bindActionCreators.html).
 
 // We hope we've given you the keys to better understand Flux and to see more clearly
 // how Flux implementations differ from one another - especially how Redux stands out ;).
 
 // Where to go from here?
 
 // The official Redux documentation is really awesome and exhaustive so you should not hesitate to
-// refer to it from now on: http://rackt.org/redux/index.html
+// refer to it from now on: http://redux.js.org/
 
 // Have fun with React and Redux!