diff --git a/home/blog/2023-05-11-greptimedb-store.md b/home/blog/2023-05-11-greptimedb-store.md
index 43bef637e8..bab74edca4 100644
--- a/home/blog/2023-05-11-greptimedb-store.md
+++ b/home/blog/2023-05-11-greptimedb-store.md
@@ -1,8 +1,8 @@
 ---
-title: GreptimeDB & HertzBeat, using the open source temporal database GreptimeDB to store metrics for the open source real-time monitoring HertzBeat    
-author: tom  
-author_title: tom   
-author_url: https://github.com/tomsun28  
+title: GreptimeDB & HertzBeat, using the open source temporal database GreptimeDB to store metrics for the open source real-time monitoring HertzBeat
+author: tom
+author_title: tom
+author_url: https://github.com/tomsun28
 tags: [opensource, practice]
 keywords: [open source monitoring system, open source temporal database, HertzBeat, GreptimeDB]
 ---
@@ -18,7 +18,7 @@ keywords: [open source monitoring system, open source temporal database, HertzBe
 - Efficient storage and computation, with object storage and high data compression rate to achieve ultra-low storage costs. Built-in data analytics solution to avoid replicating data to external data warehouses.
 - Distributed, Highly Reliable & Highly Available, easily scale each module independently with decoupled cloud-native architecture. Ensure data reliability and availability with configurable replicas and automated failover mechanisms.
 
-Cloud: **[GreptimePlay](https://greptime.com/playground)**
+Cloud: **[GreptimePlay](https://greptime.com/product/cloud)**
 
 ### What is HertzBeat?
 
diff --git a/home/docs/community/code-style-and-quality-guide.md b/home/docs/community/code-style-and-quality-guide.md
index f1a489a92f..c9fa91e1c0 100644
--- a/home/docs/community/code-style-and-quality-guide.md
+++ b/home/docs/community/code-style-and-quality-guide.md
@@ -27,7 +27,7 @@ limitations under the License.
 
    - After creating a new `PR`, you need to associate the existing corresponding `ISSUE` at the Github Development button on the `PR` page (if there is no corresponding ISSUE, it is recommended to create a new corresponding ISSUE).
 
-   - Title naming format  
+   - Title naming format
      `[feature/bugfix/doc/improve/refactor/bug/cleanup] title`
 
 2. Description
@@ -35,7 +35,7 @@ limitations under the License.
    - Please fill in the `PR` template to describe the contribution. So that the reviewer can understand the problem and solution from the description, rather than just from the code.
    - Check the CheckList
 3. It's recommended that `PR` should be arranged changes such as `cleanup`, `Refactor`, `improve`, and `feature` into separated `PRs`/`Commits`.
-4. Commit message(English, lowercase, no special characters)  
+4. Commit message(English, lowercase, no special characters)
    The commit of messages should follow a pattern similar to the `[feature/bugfix/doc/improve/refactor/bug/cleanup] title`
 
 ## 2 Code Checkstyle
@@ -133,8 +133,8 @@ Error code description:
    ```
 
 2. Pinyin abbreviations are prohibited for variables (excluding nouns such as place names), such as chengdu.
-3. It is recommended to end variable names with a `type`.  
-   For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type).  
+3. It is recommended to end variable names with a `type`.
+   For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type).
    For variables of type `map`, describe the `key` and `value` clearly:
 
    ```java
@@ -142,7 +142,7 @@ Error code description:
    Map<Long, String> userIdNameMap;
    ```
 
-4. That can intuitively know the type and meaning of the variable through its name.  
+4. That can intuitively know the type and meaning of the variable through its name.
    Method names should start with a verb first as follows:
 
    ```java
@@ -320,7 +320,7 @@ to reduce code line depth and improve readability like follows:
           ......
           }
       }
-    
+
       ```
 
   - Positive demo:
@@ -630,7 +630,7 @@ public void process(String input) {
      // ignored declaration lines.
      List`<User>` userList = getUsersByBatch(1000);
      if (LOG.isDebugEnabled()) {
-       LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); 
+       LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList));
      }
      ```
 
@@ -644,6 +644,5 @@ public void process(String input) {
 
 - [https://site.mockito.org/](https://site.mockito.org/)
 - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/)
-- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/)
 - [https://junit.org/junit5/](https://junit.org/junit5/)
 - [https://streampark.apache.org/](https://streampark.apache.org/)
diff --git a/home/docs/community/how-to-verify.md b/home/docs/community/how-to-verify.md
index 91aa60cdb7..4bd9c90a08 100644
--- a/home/docs/community/how-to-verify.md
+++ b/home/docs/community/how-to-verify.md
@@ -91,10 +91,10 @@ check result
 > If something like the following appears, it means the signature is correct. Keyword: **`Good signature`**
 
 ```shell
-apache-hertzbeat-xxx-src.tar.gz
+apache-hertzbeat-${release_version}-src.tar.gz
 gpg: Signature made XXXX
 gpg: using RSA key XXXXX
-gpg: Good signature from "xxx @apache.org>"
+gpg: Good signature from "XXX <xxx@apache.org>"
 ```
 
 #### 2.3 Check sha512 hash
@@ -125,10 +125,10 @@ check as follows:
 
 > If the binary/web-binary package is uploaded, check the binary package.
 
-Unzip `apache-hertzbeat-`release_version`-src.tar.gz`
+Unzip `apache-hertzbeat-${release_version}-src.tar.gz`
 
 ```shell
-cd apache-hertzbeat-`release_version`-src
+cd apache-hertzbeat-${release_version}-src
 ```
 
 compile the source code: [Build HertzBeat Binary Package](https://hertzbeat.apache.org/docs/community/development/#build-hertzbeat-binary-package)
diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-05-11-greptimedb-store.md b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-05-11-greptimedb-store.md
index d0a2f85989..b99a535f1a 100644
--- a/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-05-11-greptimedb-store.md
+++ b/home/i18n/zh-cn/docusaurus-plugin-content-blog/2023-05-11-greptimedb-store.md
@@ -1,8 +1,8 @@
 ---
-title: GreptimeDB & HertzBeat, 使用开源时序数据库 GreptimeDB 存储开源实时监控 HertzBeat 的度量数据    
-author: tom  
-author_title: tom   
-author_url: https://github.com/tomsun28  
+title: GreptimeDB & HertzBeat, 使用开源时序数据库 GreptimeDB 存储开源实时监控 HertzBeat 的度量数据
+author: tom
+author_title: tom
+author_url: https://github.com/tomsun28
 tags: [opensource, practice]
 keywords: [开源监控系统, 开源时序数据库, HertzBeat, GreptimeDB]
 ---
@@ -18,7 +18,7 @@ keywords: [开源监控系统, 开源时序数据库, HertzBeat, GreptimeDB]
 - 高效存储与计算，通过对象存储和高数据压缩率实现超低的存储成本。内置数据分析解决方案，避免将数据复制到外部数据仓库。
 - 分布式、高可靠与高可用，通过解耦的云原生架构，轻松独立地扩展每个模块。通过可配置的副本和自动的故障转移机制，确保数据的可靠性和可用性。
 
-Cloud: **[GreptimePlay](https://greptime.com/playground)**
+Cloud: **[GreptimePlay](https://greptime.com/product/cloud)**
 
 ### 什么是 HertzBeat
 
diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/code-style-and-quality-guide.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/code-style-and-quality-guide.md
index 1c67ee891f..2550e0e822 100644
--- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/code-style-and-quality-guide.md
+++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/code-style-and-quality-guide.md
@@ -35,7 +35,7 @@ limitations under the License.
    - 新建 `PR` 时请仔细描述此贡献，描述文档和代码同样重要。审阅者可以从描述中，而不仅仅是从代码中，了解问题和解决方案。
    - 勾选是否完成了对应的 Checklist。
 3. 建议一次 `PR` 只包含一个功能/一种修复/一类改进/一种重构/一次清理/一类文档等
-4. 提交消息(英文，小写，无特殊字符)  
+4. 提交消息(英文，小写，无特殊字符)
    消息的提交应遵循与 `PR` 类似的模式：`[feature/bugfix/doc/improve/refactor/bug/cleanup] title`
 
 ## 2 代码检查样式
@@ -631,7 +631,7 @@ public void process(String input) {
      // 忽略声明行。
      List`<User>` userList = getUsersByBatch(1000);
      if (LOG.isDebugEnabled()) {
-        LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); 
+        LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList));
      }
      ```
 
@@ -645,6 +645,5 @@ public void process(String input) {
 
 - [https://site.mockito.org/](https://site.mockito.org/)
 - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/)
-- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/)
 - [https://junit.org/junit5/](https://junit.org/junit5/)
 - [https://streampark.apache.org/](https://streampark.apache.org/)
diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/how-to-verify.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/how-to-verify.md
index ca56885448..f1f82bafb0 100644
--- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/how-to-verify.md
+++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/current/community/how-to-verify.md
@@ -86,10 +86,10 @@ for i in *.tar.gz; do echo $i; gpg --verify $i.asc $i ; done
 > 出现类似以下内容则说明签名正确，关键字：**`Good signature`**
 
 ```shell
-apache-hertzbeat-xxx-incubating-src.tar.gz
+apache-hertzbeat-${release_version}-src.tar.gz
 gpg: Signature made XXXX
 gpg:                using RSA key XXXXX
-gpg: Good signature from "xxx @apache.org>"
+gpg: Good signature from "XXX <xxx@apache.org>"
 ```
 
 #### 2.3 检查sha512哈希
@@ -102,10 +102,10 @@ for i in *.tar.gz; do echo $i; sha512sum --check  $i.sha512; done
 
 #### 2.4 检查二进制包
 
-解压缩  `apache-hertzbeat-${release.version}-incubating-bin.tar.gz`
+解压缩  `apache-hertzbeat-${release_version}-bin.tar.gz`
 
 ```shell
-tar -xzvf apache-hertzbeat-${release.version}-incubating-bin.tar.gz
+tar -xzvf apache-hertzbeat-${release_version}-bin.tar.gz
 ```
 
 进行如下检查：
@@ -123,10 +123,10 @@ tar -xzvf apache-hertzbeat-${release.version}-incubating-bin.tar.gz
 
 #### 2.5. 源码编译验证
 
-解压缩 `apache-hertzbeat-`release_version`-incubating-src.tar.gz`
+解压缩 `apache-hertzbeat-${release_version}-src.tar.gz`
 
 ```shell
-cd apache-hertzbeat-`release_version`-incubating-src
+cd apache-hertzbeat-${release_version}-src
 ```
 
 编译源码: [https://hertzbeat.apache.org/docs/community/development/#build-hertzbeat-binary-package](https://hertzbeat.apache.org/docs/community/development/#build-hertzbeat-binary-package)
diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/code-style-and-quality-guide.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/code-style-and-quality-guide.md
index dcd4abf6fe..d3d0d28ffd 100644
--- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/code-style-and-quality-guide.md
+++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.6.x/community/code-style-and-quality-guide.md
@@ -35,7 +35,7 @@ limitations under the License.
    - 新建 `PR` 时请仔细描述此贡献，描述文档和代码同样重要。审阅者可以从描述中，而不仅仅是从代码中，了解问题和解决方案。
    - 勾选是否完成了对应的 Checklist。
 3. 建议一次 `PR` 只包含一个功能/一种修复/一类改进/一种重构/一次清理/一类文档等
-4. 提交消息(英文，小写，无特殊字符)  
+4. 提交消息(英文，小写，无特殊字符)
    消息的提交应遵循与 `PR` 类似的模式：`[feature/bugfix/doc/improve/refactor/bug/cleanup] title`
 
 ## 2 代码检查样式
@@ -631,7 +631,7 @@ public void process(String input) {
      // 忽略声明行。
      List`<User>` userList = getUsersByBatch(1000);
      if (LOG.isDebugEnabled()) {
-        LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); 
+        LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList));
      }
      ```
 
@@ -645,6 +645,5 @@ public void process(String input) {
 
 - [https://site.mockito.org/](https://site.mockito.org/)
 - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/)
-- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/)
 - [https://junit.org/junit5/](https://junit.org/junit5/)
 - [https://streampark.apache.org/](https://streampark.apache.org/)
diff --git a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/code-style-and-quality-guide.md b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/code-style-and-quality-guide.md
index 1c67ee891f..2550e0e822 100644
--- a/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/code-style-and-quality-guide.md
+++ b/home/i18n/zh-cn/docusaurus-plugin-content-docs/version-1.7.x/community/code-style-and-quality-guide.md
@@ -35,7 +35,7 @@ limitations under the License.
    - 新建 `PR` 时请仔细描述此贡献，描述文档和代码同样重要。审阅者可以从描述中，而不仅仅是从代码中，了解问题和解决方案。
    - 勾选是否完成了对应的 Checklist。
 3. 建议一次 `PR` 只包含一个功能/一种修复/一类改进/一种重构/一次清理/一类文档等
-4. 提交消息(英文，小写，无特殊字符)  
+4. 提交消息(英文，小写，无特殊字符)
    消息的提交应遵循与 `PR` 类似的模式：`[feature/bugfix/doc/improve/refactor/bug/cleanup] title`
 
 ## 2 代码检查样式
@@ -631,7 +631,7 @@ public void process(String input) {
      // 忽略声明行。
      List`<User>` userList = getUsersByBatch(1000);
      if (LOG.isDebugEnabled()) {
-        LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); 
+        LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList));
      }
      ```
 
@@ -645,6 +645,5 @@ public void process(String input) {
 
 - [https://site.mockito.org/](https://site.mockito.org/)
 - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/)
-- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/)
 - [https://junit.org/junit5/](https://junit.org/junit5/)
 - [https://streampark.apache.org/](https://streampark.apache.org/)
diff --git a/home/versioned_docs/version-1.6.x/community/code-style-and-quality-guide.md b/home/versioned_docs/version-1.6.x/community/code-style-and-quality-guide.md
index 14e99295f8..8d701b64b3 100644
--- a/home/versioned_docs/version-1.6.x/community/code-style-and-quality-guide.md
+++ b/home/versioned_docs/version-1.6.x/community/code-style-and-quality-guide.md
@@ -27,7 +27,7 @@ limitations under the License.
 
    - After creating a new `PR`, you need to associate the existing corresponding `ISSUE` at the Github Development button on the `PR` page (if there is no corresponding ISSUE, it is recommended to create a new corresponding ISSUE).
 
-   - Title naming format  
+   - Title naming format
      `[feature/bugfix/doc/improve/refactor/bug/cleanup] title`
 
 2. Description
@@ -35,7 +35,7 @@ limitations under the License.
    - Please fill in the `PR` template to describe the contribution. So that the reviewer can understand the problem and solution from the description, rather than just from the code.
    - Check the CheckList
 3. It's recommended that `PR` should be arranged changes such as `cleanup`, `Refactor`, `improve`, and `feature` into separated `PRs`/`Commits`.
-4. Commit message(English, lowercase, no special characters)  
+4. Commit message(English, lowercase, no special characters)
    The commit of messages should follow a pattern similar to the `[feature/bugfix/doc/improve/refactor/bug/cleanup] title`
 
 ## 2 Code Checkstyle
@@ -133,8 +133,8 @@ Error code description:
    ```
 
 2. Pinyin abbreviations are prohibited for variables (excluding nouns such as place names), such as chengdu.
-3. It is recommended to end variable names with a `type`.  
-   For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type).  
+3. It is recommended to end variable names with a `type`.
+   For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type).
    For variables of type `map`, describe the `key` and `value` clearly:
 
    ```java
@@ -142,7 +142,7 @@ Error code description:
    Map<Long, String> userIdNameMap;
    ```
 
-4. That can intuitively know the type and meaning of the variable through its name.  
+4. That can intuitively know the type and meaning of the variable through its name.
    Method names should start with a verb first as follows:
 
    ```java
@@ -320,7 +320,7 @@ to reduce code line depth and improve readability like follows:
           ......
           }
       }
-    
+
       ```
 
   - Positive demo:
@@ -630,7 +630,7 @@ public void process(String input) {
      // ignored declaration lines.
      List`<User>` userList = getUsersByBatch(1000);
      if (LOG.isDebugEnabled()) {
-       LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); 
+       LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList));
      }
      ```
 
@@ -644,6 +644,5 @@ public void process(String input) {
 
 - [https://site.mockito.org/](https://site.mockito.org/)
 - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/)
-- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/)
 - [https://junit.org/junit5/](https://junit.org/junit5/)
 - [https://streampark.apache.org/](https://streampark.apache.org/)
diff --git a/home/versioned_docs/version-1.7.x/community/code-style-and-quality-guide.md b/home/versioned_docs/version-1.7.x/community/code-style-and-quality-guide.md
index f1a489a92f..c9fa91e1c0 100644
--- a/home/versioned_docs/version-1.7.x/community/code-style-and-quality-guide.md
+++ b/home/versioned_docs/version-1.7.x/community/code-style-and-quality-guide.md
@@ -27,7 +27,7 @@ limitations under the License.
 
    - After creating a new `PR`, you need to associate the existing corresponding `ISSUE` at the Github Development button on the `PR` page (if there is no corresponding ISSUE, it is recommended to create a new corresponding ISSUE).
 
-   - Title naming format  
+   - Title naming format
      `[feature/bugfix/doc/improve/refactor/bug/cleanup] title`
 
 2. Description
@@ -35,7 +35,7 @@ limitations under the License.
    - Please fill in the `PR` template to describe the contribution. So that the reviewer can understand the problem and solution from the description, rather than just from the code.
    - Check the CheckList
 3. It's recommended that `PR` should be arranged changes such as `cleanup`, `Refactor`, `improve`, and `feature` into separated `PRs`/`Commits`.
-4. Commit message(English, lowercase, no special characters)  
+4. Commit message(English, lowercase, no special characters)
    The commit of messages should follow a pattern similar to the `[feature/bugfix/doc/improve/refactor/bug/cleanup] title`
 
 ## 2 Code Checkstyle
@@ -133,8 +133,8 @@ Error code description:
    ```
 
 2. Pinyin abbreviations are prohibited for variables (excluding nouns such as place names), such as chengdu.
