From 90a665d18e393d4084a4634a0677b9d8108569db Mon Sep 17 00:00:00 2001 From: Mike Fitzgerald Date: Tue, 14 May 2024 07:24:38 +0200 Subject: =?UTF-8?q?=F0=9F=94=80=20Quick=20typo=20fix,=20(#127)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- pages/guide/02-state-management.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/pages/guide/02-state-management.md b/pages/guide/02-state-management.md index f572493..b29ac5c 100644 --- a/pages/guide/02-state-management.md +++ b/pages/guide/02-state-management.md @@ -164,7 +164,7 @@ As our apps grow in size, we'll be thankful for this clarity! Although Lustre does have a way to create encapsulated stateful components (something we sorely missed in Elm) it shouldn't be the default. The word "component" is a bit -overloaded in the frontend world, so for clarify Lustre considers _components_ +overloaded in the frontend world, so for clarity Lustre considers _components_ as stateful nested Model-View-Update applications and calls stateless functions that return `Element`s _view functions_. -- cgit v1.2.3