diff --git a/tidb-cloud/changefeed-sink-to-apache-kafka.md b/tidb-cloud/changefeed-sink-to-apache-kafka.md
index d29babcc7e609..f7580d4d904ec 100644
--- a/tidb-cloud/changefeed-sink-to-apache-kafka.md
+++ b/tidb-cloud/changefeed-sink-to-apache-kafka.md
@@ -66,14 +66,14 @@ For example, if your Kafka cluster is in Confluent Cloud, you can see [Resources
 ## Step 2. Configure the changefeed target
 
 1. Under **Brokers Configuration**, fill in your Kafka brokers endpoints. You can use commas `,` to separate multiple endpoints.
-2. Select your Kafka version. If you do not know that, use Kafka V2.
-3. Select a desired compression type for the data in this changefeed.
-4. Enable the **TLS Encryption** option if your Kafka has enabled TLS encryption and you want to use TLS encryption for the Kafka connection.
-5. Select the **Authentication** option according to your Kafka authentication configuration.
+2. Select an authentication option according to your Kafka authentication configuration.
 
-    - If your Kafka does not require authentication, keep the default option **DISABLE**.
+    - If your Kafka does not require authentication, keep the default option **Disable**.
     - If your Kafka requires authentication, select the corresponding authentication type, and then fill in the user name and password of your Kafka account for authentication.
 
+3. Select your Kafka version. If you do not know that, use Kafka V2.
+4. Select a desired compression type for the data in this changefeed.
+5. Enable the **TLS Encryption** option if your Kafka has enabled TLS encryption and you want to use TLS encryption for the Kafka connection.
 6. Click **Next** to check the configurations you set and go to the next page.
 
 ## Step 3. Set the changefeed
diff --git a/tidb-cloud/tidb-cloud-billing-dm.md b/tidb-cloud/tidb-cloud-billing-dm.md
index fe2f799576f47..ab7dbb0a4f3ed 100644
--- a/tidb-cloud/tidb-cloud-billing-dm.md
+++ b/tidb-cloud/tidb-cloud-billing-dm.md
@@ -11,16 +11,21 @@ This document describes the billing for Data Migration in TiDB Cloud.
 
 TiDB Cloud measures the capacity of Data Migration in Replication Capacity Units (RCUs). When you create a Data Migration job, you can select an appropriate specification. The higher the RCU, the better the migration performance. You will be charged for these Data Migration RCUs.
 
-The following table lists the specifications and corresponding performances for Data Migration.
+The following table lists the corresponding performance and the maximum number of tables that each Data Migration specification can migrate.
 
-| Specification | Full data migration | Incremental data migration |
-|---------------|---------------------|----------------------------|
-| 2 RCUs  | 25 MiB/s | 10,000 rows/s|
-| 4 RCUs  | 35 MiB/s | 20,000 rows/s|
-| 8 RCUs  | 40 MiB/s | 40,000 rows/s|
-| 16 RCUs | 45 MiB/s | 80,000 rows/s|
+| Specification | Full data migration | Incremental data migration | Maximum number of tables |
+|---------------|---------------------|----------------------------|-----------------------|
+| 2 RCUs  | 25 MiB/s | 10,000 rows/s | 500   |
+| 4 RCUs  | 35 MiB/s | 20,000 rows/s | 10000 |
+| 8 RCUs  | 40 MiB/s | 40,000 rows/s | 30000 |
+| 16 RCUs | 45 MiB/s | 80,000 rows/s | 60000 |
 
-Note that all the performance values in this table are maximum performances. It is assumed that there are no performance, network bandwidth, or other bottlenecks in the upstream and downstream databases. The performance values are for reference only and might vary in different scenarios.
+For more information about the prices of Data Migration RCUs, see [Data Migration Cost](https://www.pingcap.com/tidb-dedicated-pricing-details/#dm-cost).
+
+> **Note:**
+>
+> - If the number of tables to be migrated exceeds the maximum number of tables, the Data Migration job might still run, but the job could become unstable or even fail.
+> - All the performance values in this table are maximum and optimal ones. It is assumed that there are no performance, network bandwidth, or other bottlenecks in the upstream and downstream databases. The performance values are for reference only and might vary in different scenarios.
 
 The Data Migration job measures full data migration performance in MiB/s. This unit indicates the amount of data (in MiB) that is migrated per second by the Data Migration job.