Update descriptions

pingcap · Apr 28, 2023 · dfac7b6 · dfac7b6
1 parent 2e4f0a8
commit dfac7b6
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/tidb-lightning/tidb-lightning-distributed-import.md b/tidb-lightning/tidb-lightning-distributed-import.md
@@ -184,13 +184,13 @@ If one or more TiDB Lightning nodes exit abnormally during a parallel import, id
 
 - If the error has no impact on data accuracy, for example, network timeout, perform the following steps:
 
-    1. Run the [`checkpoint-error-ignore`](/tidb-lightning/tidb-lightning-checkpoints.md#--checkpoint-error-ignore) command on all failed nodes to clean errors in the checkpoint source data.
+    1. Run the [`checkpoint-error-ignore`](/tidb-lightning/tidb-lightning-checkpoints.md#--checkpoint-error-ignore) command with the setting `--checkpoint-error-ignore=all` on all failed nodes to clean errors in the checkpoint source data.
 
     2. Restart these nodes to continue importing data from checkpoints.
 
 - If you see errors in the log that result in data inaccuracies, such as a checksum mismatch indicating invalid data in the source file, you can perform the following steps to resolve this issue:
 
-    1. Run the [`checkpoint-error-destroy`](/tidb-lightning/tidb-lightning-checkpoints.md#--checkpoint-error-destroy) command on all Lightning nodes, including successful nodes, to remove the imported data from failed tables and reset the checkpoint status of these tables to "not yet started".
+    1. Run the [`checkpoint-error-destroy`](/tidb-lightning/tidb-lightning-checkpoints.md#--checkpoint-error-destroy) command on all Lightning nodes, including successful nodes. This command removes the imported data from failed tables and resets the checkpoint status of these tables to "not yet started".
 
     2. Reconfigure and import the data of failed tables by using the [`filter`](/table-filter.md) parameter on all TiDB Lightning nodes, including normally exiting nodes.