Update wording

tidb-lightning/tidb-lightning-physical-import-mode.md

@@ -74,7 +74,7 @@ It is recommended that you allocate CPU more than 32 cores and memory greater th
 
 - Do not use the physical import mode to directly import data to TiDB clusters in production. It has severe performance implications. If you need to do so, refer to [Pause scheduling on the table level](/tidb-lightning/tidb-lightning-physical-import-mode-usage.md#scope-of-pausing-scheduling-during-import).
 - If your TiDB cluster has a latency-sensitive application and a low concurrency, it is strongly recommended that you **do not** use the physical import mode to import data into the cluster. This mode might have significant impact on the online application.
-- Generally, **do not** run multiple TiDB Lightning instances simultaneously to import data into the same TiDB cluster. Instead, [import data in parallel](/tidb-lightning/tidb-lightning-distributed-import.md).
+- If you want to run multiple TiDB Lightning instances simultaneously to import data into the same TiDB cluster, enable [parallel import](/tidb-lightning/tidb-lightning-distributed-import.md).
 - When you use multiple TiDB Lightning to import data to the same target cluster, do not mix the import modes. That is, do not use the physical import mode and the logical import mode at the same time.
 - During the process of importing data, do not perform DDL and DML operations in the target table. Otherwise the import will fail or the data will be inconsistent. At the same time, it is not recommended to perform read operations, because the data you read might be inconsistent. You can perform read and write operations after the import operation is completed.
 - A single Lightning process can import a single table of 10 TiB at most. Parallel import can use 10 Lightning instances at most.