This is an automated email from the ASF dual-hosted git repository.
zhaojinchao 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 4b78b8034c9 Fix : fix the deadlink (#28368)
4b78b8034c9 is described below
commit 4b78b8034c9be6f88c5f6aa8eb4f0ba718ce09e6
Author: 孙念君 Nianjun Sun <[email protected]>
AuthorDate: Wed Sep 6 11:16:02 2023 +0800
Fix : fix the deadlink (#28368)
---
docs/document/content/user-manual/shardingsphere-jdbc/_index.cn.md | 2 +-
docs/document/content/user-manual/shardingsphere-jdbc/_index.en.md | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/_index.cn.md
b/docs/document/content/user-manual/shardingsphere-jdbc/_index.cn.md
index 9cc8f54921b..c7d777fb048 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/_index.cn.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/_index.cn.md
@@ -18,4 +18,4 @@ ShardingSphere-JDBC 提供了 2 种配置方式，用于不同的使用场景。
如果前一个规则是面向数据源聚合的，下一个规则在配置数据源时，则需要使用前一个规则配置的聚合后的逻辑数据源名称；
同理，如果前一个规则是面向表聚合的，下一个规则在配置表时，则需要使用前一个规则配置的聚合后的逻辑表名称。
-更多使用细节请参见[使用示例](https://github.com/apache/shardingsphere/tree/master/examples/shardingsphere-example-generator)。
+更多使用细节请参见[使用示例](https://github.com/apache/shardingsphere/tree/master/examples/shardingsphere-jdbc-example-generator)。
diff --git a/docs/document/content/user-manual/shardingsphere-jdbc/_index.en.md
b/docs/document/content/user-manual/shardingsphere-jdbc/_index.en.md
index ae71d011559..e7d4fc9b10b 100644
--- a/docs/document/content/user-manual/shardingsphere-jdbc/_index.en.md
+++ b/docs/document/content/user-manual/shardingsphere-jdbc/_index.en.md
@@ -19,4 +19,4 @@ It should be noted that the superposition between rules are
data source and tabl
If the previous rule is data source oriented aggregation, the next rule needs
to use the aggregated logical data source name configured by the previous rule
when configuring the data source;
Similarly, if the previous rule is table oriented aggregation, the next rule
needs to use the aggregated logical table name configured by the previous rule
when configuring the table.
-Please refer to
[Example](https://github.com/apache/shardingsphere/tree/master/examples/shardingsphere-example-generator)
for more details.
+Please refer to
[Example](https://github.com/apache/shardingsphere/tree/master/examples/shardingsphere-jdbc-example-generator)
for more details.
