Skip to content

Commit 0a0e107

Browse files
Fixed grammar mistake
1 parent 5945c4b commit 0a0e107

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -17,7 +17,7 @@
1717
|8 | [What is state in React?](#what-is-state-in-react) |
1818
|9 | [What are props in React?](#what-are-props-in-react) |
1919
|10 | [What is the difference between state and props?](#what-is-the-difference-between-state-and-props) |
20-
|11 | [Why should not we update the state directly?](#why-should-not-we-update-the-state-directly) |
20+
|11 | [Why should we not update the state directly?](#why-should-we-not-update-the-state-directly) |
2121
|12 | [What is the purpose of callback function as an argument of setState()?](#what-is-the-purpose-of-callback-function-as-an-argument-of-setstate)
2222
|13 | [What is the difference between HTML and React event handling?](#what-is-the-difference-between-html-and-react-event-handling) |
2323
|14 | [How to bind methods or event handlers in JSX callbacks?](#how-to-bind-methods-or-event-handlers-in-jsx-callbacks) |
@@ -440,7 +440,7 @@
440440
441441
Both *props* and *state* are plain JavaScript objects. While both of them hold information that influences the output of render, they are different in their functionality with respect to component. Props get passed to the component similar to function parameters whereas state is managed within the component similar to variables declared within a function.
442442
443-
11. ### Why should not we update the state directly?
443+
11. ### Why should we not update the state directly?
444444
445445
If you try to update state directly then it won't re-render the component.
446446

0 commit comments

Comments
 (0)