Skip to content

Commit 6455acd

Browse files
committed
Capitalize React Actions in reducer docs
1 parent 8c68ae8 commit 6455acd

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

‎src/content/learn/extracting-state-logic-into-a-reducer.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -183,11 +183,11 @@ Each of its event handlers calls `setTasks` in order to update the state. As thi
183183

184184
Reducers are a different way to handle state. You can migrate from `useState` to `useReducer` in three steps:
185185

186-
1. **Move** from setting state to dispatching actions.
186+
1. **Move** from setting state to dispatching Actions.
187187
2. **Write** a reducer function.
188188
3. **Use** the reducer from your component.
189189

190-
### Step 1: Move from setting state to dispatching actions {/*step-1-move-from-setting-state-to-dispatching-actions*/}
190+
### Step 1: Move from setting state to dispatching Actions {/*step-1-move-from-setting-state-to-dispatching-actions*/}
191191

192192
Your event handlers currently specify _what to do_ by setting state:
193193

@@ -862,7 +862,7 @@ li {
862862

863863
</Sandpack>
864864

865-
Component logic can be easier to read when you separate concerns like this. Now the event handlers only specify _what happened_ by dispatching actions, and the reducer function determines _how the state updates_ in response to them.
865+
Component logic can be easier to read when you separate concerns like this. Now the event handlers only specify _what happened_ by dispatching Actions, and the reducer function determines _how the state updates_ in response to them.
866866

867867
## Comparing `useState` and `useReducer` {/*comparing-usestate-and-usereducer*/}
868868

0 commit comments

Comments
 (0)