diff --git a/dm/dm-faq.md b/dm/dm-faq.md
index ae3c9547c2a9b..8d221dec44350 100644
--- a/dm/dm-faq.md
+++ b/dm/dm-faq.md
@@ -230,7 +230,7 @@ If this issue occurs, you need to pause the task, delete all migrated data in th
 
 You can avoid this issue in advance by configuring in the following ways:
 
-1. Increase the value of `expire_logs_days` in the upstream MySQL database to avoid wrongly purging needed binlog files before the full migration task completes. If the data volume is large, it is recommended to use dumpling and TiDB-Lightning at the same time to speed up the task.
+1. Increase the value of `expire_logs_days` in the upstream MySQL database to avoid wrongly purging needed binlog files before the full migration task completes. If the data volume is large, it is recommended to use Dumpling and TiDB Lightning at the same time to speed up the task.
 2. Enable the relay log feature for this task so that DM can read data from relay logs even though the binlog position is purged.
 
 ## Why does the Grafana dashboard of a DM cluster display `failed to fetch dashboard` if the cluster is deployed using TiUP v1.3.0 or v1.3.1?
diff --git a/get-started-with-tidb-lightning.md b/get-started-with-tidb-lightning.md
index 8bd0a04326907..f22ffb9ecebec 100644
--- a/get-started-with-tidb-lightning.md
+++ b/get-started-with-tidb-lightning.md
@@ -13,7 +13,7 @@ This document provides a quick guide on getting started with TiDB Lightning by i
 
 ## Step 1: Prepare full backup data
 
-First, you can use [dumpling](/dumpling-overview.md) to export data from MySQL.
+First, use [Dumpling](/dumpling-overview.md) to export data from MySQL.
 
 1. Run `tiup --version` to check if TiUP is already installed. If TiUP is installed, skip this step. If TiUP is not installed, run the following command:
 
diff --git a/releases/release-4.0.3.md b/releases/release-4.0.3.md
index 81ab47b39a366..66c69c0400075 100644
--- a/releases/release-4.0.3.md
+++ b/releases/release-4.0.3.md
@@ -127,7 +127,7 @@ TiDB version: 4.0.3
     - Fix the issue that `getSchedulers` might cause a data race [#2638](https://github.com/pingcap/pd/pull/2638)
     - Fix the issue that deleting the scheduler might cause deadlocks [#2637](https://github.com/pingcap/pd/pull/2637)
     - Fix the bug that placement rules are not considered when `balance-leader-scheduler` is enabled [#2636](https://github.com/pingcap/pd/pull/2636)
-    - Fix the issue that sometimes service `safepoint` cannot be set properly, which might make BR and dumpling fail [#2635](https://github.com/pingcap/pd/pull/2635)
+    - Fix the issue that sometimes service `safepoint` cannot be set properly, which might make BR and Dumpling fail [#2635](https://github.com/pingcap/pd/pull/2635)
     - Fix the issue that the target store in `hot region scheduler` is incorrectly selected [#2627](https://github.com/pingcap/pd/pull/2627)
     - Fix the issue that the TSO request might take too long when PD leader is switched [#2622](https://github.com/pingcap/pd/pull/2622)
     - Fix the issue of stale scheduler after leader change [#2608](https://github.com/pingcap/pd/pull/2608)