small edits in preventDefault

rohan-paul · rohan-paul · commit 89cd5eee60c6 · 2019-07-01T13:49:19.000+05:30
diff --git a/React/preventDefault-in-React.md b/React/preventDefault-in-React.md
@@ -51,9 +51,15 @@ const ListWithAddItem = () => {
 export default ListWithAddItem;
 ```
 
-Why is a form submit reloading the browser? All native HTML elements come with their internal native behavior. For instance, input elements store their internal state. That&rsquo;s why often React is used to take over for having controlled components by managing the state via React. The same applies for a form element which has a submit event that is invoked via a submit button element. In the past, it was desired to refresh the browser to flush all state and to submit the data to a backend. Nowadays, a library such as React, gives us more flexibility to deal with the submit event ourselves. In this case, we deal with it by updating the list in our component&rsquo;s state.
+Without a preventDefault() a form submission will reload the browser.
 
-In another scenario, you may fetch data from a backend and store it in your component&rsquo;s state. There is no native submission from the form expected anymore, that&rsquo;s why the developer is able to take over. The developer shouldn&rsquo;t need to worry about any undesired behavior of the browser.
+Because, all native HTML elements come with their internal native behavior. For instance, input elements store their internal state. That&rsquo;s why often React is used to take over for having controlled components by managing the state via React.
+
+Similarly a Form element which has a submit event that is invoked via a submit button element, in the past, was desired to refresh the browser to flush all state and to submit the data to a backend. But with React, it gives us more flexibility to deal with the submit event ourselves by invoking the preventDefault()
+
+In another scenario, you may fetch data from a backend and store it in your component&rsquo;s state. There is no native submission from the form expected anymore, that&rsquo;s why the developer is able to take over.
+
+In another scenario, you may fetch data from a backend and store it in your component&rsquo;s state. There is no native submission from the form expected anymore, and the developer should be able to take over in this situation, so he shouldn&rsquo;t need to worry about any undesired behavior of the browser.
 
 #### Reading
 

-Original file line number
+Diff line change
 export default ListWithAddItem;
 ```
 -Why is a form submit reloading the browser? All native HTML elements come with their internal native behavior. For instance, input elements store their internal state. That’s why often React is used to take over for having controlled components by managing the state via React. The same applies for a form element which has a submit event that is invoked via a submit button element. In the past, it was desired to refresh the browser to flush all state and to submit the data to a backend. Nowadays, a library such as React, gives us more flexibility to deal with the submit event ourselves. In this case, we deal with it by updating the list in our component’s state.
 +Without a preventDefault() a form submission will reload the browser.
 -In another scenario, you may fetch data from a backend and store it in your component’s state. There is no native submission from the form expected anymore, that’s why the developer is able to take over. The developer shouldn’t need to worry about any undesired behavior of the browser.
 +Because, all native HTML elements come with their internal native behavior. For instance, input elements store their internal state. That’s why often React is used to take over for having controlled components by managing the state via React.
++
 +Similarly a Form element which has a submit event that is invoked via a submit button element, in the past, was desired to refresh the browser to flush all state and to submit the data to a backend. But with React, it gives us more flexibility to deal with the submit event ourselves by invoking the preventDefault()
++
 +In another scenario, you may fetch data from a backend and store it in your component’s state. There is no native submission from the form expected anymore, that’s why the developer is able to take over.
++
 +In another scenario, you may fetch data from a backend and store it in your component’s state. There is no native submission from the form expected anymore, and the developer should be able to take over in this situation, so he shouldn’t need to worry about any undesired behavior of the browser.
 #### Reading