cloud: update a few steps for connection and migration

tidb-cloud/import-with-mysql-cli-serverless.md

@@ -67,7 +67,7 @@ Do the following to import data from an SQL file:
 2. Use the following command to import data from the SQL file:
 
     ```bash
-    mysql --comments --connect-timeout 150 -u '<your_username>' -h <your_cluster_host> -P 4000 -D test --ssl-mode=VERIFY_IDENTITY --ssl-ca=<your_ca_path> -p <your_password> < product_data.sql
+    mysql --comments --connect-timeout 150 -u '<your_username>' -h <your_cluster_host> -P 4000 -D test --ssl-mode=VERIFY_IDENTITY --ssl-ca=<your_ca_path> -p<your_password> < product_data.sql
     ```
 
 > **Note:**

tidb-cloud/import-with-mysql-cli.md

@@ -20,9 +20,13 @@ Connect to your TiDB cluster.
 
 1. Navigate to the [**Clusters**](https://tidbcloud.com/console/clusters) page, and then click the name of your target cluster to go to its overview page.
 
-2. Click **Connect** in the upper-right corner. A connection dialog is displayed.
+2. In the left navigation pane, click **Networking**.
 
-3. Click **Allow Access from Anywhere**.
+3. On the **Networking** page, click **Add IP Address** in the **IP Access List** area.
+
+4. In the dialog, choose **Allow access from anywhere**, and then click **Confirm**.
+
+5. In the upper-right corner, click **Connect** to open the dialog for connection information.
 
     For more details about how to obtain the connection string, see [Connect to TiDB Cloud Dedicated via Public Connection](/tidb-cloud/connect-via-standard-connection.md).
 
@@ -59,7 +63,7 @@ Do the following to import data from an SQL file:
 2. Use the following command to import data from the SQL file:
 
     ```bash
-    mysql --comments --connect-timeout 150 -u '<your_username>' -h <your_cluster_host> -P 4000 -D test --ssl-mode=VERIFY_IDENTITY --ssl-ca=<your_ca_path> -p <your_password> < product_data.sql
+    mysql --comments --connect-timeout 150 -u '<your_username>' -h <your_cluster_host> -P 4000 -D test --ssl-mode=VERIFY_IDENTITY --ssl-ca=<your_ca_path> -p<your_password> < product_data.sql
     ```
 
 > **Note:**

tidb-cloud/migrate-from-mysql-using-data-migration.md

@@ -145,7 +145,14 @@ If your MySQL service is in a Google Cloud VPC, take the following steps:
 
 ### Enable binary logs
 
-To perform incremental data migration, make sure you have enabled binary logs of the upstream database, and the binary logs have been kept for more than 24 hours.
+To perform incremental data migration, make sure the following requirements are met:
+
+- Binary logs are enabled for the upstream database.
+- The binary logs are retained for at least 24 hours.
+- The binlog format for the upstream database is set to `ROW`. If not, update the format to `ROW` as follows to avoid the [format error](/tidb-cloud/tidb-cloud-dm-precheck-and-troubleshooting.md#error-message-check-whether-mysql-binlog_format-is-row):
+
+    - MySQL: execute the `set global binlog_format=ROW;` statement.
+    - AWS Aurora (MySQL) or RDS MySQL: follow the instructions in [AWS documentation](https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/USER_WorkingWithDBInstanceParamGroups.html) to create a new DB parameter group. Set the `binlog_format=row` parameter in the new DB parameter group, modify the instance to use the new DB parameter group, and then restart the instance to take effect.
 
 ## Step 1: Go to the **Data Migration** page