diff --git a/content/docs/thinking-in-react.md b/content/docs/thinking-in-react.md index 68a80e99..8f3786d8 100644 --- a/content/docs/thinking-in-react.md +++ b/content/docs/thinking-in-react.md @@ -62,7 +62,7 @@ Now that we've identified the components in our mock, let's arrange them into a ## Step 2: Build A Static Version in React

See the Pen Thinking In React: Step 2 on CodePen.

- + Now that you have your component hierarchy, it's time to implement your app. The easiest way is to build a version that takes your data model and renders the UI but has no interactivity. It's best to decouple these processes because building a static version requires a lot of typing and no thinking, and adding interactivity requires a lot of thinking and not a lot of typing. We'll see why. @@ -107,7 +107,6 @@ So finally, our state is: ## Step 4: Identify Where Your State Should Live

See the Pen Thinking In React: Step 4 on CodePen.

- OK, so we've identified what the minimal set of app state is. Next, we need to identify which component mutates, or *owns*, this state. @@ -133,7 +132,6 @@ You can start seeing how your application will behave: set `filterText` to `"bal ## Step 5: Add Inverse Data Flow

See the Pen Thinking In React: Step 5 on CodePen.

- So far, we've built an app that renders correctly as a function of props and state flowing down the hierarchy. Now it's time to support data flowing the other way: the form components deep in the hierarchy need to update the state in `FilterableProductTable`.