Merge remote-tracking branch 'upstream/main' into migration-input-output

Author: rlaffers

.vscode/settings.json

@@ -0,0 +1,3 @@
+{
+  "editor.wordWrap": "on"
+}

blog/2023-05-12-office-hours-64/index.mdx

@@ -25,7 +25,7 @@ Two weeks ago, we had what some have called our “best office hours yet.” We
 
 <!--truncate-->
 
-We also talk about XState v5 being in beta (more on that soon!) and [how to migrate from XState V4 to V5](https://stately.ai/docs/xstate-v5/migration).
+We also talk about XState v5 being in beta (more on that soon!) and [how to migrate from XState V4 to V5](https://stately.ai/docs/migration).
 
 <YouTube id="FY030no59Y4" />
 

blog/2023-05-16-stately-streams/index.mdx

@@ -1,7 +1,7 @@
 ---
 title: Watch in-depth demos in our Stately Streams
-description: Tomorrow is part four in our popular Stately Stream series, where we are modeling a semi-complex client-side application using XState, Stately Studio, React and TypeScript. 
-tags: [stately, studio, xstate, xstate v5, stately stream, demo, examples ]
+description: Tomorrow is part four in our popular Stately Stream series, where we are modeling a semi-complex client-side application using XState, Stately Studio, React and TypeScript.
+tags: [stately, studio, xstate, xstate v5, stately stream, demo, examples]
 authors: [farzad]
 date: 2023-05-16
 slug: stately-streams-may-2023
@@ -16,22 +16,22 @@ Across this series, David and I have been working on a canvas-based app project
 
 In part 1 we look at the power of using statecharts to model and implement a canvas-based app.
 
-<YouTube id="9xIgDYAUfBc"/>
+<YouTube id="9xIgDYAUfBc" />
 
 ## Part 2
 
 In part 2, we look at implementing multiple selection, including collision detection and what you might need for live collaboration.
 
-<YouTube id="kYj4UsLfmlg?"/>
+<YouTube id="kYj4UsLfmlg?" />
 
 ## Part 3
 
-In part 3, we migrate our code from XState V4 to [XState V5](https://stately.ai/docs/xstate-v5/migration).
+In part 3, we migrate our code from XState V4 to [XState V5](https://stately.ai/docs/migration).
 
-<YouTube id="mgeFXyIr9iw?"/>
+<YouTube id="mgeFXyIr9iw?" />
 
 ## Watch part 4 tomorrow at 6.30 PM ET
 
 Join us tomorrow at 6.30 PM ET on YouTube or [LinkedIn](https://www.linkedin.com/events/statelystream-modelingagraphica7064177817600581634/) for our next live stream!
 
-<YouTube id="sigMw-Xelvw?"/>
+<YouTube id="sigMw-Xelvw?" />

blog/2023-05-18-explain-your-machines-with-annotations/index.mdx

@@ -1,6 +1,6 @@
 ---
 title: Explain your machines with annotations
-description: Sometimes you want to share a machine with descriptive details or comments, so we’ve added annotations to Stately Studio. 
+description: Sometimes you want to share a machine with descriptive details or comments, so we’ve added annotations to Stately Studio.
 tags: [stately, studio, annotations, comments, teams]
 authors: [laura]
 publishedAt: 2023-05-18
@@ -18,9 +18,12 @@ Unlike [descriptions](https://stately.ai/docs/descriptions), annotations are not
 
 [Check out the dog walk machine below](https://stately.ai/registry/editor/embed/5b170468-d66a-4136-84c8-676c8fea82e8?machineId=7879be19-d267-4e75-9a7d-6a870d540257), which I’ve annotated with notes describing the machine and how some of the states work.
 
-<EmbedMachine name="Annotated dog walk machine" embedURL="https://stately.ai/registry/editor/embed/5b170468-d66a-4136-84c8-676c8fea82e8?machineId=7879be19-d267-4e75-9a7d-6a870d540257" />
+<EmbedMachine
+  name="Annotated dog walk machine"
+  embedURL="https://stately.ai/registry/editor/embed/5b170468-d66a-4136-84c8-676c8fea82e8?machineId=7879be19-d267-4e75-9a7d-6a870d540257"
+/>
 
-*You can now also [embed your machines anywhere `iframe`s are supported](https://stately.ai/docs/xstate-v5/embed)!*
+_You can now also [embed your machines anywhere `iframe`s are supported](https://stately.ai/docs/embed)!_
 
 Annotations are not exported when you [export your machine as code](https://stately.ai/docs/export-as-code), so you can add as many as you like without affecting your codebase!
 

blog/2023-05-25-announcing-xstate-v5-beta/index.mdx

@@ -26,8 +26,8 @@ Over the past few years, we have collected a wealth of valuable feedback from th
 
 One of the biggest items of feedback we’ve received about XState is that although it is powerful, there is a substantial learning curve. There are some ~~new~~ old concepts to learn with XState, such as the actor model, state machines, and statecharts. With these concepts comes new terminology. In XState v5 beta and [the documentation](https://stately.ai/docs/xstate-v5), we have made a concerted effort to make XState as approachable as possible, and to reduce the learning curve as much as possible. Here are some of the changes we’ve made:
 
-- **Simplified terminology**. Concepts shouldn’t have multiple names, so we have simplified terms wherever possible. The basic unit of abstraction in XState v5 beta is the **actor**, and we’ve removed some of the more confusing terms, such as “service” and “interpreter,” “transient transitions” to “eventless transitions,” “cond” to “guard", “internal: false” to “reenter: true,” and [more](https://stately.ai/docs/xstate-v5/migration).
-- **Reduced API surface area**. Some of the new features, such as [input](#actor-input) made existing features redundant, such as `machine.withContext(...)`. We’ve also removed redundant functionality, such as `actor.onTransition(...)`, in favor of `actor.subscribe(...)`. [Read about all the breaking changes](https://stately.ai/docs/xstate-v5/migration).
+- **Simplified terminology**. Concepts shouldn’t have multiple names, so we have simplified terms wherever possible. The basic unit of abstraction in XState v5 beta is the **actor**, and we’ve removed some of the more confusing terms, such as “service” and “interpreter,” “transient transitions” to “eventless transitions,” “cond” to “guard", “internal: false” to “reenter: true,” and [more](https://stately.ai/docs/migration).
+- **Reduced API surface area**. Some of the new features, such as [input](#actor-input) made existing features redundant, such as `machine.withContext(...)`. We’ve also removed redundant functionality, such as `actor.onTransition(...)`, in favor of `actor.subscribe(...)`. [Read about all the breaking changes](https://stately.ai/docs/migration).
 - **Examples, examples, examples**. We’re adding many [XState v5 beta examples in the XState repository’s examples folder](https://github.com/statelyai/xstate/tree/next/examples) to help you quickly understand how XState can help with your use cases.
 - **Interactive documentation**. We’re working on adding interactive examples to the documentation, so you can visualize the concepts as you learn them.
 - **From zero to “hello world” as quickly as possible**. Our goal with XState v5 and the [updated documentation (work in progress)](https://stately.ai/docs/xstate-v5) is to make developers productive with XState quickly. A simple, complete counter example in XState looks like this:
@@ -388,7 +388,7 @@ For more examples, [visit the `/examples` directory in the XState repository](ht
 
 ## Migration and breaking changes
 
-As with any major version, there are some breaking changes. We’ve tried to keep these to a minimum, but some are necessary to make XState v5 beta as powerful and flexible as possible. [Read our current guide for migrating from XState v4 to v5 and the list of breaking changes](https://stately.ai/docs/xstate-v5/migration).
+As with any major version, there are some breaking changes. We’ve tried to keep these to a minimum, but some are necessary to make XState v5 beta as powerful and flexible as possible. [Read our current guide for migrating from XState v4 to v5 and the list of breaking changes](https://stately.ai/docs/migration).
 
 ## In progress