-3. It is recommended to end variable names with a `type`.  
-   For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type).  
+3. It is recommended to end variable names with a `type`.
+   For variables of type `Collection/List`, take `xxxx` (plural representing multiple elements) or end with `xxxList` (specific type).
    For variables of type `map`, describe the `key` and `value` clearly:
 
    ```java
@@ -142,7 +142,7 @@ Error code description:
    Map<Long, String> userIdNameMap;
    ```
 
-4. That can intuitively know the type and meaning of the variable through its name.  
+4. That can intuitively know the type and meaning of the variable through its name.
    Method names should start with a verb first as follows:
 
    ```java
@@ -320,7 +320,7 @@ to reduce code line depth and improve readability like follows:
           ......
           }
       }
-    
+
       ```
 
   - Positive demo:
@@ -630,7 +630,7 @@ public void process(String input) {
      // ignored declaration lines.
      List`<User>` userList = getUsersByBatch(1000);
      if (LOG.isDebugEnabled()) {
-       LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList)); 
+       LOG.debug("All ids of users: {}", getAllIDsOfUsers(userList));
      }
      ```
 
@@ -644,6 +644,5 @@ public void process(String input) {
 
 - [https://site.mockito.org/](https://site.mockito.org/)
 - [https://alibaba.github.io/p3c/](https://alibaba.github.io/p3c/)
-- [https://rules.sonarsource.com/java/](https://rules.sonarsource.com/java/)
 - [https://junit.org/junit5/](https://junit.org/junit5/)
 - [https://streampark.apache.org/](https://streampark.apache.org/)
diff --git a/script/ci/link_check.json b/script/ci/link_check.json
index 5dce366d4d..deae2430c1 100644
--- a/script/ci/link_check.json
+++ b/script/ci/link_check.json
@@ -19,6 +19,7 @@
     200,
     400,
     401,
-    403
+    403,
+    429
   ]
 }