You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@dubbo.apache.org by ra...@apache.org on 2025/11/11 15:45:28 UTC
(dubbo-website) branch master updated: dubbo-website english doc problem fix (#3147)
This is an automated email from the ASF dual-hosted git repository.
rainyu 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 ff42aac14ba dubbo-website english doc problem fix (#3147)
ff42aac14ba is described below
commit ff42aac14ba609362f9375c6a2ea29c78671ef70
Author: Rain Yu <ra...@apache.org>
AuthorDate: Tue Nov 11 23:45:17 2025 +0800
dubbo-website english doc problem fix (#3147)
fix english doc lint problem
---
.github/workflows/build_and_deploy.yml | 4 ++--
.github/workflows/build_and_deploy_history.yml | 2 +-
.github/workflows/link_check.yml | 2 +-
content/en/_index.html | 8 ++++----
.../blog/integration/dubbo-triple-with-apisix-gateway.md | 4 ++--
.../integration/how-to-proxy-dubbo-in-apache-apisix.md | 2 +-
.../blog/integration/sentinel-introduction-for-dubbo.md | 2 +-
content/en/blog/news/apache-dubbo-2019-2020.md | 2 +-
content/en/blog/news/apachecon-asia-2023-summary.md | 14 +++++++-------
content/en/blog/news/dubbo-101.md | 4 +---
content/en/blog/news/dubbo-new-async.md | 2 +-
content/en/blog/news/introduction-to-dubbo-spi.md | 2 +-
content/en/contact/_index.md | 2 +-
content/en/latest/facade-docs/how/quick-start.md | 2 +-
content/en/overview/home/_index.md | 4 ++--
content/en/overview/mannual/control-plane/test.md | 2 +-
.../mannual/golang-sdk/quickstart/microservices.md | 4 +++-
content/en/overview/mannual/java-sdk/_index.md | 2 +-
.../en/overview/mannual/java-sdk/quick-start/deploy.md | 4 ++--
.../en/overview/mannual/java-sdk/quick-start/starter.md | 6 +++---
.../java-sdk/reference-manual/architecture/dubbo-spi.md | 2 +-
.../java-sdk/reference-manual/config-center/_index.md | 2 +-
.../reference-manual/config-center/introduction.md | 4 ++--
.../java-sdk/reference-manual/config-center/nacos.md | 10 +++++-----
.../java-sdk/reference-manual/config-center/zookeeper.md | 6 +++---
.../java-sdk/reference-manual/config/principle.md | 2 +-
.../java-sdk/reference-manual/config/properties.md | 14 +++++++-------
.../reference-manual/config/spring/spring-boot.md | 10 +++++-----
.../mannual/java-sdk/reference-manual/faq/1/10.md | 2 +-
.../mannual/java-sdk/reference-manual/faq/1/7.md | 2 +-
.../mannual/java-sdk/reference-manual/faq/1/9.md | 2 +-
.../mannual/java-sdk/reference-manual/faq/2/4.md | 3 ++-
.../mannual/java-sdk/reference-manual/faq/7/7.md | 2 +-
.../java-sdk/reference-manual/metadata-center/nacos.md | 2 +-
.../reference-manual/metadata-center/overview.md | 5 ++---
.../reference-manual/metadata-center/zookeeper.md | 10 +++++-----
.../java-sdk/reference-manual/protocol/overview.md | 14 +++++++-------
.../mannual/java-sdk/reference-manual/protocol/triple.md | 14 +++++++-------
.../reference-manual/qos/introduction/profiler.md | 2 +-
.../reference-manual/qos/introduction/router-snapshot.md | 2 +-
.../mannual/java-sdk/reference-manual/registry/nacos.md | 9 ++++-----
.../java-sdk/reference-manual/registry/overview.md | 2 +-
.../service-discovery-application-vs-interface.md | 4 ++--
.../java-sdk/reference-manual/registry/zookeeper.md | 8 ++++----
.../reference-manual/serialization/triple/protobuf.md | 3 +--
.../mannual/java-sdk/reference-manual/spi/spi-list.md | 2 +-
.../upgrades-and-compatibility/migration-triple.md | 2 +-
.../upgrades-and-compatibility/migration.md | 4 ++--
.../version/2.x-to-3.x-compatibility-guide.md | 8 +++++---
.../tasks/deploy/deploy-on-kubernetes-service.md | 4 ++--
.../java-sdk/tasks/deploy/deploy-on-kubernetes.md | 4 ++--
.../mannual/java-sdk/tasks/deploy/deploy-on-vm.md | 6 +++---
.../en/overview/mannual/java-sdk/tasks/develop/api.md | 2 +-
.../mannual/java-sdk/tasks/develop/springboot.md | 2 +-
.../java-sdk/tasks/framework/fault-tolerent-strategy.md | 4 ++--
.../overview/mannual/java-sdk/tasks/framework/filter.md | 4 ++--
.../mannual/java-sdk/tasks/framework/lightweight-rpc.md | 6 +++---
.../java-sdk/tasks/framework/more/concurrency-control.md | 2 +-
.../java-sdk/tasks/framework/more/config-connections.md | 2 +-
.../tasks/framework/more/parameter-validation.md | 3 ++-
.../java-sdk/tasks/framework/more/router-snapshot.md | 2 +-
.../mannual/java-sdk/tasks/framework/version_group.md | 2 +-
.../mannual/java-sdk/tasks/gateway/architecture.md | 2 +-
.../en/overview/mannual/java-sdk/tasks/gateway/triple.md | 2 +-
.../mannual/java-sdk/tasks/mesh/migration/proxyless.md | 2 +-
.../mannual/java-sdk/tasks/observability/console.md | 3 +--
.../mannual/java-sdk/tasks/observability/grafana.md | 2 +-
.../mannual/java-sdk/tasks/protocols/triple/idl.md | 2 +-
.../en/overview/mannual/java-sdk/tasks/security/tls.md | 2 +-
.../java-sdk/tasks/service-discovery/kubernetes.md | 2 +-
.../java-sdk/tasks/service-discovery/zookeeper.md | 2 +-
.../java-sdk/tasks/traffic-management/accesslog.md | 4 ++--
.../java-sdk/tasks/traffic-management/arguments.md | 4 ++--
.../mannual/java-sdk/tasks/traffic-management/host.md | 4 ++--
.../java-sdk/tasks/traffic-management/isolation.md | 2 +-
.../mannual/java-sdk/tasks/traffic-management/mock.md | 6 +++---
.../mannual/java-sdk/tasks/traffic-management/region.md | 4 ++--
.../mannual/java-sdk/tasks/traffic-management/retry.md | 4 ++--
.../mannual/java-sdk/tasks/traffic-management/route.md | 12 ++++++------
.../mannual/java-sdk/tasks/traffic-management/timeout.md | 2 +-
.../mannual/java-sdk/tasks/traffic-management/weight.md | 2 +-
.../mannual/java-sdk/tasks/troubleshoot/no-provider.md | 4 ++--
.../mannual/java-sdk/tasks/troubleshoot/profiler.md | 2 +-
content/en/overview/mannual/web-sdk/quick-start.md | 4 ++--
content/en/overview/notices/serialization.md | 1 +
.../overview/reference/proposals/registry-config-meta.md | 2 +-
content/en/overview/what/core-features/ecosystem.md | 12 ++++++------
content/en/overview/what/core-features/extensibility.md | 14 +++++++-------
content/en/overview/what/core-features/load-balance.md | 2 +-
content/en/overview/what/core-features/more.md | 2 +-
content/en/overview/what/core-features/observability.md | 16 ++++++++--------
content/en/overview/what/core-features/protocols.md | 12 ++++++------
.../en/overview/what/core-features/service-definition.md | 12 ++++++------
.../en/overview/what/core-features/service-discovery.md | 2 +-
content/en/overview/what/core-features/service-mesh.md | 4 ++--
content/en/overview/what/core-features/traffic/_index.md | 10 +++++-----
.../what/core-features/traffic/circuit-breaking.md | 10 +++++-----
.../overview/what/core-features/traffic/introduction.md | 8 ++++----
.../en/overview/what/core-features/traffic/mesh-rule.md | 2 +-
content/zh-cn/docs/references/xml/dubbo-registry.md | 2 +-
.../docsv2.7/user/examples/simplify-registry-data.md | 4 ++--
content/zh-cn/overview/mannual/control-plane/test.md | 2 +-
.../mannual/java-sdk/reference-manual/faq/1/10.md | 2 +-
.../mannual/java-sdk/reference-manual/faq/1/7.md | 2 +-
.../mannual/java-sdk/reference-manual/faq/1/9.md | 2 +-
.../mannual/java-sdk/reference-manual/faq/7/7.md | 2 +-
.../java-sdk/reference-manual/registry/overview.md | 2 +-
.../upgrades-and-compatibility/migration.md | 4 ++--
content/zh-cn/overview/mannual/python-sdk/_index.md | 1 -
.../overview/reference/proposals/registry-config-meta.md | 2 +-
.../overview/what/core-features/service-definition.md | 4 ++--
package.json | 6 +++---
112 files changed, 243 insertions(+), 243 deletions(-)
diff --git a/.github/workflows/build_and_deploy.yml b/.github/workflows/build_and_deploy.yml
index 48cfac73ffe..3889baa81c4 100644
--- a/.github/workflows/build_and_deploy.yml
+++ b/.github/workflows/build_and_deploy.yml
@@ -24,7 +24,7 @@ jobs:
- name: Setup Hugo
uses: peaceiris/actions-hugo@v2
with:
- hugo-version: '0.134.2'
+ hugo-version: '0.152.2'
extended: true
- name: Build
env:
@@ -59,7 +59,7 @@ jobs:
- name: Setup Hugo
uses: peaceiris/actions-hugo@v2
with:
- hugo-version: '0.134.2'
+ hugo-version: '0.152.2'
extended: true
- name: Build
env:
diff --git a/.github/workflows/build_and_deploy_history.yml b/.github/workflows/build_and_deploy_history.yml
index 8a91fed44c4..bd03ac889f4 100644
--- a/.github/workflows/build_and_deploy_history.yml
+++ b/.github/workflows/build_and_deploy_history.yml
@@ -23,7 +23,7 @@ jobs:
- name: Setup Hugo
uses: peaceiris/actions-hugo@v2
with:
- hugo-version: '0.121.2'
+ hugo-version: '0.152.2'
extended: true
- name: Build
env:
diff --git a/.github/workflows/link_check.yml b/.github/workflows/link_check.yml
index 1be4dcd1080..927f2b307d7 100644
--- a/.github/workflows/link_check.yml
+++ b/.github/workflows/link_check.yml
@@ -25,7 +25,7 @@ jobs:
- name: Setup Hugo
uses: peaceiris/actions-hugo@v2
with:
- hugo-version: '0.134.2'
+ hugo-version: '0.152.2'
extended: true
- name: Build
env:
diff --git a/content/en/_index.html b/content/en/_index.html
index 11956139966..474bd9ca3bb 100644
--- a/content/en/_index.html
+++ b/content/en/_index.html
@@ -18,8 +18,8 @@ linkTitle = "Apache Dubbo Website"
Unified microservice development paradigm with multi-language SDK support. Supporting any protocol from HTTP/2, gRPC, REST, Thrift, to TCP.
{{% /blocks/feature %}}
-{{% blocks/feature image="governance" icon="fas fa-share-alt" url="./overview/what/advantages/traffic-management/" %}}
-#### [Service Governance](./overview/what/advantages/traffic-management/), Monitor and Control Cluster In Real-time
+{{% blocks/feature image="governance" icon="fas fa-share-alt" url="./overview/what/advantages/governance/" %}}
+#### [Service Governance](./overview/what/advantages/governance/), Monitor and Control Cluster In Real-time
Built-in traffic management policies such as service discovery, load balancing, and routing. Rich ecosystem with tracing, circuit break, transaction, logging, metrics, service mesh, and visualized console integrations.
{{% /blocks/feature %}}
@@ -30,8 +30,8 @@ Built-in traffic management policies such as service discovery, load balancing,
Making the Alibaba Global Shopping Festival possible by supporting millions of instances and trillions of calls every year, it's designed as low-latency, high-throughput, and high-scalability in the first place.
{{% /blocks/feature %}}
-{{% blocks/feature image="production" icon="fa fa-share-alt" title="production" url="./overview/what/advantages/extensibility/" %}}
-#### [Production Ready](./overview/what/advantages/extensibility/), Proven Production-stable For Years
+{{% blocks/feature image="production" icon="fa fa-share-alt" title="production" url="./overview/what/advantages/production-ready/" %}}
+#### [Production Ready](./overview/what/advantages/production-ready/), Proven Production-stable For Years
Dubbo users has achieved full industry coverage: Commercial Bank of China, Ctrip, Haier, Kingdee, Cloud Vendors like Alibaba Cloud, Tencent Cloud, Huawei Cloud, etc.
{{% /blocks/feature %}}
diff --git a/content/en/blog/integration/dubbo-triple-with-apisix-gateway.md b/content/en/blog/integration/dubbo-triple-with-apisix-gateway.md
index 914e01f9afc..467902bd141 100644
--- a/content/en/blog/integration/dubbo-triple-with-apisix-gateway.md
+++ b/content/en/blog/integration/dubbo-triple-with-apisix-gateway.md
@@ -55,7 +55,7 @@ dubbo:
## Deploy Application
-1. Download and start Nacos [locally](/en/overview/reference/integrations/nacos/#本地下载).
+1. Download and start Nacos [locally](/en/overview/reference/integrations/nacos#local-download).
2. Run the following command to start the Dubbo application.
@@ -147,5 +147,5 @@ curl -i http://127.0.0.1:9080/org.apache.dubbo.samples.gateway.apisix.DemoServic
### REST Mode
-If you find the HTTP port `/org.apache.dubbo.samples.gateway.apisix.DemoService/sayHello/` not friendly enough for gateway access, refer to [Publishing REST Style HTTP Interfaces for Triple Protocol](/en/overview/mannual/java-sdk/tasks/gateway/triple/#rest-风格接口).
+If you find the HTTP port `/org.apache.dubbo.samples.gateway.apisix.DemoService/sayHello/` not friendly enough for gateway access, refer to [Publishing REST Style HTTP Interfaces for Triple Protocol](/en/overview/mannual/java-sdk/tasks/gateway/triple#rest-style-interface).
diff --git a/content/en/blog/integration/how-to-proxy-dubbo-in-apache-apisix.md b/content/en/blog/integration/how-to-proxy-dubbo-in-apache-apisix.md
index 3b0c66a339d..1a06f8c6dca 100644
--- a/content/en/blog/integration/how-to-proxy-dubbo-in-apache-apisix.md
+++ b/content/en/blog/integration/how-to-proxy-dubbo-in-apache-apisix.md
@@ -11,7 +11,7 @@ aliases:
---
{{% alert title="Note" color="warning" %}}
-This article is only applicable to the Dubbo protocol communication scenario. If you are a Dubbo3 user, it is recommended to use the triple protocol. Please refer to [Using Apache APISIX to Proxy Dubbo Services (Triple Protocol)](/en/blog/2024/04/22/using-apache-apisix-to-proxy-dubbo-services-triple-protocol/) for specific examples.
+This article is only applicable to the Dubbo protocol communication scenario. If you are a Dubbo3 user, it is recommended to use the triple protocol. Please refer to [Using Apache APISIX to Proxy Dubbo Services (Triple Protocol)](/en/blog/2024/04/22/use-apache-apisix-to-proxy-dubbo-services-triple-protocol/) for specific examples.
{{% /alert %}}
[Apache APISIX](https://apisix.apache.org/) is a top-level open-source project of the Apache Software Foundation and the most active open-source gateway project currently. As a dynamic, real-time, high-performance open-source API gateway, Apache APISIX provides rich traffic management features such as load balancing, dynamic upstream, gray release, service circuit breaking, authentication, and observability.
diff --git a/content/en/blog/integration/sentinel-introduction-for-dubbo.md b/content/en/blog/integration/sentinel-introduction-for-dubbo.md
index 627969fef5f..6f308b675f5 100644
--- a/content/en/blog/integration/sentinel-introduction-for-dubbo.md
+++ b/content/en/blog/integration/sentinel-introduction-for-dubbo.md
@@ -121,7 +121,7 @@ When a service depends on multiple downstream services, a sluggish downstream ca
### Fallback
-Starting from version 0.1.1, the Sentinel Dubbo Adapter also supports configuring a global fallback function to handle fallback operations when Dubbo services are rate limited/degraded/load protected. Users simply need to implement a custom [`DubboFallback`](https://github.com/alibaba/Sentinel/blob/master/sentinel-adapter/sentinel-dubbo-adapter/src/main/java/com/alibaba/csp/sentinel/adapter/dubbo/fallback/DubboFallback.java) interface and register it through `DubboFallbackRegistry`. By d [...]
+Starting from version 0.1.1, the Sentinel Dubbo Adapter also supports configuring a global fallback function to handle fallback operations when Dubbo services are rate limited/degraded/load protected. Users simply need to implement a custom [`DubboFallback`](https://github.com/alibaba/Sentinel/blob/master/sentinel-adapter/sentinel-dubbo-adapter/src/main/java/com/alibaba/csp/sentinel/adapter/dubbo/fallback/DubboFallback.java) interface and register it through `DubboFallbackRegistry`. By d [...]
## Comparison Between Sentinel and Hystrix
diff --git a/content/en/blog/news/apache-dubbo-2019-2020.md b/content/en/blog/news/apache-dubbo-2019-2020.md
index 38b84697886..ce6bf61ca0c 100644
--- a/content/en/blog/news/apache-dubbo-2019-2020.md
+++ b/content/en/blog/news/apache-dubbo-2019-2020.md
@@ -119,7 +119,7 @@ Version 2.7 has also made significant strides in performance optimization, with
- In terms of optimizing the consumer thread model, applications that consume a large number of services, like gateway applications, see a significant improvement in system stability and performance. The overall working principle diagram after optimization is shown below; specific analyses can be referenced in the previously published article: [“Consumer Thread Pool Model”](/en/docsv2.7/user/examples/consumer-threadpool/)
+ In terms of optimizing the consumer thread model, applications that consume a large number of services, like gateway applications, see a significant improvement in system stability and performance. The overall working principle diagram after optimization is shown below; specific analyses can be referenced in the previously published article: [“Consumer Thread Pool Model”](/zh-cn/docsv2.7/user/examples/consumer-threadpool/)
Old thread model working principle:
diff --git a/content/en/blog/news/apachecon-asia-2023-summary.md b/content/en/blog/news/apachecon-asia-2023-summary.md
index bd8e45bbff4..ada6942ed37 100644
--- a/content/en/blog/news/apachecon-asia-2023-summary.md
+++ b/content/en/blog/news/apachecon-asia-2023-summary.md
@@ -7,13 +7,13 @@ description: >
---
This includes the complete transcripts of the speeches and highlights from the event. For more PPTs and video recordings, please follow the "apachedubbo" WeChat official account.
-* [Realizing Full Connectivity of Web, Mobile, and Backend Microservices Based on Triple Protocol](/en/blog/2023/10/07/基于-triple-实现-web-移动端后端全面打通/)
-* [Step-by-Step Guide to Deploying Dubbo Applications on Kubernetes - Best Practices for Apache Dubbo & Kubernetes](/en/blog/2023/10/07/手把手教你部署dubbo应用到kubernetes-apache-dubbo-kubernetes-最佳实践/)
-* [Exploration and Practice of Cloud-Native Observability in Apache Dubbo](/en/blog/2023/10/07/apache-dubbo-云原生可观测性的探索与实践/)
-* [Best Practices for Opensergo & Dubbo Microservices Governance](/en/blog/2023/10/07/opensergo-dubbo-微服务治理最佳实践/)
-* [One-Stop Distributed Transaction Solution under Seata Microservices Architecture](/en/blog/2023/10/07/seata-微服务架构下的一站式分布式事务解决方案/)
-* [10x Startup Speed Improvement: Deep Dive into Apache Dubbo - Static GraalVM Native Image](/en/blog/2023/10/07/启动速度提升10倍apache-dubbo-静态化-graalvm-native-image-深度解析/)
-* [Hybrid Cloud Data Cross-Network Practice Based on Dubbo by Government Procurement Cloud](/en/blog/2023/10/07/政采云基于dubbo的混合云数据跨网实践/)
+* [Realizing Full Connectivity of Web, Mobile, and Backend Microservices Based on Triple Protocol](/zh-cn/blog/2023/10/07/基于-triple-实现-web-移动端后端全面打通/)
+* [Step-by-Step Guide to Deploying Dubbo Applications on Kubernetes - Best Practices for Apache Dubbo & Kubernetes](/zh-cn/blog/2023/10/07/手把手教你部署dubbo应用到kubernetes-apache-dubbo-kubernetes-最佳实践/)
+* [Exploration and Practice of Cloud-Native Observability in Apache Dubbo](/zh-cn/blog/2023/10/07/apache-dubbo-云原生可观测性的探索与实践/)
+* [Best Practices for Opensergo & Dubbo Microservices Governance](/zh-cn/blog/2023/10/07/opensergo-dubbo-微服务治理最佳实践/)
+* [One-Stop Distributed Transaction Solution under Seata Microservices Architecture](/zh-cn/blog/2023/10/07/seata-微服务架构下的一站式分布式事务解决方案/)
+* [10x Startup Speed Improvement: Deep Dive into Apache Dubbo - Static GraalVM Native Image](/zh-cn/blog/2023/10/07/启动速度提升10倍apache-dubbo-静态化-graalvm-native-image-深度解析/)
+* [Hybrid Cloud Data Cross-Network Practice Based on Dubbo by Government Procurement Cloud](/zh-cn/blog/2023/10/07/政采云基于dubbo的混合云数据跨网实践/)
* Distributed Construction and Transformation Practice of Industrial and Commercial Bank of China
diff --git a/content/en/blog/news/dubbo-101.md b/content/en/blog/news/dubbo-101.md
index 8126ae4d57b..07316c30a35 100644
--- a/content/en/blog/news/dubbo-101.md
+++ b/content/en/blog/news/dubbo-101.md
@@ -385,6 +385,4 @@ Eventually, we give an outline of how to create a Dubbo application quickly base
---
1. [Getting Started Using JavaTM RMI](https://docs.oracle.com/javase/6/docs/technotes/guides/rmi/hello/hello-world.html)
-2. [Explicit target](/en/docs/v2.7/user/examples/explicit-target/)
-3. [Multicast Registry](/en/docs/v2.7/user/references/registry/multicast/)
-4. [Online QOS command](/en/docs/v2.7/user/references/qos/)
+
diff --git a/content/en/blog/news/dubbo-new-async.md b/content/en/blog/news/dubbo-new-async.md
index 80cb51d09bb..1fab263237a 100644
--- a/content/en/blog/news/dubbo-new-async.md
+++ b/content/en/blog/news/dubbo-new-async.md
@@ -11,7 +11,7 @@ Implementing the full asynchronous programming based on Dubbo, which is a new fe
## Asynchronous mode before version 2.6.x
-Dubbo Provides some asynchronous programming capabilities in 2.6.x and earlier versions, including [Asynchronous Call](/en/docs/v2.7/user/examples/async-call/), [Parameter Callback](/en/docs/v2.7/user/examples/callback-parameter/) and [Event Notification](/en/docs/v2.7/user/examples/events-notify/) on Consumer side. There are some brief introductions to the usage and Demo in the above document links.
+Dubbo Provides some asynchronous programming capabilities in 2.6.x and earlier versions, including [Asynchronous Call](/zh-cn/docsv2.7/user/examples/async-call/), [Parameter Callback](/zh-cn/docsv2.7/user/examples/callback-parameter/) and [Event Notification](/zh-cn/docsv2.7/user/examples/events-notify/) on Consumer side. There are some brief introductions to the usage and Demo in the above document links.
But the current asynchronous method has the following problems:
diff --git a/content/en/blog/news/introduction-to-dubbo-spi.md b/content/en/blog/news/introduction-to-dubbo-spi.md
index 9b97c18b0ef..201981c6270 100644
--- a/content/en/blog/news/introduction-to-dubbo-spi.md
+++ b/content/en/blog/news/introduction-to-dubbo-spi.md
@@ -220,7 +220,7 @@ Through the above 2 steps, we have already added a LoadBalance implementation na
```xml
<dubbo:reference id="helloService" interface="com.dubbo.spi.demo.api.IHelloService" loadbalance="demo" />
```
-Configure <loadbalance="demo"> in [dubbo:reference](dubbo:reference) at consumer part.
+Configure <loadbalance="demo"> in `dubbo:reference` at consumer part.
### 7.4 launch Dubbo
diff --git a/content/en/contact/_index.md b/content/en/contact/_index.md
index 8cb992266ca..276ce71bff8 100755
--- a/content/en/contact/_index.md
+++ b/content/en/contact/_index.md
@@ -50,7 +50,7 @@ Dubbo is released under the permissive Apache 2.0 license, follows the standard
<a href="https://github.com/apache/dubbo-awesome">
<img src="/imgs/contacts/github.png" alt="GitHub">
</a>
- <a href="../github/">GitHub ▶</a>
+ <p>GitHub ▶</p>
<p>Find the GitHub address of the corresponding language implementation or ecosystem project and participate in Dubbo's source code contribution</p>
</div>
{{< /card >}}
diff --git a/content/en/latest/facade-docs/how/quick-start.md b/content/en/latest/facade-docs/how/quick-start.md
index ecd0b5feb63..ac13ec9aa55 100644
--- a/content/en/latest/facade-docs/how/quick-start.md
+++ b/content/en/latest/facade-docs/how/quick-start.md
@@ -13,7 +13,7 @@ weight: 3
<div class="h-100 card shadow" href="#">
<div class="card-body">
<h4 class="card-title">
- <a href="/en/docs/v2.7/user/quick-start/">Quick start</a>
+ <a href="/zh-cn/docsv2.7/user/quick-start/">Quick start</a>
</h4>
<p>Dubbo Java SDK</p>
</div>
diff --git a/content/en/overview/home/_index.md b/content/en/overview/home/_index.md
index 4008d2e2f11..5a12ca85786 100644
--- a/content/en/overview/home/_index.md
+++ b/content/en/overview/home/_index.md
@@ -31,7 +31,7 @@ content:
links:
- "[Service Discovery & Configuration & Metadata Center](/overview/mannual/java-sdk/reference-manual/registry/)"
- "[HTTP Gateway](../tasks/ecosystem/gateway/)"
- - "[Ensuring Data Consistency](../tasks/ecosystem/transaction/)"
+ - "[Ensuring Data Consistency](/en/overview/mannual/golang-sdk/tutorial/transaction/)"
- "[Full-link Tracing](../tasks/observability/tracing/)"
- "[Custom Extensions](../tasks/extensibility/)"
- name: "SDK Reference Manual"
@@ -69,5 +69,5 @@ Follow the content below to quickly understand the features, advantages, and bes
<br/>
<br/>
-{{% docs/document_box %}}
+[//]: # ({{% docs/document_box %}})
diff --git a/content/en/overview/mannual/control-plane/test.md b/content/en/overview/mannual/control-plane/test.md
index 3991d3d88f3..c4360839a72 100644
--- a/content/en/overview/mannual/control-plane/test.md
+++ b/content/en/overview/mannual/control-plane/test.md
@@ -18,7 +18,7 @@ The service testing feature is usually provided for developers of Dubbo services
### Prepare Test Cases
1. Start the test case
- You can refer to [Quick Start](../../../quickstart/java/) to start a simple Dubbo service. For service testing, you only need to start the provider.
+ You can refer to [Quick Start](../../../quickstart/java/) to start a simple Dubbo service. For service testing, you only need to start the provider.
2. Query Services
diff --git a/content/en/overview/mannual/golang-sdk/quickstart/microservices.md b/content/en/overview/mannual/golang-sdk/quickstart/microservices.md
index 66911e3f6a7..077bc482d9d 100644
--- a/content/en/overview/mannual/golang-sdk/quickstart/microservices.md
+++ b/content/en/overview/mannual/golang-sdk/quickstart/microservices.md
@@ -16,7 +16,9 @@ In this example, we will continue to use Protobuf to develop the microservice ap
## Quick Run Example
### Download Example Source Code
-We maintain a series of dubbo-go usage examples in the [apache/dubbo-go-samples](https://github.com/apache/dubbo-go-samples/) repository to help users quickly learn how to use dubbo-go.
+We maintain a series of dubbo-go usage examples in the <a href="https://github.com/apache/dubbo-go-samples/" target="_blank">apache/dubbo-go-samples</a> repository to help users quickly learn how to use dubbo-go.
+
+You can <a href="https://github.com/apache/dubbo-go-samples/archive/refs/heads/master.zip" target="_blank">download the example zip package and extract it</a>, or clone the repository:
```shell
$ git clone --depth 1 https://github.com/apache/dubbo-go-samples
diff --git a/content/en/overview/mannual/java-sdk/_index.md b/content/en/overview/mannual/java-sdk/_index.md
index b1cbfd8a81d..81a534ff387 100755
--- a/content/en/overview/mannual/java-sdk/_index.md
+++ b/content/en/overview/mannual/java-sdk/_index.md
@@ -19,7 +19,7 @@ content:
name: '[Version Migration Guide](reference-manual/upgrades-and-compatibility/)'
- Historical Version Documentation:
- description: Historical Version Documentation
- name: '[2.x and Earlier Version Documentation](/en/docsv2.7/)'
+ name: '[2.x and Earlier Version Documentation](/zh-cn/docsv2.7/)'
description: Java SDK Manual
hide_feedback: true
hide_summary: true
diff --git a/content/en/overview/mannual/java-sdk/quick-start/deploy.md b/content/en/overview/mannual/java-sdk/quick-start/deploy.md
index 9198d81efd5..61cf18434d1 100644
--- a/content/en/overview/mannual/java-sdk/quick-start/deploy.md
+++ b/content/en/overview/mannual/java-sdk/quick-start/deploy.md
@@ -11,10 +11,10 @@ weight: 3
In the previous article, we created a Dubbo application from scratch and detailed its code structure. Next, we will learn how to deploy this Dubbo application.
This article will explain the deployment of Dubbo applications based on a Kubernetes cluster, and the deployment architecture is shown in the diagram below.
-![Dubbo+Kubernetes+Nacos Deployment Architecture]()
+!`Dubbo+Kubernetes+Nacos Deployment Architecture`
{{% alert title="Note" color="info" %}}
-In real-world usage, the deployment environment may vary widely, including Kubernetes Services, Service Mesh, virtual machines, and more. Please refer to [Deployment Documentation]() for more detailed content.
+In real-world usage, the deployment environment may vary widely, including Kubernetes Services, Service Mesh, virtual machines, and more. Please refer to `Deployment Documentation` for more detailed content.
{{% /alert %}}
## Prerequisites
diff --git a/content/en/overview/mannual/java-sdk/quick-start/starter.md b/content/en/overview/mannual/java-sdk/quick-start/starter.md
index 69ae8670b90..382873e8496 100644
--- a/content/en/overview/mannual/java-sdk/quick-start/starter.md
+++ b/content/en/overview/mannual/java-sdk/quick-start/starter.md
@@ -81,7 +81,7 @@ Open pom.xml, and you can see the core dependencies related to Dubbo in the samp
</dependencies>
```
-Among them, `dubbo-spring-boot-starter` and `dubbo-zookeeper-spring-boot-starter` introduce the dependencies related to the Dubbo kernel framework and Zookeeper client respectively. More content can be viewed in the [list of Spring Boot Starters supported by Dubbo]().
+Among them, `dubbo-spring-boot-starter` and `dubbo-zookeeper-spring-boot-starter` introduce the dependencies related to the Dubbo kernel framework and Zookeeper client respectively. More content can be viewed in the `list of Spring Boot Starters supported by Dubbo`.
### Service Definition
@@ -173,6 +173,6 @@ mvn clean deploy
```
## More Content
-- Next, you can [quickly deploy Dubbo applications to microservice clusters]()
-- Dubbo has built-in capabilities such as service discovery, load balancing, and traffic control rules. Learn [how to configure more service governance capabilities]()
+- Next, you can `quickly deploy Dubbo applications to microservice clusters`
+- Dubbo has built-in capabilities such as service discovery, load balancing, and traffic control rules. Learn `how to configure more service governance capabilities`
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/architecture/dubbo-spi.md b/content/en/overview/mannual/java-sdk/reference-manual/architecture/dubbo-spi.md
index ad7db87fdb3..0e5b0e1160e 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/architecture/dubbo-spi.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/architecture/dubbo-spi.md
@@ -18,7 +18,7 @@ The extension mechanism in Dubbo is similar to the <a href="https://www.baeldung
* Adds [IOC](#23-ioc-mechanism), [AOP](#24-aop-mechanism) capabilities.
* Adds sorting capabilities.
* Adds conditional activation capabilities.
-* Provides a series of more flexible APIs, such as [getting all SPI extension implementations](./#21-getting-all-extension-implementations), [querying a specific extension implementation by name](./#211-getting-all-extensions), querying extensions by type, and querying extension implementations that match conditions.
+* Provides a series of more flexible APIs, such as `getting all SPI extension implementations`, `querying a specific extension implementation by name`, querying extensions by type, and querying extension implementations that match conditions.
### 1.1 Definition of SPI
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/config-center/_index.md b/content/en/overview/mannual/java-sdk/reference-manual/config-center/_index.md
index 0375023f4ef..6d1b3dff742 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/config-center/_index.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/config-center/_index.md
@@ -17,7 +17,7 @@ weight: 6
The configuration center (config-center) in Dubbo can undertake two types of responsibilities:
-1. [External configuration](../config/principle/#33-external-configuration): centralized storage of startup configurations (simply understood as external storage of dubbo.properties).
+1. [External configuration](../config/principle#33-external-configuration): centralized storage of startup configurations (simply understood as external storage of dubbo.properties).
2. Storage of traffic governance rules.
Please refer to the specific extension implementations to understand how to enable the configuration center.
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/config-center/introduction.md b/content/en/overview/mannual/java-sdk/reference-manual/config-center/introduction.md
index 4d6d6003321..47f304daac4 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/config-center/introduction.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/config-center/introduction.md
@@ -13,7 +13,7 @@ weight: 1
The Config Center in Dubbo has two main responsibilities:
-1. [Externalized Configuration](/en/overview/mannual/java-sdk/reference-manual/config/principle/#33-Externalized-Configuration): Centralized storage for startup configurations (simplified as external storage of dubbo.properties).
+1. [Externalized Configuration](/en/overview/mannual/java-sdk/reference-manual/config/principle#33-external-configuration): Centralized storage for startup configurations (simplified as external storage of dubbo.properties).
2. Storage of traffic governance rules.
Please refer to specific extension implementations to learn how to enable the Config Center.
@@ -22,7 +22,7 @@ It is worth noting that the Dubbo dynamic configuration center defines two diffe
* namespace - Configuration namespace, default value `dubbo`. The namespace is usually used for multi-tenant isolation, logically isolating different users, different environments, or completely unrelated sets of configurations, as opposed to physical isolation, where different namespaces still use the same physical cluster.
* group - Configuration group, default value `dubbo`. The `group` is typically used to classify a set of configuration items of the same type/purpose, providing further isolation of configuration items under the `namespace`.
-Refer to [Configuration Instructions - Configuration Item Manual](/en/overview/mannual/java-sdk/reference-manual/config/properties/#dubboconfig-center) for more configuration items available in the config-center beyond namespace and group.
+Refer to [Configuration Instructions - Configuration Item Manual](/en/overview/mannual/java-sdk/reference-manual/config/properties#config-center) for more configuration items available in the config-center beyond namespace and group.
{{% alert title="Using the Registry Center as the Default Config Center" color="info" %}}
When using Zookeeper or Nacos as a registry center without explicitly configuring a config center, the Dubbo framework defaults to using Zookeeper or Nacos as the config center for service governance purposes.
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/config-center/nacos.md b/content/en/overview/mannual/java-sdk/reference-manual/config-center/nacos.md
index 51aeadf395f..0cf6d6719f0 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/config-center/nacos.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/config-center/nacos.md
@@ -14,14 +14,14 @@ weight: 3
* Understand [Basic Development Steps of Dubbo](/en/overview/mannual/java-sdk/quick-start/starter/)
* Install and start [Nacos](/en/overview/reference/integrations/nacos/)
-> When Dubbo uses version `3.0.0` or above, Nacos version `2.0.0` or above is required. Please refer to [nacos registry]( /en/overview/mannual/java-sdk/reference-manual/registry/nacos/#12-nacos-version) for Nacos version compatibility.
+> When Dubbo uses version `3.0.0` or above, Nacos version `2.0.0` or above is required. Please refer to [nacos registry]( /en/overview/mannual/java-sdk/reference-manual/registry/nacos#Nacos-Version) for Nacos version compatibility.
## 2 Instructions
### 2.1 Add Maven Dependency
If the project has already enabled Nacos as a registry, no additional configuration is required.
-If Nacos registry is not enabled, please refer to [Add Nacos dependency for registry](/en/overview/mannual/java-sdk/reference-manual/registry/nacos/#11-add-dependency).
+If Nacos registry is not enabled, please refer to [Add Nacos dependency for registry](/en/overview/mannual/java-sdk/reference-manual/registry/nacos#11-Add-Dependency).
### 2.2 Enable Nacos Configuration Center
```xml
@@ -49,10 +49,10 @@ ConfigCenterConfig configCenter = new ConfigCenterConfig();
configCenter.setAddress("nacos://127.0.0.1:8848");
```
-For `address` format, please refer to [Nacos Registry - Enable Configuration](../../registry/nacos/#22-configure-and-enable-nacos)
+For `address` format, please refer to [Nacos Registry - Enable Configuration](../../registry/nacos#22-configure-and-enable-nacos)
## 3 Advanced Configuration
-To enable authentication, please refer to [Nacos Registry - Enable Authentication](../../registry/nacos/#31-authentication)
+To enable authentication, please refer to [Nacos Registry - Enable Authentication](../../registry/nacos#22-configure-and-enable-nacos)
### 3.1 Externalized Configuration
#### 3.1.1 Global Externalized Configuration
@@ -101,7 +101,7 @@ dubbo
For the configuration center, `group` and `namespace` should be consistent across the company (cluster) and avoid different values for different applications.
### 3.3 Nacos Extended Configuration
-For more Nacos sdk/server supported parameter configurations, refer to [Nacos Registry - More Configurations](../../registry/nacos/#35-more-configurations)
+For more Nacos sdk/server supported parameter configurations, refer to [Nacos Registry - More Configurations](../../registry/nacos)
## 4 Traffic Governance Rules
For Nacos, all traffic governance rules and externalized configurations should be globally visible, thus applications in the same logical cluster must use the same namespace and group. The default value for namespace is `public` and the default value for group is `dubbo`. Applications must not modify the namespace and group without maintaining global consistency.
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/config-center/zookeeper.md b/content/en/overview/mannual/java-sdk/reference-manual/config-center/zookeeper.md
index 85ee88f387c..43e834bb368 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/config-center/zookeeper.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/config-center/zookeeper.md
@@ -21,7 +21,7 @@ View the [complete sample code](https://github.com/apache/dubbo-samples/tree/mas
### 2.1 Add Maven Dependencies
If the project has already enabled Zookeeper as the registry, no additional configurations are necessary.
-If Zookeeper is not used as the registry, refer to [Add Zookeeper related dependencies for the registry](/en/overview/mannual/java-sdk/reference-manual/registry/zookeeper/#11-Add-Maven-dependencies).
+If Zookeeper is not used as the registry, refer to [Add Zookeeper related dependencies for the registry](/en/overview/mannual/java-sdk/reference-manual/registry/zookeeper#11-Add-Maven-dependencies).
### 2.2 Enable Zookeeper Configuration Center
```xml
@@ -49,10 +49,10 @@ ConfigCenterConfig configCenter = new ConfigCenterConfig();
configCenter.setAddress("zookeeper://127.0.0.1:2181");
```
-For the format of `address`, refer to [zookeeper registry - enable configuration](../../registry/zookeeper/#13-Configure-and-enable-Zookeeper)
+For the format of `address`, refer to [zookeeper registry - enable configuration](../../registry/zookeeper#13-Configure-and-enable-Zookeeper)
## 3 Advanced Configuration
-To enable authentication and authorization, refer to [zookeeper registry - enable authentication and authorization](../../registry/zookeeper/#21-Authentication-and-authorization)
+To enable authentication and authorization, refer to [zookeeper registry - enable authentication and authorization](../../registry/zookeeper#21-Authentication-and-authorization)
### 3.1 Customize Externalized Configuration Key
**1. Enable externalized configuration and specify key**
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/config/principle.md b/content/en/overview/mannual/java-sdk/reference-manual/config/principle.md
index fef59636133..2d20c9bbdce 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/config/principle.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/config/principle.md
@@ -504,7 +504,7 @@ The search is conducted from high to low priority; if a preceding prefix propert
-### 3.3 Externalized Configuration
+### 3.3 Externalized Configuration {#33-external-configuration}
One of the aims of externalized configuration is to achieve centralized management of configurations. There are many mature professional configuration systems in the industry, such as Apollo and Nacos. What Dubbo does primarily is ensure proper functionality with these systems.
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/config/properties.md b/content/en/overview/mannual/java-sdk/reference-manual/config/properties.md
index bed019fb861..58834ca8230 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/config/properties.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/config/properties.md
@@ -21,7 +21,7 @@ weight: 6
| JVM Parameter | Example Value | Description |
| --- | --- | --- |
-| dubbo.{config-name}.{property} | -Ddubbo.application.name="dubbo-demo"<br/><br/>-Ddubbo.registry.address="nacos://host:port"<br/><br/>-Ddubbo.protocol.port="20880"<br/><br/>...... | Dubbo supports specifying [all configuration items](aaa) in the JVM parameter format. Here, `config` refers to items such as application, registry, protocol, and `property` refers to specific properties within each configuration item. |
+| dubbo.{config-name}.{property} | -Ddubbo.application.name="dubbo-demo"<br/><br/>-Ddubbo.registry.address="nacos://host:port"<br/><br/>-Ddubbo.protocol.port="20880"<br/><br/>...... | Dubbo supports specifying all configuration items in the JVM parameter format. Here, `config` refers to items such as application, registry, protocol, and `property` refers to specific properties within each configuration item. |
| dubbo.resolve.file | -Ddubbo.resolve.file=/home/ken/.../dubbo-resolve.properties | Specifies the direct connection URL for each interface in the file, e.g., org.apache.dubbo.demo.DemoService=tri://127.0.0.1:50051/org.apache.dubbo.demo.DemoService?xxx=xxx |
| org.graalvm.nativeimage.imagecode | | [https://github.com/oracle/graal/blob/master/sdk/src/org.graalvm.nativeimage/src/org/graalvm/nativeimage/ImageInfo.java](https://github.com/oracle/graal/blob/master/sdk/src/org.graalvm.nativeimage/src/org/graalvm/nativeimage/ImageInfo.java) |
| dubbo.properties.file | -Ddubbo.properties.file=foo.properties | Specifies the properties configuration file path, which can be an absolute path or a classpath-relative path. Default value is `dubbo.properties`. |
@@ -60,7 +60,7 @@ weight: 6
| Environment Variable | Example Value | Description |
| --- | --- | --- |
-| DUBBO_{CONFIG-NAME}.{PROPERTY} | DUBBO_APPLICATION_NAME="dubbo-demo"<br/><br/>DUBBO_REGISTRY_ADDRESS="nacos://host:port"<br/><br/>DUBBO_PROTOCOL_PORT="20880"<br/><br/>...... | Dubbo supports specifying [all configuration items](aaa) as environment variables. `CONFIG-NAME` refers to items such as application, registry, protocol, and `PROPERTY` refers to specific properties within each item. |
+| DUBBO_{CONFIG-NAME}.{PROPERTY} | DUBBO_APPLICATION_NAME="dubbo-demo"<br/><br/>DUBBO_REGISTRY_ADDRESS="nacos://host:port"<br/><br/>DUBBO_PROTOCOL_PORT="20880"<br/><br/>...... | Dubbo supports specifying all configuration items as environment variables. `CONFIG-NAME` refers to items such as application, registry, protocol, and `PROPERTY` refers to specific properties within each item. |
| DUBBO_DEFAULT_SERIALIZATION | DUBBO_DEFAULT_SERIALIZATION="hessian2" | Sets the default serialization method for the framework, e.g., `hessian2`, `fastjson2`, `msgpack`. |
| DUBBO2_COMPACT_ENABLE | DUBBO2_COMPAT_ENABLE="true" | |
| DUBBO_ENV_KEYS | DUBBO_LABELS="tag1=value1; tag2=value2" | `tag1=value1` will be reported as an additional parameter to the URL, serving as a system environment variable for instance tagging, etc. |
@@ -82,7 +82,7 @@ weight: 6
Regardless of whether you are using Spring Boot, XML, annotations, or APIs to write Dubbo applications, you can refer to the table below to understand the specific meaning of each configuration item.
-### dubbo.tracing.baggage.correlation
+### dubbo.tracing.baggage.correlation {#dubbo.tracing.baggage.correlation}
**Class:** `org.apache.dubbo.config.nested.BaggageConfig$Correlation`
|Key|Type|Description|Default value|Deprecation|
@@ -260,7 +260,7 @@ Regardless of whether you are using Spring Boot, XML, annotations, or APIs to wr
| trust-serialize-class-level| java.lang.Integer| The trust level for serialized classes.| | |
| version| java.lang.String| The application version.| | |
-### dubbo.config-center
+### dubbo.config-center {#config-center}
**Class:** `org.apache.dubbo.config.ConfigCenterConfig`
|Key|Type|Description|Default value|Deprecation|
@@ -364,7 +364,7 @@ Regardless of whether you are using Spring Boot, XML, annotations, or APIs to wr
| validation| java.lang.String| Enable JSR303 standard annotation validation for method parameters.| | |
| version| java.lang.String| Version of the remote service referenced by the consumer/provider.| | |
-### dubbo.metadata-report
+### dubbo.metadata-report {#dubbometadata-report}
**Class:** `org.apache.dubbo.config.MetadataReportConfig`
|Key|Type|Description|Default value|Deprecation|
@@ -618,7 +618,7 @@ Regardless of whether you are using Spring Boot, XML, annotations, or APIs to wr
| warmup| java.lang.Integer| Warm-up period for the service.| | |
| weight| java.lang.Integer| The service weight.| | |
-### dubbo.registry
+### dubbo.registry {#dubbo.registry}
**Class:** `org.apache.dubbo.config.RegistryConfig`
|Key|Type|Description|Default value|Deprecation|
@@ -698,7 +698,7 @@ Regardless of whether you are using Spring Boot, XML, annotations, or APIs to wr
| server-trust-cert-collection-path| java.lang.String| Path to the server's trust certificate collection file.| | |
| server-trust-cert-collection-path-stream| java.io.InputStream| Input stream for the server's trust certificate collection (if provided).| | |
-### dubbo.tracing
+### dubbo.tracing {#dubbo.tracing}
**Class:** `org.apache.dubbo.config.TracingConfig`
|Key|Type|Description|Default value|Deprecation|
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/config/spring/spring-boot.md b/content/en/overview/mannual/java-sdk/reference-manual/config/spring/spring-boot.md
index 1b1fd7cd744..5a40b80b1ba 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/config/spring/spring-boot.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/config/spring/spring-boot.md
@@ -32,14 +32,14 @@ dubbo:
### dubbo
* [**dubbo.application** - `org.apache.dubbo.config.ApplicationConfig`](../../properties#dubboapplication)
-* [**dubbo.config-center** - `org.apache.dubbo.config.ConfigCenterConfig`](../../properties#dubboconfig-center)
+* [**dubbo.config-center** - `org.apache.dubbo.config.ConfigCenterConfig`](../../properties#config-center)
* [**dubbo.consumer** - `org.apache.dubbo.config.ConsumerConfig`](../../properties#dubboconsumer)
* [**dubbo.metadata-report** - `org.apache.dubbo.config.MetadataReportConfig`](../../properties#dubbometadata-report)
* [**dubbo.protocol** - `org.apache.dubbo.config.ProtocolConfig`](../../properties#dubboprotocol)
* [**dubbo.provider** - `org.apache.dubbo.config.ProviderConfig`](../../properties#dubboprovider)
-* [**dubbo.registry** - `org.apache.dubbo.config.RegistryConfig`](../../properties#dubboregistry)
+* [**dubbo.registry** - `org.apache.dubbo.config.RegistryConfig`](../../properties#dubbo.registry)
* [**dubbo.metrics** - `org.apache.dubbo.config.MetricsConfig`](../../properties#dubbometrics)
-* [**dubbo.tracing** - `org.apache.dubbo.config.TracingConfig`](../../properties#dubbotracing)
+* [**dubbo.tracing** - `org.apache.dubbo.config.TracingConfig`](../../properties#dubbo.tracing)
* [**dubbo.ssl** - `org.apache.dubbo.config.SslConfig`](../../properties#dubbossl)
* ~~[**dubbo.monitor** - `org.apache.dubbo.config.MonitorConfig`](../../properties#dubbomonitor)~~
* ~~[**dubbo.module** - `org.apache.dubbo.config.ModuleConfig`](../../properties#dubbomodule)~~
@@ -52,7 +52,7 @@ dubbo:
* [**dubbo.metrics.prometheus.pushgateway** - `org.apache.dubbo.config.nested.PrometheusConfig$Pushgateway`](../../properties#dubbometricsprometheuspushgateway)
### dubbo.tracing
-* [**dubbo.tracing.baggage.correlation** - `org.apache.dubbo.config.nested.BaggageConfig$Correlation`](../../properties#dubbotracingbaggage.correlation)
+* [**dubbo.tracing.baggage.correlation** - `org.apache.dubbo.config.nested.BaggageConfig$Correlation`](../../properties#dubbo.tracing.baggage.correlation)
* [**dubbo.tracing.tracing-exporter.otlp-config** - `org.apache.dubbo.config.nested.ExporterConfig$OtlpConfig`](../../properties#dubbotracingtracing-exporterotlp-config)
* [**dubbo.tracing.tracing-exporter.zipkin-config** - `org.apache.dubbo.config.nested.ExporterConfig$ZipkinConfig`](../../properties#dubbotracingtracing-exporterzipkin-config)
* [**dubbo.tracing.baggage** - `org.apache.dubbo.config.nested.BaggageConfig`](../../properties#dubbotracingbaggage)
@@ -89,7 +89,7 @@ Here is the list of starters provided by the Dubbo official community (version 3
{{% alert title="Note" color="info" %}}
* For the versions of third-party components compatible with each starter, please refer to the [Component Version Mapping Table](/en/overview/mannual/java-sdk/versions/).
-* Each starter has corresponding application.yml configuration items; please refer to the above [Configuration Items List](./#Configuration%20Example) for detailed usage.
+* Each starter has corresponding application.yml configuration items; please refer to the above `Configuration Items List` for detailed usage.
{{% /alert %}}
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/faq/1/10.md b/content/en/overview/mannual/java-sdk/reference-manual/faq/1/10.md
index 9bcf422da0c..e1022d4bb72 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/faq/1/10.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/faq/1/10.md
@@ -23,5 +23,5 @@ weight: 10
This error often occurs together with error 1-9. Check if multiple Dubbo processes are using the same cache file or if multiple registries are specified to use the same cache file.
> See also
-[Configuration Reference Manual for the Registry](/en/overview/mannual/java-sdk/reference-manual/config/properties/#registry)
+[Configuration Reference Manual for the Registry](/en/overview/mannual/java-sdk/reference-manual/config/properties#dubbo.registry)
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/faq/1/7.md b/content/en/overview/mannual/java-sdk/reference-manual/faq/1/7.md
index 8109d210f2b..b4a706cb3b4 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/faq/1/7.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/faq/1/7.md
@@ -22,5 +22,5 @@ weight: 7
### Troubleshooting and Resolution Steps
> Please also refer to
-[Registry Center - Configuration Item Reference Manual](/en/overview/mannual/java-sdk/reference-manual/config/properties/#registry)
+[Registry Center - Configuration Item Reference Manual](/en/overview/mannual/java-sdk/reference-manual/config/properties#dubbo.registry)
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/faq/1/9.md b/content/en/overview/mannual/java-sdk/reference-manual/faq/1/9.md
index 171e0c75614..802fad6fc31 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/faq/1/9.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/faq/1/9.md
@@ -32,5 +32,5 @@ If `dubbo.registry.file` is not specified, the cache path for the registry servi
4. Investigate if the situation of "two registries using the same file storage" occurred and adjust accordingly.
> See also
-[Registry Configuration Reference Manual](/en/overview/mannual/java-sdk/reference-manual/config/properties/#registry)
+[Registry Configuration Reference Manual](/en/overview/mannual/java-sdk/reference-manual/config/properties#dubbo.registry)
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/faq/2/4.md b/content/en/overview/mannual/java-sdk/reference-manual/faq/2/4.md
index ecc6512c815..e1fab4e0f24 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/faq/2/4.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/faq/2/4.md
@@ -20,5 +20,6 @@ weight: 4
* Dubbo provides the SPI extension Merger interface, which aggregates responses from all downstream providers. Dubbo fails to load the configuration when loading user-defined extension Merger interfaces.
### Troubleshooting and Resolution Steps
-> Refer to the community SPI extension usage manual to check the implementation of the user-defined extension Merger interface [“SPI Extension Usage Manual”](/en/overview/mannaual/java-sdk/reference-manual/spi/) .
+> Refer to the community SPI extension usage manual to check the implementation of the user-defined extension Merger interface [“SPI Extension Usage Manual”](/en/overview/mannual/java-sdk/reference-manual/spi/) .
+
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/faq/7/7.md b/content/en/overview/mannual/java-sdk/reference-manual/faq/7/7.md
index bcb698346c3..4dbc6a2cd59 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/faq/7/7.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/faq/7/7.md
@@ -22,5 +22,5 @@ The QoS request is unauthorized to access the corresponding resource, which typi
### Troubleshooting and Resolution Steps
Check if the request is expected. If not expected, check for any sources of malicious attacks.
-> If it is expected, please refer to the article on [QoS Security](/en/overview/mannual/java-sdk/reference-manual/qos/overview/#%E5%AE%89%E5%85%A8) to configure the corresponding permission information.
+> If it is expected, please refer to the article on [QoS Security](/en/overview/mannual/java-sdk/reference-manual/qos/overview#security) to configure the corresponding permission information.
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/nacos.md b/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/nacos.md
index 29e81c853d1..d75655f0a0e 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/nacos.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/nacos.md
@@ -55,7 +55,7 @@ For the format of `address`, please refer to [Nacos Registry - Enable Configurat
## 3 Advanced Configuration
-For complete configuration parameters, please refer to [metadata-report-config](../../config/properties/#metadata-report-config).
+For complete configuration parameters, please refer to [metadata-report-config](/en/overview/mannual/java-sdk/reference-manual/config/properties#dubbometadata-report).
## 4 Working Principle
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/overview.md b/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/overview.md
index 3a4179f51a3..a47290a2a9f 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/overview.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/overview.md
@@ -17,7 +17,7 @@ The Metadata Center provides access to two types of metadata in Dubbo:
## 1 Address Discovery Metadata
Dubbo3 introduces the [application-level service discovery mechanism](/en/overview/core-features/service-discovery/) to address performance issues in heterogeneous microservice systems and large-scale cluster practices. Application-level service discovery will fully replace the interface-level service discovery of version 2.x. To maintain Dubbo's usability oriented towards services/interfaces and flexibility in service governance, Dubbo has built a metadata mechanism around application-l [...]
-### 1.1 Interface-Application Mapping Relation
+### 1.1 Interface-Application Mapping Relation {#11-interface---application-mapping-relationship}
Dubbo has always been capable of precise address discovery, subscribing only to the list of services and addresses declared by the Consumer. Achieving precise address subscription in the application-level service discovery model is not easy, as the Dubbo Consumer only declares the list of interfaces to consume. Therefore, the Consumer needs to convert the interface into the Provider's application name for accurate service subscription.
For this, Dubbo must maintain this mapping of `interface name -> application name` in the metadata center, reported actively by the provider during startup in Dubbo3.
@@ -110,7 +110,7 @@ Using Zookeeper as an example, the interface configuration metadata is stored in
}
```
-## 2 Service Operation and Maintenance Metadata
+## 2 Service Operation and Maintenance Metadata {#2-service-operation-metadata}
The service operation and maintenance metadata reported by Dubbo is typically used by various operation and maintenance systems, such as service testing, gateway data mapping, and service static dependency analysis.
@@ -213,4 +213,3 @@ dubbo.metadata-report.sync.report=false ## optional, default is false
> If the metadata address (dubbo.metadata-report.address) is not configured, it will judge whether the protocol of the registry center supports the metadata center. If supported, it will use the registry center's address as the metadata center.
Please refer to [metadata-report](../../spi/description/metadata-report/) for details on how to extend custom third-party implementations.
-
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/zookeeper.md b/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/zookeeper.md
index b64d731cabe..1527479a55c 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/zookeeper.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/metadata-center/zookeeper.md
@@ -20,7 +20,7 @@ weight: 3
### 2.1 Adding Maven Dependency
If the project has already enabled Zookeeper as the registry center, no additional configuration is needed.
-If Zookeeper is not used as the registry center, please refer to [Add Zookeeper-related dependencies for the registry center](/en/overview/mannual/java-sdk/reference-manual/registry/zookeeper/#11-add-maven-dependency).
+If Zookeeper is not used as the registry center, please refer to [Add Zookeeper-related dependencies for the registry center](/en/overview/mannual/java-sdk/reference-manual/registry/zookeeper#11-Add-Maven-dependencies).
### 2.2 Enable Zookeeper Configuration Center
```xml
@@ -48,15 +48,15 @@ MetadataReportConfig metadataConfig = new MetadataReportConfig();
metadataConfig.setAddress("zookeeper://127.0.0.1:2181");
```
-For the format of `address`, please refer to [zookeeper register center - Enable Configuration](../../registry/zookeeper/#22-configure-and-enable-zookeeper)
+For the format of `address`, please refer to [zookeeper register center - Enable Configuration](/en/overview/mannual/java-sdk/reference-manual/registry/zookeeper#13-Configure-and-enable-Zookeeper)
## 3 Advanced Configuration
-For complete configuration parameters, please refer to [metadata-report-config](/en/overview/mannual/java-sdk/reference-manual/config/properties/#dubbometadata-report).
+For complete configuration parameters, please refer to [metadata-report-config](/en/overview/mannual/java-sdk/reference-manual/config/properties#dubbometadata-report).
## 4 Working Principle
-### 4.1 [Service Operation Metadata](../overview/#2-service-operation-metadata)
+### 4.1 [Service Operation Metadata](../overview#2-service-operation-metadata)
Zookeeper stores data based on a tree structure, and its metadata information is located at the following nodes:
```text
@@ -106,7 +106,7 @@ dataLength = 219
numChildren = 0
```
-### 4.2 [Address Discovery - Interface-Application Name Mapping](../overview/#11-interface---application-mapping-relationship)
+### 4.2 [Address Discovery - Interface-Application Name Mapping](../overview#11-interface---application-mapping-relationship)
In Dubbo 3.0, the service introspection mechanism is used by default to achieve service discovery. For service introspection, you can refer to [Service Introspection](https://mercyblitz.github.io/2020/05/11/Apache-Dubbo-%E6%9C%8D%E5%8A%A1%E8%87%AA%E7%9C%81%E6%9E%B6%E6%9E%84%E8%AE%BE%E8%AE%A1/)
In short, the service introspection mechanism needs to find the corresponding application name through the interface name. This relationship can be one-to-many, meaning a service name may correspond to multiple different application names. In 3.0, the metadata center provides this mapping capability.
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/protocol/overview.md b/content/en/overview/mannual/java-sdk/reference-manual/protocol/overview.md
index d6300129d7e..9cb85804099 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/protocol/overview.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/protocol/overview.md
@@ -37,12 +37,12 @@ Here is the specific development, configuration, and runtime information for the
## Multi-Protocol Extensions
Below are the extension protocol implementations currently provided by the Dubbo official ecosystem. For information on extending more custom protocols, please refer to [SPI extension manual](/en/overview/mannual/java-sdk/reference-manual/spi/) or [usage tutorial - protocol extension](/en/overview/mannual/java-sdk/tasks/extensibility/protocol/) .
-| Protocol | Configuration Value | Description |
-| --- | --- | --- |
-| Hessian | hessian | RPC communication protocol defined by Hessian, see [Hessian Protocol](../others/hessian/) for details |
-| Spring HTTP | http | Private protocol based on HTTP defined by Spring, see [Hessian Protocol](../others/hessian/) for details |
+| Protocol | Configuration Value | Description |
+| --- | --- |-------------------------------------------------------------------------------------------------------------------------------|
+| Hessian | hessian | RPC communication protocol defined by Hessian, see [Hessian Protocol](../others/hessian/) for details |
+| Spring HTTP | http | Private protocol based on HTTP defined by Spring, see [Hessian Protocol](../others/hessian/) for details |
| Apache Thrift | thrift | Thrift protocol known for its high performance and multilingual support, see [Thrift Protocol](../others/thrift/) for details |
-| JsonRPC | jsonrpc | See [JsonRPC](../others/jsonrpc/) for details |
-| RMI | rmi | See [RMI Protocol](../others/rmi/) for details |
-| WebService | webservice | See [WebService Protocol](../others/webservice/) for details |
+| JsonRPC | jsonrpc | See `WIP JsonRPC` for details |
+| RMI | rmi | See [RMI Protocol](../others/rmi/) for details |
+| WebService | webservice | See [WebService Protocol](../others/webservice/) for details |
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/protocol/triple.md b/content/en/overview/mannual/java-sdk/reference-manual/protocol/triple.md
index 30a1266d979..f4f0b655066 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/protocol/triple.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/protocol/triple.md
@@ -21,7 +21,7 @@ Please refer to other parts of the documentation for the [triple protocol specif
When using the triple protocol, developers can define RPC services using either `Java Interface` or `Protobuf (IDL)`. Both definitions have equal protocol capabilities and only affect the programming experience and serialization methods, with the choice of development model depending on the user's business background.
### Java Interface
-**Suitable for Dubbo veteran users and development teams without cross-language requirements, with the advantage of low learning costs. [Dubbo2 legacy users can switch to this protocol at no cost]()**.
+Suitable for Dubbo veteran users and development teams without cross-language requirements, with the advantage of low learning costs. `Dubbo2 legacy users can switch to this protocol at no cost`.
Service definition example:
```java
@@ -32,11 +32,11 @@ public interface DemoService {
In this mode, serialization methods can include Hessian, JSON, Kryo, JDK, custom extensions, etc. The experience is similar to the older version of the Dubbo protocol, requiring only a change in one protocol configuration item, making migration from Dubbo protocol to triple smoother.
-Please check [advanced studies - communication protocols] for specific examples using [Java Interface + Triple protocol]().
+Please check [advanced studies - communication protocols] for specific examples using `Java Interface + Triple protocol`.
### Protobuf
-Defining services using Protobuf (IDL) is **suitable for development teams that currently or in the future have cross-language requirements. The same IDL service can be used for Java/Go/Node.js, but it has a higher learning cost**.
+Defining services using Protobuf (IDL) is suitable for development teams that currently or in the future have cross-language requirements. The same IDL service can be used for Java/Go/Node.js, but it has a higher learning cost.
```Protobuf
syntax = "proto3";
@@ -55,7 +55,7 @@ service Greeter{
}
```
-Using the [protoc compilation plugin provided by Dubbo](/en/overview/mannual/java-sdk/tasks/protocols/triple/idl/#generated-code-cannot-be-compiled), the above IDL service definition is precompiled into relevant stub code, which includes the interface definitions required by Dubbo; thus, the subsequent coding differs little, except that the plugin automatically generates the interface definitions compared to the earlier user-defined Java Interface mode.
+Using the [protoc compilation plugin provided by Dubbo](/en/overview/mannual/java-sdk/tasks/protocols/triple/idl#generated-code-cannot-be-compiled), the above IDL service definition is precompiled into relevant stub code, which includes the interface definitions required by Dubbo; thus, the subsequent coding differs little, except that the plugin automatically generates the interface definitions compared to the earlier user-defined Java Interface mode.
```java
// Generated by dubbo protoc plugin
@@ -68,7 +68,7 @@ public interface Greeter extends org.apache.dubbo.rpc.model.DubboStub {
}
```
-The Protobuf mode supports serialization modes of Protobuf Binary and Protobuf JSON. Lastly, please check [advanced studies - communication protocols] for specific examples of [Protobuf (IDL) + Triple protocol]().
+The Protobuf mode supports serialization modes of Protobuf Binary and Protobuf JSON. Lastly, please check `advanced studies - communication protocols` for specific examples of `Protobuf (IDL) + Triple protocol`.
#### 3. Which programming model should I use, and how to choose?
@@ -121,10 +121,10 @@ Both the client and server stream processing are application-specific. Since the
- Supports cancellation and timeouts
{{% /alert %}}
-For specific examples of Streaming, please refer to [Streaming communication](../triple/streaming/).
+For specific examples of Streaming, please refer to [Streaming communication](/en/overview/mannual/java-sdk/tasks/protocols/triple/streaming).
## REST Support
-By adding annotations to the Java interface, REST-style triple services can be published. A specific code example can be found <a href="" target="_blank">here</a>.
+By adding annotations to the Java interface, REST-style triple services can be published. A specific code example can be found here.
{{% alert title="Stream Semantics Guarantee" color="info" %}}
Currently, the REST protocol only supports the `Java Interface` service definition model, unlike Dubbo and the triple protocol. In REST scenarios, we need to add annotations to the Interface, supporting both Spring MVC and JAX_RS annotations.
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/qos/introduction/profiler.md b/content/en/overview/mannual/java-sdk/reference-manual/qos/introduction/profiler.md
index e384208d6c4..886f305470d 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/qos/introduction/profiler.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/qos/introduction/profiler.md
@@ -17,7 +17,7 @@ The performance sampling feature can detect the time consumption at various poin
This feature is divided into two modes: `simple profiler` and `detail profiler`. The `simple profiler` mode is enabled by default, while the `detail profiler` mode is disabled by default. The `detail profiler` collects additional information such as processing time for each filter and specific time consumption on protocols, compared to the `simple profiler`. If long processing times are found within the Dubbo framework while in `simple profiler`, the `detail profiler` can be enabled for [...]
-> [Request Time Sampling](../../../advanced-features-and-usage/performance/profiler/)
+> [Request Time Sampling](/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/profiler/)
### enableSimpleProfiler Command
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/qos/introduction/router-snapshot.md b/content/en/overview/mannual/java-sdk/reference-manual/qos/introduction/router-snapshot.md
index 93c466f5f29..b2b61286c1b 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/qos/introduction/router-snapshot.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/qos/introduction/router-snapshot.md
@@ -15,7 +15,7 @@ weight: 8
Many traffic governance capabilities in Dubbo are implemented based on the Router. In production environments, if traffic results do not meet expectations, you can use the router status command to check the router's status to locate potential issues.
-> [Router Status Collection](../../../advanced-features-and-usage/performance/router-snapshot/)
+> [Router Status Collection](/en/docs3-v2/java-sdk/advanced-features-and-usage/performance/router-snapshot/)
### getRouterSnapshot Command
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/registry/nacos.md b/content/en/overview/mannual/java-sdk/reference-manual/registry/nacos.md
index 6e3ae3b57d8..f60fa9b1e86 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/registry/nacos.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/registry/nacos.md
@@ -15,7 +15,7 @@ This example demonstrates automatic service discovery using Nacos as a registry
## 1 Basic Configuration
-### 1.1 Add Dependencies
+### 1.1 Add Dependencies {#11-Add-Dependency}
For Spring Boot applications, use the following spring-boot-starter:
```xml
@@ -47,7 +47,7 @@ Non-Spring Boot users can add dubbo and nacos-client dependencies:
</dependencies>
```
-### 1.2 Nacos Version Mapping
+### 1.2 Nacos Version Mapping {#Nacos-Version}
| Dubbo | Recommended Nacos Version | Nacos Compatibility Range |
| --- | --- | --- |
| 3.3.0 | 2.3.0 | 2.x |
@@ -75,7 +75,7 @@ or
<dubbo:registry address="nacos://localhost:8848" />
```
-## 2 Advanced Configuration
+## 2 Advanced Configuration {#22-configure-and-enable-nacos}
### 2.1 Authentication
@@ -141,7 +141,7 @@ dubbo:
parameters.register-consumer-url: true
```
-### 2.5 More Configurations
+### 2.5 More Configurations {#35-more-configurations]
Parameter Name | Description | Default Value
---|---|---
@@ -204,5 +204,4 @@ The application-level service discovery "service name" is the application name.
### 3.4 Heartbeat Detection
-### 3.5
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/registry/overview.md b/content/en/overview/mannual/java-sdk/reference-manual/registry/overview.md
index 0c0c267d75a..bc1f16d26e2 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/registry/overview.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/registry/overview.md
@@ -36,7 +36,7 @@ For cluster format addresses, you can use the backup parameter:
In versions 3.3.0 and later, the registry is optional. However, in versions prior to 3.3.0, Dubbo applications must specify registry configuration, even if the registry is not enabled (it can be set to an empty address: address='N/A').
{{% /alert %}}
-Each registry component has its unique configurations to control namespaces, groups, authentication, etc. For more details, refer to the [Registry Configuration Reference Manual](/en/overview/mannual/java-sdk/reference-manual/config/properties/#registry) or extend through parameters.
+Each registry component has its unique configurations to control namespaces, groups, authentication, etc. For more details, refer to the [Registry Configuration Reference Manual](/en/overview/mannual/java-sdk/reference-manual/config/properties#dubbo.registry) or extend through parameters.
## Configuration Center and Metadata Center
The configuration center and metadata center are components that Dubbo relies on to implement advanced service governance capabilities, such as traffic control rules. Compared to the registry, the configurations for these two components are typically optional.
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/registry/service-discovery-application-vs-interface.md b/content/en/overview/mannual/java-sdk/reference-manual/registry/service-discovery-application-vs-interface.md
index 1377edd8c2a..a06809a890b 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/registry/service-discovery-application-vs-interface.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/registry/service-discovery-application-vs-interface.md
@@ -99,9 +99,9 @@ If your cluster is sufficiently large and has encountered performance bottleneck
1. Simplify the number of provider and consumer configurations entering the registration center.
2. Store certain configuration items in other forms. These configuration items need to satisfy: they do not exist on the service call path, and they do not belong to the core link of the registration center (service query, service list).
-Service configuration items in the Dubbo provider have nearly [30 configuration items](/en/docs/references/xml/dubbo-parameter). Excluding the needs for registration center service governance, a substantial number of configuration items are used internally by the provider and do not need to be passed to consumers. This data does not need to enter the registration center but can be persistently stored in key-value format.
+Service configuration items in the Dubbo provider have nearly [30 configuration items](/en/overview/mannual/java-sdk/reference-manual/config/properties). Excluding the needs for registration center service governance, a substantial number of configuration items are used internally by the provider and do not need to be passed to consumers. This data does not need to enter the registration center but can be persistently stored in key-value format.
-Similarly, there are [20+ configuration items](/en/docs/references/xml/dubbo-consumer) in the Dubbo consumer. Within the registration center, the consumer list only needs to focus on a small number of configurations such as application, version, group, IP, and Dubbo version, while other configurations can also be persisted in key-value format. Registering this data on a service basis leads to data volume inflation, resulting in increased network overhead and reduced performance for the r [...]
+Similarly, there are [20+ configuration items](/en/overview/mannual/java-sdk/reference-manual/config/properties) in the Dubbo consumer. Within the registration center, the consumer list only needs to focus on a small number of configurations such as application, version, group, IP, and Dubbo version, while other configurations can also be persisted in key-value format. Registering this data on a service basis leads to data volume inflation, resulting in increased network overhead and red [...]
{{% alert title="Note" color="warning" %}}
Simplifying registration center configurations is only supported in versions after 2.7.
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/registry/zookeeper.md b/content/en/overview/mannual/java-sdk/reference-manual/registry/zookeeper.md
index f8575abb1f2..a556bed7b9b 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/registry/zookeeper.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/registry/zookeeper.md
@@ -14,7 +14,7 @@ weight: 3
This example demonstrates how Zookeeper is used as a registration center for automatic service discovery, based on a Spring Boot application. You can view the [full example code](https://github.com/apache/dubbo-samples/tree/master/3-extensions/registry/dubbo-samples-zookeeper).
## 1 Basic Configuration
-### 1.1 Add Maven Dependencies
+### 1.1 Add Maven Dependencies {#11-Add-Maven-dependencies}
Add dependencies like dubbo and zookeeper. The `dubbo-spring-boot-starter` will automatically add Zookeeper-related client dependencies for the application, reducing the cost of using Zookeeper. If you encounter version compatibility issues, you can also choose to add Curator, Zookeeper Client, and other dependencies manually.
For Spring Boot applications, you can use the following dependencies:
@@ -82,7 +82,7 @@ Dubbo provides a helper management component for Zookeeper dependencies, allowin
{{% /alert %}}
-### 1.3 Configure and Enable Zookeeper
+### 1.3 Configure and Enable Zookeeper {#13-Configure-and-enable-Zookeeper}
```yaml
# application.yml
dubbo
@@ -108,7 +108,7 @@ Protocols and addresses can also be configured separately, such as
`<dubbo:registry protocol="zookeeper" address="10.20.153.10:2181,10.20.153.11:2181,10.20.153.12:2181" />`
## 2 Advanced Configuration
-### 2.1 Authentication and Authorization
+### 2.1 Authentication and Authorization {#21-Authentication-and-authorization}
If Zookeeper has authentication enabled, Dubbo supports specifying the username and password for identity verification.
@@ -145,7 +145,7 @@ dubbo
session: 60 * 1000* # Session timeout, default is 60s
```
-The Zookeeper registration center also supports other control parameters, please refer to the [Registry configuration manual](../../config/properties#registry)
+The Zookeeper registration center also supports other control parameters, please refer to the [Registry configuration manual](../../config/properties#dubbo.registry)
## 3 Working Principle
In the previous section, we explained the differences between application-level service discovery and interface-level service discovery. In the Zookeeper implementation, their storage structures differ significantly. Overall, the Zookeeper registration center implementation supports the following high availability capabilities:
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/serialization/triple/protobuf.md b/content/en/overview/mannual/java-sdk/reference-manual/serialization/triple/protobuf.md
index 062d07080d4..2e0cd3b01f1 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/serialization/triple/protobuf.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/serialization/triple/protobuf.md
@@ -10,7 +10,7 @@ weight: 1
## 1 Introduction
-<a href="" target="_blank">Protobuf (Protocol Buffers)</a> is a lightweight and efficient data interchange format developed by Google, used for the serialization, deserialization, and transmission of structured data. Compared to text formats like XML and JSON, Protobuf has smaller data sizes, faster parsing speeds, and better scalability.
+[Protobuf (Protocol Buffers)](https://developers.google.com/protocol-buffers) is a lightweight and efficient data interchange format developed by Google, used for the serialization, deserialization, and transmission of structured data. Compared to text formats like XML and JSON, Protobuf has smaller data sizes, faster parsing speeds, and better scalability.
## 2 Usage
**When using [Protobuf (IDL) to develop triple communication services](/en/overview/mannual/java-sdk/tasks/protocols/triple/idl/), the Dubbo server will automatically enable support for protobuf and protobuf-json serialization modes.**
@@ -83,4 +83,3 @@ or
```xml
<dubbo:protocol name="tri" />
```
-
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/spi/spi-list.md b/content/en/overview/mannual/java-sdk/reference-manual/spi/spi-list.md
index dff8a694c02..4e86dd7da3a 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/spi/spi-list.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/spi/spi-list.md
@@ -8,7 +8,7 @@ weight: 2
Dubbo defines many extension points within the framework, so **when you find that the official library cannot meet business needs and wish to provide customization for the Dubbo framework, please first refer to the following extension point definitions to see if you can achieve non-intrusive customization of the Dubbo framework by providing extension implementations**.
-For specific information, please refer to the [Summary of Dubbo SPI Extension Definitions](./#extension-summary) below this article.
+For specific information, please refer to the `Summary of Dubbo SPI Extension Definitions` below this article.
<img src="/imgs/v3/concepts/extension-use.png" style="max-width:600px;height:auto;">
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration-triple.md b/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration-triple.md
index 3a07401e4dc..df04d34b66d 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration-triple.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration-triple.md
@@ -12,7 +12,7 @@ weight: 2
{{% alert title="Note" color="warning" %}}
* The content of this document is not mandatory for upgrading Dubbo3. You can simply upgrade the framework and continue using the Dubbo communication protocol.
-* If you are a new Dubbo user, it is highly recommended to directly [use the Triple protocol](/en/overview/mannual/java-sdk/tasks/protocol/).
+* If you are a new Dubbo user, it is highly recommended to directly [use the Triple protocol](/en/overview/mannual/java-sdk/tasks/protocols/).
{{% /alert %}}
This document is suitable for users whose services are already running on the Dubbo protocol. Please first refer to the previous document [How to Upgrade from Dubbo2 to Dubbo3](../migration/) to complete the framework version upgrade, and then follow these steps for a smooth migration to the Triple protocol with minimal changes.
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration.md b/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration.md
index b82edb8eef9..596604108b7 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration.md
@@ -53,7 +53,7 @@ If the previous application was Spring Boot, it is recommended to use the follow
{{% alert title="Upgrade Notes for Spring and Spring Boot related to Dubbo3" color="warning" %}}
Dubbo3 supports a wide range of compatible Spring and Spring Boot versions:
* It supports both Spring 3.x ~ Spring 5.x versions as well as Spring Boot 1.x ~ Spring Boot 2.x. If you encounter issues upgrading to higher versions of Spring or Spring Boot, you can remove the high-version Spring dependencies propagated by `dubbo-spring-boot-starter` or `dubbo`, and specify the acceptable Spring version dependencies for the project.
-* Spring Boot 3.x and Spring 6 versions require JDK 17 or higher; please refer to the [Dubbo Spring Boot Manual]() for more details.
+* Spring Boot 3.x and Spring 6 versions require JDK 17 or higher; please refer to the `Dubbo Spring Boot Manual` for more details.
{{% /alert %}}
### Step 2: Upgrade Other Component Dependencies
@@ -127,7 +127,7 @@ Dubbo3 supports a wide range of compatible Spring and Spring Boot versions:
In addition to the registry, if you are using other features of Dubbo and depend on third-party components to support these features, you need to upgrade the corresponding component versions based on specific circumstances to ensure that the components work with Dubbo3.
{{% alert title="Check Third-Party Component Versions" color="info" %}}
-The goal is to confirm that the third-party dependencies in the project can work normally with Dubbo3 (maintain API compatibility). Typically, there aren't too many third-party component dependencies in Dubbo applications, so just confirm as needed. Additionally, you can refer to [Dubbo3 Version Dependencies]() to confirm suitable component versions.
+The goal is to confirm that the third-party dependencies in the project can work normally with Dubbo3 (maintain API compatibility). Typically, there aren't too many third-party component dependencies in Dubbo applications, so just confirm as needed. Additionally, you can refer to `Dubbo3 Version Dependencies` to confirm suitable component versions.
{{% /alert %}}
### Step 3: Compatibility Checks
diff --git a/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/version/2.x-to-3.x-compatibility-guide.md b/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/version/2.x-to-3.x-compatibility-guide.md
index 4b6b0f59a1e..61ffc6f88b7 100644
--- a/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/version/2.x-to-3.x-compatibility-guide.md
+++ b/content/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/version/2.x-to-3.x-compatibility-guide.md
@@ -23,9 +23,11 @@ Dubbo 3 maintains the classic architecture of 2.x, focusing on inter-process com
New features in Dubbo 3.0 include:
* **New address discovery model (Application-level service discovery).**
- * See [Application-level service discovery migration example](/en/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-samples/).
- * See [Migration steps for application-level service discovery](/en/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/migration-service-discovery/)
- * See [Description of address migration rules for application-level service discovery](/en/overview/mAnnual/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-rule/)
+ * See [Application-level service discovery migration example](/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility).
+ * See [Migration steps for application-level service discovery](/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility)
+
+[//]: # ( FIXME:缺少翻译)
+ * See [Description of address migration rules for application-level service discovery](/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility)
* **Next-generation HTTP/2 based Triple protocol.**
* See [Triple protocol migration steps](/en/overview/mannual/java-sdk/upgrades-and-compatibility/migration-triple/)
* See [Using Triple protocol](/en/overview/mannual/java-sdk/reference-manual/protocol/triple/guide/)
diff --git a/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-kubernetes-service.md b/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-kubernetes-service.md
index 0bf2b8e52ae..feff6e14523 100644
--- a/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-kubernetes-service.md
+++ b/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-kubernetes-service.md
@@ -8,7 +8,7 @@ title: Deploying Dubbo Applications to a Virtual Machine Environment
type: docs
weight: 3
---
-This model maps Dubbo Service to the concept of <a target="_blank" href="">Kubernetes Service</a>, eliminating the need for traditional registries like Nacos, with the Kubernetes APISERVER taking on the role of the registry.
+This model maps Dubbo Service to the concept of `Kubernetes Service`, eliminating the need for traditional registries like Nacos, with the Kubernetes APISERVER taking on the role of the registry.
<img src="/imgs/v3/manual/java/tutorial/kubernetes/kubernetes-service.png" style="max-width:650px;height:auto;" />
@@ -47,7 +47,7 @@ Configure pre-stop
Through Dubbo3's SPI mechanism, multiple "probes" are internally implemented based on Dubbo3 QOS operations module's HTTP services, enabling container probes to obtain corresponding probe states within the application. Moreover, the SPI implementation mechanism also facilitates users to extend internal "probes," making the entire application lifecycle more effectively governed.
-**Three Probes Corresponding SPI Interfaces**
+Three Probes Corresponding SPI Interfaces
- livenessProbe: `org.apache.dubbo.qos.probe.LivenessProbe`
- readinessProbe: `org.apache.dubbo.qos.probe.ReadinessProbe`
diff --git a/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-kubernetes.md b/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-kubernetes.md
index c726f004e29..5a8e145e617 100644
--- a/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-kubernetes.md
+++ b/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-kubernetes.md
@@ -26,7 +26,7 @@ $ dubboctl install --profile=demo
{{% /alert %}}
## Deploy Application
-We still take the project in [Quick Start]() as an example to demonstrate the specific steps for packaging and deploying the application.
+We still take the project in `Quick Start` as an example to demonstrate the specific steps for packaging and deploying the application.
First, clone the sample project locally:
```shell
@@ -72,7 +72,7 @@ Access `http://xxx` to view the service deployment details.
### Graceful Online/Offline
As shown in the architecture diagram above, we still use Nacos as the registry. Therefore, similar to traditional Linux deployment models, the timing of publishing instances to the registry and removing instances from the registry is key to achieving graceful online/offline:
-1. Online phase, control when instances register to the registry using the [delayed publishing]() mechanism, and ensure traffic is gradually directed to new nodes by enabling [consumer-side warming]().
+1. Online phase, control when instances register to the registry using the `delayed publishing` mechanism, and ensure traffic is gradually directed to new nodes by enabling `consumer-side warming`.
2. Offline phase, configure `prestop` to ensure instance registration information is removed from the registry first, before proceeding to the process destruction phase.
Example configuration for gracefully offline removing instances:
diff --git a/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-vm.md b/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-vm.md
index 306fc8e02f7..1255216dd32 100644
--- a/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-vm.md
+++ b/content/en/overview/mannual/java-sdk/tasks/deploy/deploy-on-vm.md
@@ -14,10 +14,10 @@ The following diagram illustrates a typical Dubbo microservice deployment archit
<img src="/imgs/v3/manual/java/tutorial/kubernetes/kubernetes.png" style="max-width:650px;height:auto;" />
## Install Nacos
-Please refer to the following documentation for how to [install Nacos]() locally.
+Please refer to the following documentation for how to `install Nacos` locally.
## Deploy Application
-We will continue to use the project in [Quick Start]() as an example to demonstrate the detailed steps for application packaging and deployment.
+We will continue to use the project in `Quick Start` as an example to demonstrate the detailed steps for application packaging and deployment.
Clone the sample project locally:
```shell
@@ -107,7 +107,7 @@ Visit `http://xxx` to view service deployment details.
### Graceful Online and Offline
In the case of using a traditional registration center, we need to control the timing of when instances are published to the registration center and when instances are removed from the registration center to achieve a graceful online and offline:
-1. In the online phase, control the timing of instance registration to the registration center through the [delayed release]() mechanism and ensure that traffic is gradually forwarded to the new nodes through enabling [consumer preheating]().
+1. In the online phase, control the timing of instance registration to the registration center through the `delayed release` mechanism and ensure that traffic is gradually forwarded to the new nodes through enabling `consumer preheating`.
2. In the offline phase, configure `prestop` to ensure that instance registration information is first removed from the registration center, and then enter the process of destruction.
Before going offline, it is recommended to call the following http port to remove the instance from the registration center first, then attempt to stop the process.
diff --git a/content/en/overview/mannual/java-sdk/tasks/develop/api.md b/content/en/overview/mannual/java-sdk/tasks/develop/api.md
index 63bb8ae9876..f7eaab71ae7 100644
--- a/content/en/overview/mannual/java-sdk/tasks/develop/api.md
+++ b/content/en/overview/mannual/java-sdk/tasks/develop/api.md
@@ -27,7 +27,7 @@ The above is a code example of starting a Dubbo RPC Server. The `DubboBootstrap`
The official recommendation is to use `DubboBootstrap.start()` as the centralized entry for application startup, but to facilitate the separate publication of some services after the process starts, the Dubbo framework also allows directly calling `ServiceConfig.export()` or `ReferenceConfig.refer()` methods to publish individual services. In this case, Service/Reference will register with the default DubboBootstrap instance, similar to calling `DubboBootstrap.service(...).start()`.
-Below are some components commonly used in development. For a complete component definition and detailed parameter description, please refer to the [Reference Manual - Configuration Items Manual](/en/overview/mannual/java-sdk/reference-manual/config/properties/#Configuration%20Manual):
+Below are some components commonly used in development. For a complete component definition and detailed parameter description, please refer to the [Reference Manual - Configuration Items Manual](/en/overview/mannual/java-sdk/reference-manual/config/properties):
| API Component | Globally Unique | Core Methods or Properties | Description |
| --- | --- | --- | --- |
diff --git a/content/en/overview/mannual/java-sdk/tasks/develop/springboot.md b/content/en/overview/mannual/java-sdk/tasks/develop/springboot.md
index 453f46bba7c..983d6bb157c 100644
--- a/content/en/overview/mannual/java-sdk/tasks/develop/springboot.md
+++ b/content/en/overview/mannual/java-sdk/tasks/develop/springboot.md
@@ -182,7 +182,7 @@ public class ProviderConfiguration {
```
#### Supplementing Configuration Through dubbo.properties
-For scenarios using `DubboService` or `DubboReference`, additional configuration can be provided by adding a dubbo.properties file under the project's resources directory. [Specific format](../principle/) has more detailed explanations here.
+For scenarios using `DubboService` or `DubboReference`, additional configuration can be provided by adding a dubbo.properties file under the project's resources directory. [Specific format](/en/overview/mannual/java-sdk/reference-manual/config/principle) has more detailed explanations here.
```properties
dubbo.service.org.apache.dubbo.springboot.demo.DemoService.timeout=5000
diff --git a/content/en/overview/mannual/java-sdk/tasks/framework/fault-tolerent-strategy.md b/content/en/overview/mannual/java-sdk/tasks/framework/fault-tolerent-strategy.md
index 84396973142..7b447598ed0 100644
--- a/content/en/overview/mannual/java-sdk/tasks/framework/fault-tolerent-strategy.md
+++ b/content/en/overview/mannual/java-sdk/tasks/framework/fault-tolerent-strategy.md
@@ -1,6 +1,6 @@
---
aliases:
- - /en/docsv2.7/user/examples/fault-tolerent-strategy/
+ - /zh-cn/docsv2.7/user/examples/fault-tolerent-strategy/
- /en/overview/mannual/java-sdk/advanced-features-and-usage/service/fault-tolerent-strategy/
description: Fault tolerance solutions provided by Dubbo when cluster calls fail
linkTitle: Cluster Fault Tolerance (Retry)
@@ -24,7 +24,7 @@ Node relationships:
## Cluster Fault Tolerance Modes
-You can extend the cluster fault tolerance strategy. See: [Cluster Extension](../../../dev/impls/cluster)
+You can extend the cluster fault tolerance strategy. See: [Cluster Extension](/en/overview/mannual/java-sdk/reference-manual/spi/description/cluster)
### Failover Cluster
diff --git a/content/en/overview/mannual/java-sdk/tasks/framework/filter.md b/content/en/overview/mannual/java-sdk/tasks/framework/filter.md
index 4c5c55f9577..d1e886cbd93 100644
--- a/content/en/overview/mannual/java-sdk/tasks/framework/filter.md
+++ b/content/en/overview/mannual/java-sdk/tasks/framework/filter.md
@@ -34,7 +34,7 @@ As shown in the figure above, the Dubbo proxy automatically loads Filter impleme
public interface Filter extends BaseFilter {}
```
-The default activation status of a Filter can be set in the definition using the `@Activate` annotation, as shown in the following definition, which indicates that this Filter is automatically enabled when executing RPC requests on the provider side (not enabled on the consumer side). The `@Activate` annotation supports various conditional controls, including enabling it when a specific class is present in the classpath, or when certain parameter values are present in the URL, more detai [...]
+The default activation status of a Filter can be set in the definition using the `@Activate` annotation, as shown in the following definition, which indicates that this Filter is automatically enabled when executing RPC requests on the provider side (not enabled on the consumer side). The `@Activate` annotation supports various conditional controls, including enabling it when a specific class is present in the classpath, or when certain parameter values are present in the URL, more detai [...]
```java
@Activate(group = PROVIDER)
@@ -129,5 +129,5 @@ public interface ClusterFilter extends BaseFilter {}
### Extend Filter
-Refer to [Usage Tutorial - Custom Extensions]() for specific examples.
+Refer to `Usage Tutorial - Custom Extensions` for specific examples.
diff --git a/content/en/overview/mannual/java-sdk/tasks/framework/lightweight-rpc.md b/content/en/overview/mannual/java-sdk/tasks/framework/lightweight-rpc.md
index 0d94f75a79b..4e9b87ac438 100644
--- a/content/en/overview/mannual/java-sdk/tasks/framework/lightweight-rpc.md
+++ b/content/en/overview/mannual/java-sdk/tasks/framework/lightweight-rpc.md
@@ -104,7 +104,7 @@ Congratulations! You have now learned the basic usage of Dubbo Java RPC communic
## More Content
-- The Triple protocol is fully compatible with gRPC; you can refer here to learn how to [write gRPC-compatible services using IDL](/en/overview/mannual/java-sdk/quick-start/), or [use other communication protocols]()
-- As an RPC framework, Dubbo supports asynchronous calls, connection management, context, etc. Please refer to [RPC framework core features]()
-- You can continue to [add more microservice governance capabilities to your application using API]() but we encourage you to use [Dubbo Spring Boot to develop microservice applications](../../microservice/develop/)
+- The Triple protocol is fully compatible with gRPC; you can refer here to learn how to [write gRPC-compatible services using IDL](/en/overview/mannual/java-sdk/quick-start/), or `use other communication protocols`
+- As an RPC framework, Dubbo supports asynchronous calls, connection management, context, etc. Please refer to `RPC framework core features`
+- You can continue to `add more microservice governance capabilities to your application using API` but we encourage you to use [Dubbo Spring Boot to develop microservice applications](/en/overview/mannual/java-sdk/reference-manual/architecture/multi-instance/develop)
diff --git a/content/en/overview/mannual/java-sdk/tasks/framework/more/concurrency-control.md b/content/en/overview/mannual/java-sdk/tasks/framework/more/concurrency-control.md
index fd7e42879fa..cccc097a1c3 100644
--- a/content/en/overview/mannual/java-sdk/tasks/framework/more/concurrency-control.md
+++ b/content/en/overview/mannual/java-sdk/tasks/framework/more/concurrency-control.md
@@ -23,7 +23,7 @@ Allow for smoother scaling of services when demand increases.
Ensure services remain reliable and stable during peak usage times.
-This method requires users to accurately evaluate in advance the concurrency level the system can handle, and accurately assessing system capacity is not an easy task. Therefore, Dubbo also provides an adaptive flow control mode that automatically identifies system health based on system load and implements flow control protection. You can [view the documentation here](../adaptive-concurrency-control).
+This method requires users to accurately evaluate in advance the concurrency level the system can handle, and accurately assessing system capacity is not an easy task. Therefore, Dubbo also provides an adaptive flow control mode that automatically identifies system health based on system load and implements flow control protection. You can [view the documentation here](/en/overview/mannual/java-sdk/tasks/rate-limit/adaptive-concurrency-control).
## Usage
### Example 1
diff --git a/content/en/overview/mannual/java-sdk/tasks/framework/more/config-connections.md b/content/en/overview/mannual/java-sdk/tasks/framework/more/config-connections.md
index cc5a61c1dc9..c326867c5ef 100644
--- a/content/en/overview/mannual/java-sdk/tasks/framework/more/config-connections.md
+++ b/content/en/overview/mannual/java-sdk/tasks/framework/more/config-connections.md
@@ -71,7 +71,7 @@ Consumers can send requests to the provider before the provider is ready to rece
## Use Cases
Sticky connections are used for stateful services, allowing clients to always invoke the same provider unless that provider is down.
-Sticky connections will automatically enable [lazy connect](../lazy-connect) to reduce the number of long connections.
+Sticky connections will automatically enable `lazy connect` to reduce the number of long connections.
## Usage
```xml
diff --git a/content/en/overview/mannual/java-sdk/tasks/framework/more/parameter-validation.md b/content/en/overview/mannual/java-sdk/tasks/framework/more/parameter-validation.md
index 59112982cc6..d0c8d4c2201 100644
--- a/content/en/overview/mannual/java-sdk/tasks/framework/more/parameter-validation.md
+++ b/content/en/overview/mannual/java-sdk/tasks/framework/more/parameter-validation.md
@@ -197,5 +197,6 @@ public class ValidationConsumer {
}
```
-> **Validation methods are extensible. See the developer manual for [validation extensions](/en/overview/manual/java-sdk/reference-manual/spi/description/validation) for more information.**
+> **Validation methods are extensible. See the developer manual for [validation extensions](/en/overview/mannual/java-sdk/reference-manual/spi/description/validation) for more information.**
+
diff --git a/content/en/overview/mannual/java-sdk/tasks/framework/more/router-snapshot.md b/content/en/overview/mannual/java-sdk/tasks/framework/more/router-snapshot.md
index 99b926ddfff..0fbf8002d05 100644
--- a/content/en/overview/mannual/java-sdk/tasks/framework/more/router-snapshot.md
+++ b/content/en/overview/mannual/java-sdk/tasks/framework/more/router-snapshot.md
@@ -86,5 +86,5 @@ dubbo>
```
#### Note:
-For cases where logs are empty due to incompatibility with the logging framework, you can refer to [Log Framework Adaptation and Runtime Management](../../others/logger-management/) to dynamically modify the log output framework.
+For cases where logs are empty due to incompatibility with the logging framework, you can refer to [Log Framework Adaptation and Runtime Management](/en/overview/mannual/java-sdk/reference-manual/qos/introduction/logger-management) to dynamically modify the log output framework.
diff --git a/content/en/overview/mannual/java-sdk/tasks/framework/version_group.md b/content/en/overview/mannual/java-sdk/tasks/framework/version_group.md
index 54d9fc6e180..9d0a00433be 100644
--- a/content/en/overview/mannual/java-sdk/tasks/framework/version_group.md
+++ b/content/en/overview/mannual/java-sdk/tasks/framework/version_group.md
@@ -128,7 +128,7 @@ After starting the Dubbo service, the same service name with different groups ca
#### Service Consumer Side (XML Configuration)
-Using the <dubbo:reference/> annotation, add the group parameter
+Using the `dubbo:reference`annotation, add the group parameter
```xml
<?xml version="1.0" encoding="UTF-8"?>
diff --git a/content/en/overview/mannual/java-sdk/tasks/gateway/architecture.md b/content/en/overview/mannual/java-sdk/tasks/gateway/architecture.md
index cbe6bfd93d7..d1a7c3ed11d 100644
--- a/content/en/overview/mannual/java-sdk/tasks/gateway/architecture.md
+++ b/content/en/overview/mannual/java-sdk/tasks/gateway/architecture.md
@@ -22,7 +22,7 @@ BFF applications can typically be developed using common frameworks such as Spri
{{% alert title="Note" color="info" %}}
Both `dubbo` and `triple` protocols support this access architecture. Additionally, when configuring BFF applications to call Dubbo services, you can use the regular Dubbo configuration method or use generalized calls:
-* The advantage of using [generalized calls]() for accessing Dubbo protocol is that it avoids dependency on the service binary package and achieves dynamic configuration effects.
+* The advantage of using `generalized calls` for accessing Dubbo protocol is that it avoids dependency on the service binary package and achieves dynamic configuration effects.
* When configuring access to the triple protocol, you can use HTTP calling methods to similarly avoid dependency on the service binary package for dynamic configuration effects.
{{% /alert %}}
diff --git a/content/en/overview/mannual/java-sdk/tasks/gateway/triple.md b/content/en/overview/mannual/java-sdk/tasks/gateway/triple.md
index caf5d65cef3..90dabdd4b6d 100644
--- a/content/en/overview/mannual/java-sdk/tasks/gateway/triple.md
+++ b/content/en/overview/mannual/java-sdk/tasks/gateway/triple.md
@@ -250,6 +250,6 @@ The content described in this article applies only to the versions of the triple
{{% /alert %}}
## Reference Links
-* [Use Apache APISIX to Proxy Triple Protocol Traffic](/en/blog/2024/04/22/using-apache-apisix-to-proxy-dubbo-service-triple-protocol/)
+* `Use Apache APISIX to Proxy Triple Protocol Traffic`
* [Higress Achieves Microservice Discovery and Routing Configuration Based on HTTP Protocol](https://higress.io/en/docs/user/spring-cloud)
diff --git a/content/en/overview/mannual/java-sdk/tasks/mesh/migration/proxyless.md b/content/en/overview/mannual/java-sdk/tasks/mesh/migration/proxyless.md
index 070204633c2..d0e165f437e 100644
--- a/content/en/overview/mannual/java-sdk/tasks/mesh/migration/proxyless.md
+++ b/content/en/overview/mannual/java-sdk/tasks/mesh/migration/proxyless.md
@@ -65,7 +65,7 @@ The server configuration registers the Istio address as the registration center,
We recommend setting the `protocol` to tri (fully compatible with grpc) for a better experience within the Istio environment.
-To allow Kubernetes to be aware of the application's status, the `qosAcceptForeignIp` parameter needs to be configured for Kubernetes to obtain the correct application status, [aligning the lifecycle](/en/overview/mannual/java-sdk/advanced-features-and-usage/others/dubbo-kubernetes-probe/).
+To allow Kubernetes to be aware of the application's status, the `qosAcceptForeignIp` parameter needs to be configured for Kubernetes to obtain the correct application status, `aligning the lifecycle`.
```properties
dubbo.application.name=dubbo-samples-xds-provider
diff --git a/content/en/overview/mannual/java-sdk/tasks/observability/console.md b/content/en/overview/mannual/java-sdk/tasks/observability/console.md
index c269e2bb719..18da0a34c3c 100755
--- a/content/en/overview/mannual/java-sdk/tasks/observability/console.md
+++ b/content/en/overview/mannual/java-sdk/tasks/observability/console.md
@@ -9,7 +9,7 @@ type: docs
weight: 1
---
-The most direct way to manage Dubbo is through the visual interface provided by the Dubbo control plane (dubbo-control-plane). In the previous article on [Quick Start - Deploying Dubbo Applications]() we also used it to check the status after the service was started.
+The most direct way to manage Dubbo is through the visual interface provided by the Dubbo control plane (dubbo-control-plane). In the previous article on `Quick Start - Deploying Dubbo Applications` we also used it to check the status after the service was started.
**`dubbo-control-plane` supports visual displays, monitoring cluster status, and real-time delivery of traffic control rules.**
@@ -28,7 +28,6 @@ To experience the effects, we first need to install dubbo-control-plane. Here ar
```
Note that the `conf/dubbo.yml` configuration needs to be adjusted according to your needs to point to the registry and other backend services you want to connect to. For specifics, please refer to the backend services dependent on the dubbo-control-plane architecture.
3. Access `http://xxx` to open the console page.
- ![Page Screenshot]()
{{% alert title="Note" color="info" %}}
* Please refer to the documentation for detailed installation steps of dubbo-control-plane, including installation methods and configuration guidance for multiple platforms.
diff --git a/content/en/overview/mannual/java-sdk/tasks/observability/grafana.md b/content/en/overview/mannual/java-sdk/tasks/observability/grafana.md
index 81e027c622e..d35d35b340d 100644
--- a/content/en/overview/mannual/java-sdk/tasks/observability/grafana.md
+++ b/content/en/overview/mannual/java-sdk/tasks/observability/grafana.md
@@ -51,7 +51,7 @@ kubectl -n dubbo-demo get deployments
## View Grafana Visualization Panel
After the sample program starts, it will automatically simulate service calls; just wait a bit to see metrics visualized in Grafana.
-1. If Grafana was installed via the [Dubbo Admin Panel](../../../reference/admin/architecture/), access the Admin console and find the Grafana monitoring entry in the left menu.
+1. If Grafana was installed via the [Dubbo Admin Panel](/en/overview/mannual/control-plane/architecture), access the Admin console and find the Grafana monitoring entry in the left menu.
2. If Grafana is a standalone installation, access the Grafana console directly:
diff --git a/content/en/overview/mannual/java-sdk/tasks/protocols/triple/idl.md b/content/en/overview/mannual/java-sdk/tasks/protocols/triple/idl.md
index 1471bac8a95..797af9d39a9 100644
--- a/content/en/overview/mannual/java-sdk/tasks/protocols/triple/idl.md
+++ b/content/en/overview/mannual/java-sdk/tasks/protocols/triple/idl.md
@@ -131,7 +131,7 @@ Additionally, to support direct access to `application/json` format requests, th
</dependency>
```
-### Generated Code Cannot Compile
+### Generated Code Cannot Compile {#generated-code-cannot-be-compiled}
When using Protobuf, ensure that the core Dubbo library version matches the protoc plugin version and run `mvn clean compile` to regenerate the code.
**Before version 3.3.0**
diff --git a/content/en/overview/mannual/java-sdk/tasks/security/tls.md b/content/en/overview/mannual/java-sdk/tasks/security/tls.md
index 658bf14722b..ce75f3af7ea 100644
--- a/content/en/overview/mannual/java-sdk/tasks/security/tls.md
+++ b/content/en/overview/mannual/java-sdk/tasks/security/tls.md
@@ -57,7 +57,7 @@ if (!mutualTls) {}
}
```
-To ensure flexibility in application startup, the TLS Cert specification can also be dynamically set during startup based on the deployment environment using -D parameters or environment variables. Refer to Dubbo's [configuration reading rules](/en/docs/advanced/config-rule).
+To ensure flexibility in application startup, the TLS Cert specification can also be dynamically set during startup based on the deployment environment using -D parameters or environment variables. Refer to Dubbo's `configuration reading rules`.
> Regarding the security of service calls, Dubbo will continue to invest in this area in future versions, with authentication mechanisms for service discovery/calls expected to be available in upcoming releases.
diff --git a/content/en/overview/mannual/java-sdk/tasks/service-discovery/kubernetes.md b/content/en/overview/mannual/java-sdk/tasks/service-discovery/kubernetes.md
index 82c8084e840..cbb82d3d06d 100644
--- a/content/en/overview/mannual/java-sdk/tasks/service-discovery/kubernetes.md
+++ b/content/en/overview/mannual/java-sdk/tasks/service-discovery/kubernetes.md
@@ -17,5 +17,5 @@ In the previous two sections, we discussed two registration center patterns: Nac
In this mode, service discovery aligns with the user's deployment and operation tasks. Users define standard Kubernetes Services and Deployments, deploying them to Kubernetes. The Control Plane then monitors the APISERVER resources and interacts with the SDK processes to form a complete service discovery system.
-For specific practical cases of using Kubernetes as a registry, please refer to the section on [Kubernetes Service Deployment]() for more details.
+For specific practical cases of using Kubernetes as a registry, please refer to the section on `Kubernetes Service Deployment` for more details.
diff --git a/content/en/overview/mannual/java-sdk/tasks/service-discovery/zookeeper.md b/content/en/overview/mannual/java-sdk/tasks/service-discovery/zookeeper.md
index 6338ec275a4..c2ef3e3cddd 100644
--- a/content/en/overview/mannual/java-sdk/tasks/service-discovery/zookeeper.md
+++ b/content/en/overview/mannual/java-sdk/tasks/service-discovery/zookeeper.md
@@ -166,7 +166,7 @@ dubbo
session: 60 * 1000 * # Session timeout, default 60s
```
-The Zookeeper registry center also supports other control parameters, see the [Registry Configuration Handbook](../../config/properties#registry)
+The Zookeeper registry center also supports other control parameters, see the [Registry Configuration Handbook](/en/overview/mannual/java-sdk/reference-manual/config/properties#dubbo.registry)
## 3 Working Principle
In the previous section, we explained the difference between application-level service discovery and interface-level service discovery. In the Zookeeper implementation, their storage structures also differ significantly. Overall, the Zookeeper registry center implementation supports the following high availability capabilities:
diff --git a/content/en/overview/mannual/java-sdk/tasks/traffic-management/accesslog.md b/content/en/overview/mannual/java-sdk/tasks/traffic-management/accesslog.md
index 04a4f47df49..90905a8b7ff 100644
--- a/content/en/overview/mannual/java-sdk/tasks/traffic-management/accesslog.md
+++ b/content/en/overview/mannual/java-sdk/tasks/traffic-management/accesslog.md
@@ -13,8 +13,8 @@ weight: 3
The access log can effectively record all service request information processed by a machine over a period of time, including request reception time, remote IP, request parameters, response results, etc. Dynamically enabling the access log at runtime is very helpful for problem troubleshooting.
## Before You Start
-* [Deploy the Shop Mall Project](../#Deploy-Mall-System)
-* Deploy and open [Dubbo Admin](../.././../reference/admin/architecture/)
+* `Deploy the Shop Mall Project`
+* Deploy and open [Dubbo Admin](/en/overview/mannual/control-plane/architecture)
## Task Details
diff --git a/content/en/overview/mannual/java-sdk/tasks/traffic-management/arguments.md b/content/en/overview/mannual/java-sdk/tasks/traffic-management/arguments.md
index ab652327c6c..f44c3a8b973 100644
--- a/content/en/overview/mannual/java-sdk/tasks/traffic-management/arguments.md
+++ b/content/en/overview/mannual/java-sdk/tasks/traffic-management/arguments.md
@@ -17,8 +17,8 @@ Alternatively, some products offer differentiated paid services that require rou
## Before You Begin
-* [Deploy Shop Mall Project](../#Deploy-Mall-System)
-* Deploy and open [Dubbo Admin](../.././../reference/admin/architecture/)
+* `Deploy Shop Mall Project`
+* Deploy and open [Dubbo Admin](/en/overview/mannual/control-plane/architecture)
## Task Details
diff --git a/content/en/overview/mannual/java-sdk/tasks/traffic-management/host.md b/content/en/overview/mannual/java-sdk/tasks/traffic-management/host.md
index e957fafa510..337d026b3aa 100644
--- a/content/en/overview/mannual/java-sdk/tasks/traffic-management/host.md
+++ b/content/en/overview/mannual/java-sdk/tasks/traffic-management/host.md
@@ -15,8 +15,8 @@ Automatic address discovery and load balancing mechanisms have many advantages;
## Before You Begin
-* [Deploy the Shop Mall Project](../#deploy-the-shop-mall-project)
-* Deploy and open [Dubbo Admin](../.././../reference/admin/architecture/)
+* `Deploy the Shop Mall Project`
+* Deploy and open [Dubbo Admin](/en/overview/mannual/control-plane/architecture)
## Task Details
diff --git a/content/en/overview/mannual/java-sdk/tasks/traffic-management/isolation.md b/content/en/overview/mannual/java-sdk/tasks/traffic-management/isolation.md
index 5517f75d9c2..88cc5c71aa7 100644
--- a/content/en/overview/mannual/java-sdk/tasks/traffic-management/isolation.md
+++ b/content/en/overview/mannual/java-sdk/tasks/traffic-management/isolation.md
@@ -22,7 +22,7 @@ Using Dubbo's tag routing capability allows for very flexible traffic isolation.
## Before You Begin
* Deploy Shop Mall Project
-* Deploy and open [Dubbo Admin](../.././../reference/admin/architecture/)
+* Deploy and open [Dubbo Admin](/en/overview/mannual/control-plane/architecture)
## Task Details
diff --git a/content/en/overview/mannual/java-sdk/tasks/traffic-management/mock.md b/content/en/overview/mannual/java-sdk/tasks/traffic-management/mock.md
index a7a07830936..32ad83b9f60 100644
--- a/content/en/overview/mannual/java-sdk/tasks/traffic-management/mock.md
+++ b/content/en/overview/mannual/java-sdk/tasks/traffic-management/mock.md
@@ -17,8 +17,8 @@ The core objective of service downgrading is to address these weak dependencies.
## Before You Start
-* [Deploy Shop Mall Project](../#deploy-the-mall-system)
-* Deploy and open [Dubbo Admin](../.././../reference/admin/architecture/)
+* `Deploy Shop Mall Project`
+* Deploy and open [Dubbo Admin](/en/overview/mannual/control-plane/architecture)
## Task Details
@@ -67,7 +67,7 @@ To avoid affecting other tasks, delete or disable the downgrade rules just confi
## Other Matters
-The service downgrading feature can also be utilized in development and testing environments. Due to the distributed characteristics of microservices, there are interdependencies among different services or applications. Thus, it is challenging for a service or application to be deployed independently without relying on other services. However, not all services in the testing environment are always ready, presenting a significant obstacle to the independent evolution of services emphasiz [...]
+The service downgrading feature can also be utilized in development and testing environments. Due to the distributed characteristics of microservices, there are interdependencies among different services or applications. Thus, it is challenging for a service or application to be deployed independently without relying on other services. However, not all services in the testing environment are always ready, presenting a significant obstacle to the independent evolution of services emphasiz [...]
Dubbo's downgrade rules are used to set behaviors and return values upon downgrading. However, the judgment of when to execute flow limiting downgrade actions has not been extensively covered. Dubbo has completed this by integrating more specialized flow limiting downgrade products such as Sentinel, which can be used in conjunction with Dubbo downgrade rules, as detailed in the [flow limiting downgrade](/en/overview/core-features/traffic/circuit-breaking/) documentation.
diff --git a/content/en/overview/mannual/java-sdk/tasks/traffic-management/region.md b/content/en/overview/mannual/java-sdk/tasks/traffic-management/region.md
index c2e26bdbad4..77a7199679b 100644
--- a/content/en/overview/mannual/java-sdk/tasks/traffic-management/region.md
+++ b/content/en/overview/mannual/java-sdk/tasks/traffic-management/region.md
@@ -17,8 +17,8 @@ When applications are deployed across multiple different data centers/regions, c
## Before You Begin
-* [Deploy the Shop Marketplace Project](../#Deploy-the-Market-System)
-* Deploy and open [Dubbo Admin](../.././../reference/admin/architecture/)
+* `Deploy the Shop Marketplace Project`
+* Deploy and open [Dubbo Admin](/en/overview/mannual/control-plane/architecture)
## Task Details
diff --git a/content/en/overview/mannual/java-sdk/tasks/traffic-management/retry.md b/content/en/overview/mannual/java-sdk/tasks/traffic-management/retry.md
index 8ee43e5b44d..4590983cd8f 100644
--- a/content/en/overview/mannual/java-sdk/tasks/traffic-management/retry.md
+++ b/content/en/overview/mannual/java-sdk/tasks/traffic-management/retry.md
@@ -14,8 +14,8 @@ weight: 2
Retrying after an initial service call failure can effectively increase the overall call success rate. However, it is important to note that retries may lead to increased response times and higher system load. Additionally, retries are generally suitable for read-only services or write services that guarantee idempotency.
## Before You Begin
-* [Deploy the Shop Mall Project](../#deploy-the-mall-system)
-* Deploy and open [Dubbo Admin](../.././../reference/admin/architecture/)
+* `Deploy the Shop Mall Project`
+* Deploy and open [Dubbo Admin](/en/overview/mannual/control-plane/architecture)
## Task Details
diff --git a/content/en/overview/mannual/java-sdk/tasks/traffic-management/route.md b/content/en/overview/mannual/java-sdk/tasks/traffic-management/route.md
index 721e5cfcf3f..4ffcb8eed68 100644
--- a/content/en/overview/mannual/java-sdk/tasks/traffic-management/route.md
+++ b/content/en/overview/mannual/java-sdk/tasks/traffic-management/route.md
@@ -24,18 +24,18 @@ The requirements are very straightforward.
- Forward traffic matching this condition to this batch of machines
- Forward traffic matching another condition to another batch of machines
-![Draw a diagram of traffic matching and forwarding]()
+!`Draw a diagram of traffic matching and forwarding`
This is implemented in Dubbo through conditional routing, and its detailed working principle is explained in our introduction. In the above example, xxx represents; yyy represents.
We need to deploy the rules to the running Dubbo SDK. In the Dubbo system, this is done as follows.
-![Routing Rule Distribution and Effect Principle Diagram]()
+!`Routing Rule Distribution and Effect Principle Diagram`
A zk/nacos distributes a rule, and the Dubbo instance receives the rule push. During the RPC call, rules are applied to filter, selecting a subset of addresses to call.
{{% alert title="Note" color="info" %}}
-In the traditional Nacos/Zookeeper microservice deployment scheme, the routing rule configuration center stores and forwards to the Dubbo SDK. However, in Kubernetes Service or service mesh scenarios, the storage and push mechanisms for routing rules may change. For specifics, please refer to [Kubernetes Best Practices]().
+In the traditional Nacos/Zookeeper microservice deployment scheme, the routing rule configuration center stores and forwards to the Dubbo SDK. However, in Kubernetes Service or service mesh scenarios, the storage and push mechanisms for routing rules may change. For specifics, please refer to `Kubernetes Best Practices`.
{{% /alert %}}
At this point, if we send a request to the xxx service,
@@ -43,7 +43,7 @@ At this point, if we send a request to the xxx service,
There is one very important point.
## More Content
-- Routing rules not taking effect? [Dubbo Routing Rule Troubleshooting Methods]()
-- Current routing rules not flexible enough to achieve the desired effect? Check out [Script Routing]()
-- You can also customize your traffic strategy by [Extending Dubbo's Routing Implementation]()
+- Routing rules not taking effect? `Dubbo Routing Rule Troubleshooting Methods`
+- Current routing rules not flexible enough to achieve the desired effect? Check out `Script Routing`
+- You can also customize your traffic strategy by `Extending Dubbo's Routing Implementation`
diff --git a/content/en/overview/mannual/java-sdk/tasks/traffic-management/timeout.md b/content/en/overview/mannual/java-sdk/tasks/traffic-management/timeout.md
index f388b7d48f6..f5723c5ee9d 100644
--- a/content/en/overview/mannual/java-sdk/tasks/traffic-management/timeout.md
+++ b/content/en/overview/mannual/java-sdk/tasks/traffic-management/timeout.md
@@ -13,7 +13,7 @@ Dubbo provides the ability to dynamically adjust service timeout, allowing adjus
## Before You Start
* Deploy the Shop mall project
-* Deploy and open [Dubbo Admin](../.././../reference/admin/architecture/)
+* Deploy and open [Dubbo Admin](/en/overview/mannual/control-plane/architecture)
## Task Details
diff --git a/content/en/overview/mannual/java-sdk/tasks/traffic-management/weight.md b/content/en/overview/mannual/java-sdk/tasks/traffic-management/weight.md
index 46921d3d696..34a4d04bcab 100644
--- a/content/en/overview/mannual/java-sdk/tasks/traffic-management/weight.md
+++ b/content/en/overview/mannual/java-sdk/tasks/traffic-management/weight.md
@@ -21,7 +21,7 @@ Based on a weight-based traffic scheduling algorithm, dynamically adjusting the
## Before You Begin
* Deploy Shop Mall Project
-* Deploy and open [Dubbo Admin](../.././../reference/admin/architecture/)
+* Deploy and open [Dubbo Admin](/en/overview/mannual/control-plane/architecture)
## Task Details
diff --git a/content/en/overview/mannual/java-sdk/tasks/troubleshoot/no-provider.md b/content/en/overview/mannual/java-sdk/tasks/troubleshoot/no-provider.md
index b6e2b811318..aeb262a3900 100644
--- a/content/en/overview/mannual/java-sdk/tasks/troubleshoot/no-provider.md
+++ b/content/en/overview/mannual/java-sdk/tasks/troubleshoot/no-provider.md
@@ -354,7 +354,7 @@ If you found your published service, but the number of addresses is `0`, please
If found with an incorrect service discovery model, check:
-1. The configured subscription migration rules in files like `dubbo-migration.yaml` or dynamic configurations. Refer to [Application-level Service Discovery Address Migration Rules](/en/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-rule/).
+1. The configured subscription migration rules in files like `dubbo-migration.yaml` or dynamic configurations. Refer to `Application-level Service Discovery Address Migration Rules`.
If you located your published service and the corresponding service discovery model shows more than `0` addresses, proceed to Step 7 for further troubleshooting.
@@ -497,7 +497,7 @@ All blacklisted addresses (typically taken offline voluntarily)
Check whether the corresponding migration model meets your expectations, with the default being `APPLICATION_FIRST`. If the corresponding service discovery model is incorrect, please check the following checklist:
-1. The configured subscription migration rule, in files like `dubbo-migration.yaml` or dynamic settings. Refer to [Application-level Service Discovery Address Migration Rules](/en/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/service-discovery-rule/)
+1. The configured subscription migration rule, in files like `dubbo-migration.yaml` or dynamic settings. Refer to `Application-level Service Discovery Address Migration Rules`
If the migration model is correct, confirm that **all** addresses in the corresponding model match expectations. If not, check the following checklist:
diff --git a/content/en/overview/mannual/java-sdk/tasks/troubleshoot/profiler.md b/content/en/overview/mannual/java-sdk/tasks/troubleshoot/profiler.md
index 027b3877920..e662d2007ca 100644
--- a/content/en/overview/mannual/java-sdk/tasks/troubleshoot/profiler.md
+++ b/content/en/overview/mannual/java-sdk/tasks/troubleshoot/profiler.md
@@ -184,6 +184,6 @@ Start time: 285965612316294
+-[ Offset: 1.558545ms; Usage: 804.276436ms, 99% ] Receive request. Server biz impl invoke begin., dubbo version: 3.0.10-SNAPSHOT, current host: xx.xx.xx.xx
```
{{% alert title="Note" color="warning" %}}
-For empty logs caused by log framework mismatches, refer to [Log Framework Adaptation and Runtime Management](../../others/logger-management/) for dynamically modifying the log output framework.
+For empty logs caused by log framework mismatches, refer to [Log Framework Adaptation and Runtime Management](/en/overview/mannual/java-sdk/reference-manual/qos/introduction/logger-management) for dynamically modifying the log output framework.
{{% /alert %}}
diff --git a/content/en/overview/mannual/web-sdk/quick-start.md b/content/en/overview/mannual/web-sdk/quick-start.md
index ddf4bfd54bf..ccdd1625982 100644
--- a/content/en/overview/mannual/web-sdk/quick-start.md
+++ b/content/en/overview/mannual/web-sdk/quick-start.md
@@ -13,13 +13,13 @@ Based on the Triple protocol defined by Dubbo3, you can easily write browser and
Dubbo-js released its first alpha version supporting the Dubbo3 protocol in September, which can fundamentally change the architecture and communication patterns of microservices' front and back end, allowing you to directly access backend Dubbo RPC services from a browser page or web server.
-
+[//]: # ()
# Browser Web Application Example
This example demonstrates how to use dubbo-js to develop a web application running in a browser, where the web page will call backend services developed in dubbo node.js to generate page content. This example shows both IDL and non-IDL coding modes.
-
+[//]: # ()
## IDL Mode
diff --git a/content/en/overview/notices/serialization.md b/content/en/overview/notices/serialization.md
index e545c9c16a6..9567aae3bb5 100644
--- a/content/en/overview/notices/serialization.md
+++ b/content/en/overview/notices/serialization.md
@@ -53,3 +53,4 @@ If other serialization protocols must be used, and some security is desired, the
[Reinforcement Reference](/en/overview/mannual/java-sdk/advanced-features-and-usage/security/)
+
diff --git a/content/en/overview/reference/proposals/registry-config-meta.md b/content/en/overview/reference/proposals/registry-config-meta.md
index b0de6f8263c..dd130f4e78d 100644
--- a/content/en/overview/reference/proposals/registry-config-meta.md
+++ b/content/en/overview/reference/proposals/registry-config-meta.md
@@ -82,7 +82,7 @@ Taking the registry center as an example, below is a schematic diagram of a mult
## Physical Deployment Architecture of the Three Centers
-
+[//]: # ()
## Recommended Usage in Different Scenarios
* Configure only the registry, defaulting to serve as the metadata and config-center.
diff --git a/content/en/overview/what/core-features/ecosystem.md b/content/en/overview/what/core-features/ecosystem.md
index 918ab049365..9df541052e5 100644
--- a/content/en/overview/what/core-features/ecosystem.md
+++ b/content/en/overview/what/core-features/ecosystem.md
@@ -21,13 +21,13 @@ The following table shows the support status of ecosystem components based on th
| --- | --- | --- | --- | --- | --- |
| Service Discovery | [Zookeeper](../../mannual/java-sdk/reference-manual/registry/zookeeper) | [Nacos](../../mannual/java-sdk/reference-manual/registry/nacos) | [Kubernetes Service](/) | DNS [In Development] | <a href="https://github.com/apache/dubbo-spi-extensions/tree/master/dubbo-registry-extensions" target="_blank">More</a> |
| Dynamic Configuration | [Zookeeper](../../mannual/java-sdk/reference-manual/config-center/zookeeper) | [Nacos](../../mannual/java-sdk/reference-manual/config-center/nacos) | [Apollo](../../mannual/java-sdk/reference-manual/config-center/apollo) | Kubernetes [In Development] | <a href="https://github.com/apache/dubbo-spi-extensions/tree/master/dubbo-configcenter-extensions" target="_blank">More</a> |
-| Metadata Management | [Zookeeper](../../mannual/java-sdk/reference-manual/metadata-center/zookeeper) | [Nacos](../../mannual/java-sdk/reference-manual/metadata-center/nacos) | [Redis](../../mannual/java-sdk/reference-manual/metadata-center/redis) | Kubernetes [In Development] | <a href="https://github.com/apache/dubbo-spi-extensions/tree/master/dubbo-metadata-report-extensions" target="_blank">More</a> |
+| Metadata Management | [Zookeeper](../../mannual/java-sdk/reference-manual/metadata-center/zookeeper) | [Nacos](../../mannual/java-sdk/reference-manual/metadata-center/nacos) | `Redis` | Kubernetes [In Development] | <a href="https://github.com/apache/dubbo-spi-extensions/tree/master/dubbo-metadata-report-extensions" target="_blank">More</a> |
| RPC Protocol | [HTTP/2 (Triple)](../../reference/protocols/triple) | [TCP](../../reference/protocols/tcp) | [HTTP/REST [Alpha]](../../reference/protocols/http) | [gRPC](../../reference/protocols/triple) | [More](../../reference/protocols/) |
-| Visualization and Observability Platform | [Admin](../../tasks/observability/admin/) | [Grafana](../../tasks/observability/grafana/) | [Prometheus](../../tasks/observability/prometheus/) | - | - |
-| Full Link Tracing | [Zipkin](../../tasks/observability/tracing/zipkin/) | [Skywalking](../../tasks/observability/tracing/skywalking/) | <a href="https://github.com/apache/dubbo-samples/tree/master/4-governance/dubbo-samples-spring-boot3-tracing#2-adding-micrometer-tracing-bridge-to-your-project" target="_blank">OpenTelemetry</a> | - | - |
-| Rate Limiting and Degradation | [Sentinel](../../tasks/rate-limit/sentinel) | [Resilience4j](../../tasks/rate-limit/resilience4j) | [Hystrix](../../tasks/rate-limit/hystrix) | - | - |
-| Distributed Transactions | [Seata](../../tasks/ecosystem/transaction/) | - | - | - | - |
-| Gateway | [Higress]({{< relref "../../../../blog/integration/how-to-proxy-dubbo-in-higress" >}}) | [APISIX](../../tasks/ecosystem/gateway/) | [Shenyu]({{< relref "../../../../blog/integration/how-to-proxy-dubbo-in-apache-shenyu" >}}) | [Envoy](https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/network_filters/dubbo_proxy_filter) | - |
+| Visualization and Observability Platform | `Admin` | [Grafana](/en/overview/mannual/java-sdk/tasks/observability/grafana/) | [Prometheus](/en/overview/mannual/java-sdk/tasks/observability/prometheus/) | - | - |
+| Full Link Tracing | [Zipkin](/en/overview/mannual/java-sdk/tasks/observability/tracing/zipkin/) | [Skywalking](/en/overview/mannual/java-sdk/tasks/observability/tracing/skywalking/) | <a href="https://github.com/apache/dubbo-samples/tree/master/4-governance/dubbo-samples-spring-boot3-tracing#2-adding-micrometer-tracing-bridge-to-your-project" target="_blank">OpenTelemetry</a> | - | - |
+| Rate Limiting and Degradation | [Sentinel](/en/overview/mannual/java-sdk/tasks/rate-limit/sentinel) | `Resilience4j` | `Hystrix`) | - | - |
+| Distributed Transactions | `Seata` | - | - | - | - |
+| Gateway | [Higress]({{< relref "../../../../blog/integration/how-to-proxy-dubbo-in-higress" >}}) | [APISIX](/en/overview/mannual/java-sdk/tasks/gateway) | [Shenyu]({{< relref "../../../../blog/integration/how-to-proxy-dubbo-in-apache-shenyu" >}}) | [Envoy](https://www.envoyproxy.io/docs/envoy/latest/configuration/listeners/network_filters/dubbo_proxy_filter) | - |
| Service Mesh | Istio [In Development] | <a href="https://www.aeraki.net/" target="_blank">Aeraka</a> | OpenSergo [In Development] | Proxyless [Alpha] | More |
## Microservices Ecosystem Example Architecture
diff --git a/content/en/overview/what/core-features/extensibility.md b/content/en/overview/what/core-features/extensibility.md
index 0cc8b434f47..0b221a42950 100644
--- a/content/en/overview/what/core-features/extensibility.md
+++ b/content/en/overview/what/core-features/extensibility.md
@@ -35,8 +35,8 @@ Dubbo's extensibility allows the Dubbo project to be conveniently divided into s
## Microservice Ecosystem Based on Extension Points
Numerous extension points and abstractions are the foundation for Dubbo to interface with many microservice ecosystem components and achieve microservice governance capabilities.
-* [Full-Link Tracing](../../tasks/observability/tracing/)
-* [Data Consistency](../../tasks/ecosystem/transaction/)
+* [Full-Link Tracing](/en/overview/mannual/java-sdk/tasks/observability/tracing/tracing)
+* `Data Consistency`
* [Rate Limiting and Degradation](../../core-features/traffic/circuit-breaking/)
Dubbo's SDK implementations in various languages adopt the "microkernel + plugin" design pattern. Almost all core nodes in the process are defined as extension points. The components released by the official team are also released in the form of extension point implementations. Therefore, Dubbo can treat all official and third-party component extensions equally.
@@ -98,7 +98,7 @@ The registry is the foundation for Dubbo's service discovery capabilities. Dubbo
By supporting Consul and Eureka, Dubbo also achieves address and communication layer interoperability with the Spring Cloud ecosystem, making it easier for users to deploy Dubbo and Spring Cloud simultaneously or migrate from Spring Cloud to Dubbo.
### Config Center
-The configuration center is a key component for users to dynamically control Dubbo's behavior. All rules issued in the [Traffic Management](../../tasks/traffic-management) tasks are first sent to the configuration center for storage. Dubbo instances then listen for changes in the configuration center, receive routing rules, and achieve traffic control behavior.
+The configuration center is a key component for users to dynamically control Dubbo's behavior. All rules issued in the [Traffic Management](/en/overview/mannual/java-sdk/tasks/traffic-management/) tasks are first sent to the configuration center for storage. Dubbo instances then listen for changes in the configuration center, receive routing rules, and achieve traffic control behavior.
Dubbo officially supports configuration centers like Zookeeper, Nacos, Etcd, Redis, and Apollo.
@@ -111,10 +111,10 @@ Dubbo officially supports metadata centers like Zookeeper, Nacos, Etcd, and Redi
The following examples demonstrate how to extend Dubbo to solve practical problems. You can follow the examples to learn.
-* [Custom RPC Protocol](../../tasks/extensibility/protocol/)
-* [Custom Traffic Routing Rules](../../tasks/extensibility/router/)
-* [Custom Registry](../../tasks/extensibility/registry/)
-* [Custom Interceptor](../../tasks/extensibility/filter/)
+* [Custom RPC Protocol](/en/overview/mannual/java-sdk/tasks/extensibility/protocol/)
+* [Custom Traffic Routing Rules](/en/overview/mannual/java-sdk/tasks/extensibility/router/)
+* [Custom Registry](/en/overview/mannual/java-sdk/tasks/extensibility/registry/)
+* [Custom Interceptor](/en/overview/mannual/java-sdk/tasks/extensibility/filter/)
## More Extension Points
This document lists some commonly used extension points in Dubbo, but there are many more extension points available for flexible customization. The extension definitions and configuration methods also vary across different language SDKs. Below are the extension point manuals for Dubbo SDKs.
diff --git a/content/en/overview/what/core-features/load-balance.md b/content/en/overview/what/core-features/load-balance.md
index 675bdbd573b..625c48ebbf5 100644
--- a/content/en/overview/what/core-features/load-balance.md
+++ b/content/en/overview/what/core-features/load-balance.md
@@ -96,7 +96,7 @@ Within the same application, different services can be configured to use differe
For specific configuration methods, refer to the following multi-language implementations:
-* [Java](../../mannual/java-sdk/advanced-features-and-usage/performance/loadbalance/)
+* [Java](../../mannual/java-sdk/tasks/service-discovery/loadbalance)
* [Golang](../../mannual/golang-sdk/)
## Custom Extension
diff --git a/content/en/overview/what/core-features/more.md b/content/en/overview/what/core-features/more.md
index 7a51b512984..8a6e44e0986 100644
--- a/content/en/overview/what/core-features/more.md
+++ b/content/en/overview/what/core-features/more.md
@@ -12,7 +12,7 @@ weight: 11
As a microservices framework closely related to application development and aimed at providing enterprise-level service governance capabilities for microservice clusters, Dubbo also offers many advanced features, covering service invocation behavior control, service diagnosis and tuning, service governance, and more.
There may be slight differences in feature implementation and configuration methods across different language SDKs. For specific feature lists and usage, please refer to the following documents:
-* [Java](../../mannual/java-sdk/advanced-features-and-usage/)
+* [Java](../../mannual/java-sdk/reference-manual/)
* [Golang](../../mannual/golang-sdk/tutorial/)
## Controlling Service Invocation Behavior
diff --git a/content/en/overview/what/core-features/observability.md b/content/en/overview/what/core-features/observability.md
index abdbbc85209..a75af3216c4 100644
--- a/content/en/overview/what/core-features/observability.md
+++ b/content/en/overview/what/core-features/observability.md
@@ -30,7 +30,7 @@ The Admin console visually displays applications, services, instances, and depen
-* [Admin Deployment and Effect Demonstration](../../tasks/observability/admin/)
+* `Admin Deployment and Effect Demonstration`
## Metrics
Dubbo runtime collects core service metrics including qps, rt, total calls, successful calls, failed calls, and failure reasons statistics. To better monitor the service running status, Dubbo also provides monitoring of core component statuses such as thread pool count and service health status.
@@ -39,8 +39,8 @@ Metrics can be visualized through Grafana.
-* [Visualize Metrics with Grafana](../../tasks/observability/grafana/)
-* [How to Query Specific Metrics from Prometheus](../../tasks/observability/prometheus/)
+* [Visualize Metrics with Grafana](/en/overview/mannual/java-sdk/tasks/observability/grafana/)
+* [How to Query Specific Metrics from Prometheus](/en/overview/mannual/java-sdk/tasks/observability/prometheus/)
## Tracing
Full link tracing is of great value for monitoring the running status of distributed systems. Dubbo implements runtime request tracking through Filter interceptors. By exporting tracking data to some mainstream implementations such as Zipkin, Skywalking, Jaeger, etc., full link tracking data analysis and visualization can be achieved.
@@ -49,12 +49,12 @@ Full link tracing is of great value for monitoring the running status of distrib
> In the future, we plan to support dynamically adjusting Dubbo's link tracing sampling rate through governance platforms such as Dubbo Admin.
-* [Implement Full Link Tracing with Skywalking](../../tasks/observability/tracing/skywalking/)
-* [Implement Full Link Tracing with Zipkin](../../tasks/observability/tracing/zipkin/)
-* [Associate Logs with Link Tracing](../../mannual/java-sdk/advanced-features-and-usage/observability/tracing/)
+* [Implement Full Link Tracing with Skywalking](/en/overview/mannual/java-sdk/tasks/observability/tracing/skywalking/)
+* [Implement Full Link Tracing with Zipkin](/en/overview/mannual/java-sdk/tasks/observability/tracing/zipkin/)
+* [Associate Logs with Link Tracing](/en/overview/mannual/java-sdk/tasks/observability/tracing/tracing)
## Logging
Access logs can help analyze the system's traffic situation. In some scenarios, enabling access logs is also very helpful for troubleshooting issues.
-* [Enable Access Log](../../mannual/java-sdk/advanced-features-and-usage/service/accesslog/)
-* [Enable Access Log at Runtime](../../tasks/traffic-management/accesslog/)
+* [Enable Access Log](/en/overview/mannual/java-sdk/tasks/traffic-management/accesslog)
+* [Enable Access Log at Runtime](/en/overview/mannual/java-sdk/tasks/traffic-management/accesslog)
diff --git a/content/en/overview/what/core-features/protocols.md b/content/en/overview/what/core-features/protocols.md
index f7028978693..7db46afd022 100644
--- a/content/en/overview/what/core-features/protocols.md
+++ b/content/en/overview/what/core-features/protocols.md
@@ -43,7 +43,7 @@ In terms of programming and communication models, the Triple protocol supports t
* Bidirectional Streaming
Development Practices
-* For using the Triple protocol, refer to [Triple Protocol Development Tasks](../../tasks/protocols/triple/) or [Java SDK Example Documentation](../../mannual/java-sdk/reference-manual/protocol/triple/)
+* For using the Triple protocol, refer to [Triple Protocol Development Tasks](/en/overview/mannual/java-sdk/tasks/protocols/triple/) or [Java SDK Example Documentation](../../mannual/java-sdk/reference-manual/protocol/triple/)
* [Triple Design Ideas and Protocol Specifications](../../reference/protocols/triple/)
## Dubbo2
@@ -51,7 +51,7 @@ The Dubbo2 protocol is an RPC communication protocol built on top of the TCP tra
The Dubbo2 protocol also has built-in HTTP support, so you can use curl to quickly verify or debug services during the development phase.
-* [Dubbo2 Protocol Development Tasks](../../tasks/protocols/dubbo/)
+* [Dubbo2 Protocol Development Tasks](/en/overview/mannual/java-sdk/tasks/protocols/dubbo/)
* [Dubbo2 Design Concepts and Protocol Specifications](../../reference/protocols/tcp/)
## gRPC
@@ -61,13 +61,13 @@ gRPC is an open-source communication protocol based on HTTP/2 by Google. As ment
Using the gRPC protocol within the Dubbo framework (gRPC over Dubbo Framework) is a highly efficient and lightweight choice. It allows you to use the native gRPC protocol for communication while avoiding the complexity of secondary customization and development based on gRPC (secondary development and customization of gRPC is an unavoidable step confirmed by many enterprises after large-scale practice. The Dubbo framework completes this step for developers, allowing them to use gRPC in t [...]
-[gRPC over Dubbo Example](../../tasks/protocols/grpc/)
+[gRPC over Dubbo Example](/en/overview/mannual/java-sdk/tasks/protocols/triple/grpc)
## REST
A common communication pattern in the microservice field is HTTP + JSON. Some mainstream microservice frameworks like Spring Cloud and Microprofile default to this communication pattern. Dubbo also provides support for HTTP-based programming and communication patterns.
-* [HTTP over Dubbo Example](../../tasks/protocols/web/)
-* [Dubbo and Spring Cloud Interoperability](../../tasks/protocols/springcloud/)
+* `HTTP over Dubbo Example`
+* `Dubbo and Spring Cloud Interoperability`
## Other Communication Protocols
In addition to the protocols introduced above, you can also run the following protocols on top of Dubbo. For Dubbo, you only need to change a simple configuration line to switch the underlying service communication protocol, without affecting other peripheral APIs and governance capabilities.
@@ -83,4 +83,4 @@ For the configuration and usage methods of the above protocols, including how to
* [Rust](../../mannual/rust-sdk/)
## Custom Extensions
-In addition to the communication protocols supported by the official version above, Dubbo supports extending new protocol support. For details, please refer to [Tasks - Extensibility - Protocol](../../tasks/extensibility/protocol/)
+In addition to the communication protocols supported by the official version above, Dubbo supports extending new protocol support. For details, please refer to [Tasks - Extensibility - Protocol](/en/overview/mannual/java-sdk/tasks/extensibility/protocol)
diff --git a/content/en/overview/what/core-features/service-definition.md b/content/en/overview/what/core-features/service-definition.md
index 134d6e40bf9..f038e9d2e66 100644
--- a/content/en/overview/what/core-features/service-definition.md
+++ b/content/en/overview/what/core-features/service-definition.md
@@ -20,7 +20,7 @@ Dubbo addresses a series of challenges from development, deployment to governanc
Next, we will explain the basic steps of Dubbo application development using a Java-based Spring Boot project as an example. The entire process is very intuitive and simple, and the development process for other languages is similar.
### Create Project
-<a href="https://start.dubbo.apache.org/bootstrap.html" target="_blank">Dubbo Microservice Project Scaffolding</a> (supports browser pages, command line, and IDE) can be used to quickly create microservice projects. You only need to tell the scaffolding the desired features or components, and the scaffolding can help developers generate microservice projects with the necessary dependencies. For more explanations on how to use the scaffolding, please refer to the task module [Generate Pro [...]
+<a href="https://start.dubbo.apache.org/bootstrap.html" target="_blank">Dubbo Microservice Project Scaffolding</a> (supports browser pages, command line, and IDE) can be used to quickly create microservice projects. You only need to tell the scaffolding the desired features or components, and the scaffolding can help developers generate microservice projects with the necessary dependencies. For more explanations on how to use the scaffolding, please refer to the task module `Generate Pro [...]
@@ -88,17 +88,17 @@ public class Consumer {
```
The above is a procedural explanation of Dubbo microservice development. For detailed guidance steps in actual development, please refer to:
-* [Java Microservice Development Quick Start](../../quickstart/java)
+* [Java Microservice Development Quick Start](../../mannual/java-sdk/quick-start)
* [Go Microservice Development Quick Start](../../mannual/golang-sdk/quickstart)
-* [Rust Microservice Development Quick Start](../../quickstart/rust)
+* [Rust Microservice Development Quick Start](../../mannual/rust-sdk/quick-start)
* [Node.js Microservice Development Quick Start](https://github.com/apache/dubbo-js)
## Deployment
Dubbo native services can be packaged and deployed to cloud-native infrastructures and microservice architectures such as Docker containers, Kubernetes, and service meshes.
For deployment examples in different environments, refer to:
-* [Deploy Dubbo Services to Docker Containers](../../tasks/deploy/deploy-on-docker)
-* [Deploy Dubbo Services to Kubernetes](../../tasks/deploy/deploy-on-k8s-docker)
+* `Deploy Dubbo Services to Docker Containers`
+* `Deploy Dubbo Services to Kubernetes`
## Governance
For service governance, most applications only need to add the following configuration, and Dubbo applications will have address discovery and load balancing capabilities.
@@ -109,7 +109,7 @@ dubbo:
address: zookeeper://127.0.0.1:2181
```
-Deploy and open the [Dubbo Admin Console](../../tasks/deploy), where you can see the service deployment and call data of the cluster.
+Deploy and open the `Dubbo Admin Console`, where you can see the service deployment and call data of the cluster.
diff --git a/content/en/overview/what/core-features/service-discovery.md b/content/en/overview/what/core-features/service-discovery.md
index 5d21d04047a..64bb4bf88df 100644
--- a/content/en/overview/what/core-features/service-discovery.md
+++ b/content/en/overview/what/core-features/service-discovery.md
@@ -37,7 +37,7 @@ Unlike many other microservice frameworks, **Dubbo3's service discovery mechanis
From the registry center's perspective, it aggregates instance addresses for the entire cluster by application name (dubbo.application.name). Each service-providing instance registers its application name, instance ip:port address information (usually with a small amount of instance metadata, such as the machine's region, environment, etc.) to the registry center.
> In Dubbo2, the registry center aggregates instance addresses at the service granularity, which is finer than the application granularity, meaning more data is transmitted. Therefore, some performance issues were encountered in large-scale clusters.
-> To address the inconsistency between Dubbo2 and Dubbo3 cross-version data models, Dubbo3 provides a [smooth migration solution](/en/overview/mannual/java-sdk/upgrades-and-compatibility/service-discovery/migration-service-discovery/), ensuring that model changes are transparent to users.
+> To address the inconsistency between Dubbo2 and Dubbo3 cross-version data models, Dubbo3 provides a [smooth migration solution](/en/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration-service-discovery), ensuring that model changes are transparent to users.
diff --git a/content/en/overview/what/core-features/service-mesh.md b/content/en/overview/what/core-features/service-mesh.md
index b18ed8c5aa9..4737502fde3 100644
--- a/content/en/overview/what/core-features/service-mesh.md
+++ b/content/en/overview/what/core-features/service-mesh.md
@@ -65,10 +65,10 @@ In Proxyless mode, Dubbo processes continue to maintain direct communication:
* Suitable for almost all deployment environments.
## Example Tasks
-Having understood enough theoretical knowledge, we recommend you visit the following [examples](../../tasks/mesh) for hands-on practice.
+Having understood enough theoretical knowledge, we recommend you visit the following [examples](/en/overview/mannual/java-sdk/reference-manual/mesh/mesh) for hands-on practice.
## Visualization
-We recommend using [Dubbo Admin](../../tasks/deploy) as the visual control console for your Dubbo cluster. It is compatible with all Kubernetes, Mesh, and non-Mesh architecture deployments.
+We recommend using [Dubbo Admin](/en/overview/mannual/java-sdk/quick-start/deploy) as the visual control console for your Dubbo cluster. It is compatible with all Kubernetes, Mesh, and non-Mesh architecture deployments.
In addition, you can use the [officially recommended visualization tool by Istio](https://istio.io/latest/docs/tasks/observability/kiali/) to manage your Dubbo Mesh cluster.
diff --git a/content/en/overview/what/core-features/traffic/_index.md b/content/en/overview/what/core-features/traffic/_index.md
index c217548692b..d4d8299cd3e 100755
--- a/content/en/overview/what/core-features/traffic/_index.md
+++ b/content/en/overview/what/core-features/traffic/_index.md
@@ -49,7 +49,7 @@ Typically, in Dubbo, multiple routers form a routing chain that works together.
Tag routing divides instances of a service into different groups, constraining traffic with specific tags to flow only within designated groups. Different groups serve different traffic scenarios, achieving traffic isolation. Tag routing can serve as the foundation for scenarios like blue-green deployment and grayscale release.
-Tag routing rules are an either-or traffic isolation solution, meaning requests that match the `tag` will be 100% forwarded to instances with the same `tag`, and requests that do not match the `tag` will be 100% forwarded to the remaining unmatched instances. If you need a proportional traffic scheduling solution, please refer to the example [Proportional Traffic Routing Based on Weight](../../tasks/traffic-management/weight/).
+Tag routing rules are an either-or traffic isolation solution, meaning requests that match the `tag` will be 100% forwarded to instances with the same `tag`, and requests that do not match the `tag` will be 100% forwarded to the remaining unmatched instances. If you need a proportional traffic scheduling solution, please refer to the example [Proportional Traffic Routing Based on Weight](/en/overview/mannual/java-sdk/tasks/traffic-management/weight/).
`Tags` mainly refer to the grouping of provider application instances. Currently, there are two ways to complete instance grouping: `dynamic rule tagging` and `static rule tagging`. `Dynamic rule tagging` can dynamically enclose a group of machine instances at runtime, while `static rule tagging` requires instance restart to take effect. Among them, dynamic rules have higher priority than static rules, and when both rules exist and conflict, dynamic rules will prevail.
@@ -118,7 +118,7 @@ RpcContext.getContext().setAttachment(Constants.TAG_KEY, "Hangzhou");
Traffic with the above tag will be routed to instances divided into the `hangzhou-region`.
-> The scope of the request tag is limited to a single point-to-point RPC request. For example, in an A -> B -> C call chain, if the A -> B call sets the `tag` parameter via `setAttachment`, this parameter will not be effective in the B -> C call. Similarly, after completing the entire A -> B -> C call and A receives the result, if you want the same `tag` parameter, you still need to set `setAttachment` separately before initiating another call. You can refer to [Example Task - Environmen [...]
+> The scope of the request tag is limited to a single point-to-point RPC request. For example, in an A -> B -> C call chain, if the A -> B call sets the `tag` parameter via `setAttachment`, this parameter will not be effective in the B -> C call. Similarly, after completing the entire A -> B -> C call and A receives the result, if you want the same `tag` parameter, you still need to set `setAttachment` separately before initiating another call. You can refer to [Example Task - Environmen [...]
### Conditional Routing Rules
@@ -194,7 +194,7 @@ scope: service
key: org.apache.dubbo.samples.UserService
```
-> For more information on `scope` and `service`, `application` in Dubbo rules, please refer to the [Dynamic Configuration Reference Manual](./configuration-rule/) or [Dynamic Configuration Example](../../tasks/traffic-management/timeout/).
+> For more information on `scope` and `service`, `application` in Dubbo rules, please refer to the [Dynamic Configuration Reference Manual](./configuration-rule/) or [Dynamic Configuration Example](/en/overview/mannual/java-sdk/tasks/traffic-management/timeout/).
The `parameters` parameter specifies the new modification value, here setting the timeout to 2000ms through `timeout: 2000`.
@@ -253,7 +253,7 @@ spec:
value: "gray"
```
-If you have a different instance environment storage mechanism, you can customize your own tag loading method by extending the `InfraAdapter extension point`. If your application is deployed in a Kubernetes environment and has integrated with the service mesh system, you can also use the standard deployment tag method for tagging. For details, please follow the [Service Mesh Task Example](../../tasks/mesh/).
+If you have a different instance environment storage mechanism, you can customize your own tag loading method by extending the `InfraAdapter extension point`. If your application is deployed in a Kubernetes environment and has integrated with the service mesh system, you can also use the standard deployment tag method for tagging. For details, please follow the [Service Mesh Task Example](/en/overview/tasks/mesh/).
## How to Configure Traffic Rules
Dubbo provides a console called Dubbo Admin to help you visualize and issue traffic control rules, and monitor the effectiveness of the rules in real-time.
@@ -271,4 +271,4 @@ The above introduces traffic governance rules within the Dubbo system. If you ar
For details, please refer to [Service Mesh Architecture in Dubbo](../service-mesh).
## Learn by Example
-We have set up an [online shopping system](../../tasks/traffic-management/) for you to learn the specific usage of traffic rules.
+We have set up an [online shopping system](/en/overview/mannual/java-sdk/tasks/traffic-management/) for you to learn the specific usage of traffic rules.
diff --git a/content/en/overview/what/core-features/traffic/circuit-breaking.md b/content/en/overview/what/core-features/traffic/circuit-breaking.md
index a3fd27c6dcb..f588a18d3f4 100644
--- a/content/en/overview/what/core-features/traffic/circuit-breaking.md
+++ b/content/en/overview/what/core-features/traffic/circuit-breaking.md
@@ -21,9 +21,9 @@ Depending on the specific deployment of the service, the upper limit of traffic
The problem solved by rate limiting and its working mechanism are relatively easy to understand. The difficulty lies in determining the maximum traffic that the service can handle.
* One mode is for the user to preset a fixed rate limit value. For example, Dubbo achieves rate limiting capabilities by integrating products like Sentinel.
- * [Dubbo Sentinel Rate Limiting](../../../tasks/rate-limit/sentinel/)
+ * [Dubbo Sentinel Rate Limiting](/en/overview/mannual/java-sdk/tasks/rate-limit/sentinel/)
* Another way is for the Dubbo framework to automatically perform rate limiting based on system or cluster load conditions. This is more flexible and convenient compared to the user presetting the rate limit value. Dubbo currently has a built-in adaptive rate limiting mode. For details, see:
- * [Java Adaptive Rate Limiting Usage](../../../mannual/java-sdk/advanced-features-and-usage/performance/adaptive-concurrency-control/)
+ * [Java Adaptive Rate Limiting Usage](/en/overview/mannual/java-sdk/tasks/rate-limit/adaptive-concurrency-control)
* [Go Adaptive Rate Limiting Usage](../../../reference/proposals/heuristic-flow-control/)
* [Adaptive Rate Limiting Design Principles](../../../reference/proposals/heuristic-flow-control/)
@@ -38,7 +38,7 @@ As shown in the figure above, Dubbo Consumer relies on three downstream Dubbo se
Dubbo has achieved service circuit breaking and degradation capabilities by integrating mainstream frameworks in the industry.
-* [Sentinel](../../../tasks/rate-limit/sentinel/)
-* [Hystrix](../../../tasks/rate-limit/hystrix/)
-* [Resilience4J](../../../tasks/rate-limit/resilience4j/)
+* [Sentinel](/en/overview/mannual/java-sdk/tasks/rate-limit/sentinel/)
+* `Hystrix`
+* `Resilience4J`
diff --git a/content/en/overview/what/core-features/traffic/introduction.md b/content/en/overview/what/core-features/traffic/introduction.md
index 87649f0e0c8..1995942317e 100644
--- a/content/en/overview/what/core-features/traffic/introduction.md
+++ b/content/en/overview/what/core-features/traffic/introduction.md
@@ -42,7 +42,7 @@ Typically, in Dubbo, multiple routers form a routing chain that works together.
Tag routing divides instances of a service into different groups, constraining traffic with specific tags to flow only within designated groups. Different groups serve different traffic scenarios, achieving traffic isolation. Tag routing can serve as the foundation for scenarios such as blue-green deployment and canary release.
-Tag routing rules are an either-or traffic isolation solution, meaning requests matching a `tag` will be 100% forwarded to instances with the same `tag`, and requests not matching a `tag` will be 100% forwarded to the remaining unmatched instances. If you need a proportional traffic scheduling solution, please refer to the example [Proportional Traffic Routing Based on Weight](../../tasks/traffic-management/weight/).
+Tag routing rules are an either-or traffic isolation solution, meaning requests matching a `tag` will be 100% forwarded to instances with the same `tag`, and requests not matching a `tag` will be 100% forwarded to the remaining unmatched instances. If you need a proportional traffic scheduling solution, please refer to the example [Proportional Traffic Routing Based on Weight](/en/overview/mannual/java-sdk/tasks/traffic-management/weight).
`Tags` mainly refer to the grouping of provider-side application instances. Currently, there are two ways to complete instance grouping: `dynamic rule tagging` and `static rule tagging`. `Dynamic rule tagging` can dynamically enclose a group of machine instances at runtime, while `static rule tagging` requires instance restart to take effect. Among them, dynamic rules have a higher priority than static rules, and when both rules exist and conflict, dynamic rules will prevail.
@@ -111,7 +111,7 @@ RpcContext.getContext().setAttachment(Constants.TAG_KEY, "Hangzhou");
Traffic with the above tag will be routed to instances divided by the `hangzhou-region`.
-> The scope of the request tag is limited to a single point-to-point RPC request. For example, in an A -> B -> C call chain, if the A -> B call sets the `tag` parameter through `setAttachment`, this parameter will not be effective in the B -> C call. Similarly, after completing the entire A -> B -> C call and A receives the result, if you want the same `tag` parameter, you still need to set `setAttachment` separately before initiating other calls. You can refer to [Example Task - Environ [...]
+> The scope of the request tag is limited to a single point-to-point RPC request. For example, in an A -> B -> C call chain, if the A -> B call sets the `tag` parameter through `setAttachment`, this parameter will not be effective in the B -> C call. Similarly, after completing the entire A -> B -> C call and A receives the result, if you want the same `tag` parameter, you still need to set `setAttachment` separately before initiating other calls. You can refer to [Example Task - Environ [...]
### Conditional Routing Rules
@@ -187,7 +187,7 @@ scope: service
key: org.apache.dubbo.samples.UserService
```
-> For more information about `scope` and `service`, `application` in Dubbo rules, please refer to the [Dynamic Configuration Reference Manual](./configuration-rule/) or [Dynamic Configuration Example](../../tasks/traffic-management/timeout/).
+> For more information about `scope` and `service`, `application` in Dubbo rules, please refer to the [Dynamic Configuration Reference Manual](./configuration-rule/) or [Dynamic Configuration Example](/en/overview/mannual/java-sdk/tasks/traffic-management/timeout).
The `parameters` parameter specifies the new modification value. Here, the timeout is set to 2000ms through `timeout: 2000`.
@@ -246,7 +246,7 @@ spec:
value: "gray"
```
-If you have a different instance environment preservation mechanism, you can customize your own tag loading method by extending the `InfraAdapter extension point`. If your application is deployed in a Kubernetes environment and has already integrated with the service mesh system, you can also use the standard deployment tag method for tagging. For details, please follow the [Service Mesh Task Example](../../tasks/mesh/).
+If you have a different instance environment preservation mechanism, you can customize your own tag loading method by extending the `InfraAdapter extension point`. If your application is deployed in a Kubernetes environment and has already integrated with the service mesh system, you can also use the standard deployment tag method for tagging. For details, please follow the [Service Mesh Task Example](/en/overview/mannual/java-sdk/reference-manual/mesh/mesh).
```
## How to Configure Traffic Rules
diff --git a/content/en/overview/what/core-features/traffic/mesh-rule.md b/content/en/overview/what/core-features/traffic/mesh-rule.md
index 2360ffd6b3a..9f3024b5075 100644
--- a/content/en/overview/what/core-features/traffic/mesh-rule.md
+++ b/content/en/overview/what/core-features/traffic/mesh-rule.md
@@ -363,4 +363,4 @@ subsets:
> Similar to label routing, this involves how to label your instances (here it is `detail_version`). Please refer to the section How to Label Instances below.
-In addition to the functions introduced above that are very similar to Istio's traffic rules, Dubbo's VirtualService and DestinationRule can also achieve things that Istio rules cannot, such as method parameter routing. For details, see the [Reference Manual]().
+In addition to the functions introduced above that are very similar to Istio's traffic rules, Dubbo's VirtualService and DestinationRule can also achieve things that Istio rules cannot, such as method parameter routing. For details, see the `Reference Manual`.
diff --git a/content/zh-cn/docs/references/xml/dubbo-registry.md b/content/zh-cn/docs/references/xml/dubbo-registry.md
index 94f55bd6ee3..a9ffc44f7de 100644
--- a/content/zh-cn/docs/references/xml/dubbo-registry.md
+++ b/content/zh-cn/docs/references/xml/dubbo-registry.md
@@ -10,7 +10,7 @@ weight: 1
-{{% pageinfo %}} 此文档已经不再维护。您当前查看的是快照版本。如果想要查看最新版本的文档，请参阅[最新版本](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/#registry)。
+{{% pageinfo %}} 此文档已经不再维护。您当前查看的是快照版本。如果想要查看最新版本的文档，请参阅[最新版本](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/registry)。
{{% /pageinfo %}}
注册中心配置。对应的配置类： `org.apache.dubbo.config.RegistryConfig`。同时如果有多个不同的注册中心，可以声明多个 `<dubbo:registry>` 标签，并在 `<dubbo:service>` 或 `<dubbo:reference>` 的 `registry` 属性指定使用的注册中心。
diff --git a/content/zh-cn/docsv2.7/user/examples/simplify-registry-data.md b/content/zh-cn/docsv2.7/user/examples/simplify-registry-data.md
index 854a60613ba..75de49a22df 100644
--- a/content/zh-cn/docsv2.7/user/examples/simplify-registry-data.md
+++ b/content/zh-cn/docsv2.7/user/examples/simplify-registry-data.md
@@ -12,9 +12,9 @@ weight: 37
## 背景
-Dubbo provider 中的服务配置项有接近 [30 个配置项](/en/docs/v2.7/user/references/xml/dubbo-service/)。 排除注册中心服务治理需要之外，很大一部分配置项是 provider 自己使用，不需要透传给消费者。这部分数据不需要进入注册中心，而只需要以 key-value 形式持久化存储。
+Dubbo provider 中的服务配置项有接近 [30 个配置项](/zh-cn/docsv2.7/user/references/xml/dubbo-service/)。 排除注册中心服务治理需要之外，很大一部分配置项是 provider 自己使用，不需要透传给消费者。这部分数据不需要进入注册中心，而只需要以 key-value 形式持久化存储。
-Dubbo consumer 中的配置项也有 [20+个配置项](/en/docs/v2.7/user/references/xml/dubbo-reference/)。在注册中心之中，服务消费者列表中只需要关注 application，version，group，ip，dubbo 版本等少量配置，其他配置也可以以 key-value 形式持久化存储。
+Dubbo consumer 中的配置项也有 [20+个配置项](/zh-cn/docsv2.7/user/references/xml/dubbo-reference/)。在注册中心之中，服务消费者列表中只需要关注 application，version，group，ip，dubbo 版本等少量配置，其他配置也可以以 key-value 形式持久化存储。
这些数据是以服务为维度注册进入注册中心，导致了数据量的膨胀，进而引发注册中心(如 zookeeper)的网络开销增大，性能降低。
diff --git a/content/zh-cn/overview/mannual/control-plane/test.md b/content/zh-cn/overview/mannual/control-plane/test.md
index ce4a83b3356..3df633fff4c 100644
--- a/content/zh-cn/overview/mannual/control-plane/test.md
+++ b/content/zh-cn/overview/mannual/control-plane/test.md
@@ -18,7 +18,7 @@ working_in_progress: true
### 准备用例
1. 启动用例
- 可以参考 [快速开始](../../../quickstart/java/) 启动一个简单的 Dubbo 服务，对于服务测试来说，只需要启动 provider 即可。
+ 可以参考 [快速开始](../../../mannual/java-sdk/quickstart/) 启动一个简单的 Dubbo 服务，对于服务测试来说，只需要启动 provider 即可。
2. 查询服务
diff --git a/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/10.md b/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/10.md
index 569d0035c0b..b3646471067 100644
--- a/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/10.md
+++ b/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/10.md
@@ -23,4 +23,4 @@ weight: 10
该错误常与 1-9 错误共同出现。检查是否有多个 Dubbo 进程使用了同一个缓存文件或者是否指定多个注册中心使用同一缓存文件。
> 另请参阅
-[注册中心的配置项参考手册](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/#registry)
+[注册中心的配置项参考手册](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/registry)
diff --git a/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/7.md b/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/7.md
index 03355ae06d7..72d51ba7739 100644
--- a/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/7.md
+++ b/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/7.md
@@ -22,4 +22,4 @@ weight: 7
### 排查和解决步骤
> 另请参阅
-[注册中心-配置项参考手册](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/#registry)
+[注册中心-配置项参考手册](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/registry)
diff --git a/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/9.md b/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/9.md
index 8fbeab0ac0e..7936958d0ab 100644
--- a/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/9.md
+++ b/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/1/9.md
@@ -32,4 +32,4 @@ weight: 9
4. 排查是否出现了“两个注册中心使用了同一文件存储” 这一情况，如果出现则调整。
> 另请参阅
-[注册中心的配置项参考手册](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/#registry)
+[注册中心的配置项参考手册](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/registry)
diff --git a/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/7/7.md b/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/7/7.md
index 5ac45a2ee3b..3f8ccaff434 100644
--- a/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/7/7.md
+++ b/content/zh-cn/overview/mannual/java-sdk/reference-manual/faq/7/7.md
@@ -22,4 +22,4 @@ weight: 7
### 排查和解决步骤
检查请求是否是预期发生的，如果非预期请检查是否有恶意攻击源。
-> 如果是预期的，请参考 [QoS 安全](/zh-cn/overview/mannual/java-sdk/reference-manual/qos/overview/#%E5%AE%89%E5%85%A8) 一文配置对应的权限信息。
+> 如果是预期的，请参考 [QoS 安全](/zh-cn/overview/mannual/java-sdk/reference-manual/qos/overview#安全) 一文配置对应的权限信息。
diff --git a/content/zh-cn/overview/mannual/java-sdk/reference-manual/registry/overview.md b/content/zh-cn/overview/mannual/java-sdk/reference-manual/registry/overview.md
index 2fe82a1643f..2612b8c87c5 100644
--- a/content/zh-cn/overview/mannual/java-sdk/reference-manual/registry/overview.md
+++ b/content/zh-cn/overview/mannual/java-sdk/reference-manual/registry/overview.md
@@ -36,7 +36,7 @@ dubbo
3.3.0 及之后的版本可不配置注册中心。而在 3.3.0 版本之前的 Dubbo 应用必须指定注册中心配置，即使不启用注册中心也要配置（可通过设置地址为空 address='N/A' ）。
{{% /alert %}}
-每个注册中心组件有自己特有的配置，可以用来控制命名空间、分组、鉴权等，具体可以参考 [registry 配置参考手册](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/#registry)或通过 parameters 参数进行扩展。
+每个注册中心组件有自己特有的配置，可以用来控制命名空间、分组、鉴权等，具体可以参考 [registry 配置参考手册](/zh-cn/overview/mannual/java-sdk/reference-manual/config/properties/registry)或通过 parameters 参数进行扩展。
## 配置中心与元数据中心
配置中心、元数据中心是实现 Dubbo 高阶服务治理能力会依赖的组件，如流量管控规则等，相比于注册中心通常这两个组件的配置是可选的。
diff --git a/content/zh-cn/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration.md b/content/zh-cn/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration.md
index 3cee46083f5..d5161f1a604 100644
--- a/content/zh-cn/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration.md
+++ b/content/zh-cn/overview/mannual/java-sdk/reference-manual/upgrades-and-compatibility/migration.md
@@ -53,7 +53,7 @@ weight: 1
{{% alert title="Dubbo3 相关的 Spring、Spring Boot 版本升级说明" color="warning" %}}
Dubbo3 支持的 Spring、Spring Boot 版本兼容范围非常广：
* 既支持 Spring 3.x ~ Spring 5.x 相关版本，同时也支持 Spring Boot 1.x ~ Spring Boot 2.x 版本。如果遇到应用无法升级高版本 Spring、Spring Boot 的情况下，可排掉 `dubbo-spring-boot-starter` 或 `dubbo` 中传递的高版本 Spring 依赖，指定项目可接受的 Spring 版本依赖即可。
-* Spring Boot 3.x 和 Spring 6 版本由于需要 JDK 17 及以上版本，请参考 [Dubbo Spring Boot 手册]() 了解详情。
+* Spring Boot 3.x 和 Spring 6 版本由于需要 JDK 17 及以上版本，请参考 `Dubbo Spring Boot 手册` 了解详情。
{{% /alert %}}
### 步骤二：升级其它组件依赖
@@ -126,7 +126,7 @@ Dubbo3 支持的 Spring、Spring Boot 版本兼容范围非常广：
除了注册中心之外，如果您有用到 Dubbo 的其它特性并且依赖第三方组件支持此特性，则您需要根据具体情况升级相应的组件版本，以确保组件能配合 Dubbo3 工作。
{{% alert title="查看依赖的三方组件版本" color="info" %}}
-目的是确认项目中的三方依赖可以与 Dubbo3 正常工作（保持API兼容性）。正常来说，Dubbo 应用中并不会有非常多的第三方组件依赖，所以只要按需确认即可，另外，您可以参考 [Dubbo3 版本依赖的组件版本]() 确认合适的组件版本。
+目的是确认项目中的三方依赖可以与 Dubbo3 正常工作（保持API兼容性）。正常来说，Dubbo 应用中并不会有非常多的第三方组件依赖，所以只要按需确认即可，另外，您可以参考 `Dubbo3 版本依赖的组件版本` 确认合适的组件版本。
{{% /alert %}}
### 步骤三：兼容性检查
diff --git a/content/zh-cn/overview/mannual/python-sdk/_index.md b/content/zh-cn/overview/mannual/python-sdk/_index.md
index ad1bf419094..c310cd71c58 100755
--- a/content/zh-cn/overview/mannual/python-sdk/_index.md
+++ b/content/zh-cn/overview/mannual/python-sdk/_index.md
@@ -3,7 +3,6 @@ description: Dubbo Python SDK 使用手册
aliases:
- /zh/docs3-v2/python-sdk/
- /zh-cn/docs3-v2/python-sdk/
-description: Python SDK 使用手册
linkTitle: Python SDK
title: Python SDK 手册
type: docs
diff --git a/content/zh-cn/overview/reference/proposals/registry-config-meta.md b/content/zh-cn/overview/reference/proposals/registry-config-meta.md
index 11c0f4c5f23..d34dbf0a1a6 100644
--- a/content/zh-cn/overview/reference/proposals/registry-config-meta.md
+++ b/content/zh-cn/overview/reference/proposals/registry-config-meta.md
@@ -86,7 +86,7 @@ Dubbo SDK对三大中心都支持了Multiple模式。
## 三中心物理部署架构
-
+[//]: # ()
## 不同场景下的推荐使用方式
* 只配置 registry，默认作为 metadata、config-center
diff --git a/content/zh-cn/overview/what/core-features/service-definition.md b/content/zh-cn/overview/what/core-features/service-definition.md
index 127ebbf9b64..13b94145060 100644
--- a/content/zh-cn/overview/what/core-features/service-definition.md
+++ b/content/zh-cn/overview/what/core-features/service-definition.md
@@ -88,9 +88,9 @@ public class Consumer {
```
以上是 Dubbo 微服务开发的流程性说明，实际开发的详细指导步骤请参见：
-* [Java 微服务开发入门](../../quickstart/java)
+* [Java 微服务开发入门](../../mannual/java-sdk/quickstart)
* [Go 微服务开发入门](../../mannual/golang-sdk/quickstart)
-* [Rust 微服务开发入门](../../quickstart/rust)
+* [Rust 微服务开发入门](../../mannual/rust-sdk/quickstart)
* [Node.js 微服务开发入门](https://github.com/apache/dubbo-js)
## 部署
diff --git a/package.json b/package.json
index 289965c3f8b..d6f4d3f59d0 100644
--- a/package.json
+++ b/package.json
@@ -13,8 +13,8 @@
},
"homepage": "https://dubbo.apache.org",
"devDependencies": {
- "autoprefixer": "^10.4.19",
- "postcss": "^8.4.38",
- "postcss-cli": "^11.0.0"
+ "autoprefixer": "^10.4.21",
+ "postcss": "^8.5.6",
+ "postcss-cli": "^11.0.1"
}
}