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

albumenj pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/dubbo-website.git


The following commit(s) were added to refs/heads/master by this push:
     new ce42b60495 [fix] Hyperlink failure (#1131)
ce42b60495 is described below

commit ce42b6049586dd520320422024180b19ec726e80
Author: JIAN ZHONG <[email protected]>
AuthorDate: Thu Jun 23 14:23:24 2022 +0800

    [fix] Hyperlink failure (#1131)
    
    * [fix] Hyperlink failure
    
    * [fix] 路径更改
---
 .../java-sdk/concepts-and-architecture/service-discovery.md           | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git 
a/content/zh/docs3-building/java-sdk/concepts-and-architecture/service-discovery.md
 
b/content/zh/docs3-building/java-sdk/concepts-and-architecture/service-discovery.md
index 4af2a11e39..866f2edcbb 100644
--- 
a/content/zh/docs3-building/java-sdk/concepts-and-architecture/service-discovery.md
+++ 
b/content/zh/docs3-building/java-sdk/concepts-and-architecture/service-discovery.md
@@ -32,9 +32,9 @@ dubbo
 * Dubbo2 接口级服务发现,以接口粒度组织地址数据
 
 Dubbo3 格式的 Provider 地址不能被 Dubbo2 的 Consumer 识别到,反之 Dubbo2 的消费者也不能订阅到 Dubbo3 
Provider。
-* 对于新用户,我们提倡直接启用 Dubbo3 
的默认行为,即启用应用级服务发现,参见《[应用级服务发现](../../examples/service-discovery)》;
+* 对于新用户,我们提倡直接启用 Dubbo3 
的默认行为,即启用应用级服务发现,参见《[应用级服务发现](../../../java-sdk/upgrades-and-compatibility/service-discovery#应用级服务发现)》;
 * 对于老用户,要面临如何平滑迁移到应用级服务发现的问题,考虑到老用户的规模如此之大,Dubbo3 
默认保持了接口级地址发现的行为,这保证了老用户可以直接无感升级到 Dubbo3。
-而如果要开启应用级服务发现,则需要通过配置显示开启(双注册、双订阅),具体开启与平滑迁移过程,可参见《[地址发现迁移指南](../../migration/migration-service-discovery)》。
+而如果要开启应用级服务发现,则需要通过配置显示开启(双注册、双订阅),具体开启与平滑迁移过程,可参见《[地址发现迁移指南](../../../java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples#应用级服务发现迁移示例)》。
 
 ## 应用级服务发现简介
 概括来说,Dubbo3 引入的应用级服务发现主要有以下优势

Reply via email to