From 2566da5371e100b4f76de849f5c85d7fea30e2bb Mon Sep 17 00:00:00 2001 From: Leon Yip Date: Sat, 22 Aug 2015 00:56:23 -0700 Subject: [PATCH] Update 04-multiple-components.md Added an extra word to make the sentence read a little easier. --- docs/04-multiple-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/04-multiple-components.md b/docs/04-multiple-components.md index 22c96391..cf57260a 100644 --- a/docs/04-multiple-components.md +++ b/docs/04-multiple-components.md @@ -181,7 +181,7 @@ In React, data flows from owner to owned component through `props` as discussed ## A Note on Performance -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. +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. 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.