added the highlight (#3507)

Co-authored-by: Iain Cox <[email protected]>

_partials/_migrate_pg_dump_do_not_recommend_for_large_migration.md

@@ -1,7 +1,7 @@
 
-If you want to migrate more than 400GB of data, create a [Timescale Console support request][support-link], or 
+<Highlight type="important">
+If you want to migrate more than 400GB of data, create a [Timescale Console support request](https://console.cloud.timescale.com/dashboard/support), or 
 send us an email at [[email protected]](mailto:[email protected]) saying how much data you want to migrate. We will pre-provision 
 your Timescale Cloud instance for you.
+</Highlight>
 
-[live migration]: /migrate/:currentVersion:/live-migration
-[support-link]: https://console.cloud.timescale.com/dashboard/support

migrate/live-migration.md

@@ -26,6 +26,8 @@ your target Timescale Cloud service, then replicates the database activity in yo
 
 You use the live-migration Docker image to move 100GB-10TB+ of data to a Timescale Cloud service seamlessly with only a few minutes downtime.
 
+<DoNotRecommendForLargeMigration />
+
 Best practice is to use live-migration when:
 - Modifying your application logic to perform dual writes is a significant effort. 
 - The insert workload does not exceed 20,000 rows per second, and inserts are batched.
@@ -38,8 +40,6 @@ Best practice is to use live-migration when:
   - Has large, busy tables with primary keys.
   - Does not have many `UPDATE` or `DELETE` statements.
 
-<DoNotRecommendForLargeMigration />
-
 This page shows you how to move your data from a self-hosted database to a Timescale Cloud service using
 the live-migration Docker image.