diff --git a/en/application-dev/ability/context-userguide.md b/en/application-dev/ability/context-userguide.md index c7447fde5764729f2592321460e03fc07218465c..091710724717444022fce17442b0b4d444996459 100644 --- a/en/application-dev/ability/context-userguide.md +++ b/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 diff --git a/en/application-dev/dfx/hitracemeter-guidelines.md b/en/application-dev/dfx/hitracemeter-guidelines.md index e7e97631c240bb42358d3b0b630a92094f34bcfc..db5ebd75831bfd16fd66e5818bac2586c2b4cf7d 100644 --- a/en/application-dev/dfx/hitracemeter-guidelines.md +++ b/en/application-dev/dfx/hitracemeter-guidelines.md @@ -5,8 +5,8 @@ HiTraceMeter provides APIs for system performance tracing. You can call the APIs provided by HiTraceMeter module in your own service logic to effectively track service processes and check the system performance. ## 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/ui/figures/en-us_image_tab.gif b/en/application-dev/ui/figures/en-us_image_tab.gif new file mode 100644 index 0000000000000000000000000000000000000000..fde104516f23c4dcc56b3c9f54334d7ee40925a6 Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_tab.gif differ diff --git a/en/contribute/OpenHarmony-hdf-coding-guide.md b/en/contribute/OpenHarmony-hdf-coding-guide.md index 84deab62a8cea60e9cd9febfe50ab8df0b3dc2f7..c06bce8243da5092c8d2f7987c11c7d7ffe7e9b0 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. -![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. diff --git a/en/device-dev/guide/device-iotcamera-control-example.md b/en/device-dev/guide/device-iotcamera-control-example.md index 0d2fbf23bf92862441b826088fbc42b55ba3beea..0519ebb57b512c8572787fd53f2538b68208f867 100644 --- a/en/device-dev/guide/device-iotcamera-control-example.md +++ b/en/device-dev/guide/device-iotcamera-control-example.md @@ -1,6 +1,6 @@ # Use Case -- 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**. diff --git a/en/device-dev/guide/device-wlan-led-control.md b/en/device-dev/guide/device-wlan-led-control.md index 08fa2a01992eb40a3cc7927a3ec50510f48dbdae..15ff2cfe40a1fd98fbac176a967d5baec07b21da 100644 --- a/en/device-dev/guide/device-wlan-led-control.md +++ b/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 -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. diff --git a/en/device-dev/quick-start/quickstart-lite-package-directory.md b/en/device-dev/quick-start/quickstart-lite-package-directory.md index 78fee5a65bc346220534309249b4b2cb19255d7c..9b60a97bd82f0d53d4eb9d433677a173b9d35037 100644 --- a/en/device-dev/quick-start/quickstart-lite-package-directory.md +++ b/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) diff --git a/en/device-dev/subsystems/subsys-boot-overview.md b/en/device-dev/subsystems/subsys-boot-overview.md index 35ac22931c29e64bd85659655148b924c1cb09fe..40c6bbef8b3bf45d5082e4fc4af1a00cdca59c6c 100644 --- a/en/device-dev/subsystems/subsys-boot-overview.md +++ b/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: diff --git a/en/readme/common-event-notification.md b/en/readme/common-event-notification.md index 9494b3d2eef1fe66272faa4be5bdbfd850cb581a..cd92d60394f4b8c8efd9da9a71cbdebc5ea1c47a 100644 --- a/en/readme/common-event-notification.md +++ b/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