From 5551b3420d206ade06d5e70f2adb32bd9db17613 Mon Sep 17 00:00:00 2001 From: Tanya Bouman Date: Mon, 14 Mar 2022 16:46:46 -0400 Subject: [PATCH] props-vs-state: grammar fix --- props-vs-state.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/props-vs-state.md b/props-vs-state.md index d53c26d..b482bd9 100644 --- a/props-vs-state.md +++ b/props-vs-state.md @@ -11,7 +11,7 @@ It's fairly easy to understand how they work—especially when seen in context The main responsibility of a Component is to translate raw data into rich HTML. With that in mind, the _props_ and the _state_ together constitute the _raw data_ that the HTML output derives from. -You could say _props_ + _state_ is the input data for the `render()` function of a Component, so we need to zoom in and see what each data type represents and where does it come from. +You could say _props_ + _state_ is the input data for the `render()` function of a Component, so we need to zoom in and see what each data type represents and where it comes from. Because we also use [Cosmos](https://github.com/skidding/cosmos) where _props_ can contain an initial _state_, getting this straight is crucial.