From 3b671d1d1bc7af2e1dbb81e97e129e851b3dd0e9 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Van=20der=20Auwermeulen=20Gr=C3=A9goire?= Date: Wed, 4 Jan 2017 18:18:52 +0100 Subject: [PATCH] Update state-and-lifecycle.md (#8424) * Update state-and-lifecycle.md Isn't clock state and props the same in this example? * Clarify --- docs/state-and-lifecycle.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/state-and-lifecycle.md b/docs/state-and-lifecycle.md index 5aa95e93..5c23a995 100644 --- a/docs/state-and-lifecycle.md +++ b/docs/state-and-lifecycle.md @@ -432,7 +432,7 @@ This also works for user-defined components: ``` -The `FormattedDate` component would receive the `date` in its props and wouldn't know whether it came from the `Clock`'s state, the props, or was typed by hand: +The `FormattedDate` component would receive the `date` in its props and wouldn't know whether it came from the `Clock`'s state, from the `Clock`'s props, or was typed by hand: ```js function FormattedDate(props) {