From 3ab3fabf5e6d8ff42263a323b3263a84a75ee4d6 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Paul=20O=E2=80=99Shannessy?= Date: Mon, 22 Dec 2014 13:56:44 -0800 Subject: [PATCH] Merge pull request #2760 from alextsg/patch-3 Update 14-communicate-between-components.md for grammatical changes --- docs/tips/14-communicate-between-components.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/tips/14-communicate-between-components.md b/docs/tips/14-communicate-between-components.md index 06afe3d921..e217340ae8 100644 --- a/docs/tips/14-communicate-between-components.md +++ b/docs/tips/14-communicate-between-components.md @@ -38,4 +38,4 @@ React.render( Notice the use of `bind(this, arg1, arg2, ...)`: we're simply passing more arguments to `handleClick`. This is not a new React concept; it's just JavaScript. -For communication between two components that don't have a parent-child relationship, you can set up your own global event system. Subscribe to events in `componentDidMount()`, unsubscribe in `componentWillUnmount()`, and when you receive an event, call `setState()`. +For communication between two components that don't have a parent-child relationship, you can set up your own global event system. Subscribe to events in `componentDidMount()`, unsubscribe in `componentWillUnmount()`, and call `setState()` when you receive an event.