Clearer differentiation between data and state in "Thinking in React" page.

"To build a static version of your app that renders your data model, you’ll want to build components that reuse other components and pass data using props. props are a way of passing data from parent to child. If you’re familiar with the concept of state, don’t use state at all to build this static version. State is reserved only for interactivity, that is, data that changes over time. Since this is a static version of the app, you don’t need it."

Perhaps by quantifying "data" as "model data" might be better. Generally it took me a few re-reads before I understood that in this paragraph "data" refers to model properties and "state" refers to interactions.

Open the “Thinking in React” page and review the paragraph distinguishing data from state. Clarify that “data” means model data or properties and that state represents changing interactive values. Done means the distinction is understandable without rereading the paragraph several times.