resolve conflicts

Signed-off-by: Aolin <[email protected]>

migration-tools.md

@@ -42,14 +42,12 @@ This document introduces the user scenarios, supported upstreams and downstreams
 
 ## [TiCDC](/ticdc/ticdc-overview.md)
 
-- **User scenario**: This tool is implemented by pulling TiKV change logs. It can restore cluster data to a consistent state with any upstream TSO, and support other systems to subscribe to data changes.
-- **Upstream**: TiDB
-- **Downstream**: TiDB, MySQL, Kafka, MQ, Confluent, storage services such as Amazon S3, GCS, Azure Blob Storage, and NFS.
-- **Advantages**: Provide TiCDC Open Protocol
-- **Limitation**: TiCDC only replicates tables that have at least one valid index. The following scenarios are not supported:
-    - The TiKV cluster that uses RawKV alone.
-    - The DDL operation `CREATE SEQUENCE` and the `SEQUENCE` function in TiDB.
-
+| User scenario | <span style="font-weight:normal">This tool is implemented by pulling TiKV change logs. It can restore cluster data to a consistent state with any upstream TSO, and support other systems to subscribe to data changes.</span> |
+|---|---|
+| **Upstream** | TiDB |
+| **Downstream** | TiDB, MySQL, Kafka, MQ, Confluent, storage services such as Amazon S3, GCS, Azure Blob Storage, and NFS. |
+| **Advantages** | Provide TiCDC Open Protocol |
+| **Limitation** | TiCDC only replicates tables that have at least one valid index. The following scenarios are not supported:<ul><li>The TiKV cluster that uses RawKV alone.</li><li>The DDL operation `CREATE SEQUENCE` and the `SEQUENCE` function in TiDB.</li></ul> |
 ## [Backup & Restore (BR)](/br/backup-and-restore-overview.md)
 
 | User scenario | <span style="font-weight:normal">Migrate a large amount of TiDB cluster data by backing up and restoring data</span> |