!4563 更正链接错误

Merge pull request !4563 from wusongqing/E0528

en/application-dev/ability/context-userguide.md

@@ -213,17 +213,9 @@ export default class ServiceExtAbility extends ServiceExtensionAbility {
 
 ```
 
-**d.ts statement**
-
-https://gitee.com/openharmony/interface_sdk-js/blob/master/api/application/ServiceExtensionContext.d.ts
-
 ### application/FormExtensionContext
 
-For details, see [FormExtensionContext](/en/application-dev/reference/apis/js-apis-formextensioncontext.md)
-
-**d.ts statement**
-
-https://gitee.com/openharmony/interface_sdk-js/blob/master/api/application/FormExtensionContext.d.ts
+For details, see [FormExtensionContext](../reference/apis/js-apis-formextensioncontext.md).
 
 ## FAQs
 

en/application-dev/dfx/hitracemeter-guidelines.md

@@ -6,7 +6,7 @@ HiTraceMeter provides APIs for system performance tracing. You can call the APIs
 
 ## 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**
 

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.
 
-![HDFDriverModel.png]( ../device-dev/driver/figures/HDFDriverModel.png)
+![HDFDriverModel.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.
 

en/device-dev/guide/device-iotcamera-control-example.md

 # Use Case<a name="EN-US_TOPIC_0000001055686082"></a>
 
--   For details about the development board, compilation, burning, and image running, see  [Hi3518 Development Board](../quick-start/quickstart-lite-introduction-hi3518.md#section14815247616). A compilation result file of sample code is stored in  **out/ipcamera\_hi3518ev300/dev\_tools/bin/camera\_sample**. You can copy the file to a TF card, or modify the compilation script of  **camera\_sample**  to copy the result to  **rootfs.img**.
+-   For details about the development board, compilation, burning, and image running, see  [Hi3518 Development Board](../quick-start/quickstart-lite-overview.md). A compilation result file of sample code is stored in  **out/ipcamera\_hi3518ev300/dev\_tools/bin/camera\_sample**. You can copy the file to a TF card, or modify the compilation script of  **camera\_sample**  to copy the result to  **rootfs.img**.
 
     Modify  **output\_dir**  in  **applications/sample/camera/media/BUILD.gn**.
 

en/device-dev/guide/device-wlan-led-control.md

@@ -97,7 +97,7 @@ Based on the Hi3861 platform, the OpenHarmony WLAN module provides abundant peri
 
 ## Verification<a name="section1949121910344"></a>
 
-For details about the compilation and burning processes, see  [Building Source Code](../quick-start/quickstart-lite-steps-hi3861-connection.md#section191121332125319)  and  [Burning Images](../quick-start/quickstart-lite-steps-hi3861-connection.md#section3288165814218)  in the  _Getting Started with Hi3861_.
+For details about the compilation and burning processes, see [Building](../quick-start/quickstart-lite-steps-hi3861-building.md) and [Burning](../quick-start/quickstart-lite-steps-hi3861-burn.md) in the  _Getting Started with Hi3861_.
 
 After the preceding two steps are complete, press the  **RST**  button to reset the module. If the LED blinks periodically as expected, the verification is passed.
 

en/device-dev/quick-start/quickstart-lite-package-directory.md

@@ -9,7 +9,7 @@
         - [Burning](quickstart-lite-steps-hi3861-burn.md)
         - [Networking](quickstart-lite-steps-hi3861-netconfig.md)
         - [Debugging and Verification](quickstart-lite-steps-hi3861-debug.md)
-        - [Running](quickstart-lite-steps-hi3816-running.md)
+        - [Running](quickstart-lite-steps-hi3861-running.md)
     - Hi3516 Development Board
         - [Setting Up the Hi3516 Development Board Environment](quickstart-lite-steps-hi3516-setting.md)
         - [Writing a Hello World Program](quickstart-lite-steps-hi3516-application-framework.md)

en/device-dev/subsystems/subsys-boot-overview.md

@@ -4,7 +4,7 @@
 
 The following figure shows the context structure of the Startup subsystem.
 
-![](figure/The-following-figure-shows-the-context-structure-of-the-Startup-subsystem.png)
+![](figure/context-structure-of-the-Startup-subsystem.png)
 
 Upon completion of system power-on and kernel loading, system services and applications are started as follows:
 

en/readme/common-event-notification.md

@@ -14,7 +14,7 @@ Each application can subscribe to common events as required. After your applicat
 
 ### Architecture
 
-![]( figures/cesfwk_architecture_diagram.png "CES Architecture")
+![](figures/cesfwk_architecture_diagram.png "CES Architecture")
 
 ## Directory Structure