diff --git a/docs/en/devmaster_usage.md b/docs/en/devmaster_usage.md
index ac3fc1cf5be0cd8a5a267010a56edb651ffb3ecd..251d9beea4429e96ea1e490286c0ebac64e72df3 100644
--- a/docs/en/devmaster_usage.md
+++ b/docs/en/devmaster_usage.md
@@ -106,13 +106,13 @@ Command options:
 
 devmaster rules consist of a group of rule files. After the devmaster daemon is started, it loads the rule files in lexicographic order based on the rule path specified in the configuration file.
 
-> ![Note](./public_sys-resources/icon-note.gif)**Note:**
+> [!Note]Note
 >
 > After adding, deleting, or modifying a rule, you need to restart devmaster for the rule to take effect.
 
 ### Rule Examples
 
-The following describes several common rule examples. For details about the rule syntax, see the [devmaster manual](http://sysmaster.online/man/exts/devmaster/devmaster/).
+The following describes several common rule examples.
 
 #### Example 1: Creating a Soft Link for a Block Device
 
@@ -209,10 +209,9 @@ The following uses the **ens33** NIC as an example to test the effect of the NIC
     # ip link set ens33 up
     ```
 
-> ![Note](./public_sys-resources/icon-note.gif)**Note:**
+> [!Note]Note
 >
 > An activated NIC cannot be renamed. You need to bring it offline first. In addition, the renaming rule of devmaster takes effect only in the **add** event of the NIC.
->
 
 #### Example 3: Modifying the User Permissions on a Device Node
 
@@ -250,5 +249,3 @@ devmaster provides the following default NIC configurations:
 The NIC configuration file contains the **\[Match]** matching section and **\[Link]** control section. Each section contains several configuration items. The configuration items in the **\[Match]** section are used to match NICs. When a NIC meets all matching conditions, all configuration items in the **\[Link]** section are applied to the NIC, for example, setting the NIC naming style and adjusting NIC parameters.
 
 The preceding default NIC configuration indicates that the configuration takes effect on all NICs and checks the NIC naming styles of the **onboard**, **slot**, and **path** styles in sequence. If an available style is found, the NIC is named in this style.
-
-For details about the NIC configuration, see the [devmaster manual](http://sysmaster.online/man/exts/devmaster/netif_config/#1).
diff --git a/docs/en/sysmaster_usage.md b/docs/en/sysmaster_usage.md
index d0ae28310f5d39c1cb5eb17227aa47cb792652b7..6b5651e01ee991527593576eb2ddc9c0e2a48ba9 100644
--- a/docs/en/sysmaster_usage.md
+++ b/docs/en/sysmaster_usage.md
@@ -5,8 +5,6 @@ This section provides examples on how to use sysmaster, including:
 * service unit configuration file creation
 * unit service management operations, such as starting, stopping, and viewing services
 
-For more, see the [sysMaster official manual](http://sysmaster.online/man/all/).
-
 ## Unit Configuration File Creation
 
 You can create unit configuration files in the **/usr/lib/sysmaster/system/** directory.
diff --git a/docs/zh/devmaster_usage.md b/docs/zh/devmaster_usage.md
index 38b96356aa7cda7957eff2d2b58d0aba07148d5f..abcd681b74e2855ae684d94a2627bfa8a21c4941 100644
--- a/docs/zh/devmaster_usage.md
+++ b/docs/zh/devmaster_usage.md
@@ -111,7 +111,7 @@
 
 ### 常用规则案例
 
-以下介绍几种常见的规则应用案例，规则语法详见官方文档中的[devmaster手册](http://sysmaster.online/man/exts/devmaster/devmaster/)。
+以下介绍几种常见的规则应用案例。
 
 #### 示例1: 创建块设备软链接
 
@@ -247,5 +247,3 @@
 网卡配置文件中包含 `[Match]`匹配节和 `[Link]`控制节，每节中包含若干配置项。匹配节的配置项用于匹配网卡设备，当网卡满足所有匹配条件时，将控制节中的所有配置项作用在网卡上，比如设置网卡名选取策略、调整网卡参数等等。
 
 以上列举的默认网卡配置表示将该配置作用在所有网卡设备上，并依次检查 `onboard`、`slot`和 `path`风格的网卡命名风格，如果找到一个可用的风格，就以该风格对网卡进行命名。
-
-网卡配置的详细说明可以参考 `sysMaster`官方手册中的[devmaster手册](http://sysmaster.online/man/exts/devmaster/netif_config/#1)。