diff --git a/docs/04-deployment/01deploy.md b/docs/04-deployment/01deploy.md
index ae57686695..d48803567f 100644
--- a/docs/04-deployment/01deploy.md
+++ b/docs/04-deployment/01deploy.md
@@ -11,6 +11,10 @@ Apache RocketMQ 5.0 版本完成基本消息收发，包括 NameServer、Broker
 
 由于 Local 模式下 Proxy 和 Broker 是同进程部署，Proxy本身无状态，因此主要的集群配置仍然以 Broker 为基础进行即可。
 
+:::caution
+Local 模式下 Proxy 不应该修改`grpcServerPort`参数，否则可能会连接到错误的集群上。
+:::
+
 ### 单组节点单副本模式
 
 :::caution
diff --git a/i18n/en/docusaurus-plugin-content-docs/version-5.0/05-deploymentOperations/01deploy.md b/i18n/en/docusaurus-plugin-content-docs/version-5.0/05-deploymentOperations/01deploy.md
index 8608f2b12b..d4c6dbe2e7 100644
--- a/i18n/en/docusaurus-plugin-content-docs/version-5.0/05-deploymentOperations/01deploy.md
+++ b/i18n/en/docusaurus-plugin-content-docs/version-5.0/05-deploymentOperations/01deploy.md
@@ -10,6 +10,10 @@ In the Apache RocketMQ 5.0 version, basic message sending and receiving is compl
 
 Since the Proxy and Broker are deployed in the same process in Local mode, the Proxy is stateless, so the main cluster configuration can still be based on the Broker.
 
+:::caution
+The Local Mode Proxy should not modify the `grpcServerPort` parameter, otherwise it may connect to the wrong cluster.
+:::
+
 ### Start NameServer
 
 ```bash
diff --git a/versioned_docs/version-5.0/05-deploymentOperations/01deploy.md b/versioned_docs/version-5.0/05-deploymentOperations/01deploy.md
index a55e809e54..68a8240233 100644
--- a/versioned_docs/version-5.0/05-deploymentOperations/01deploy.md
+++ b/versioned_docs/version-5.0/05-deploymentOperations/01deploy.md
@@ -10,6 +10,11 @@ Apache RocketMQ 5.0 版本完成基本消息收发，包括 NameServer、Broker
 ## Local模式部署
 
 由于 Local 模式下 Proxy 和 Broker 是同进程部署，Proxy本身无状态，因此主要的集群配置仍然以 Broker 为基础进行即可。
+
+:::caution
+Local 模式下 Proxy 不应该修改`grpcServerPort`参数，否则可能会连接到错误的集群上。
+:::
+
 ### 启动 NameServer
 NameServer需要先于Broker启动，且如果在生产环境使用，为了保证高可用，建议一般规模的集群启动3个NameServer，各节点的启动命令相同，如下：