diff --git a/en/application-dev/dfx/hitracemeter-guidelines.md b/en/application-dev/dfx/hitracemeter-guidelines.md
index 3244aa9356bbcd3748594061a3752fad8aa3d3f3..3adf91286aaf410d7862c60320878e57acb359e8 100644
--- a/en/application-dev/dfx/hitracemeter-guidelines.md
+++ b/en/application-dev/dfx/hitracemeter-guidelines.md
@@ -21,7 +21,7 @@ Due to the asynchronous I/O feature of JS, the hiTraceMeter module provides only
 
 ## Available APIs
 
-The performance tracing APIs are provided by the **hiTraceMeter** module. For details, see [API Reference](../reference/apis/js-apis-hitracemeter.md).
+The performance tracing APIs are provided by the **hiTraceMeter** module. For details, see [API Reference]( ../reference/apis/js-apis-hitracemeter.md).
 
 **APIs for performance tracing**
 
diff --git a/en/application-dev/reference/apis/js-apis-distributedMissionManager.md b/en/application-dev/reference/apis/js-apis-distributedMissionManager.md
index 97bba800fdf3549c1e4b33bded39f481f98006ab..506b940eae2f206b9a1bb5a10a39350abcd99753 100644
--- a/en/application-dev/reference/apis/js-apis-distributedMissionManager.md
+++ b/en/application-dev/reference/apis/js-apis-distributedMissionManager.md
@@ -368,8 +368,8 @@ Continues a mission on a remote device. This API uses an asynchronous callback t
 
 | Name      | Type                                     | Mandatory  | Description   |
 | --------- | --------------------------------------- | ---- | ----- |
-| parameter | [ContinueDeviceInfo](js-apis-inner-application-continueDeviceInfo.md) | Yes   | Parameters required for mission continuation.|
-| options | [ContinueCallback](js-apis-inner-application-continueCallback.md) | Yes   | Callback invoked when the mission continuation is complete.|
+| parameter | [ContinueDeviceInfo](#js-apis-inner-application-continueDeviceInfo.md) | Yes   | Parameters required for mission continuation.|
+| options | [ContinueCallback](#js-apis-inner-application-continueCallback.md) | Yes   | Callback invoked when the mission continuation is complete.|
 | callback | AsyncCallback<void> | Yes   | Callback used to return the result.|
 
 **Error codes**
@@ -426,8 +426,8 @@ Continues a mission on a remote device. This API uses a promise to return the re
 
 | Name      | Type                                     | Mandatory  | Description   |
 | --------- | --------------------------------------- | ---- | ----- |
-| parameter | [ContinueDeviceInfo](js-apis-inner-application-continueDeviceInfo.md) | Yes   | Parameters required for mission continuation.|
-| options | [ContinueCallback](js-apis-inner-application-continueCallback.md) | Yes   | Callback invoked when the mission continuation is complete.|
+| parameter | [ContinueDeviceInfo](#js-apis-inner-application-continueDeviceInfo.md) | Yes   | Parameters required for mission continuation.|
+| options | [ContinueCallback](#js-apis-inner-application-continueCallback.md) | Yes   | Callback invoked when the mission continuation is complete.|
 
 **Return value**
 
diff --git a/en/contribute/OpenHarmony-hdf-coding-guide.md b/en/contribute/OpenHarmony-hdf-coding-guide.md
index 276910b4a2a02a608e3b8a5e39deef2f0c8d9009..2349d0148c5b4c2bd3128afbe5e4b5f026ae5222 100644
--- a/en/contribute/OpenHarmony-hdf-coding-guide.md
+++ b/en/contribute/OpenHarmony-hdf-coding-guide.md
@@ -190,7 +190,7 @@ root {
 
 [Description] The HDF places the same type of devices in the same host. You can develop and deploy the driver functionalities of the host by layer, so that one driver has multiple nodes. The following figure shows the HDF driver model.
 
-![hdf-driver-model.png](../device-dev/driver/figures/hdf-driver-model.png)
+![hdf-driver-model.png]( ../device-dev/driver/figures/hdf-driver-model.png)
 
 Place devices of the same type in the same host. When adding a device, check whether the host of the same type already exists. If such a host already exists, configure the device in the host. Do not configure the same host again. A device belongs to only one driver. Therefore, do not configure the same device in different hosts.
 
diff --git a/en/release-notes/OpenHarmony-v3.2-beta5.md b/en/release-notes/OpenHarmony-v3.2-beta5.md
index b0da1a6421cf545a3d7a9f124786894ae2225f42..3dd8c303fa230e852ccb018b17dd0edf0fc63056 100644
--- a/en/release-notes/OpenHarmony-v3.2-beta5.md
+++ b/en/release-notes/OpenHarmony-v3.2-beta5.md
@@ -139,7 +139,7 @@ This version has the following updates to OpenHarmony 3.2 Beta4.
 
 From this version on, only the public SDK is released. You can obtain the public SDK from the mirror or download it from DevEco Studio for your application development.
 
-To use the full SDK that contains system APIs, you must download the full code, compile and build an SDK file, and switch to the full SDK on DevEco Studio. For details about how to compile the full SDK using the source code, see [Full SDK Compilation Guide](../application-dev/faqs/full-sdk-compile-guide.md).
+To use the full SDK that contains system APIs, you must download the full code, compile and build an SDK file, and switch to the full SDK on DevEco Studio. For details about how to compile the full SDK using the source code, see [Full SDK Compilation Guide](../application-dev/quick-start/full-sdk-compile-guide.md).
 
 
 ### Feature Updates
@@ -164,7 +164,7 @@ To use the full SDK that contains system APIs, you must download the full code,
 
 For details about the API changes, see [API Differences](api-diff/v3.2-beta5/Readme-EN.md).
 
-
+For details about the API changes of each subsystem, see [Changelogs](changelogs/v3.2-beta5/Readme-EN.md).
 
 ### Chip and Development Board Adaptation