From 6455acd16f0a5ad40e2ff4a6698a99f8ebf1788b Mon Sep 17 00:00:00 2001 From: Meetr Date: Tue, 6 Oct 2026 22:08:12 +0530 Subject: [PATCH] Capitalize React Actions in reducer docs --- src/content/learn/extracting-state-logic-into-a-reducer.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/src/content/learn/extracting-state-logic-into-a-reducer.md b/src/content/learn/extracting-state-logic-into-a-reducer.md index 5c08c012390..9d98c8cfb2a 100644 --- a/src/content/learn/extracting-state-logic-into-a-reducer.md +++ b/src/content/learn/extracting-state-logic-into-a-reducer.md @@ -183,11 +183,11 @@ Each of its event handlers calls `setTasks` in order to update the state. As thi Reducers are a different way to handle state. You can migrate from `useState` to `useReducer` in three steps: -1. **Move** from setting state to dispatching actions. +1. **Move** from setting state to dispatching Actions. 2. **Write** a reducer function. 3. **Use** the reducer from your component. -### Step 1: Move from setting state to dispatching actions {/*step-1-move-from-setting-state-to-dispatching-actions*/} +### Step 1: Move from setting state to dispatching Actions {/*step-1-move-from-setting-state-to-dispatching-actions*/} Your event handlers currently specify _what to do_ by setting state: @@ -862,7 +862,7 @@ li { -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. +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. ## Comparing `useState` and `useReducer` {/*comparing-usestate-and-usereducer*/}