From 984f51d304e4174de1e490f87c04df0b6e5abcf1 Mon Sep 17 00:00:00 2001 From: Daniel Diekmeier Date: Sun, 30 Oct 2016 19:15:19 +0100 Subject: [PATCH] Fix typo --- docs/en/intro.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/en/intro.md b/docs/en/intro.md index bce062a35..3cd9b5cc9 100644 --- a/docs/en/intro.md +++ b/docs/en/intro.md @@ -44,7 +44,7 @@ However, the simplicity quickly breaks down when we have **multiple components t - Multiple views may depend on the same piece of state. - Actions from different views may need to mutate the same piece of state. -For problem one, passing props can be tedious for deeply nested components, and simply doesn't work for sibling components. For problem two, we often find ourselves resorting to solutions such as reaching for direct parent/child instance references or trying to mutate and synchronize multiple copies of the state via events. Both of these patterns are brittle and quickly leads to unmaintainable code. +For problem one, passing props can be tedious for deeply nested components, and simply doesn't work for sibling components. For problem two, we often find ourselves resorting to solutions such as reaching for direct parent/child instance references or trying to mutate and synchronize multiple copies of the state via events. Both of these patterns are brittle and quickly lead to unmaintainable code. So why don't we extract the shared state out of the components, and manage it in a global singleton? With this, our component tree becomes a big "view", and any component can access the state or trigger actions, no matter where they are in the tree!