Skip to content

Commit 466809e

Browse files
stuymedovagaearon
andauthored
docs: fix a grammatical error (#4183)
Co-authored-by: dan <dan.abramov@gmail.com>
1 parent cb6e1d0 commit 466809e

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

beta/src/pages/learn/extracting-state-logic-into-a-reducer.md

+1-1
Original file line numberDiff line numberDiff line change
@@ -224,7 +224,7 @@ Remove all the state setting logic. What you are left with are three event handl
224224
* `handleChangeTask(task)` is called when the user toggles a task or presses "Save".
225225
* `handleDeleteTask(taskId)` is called when the user presses "Delete".
226226

227-
Managing state with reducers is slightly different from directly setting state. Instead of telling React "what to do" by setting state, you specify "what the user just did" by dispatching "actions" from your event handlers. (The state update logic will live elsewhere!) So instead of "setting `tasks`" via event handler, you're dispatching an "added/changed/deleted a task" action. This is more descriptive of the user's intent.
227+
Managing state with reducers is slightly different from directly setting state. Instead of telling React "what to do" by setting state, you specify "what the user just did" by dispatching "actions" from your event handlers. (The state update logic will live elsewhere!) So instead of "setting `tasks`" via an event handler, you're dispatching an "added/changed/deleted a task" action. This is more descriptive of the user's intent.
228228

229229
```js
230230
function handleAddTask(text) {

0 commit comments

Comments
 (0)