Merge pull request #113 from sumanpaikdev/patch-1

Highlight a heading and adding a dot.

Author: vasanthk

patterns/19.async-nature-of-setState.md

@@ -4,15 +4,15 @@ On the Async nature of setState()
 ## Gist:
 React batches updates and flushes it out once per frame (perf optimization)
 However, in some cases React has no control over batching, hence updates are made synchronously
-eg. eventListeners, Ajax, setTimeout and similar Web APIs
+e.g. eventListeners, Ajax, setTimeout and similar Web APIs.
 
 
 ### Main Idea
 setState() does not immediately mutate this.state but creates a pending state transition.
 Accessing this.state after calling this method can potentially return the existing value.
 There is no guarantee of synchronous operation of calls to setState and calls may be batched for performance gains.
 
-Run the below code and you will make the following observations:
+#### Run the below code and you will make the following observations:
 
 You can see that in every situation (addEventListener, setTimeout or AJAX call) the state before and the state after are different.
 And that render was called immediately after triggering the setState method. But why is that?