aboutsummaryrefslogtreecommitdiff
path: root/examples/03-controlled-inputs
diff options
context:
space:
mode:
authorEileen Noonan <enoonan@arcstone.com>2024-03-22 15:26:14 -0400
committerGitHub <noreply@github.com>2024-03-22 19:26:14 +0000
commit1d8d13d766b6467188cbded28d103ffb13421c77 (patch)
treeebfb5ed7e62463b6392a6f133ae675b65e97ac0c /examples/03-controlled-inputs
parente85bc4729a15d9af5af5345151178afe849036ba (diff)
downloadlustre-1d8d13d766b6467188cbded28d103ffb13421c77.tar.gz
lustre-1d8d13d766b6467188cbded28d103ffb13421c77.zip
🔀 Write a readme for example 04-custom-event-handlers. (#72)
* readme for example 04 * Update README.md tweaks
Diffstat (limited to 'examples/03-controlled-inputs')
-rw-r--r--examples/03-controlled-inputs/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/examples/03-controlled-inputs/README.md b/examples/03-controlled-inputs/README.md
index 4696c6d..fcbbb1f 100644
--- a/examples/03-controlled-inputs/README.md
+++ b/examples/03-controlled-inputs/README.md
@@ -31,7 +31,7 @@ ui.input([
Central to Lustre's architecture is the idea that your model is the single source
of truth for your application's UI. This opens up the door to things like serialising
-progam state to load in the future, time-travel debugging, and rehydrating your
+program state to load in the future, time-travel debugging, and rehydrating your
app's state from a server.
It also gives you tighter control of when and how to update your UI in response