diff --git a/en/application-dev/connectivity/Readme-EN.md b/en/application-dev/connectivity/Readme-EN.md
index b4c7a479e2492fb0ba10f359cca48e7f03dad2ff..bb544165e5f8ac20efbdea22fcfc453d929f614b 100755
--- a/en/application-dev/connectivity/Readme-EN.md
+++ b/en/application-dev/connectivity/Readme-EN.md
@@ -1,8 +1,9 @@
 # Connectivity
 
--   [IPC & RPC](ipc-rpc.md)
+-   [IPC & RPC]
     -   [IPC & RPC Overview](ipc-rpc-overview.md)  
-    -   [IPC & RPC Development Guidelines](ipc-rpc-development-guideline.md) 
+	
+    -   [IPC & RPC Development](ipc-rpc-development-guideline.md) 
     
     -   [Subscribing to State Changes of a Remote Object](subscribe-remote-state.md)  
 
diff --git a/en/application-dev/connectivity/ipc-rpc-development-guideline.md b/en/application-dev/connectivity/ipc-rpc-development-guideline.md
index 213f8be2622ec55e2cbca35bad1eadbe6ccc2377..a0107dabe7b716b4f7fe2c163c8f48970337959d 100644
--- a/en/application-dev/connectivity/ipc-rpc-development-guideline.md
+++ b/en/application-dev/connectivity/ipc-rpc-development-guideline.md
@@ -1,4 +1,4 @@
-# IPC & RPC Development Guidelines<a name="EN-US_TOPIC_0000001103710988"></a>
+# IPC & RPC Development<a name="EN-US_TOPIC_0000001103710988"></a>
 
 ## When to Use<a name="section18502174174019"></a>
 
diff --git a/en/application-dev/reference/apis/js-apis-bluetooth.md b/en/application-dev/reference/apis/js-apis-bluetooth.md
index 947a2723837dc43af7a7b4473538931c1b17e009..b92f7daa15cc0d5a2a1cbec123be36b4f0f8fdaa 100644
--- a/en/application-dev/reference/apis/js-apis-bluetooth.md
+++ b/en/application-dev/reference/apis/js-apis-bluetooth.md
@@ -1243,7 +1243,7 @@ Obtains the connection status of the profile.
 |                                                   |                         |
 | ------------------------------------------------- | ----------------------- |
 | Type                                              | Description                    |
-| [ProfileConnectionState](#profileconnectionState) | Profile connection state obtained. |
+| [ProfileConnectionState](#profileconnectionstate) | Profile connection state obtained. |
 
 
 ## A2dpSourceProfile
diff --git a/en/application-dev/security/accesstoken-overview.md b/en/application-dev/security/accesstoken-overview.md
index f47160a45f7cc0489bd7c8d99d36cf3e775cad6d..8a92f74f8dd1803a144e6aad9e193005b4e3a8e9 100644
--- a/en/application-dev/security/accesstoken-overview.md
+++ b/en/application-dev/security/accesstoken-overview.md
@@ -110,7 +110,7 @@ The Access Control List (ACL) makes low-level apps to have high-level permission
 
 The APL of app A is normal. App A needs to have permission B (system_basic level) and permission C (normal level). In this case, you can use the ACL to grant permission B to app A.
 
-For details, see [Using the ACL](#usingacl).
+For details, see [Using the ACL](#usingtheacl).
 
 ## Permission Authorization Modes
 
@@ -128,7 +128,7 @@ Permissions can be classified into the following types based on the authorizatio
 
     This type of permissions must be declared in the app installation package and authorized by users dynamically during the running of the app. The app has the permission only after user authorization.
 
-    For example, in the [Permission List](#permissionlist), the permissions for the microphone and camera are user_grant permissions. The list provides reasons for using the permissions.
+    For example, in the [Permission List](#permission-list), the permissions for the microphone and camera are user_grant permissions. The list provides reasons for using the permissions.
 
     The user_grant permission list must also be presented on the details page of the app store.
 
@@ -166,7 +166,7 @@ The procedure is as follows:
 
 If the permission required by an app has higher level than the app's APL, you can use the ACL to grant the permissions required.
 
-In addition to the preceding [authorization processes](#authorizationprocesses), you need to declare the ACL.
+In addition to the preceding [authorization processes](#authorization-processes), you need to declare the ACL.
 
 In addition to declaring the required permissions in the **config.json** file, you must declare the high-level permissions in the app's [profile](accesstoken-guidelines.md). The subsequent steps remain unchanged.