From 400e29748927d62488375aba017be41bff49e99b Mon Sep 17 00:00:00 2001 From: Jim Date: Wed, 14 Oct 2015 14:42:34 -0700 Subject: [PATCH] Tweak wording when talking about props changing --- docs/03-interactivity-and-dynamic-uis.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/03-interactivity-and-dynamic-uis.md b/docs/03-interactivity-and-dynamic-uis.md index f5f82c93..dc4a19c2 100644 --- a/docs/03-interactivity-and-dynamic-uis.md +++ b/docs/03-interactivity-and-dynamic-uis.md @@ -74,4 +74,4 @@ A common pattern is to create several stateless components that just render data * **Computed data:** Don't worry about precomputing values based on state — it's easier to ensure that your UI is consistent if you do all computation within `render()`. For example, if you have an array of list items in state and you want to render the count as a string, simply render `this.state.listItems.length + ' list items'` in your `render()` method rather than storing it on state. * **React components:** Build them in `render()` based on underlying props and state. -* **Duplicated data from props:** Try to use props as the source of truth where possible. One valid use to store props in state is to be able to know its previous values, because props can change over time. +* **Duplicated data from props:** Try to use props as the source of truth where possible. One valid use to store props in state is to be able to know its previous values, because props may change as the result of a parent component re-rendering.