aboutsummaryrefslogtreecommitdiff
path: root/pages
diff options
context:
space:
mode:
authorMike Fitzgerald <mike@xpressivecode.com>2024-05-14 07:24:38 +0200
committerGitHub <noreply@github.com>2024-05-14 07:24:38 +0200
commit90a665d18e393d4084a4634a0677b9d8108569db (patch)
tree81a91cc8d9024add834dc9882d9c07dccead873c /pages
parent05d86d928e6276d8f40d7d0e6939cb5eae03313d (diff)
downloadlustre-90a665d18e393d4084a4634a0677b9d8108569db.tar.gz
lustre-90a665d18e393d4084a4634a0677b9d8108569db.zip
🔀 Quick typo fix, (#127)
Diffstat (limited to 'pages')
-rw-r--r--pages/guide/02-state-management.md2
1 files changed, 1 insertions, 1 deletions
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_.