diff --git a/docs/cn/dledger/quick_start.md b/docs/cn/dledger/quick_start.md
index 8311395d993..2017461af06 100644
--- a/docs/cn/dledger/quick_start.md
+++ b/docs/cn/dledger/quick_start.md
@@ -61,7 +61,7 @@ $ sh bin/dledger/fast-try.sh stop
 
 ### 3. 容灾切换
 
-部署成功，杀掉 Leader 之后（在上面的例子中，杀掉端口 30931 所在的进程），等待约 10s 左右，用 clusterList 命令查看集群，就会发现 Leader 切换到另一个节点了。
+部署成功后，先用 clusterList 命令确认当前 Leader 所在的节点（BID 为 0 的表示 Master），再杀掉该 Leader 进程（conf/dledger 中 broker-n0、broker-n1、broker-n2 的 listenPort 分别为 30911、30921、30931，Leader 由 DLedger 选举产生，并不固定是哪一个）。等待约 10s 左右，再次用 clusterList 命令查看集群，就会发现 Leader 切换到另一个节点了。
 
 
 
diff --git a/docs/en/dledger/quick_start.md b/docs/en/dledger/quick_start.md
index dfc7894af56..60d85987476 100644
--- a/docs/en/dledger/quick_start.md
+++ b/docs/en/dledger/quick_start.md
@@ -60,7 +60,7 @@ Quick deployment, default configuration is in directory conf/dledger, default st
 
 ### 3. Failover
 
-After successful deployment, kill Leader process(as the above example, kill process that binds port 30931), about 10 seconds elapses, use clusterList command check cluster's status, Leader switch to another node.
+After successful deployment, first use clusterList to confirm which node is the current Leader (the entry with BID 0 is the Master), then kill that Leader process (the listenPort of broker-n0, broker-n1 and broker-n2 in conf/dledger is 30911, 30921 and 30931 respectively; the Leader is elected by DLedger and is not fixed). About 10 seconds later, check the cluster's status with clusterList again, the Leader should have switched to another node.