DOCSP-45622-remove-unsupported-scenario (#184)

Author: jeff-allen-mongo

source/getting-started/migration-scenarios.txt

@@ -51,27 +51,13 @@ the new application and shut down the legacy application.
 
 To learn more about migration jobs, see :ref:`rm-sync-jobs`.
 
-Currently Unsupported Migration Scenarios
------------------------------------------
+Unsupported Migration Scenarios
+-------------------------------
 
-Relational Migrator currently does not support the following migration
-scenarios:
-
-- Migrating multiple applications through a phased migration without
-  downtime. In this scenario, multiple legacy applications are
-  decommissioned and migrated to the new database while the original
-  database still supports writes. The migration uses :abbr:`CDC (Change
-  Data Capture)` to keep the legacy application in sync with the
-  destination database.
-
-- Migrating an operational data store. Depending on your workload, this
-  scenario could involve :abbr:`CDC (Change Data Capture)` running
-  indefinitely without completing.
-
-The preceding scenarios require long-running :abbr:`CDC (Change Data
-Capture)`, or in some cases involve :abbr:`CDC (Change Data Capture)`
-running indefinitely. Therefore, these scenarios are not recommended
-with Relational Migrator.
+Relational Migrator currently does not support migrating an operational
+data store. Depending on your workload, migrating a data store could
+cause :abbr:`CDC (Change Data Capture)` to run indefinitely without
+completing, which is not recommended with Relational Migrator.
 
 Relational Migrator will support more migration scenarios and use cases
 in future releases.