[docs] Fix typo
Introduced in #3589
Paul O’Shannessy committed
Apr 8, 2015 at 10:39 UTC
ee811b161499559271fdd04bcda3befe25caf54c
1 file changed
+1
-1
docs/docs/11-advanced-performance.md
+1
-1
@@ -11,7 +11,7 @@ One of the first questions people ask when considering React for a project is wh
11
12
React makes use of a *virtual DOM*, which is a descriptor of a DOM subtree rendered in the browser. This parallel representation allows React to avoid creating DOM nodes and accessing existing ones, which is slower than operations on JavaScript objects. When a component's props or state change, React decides whether an actual DOM update is necessary by constructing a new virtual DOM and comparing it to the old one. Only in the case they are not equal, will React [reconcile](http://facebook.github.io/react/docs/reconciliation.html) the DOM, applying as few mutations as possible.
13
14
-On top of this, React provides a component lifecycle function, `shouldComponentUpdate`, which is triggered before the re-rendering process starts (virtual DOM comparision and possible eventual DOM reconciliation), giving the developer the ability to short circuit this process. The default implementation of this function returns `true`, leaving React to perform the update:
14
+On top of this, React provides a component lifecycle function, `shouldComponentUpdate`, which is triggered before the re-rendering process starts (virtual DOM comparison and possible eventual DOM reconciliation), giving the developer the ability to short circuit this process. The default implementation of this function returns `true`, leaving React to perform the update:
15
16
```javascript
17
shouldComponentUpdate: function(nextProps, nextState) {