Fix Redux API links

Author: markerikson

docs/api.md

@@ -16,7 +16,7 @@ If you *really* need to, you can manually pass `store` as a prop to every `conne
 
 ### Props
 
-* `store` (*[Redux Store](https://redux.js.org/api-reference/store)*): The single Redux store in your application.
+* `store` (*[Redux Store](https://redux.js.org/api/store)*): The single Redux store in your application.
 * `children` (*ReactElement*) The root of your component hierarchy.
 
 ### Example
@@ -71,7 +71,7 @@ It does not modify the component class passed to it; instead, it *returns* a new
 
 * [`mapDispatchToProps(dispatch, [ownProps]): dispatchProps`] \(*Object* or *Function*): If an object is passed, each function inside it is assumed to be a Redux action creator. An object with the same function names, but with every action creator wrapped into a `dispatch` call so they may be invoked directly, will be merged into the component’s props.  
 
-  If a function is passed, it will be given `dispatch` as the first parameter.  It’s up to you to return an object that somehow uses `dispatch` to bind action creators in your own way. (Tip: you may use the [`bindActionCreators()`](https://redux.js.org/api-reference/bindactioncreators) helper from Redux.)  
+  If a function is passed, it will be given `dispatch` as the first parameter.  It’s up to you to return an object that somehow uses `dispatch` to bind action creators in your own way. (Tip: you may use the [`bindActionCreators()`](https://redux.js.org/api/bindactioncreators) helper from Redux.)  
 
   If your `mapDispatchToProps` function is declared as taking two parameters, it will be called with `dispatch` as the first parameter and the props passed to the connected component as the second parameter, and will be re-invoked whenever the connected component receives new props.  (The second parameter is normally referred to as `ownProps` by convention.)