[rocketmq] branch develop updated: [ISSUE #5791]Fix controller deploy.md and quick_start.md link not correct (#5792)

[ji...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

jinrongtong pushed a commit to branch develop
in repository https://gitbox.apache.org/repos/asf/rocketmq.git


The following commit(s) were added to refs/heads/develop by this push:
     new 5de60cf59 [ISSUE #5791]Fix controller deploy.md and quick_start.md link not correct (#5792)
5de60cf59 is described below

commit 5de60cf591f62837bd914d773be6d98706606520
Author: mxsm <lj...@gmail.com>
AuthorDate: Sat Dec 31 11:39:46 2022 +0800

    [ISSUE #5791]Fix controller deploy.md and quick_start.md link not correct (#5792)
    
    * [ISSUE #5791]Fix controller deploy.md and quick_start.md link not correct
    
    * polish document
---
 docs/en/controller/deploy.md      | 2 +-
 docs/en/controller/quick_start.md | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/en/controller/deploy.md b/docs/en/controller/deploy.md
index 1546542ad..bba79607e 100644
--- a/docs/en/controller/deploy.md
+++ b/docs/en/controller/deploy.md
@@ -76,7 +76,7 @@ Among the parameters such as inSyncReplicas and minInSyncReplicas, there are ove
 
 To summarize：
 - In a normal Master-Slave configuration, there is no ability for auto-degradation, and all parameters except for inSyncReplicas are invalid. inSyncReplicas indicates the number of replicas that need to be ACKed in synchronous replication.
-- In slaveActingMaster mode, enabling enableAutoInSyncReplicas enables the ability for degradation, and the minimum number of replicas that can be degraded to is minInSyncReplicas. The basis for degradation is the difference in Commitlog heights (haMaxGapNotInSync) and the survival of the replicas, refer to  [slaveActingMaster mode auto-degradation](https://chat.openai.com/QuorumACK.md).
+- In slaveActingMaster mode, enabling enableAutoInSyncReplicas enables the ability for degradation, and the minimum number of replicas that can be degraded to is minInSyncReplicas. The basis for degradation is the difference in Commitlog heights (haMaxGapNotInSync) and the survival of the replicas, refer to  [SlaveActingMaster mode adaptive degradation](../QuorumACK.md).
 - Automatic master-slave switching (Controller mode) relies on SyncStateSet contraction for auto-degradation. SyncStateSet replicas can work normally as long as they are contracted to a minimum of minInSyncReplicas. If it is less than minInSyncReplicas, it will return directly with insufficient number of replicas. One of the basis for contraction is the time interval (haMaxTimeSlaveNotCatchup) at which the Slave catches up, rather than the Commitlog height. If allAckInSyncStateSet=true,  [...]
 
 ## Compatibility
diff --git a/docs/en/controller/quick_start.md b/docs/en/controller/quick_start.md
index 70a65cb51..e7997213b 100644
--- a/docs/en/controller/quick_start.md
+++ b/docs/en/controller/quick_start.md
@@ -6,9 +6,9 @@
 
 This document mainly introduces how to quickly build a RocketMQ cluster that supports automatic master-slave switch, as shown in the above diagram. The main addition is the Controller component, which can be deployed independently or embedded in the NameServer.
 
-For detailed design ideas, please refer to [Design Ideas](https://chat.openai.com/chat/design.md).
+For detailed design ideas, please refer to [Design ideas](design.md).
 
-For detailed guidelines on new cluster deployment and old cluster upgrades, please refer to [Deployment Guide](https://chat.openai.com/chat/deploy.md).
+For detailed guidelines on new cluster deployment and old cluster upgrades, please refer to [Deployment guide](deploy.md).
 
 ## Compile RocketMQ source code