This is an automated email from the ASF dual-hosted git repository.
zhangliang pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/shardingsphere.git
The following commit(s) were added to refs/heads/master by this push:
new 711a8ef34f1 Fix : fix dead link (#30191)
711a8ef34f1 is described below
commit 711a8ef34f12df3a2338797fa30ecc31efccb6ae
Author: 孙念君 Nianjun Sun <[email protected]>
AuthorDate: Mon Feb 19 12:58:10 2024 +0800
Fix : fix dead link (#30191)
* Fix : fix dead link
* Fix : fix deadlink
---
.../yaml-config/jdbc-driver/known-implementation/_index.cn.md | 4 ++--
.../yaml-config/jdbc-driver/known-implementation/_index.en.md | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git
a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.cn.md
b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.cn.md
index 17ff74b4e44..308fc668b77 100644
---
a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.cn.md
+++
b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.cn.md
@@ -13,12 +13,12 @@ chapter = true
这并不阻止 `org.apache.shardingsphere.infra.url.ShardingSphereURLLoader` 的自定义实现从
XML 或 JSON 等文件手动转化为 YAML。
在解析并加载 YAML 文件为 ShardingSphere 的元数据后，
-会再次通过[模式配置](../../../java-api/mode)的相关配置决定下一步行为。讨论两种情况，
+会再次通过[模式配置](../../../../java-api/mode)的相关配置决定下一步行为。讨论两种情况，
1. 元数据持久化仓库中不存在 ShardingSphere 的元数据，本地元数据将被存储到元数据持久化仓库。
2. 元数据持久化仓库中已存在 ShardingSphere 的元数据，无论是否与本地元数据相同，本地元数据将被元数据持久化仓库的元数据覆盖。
-对元数据持久化仓库的配置需参考[元数据持久化仓库](../../../../common-config/builtin-algorithm/metadata-repository)。
+对元数据持久化仓库的配置需参考[元数据持久化仓库](../../../../../common-config/builtin-algorithm/metadata-repository)。
## 加载配置文件的方式
diff --git
a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.en.md
b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.en.md
index 20c0ec73630..3ae5bbe82bb 100644
---
a/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.en.md
+++
b/docs/document/content/user-manual/shardingsphere-jdbc/yaml-config/jdbc-driver/known-implementation/_index.en.md
@@ -13,7 +13,7 @@ If there is no specific statement, the following
implementations all use YAML 1.
This does not prevent custom implementations of
`org.apache.shardingsphere.infra.url.ShardingSphereURLLoader` from being
manually converted to YAML from files such as XML or JSON.
After parsing and loading the YAML file into ShardingSphere's metadata,
-the next behavior will be determined again through the relevant configuration
of [Mode Configuration](../../../java-api/mode).
+the next behavior will be determined again through the relevant configuration
of [Mode Configuration](../../../../java-api/mode).
Discuss two situations,
1. ShardingSphere’s metadata does not exist in the Metadata Repository, and
local metadata will be stored in the Metadata Repository.
@@ -22,7 +22,7 @@ Discuss two situations,
the local metadata will be overwritten by the metadata of the Metadata
Repository.
For the configuration of the Metadata Repository,
-please refer to [Metadata
Repository](../../../../common-config/builtin-algorithm/metadata-repository).
+please refer to [Metadata
Repository](../../../../../common-config/builtin-algorithm/metadata-repository).
## How to load configuration files
