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 99c8bd6ec1c Fix broken link (#2790)
99c8bd6ec1c is described below
commit 99c8bd6ec1c4d3856bd4f626a53a3d23cdc4be97
Author: Albumen Kevin <[email protected]>
AuthorDate: Wed Aug 9 19:18:25 2023 +0800
Fix broken link (#2790)
* Fix broken link
* Fix broken link
* Fix broken link
---
content/en/docs3-v2/java-sdk/reference-manual/protocol/grpc.md | 4 ++--
.../service-discovery/service-discovery-samples.md | 10 +++++-----
.../en/overview/tasks/migration/service-discovery-samples.md | 10 +++++-----
content/zh-cn/blog/integration/pinpoint.md | 2 +-
.../java/demos/dubbo-supporting-grpc-http2-and-protobuf.md | 4 ++--
content/zh-cn/blog/news/apache-dubbo-2019-2020.md | 2 +-
content/zh-cn/docs/references/protocols/gRPC.md | 4 ++--
content/zh-cn/docsv2.7/user/references/protocol/gRPC.md | 4 ++--
.../mannual/java-sdk/reference-manual/protocol/grpc.md | 4 ++--
.../service-discovery/service-discovery-samples.md | 8 ++++----
10 files changed, 26 insertions(+), 26 deletions(-)
diff --git a/content/en/docs3-v2/java-sdk/reference-manual/protocol/grpc.md
b/content/en/docs3-v2/java-sdk/reference-manual/protocol/grpc.md
index 3b13c58e1db..17e07a74c91 100644
--- a/content/en/docs3-v2/java-sdk/reference-manual/protocol/grpc.md
+++ b/content/en/docs3-v2/java-sdk/reference-manual/protocol/grpc.md
@@ -24,11 +24,11 @@ You can consider enabling the gRPC protocol.
## How to use
### Using gRPC in Dubbo
-[Example](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc)
+[Example](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc)
### steps
1. Define a service using IDL
2. Configure the compiler plug-in, precompile locally
3. Configure to expose/reference Dubbo service
-> In addition to the native StreamObserver interface type, Dubbo also supports
[RxJava](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc/dubbo-samples-rxjava),
[Reactor](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc/dubbo-samples-reactor)
programming style API.
\ No newline at end of file
+> In addition to the native StreamObserver interface type, Dubbo also supports
[RxJava](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc/dubbo-samples-rxjava),
[Reactor](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc/dubbo-samples-reactor)
programming style API.
diff --git
a/content/en/docs3-v2/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples.md
b/content/en/docs3-v2/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples.md
index 640db50134b..d6c4234aa12 100644
---
a/content/en/docs3-v2/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples.md
+++
b/content/en/docs3-v2/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples.md
@@ -20,7 +20,7 @@ After the application is upgraded to Dubbo 3.0, the consumer
side automatically
1. Global switch
Application configuration (can be specified by configuration file or -D)
`dubbo.application.register-mode` enables the global registration switch for
instance (only register application level) and all (both interface level and
application level registration). After configuring this switch , by default,
application-level addresses will be registered with all registries for service
discovery on the consumer side.
-> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src/main/resources/
dubbo.properties](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src
/main/resources/dubbo.properties)
+> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src/main/resources/
dubbo.properties](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src
/main/resources/dubbo.properties)
```
# double registration
@@ -34,7 +34,7 @@ dubbo.application.register-mode=instance
2. Registration center address parameter configuration
Registry-type=service can be configured on the address of the registry to
display the registry that specifies the registry as application-level service
discovery, and the registry with this configuration will only perform
application-level service discovery.
-> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src/main/resources/spring/
dubbo-provider.xml](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src
/main/resources/spring/dubbo-provider.xml)
+> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src/main/resources/spring/
dubbo-provider.xml](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src
/main/resources/spring/dubbo-provider.xml)
```xml
<dubbo:registry
address="nacos://${nacos.address:127.0.0.1}:8848?registry-type=service"/>
@@ -53,7 +53,7 @@ After upgrading to Dubbo 3.0, the default behavior is
interface-level + applicat
Application configuration (can be specified by configuration file or -D)
`dubbo.application.service-discovery.migration` is `APPLICATION_FIRST` to
enable multi-subscription mode, and configuration to `FORCE_APPLICATION` can
force application-level subscription mode only.
The specific interface subscription can be configured in `parameters` in
`ReferenceConfig`, and the Key is `migration.step`, and the Value is
`APPLICATION_FIRST` or `FORCE_APPLICATION` key-value pair to configure a single
subscription.
-> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/test/java/
org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-servicediscovery-migration
/dubbo-servicediscovery-migration-consumer/src/test/java/org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java)
+> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/test/java/
org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration
/dubbo-servicediscovery-migration-consumer/src/test/java/org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java)
```java
System.setProperty("dubbo.application.service-discovery.migration",
"APPLICATION_FIRST");
@@ -69,8 +69,8 @@ return referenceConfig.get();
3. Dynamic configuration (highest priority, configuration can be modified at
runtime)
This configuration needs to be pushed based on the configuration center, the
Key is the application name + `.migration` (such as
`demo-application.migraion`), and the Group is
`DUBBO_SERVICEDISCOVERY_MIGRATION`. For details on rule body configuration, see
[Guidelines for migrating from interface-level service discovery to
application-level service discovery](../migration-service-discovery/).
-> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/main/java/
org/apache/dubbo/demo/consumer/UpgradeUtil.java](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-servicediscovery-migration
/dubbo-servicediscovery-migration-consumer/src/main/java/org/apache/dubbo/demo/consumer/UpgradeUtil.java)
+> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/main/java/
org/apache/dubbo/demo/consumer/UpgradeUtil.java](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration
/dubbo-servicediscovery-migration-consumer/src/main/java/org/apache/dubbo/demo/consumer/UpgradeUtil.java)
```java
step: FORCE_INTERFACE
-```
\ No newline at end of file
+```
diff --git a/content/en/overview/tasks/migration/service-discovery-samples.md
b/content/en/overview/tasks/migration/service-discovery-samples.md
index c93c33737fc..66e0e2baebc 100644
--- a/content/en/overview/tasks/migration/service-discovery-samples.md
+++ b/content/en/overview/tasks/migration/service-discovery-samples.md
@@ -20,7 +20,7 @@ After the application is upgraded to Dubbo 3.0, the consumer
side automatically
1. Global switch
Application configuration (can be specified by configuration file or -D)
`dubbo.application.register-mode` enables the global registration switch for
instance (only register application level) and all (both interface level and
application level registration). After configuring this switch , by default,
application-level addresses will be registered with all registries for service
discovery on the consumer side.
-> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src/main/resources/
dubbo.properties](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src
/main/resources/dubbo.properties)
+> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src/main/resources/
dubbo.properties](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src
/main/resources/dubbo.properties)
```
# double registration
@@ -34,7 +34,7 @@ dubbo.application.register-mode=instance
2. Registration center address parameter configuration
Registry-type=service can be configured on the address of the registry to
display the registry that specifies the registry as application-level service
discovery, and the registry with this configuration will only perform
application-level service discovery.
-> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src/main/resources/spring/
dubbo-provider.xml](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src
/main/resources/spring/dubbo-provider.xml)
+> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src/main/resources/spring/
dubbo-provider.xml](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src
/main/resources/spring/dubbo-provider.xml)
```xml
<dubbo:registry
address="nacos://${nacos.address:127.0.0.1}:8848?registry-type=service"/>
@@ -55,7 +55,7 @@ After upgrading to Dubbo 3.0, the default behavior is
interface-level + applicat
Application configuration (can be specified by configuration file or -D)
`dubbo.application.service-discovery.migration` is `APPLICATION_FIRST` to
enable multi-subscription mode, and configuration to `FORCE_APPLICATION` can
force application-level subscription mode only.
The specific interface subscription can be configured in `parameters` in
`ReferenceConfig`, and the Key is `migration.step`, and the Value is
`APPLICATION_FIRST` or `FORCE_APPLICATION` key-value pair to configure a single
subscription.
-> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/test/java/
org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-servicediscovery-migration
/dubbo-servicediscovery-migration-consumer/src/test/java/org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java)
+> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/test/java/
org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration
/dubbo-servicediscovery-migration-consumer/src/test/java/org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java)
```java
System.setProperty("dubbo.application.service-discovery.migration",
"APPLICATION_FIRST");
@@ -71,8 +71,8 @@ return referenceConfig.get();
3. Dynamic configuration (highest priority, configuration can be modified at
runtime)
This configuration needs to be pushed based on the configuration center, the
Key is the application name + `.migration` (such as
`demo-application.migraion`), and the Group is
`DUBBO_SERVICEDISCOVERY_MIGRATION`. For details on rule body configuration, see
[Guidelines for migrating from interface-level service discovery to
application-level service
discovery](/en/docs3-v2/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-rule/).
-> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/main/java/
org/apache/dubbo/demo/consumer/UpgradeUtil.java](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-servicediscovery-migration
/dubbo-servicediscovery-migration-consumer/src/main/java/org/apache/dubbo/demo/consumer/UpgradeUtil.java)
+> Example:
[https://github.com/apache/dubbo-samples/blob/master/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/main/java/
org/apache/dubbo/demo/consumer/UpgradeUtil.java](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration
/dubbo-servicediscovery-migration-consumer/src/main/java/org/apache/dubbo/demo/consumer/UpgradeUtil.java)
```java
step: FORCE_INTERFACE
-```
\ No newline at end of file
+```
diff --git a/content/zh-cn/blog/integration/pinpoint.md
b/content/zh-cn/blog/integration/pinpoint.md
index eee7c5392de..ca40f035784 100644
--- a/content/zh-cn/blog/integration/pinpoint.md
+++ b/content/zh-cn/blog/integration/pinpoint.md
@@ -11,7 +11,7 @@ description: >
## 什么是Pinpoint
-> 摘自[Pinpoint学习笔记](https://skyao.gitbooks.io/learning-pinpoint/)
+>
摘自[Pinpoint学习笔记](https://skyao.gitbooks.io/learning-pinpoint/content/index.html)
[Pinpoint](https://github.com/naver/pinpoint)是一个开源的 APM (Application
Performance Management/应用性能管理)工具，用于基于java的大规模分布式系统。
仿照Google Dapper，Pinpoint通过跟踪分布式应用之间的调用来提供解决方案，以帮助分析系统的总体结构和内部模块之间如何相互联系。
diff --git
a/content/zh-cn/blog/java/demos/dubbo-supporting-grpc-http2-and-protobuf.md
b/content/zh-cn/blog/java/demos/dubbo-supporting-grpc-http2-and-protobuf.md
index dc1dbfd9337..95f3ac1c403 100644
--- a/content/zh-cn/blog/java/demos/dubbo-supporting-grpc-http2-and-protobuf.md
+++ b/content/zh-cn/blog/java/demos/dubbo-supporting-grpc-http2-and-protobuf.md
@@ -155,7 +155,7 @@ service SearchService {
[gRPC](https://grpc.io/) 是 Google 开源的构建在 HTTP/2 之上的一个 PRC 通信协议。Dubbo
依赖其灵活的协议扩展机制，增加了对 gRPC (HTTP/2) 协议的支持。
-目前的支持限定在 Dubbo Java 语言版本，后续 Go
语言或其他语言版本将会以类似方式提供支持。下面，通过一个[简单的示例](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc)来演示如何在
Dubbo 中使用 gRPC 协议通信。
+目前的支持限定在 Dubbo Java 语言版本，后续 Go
语言或其他语言版本将会以类似方式提供支持。下面，通过一个[简单的示例](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc)来演示如何在
Dubbo 中使用 gRPC 协议通信。
#### 1. 定义服务 IDL
@@ -589,7 +589,7 @@ message HelloReply {
</plugin>
```
-注意，这里与 [Dubbo 对
gRPC](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc)
支持部分的区别在于：
+注意，这里与 [Dubbo 对
gRPC](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc)
支持部分的区别在于：
` <pluginParameter>dubbo</pluginParameter>`
2. 生成 Dubbo stub
diff --git a/content/zh-cn/blog/news/apache-dubbo-2019-2020.md
b/content/zh-cn/blog/news/apache-dubbo-2019-2020.md
index 8ba16527f55..99641f9703a 100644
--- a/content/zh-cn/blog/news/apache-dubbo-2019-2020.md
+++ b/content/zh-cn/blog/news/apache-dubbo-2019-2020.md
@@ -107,7 +107,7 @@ CompletableFuture<String> future =
helloService.sayHello("world");
-但是需要注意的一定是，由于外围的 Reactive API 需要有底层传输协议的支持才有意义，因此，目前 Reactive API 只能在使用 gRPC
协议时才有意义，具体请参见示例以及下面关于 ”[Dubbo 对 gRPC
的支持](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc/dubbo-samples-rxjava)”
一节的讲解。
+但是需要注意的一定是，由于外围的 Reactive API 需要有底层传输协议的支持才有意义，因此，目前 Reactive API 只能在使用 gRPC
协议时才有意义，具体请参见示例以及下面关于 ”[Dubbo 对 gRPC
的支持](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc/dubbo-samples-rxjava)”
一节的讲解。
### 性能优化
diff --git a/content/zh-cn/docs/references/protocols/gRPC.md
b/content/zh-cn/docs/references/protocols/gRPC.md
index 6b3fd0e43b1..1d66cc84f37 100644
--- a/content/zh-cn/docs/references/protocols/gRPC.md
+++ b/content/zh-cn/docs/references/protocols/gRPC.md
@@ -26,6 +26,6 @@ Dubbo 自 2.7.5 版本开始支持 gRPC 协议，对于计划使用 HTTP/2 通
2. 配置 compiler 插件，本地预编译
3. 配置暴露/引用 Dubbo 服务
-具体可参见以下[示例](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc)
+具体可参见以下[示例](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc)
-除了原生 StreamObserver 接口类型之外，Dubbo 还支持
[RxJava](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc/dubbo-samples-rxjava)、[Reactor](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc/dubbo-samples-reactor)
编程风格的 API
+除了原生 StreamObserver 接口类型之外，Dubbo 还支持
[RxJava](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc/dubbo-samples-rxjava)、[Reactor](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc/dubbo-samples-reactor)
编程风格的 API
diff --git a/content/zh-cn/docsv2.7/user/references/protocol/gRPC.md
b/content/zh-cn/docsv2.7/user/references/protocol/gRPC.md
index f01b15e1019..f7da1ad7ed4 100644
--- a/content/zh-cn/docsv2.7/user/references/protocol/gRPC.md
+++ b/content/zh-cn/docsv2.7/user/references/protocol/gRPC.md
@@ -23,6 +23,6 @@ Dubbo 自 2.7.5 版本开始支持 gRPC 协议，对于计划使用 HTTP/2 通
2. 配置 compiler 插件，本地预编译
3. 配置暴露/引用 Dubbo 服务
-具体可参见以下[示例](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc)
+具体可参见以下[示例](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc)
-除了原生 StreamObserver 接口类型之外，Dubbo 还支持
[RxJava](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc/dubbo-samples-rxjava)、[Reactor](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc/dubbo-samples-reactor)
编程风格的 API
\ No newline at end of file
+除了原生 StreamObserver 接口类型之外，Dubbo 还支持
[RxJava](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc/dubbo-samples-rxjava)、[Reactor](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc/dubbo-samples-reactor)
编程风格的 API
diff --git
a/content/zh-cn/overview/mannual/java-sdk/reference-manual/protocol/grpc.md
b/content/zh-cn/overview/mannual/java-sdk/reference-manual/protocol/grpc.md
index ac39524fc1d..07eb38fa2f3 100644
--- a/content/zh-cn/overview/mannual/java-sdk/reference-manual/protocol/grpc.md
+++ b/content/zh-cn/overview/mannual/java-sdk/reference-manual/protocol/grpc.md
@@ -34,11 +34,11 @@ Dubbo 自 2.7.5 版本开始支持 gRPC 协议，对于计划使用 HTTP/2 通
## 使用方式
### 在 Dubbo 中使用 gRPC
-[示例](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc)
+[示例](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc)
### 步骤
1. 使用 IDL 定义服务
2. 配置 compiler 插件，本地预编译
3. 配置暴露/引用 Dubbo 服务
-> 除了原生 StreamObserver 接口类型之外，Dubbo 还支持
[RxJava](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc/dubbo-samples-rxjava)、[Reactor](https://github.com/apache/dubbo-samples/tree/master/3-extensions/protocol/dubbo-samples-grpc/dubbo-samples-reactor)
编程风格的 API。
\ No newline at end of file
+> 除了原生 StreamObserver 接口类型之外，Dubbo 还支持
[RxJava](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc/dubbo-samples-rxjava)、[Reactor](https://github.com/apache/dubbo-samples/tree/master/99-integration/dubbo-samples-grpc/dubbo-samples-reactor)
编程风格的 API。
diff --git
a/content/zh-cn/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples.md
b/content/zh-cn/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples.md
index 52c78f423b9..4fab199133a 100644
---
a/content/zh-cn/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples.md
+++
b/content/zh-cn/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples.md
@@ -28,7 +28,7 @@ weight: 5
1. 全局开关
应用配置（可以通过配置文件或者 -D 指定）`dubbo.application.register-mode` 为
instance（只注册应用级）、all（接口级+应用级均注册）开启全局的注册开关，配置此开关后，默认会向所有的注册中心中注册应用级的地址，供消费端服务发现使用。
->
[参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src/main/resources/dubbo.properties)
+>
[参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-provider2/src/main/resources/dubbo.properties)
```
# 双注册
@@ -42,7 +42,7 @@ dubbo.application.register-mode=instance
2. 注册中心地址参数配置
注册中心的地址上可以配置 `registry-type=service`
来显示指定该注册中心为应用级服务发现的注册中心，带上此配置的注册中心将只进行应用级服务发现。
->
[参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src/main/resources/spring/dubbo-provider.xml)
+>
[参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-demo-servicediscovery-xml/servicediscovery-provider/src/main/resources/spring/dubbo-provider.xml)
```xml
<dubbo:registry
address="nacos://${nacos.address:127.0.0.1}:8848?registry-type=service"/>
@@ -61,7 +61,7 @@ FORCE_APPLICATION：仅应用级订阅，将只采用全新的服务发现模型
应用配置（可以通过配置文件或者 -D 指定）`dubbo.application.service-discovery.migration` 为
`APPLICATION_FIRST` 可以开启多订阅模式，配置为 `FORCE_APPLICATION` 可以强制为仅应用级订阅模式。
具体接口订阅可以在 `ReferenceConfig` 中的 `parameters` 中配置 Key 为 `migration.step`，Value 为
`APPLICATION_FIRST` 或 `FORCE_APPLICATION` 的键值对来对单一订阅进行配置。
->
[参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/test/java/org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java)
+>
[参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/test/java/org/apache/dubbo/demo/consumer/DemoServiceConfigIT.java)
```java
System.setProperty("dubbo.application.service-discovery.migration",
"APPLICATION_FIRST");
@@ -77,7 +77,7 @@ return referenceConfig.get();
3. 动态配置（优先级最高，可以在运行时修改配置）
此配置需要基于配置中心进行推送，Key 为应用名 + `.migration` （如 `demo-application.migraion`），Group
为
`DUBBO_SERVICEDISCOVERY_MIGRATION`。规则体配置详见[接口级服务发现迁移至应用级服务发现指南](../migration-service-discovery/)。
->
[参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-cloud-native/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/main/java/org/apache/dubbo/demo/consumer/UpgradeUtil.java)
+>
[参考示例](https://github.com/apache/dubbo-samples/blob/master/2-advanced/dubbo-samples-service-discovery/dubbo-servicediscovery-migration/dubbo-servicediscovery-migration-consumer/src/main/java/org/apache/dubbo/demo/consumer/UpgradeUtil.java)
```java
step: FORCE_INTERFACE
