{"files":[{"path":"docs\/docs\/04-multiple-components.md","status":"M"}],"body":"Fix broken guide example in \"Motivation: Separation of Concerns\"","commit":{"revision":"4b2b7b0d3edf1ace0e070960d764073b9c2040eb","shortRevision":"4b2b7b0d3e","authorEmail":"paul@oshannessy.com","subject":"Merge pull request #5911 from Mathieuu\/patch-1","authorName":"Paul O’Shannessy","authoredAt":"2016-01-28T10:22:33-08:00"},"parents":["fc547e8380cfe778d0995dc452b56e8d15b87cf4","e1b7c3aa0c4ca3bf3b459c8a968ec5d5d7be56f5"],"patch":"diff --git a\/docs\/docs\/04-multiple-components.md b\/docs\/docs\/04-multiple-components.md\nindex f6fa1de1e6..08009746f6 100644\n--- a\/docs\/docs\/04-multiple-components.md\n+++ b\/docs\/docs\/04-multiple-components.md\n@@ -14,49 +14,49 @@ By building modular components that reuse other components with well-defined int\n \n ## Composition Example\n \n-Let's create a simple Avatar component which shows a profile picture and username using the Facebook Graph API.\n+Let's create a simple Avatar component which shows a Facebook page picture and name using the Facebook Graph API.\n \n ```javascript\n var Avatar = React.createClass({\n render: function() {\n return (\n

\n- \n- \n+ \n+ \n <\/div>\n );\n }\n });\n \n-var ProfilePic = React.createClass({\n+var PagePic = React.createClass({\n render: function() {\n return (\n-

\n+

\n );\n }\n });\n \n-var ProfileLink = React.createClass({\n+var PageLink = React.createClass({\n render: function() {\n return (\n- \n- {this.props.username}\n+ \n+ {this.props.pagename}\n <\/a>\n );\n }\n });\n \n ReactDOM.render(\n- ,\n+ ,\n document.getElementById('example')\n );\n ```\n \n ## Ownership\n \n-In the above example, instances of `Avatar` *own* instances of `ProfilePic` and `ProfileLink`. In React, **an owner is the component that sets the `props` of other components**. More formally, if a component `X` is created in component `Y`'s `render()` method, it is said that `X` is *owned by* `Y`. As discussed earlier, a component cannot mutate its `props` — they are always consistent with what its owner sets them to. This fundamental invariant leads to UIs that are guaranteed to be consistent.\n+In the above example, instances of `Avatar` *own* instances of `PagePic` and `PageLink`. In React, **an owner is the component that sets the `props` of other components**. More formally, if a component `X` is created in component `Y`'s `render()` method, it is said that `X` is *owned by* `Y`. As discussed earlier, a component cannot mutate its `props` — they are always consistent with what its owner sets them to. This fundamental invariant leads to UIs that are guaranteed to be consistent.\n \n-It's important to draw a distinction between the owner-ownee relationship and the parent-child relationship. The owner-ownee relationship is specific to React, while the parent-child relationship is simply the one you know and love from the DOM. In the example above, `Avatar` owns the `div`, `ProfilePic` and `ProfileLink` instances, and `div` is the **parent** (but not owner) of the `ProfilePic` and `ProfileLink` instances.\n+It's important to draw a distinction between the owner-ownee relationship and the parent-child relationship. The owner-ownee relationship is specific to React, while the parent-child relationship is simply the one you know and love from the DOM. In the example above, `Avatar` owns the `div`, `PagePic` and `PageLink` instances, and `div` is the **parent** (but not owner) of the `PagePic` and `PageLink` instances.\n \n ## Children\n \n"}

dillon1000/react

Files changed