docs: reorder pages (#1151)

apps/docs/content/docs/migrations/deprecation-policy.mdx

@@ -8,7 +8,7 @@ Rarely, we need to deprecate a feature we've already shipped, because it is caus
 In such cases, we will communicate the intent to unship as soon as possible by marking the feature as `@deprecated` and publishing a notice in the documentation.
 
 Deprecations and breaking changes primarily affect new features released. The longer an API has been in the library, the less likely it is to be deprecated.
-For features that have long existed in the library, we will provider a longer deprecation notice period (as described below).
+For features that have long existed in the library, we will provide a longer deprecation notice period (as described below).
 
 Below is a list of features considered stable and those considered experimental.
 
@@ -17,11 +17,11 @@ Below is a list of features considered stable and those considered experimental.
 These features may be removed at any time without notice.
 
 - Anything marked as `unstable_`, `experimental_`, or `internal`
-- The `RuntimeCore` API (conisdered internal)
+- The `RuntimeCore` API (considered internal)
 
 ## Beta Features
 
-A deprecation of this features will undergo a short (<1) month deprecation notice period.
+A deprecation of these features will undergo a short (<1) month deprecation notice period.
 
 - TailwindCSS Plugins (e.g. `@assistant-ui/react/tailwindcss`)
 - Context API
@@ -34,7 +34,7 @@ A deprecation of this features will undergo a short (<1) month deprecation no
 
 ## Stable Features
 
-A deprecation of this features will undergo a long (>3 month) deprecation notice period.
+A deprecation of these features will undergo a long (>3 month) deprecation notice period.
 
 The following features are considered stable:
 

apps/docs/content/docs/migrations/v0-7.mdx

@@ -4,9 +4,9 @@ title: Migration to v0.7
 
 import { Callout } from "fumadocs-ui/components/callout";
 
-This guide serves as a reference for users facing breaking changes during upgrade to v0.6. You do not need to read this guide to upgrade to v0.6.
+This guide serves as a reference for users facing breaking changes during upgrade to v0.7. You do not need to read this guide to upgrade to v0.7.
 
-All breaking changes in v0.6 are renames or removals of existing APIs. Therefore, all breaking changes should cause a Typescript error, so you can simply check for errors after upgrading.
+All breaking changes in v0.7 are renames or removals of existing APIs. Therefore, all breaking changes should cause a Typescript error, so you can simply check for errors after upgrading.
 
 # Component Property Types moved to `Component.Props`