[Docs] Reorder categories, remove Other category and move its pages (reduxjs#3898)

Former-commit-id: 3ae9d7b

Author: sbaudray

docs/api/README.md

@@ -6,7 +6,7 @@ hide_title: true
 
 # API Reference
 
-The Redux API surface is tiny. Redux defines a set of contracts for you to implement (such as [reducers](../Glossary.md#reducer)) and provides a few helper functions to tie these contracts together.
+The Redux API surface is tiny. Redux defines a set of contracts for you to implement (such as [reducers](../understanding/thinking-in-redux/Glossary.md#reducer)) and provides a few helper functions to tie these contracts together.
 
 This section documents the complete Redux API. Keep in mind that Redux is only concerned with managing the state. In a real app, you'll also want to use UI bindings like [react-redux](https://github.com/gaearon/react-redux).
 

docs/api/Store.md.REMOVED.git-id

@@ -1 +1 @@
-c9c9e3c89951aca829cbebbac7054eff2ba7534e
+72f0e536b6bfffb8535e63dce5976563a13dcece

docs/api/applyMiddleware.md.REMOVED.git-id

@@ -1 +1 @@
-8e1b9e23ed6f9db0a94a9294f63b928c791785f6
+0c74fe5d6c28ea08e41a9620860e2fe1056d429d

docs/api/bindActionCreators.md

@@ -6,7 +6,7 @@ hide_title: true
 
 # `bindActionCreators(actionCreators, dispatch)`
 
-Turns an object whose values are [action creators](../Glossary.md#action-creator), into an object with the same keys, but with every action creator wrapped into a [`dispatch`](Store.md#dispatchaction) call so they may be invoked directly.
+Turns an object whose values are [action creators](../understanding/thinking-in-redux/Glossary.md#action-creator), into an object with the same keys, but with every action creator wrapped into a [`dispatch`](Store.md#dispatchaction) call so they may be invoked directly.
 
 Normally you should just call [`dispatch`](Store.md#dispatchaction) directly on your [`Store`](Store.md) instance. If you use Redux with React, [react-redux](https://github.com/gaearon/react-redux) will provide you with the [`dispatch`](Store.md#dispatchaction) function so you can call it directly, too.
 
@@ -16,7 +16,7 @@ For convenience, you can also pass an action creator as the first argument, and
 
 #### Parameters
 
-1. `actionCreators` (_Function_ or _Object_): An [action creator](../Glossary.md#action-creator), or an object whose values are action creators.
+1. `actionCreators` (_Function_ or _Object_): An [action creator](../understanding/thinking-in-redux/Glossary.md#action-creator), or an object whose values are action creators.
 
 2. `dispatch` (_Function_): A [`dispatch`](Store.md#dispatchaction) function available on the [`Store`](Store.md) instance.
 

docs/api/combineReducers.md.REMOVED.git-id

@@ -1 +1 @@
-e284dca79c60bbbcf0bf0529b2a91a1e471300c1
+97d4e9bff3ef6ef1eca7f34ee470bb276251f88b

docs/api/compose.md

@@ -9,7 +9,7 @@ hide_title: true
 Composes functions from right to left.
 
 This is a functional programming utility, and is included in Redux as a convenience.
-You might want to use it to apply several [store enhancers](../Glossary.md#store-enhancer) in a row.
+You might want to use it to apply several [store enhancers](../understanding/thinking-in-redux/Glossary.md#store-enhancer) in a row.
 
 #### Arguments
 

docs/api/createStore.md

@@ -11,7 +11,7 @@ There should only be a single store in your app.
 
 #### Arguments
 
-1. `reducer` _(Function)_: A [reducing function](../Glossary.md#reducer) that returns the next [state tree](../Glossary.md#state), given the current state tree and an [action](../Glossary.md#action) to handle.
+1. `reducer` _(Function)_: A [reducing function](../understanding/thinking-in-redux/Glossary.md#reducer) that returns the next [state tree](../understanding/thinking-in-redux/Glossary.md#state), given the current state tree and an [action](../understanding/thinking-in-redux/Glossary.md#action) to handle.
 
 2. [`preloadedState`] _(any)_: The initial state. You may optionally specify it to hydrate the state from the server in universal apps, or to restore a previously serialized user session. If you produced `reducer` with [`combineReducers`](combineReducers.md), this must be a plain object with the same shape as the keys passed to it. Otherwise, you are free to pass anything that your `reducer` can understand.
 

docs/faq/ImmutableData.md.REMOVED.git-id

@@ -1 +1 @@
-71a09935342dbe5832630bb1fd13a69260359e67
+884b4c438bf7abd2c98c5797055f3bd04e94c482

docs/faq/ReactRedux.md.REMOVED.git-id

@@ -1 +1 @@
-ee79002d71e2c3a5ea96af16aab8ade3a8560711
+213c0c2c3eee51440e5a892071c59547a2619de9

docs/recipes/MigratingToRedux.md

@@ -13,7 +13,7 @@ We don't want to lock you in!
 
 ## From Flux
 
-[Reducers](../Glossary.md#reducer) capture “the essence” of Flux Stores, so it's possible to gradually migrate an existing Flux project towards Redux, whether you are using [Flummox](http://github.com/acdlite/flummox), [Alt](http://github.com/goatslacker/alt), [traditional Flux](https://github.com/facebook/flux), or any other Flux library.
+[Reducers](../understanding/thinking-in-redux/Glossary.md#reducer) capture “the essence” of Flux Stores, so it's possible to gradually migrate an existing Flux project towards Redux, whether you are using [Flummox](http://github.com/acdlite/flummox), [Alt](http://github.com/goatslacker/alt), [traditional Flux](https://github.com/facebook/flux), or any other Flux library.
 
 Your process will look like this:
 

docs/recipes/README.md

@@ -20,4 +20,5 @@ These are some use cases and code snippets to get you started with Redux in a re
 - [Isolating Redux Sub-Apps](IsolatingSubapps.md)
 - [Using Immutable.JS with Redux](UsingImmutableJS.md)
 - [Code Splitting](CodeSplitting.md)
+- [Troubleshooting](Troubleshooting.md)
 - [Structuring Reducers](structuring-reducers/StructuringReducers.md)

docs/recipes/ReducingBoilerplate.md.REMOVED.git-id

@@ -1 +1 @@
-4ec813343df774979c6330652706a1bd759d2589
+571a3c1934c0cd249fb855870325a9f555d5fdad

docs/Troubleshooting.md.REMOVED.git-id renamed to docs/recipes/Troubleshooting.md.REMOVED.git-id

@@ -1 +1 @@
-0bc33b24d5ef987d98dc222ac56457676b239a52
+7dc6bf13a048526ea11a1847314e48616d5fca5e

docs/recipes/UsingImmutableJS.md.REMOVED.git-id

@@ -11,7 +11,7 @@ Redux can be described in three fundamental principles:
 
 ### Single source of truth
 
-**The [global state](../../Glossary.md#state) of your application is stored in an object tree within a single [store](../../Glossary.md#store).**
+**The [global state](./Glossary.md#state) of your application is stored in an object tree within a single [store](./Glossary.md#store).**
 
 This makes it easy to create universal apps, as the state from your server can be serialized and hydrated into the client with no extra coding effort. A single state tree also makes it easier to debug or inspect an application; it also enables you to persist your app's state in development, for a faster development cycle. Some functionality which has been traditionally difficult to implement - Undo/Redo, for example - can suddenly become trivial to implement, if all of your state is stored in a single tree.
 
@@ -37,7 +37,7 @@ console.log(store.getState())
 
 ### State is read-only
 
-**The only way to change the state is to emit an [action](../../Glossary.md#action), an object describing what happened.**
+**The only way to change the state is to emit an [action](./Glossary.md), an object describing what happened.**
 
 This ensures that neither the views nor the network callbacks will ever write directly to the state. Instead, they express an intent to transform the state. Because all changes are centralized and happen one by one in a strict order, there are no subtle race conditions to watch out for. As actions are just plain objects, they can be logged, serialized, stored, and later replayed for debugging or testing purposes.
 
@@ -55,7 +55,7 @@ store.dispatch({
 
 ### Changes are made with pure functions
 
-**To specify how the state tree is transformed by actions, you write pure [reducers](../../Glossary.md#reducer).**
+**To specify how the state tree is transformed by actions, you write pure [reducers](./Glossary.md#reducer).**
 
 Reducers are just pure functions that take the previous state and an action, and return the next state. Remember to return new state objects, instead of mutating the previous state. You can start with a single reducer, and as your app grows, split it off into smaller reducers that manage specific parts of the state tree. Because reducers are just functions, you can control the order in which they are called, pass additional data, or even make reusable reducers for common tasks such as pagination.
 

docs/Glossary.md.REMOVED.git-id renamed to docs/understanding/thinking-in-redux/Glossary.md.REMOVED.git-id

@@ -1 +1 @@
-bdd7a5aa79ff8387a95f2d35bae27f584c565c23
+f30372243f37def103b1ebcf2d468a082600f584

docs/understanding/thinking-in-redux/ThreePrinciples.md

@@ -8,21 +8,6 @@ module.exports = {
       'introduction/ecosystem',
       'introduction/examples'
     ],
-    'Understanding Redux': [
-      {
-        type: 'category',
-        label: 'Thinking in Redux',
-        items: [
-          'understanding/thinking-in-redux/motivation',
-          'understanding/thinking-in-redux/three-principles'
-        ]
-      },
-      {
-        type: 'category',
-        label: 'History and Design',
-        items: ['understanding/history-and-design/prior-art']
-      }
-    ],
     Tutorials: [
       'tutorials/tutorials-index',
       {
@@ -78,6 +63,7 @@ module.exports = {
       'recipes/isolating-redux-sub-apps',
       'recipes/using-immutablejs-with-redux',
       'recipes/code-splitting',
+      'recipes/troubleshooting',
       {
         type: 'category',
         label: 'Structuring Reducers',
@@ -97,6 +83,22 @@ module.exports = {
         ]
       }
     ],
+    'Understanding Redux': [
+      {
+        type: 'category',
+        label: 'Thinking in Redux',
+        items: [
+          'understanding/thinking-in-redux/motivation',
+          'understanding/thinking-in-redux/three-principles',
+          'understanding/thinking-in-redux/glossary'
+        ]
+      },
+      {
+        type: 'category',
+        label: 'History and Design',
+        items: ['understanding/history-and-design/prior-art']
+      }
+    ],
     FAQ: [
       'faq',
       'faq/general',
@@ -112,7 +114,6 @@ module.exports = {
       'faq/miscellaneous'
     ],
     'Style Guide': ['style-guide/style-guide'],
-    Other: ['glossary', 'troubleshooting'],
     'API Reference': [
       'api/api-reference',
       'api/createstore',