diff --git a/tidb-lightning/deploy-tidb-lightning.md b/tidb-lightning/deploy-tidb-lightning.md
index 2cdc4e5fe8a77..39aed59f98eac 100644
--- a/tidb-lightning/deploy-tidb-lightning.md
+++ b/tidb-lightning/deploy-tidb-lightning.md
@@ -7,13 +7,12 @@ summary: Deploy TiDB Lightning to quickly import large amounts of new data.
 
 This document describes the hardware requirements of TiDB Lightning using the Local-backend, and how to deploy it manually.
 
-If you do not want the TiDB services to be impacted, read [TiDB Lightning TiDB-backend](/tidb-lightning/tidb-lightning-backends.md#tidb-lightning-tidb-backend) for the changes to the deployment steps.
+If Local-backend is used for data import, during the import process, **the cluster cannot provide services**. If you do not want the TiDB services to be impacted, perform the data import according to [TiDB Lightning TiDB-backend](/tidb-lightning/tidb-lightning-backends.md#tidb-lightning-tidb-backend).
 
 ## Notes
 
 Before starting TiDB Lightning, note that:
 
-- During the import process, the cluster cannot provide normal services.
 - If `tidb-lightning` crashes, the cluster is left in "import mode". Forgetting to switch back to "normal mode" can lead to a high amount of uncompacted data on the TiKV cluster, and cause abnormally high CPU usage and stall. You can manually switch the cluster back to "normal mode" via the `tidb-lightning-ctl` tool:
 
     ```sh
diff --git a/tidb-lightning/tidb-lightning-backends.md b/tidb-lightning/tidb-lightning-backends.md
index 9fe767b3175cd..07f88c877743c 100644
--- a/tidb-lightning/tidb-lightning-backends.md
+++ b/tidb-lightning/tidb-lightning-backends.md
@@ -28,6 +28,7 @@ The **TiDB-backend**: `tidb-lightning` first encodes these data into SQL `INSERT
 | Target tables | Must be empty | Must be empty | Can be populated |
 | Additional component required | No | `tikv-importer` | No |
 | TiDB versions supported | >= v4.0.0 | All | All |
+| TiDB services impacted | Yes | Yes | No |
 
 ## How to choose the backend modes