Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Fix broken links #56

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions _glossary/enter.md
Original file line number Diff line number Diff line change
Expand Up @@ -7,10 +7,10 @@ redirect_from:

# Enter

Refers to the act of _entering a state_ during the execution of a state machine. The state machine keeps track of which state is [active](active.html){:.glossary} and its behaviour is defined based on the active state(s). A state may declare entry [actions](action.html){:.glossary}, which will be executed when a state is entered.
Refers to the act of _entering a state_ during the execution of a state machine. The state machine keeps track of which state is active and its behaviour is defined based on the active state(s). A state may declare entry [actions](action.html){:.glossary}, which will be executed when a state is entered.

If a state is a [compound state](compound-state.html){:.glossary}, the defined [initial state](initial-state.html){:.glossary} is also entered, since in an active compound state, exactly one substate must also be active.

If a state is a [parallel state], each region and their initial states will also be entered.
If a state is a [parallel state](parallel-state.html){:.glossary}, each region and their initial states will also be entered.

Entry of a state is defined to be instantaneous for all practical purposes; this includes the execution of any entry actions, and the entry of all substates. In other words, a state can never be "half entered" or "half active".
5 changes: 2 additions & 3 deletions _glossary/final-state.md
Original file line number Diff line number Diff line change
Expand Up @@ -14,8 +14,7 @@ The "completion" of a state is wholly defined by the statechart itself.

## Notation

Final states are depicted using a solid filled circle, like the [initial state](initial-state.html){:.glossary} with an additional circle enclosing it. Transitions from the final state must be [automatic], in other words they can not rely on events.

Final states are depicted using a solid filled circle, like the [initial state](initial-state.html){:.glossary} with an additional circle enclosing it. Transitions from the final state must be [automatic](automatic-transition.html){:.glossary}, in other words they can not rely on events.

## SCXML

Expand All @@ -31,4 +30,4 @@ resolved: {
}
```

See [xstate.js.org/docs/guides/final](https://xstate.js.org/docs/guides/final/) for more information.
See [xstate.js.org/docs/guides/final.html](https://xstate.js.org/docs/guides/final.html) for more information.
2 changes: 1 addition & 1 deletion _glossary/local-transition.md
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ on {

Important to note that `internal: false` is the default, taking the lead from SCXML.

See [xstate.js.org/docs/guides/internal](https://xstate.js.org/docs/guides/internal/) for more information.
See [xstate.js.org/docs/guides/transitions.html#internal-transitions](https://xstate.js.org/docs/guides/transitions.html#internal-transitions) for more information.

## SCXML

Expand Down