docs: migration intro edit

documentation/migration-guide.md

@@ -29,12 +29,17 @@ npx markdown-toc documentation/migration-guide.md --maxdepth 2 --bullets="-" -i
 
 ### Overview
 
-A [bi-directional syncing](https://docs.readme.com/main/docs/bi-directional-sync) workflow with [ReadMe Refactored](https://docs.readme.com/main/docs/welcome-to-readme-refactored) mostly eliminates the need for a tool like `rdme`. For syncing Markdown files, syncing API definitions, and managing project hierarchy (e.g., project versions and categories) with ReadMe Refactored, you'll want to set up bi-directional syncing.
+This guide explains how to install `rdme@10` for use with [ReadMe Refactored]{https://docs.readme.com/main/docs/welcome-to-readme-refactored}. In general, we recommend [bi-directional syncing](https://docs.readme.com/main/docs/bi-directional-sync) for tasks like:
 
-`rdme@10` is recommended for the following use cases:
+- Syncing Markdown files
+- Syncing API definitions (and editing them visually with [the API designer](https://docs.readme.com/main/docs/building-apis-from-scratch-with-the-api-designer))
+- Managing project hierarchy (e.g., versions and categories)
 
-- Syncing your API definition (generated via a build process and not tracked via Git) to your ReadMe Refactored-enabled project
-- Syncing Markdown files to the Changelog for your ReadMe Refactored-enabled project
+However `rdme@10` is useful for more targeted workflows—particularly when syncing happens outside of Git, such as:
+
+- A one-directional sync of an API definition (e.g., if it is generated via a build process and/or is not tracked via your bidirectionally synced Git repo)
+- A one-directional sync of Markdown files (e.g., if they are updated via a build process and/or are not tracked via your bidirectionally synced Git repo)
+- Any non-syncing processing for an API definition (e.g., validating it, reducing it a set of fewer operations)
 
 <!-- prettier-ignore-start -->
 > [!NOTE]