Skip to content

Commit 11dbff7

Browse files
authored
Fix typo
1 parent 2087912 commit 11dbff7

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

use-case-statecharts-in-user-interfaces.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -146,7 +146,7 @@ var stateMachine = new xstate.Machine({
146146
147147
One thing to note is that in state machines, and statecharts, events are given explicit names. For our simple example I called the event `change`.
148148
149-
Now, this `stateMachine` variable provides a _pure functional_ interface to the state machine. This means that this state machine cannot and wiil not have side effects. Every time you use it, you tell it what the "current" state is, the event (what "happens"), and _it_ tells you what happened.
149+
Now, this `stateMachine` variable provides a _pure functional_ interface to the state machine. This means that this state machine cannot and will not have side effects. Every time you use it, you tell it what the "current" state is, the event (what "happens"), and _it_ tells you what happened.
150150
151151
We start off our state machine by asking the state machine what the "initial" state is:
152152

0 commit comments

Comments
 (0)