Update 04-multiple-components.md
Added an extra word to make the sentence read a little easier.
Leon Yip committed
Aug 22, 2015 at 00:56 UTC
2f4ea6057108985815a86c0531a71c22843749a6
1 file changed
+1
-1
docs/docs/04-multiple-components.md
+1
-1
@@ -181,7 +181,7 @@ In React, data flows from owner to owned component through `props` as discussed
181
182
## A Note on Performance
183
184
-You may be thinking that it's expensive to change data if there are a large number of nodes under an owner. The good news is that JavaScript is fast and `render()` methods tend to be quite simple, so in most applications this is extremely fast. Additionally, the bottleneck is almost always the DOM mutation and not JS execution. React will optimize this for you using batching and change detection.
184
+You may be thinking that it's expensive to change data if there are a large number of nodes under an owner. The good news is that JavaScript is fast and `render()` methods tend to be quite simple, so in most applications this is extremely fast. Additionally, the bottleneck is almost always the DOM mutation and not JS execution. React will optimize this for you by using batching and change detection.
185
186
However, sometimes you really want to have fine-grained control over your performance. In that case, simply override `shouldComponentUpdate()` to return false when you want React to skip processing of a subtree. See [the React reference docs](/react/docs/component-specs.html) for more information.
187