diff --git a/README.md b/README.md
index 2c4cd02c..b8db5b72 100644
--- a/README.md
+++ b/README.md
@@ -17,7 +17,7 @@
 |8  | [What is state in React?](#what-is-state-in-react) |
 |9  | [What are props in React?](#what-are-props-in-react) |
 |10 | [What is the difference between state and props?](#what-is-the-difference-between-state-and-props) |
-|11 | [Why should not we update the state directly?](#why-should-not-we-update-the-state-directly) |
+|11 | [Why should we not update the state directly?](#why-should-we-not-update-the-state-directly) |
 |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)
 |13 | [What is the difference between HTML and React event handling?](#what-is-the-difference-between-html-and-react-event-handling) |
 |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 @@
 
     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.
 
-11. ### Why should not we update the state directly?
+11. ### Why should we not update the state directly?
 
     If you try to update state directly then it won't re-render the component.