Merge pull request #2387 from aiven/reduce-content

Delete in-text label and shorten content

docs/platform/howto/manage-vpc-peering.rst

@@ -83,18 +83,19 @@ Also note that safelisting applies to both internal and external traffic. If you
 Troubleshoot VPC connection issues
 ----------------------------------
 
-Any network changes to VPC peered hosts external from Aiven can cause issues with routing to your Aiven services hosted in a VPC. To troubleshoot such issues, :ref:`refresh VPC connections <refresh-vcp-connections>`.
+Any network changes to VPC peered hosts external from Aiven can cause issues with routing to your Aiven services hosted in a VPC.
+In such case, try to refresh your VPC connections.
 
-Changes to your VPCs (such as adding a new subnet) can take up to 24 hours to take effect. There's no need to troubleshoot issues with your changes not applied unless it's been over 24 hours since you introduced the changes. You can always request the application of your changes by :ref:`refreshing VPC connections <refresh-vcp-connections>`.
-
-.. _refresh-vcp-connections:
+.. note::
+ 
+   Changes to your VPCs (such as adding a new subnet) can take up to 24 hours to take effect so wait at least 24h before refreshing your VPC connections.
 
-To refresh VCP connections, take the following steps:
+To refresh your VCP connections:
 
 1. In `Aiven Console <https://console.aiven.io/>`_, select **VPCs**.
 2. Find the ID of the affected VPC and select it from the **Internal ID** column.
 3. Select **Refresh VPC connections**.
 
-As a result, the platform checks the VPC peering connection and rebuilds the peering connection state if there are any changes detected.
+The platform checks the VPC peering connection and rebuilds the peering connection state if there are any changes detected.
 
 For any other issues, open a support ticket from `Aiven Console <https://console.aiven.io/>`_ to get in touch with the support team and/or see :doc:`Get support in the Aiven Console </docs/platform/howto/project-support-center>`.

docs/products/mysql/howto/migrate-db-to-aiven-via-console.rst

@@ -16,15 +16,14 @@ The console migration tool enables you to migrate MySQL databases to managed MyS
 * Cloud-hosted MySQL databases
 * Managed MySQL database clusters on Aiven.
 
-With the console migration tool, you can migrate your data using either the :ref:`continuous migration method <continuous-migration>` (default and recommended) or the :ref:`one-time snapshot method <mysqldump-migration>` (``mysqldump``).
+The console migration tool provides 2 migration methods:
 
-.. _continuous-migration:
+- **(Recommended) Continuous migration:** Used by default in the tool and taken as a method to follow in this guide. This method uses logical replication so that data transfer is possible not only for existing data in the source database when triggering the migration but also for any data written to the source database during the migration.
 
-* Recommended continuous migration method is used by default in the tool and taken as a method to follow in this guide. This method uses logical replication so that data transfer is possible not only for the data that has already been there in the source database when triggering the migration but also for any data written to the source database during the migration.
+- **mysqldump**: Exports the current contents of the source database into a text file and imports it to the target database.
+  Any changes written to the source database during the migration are **not transferred**. 
 
-.. _mysqldump-migration:
-
-* ``mysqldump`` exports current contents of the source database into a text file and imports it to the target database. Any changes written to the source database during the migration are not transferred. When you trigger the migration setup in the console and initial checks detect that your source database does not support the logical replication, you are notified about it via wizard. To continue with the migration, you can select the alternative ``mysqldump`` migration method in the wizard.
+  When you trigger the migration setup in the console and initial checks detect that your source database does not support the logical replication, you are notified about it via the migration wizard. To continue with the migration, you can select the alternative ``mysqldump`` migration method in the wizard.
 
 Prerequisites
 -------------
@@ -164,12 +163,12 @@ Step 3 - migration
 
 If all the checks pass with no error messages, you can trigger the migration by selecting **Start migration**.
 
+.. _stop-migration-mysql:
+
 Step 4 - replicating
 ''''''''''''''''''''
 
-.. _stop-migration-mysql:
-
-While the migration is in progress, you can
+While the migration is in progress, you can:
 
 * Let it proceed until completed by selecting **Close window**, which closes the wizard. You come back to check the status at any time.
 * Discontinue the migration by selecting **Stop migration**, which retains the data already migrated. For information on how to follow up on a stopped migration process, see :ref:`Start over <start-over-mysql>`.