chore(release): 0.5.0

docs/002. hsmc-semantics-formal.md

@@ -93,8 +93,9 @@ and still nothing handles it, the event is silently discarded.
 
 That's all. Three other things follow from this rule:
 
-- A handler on a leaf state shadows a handler on its ancestor for the same
-  event. The leaf wins because the search starts there.
+- A handler on the innermost active state shadows a handler on any
+  ancestor for the same event. The innermost wins because the search
+  starts there.
 - If a single state has multiple handlers (actions and/or a transition)
   for the same trigger, the actions fire in declaration order, then the
   transition fires last.
@@ -115,8 +116,8 @@ in `statechart! { Foo { ... } }`, an `on(Trig) => Foo;` is a valid
 transition whose target is the root. From any state inside the chart this
 is an up-transition (root is always on the active path) — exiting only
 the states strictly between current and root, with no entry actions and
-no default-descent on root. Use this when you want to wind everything
-back up to the chart's own scope.
+no default firing on root (the root wasn't freshly entered). Use this
+when you want to wind everything back up to the chart's own scope.
 
 To run a transition:
 
@@ -140,8 +141,9 @@ in which steps fire.
 ### Transitioning to a sibling (or anywhere not on your active path)
 
 The standard case. LCA is somewhere strictly above both current and
-target. Exit up to LCA, enter down to target, default-descend from the
-target if it declares a `default`. Already covered above.
+target. Exit up to LCA, enter down to target, then if the target
+declares a `default(...)`, fire it as a chained transition. Already
+covered above.
 
 ### Transitioning to yourself