diff --git a/docs/en_US/tasks/assets/configure-emqx-blueGreenUpdate/grafana.png b/docs/en_US/tasks/assets/configure-emqx-blueGreenUpdate/grafana.png
index 29c05fa3c..d5cee7c00 100644
Binary files a/docs/en_US/tasks/assets/configure-emqx-blueGreenUpdate/grafana.png and b/docs/en_US/tasks/assets/configure-emqx-blueGreenUpdate/grafana.png differ
diff --git a/docs/en_US/tasks/configure-emqx-blueGreenUpdate.md b/docs/en_US/tasks/configure-emqx-blueGreenUpdate.md
index 99e6cd382..44868aaa8 100644
--- a/docs/en_US/tasks/configure-emqx-blueGreenUpdate.md
+++ b/docs/en_US/tasks/configure-emqx-blueGreenUpdate.md
@@ -123,7 +123,7 @@ metadata:
   name: emqx
 spec:
   image: emqx:5.1
-	updateStrategy:
+  updateStrategy:
     evacuationStrategy:
       connEvictRate: 1000
       sessEvictRate: 1000
@@ -296,14 +296,14 @@ Output is similar to:
 
 ## Grafana Monitoring
 
-The monitoring graph of the number of connections during the upgrade process is shown below (using 100,000 connections as an example).
+The monitoring graph of the number of connections during the upgrade process is shown below (using 10,000 connections as an example).
 
 ![](./assets/configure-emqx-blueGreenUpdate/grafana.png)
 
-sum: Total number of connections, represented by the top line in the graph.
+Total: Total number of connections, represented by the top line in the graph.
 
-emqx-ee-86d7758868: Three EMQX nodes before the upgrade.
+emqx-ee-86f864f975： This prefix represents the 3 EMQX nodes before the upgrade.
 
-emqx-ee-745858464d: Three EMQX nodes after the upgrade.
+emqx-ee-648c45c747： This prefix represents the 3 EMQX nodes after the upgrade.
 
 As shown in the figure above, we have implemented graceful upgrade in Kubernetes through EMQX Kubernetes Operator's blue-green deployment. Through this solution, the total number of connections did not have a significant shake (depending on migration rate, server reception rate, client reconnection policy, etc.) during the upgrade process, which can greatly ensure the smoothness of the upgrade process, effectively prevent server overload, reduce business perception, and improve the stability of the service.
diff --git a/docs/zh_CN/tasks/assets/configure-emqx-blueGreenUpdate/grafana.png b/docs/zh_CN/tasks/assets/configure-emqx-blueGreenUpdate/grafana.png
index 29c05fa3c..d5cee7c00 100644
Binary files a/docs/zh_CN/tasks/assets/configure-emqx-blueGreenUpdate/grafana.png and b/docs/zh_CN/tasks/assets/configure-emqx-blueGreenUpdate/grafana.png differ
diff --git a/docs/zh_CN/tasks/configure-emqx-blueGreenUpdate.md b/docs/zh_CN/tasks/configure-emqx-blueGreenUpdate.md
index 4acb132db..1b10c035a 100644
--- a/docs/zh_CN/tasks/configure-emqx-blueGreenUpdate.md
+++ b/docs/zh_CN/tasks/configure-emqx-blueGreenUpdate.md
@@ -118,7 +118,7 @@ metadata:
   name: emqx
 spec:
   image: emqx:5.1
-	updateStrategy:
+  updateStrategy:
     evacuationStrategy:
       connEvictRate: 1000
       sessEvictRate: 1000
@@ -290,15 +290,14 @@ mqttx bench conn -h ${IP} -p ${PORT} -c 3000
 
 ## Grafana 监控
 
-升级过程中连接数监控图如下（10万连接为例）
+升级过程中连接数监控图如下（1万连接为例）
 
 ![](./assets/configure-emqx-blueGreenUpdate/grafana.png)
 
+Total：总的连接数，图中最上面的一条线
 
-sum：总的连接数，图中最上面的一条线
+emqx-ee-86f864f975：前缀表示的是升级前的 3 个 EMQX 节点
 
-emqx-ee-86d7758868：升级前的 3 个 EMQX 节点
-
-emqx-ee-745858464d：升级后的 3 个 EMQX 节点
+emqx-ee-648c45c747：前缀表示升级后的 3 个 EMQX 节点
 
 如上图，我们通过 EMQX Kubernetes Operator 的蓝绿发布在 Kubernetes 中实现了优雅升级，通过该方案升级，总连接数未出现较大抖动（取决于迁移速率、服务端能够接收的速率、客户端重连策略等），能够极大程度保障升级过程的平滑，有效防止服务端过载，减少业务感知，从而提升服务的稳定性。