Skip to content

Commit b86d062

Browse files
committed
Grammatical clarification
1 parent eff90e9 commit b86d062

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

article/react-redux-concept-workflow.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -93,7 +93,7 @@ I'd like to start with a graphical cheat sheet explaining the workflow in a Reac
9393

9494
1. It is a [popular convention](http://redux.js.org/docs/api/combineReducers.html) (but not an obligation) to name a reducer function after the slice it manages. I suggest, that you really stick to this convention, because it is helpful in many respects when you go in. So a reducer for *state.slice01* would be called *slice01()*.
9595

96-
1. Since there usually is a reducer for each slice, we end up with a lot of individual slice reducers each of them is only concerned with its slice. However, we need to take care of all slices all at the same time. The solution is to combine all slice reducers into one overall reducer that is often named *rootReducer()*. To achieve this there is a function called [*combineReducers()*](http://redux.js.org/docs/api/combineReducers.html) that takes an object containing the individal reducers:
96+
1. Since there usually is a reducer for each slice, we end up with a lot of individual slice reducers where each of them is only concerned with its slice. However, we need to take care of all the slices at the same time. The solution is to combine all slice reducers into one overall reducer that is often named *rootReducer()*. To achieve this there is a function called [*combineReducers()*](http://redux.js.org/docs/api/combineReducers.html) that takes an object containing the individal reducers:
9797

9898
```JavaScript
9999
import { combineReducers } from 'redux'

0 commit comments

Comments
 (0)