[shardingsphere] branch master updated: Change link of repojacking vulnerable link (#21370)

[zh...@apache.org]

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 9ff2412eee4 Change link of repojacking vulnerable link (#21370)
9ff2412eee4 is described below

commit 9ff2412eee4b12a326741d1753257a35577682be
Author: yakirk <ka...@gmail.com>
AuthorDate: Sat Oct 8 17:29:30 2022 +0300

    Change link of repojacking vulnerable link (#21370)
---
 docs/blog/content/material/committer.en.md | 4 ++--
 docs/blog/content/material/proxy.en.md     | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/docs/blog/content/material/committer.en.md b/docs/blog/content/material/committer.en.md
index fd699215307..0ce8897fcca 100644
--- a/docs/blog/content/material/committer.en.md
+++ b/docs/blog/content/material/committer.en.md
@@ -44,11 +44,11 @@ How about starting with a task and training hands? The tasks currently announced
 
 - Implement rule configuration of Sharding-SpringBoot using Inline expression
 
-  https://github.com/sharding-sphere/sharding-sphere/issues/1686
+  https://github.com/apache/shardingsphere/issues/1686
 
 - Implement the rule configuration of Sharding-SpringBoot using SpringBoot placeholder
 
-  https://github.com/sharding-sphere/sharding-sphere/issues/1687
+  https://github.com/apache/shardingsphere/issues/1687
 
 
 We will also regularly publish some development function tasks in the form of issue on GitHub in the future. Welcome to follow us by subscribing to our mailing list. For details, please refer to the official website:
diff --git a/docs/blog/content/material/proxy.en.md b/docs/blog/content/material/proxy.en.md
index b3d955c5eb9..6c19b758f58 100644
--- a/docs/blog/content/material/proxy.en.md
+++ b/docs/blog/content/material/proxy.en.md
@@ -247,7 +247,7 @@ If you feel confused, please keep it in mind CONNECTION_STRICTLY is a scenario t
 ### 03 Summary
 Sharding-Sphere has been continuous improvement and development since 2016. A growing number of companies and individuals uses it, and they provide many successful cases for us.  We will move forward to improve current features, achieve soft transaction, data governance and so on in succession. If someone has good ideas or wants to do proposals, welcome to join Sharding-Sphere open source project.
 
-*   https://github.com/sharding-sphere/sharding-sphere/
+*   https://github.com/apache/shardingsphere
     
 *   https://gitee.com/sharding-sphere/sharding-sphere/