Merge branch 'master' of gitee.com:openharmony/docs into TR-7138

Signed-off-by: Nester.zhou <ester.zhou@huawei.com>

CODEOWNERS

@@ -24,11 +24,16 @@ zh-cn/device-dev/driver/ @li-yan339
 zh-cn/device-dev/get-code/ @li-yan339
 zh-cn/device-dev/hpm-part/ @duangavin123_admin
 zh-cn/device-dev/reference/hdi-apis/ @li-yan339
-zh-cn/device-dev/subsystems/subsys-build-mini-lite.md @Austin23
-zh-cn/device-dev/subsystems/subsys-build-standard-large.md @Austin23
-zh-cn/device-dev/subsystems/subsys-build-gn-coding-style-and-best-practice.md @Austin23
-zh-cn/device-dev/subsystems/subsys-build-gn-kconfig-visual-config-guid.md @Austin23
-zh-cn/device-dev/subsystems/subsys-build-gn-hap-compilation-guide.md @Austin23
+zh-cn/device-dev/quick-start/quickstart-standard-env-setup.md @li-yan339 @chenmudan
+zh-cn/device-dev/quick-start/quickstart-lite-env-setup.md @li-yan339 @chenmudan
+zh-cn/device-dev/porting/porting-thirdparty-overview.md @Austin23 @chenmudan
+zh-cn/device-dev/porting/porting-thirdparty-makefile.md @Austin23 @chenmudan
+zh-cn/device-dev/porting/porting-thirdparty-cmake.md @Austin23 @chenmudan
+zh-cn/device-dev/subsystems/subsys-build-mini-lite.md @Austin23 @chenmudan
+zh-cn/device-dev/subsystems/subsys-build-standard-large.md @Austin23 @chenmudan
+zh-cn/device-dev/subsystems/subsys-build-gn-coding-style-and-best-practice.md @Austin23 @chenmudan
+zh-cn/device-dev/subsystems/subsys-build-gn-kconfig-visual-config-guid.md @Austin23 @chenmudan
+zh-cn/device-dev/subsystems/subsys-build-gn-hap-compilation-guide.md @Austin23 @chenmudan
 zh-cn/device-dev/subsystems/subsys-remote-start.md @duangavin123_admin
 zh-cn/device-dev/subsystems/subsys-graphics-overview.md @duangavin123_admin
 zh-cn/device-dev/subsystems/subsys-graphics-container-guide.md @duangavin123_admin
@@ -46,7 +51,7 @@ zh-cn/device-dev/subsystems/subsys-utils-overview.md @Austin23
 zh-cn/device-dev/subsystems/subsys-utils-guide.md @Austin23
 zh-cn/device-dev/subsystems/subsys-utils-faqs.md @Austin23
 zh-cn/device-dev/subsystems/subsys-aiframework-guide.md @Austin23
-zh-cn/device-dev/subsystems/subsys-aiframework-envbuild.md @Austin23
+zh-cn/device-dev/subsystems/subsys-aiframework-envbuild.md @Austin23 
 zh-cn/device-dev/subsystems/subsys-aiframework-tech-codemanage.md @Austin23
 zh-cn/device-dev/subsystems/subsys-aiframework-tech-name.md @Austin23
 zh-cn/device-dev/subsystems/subsys-aiframework-tech-interface.md @Austin23

README_zh.md

@@ -18,7 +18,7 @@
 
  - master：最新开发版本。  
 
- - OpenHarmony 3.2 Beta1版本：点击[此处](zh-cn/release-notes/OpenHarmony-v3.2-beta1.md)了解版本详情。
+ - OpenHarmony 3.2 Beta2版本：点击[此处](zh-cn/release-notes/OpenHarmony-v3.2-beta2.md)了解版本详情。
 
  - OpenHarmony 3.1 Release版本：点击[此处](zh-cn/release-notes/OpenHarmony-v3.1-release.md)了解版本详情。
 

en/application-dev/ability/stage-ability.md

@@ -78,29 +78,29 @@ To create Page abilities for an application in the stage model, you must impleme
     onCreate(want, launchParam) {
         console.log("MainAbility onCreate")
     }
-   
+
     onDestroy() {
         console.log("MainAbility onDestroy")
     }
-   
+
     onWindowStageCreate(windowStage) {
         console.log("MainAbility onWindowStageCreate")
-   
+
         windowStage.loadContent("pages/index").then((data) => {
             console.log("MainAbility load content succeed with data: " + JSON.stringify(data))
         }).catch((error) => {
             console.error("MainAbility load content failed with error: " + JSON.stringify(error))
         })
     }
-   
+
     onWindowStageDestroy() {
         console.log("MainAbility onWindowStageDestroy")
     }
-   
+
     onForeground() {
         console.log("MainAbility onForeground")
     }
-   
+
     onBackground() {
         console.log("MainAbility onBackground")
     }
@@ -300,7 +300,7 @@ export default class MainAbility extends Ability {
 
 Obtain the `want` parameter that contains the page information from the custom component and process the route based on the URI.
 ```ts
-import router from '@system.router'
+import router from '@ohos.router'
 
 @Entry
 @Component

en/application-dev/application-dev-guide-for-gitee.md

@@ -54,8 +54,10 @@ To make you better understand how functions work together and jumpstart your app
 API references encompass all components and APIs available in OpenHarmony, helping you use and integrate APIs more effectively.
 
 They are organized as follows:
+
+- [Component Reference (TypeScript-based Declarative Development Paradigm)](reference/arkui-ts/Readme-EN.md)
+
 -   [Component Reference (JavaScript-based Web-like Development Paradigm)](reference/arkui-js/Readme-EN.md)
--   [Component Reference (TypeScript-based Declarative Development Paradigm)](reference/arkui-ts/Readme-EN.md)
 -   APIs
     -   [JS and TS APIs](reference/apis/Readme-EN.md)
     -   Native APIs

en/application-dev/internationalization/intl-guidelines.md

@@ -292,7 +292,7 @@ Use [RelativeTimeFormat](../reference/apis/js-apis-intl.md) APIs to format the r
    Alternatively, use your own locale and formatting parameters to create a **RelativeTimeFormat** object. Formatting parameters are optional. For a full list of formatting parameters, see [ RelativeTimeFormatInputOptions](../reference/apis/js-apis-intl.md).
    
    ```
-   var relativeTimeFormat = new intl.RelativeTimeFormat("zh-CN", {numeric: "always", style: "long"};
+   var relativeTimeFormat = new intl.RelativeTimeFormat("zh-CN", {numeric: "always", style: "long"});
    ```
 
 2. Format the relative time.<br>

en/application-dev/reference/Readme-EN.md

 # Development References
 
--   [JavaScript-based Web-like Development Paradigm](arkui-js/Readme-EN.md)
--   [TypeScript-based Declarative Development Paradigm](arkui-ts/Readme-EN.md)
+-   [Component Reference(TypeScript-based Declarative Development Paradigm)](arkui-ts/Readme-EN.md)
+-   [Component Reference(JavaScript-based Web-like Development Paradigm)](arkui-js/Readme-EN.md)
 -   [APIs](apis/Readme-EN.md)
-    
+
     -   [JS (eTS Included) APIs](apis/Readme-EN.md)
     -   Native APIs
         -   [Standard Library](native-lib/third_party_libc/musl.md)

en/application-dev/reference/apis/js-apis-application-abilityManager.md

+# AbilityManager
+
+The **AbilityManager** module provides APIs for obtaining, adding, and modifying ability running information and state information.
+
+> **NOTE**
+>
+> The initial APIs of this module are supported since API version 8. Newly added APIs will be marked with a superscript to indicate their earliest API version. 
+> The APIs of this module are system APIs and cannot be called by third-party applications.
+
+# Modules to Import
+
+```js
+import AbilityManager from '@ohos.application.abilityManager'
+```
+
+## AbilityState
+
+Enumerates the ability states.
+
+**System capability**: SystemCapability.Ability.AbilityRuntime.Core
+
+| Name| Value| Description| 
+| -------- | -------- | -------- |
+| INITIAL | 0 | The ability is in the initial state.| 
+| FOREGROUND | 9 | The ability is in the foreground state. | 
+| BACKGROUND | 10 | The ability is in the background state. | 
+| FOREGROUNDING | 11 | The ability is in the foregrounding state. | 
+| BACKGROUNDING | 12 | The ability is in the backgrounding state. | 
+
+## updateConfiguration
+
+updateConfiguration(config: Configuration, callback: AsyncCallback\<void>): void
+
+Updates the configuration. This API uses an asynchronous callback to return the result.
+
+**Permission required**: ohos.permission.UPDATE_CONFIGURATION
+
+**System capability**: SystemCapability.Ability.AbilityRuntime.Core
+ 
+**Parameters**
+
+| Name       | Type                                      | Mandatory  | Description            |
+| --------- | ---------------------------------------- | ---- | -------------- |
+| config    | Configuration                            | Yes   | New configuration.|
+| callback  | AsyncCallback\<void>                   | Yes   | Callback used to return the result.     |
+
+**Example**
+
+```js
+import abilitymanager from '@ohos.application.abilityManager';
+
+var config = {
+  language: 'chinese' 
+}
+
+abilitymanager.updateConfiguration(config, () => {
+    console.log('------------ updateConfiguration -----------');
+})
+```
+
+## updateConfiguration
+
+updateConfiguration(config: Configuration): Promise\<void>
+
+Updates the configuration. This API uses a promise to return the result.
+
+**Permission required**: ohos.permission.UPDATE_CONFIGURATION
+
+**System capability**: SystemCapability.Ability.AbilityRuntime.Core
+
+**Parameters**
+
+| Name       | Type                                      | Mandatory  | Description            |
+| --------- | ---------------------------------------- | ---- | -------------- |
+| config    | Configuration                            | Yes   | New configuration.|
+
+**Return value**
+
+| Type                                      | Description     |
+| ---------------------------------------- | ------- |
+| Promise\<void> | Promise used to return the result.|
+
+**Example**
+
+```js
+import abilitymanager from '@ohos.application.abilityManager';
+
+var config = {
+  language: 'chinese' 
+}
+
+abilitymanager.updateConfiguration(config).then(() => {
+  console.log('updateConfiguration success');
+}).catch((err) => {
+  console.log('updateConfiguration fail');
+})
+```
+
+## getAbilityRunningInfos
+
+getAbilityRunningInfos(callback: AsyncCallback\<Array\<AbilityRunningInfo>>): void
+
+Obtains the ability running information. This API uses an asynchronous callback to return the result.
+
+**Required permissions**: ohos.permission.GET_RUNNING_INFO
+
+**System capability**: SystemCapability.Ability.AbilityRuntime.Core
+
+**Parameters**
+
+| Name       | Type                                      | Mandatory  | Description            |
+| --------- | ---------------------------------------- | ---- | -------------- |
+| callback  | AsyncCallback\<Array\<AbilityRunningInfo>>  | Yes   | Callback used to return the result.     |
+
+**Example**
+
+```js
+import abilitymanager from '@ohos.application.abilityManager';
+
+abilitymanager.getAbilityRunningInfos((err,data) => { 
+    console.log("getAbilityRunningInfos err: "  + err + " data: " + JSON.stringify(data));
+});
+```
+
+## getAbilityRunningInfos
+
+getAbilityRunningInfos(): Promise\<Array\<AbilityRunningInfo>>
+
+Obtains the ability running information. This API uses a promise to return the result.
+
+**Required permissions**: ohos.permission.GET_RUNNING_INFO
+
+**System capability**: SystemCapability.Ability.AbilityRuntime.Core
+
+**Return value**
+
+| Type                                      | Description     |
+| ---------------------------------------- | ------- |
+| Promise\<Array\<AbilityRunningInfo>> | Promise used to return the result.|
+
+**Example**
+
+```js
+import abilitymanager from '@ohos.application.abilityManager';
+ 
+abilitymanager.getAbilityRunningInfos().then((data) => {
+    console.log("getAbilityRunningInfos  data: " + JSON.stringify(data))
+}).catch((err) => {
+  console.log("getAbilityRunningInfos err: "  + err)
+});
+```
+
+## getExtensionRunningInfos<sup>9+</sup>
+
+getExtensionRunningInfos(upperLimit: number, callback: AsyncCallback\<Array\<ExtensionRunningInfo>>): void
+
+Obtains the extension running information. This API uses an asynchronous callback to return the result.
+
+**Required permissions**: ohos.permission.GET_RUNNING_INFO
+
+**System capability**: SystemCapability.Ability.AbilityRuntime.Core
+
+**Parameters**
+
+| Name       | Type                                      | Mandatory  | Description            |
+| --------- | ---------------------------------------- | ---- | -------------- |
+| upperLimit | number                                   | Yes| Maximum number of messages that can be obtained.|
+| callback  | AsyncCallback\<Array\<AbilityRunningInfo>>  | Yes   | Callback used to return the result.     |
+
+**Example**
+
+```js
+import abilitymanager from '@ohos.application.abilityManager';
+
+var upperLimit = 0;
+
+abilitymanager.getExtensionRunningInfos(upperLimit, (err,data) => { 
+    console.log("getExtensionRunningInfos err: "  + err + " data: " + JSON.stringify(data));
+});
+```
+
+## getExtensionRunningInfos<sup>9+</sup>
+
+getExtensionRunningInfos(upperLimit: number): Promise\<Array\<ExtensionRunningInfo>>
+
+Obtains the extension running information. This API uses a promise to return the result.
+ 
+**Required permissions**: ohos.permission.GET_RUNNING_INFO
+
+**System capability**: SystemCapability.Ability.AbilityRuntime.Core
+
+**Parameters**
+
+| Name       | Type                                      | Mandatory  | Description            |
+| --------- | ---------------------------------------- | ---- | -------------- |
+| upperLimit | number                                   | Yes| Maximum number of messages that can be obtained.|
+
+**Return value**
+
+| Type                                      | Description     |
+| ---------------------------------------- | ------- |
+| Promise\<Array\<AbilityRunningInfo>> | Promise used to return the result.|
+
+**Example**
+
+```js
+import abilitymanager from '@ohos.application.abilityManager';
+
+var upperLimit = 0;
+
+abilitymanager.getExtensionRunningInfos(upperLimit).then((data) => {
+  console.log("getAbilityRunningInfos data: " + JSON.stringify(data));
+}).catch((err) => {
+  console.log("getAbilityRunningInfos err: "  + err);
+})
+```
+
+## getTopAbility<sup>9+</sup>
+
+getTopAbility(callback: AsyncCallback\<ElementName>): void;
+
+Obtains the top ability, which is the ability that has the window focus. This API uses an asynchronous callback to return the result.
+
+**System capability**: SystemCapability.Ability.AbilityRuntime.Core
+
+**Parameters**
+
+| Name       | Type                                      | Mandatory  | Description            |
+| --------- | ---------------------------------------- | ---- | -------------- |
+| callback  | AsyncCallback\<ElementName>  | Yes   | Callback used to return the result.     |
+
+**Example**
+
+```js
+import abilitymanager from '@ohos.application.abilityManager';
+
+abilitymanager.getTopAbility((err,data) => { 
+    console.log("getTopAbility err: "  + err + " data: " + JSON.stringify(data));
+});
+```
+
+## getTopAbility<sup>9+</sup>
+
+getTopAbility(): Promise\<ElementName>;
+
+Obtains the top ability, which is the ability that has the window focus. This API uses a promise to return the result.
+ 
+**System capability**: SystemCapability.Ability.AbilityRuntime.Core
+
+**Return value**
+
+| Type                                      | Description     |
+| ---------------------------------------- | ------- |
+| Promise\<ElementName>| Promise used to return the result.|
+
+**Example**
+
+```js
+import abilitymanager from '@ohos.application.abilityManager';
+
+abilitymanager.getTopAbility().then((data) => {
+  console.log("getTopAbility data: " + JSON.stringify(data));
+}).catch((err) => {
+  console.log("getTopAbility err: "  + err);
+})
+```

en/application-dev/reference/apis/js-apis-bundle-ApplicationInfo.md

 # ApplicationInfo
 
+The **ApplicationInfo** module provides application information. Unless otherwise specified, all attributes are obtained through **GET_BUNDLE_DEFAULT**.
+
 > **NOTE**
 >
 > The initial APIs of this module are supported since API version 7. Newly added APIs will be marked with a superscript to indicate their earliest API version.
 
-Provides the application information.
-
 ## ApplicationInfo
 
 **System capability**: SystemCapability.BundleManager.BundleFramework
 
-
-
 | Name                      | Type                                                        | Readable| Writable| Description                                                        |
 | -------------------------- | ------------------------------------------------------------ | ---- | ---- | ------------------------------------------------------------ |
 | name                       | string                                                       | Yes  | No  | Application name.                                              |
@@ -26,16 +24,19 @@ Provides the application information.
 | process                    | string                                                       | Yes  | No  | Process in which the application runs. If this parameter is not set, the bundle name is used.                  |
 | supportedModes             | number                                                       | Yes  | No  | Running modes supported by the application.                                      |
 | moduleSourceDirs           | Array\<string>                                               | Yes  | No  | Relative paths for storing application resources.                                |
-| permissions                | Array\<string>                                               | Yes  | No  | Permissions required for accessing the application.                                      |
+| permissions                | Array\<string>                                               | Yes  | No  | Permissions required for accessing the application.<br>The value is obtained by passing **GET_APPLICATION_INFO_WITH_PERMISSION**.|
 | moduleInfos                | Array\<[ModuleInfo](js-apis-bundle-ModuleInfo.md)>           | Yes  | No  | Application module information.                                          |
 | entryDir                   | string                                                       | Yes  | No  | Path for storing application files.                                      |
 | codePath<sup>8+</sup>      | string                                                       | Yes  | No  | Installation directory of the application.                                          |
-| metaData<sup>8+</sup>      | Map\<string, Array\<[CustomizeData](js-apis-bundle-CustomizeData.md)>> | Yes  | No  | Custom metadata of the application.                                      |
-| metadata<sup>9+</sup>      | Map\<string, Array\<[Metadata](js-apis-bundle-Metadata.md)>> | Yes  | No  | Metadata of the application.                                            |
+| metaData<sup>8+</sup>      | Map\<string, Array\<[CustomizeData](js-apis-bundle-CustomizeData.md)>> | Yes  | No  | Custom metadata of the application.<br>The value is obtained by passing **GET_APPLICATION_INFO_WITH_METADATA**.|
+| metadata<sup>9+</sup>      | Map\<string, Array\<[Metadata](js-apis-bundle-Metadata.md)>> | Yes  | No  | Metadata of the application.<br>The value is obtained by passing **GET_APPLICATION_INFO_WITH_METADATA**.|
 | removable<sup>8+</sup>     | boolean                                                      | Yes  | No  | Whether the application is removable.                                      |
 | accessTokenId<sup>8+</sup> | number                                                       | Yes  | No  | Access token ID of the application.                                     |
 | uid<sup>8+</sup>           | number                                                       | Yes  | No  | UID of the application.                                               |
 | entityType<sup>8+</sup>    | string                                                       | Yes  | No  | Entity type of the application.                                          |
-| fingerprint<sup>9+</sup>   | string                                                       | Yes  | No  | Signing certificate fingerprint of the application, that is, the SHA-256 checksum of the signing certificate that you request for the application.|
+| fingerprint<sup>9+</sup>   | string                                                       | Yes  | No  | Signing certificate fingerprint of the application, that is, the SHA-256 checksum of the signing certificate that you request for the application.<br>The value is obtained by passing **GET_APPLICATION_INFO_WITH_CERTIFICATE_FINGERPRINT**.|
+| iconResource<sup>9+</sup> | [Resource](js-apis-resource-manager.md#resource9) | Yes| No| Icon resource of the application.|
+| labelResource<sup>9+</sup> | [Resource](js-apis-resource-manager.md#resource9) | Yes| No| Label resource of the application.|
+| descriptionResource<sup>9+</sup> | [Resource](js-apis-resource-manager.md#resource9) | Yes| No| Description resource of the application.|
 | appDistributionType<sup>9+</sup>   | string                                                       | Yes  | No  | Distribution type of the application signing certificate. The options are **app_gallery**, **enterprise**, **os_integration**, and **crowdtesting**.   |
 | appProvisionType<sup>9+</sup>   | string                                                       | Yes  | No  | Type of the application signing certificate file. The options are **debug** and **release**.|

en/application-dev/reference/apis/js-apis-http.md

 # Data Request
 
->![](public_sys-resources/icon-note.gif) **NOTE**
+This module provides the HTTP data request capability. An application can initiate a data request over HTTP. Common HTTP methods include **GET**, **POST**, **OPTIONS**, **HEAD**, **PUT**, **DELETE**, **TRACE**, and **CONNECT**.
+
+>**NOTE**
 >
 >The initial APIs of this module are supported since API version 6. Newly added APIs will be marked with a superscript to indicate their earliest API version.
 >
@@ -18,17 +20,17 @@ import http from '@ohos.net.http';
 
 // Each HttpRequest corresponds to an HttpRequestTask object and cannot be reused.
 let httpRequest = http.createHttp();
-// Subscribe to the HTTP response header, which is returned earlier than HttpRequest. You can subscribe to HTTP Response Header events based on service requirements.
-// on('headerReceive', AsyncCallback) will be replaced by on('headersReceive', Callback) in API version 8. 8+
+// Subscribe to the HTTP response header, which is returned earlier than httpRequest. Whether to subscribe to the HTTP response header is up to your decision.
+// on('headerReceive', AsyncCallback) is replaced by on('headersReceive', Callback) since API version 8.
 httpRequest.on('headersReceive', (header) => {
     console.info('header: ' + JSON.stringify(header));
 });
 httpRequest.request(
-    // Set the URL of the HTTP request. You need to define the URL. Set the parameters of the request in extraData.
+    // Customize EXAMPLE_URL on your own. It is up to you whether to add parameters to the URL.
     "EXAMPLE_URL",
     {
         method: http.RequestMethod.POST, // Optional. The default value is http.RequestMethod.GET.
-        // You can add the header field based on service requirements.
+        // You can add header fields based on service requirements.
         header: {
             'Content-Type': 'application/json'
         },
@@ -48,7 +50,7 @@ httpRequest.request(
             console.info('cookies:' + data.cookies); // 8+
         } else {
             console.info('error:' + JSON.stringify(err));
-            // Call the destroy() method to release resources after the call is complete.
+            // Call the destroy() method to release resources after HttpRequest is complete.
             httpRequest.destroy();
         }
     }
@@ -79,7 +81,7 @@ let httpRequest = http.createHttp();
 
 ## HttpRequest
 
-Defines an **HttpRequest** object. Before invoking HttpRequest APIs, you must call [createHttp\(\)](#httpcreatehttp) to create an **HttpRequestTask** object.
+HTTP request task. Before invoking APIs provided by **HttpRequest**, you must call [createHttp\(\)](#httpcreatehttp) to create an **HttpRequestTask** object.
 
 ### request
 
@@ -93,9 +95,9 @@ Initiates an HTTP request to a given URL. This API uses an asynchronous callback
 
 **Parameters**
 
-| Name  | Type                                                   | Mandatory| Description                   |
-| -------- | ------------------------------------------------------- | ---- | ----------------------- |
-| url      | string                                                  | Yes  | URL for initiating an HTTP request.|
+| Name  | Type                                          | Mandatory| Description                   |
+| -------- | ---------------------------------------------- | ---- | ----------------------- |
+| url      | string                                         | Yes  | URL for initiating an HTTP request.|
 | callback | AsyncCallback\<[HttpResponse](#httpresponse)\> | Yes  | Callback used to return the result.             |
 
 **Example**
@@ -169,15 +171,15 @@ Initiates an HTTP request to a given URL. This API uses a promise to return the
 
 **Parameters**
 
-| Name | Type              | Mandatory| Description                                              |
-| ------- | ------------------ | ---- | -------------------------------------------------- |
-| url     | string             | Yes  | URL for initiating an HTTP request.                           |
+| Name | Type              | Mandatory| Description                                           |
+| ------- | ------------------ | ---- | ----------------------------------------------- |
+| url     | string             | Yes  | URL for initiating an HTTP request.                        |
 | options | HttpRequestOptions | Yes  | Request options. For details, see [HttpRequestOptions](#httprequestoptions).|
 
 **Return value**
 
-| Type                 | Description                             |
-| :-------------------- | :-------------------------------- |
+| Type                                  | Description                             |
+| :------------------------------------- | :-------------------------------- |
 | Promise<[HttpResponse](#httpresponse)> | Promise used to return the result.|
 
 
@@ -225,8 +227,7 @@ on\(type: 'headerReceive', callback: AsyncCallback<Object\>\): void
 Registers an observer for HTTP Response Header events.
 
 >![](public_sys-resources/icon-note.gif) **NOTE**
->
-> This API has been deprecated. You are advised to use [on\('headersReceive'\)<sup>8+</sup>](#onheadersreceive8) instead.
+>This API has been deprecated. You are advised to use [on\('headersReceive'\)<sup>8+</sup>](#onheadersreceive8) instead.
 
 **System capability**: SystemCapability.Communication.NetStack
 
@@ -308,7 +309,6 @@ off\(type: 'headersReceive', callback?: Callback<Object\>\): void
 Unregisters the observer for HTTP Response Header events.
 
 >![](public_sys-resources/icon-note.gif) **NOTE**
->
 >You can pass the callback of the **on** function if you want to cancel listening for a certain type of event. If you do not pass the callback, you will cancel listening for all events.
 
 **System capability**: SystemCapability.Communication.NetStack
@@ -355,13 +355,13 @@ Specifies the type and value range of the optional parameters in the HTTP reques
 
 **System capability**: SystemCapability.Communication.NetStack
 
-| Name         | Type                                | Mandatory| Description                                                      |
-| -------------- | ------------------------------------ | ---- | ---------------------------------------------------------- |
-| method         | [RequestMethod](#requestmethod) | No  | Request method.                                                |
+| Name        | Type                                         | Mandatory| Description                                                        |
+| -------------- | --------------------------------------------- | ---- | ------------------------------------------------------------ |
+| method         | [RequestMethod](#requestmethod)               | No  | Request method.                                                  |
 | extraData      | string \| Object  \| ArrayBuffer<sup>8+</sup> | No  | Additional data of the request.<br>- If the HTTP request uses a POST or PUT method, this parameter serves as the content of the HTTP request.<br>- If the HTTP request uses a GET, OPTIONS, DELETE, TRACE, or CONNECT method, this parameter is a supplement to the HTTP request parameters and will be added to the URL when the request is sent.<sup>8+</sup><br>- To pass in a string object, you first need to encode the object on your own.<sup>8+</sup> |
-| header         | Object                               | No  | HTTP request header. The default value is {'Content-Type': 'application/json'}.|
-| readTimeout    | number                               | No  | Read timeout duration. The default value is **60000**, in ms.           |
-| connectTimeout | number                               | No  | Connection timeout interval. The default value is **60000**, in ms.           |
+| header         | Object                                        | No  | HTTP request header. The default value is **{'Content-Type': 'application/json'}**.  |
+| readTimeout    | number                                        | No  | Read timeout duration. The default value is **60000**, in ms.             |
+| connectTimeout | number                                        | No  | Connection timeout interval. The default value is **60000**, in ms.             |
 
 ## RequestMethod
 
@@ -388,13 +388,13 @@ Enumerates the response codes for an HTTP request.
 
 | Name             | Value  | Description                                                        |
 | ----------------- | ---- | ------------------------------------------------------------ |
-| OK                | 200  | "OK." The request has been processed successfully. This return code is generally used for GET and POST requests.                           |
+| OK                | 200  | Request succeeded. The request has been processed successfully. This return code is generally used for GET and POST requests.                           |
 | CREATED           | 201  | "Created." The request has been successfully sent and a new resource is created.                          |
-| ACCEPTED          | 202  | "Accepted." The request has been accepted, but the processing has not been completed.                         |
+| ACCEPTED          | 202  | "Accepted." The request has been accepted, but the processing has not been completed.                        |
 | NOT_AUTHORITATIVE | 203  | "Non-Authoritative Information." The request is successful.                                      |
 | NO_CONTENT        | 204  | "No Content." The server has successfully fulfilled the request but there is no additional content to send in the response payload body.                      |
 | RESET             | 205  | "Reset Content." The server has successfully fulfilled the request and desires that the user agent reset the content.                                                  |
-| PARTIAL           | 206  | "Partial Content." The server has successfully fulfilled the partial GET request for a given resource.                      |
+| PARTIAL           | 206  | "Partial Content." The server has successfully fulfilled the partial GET request for a given resource.                     |
 | MULT_CHOICE       | 300  | "Multiple Choices." The requested resource corresponds to any one of a set of representations.                                                  |
 | MOVED_PERM        | 301  | "Moved Permanently." The requested resource has been assigned a new permanent URI and any future references to this resource will be redirected to this URI.|
 | MOVED_TEMP        | 302  | "Moved Temporarily." The requested resource is moved temporarily to a different URI.                                                  |
@@ -418,7 +418,7 @@ Enumerates the response codes for an HTTP request.
 | REQ_TOO_LONG      | 414  | "Request-URI Too Long." The Request-URI is too long for the server to process.             |
 | UNSUPPORTED_TYPE  | 415  | "Unsupported Media Type." The server is unable to process the media format in the request.                                   |
 | INTERNAL_ERROR    | 500  | "Internal Server Error." The server encounters an unexpected error that prevents it from fulfilling the request.                              |
-| NOT_IMPLEMENTED   | 501  | "Not Implemented." The server does not support the function required to fulfill the request.                       |
+| NOT_IMPLEMENTED   | 501  | "Not Implemented." The server does not support the function required to fulfill the request.                      |
 | BAD_GATEWAY       | 502  | "Bad Gateway." The server acting as a gateway or proxy receives an invalid response from the upstream server.|
 | UNAVAILABLE       | 503  | "Service Unavailable." The server is currently unable to process the request due to a temporary overload or system maintenance.      |
 | GATEWAY_TIMEOUT   | 504  | "Gateway Timeout." The server acting as a gateway or proxy does not receive requests from the remote server within the timeout period.        |
@@ -433,6 +433,17 @@ Defines the response to an HTTP request.
 | Name              | Type                                        | Mandatory| Description                                                        |
 | -------------------- | -------------------------------------------- | ---- | ------------------------------------------------------------ |
 | result               | string \| Object \| ArrayBuffer<sup>8+</sup> | Yes  | Response content returned based on **Content-type** in the response header:<br>- application/json: a string in JSON format. If you want to use specific content in the response, you need to implement parsing of that content.<br>- application/octet-stream: ArrayBuffer<br>- Others: string|
-| responseCode         | [ResponseCode](#responsecode) \| number      | Yes  | Result code for an HTTP request. If the callback function is successfully executed, a result code defined in [ResponseCode](#responsecode) will be returned. Otherwise, an error code will be returned in the **err** field in **AsyncCallback**. The error code can be one of the following:<br>- 200: common error<br>- 202: parameter error<br>- 300: I/O error|
+| responseCode         | [ResponseCode](#responsecode) \| number      | Yes  | Result code for an HTTP request. If the callback function is successfully executed, a result code defined in [ResponseCode](#responsecode) will be returned. Otherwise, an error code will be returned in the **err** field in **AsyncCallback**. For details, see [Error Codes](#error-codes).|
 | header               | Object                                       | Yes  | Response header. The return value is a string in JSON format. If you want to use specific content in the response, you need to implement parsing of that content. Common fields and parsing methods are as follows:<br>- Content-Type: header['Content-Type'];<br>- Status-Line: header['Status-Line'];<br>- Date: header.Date/header['Date'];<br>- Server: header.Server/header['Server'];|
 | cookies<sup>8+</sup> | Array\<string\>                              | Yes  | Cookies returned by the server.                                      |
+
+## Error Codes
+
+| Error Code| Description                                                        |
+| ------ | ------------------------------------------------------------ |
+| -1     | Incorrect parameters.                                                  |
+| 3      | Incorrect URL format.                                               |
+| 4      | Built-in request function, protocol, or option not found during build.                  |
+| 5      | Unable to resolve the proxy.                                              |
+| 6      | Unable to resolve the host.                                              |
+| 7      | Unable to connect to the proxy or host.                                        |

en/application-dev/reference/apis/js-apis-process.md

 # Obtaining Process Information
 
-> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+> **NOTE**
+>
 > The initial APIs of this module are supported since API version 7. Newly added APIs will be marked with a superscript to indicate their earliest API version.
 
 
@@ -409,7 +410,7 @@ This is a system API and cannot be called by third-party applications.
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
 | timeout | number | No| Maximum running time (in ms) of the child process. When the running time of the child process exceeds the value of this parameter, the parent process sends a **killSignal** to the child process to terminate it. The default value is **0**.|
-| killSignal | number  \| string | No| Signal sent to the child process when the running time of a child process exceeds the timeout period. The default value is **SIGTERM**.|
+| killSignal | number \| string | No| Signal sent to the child process when the running time of a child process exceeds the timeout period. The default value is **SIGTERM**.|
 | maxBuffer | number | No| Maximum buffer size for the standard input and output of the child process. When the size is exceeded, the child process will be terminated. The default value is **1024 \* 1024**.|
 
 **Return value**

en/application-dev/reference/apis/js-apis-router.md

@@ -29,7 +29,7 @@ Navigates to a specified page in the application.
 
 
 **Example**
-  ```js
+```js
 router.push({
   url: 'pages/routerpage2',
   params: {
@@ -39,7 +39,7 @@ router.push({
     },
   },
 });
-  ```
+```
 ## router.push<sup>9+</sup>
 
 push(options: RouterOptions, mode: RouterMode): void
@@ -56,7 +56,7 @@ Navigates to a specified page in the application.
 
 
 **Example**
-  ```js
+```js
 router.push({
   url: 'pages/routerpage2/routerpage2',
   params: {
@@ -66,11 +66,11 @@ router.push({
     },
   },
 },router.RouterMode.Standard);
-  ```
+```
 
 ## router.replace
 
-replace(options: RouterOptions, mode?: RouterMode): void
+replace(options: RouterOptions): void
 
 Replaces the current page with another one in the application and destroys the current page.
 
@@ -83,14 +83,14 @@ Replaces the current page with another one in the application and destroys the c
 
 **Example**
 
-  ```js
+```js
 router.replace({
   url: 'pages/detail',
   params: {
     data1: 'message',
   },
 });
-  ```
+```
 
   ## router.replace<sup>9+</sup>
 
@@ -108,14 +108,14 @@ Replaces the current page with another one in the application and destroys the c
 
 **Example**
 
-  ```js
+```js
 router.replace({
   url: 'pages/detail/detail',
   params: {
     data1: 'message',
   },
 }, router.RouterMode.Standard);
-  ```
+```
 
 ## router.back
 
@@ -132,9 +132,9 @@ Returns to the previous page or a specified page.
 
 **Example**
 
-  ```js
-router.back({uri:'pages/detail'});    
-  ```
+```js
+router.back({url:'pages/detail'});    
+```
 
 ## router.clear
 
@@ -146,9 +146,9 @@ Clears all historical pages in the stack and retains only the current page at th
 
 **Example**
 
-  ```js
+```js
 router.clear();    
-  ```
+```
 
 ## router.getLength
 
@@ -164,10 +164,10 @@ Obtains the number of pages in the current stack.
 | string | Number of pages in the stack. The maximum value is **32**.|
 
 **Example**
-  ```js
+```js
 var size = router.getLength();        
 console.log('pages stack size = ' + size);    
-  ```
+```
 
 ## router.getState
 
@@ -242,9 +242,9 @@ Disables the display of a confirm dialog box before returning to the previous pa
 **System capability**: SystemCapability.ArkUI.ArkUI.Full
 
 **Example**
-  ```js
+```js
 router.disableAlertBeforeBackPage();    
-  ```
+```
 
 ##  router.getParams
 
@@ -270,7 +270,7 @@ router.getParams();
 
 Describes the page routing options.
 
-**System capability**: SystemCapability.ArkUI.ArkUI.Full
+**System capability**: SystemCapability.ArkUI.ArkUI.Lite
 
 | Name  | Type  | Mandatory| Description                                                        |
 | ------ | ------ | ---- | ------------------------------------------------------------ |
@@ -314,7 +314,7 @@ export default {
 // detail page
 export default {
   onInit() {
-    console.info('showData1:' + router.getParams().data1);
+    console.info('showData1:' + router.getParams()[data1]);
   }
 }
 ```

en/application-dev/reference/apis/js-apis-url.md

 # URL String Parsing
 
-> **NOTE**<br>
+> **NOTE**
+>
 > The initial APIs of this module are supported since API version 7. Newly added APIs will be marked with a superscript to indicate their earliest API version.
 
 
@@ -25,7 +26,7 @@ Creates a **URLSearchParams** instance.
 
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
-| init | string[][]&nbsp;\|&nbsp;Record&lt;string,&nbsp;string&gt;&nbsp;\|&nbsp;string&nbsp;\|&nbsp;URLSearchParams | No| Input parameter objects, which include the following:<br>- **string[][]**: two-dimensional string array<br>-&nbsp;**Record&lt;string,&nbsp;string&gt;**: list of objects<br>- **string**: string<br>- **URLSearchParams**: object |
+| init | string[][]&nbsp;\|&nbsp;Record&lt;string,&nbsp;string&gt;&nbsp;\|&nbsp;string&nbsp;\|&nbsp;URLSearchParams | No| Input parameter objects, which include the following:<br>- **string[][]**: two-dimensional string array<br>- **Record&lt;string,&nbsp;string&gt;**: list of objects<br>- **string**: string<br>- **URLSearchParams**: object|
 
 **Example**
 
@@ -48,10 +49,10 @@ Appends a key-value pair into the query string.
 
 **Parameters**
 
- | Name | Type | Mandatory | Description |
- | -------- | -------- | -------- | -------- |
- | name | string | Yes | Key of the key-value pair to append. |
- | value | string | Yes | Value of the key-value pair to append. |
+| Name| Type| Mandatory| Description|
+| -------- | -------- | -------- | -------- |
+| name | string | Yes| Key of the key-value pair to append.|
+| value | string | Yes| Value of the key-value pair to append.|
 
 **Example**
 
@@ -72,9 +73,9 @@ Deletes key-value pairs of the specified key.
 
 **Parameters**
 
- | Name | Type | Mandatory | Description |
- | -------- | -------- | -------- | -------- |
- | name | string | Yes | Key of the key-value pairs to delete. |
+| Name| Type| Mandatory| Description|
+| -------- | -------- | -------- | -------- |
+| name | string | Yes| Key of the key-value pairs to delete.|
 
 **Example**
 
@@ -95,15 +96,15 @@ Obtains all the key-value pairs based on the specified key.
 
 **Parameters**
 
- | Name | Type | Mandatory | Description |
- | -------- | -------- | -------- | -------- |
- | name | string | Yes | Key specified to obtain all key-value pairs. |
+| Name| Type| Mandatory| Description|
+| -------- | -------- | -------- | -------- |
+| name | string | Yes| Key specified to obtain all key-value pairs.|
 
 **Return value**
 
- | Type | Description |
- | -------- | -------- |
- | string[] | All key-value pairs matching the specified key. |
+| Type| Description|
+| -------- | -------- |
+| string[] | All key-value pairs matching the specified key.|
 
 **Example**
 
@@ -125,9 +126,9 @@ Obtains an ES6 iterator. Each item of the iterator is a JavaScript array, and th
 
 **Return value**
 
- | Type | Description |
- | -------- | -------- |
- | IterableIterator&lt;[string,&nbsp;string]&gt; | ES6 iterator. |
+| Type| Description|
+| -------- | -------- |
+| IterableIterator&lt;[string,&nbsp;string]&gt; | ES6 iterator.|
 
 **Example**
 
@@ -149,18 +150,18 @@ Traverses the key-value pairs in the **URLSearchParams** instance by using a cal
 
 **Parameters**
 
- | Name | Type | Mandatory | Description |
- | -------- | -------- | -------- | -------- |
- | callbackfn | function | Yes | Callback invoked to traverse the key-value pairs in the **URLSearchParams** instance. |
- | thisArg | Object | No | Value to use when the callback is invoked. |
+| Name| Type| Mandatory| Description|
+| -------- | -------- | -------- | -------- |
+| callbackfn | function | Yes| Callback invoked to traverse the key-value pairs in the **URLSearchParams** instance.|
+| thisArg | Object | No| Value to use when the callback is invoked.|
 
 **Table 1** callbackfn parameter description
 
- | Name | Type | Mandatory | Description |
- | -------- | -------- | -------- | -------- |
- | value | string | Yes | Value that is currently traversed. |
- | key | string | Yes | Key that is currently traversed. |
- | searchParams | Object | Yes | Instance that invokes the **forEach** method. |
+| Name| Type| Mandatory| Description|
+| -------- | -------- | -------- | -------- |
+| value | string | Yes| Value that is currently traversed.|
+| key | string | Yes| Key that is currently traversed.|
+| searchParams | Object | Yes| Instance that invokes the **forEach** method.|
 
 **Example**
 
@@ -182,16 +183,16 @@ Obtains the value of the first key-value pair based on the specified key.
 
 **Parameters**
 
- | Name | Type | Mandatory | Description |
- | -------- | -------- | -------- | -------- |
- | name | string | Yes | Key specified to obtain the value. |
+| Name| Type| Mandatory| Description|
+| -------- | -------- | -------- | -------- |
+| name | string | Yes| Key specified to obtain the value.|
 
 **Return value**
 
- | Type | Description |
- | -------- | -------- |
- | string | Returns the value of the first key-value pair if obtained. |
- | null | Returns null if no value is obtained. |
+| Type| Description|
+| -------- | -------- |
+| string | Returns the value of the first key-value pair if obtained.|
+| null | Returns null if no value is obtained.|
 
 **Example**
 
@@ -212,15 +213,15 @@ Checks whether a key has a value.
 
 **Parameters**
 
- | Name | Type | Mandatory | Description |
- | -------- | -------- | -------- | -------- |
- | name | string | Yes | Key specified to search for its value. |
+| Name| Type| Mandatory| Description|
+| -------- | -------- | -------- | -------- |
+| name | string | Yes| Key specified to search for its value.|
 
 **Return value**
 
- | Type | Description |
- | -------- | -------- |
- | boolean | Returns **true** if the value exists; returns **false** otherwise. |
+| Type| Description|
+| -------- | -------- |
+| boolean | Returns **true** if the value exists; returns **false** otherwise.|
 
 **Example**
 
@@ -241,10 +242,10 @@ Sets the value for a key. If key-value pairs matching the specified key exist, t
 
 **Parameters**
 
- | Name | Type | Mandatory | Description |
- | -------- | -------- | -------- | -------- |
- | name | string | Yes | Key of the value to set. |
- | value | string | Yes | Value to set. |
+| Name| Type| Mandatory| Description|
+| -------- | -------- | -------- | -------- |
+| name | string | Yes| Key of the value to set.|
+| value | string | Yes| Value to set.|
 
 **Example**
 
@@ -282,9 +283,9 @@ Obtains an ES6 iterator that contains the keys of all the key-value pairs.
 
 **Return value**
 
- | Type | Description |
- | -------- | -------- |
- | IterableIterator&lt;string&gt; | ES6 iterator that contains the keys of all the key-value pairs. |
+| Type| Description|
+| -------- | -------- |
+| IterableIterator&lt;string&gt; | ES6 iterator that contains the keys of all the key-value pairs.|
 
 **Example**
 
@@ -306,9 +307,9 @@ Obtains an ES6 iterator that contains the values of all the key-value pairs.
 
 **Return value**
 
- | Type | Description |
- | -------- | -------- |
- | IterableIterator&lt;string&gt; | ES6 iterator that contains the values of all the key-value pairs. |
+| Type| Description|
+| -------- | -------- |
+| IterableIterator&lt;string&gt; | ES6 iterator that contains the values of all the key-value pairs.|
 
 **Example**
 
@@ -330,9 +331,9 @@ Obtains an ES6 iterator. Each item of the iterator is a JavaScript array, and th
 
 **Return value**
 
- | Type | Description |
- | -------- | -------- |
- | IterableIterator&lt;[string,&nbsp;string]&gt; | ES6 iterator. |
+| Type| Description|
+| -------- | -------- |
+| IterableIterator&lt;[string,&nbsp;string]&gt; | ES6 iterator.|
 
 **Example**
 
@@ -354,9 +355,9 @@ Obtains search parameters that are serialized as a string and, if necessary, per
 
 **Return value**
 
- | Type | Description |
- | -------- | -------- |
- | string | String of serialized search parameters, which is percent-encoded if necessary. |
+| Type| Description|
+| -------- | -------- |
+| string | String of serialized search parameters, which is percent-encoded if necessary.|
 
 **Example**
 
@@ -400,10 +401,10 @@ Creates a URL.
 
 **Parameters**
 
- | Name | Type | Mandatory | Description |
- | -------- | -------- | -------- | -------- |
- | url | string | Yes | Input object. |
- | base | string&nbsp;\ |&nbsp;URL | No | Input parameter, which can be any of the following:<br>- **string**: string<br>- **URL**: string or object |
+| Name| Type| Mandatory| Description|
+| -------- | -------- | -------- | -------- |
+| url | string | Yes| Input object.|
+| base | string&nbsp;\|&nbsp;URL | No| Input parameter, which can be any of the following:<br>- **string**: string<br>- **URL**: string or object|
 
 **Example**
 
@@ -433,9 +434,9 @@ Converts the parsed URL into a string.
 
 **Return value**
 
- | Type | Description |
- | -------- | -------- |
- | string | Website address in a serialized string. |
+| Type| Description|
+| -------- | -------- |
+| string | Website address in a serialized string.|
 
 **Example**
 
@@ -455,12 +456,12 @@ Converts the parsed URL into a JSON string.
 
 **Return value**
 
- | Type | Description |
- | -------- | -------- |
- | string | Website address in a serialized string. |
+| Type| Description|
+| -------- | -------- |
+| string | Website address in a serialized string.|
 
 **Example**
 ```js
 const url = new Url.URL('http://username:password@host:8080/directory/file?query=pppppp#qwer=da');
 url.toJSON()
-```
\ No newline at end of file
+```

en/application-dev/reference/apis/js-apis-usb.md

 # USB
 
-> **NOTE**<br>
+This module provides USB device management functions, including USB device list query, bulk data transfer, control transfer, and permission control.
+
+> **NOTE**
+> 
 > The initial APIs of this module are supported since API version 8. Newly added APIs will be marked with a superscript to indicate their earliest API version.
 
 ## Modules to Import

en/application-dev/reference/apis/js-apis-util.md

@@ -61,7 +61,7 @@ Obtains detailed information about a system error code.
 
 **Example**
   ```js
-  var errnum = 10; // 10 is the system error code.
+  var errnum = 10; // 10 is a system error code.
   var result = util.getErrorString(errnum);
   console.log("result = " + result);
   ```
@@ -104,14 +104,16 @@ Calls back an asynchronous function. In the callback, the first parameter indica
 
 promiseWrapper(original: (err: Object, value: Object) => void): Object
 
-> **Introduce**<br/>
-> Deprecated starting from API version 9, it is recommended to use [util.promisify9 +] (\utilpromisify9) instead.
+> **NOTE**
+>
+> This API is deprecated since API version 9. You are advised to use **[util.promisify9+](#utilpromisify9)** instead.
 
 Processes an asynchronous function and returns a promise version.
 
 **System capability**: SystemCapability.Utils.Lang
 
 **Parameters**
+
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
 | original | Function | Yes| Asynchronous function.|
@@ -136,7 +138,7 @@ Processes an asynchronous function and returns a promise version.
 
 promisify(original: (err: Object, value: Object) =&gt; void): Function
 
-Processes an asynchronous function and returns a promise function.
+Processes an asynchronous function and returns a promise.
 
 **System capability**: SystemCapability.Utils.Lang
 
@@ -148,7 +150,7 @@ Processes an asynchronous function and returns a promise function.
 **Return value**
 | Type| Description|
 | -------- | -------- |
-| Function | Function in the error-first style (that is, **(err, value) =>...** is called as the last parameter) and the promise version.|
+| Function | Function in the error-first style (that is, **(err, value) =>...** is called as the last parameter) and the promise.|
 
 **Example**
   ```js
@@ -165,7 +167,6 @@ Processes an asynchronous function and returns a promise function.
   })
   ```
 
-
 ## TextDecoder
 
 ### Attributes
@@ -217,7 +218,7 @@ Decodes the input content.
 **Parameters**
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
-| input | Unit8Array | Yes| Uint8Array to decode.|
+| input | Uint8Array | Yes| Uint8Array to decode.|
 | options | Object | No| Options related to decoding.|
 
   **Table 2** options
@@ -982,7 +983,6 @@ Performs subsequent operations after a value is removed.
 **Example**
   ```js
   var arr = [];
-  var arr = [];
   class ChildLruBuffer extends util.LruBuffer
   {
   	constructor()

en/application-dev/reference/apis/js-apis-xml.md

 # XML Parsing and Generation
 
-> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
+> **NOTE**
+>
 > The initial APIs of this module are supported since API version 8. Newly added APIs will be marked with a superscript to indicate their earliest API version.
 
 

en/application-dev/reference/arkui-ts/ts-basic-components-button.md

 # Button
 
+The **\<Button>** component can be used to create different types of buttons.
 
-> **NOTE**<br>
+> **NOTE**
+>
 > This component is supported since API version 7. Updates will be marked with a superscript to indicate their earliest API version.
 
 
-The **&lt;Button&gt;** component represents a component that can trigger actions.
-
-
 ## Required Permissions
 
 None
@@ -30,15 +29,15 @@ Supported
   | stateEffect | boolean | No | true | Whether to enable the state switchover effect when a button is pressed. When the state is set to **false**, the state switchover effect is disabled. |
 
 
-- Button(label?: string, options?: { type?: ButtonType, stateEffect?: boolean })
+- Button(label?: ResourceStr, options?: { type?: ButtonType, stateEffect?: boolean })
   
-  Creates a button component based on text content. In this case, the **&lt;Button&gt;** component cannot contain child components.
+  Creates a button component based on text content. In this case, the **\<Button>** component cannot contain child components.
 
-  **Table 2** value parameters
+  **Table 2** Parameters
 
   | Name | Type | Mandatory | Default Value | Description |
   | -------- | -------- | -------- | -------- | -------- |
-  | label | string | No | - | Button text. |
+  | label | [ResourceStr](../../ui/ts-types.md) | No | - | Button text. |
   | options | Object | No | - | For details, see the **options** parameters. |
 
 
@@ -54,8 +53,8 @@ Supported
 | Name | Description |
 | -------- | -------- |
 | Capsule | Capsule-type button (the round corner is half of the height by default). |
-| Circle | Circle button. |
-| Normal | Normal button (without rounded corners by default). |
+| Circle  | Circle button. |
+| Normal  | Normal button (without rounded corners by default). |
 
 > **NOTE**
 > - The rounded corner of a button is set by using [Border](ts-universal-attributes-border.md). (The rounded corner cannot be set by using a border API.)
@@ -67,7 +66,8 @@ Supported
 ## Example
 
 
-```
+```ts
+// xxx.ets
 @Entry
 @Component
 struct ButtonExample {
@@ -78,6 +78,7 @@ struct ButtonExample {
         Button('Ok', { type: ButtonType.Normal, stateEffect: true }).borderRadius(8).backgroundColor(0x317aff).width(90)
         Button({ type: ButtonType.Normal, stateEffect: true }) {
           Row() {
+            // You are advised to reference an image by using $r to create a Resource object.
             Image($r('app.media.loading')).width(20).height(20).margin({ left: 12 })
             Text('loading').fontSize(12).fontColor(0xffffff).margin({ left: 5, right: 12 })
           }.alignItems(VerticalAlign.Center)

en/application-dev/reference/arkui-ts/ts-universal-attributes-background.md

 # Background
 
+You can set the background of a component.
 
-> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+> **NOTE**
+>
 > This attribute is supported since API version 7. Updates will be marked with a superscript to indicate their earliest API version.
 
 
-The attributes in this topic are used to set the background color of a component.
-
-
 ## Required Permissions
 
 None
@@ -18,24 +17,25 @@ None
 
 | Name | Type | Default Value | Description |
 | -------- | -------- | -------- | -------- |
-| backgroundColor | Color | - | Background color of a component. |
-| backgroundImage | src: string,<br/>repeat?: [ImageRepeat](ts-appendix-enums.md#imagerepeat-enums) | - | **src**: image address, which can be the address of an Internet or a local image. (SVG images are not supported.)<br/>**repeat**: whether the background image is repeatedly used. By default, the background image is not repeatedly used. |
+| backgroundColor | [ResourceColor](../../ui/ts-types.md) | - | Background color of a component. |
+| backgroundImage | src: [ResourceStr](../../ui/ts-types.md),<br/>repeat?: [ImageRepeat](ts-appendix-enums.md#imagerepeat-enums) | - | **src**: image address, which can be the address of an Internet or a local image. (SVG images are not supported.)<br/>**repeat**: whether the background image is repeatedly used. By default, the background image is not repeatedly used. |
 | backgroundImageSize | {<br/>width?: Length,<br/>height?: Length<br/>} \| ImageSize | Auto | Width and height of the background image. When the input is a **{width: Length, height: Length}** object, if only one attribute is set, the other attribute is the set value multiplied by the original aspect ratio of the image. By default, the original image aspect ratio remains unchanged. |
 | backgroundImagePosition | {<br/>x?: Length,<br/>y?: Length<br/>} \| [Alignment](ts-appendix-enums.md#alignment-enums) | {<br/>x: 0,<br/>y: 0<br/>} | Position of the background image in the component. |
 
 
 - ImageSize enums
-    | Name | Description | 
+  | Name | Description |
   | -------- | -------- |
-  | Cover | Default value. The image is scaled with its aspect ratio retained for both sides to be greater than or equal to the display boundaries. | 
-  | Contain | The image is scaled with its aspect ratio retained for the content to be completely displayed within the display boundaries. | 
-  | Auto | The original image aspect ratio is retained. | 
+  | Cover | Default value. The image is scaled with its aspect ratio retained for both sides to be greater than or equal to the display boundaries. |
+  | Contain | The image is scaled with its aspect ratio retained for the content to be completely displayed within the display boundaries. |
+  | Auto | The original image aspect ratio is retained. |
 
 
 ## Example
 
 
-```
+```ts
+// xxx.ets
 @Entry
 @Component
 struct BackgroundExample {

en/application-dev/reference/arkui-ts/ts-universal-attributes-gradient-color.md

 # Gradient Color
 
+Create a more gorgeous look for a component by applying a gradient color effect to it.
 
-> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+> **NOTE**
+>
 > This attribute is supported since API version 7. Updates will be marked with a superscript to indicate their earliest API version.
 
 
@@ -15,31 +17,32 @@ None
 
 | Name | Type | Default Value | Description |
 | -------- | -------- | -------- | -------- |
-| linearGradient | {<br/>angle?: [Angle](../../ui/ts-types.md),<br/>direction?:GradientDirection,<br/>colors: Array<[ColorStop](../../ui/ts-types.md)><br/>repeating?: boolean<br/>} | - | Linear gradient.<br/>**angle**: angle of the linear gradient.<br/>**direction**: direction of the linear gradient.<br/>**colors**: description of the gradient colors.<br/>**repeating**: whether the colors are repeated. |
+| linearGradient | {<br/>angle?: [Angle](../../ui/ts-types.md),<br/>direction?:GradientDirection,<br/>colors: Array<[ColorStop](../../ui/ts-types.md)><br/>repeating?: boolean<br/>} | - | Linear gradient.<br/>**angle**: angle of the linear gradient.<br/>**direction**: direction of the linear gradient. It does not take effect when **angle** is set.<br/>**colors**: description of the gradient colors.<br/>**repeating**: whether the colors are repeated. |
 | sweepGradient | {<br/>center: Point,<br/>start?: angle,<br/>end?: angle,<br/>colors: Array<[ColorStop](../../ui/ts-types.md)><br/>repeating?: boolean<br/>} | - | Angle gradient.<br/>**center**: center point of the angle gradient.<br/>**start**: start point of the angle gradient.<br/>**end**: end point of the angle gradient.<br/>**colors**: description of the gradient colors.<br/>**repeating**: whether the colors are repeated. |
 | radialGradient | {<br/>center: Point,<br/>radius: Length,<br/>colors: Array<[ColorStop](../../ui/ts-types.md)><br/>repeating: boolean<br/>} | - | Radial gradient.<br/>**center**: center point of the radial gradient.<br/>**radius**: radius of the radial gradient.<br/>**colors**: description of the gradient colors.<br/>**repeating**: whether the colors are repeated. |
 
+- GradientDirection
 
-- GradientDirection enums
-  **GradientDirection** is used to describe the gradient direction.
+  Enumerates the gradient directions.
 
-    | Name | Description | 
+  | Name | Description |
   | -------- | -------- |
-  | Left | The gradient direction is from right to left. | 
-  | Top | The gradient direction is from bottom to top. | 
-  | Right | The gradient direction is from left to right. | 
-  | Bottom | The gradient direction is from top to bottom. | 
-  | LeftTop | The gradient direction is upper left. | 
-  | LeftBottom | The gradient direction is lower left. | 
-  | RightTop | The gradient direction is upper right. | 
-  | RightBottom | The gradient direction is lower right. | 
-  | None | No gradient. | 
+  | Left | The gradient direction is from right to left. |
+  | Top | The gradient direction is from bottom to top. |
+  | Right | The gradient direction is from left to right. |
+  | Bottom | The gradient direction is from top to bottom. |
+  | LeftTop | The gradient direction is upper left. |
+  | LeftBottom | The gradient direction is lower left. |
+  | RightTop | The gradient direction is upper right. |
+  | RightBottom | The gradient direction is lower right. |
+  | None | No gradient. |
 
 
 ## Example
 
 
-```
+```ts
+// xxx.ets
 @Entry
 @Component
 struct ColorGradientExample {
@@ -51,7 +54,6 @@ struct ColorGradientExample {
         .height(50)
         .linearGradient({
           angle: 90,
-          direction: GradientDirection.Left,
           colors: [[0xAEE1E1, 0.0], [0xD3E0DC, 0.3], [0xFCD1D1, 1.0]]
         })
       Text('sweepGradient').fontSize(12).width('90%').fontColor(0xCCCCCC)

en/application-dev/ui/Readme-EN.md

@@ -145,4 +145,4 @@
             - Interpolator Animation
                 - [Animation Effect](ui-js-animate-dynamic-effects.md)
                 - [Animation Frame](ui-js-animate-frame.md)
-    - [Custom Components](ui-js-custom-components.md)
\ No newline at end of file
+    - [Custom Components](ui-js-custom-components.md)

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)
+![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.
 

en/design/OpenHarmony-API-governance.md

@@ -2,7 +2,7 @@
 
 ## Introduction
 
-To help the OpenHarmony ecosystem develop and evolve in a healthy and orderly way, this Charter defines the governance process and lifecycle (create, change, deprecate, and delete) of OpenHarmony APIs. It also specifies basic design requirements of OpenHarmony APIs.
+To help the OpenHarmony ecosystem develop and evolve in a healthy and orderly way, this Charter defines the governance process and lifecycle (creation, change, deprecation, and deletion) of OpenHarmony APIs. It also specifies basic design requirements of OpenHarmony APIs.
 
 This Charter is formulated by the API SIG and approved by the PMC for release. Any revision to this Charter will be released only after being reviewed by the API SIG and approved by the PMC.
 
@@ -16,14 +16,14 @@ The OpenHarmony software stack contains multiple roles. Naturally, OpenHarmony A
 
 Different types of APIs have different compatibility requirements, as described in the table below.
 
-| Type| Prepared By| Used By| Compatibility Requirement| Guarding Method|
-|---|---|---|---|---|
-| Public API | System and framework| All application developers| 5 API versions| X test suite (XTS)|
-| Test API | Test framework| All application developers| 3 API versions| To be built|
-| System API |  System and framework|System application developers|Not guaranteed| To be built|
-| HDI | HDF| System services| 4 API versions| XTS |
-| Driver API | HDF | Driver developers| Not guaranteed| None|
-| Inner API | System parts| System parts| Not guaranteed| None|
+ | Type | Prepared By | Used By | Compatibility Requirement | Guarding Method |
+ |--- |--- |--- |--- |--- |
+ | Public API | System and framework | All application developers | Five API versions | X test suite (XTS) |
+ | Test API | Test framework | All application developers | Three API versions | To be built |
+ | System API |  System and framework |System application developers |Not guaranteed | To be built |
+ | HDI | HDF | System services | Four API versions | XTS |
+ | Driver API | HDF | Driver developers | Not guaranteed | None |
+ | Inner API | System parts | System parts | Not guaranteed | None |
 
 The APIs are described as follows:
 
@@ -48,13 +48,13 @@ The content described in this Charter is irrelevant to the programming language
 
 ### Roles and Responsibilities
 
-|**Role**|**Responsibilities in API Governance**|
-| - | - |
-|Contributor|Commit API code and design documents.|
-|Committer|Review the code and submit a pre-review comment on an API commit.|
-|Domain SIG|Comment on the commits of new API code, so the passed commits can be merged. <br/>Submit a pre-review comment on updated API code.|
-|API SIG|Comment on updated API code.|
-|PMC|Release API version plans. Review amendments of this Charter, revise the terms, and publish this Charter.|
+ | Role | Responsibilities in API Governance |
+ | --- | --- |
+ | Contributor | Commit API code and design documents. |
+ | Committer | Review the code and submit a pre-review comment on an API commit. |
+ | Domain SIG | Comment on the commits of new API code, so the passed commits can be merged. <br/>Submit a pre-review comment on updated API code. |
+ | API SIG | Comment on updated API code. |
+ | PMC | Release API version plans. Review amendments of this Charter, revise the terms, and publish this Charter. |
 
 ### API Review Process
 The API review process is as follows:
@@ -66,7 +66,7 @@ The main process is as follows:
 1. Initiate API review and commit code (contributor). If any APIs are added or modified, the contributor must additionally submit an API review application to specify the API requirement source, usage scenario, permission design, and privacy protection design. For details, see "API Review Application Composites" below. To avoid rework, the contributor can send an email to submit the API design document to the committer, domain SIG, and API SIG for pre-review before the formal API review application and code commit.
 1. Review code (committer). After the code review is approved, the committer should submit the APIs to the domain SIG. If the API code involves multiple domains, they should be submitted to the committers of the corresponding domains. The next review step can be performed only after all committers review and approve the code.
 1. Review APIs (domain SIG). The code of new APIs can be merged only after being reviewed and approved by the domain SIG. If there are changes to existing APIs, the domain SIG should submit them to the API SIG. If the new APIs involve multiple domains, they should be submitted to the SIGs of the corresponding domains. The code can be merged after being reviewed and approved by one of the domain SIGs. If the changed APIs involve multiple domains, they should be submitted to the SIGs of the corresponding domains. The next review step can be performed only after all domain SIGs approve the APIs.
-1. Review API changes (owner: API SIG): The code of changed APIs can be merged only after being reviewed and approved by the API SIG.
+1. Review API changes (API SIG). The code of changed APIs can be merged only after being reviewed and approved by the API SIG.
 1. The review is complete.
 
 ### API Review Application Composites
@@ -175,18 +175,18 @@ Design APIs from the perspective of their users rather than providers.
 
 ### Performance
 1. Respond in a timely manner to avoid callers waiting. If an API call takes a long time, use an asynchronous API.
-2. Pay attention to the impact of the API call timing and frequency on the RAM usage.
-3. Pay attention to the impact of the API call timing and frequency on power consumption.
+2. Make sure that the impact of API call timing and frequency on the RAM usage is under control.
+3. Make sure that the impact of API call timing and frequency on the power consumption is under control.
 4. Resources must be released in a timely manner when APIs that use resources are called. A fault tolerance mechanism must be provided for abnormal scenarios to ensure timely resource release.
 
 ### Power Consumption
 
-1. Evaluate the impact of the API call timing and frequency on power consumption, and perform related design if there is any impact.
-2. The power consumption should not deteriorate during version evolution.
+1. Evaluate the impact of the API call timing and frequency on power consumption, and optimize the design if there is any impact.
+2. Make sure that the power consumption does not deteriorate during version evolution.
 
 ### Reliability
 
-1. APIs cannot crash due to external input (such as input parameters, system status, and external data), internal status, or data exceptions. It must return a specific error code or throw a predefined exception.
+1. APIs shall not crash due to external input (such as input parameters, system status, and external data), internal status, or data exceptions. It must return a specific error code or throw a predefined exception.
 2. It must be specified whether an API is called synchronously or asynchronously. If an API is called synchronously, specify the timeout duration or allow the caller to set the timeout duration to prevent service response failure caused by call suspension.
 3. APIs must support multi-thread reentrant.
 4. APIs must meet the idempotence requirement, which means that the same effect should be obtained for one or multiple API call requests with the same service meaning (except that API call depends on external resource changes). For reentrant API call, avoid introducing time-varying factors, such as system ticks, static variables, and global variables without mutual exclusion protection. For repeated call of the same client, **contextID**, **clientToken**, and **sequenceNo** can be used as input parameters.

en/design/OpenHarmony-part-design.md

@@ -4,7 +4,7 @@
 
 For easy software design and management, OpenHarmony decouples software from physical components, parts, and modules. A **component** can be independently deployed and reused at the binary level. A **part** can be independently developed, built, and tested. A **module** can be reused at the code level.
 
-OpenHarmony abstracts system capabilities as parts, so you can customize OSs for different devices by assembling and configuring these parts.
+OpenHarmony abstracts system capabilities as parts, so you can assemble and configure these parts to customize an OS for different devices.
 
 ## Part Definition
 
@@ -12,7 +12,7 @@ A part is the basic unit of system capabilities. Divided based on source code, e
 
 ## Part Division
 
-Follow the following rules for part classification:
+Observe the following rules for part classification:
 
 - A part must have an independent code directory for compiling libraries or executable files.
 
@@ -50,7 +50,7 @@ Comply with the following rules and recommendations during parts design and deve
 
 #### **Part Name**
 
-The name must reflect the key function of a part and must be globally unique in the system. The name can contain a maximum of 63 characters and must be in the unix\_like style, where only lowercase letters separated by underscores (\_) are used.
+The name must reflect the key function of a part and must be globally unique in the system. It can contain a maximum of 63 characters and must be in the unix\_like style, where only lowercase letters separated by underscores (\_) are used.
 
 #### **Repository Name**
 
@@ -96,21 +96,23 @@ The addition, deletion, and modification of parts must be reviewed by the archit
 
 Table 1 Part attribute review form
 
-| Part Attribute| Description|
+| Part Attribute | Description |
 | ------------ | ------------------------------------------------------------ |
-| Part name| The name must reflect the key function of a part and must be globally unique in the system. The name can contain a maximum of 63 characters and must be in the unix\_like style, where only lowercase letters separated by underscores (\_) are used.|
-| Subsystem| Subsystem to which the part belongs.|
-| Function description| Brief description of the functions of the part in one or two sentences.|
-| Configurable features| Features that can be configured externally.|
-| Applicable systems| Mini system, small system, standard system, or their combinations.|
-| Source code directory| Root directory of the source code of the part.|
-| ROM          | ROM baseline value of the part.|
-| RAM          | RAM baseline value of the part.|
-| Dependencies| Parts and open source software on which the part depends.|
+| Part name | The name must reflect the key function of a part and must be globally unique in the system. The name can contain a maximum of 63 characters and must be in the unix\_like style, where only lowercase letters separated by underscores (\_) are used. |
+| Subsystem | Subsystem to which the part belongs. |
+| Function description | Brief description of the functions of the part in one or two sentences. |
+| Configurable features | Features that can be configured externally. |
+| Applicable systems | Mini system, small system, standard system, or their combinations. |
+| Source code directory | Root directory of the source code of the part. |
+| ROM          | ROM baseline value of the part. |
+| RAM          | RAM baseline value of the part. |
+| Dependencies | Parts and open source software on which the part depends. |
 
 
 2. Send an email to the architecture SIG (dev@openharmony.io) and the [related domain SIG leaders](https://gitee.com/openharmony/community/blob/master/sig/sigs_subsystem_list.md) for review. Use "Application for Adding/Deleting/Modifying OpenHarmony Parts" as the email subject, and include the filled-in **Table 1 Part Attribute Review Form** in the email body.
 
-> Note: For modified parts, provide a before and after comparison of the part attributes. For deleted parts, provide the plan for stopping part maintenance. Exercise caution when deleting or modifying parts and evaluate the impact on existing versions.
+> Note: 
+>
+> For modified parts, provide a before and after comparison of the part attributes. For deleted parts, provide the plan for stopping part maintenance. Exercise caution when deleting or modifying parts and evaluate the impact on existing versions.
 
 3. After the review is passed, create a part repository and modify the manifest according to [SIG Management Regulations](https://gitee.com/openharmony/community/blob/master/sig/README-EN.md). After the SIG is incubated, incorporate it into the main code library of OpenHarmony.

en/device-dev/device-dev-guide.md

@@ -36,7 +36,7 @@ In addition, OpenHarmony provides a wide array of system components that can be
 | Getting started       | Getting started with setup, build, burning, debugging, and running of OpenHarmony         | - [Mini and Small System Overview](quick-start/quickstart-ide-lite-overview.md)|
 | Basic capabilities   | Using basic capabilities of OpenHarmony                               | - [Kernel for Mini System](kernel/kernel-mini-overview.md)<br>- [Kernel for Small System](kernel/kernel-small-overview.md)<br>- [HDF](driver/driver-hdf-overview.md)<br>- [Subsystems](subsystems/subsys-build-mini-lite.md)<br>- [Security Guidelines](security/security-guidelines-overall.md)<br>- [Privacy Protection](security/security-privacy-protection.md)|
 | Advanced development       | Developing smart devices based on system capabilities                                    | - [WLAN-connected Products](guide/device-wlan-led-control.md)<br>- [Cameras Without a Screen](guide/device-iotcamera-control-overview.md)<br>- [Cameras with a Screen](guide/device-camera-control-overview.md) |
-| Porting and adaptation       | - Porting and adapting OpenHarmony to an SoC<br>- Porting and adapting OpenHarmony to a third-party library<br>- Third-party vendor porting cases<br>| - [Mini System SoC Porting Guide](porting/porting-minichip.md)<br>- [Small System SoC Porting Guide](porting/porting-smallchip-prepare-needs.md)<br>- [Third-Party Library Porting Guide for Mini and Small Systems](porting/porting-thirdparty-overview.md) <br>   - [Mini-System Devices with Screens — Bestechnic SoC Porting Case](porting-bes2600w-on-minisystem-display-demo.md)<br>    - [Combo Solution – ASR Chip Porting Case](porting/porting-asr582x-combo-demo.md)<br> |
+| Porting and adaptation       | - Porting and adapting OpenHarmony to an SoC<br>- Porting and adapting OpenHarmony to a third-party library<br>- Third-party vendor porting cases<br>| - [Mini System SoC Porting Guide](porting/porting-minichip.md)<br>- [Small System SoC Porting Guide](porting/porting-smallchip-prepare-needs.md)<br>- [Third-Party Library Porting Guide for Mini and Small Systems](porting/porting-thirdparty-overview.md) <br>   - [Mini-System Devices with Screens — Bestechnic SoC Porting Case](porting/porting-bes2600w-on-minisystem-display-demo.md)<br>    - [Combo Solution – ASR Chip Porting Case](porting/porting-asr582x-combo-demo.md)<br> |
 | Contributing components       | Contributing components to OpenHarmony                                   | - [HPM Part Overview](hpm-part/hpm-part-about.md)<br>- [HPM Part Development](hpm-part/hpm-part-development.md)<br>- [HPM Part Reference](hpm-part/hpm-part-reference.md) |
 | Reference | Referring to development specifications | [FAQs](faqs/faqs-overview.md) |
 

en/device-dev/driver/driver-platform-i2c-des.md

@@ -64,7 +64,7 @@ The figure below illustrates how to use the APIs.
 
 **Figure  2**  Using I2C driver APIs
 
-![](figures/using-i2c-process.png "process-of-using-an-i2c-device")
+![](figures/using-I2C-process.png "process-of-using-an-i2c-device")
 
 ### Opening an I2C Controller<a name="section13751110132914"></a>
 

en/device-dev/driver/driver-platform-spi-des.md

@@ -107,7 +107,7 @@ SPI communication is usually initiated by the SPI controller and is operated as
 The figure below illustrates how to use the APIs.
 
 **Figure  2** Using SPI driver APIs<a name="fig1586912310348"></a>  
-![](figures/using-spi-process.png "process-of-using-an-spi-device")
+![](figures/using-SPI-process.png "process-of-using-an-spi-device")
 
 ### Obtaining an SPI Device Handle<a name="section1927265711481"></a>
 

en/device-dev/driver/driver-platform-uart-des.md

@@ -106,7 +106,7 @@ The UART interface defines a set of common functions for operating a UART port,
 The figure below illustrates how to use the APIs.
 
 **Figure  3** Using UART driver APIs<a name="fig99673244388"></a>  
-![](figures/using-uart-process.png "process-of-using-a-uart-device")
+![](figures/using-UART-process.png "process-of-using-a-uart-device")
 
 ### Obtaining a UART Device Handle<a name="section124512065617"></a>
 

en/device-dev/quick-start/Readme-EN.md

@@ -19,9 +19,9 @@
             - [Burning](quickstart-ide-lite-steps-hi3516-burn.md)
             - [Running](quickstart-ide-lite-steps-hi3516-running.md)
     - Appendix
-        - Introduction to Development Boards
-            - [Introduction to the Hi3861 Development Board](quickstart-ide-lite-introduction-hi3861.md)
-            - [Introduction to the Hi3516 Development Board](quickstart-ide-lite-introduction-hi3516.md)
+        - [Introduction to the Hi3861 Development Board](quickstart-ide-lite-introduction-hi3861.md)
+        - [Introduction to the Hi3516 Development Board](quickstart-ide-lite-introduction-hi3516.md)
+        - [Overall Description of Compilation Form Factors](quickstart-build.md)
 - Getting Started with Mini and Small Systems (Installation Package Mode)
     - [Mini and Small System Overview](quickstart-lite-overview.md)
     - [Environment Preparation](quickstart-lite-env-setup.md)
@@ -49,6 +49,7 @@
             - [Introduction to the Hi3861 Development Board](quickstart-lite-introduction-hi3861.md)
             - [Introduction to the Hi3516 Development Board](quickstart-lite-introduction-hi3516.md)
         - [Reference](quickstart-lite-reference.md)
+        - [Overall Description of Compilation Form Factors](quickstart-build.md)
 - Getting Started with Standard System (IDE Mode, Recommended)
     - [Standard System Overview](quickstart-ide-standard-overview.md)
     - Environment Preparation
@@ -67,9 +68,9 @@
             - [Burning](quickstart-ide-standard-running-rk3568-burning.md)
             - [Running](quickstart-ide-standard-running-rk3568-running.md)
     - Appendix
-        - Introduction to Development Boards
-            - [Introduction to the Hi3516 Development Board](quickstart-ide-standard-board-introduction-hi3516.md)
-            - [Introduction to the RK3568 Development Board](quickstart-ide-standard-board-introduction-rk3568.md)
+        - [Introduction to the Hi3516 Development Board](quickstart-ide-standard-board-introduction-hi3516.md)
+        - [Introduction to the RK3568 Development Board](quickstart-ide-standard-board-introduction-rk3568.md)
+        - [Overall Description of Compilation Form Factors](quickstart-build.md)
 - Getting Started with Standard System (Installation Package Mode)
     - [Standard System Overview](quickstart-standard-overview.md)
     - [Setting Up Environments for Standard System](quickstart-standard-env-setup.md)
@@ -93,3 +94,4 @@
             - [Introduction to the Hi3516 Development Board](quickstart-standard-board-introduction-hi3516.md)
             - [Introduction to the RK3568 Development Board](quickstart-standard-board-introduction-rk3568.md)
         - [Reference](quickstart-standard-reference.md)
+        - [Overall Description of Compilation Form Factors](quickstart-build.md)

en/device-dev/quick-start/quickstart-build.md

+# Overall Description of Compilation Form Factors
+Products Supported for Compilation and Building (Click the links to learn about the specific product configurations and related differences.)
+
+| Compilation Form Factor                     | Development Board          | Main Chip     | Kernel        | System Type    |
+| ----------------------------- | --------------- | ----------- | ----------- | ----------- |
+| [neptune100](https://gitee.com/openharmony/vendor_hihope/blob/master/neptune_iotlink_demo/config.json)                    | neptune100      | WinnerMicro | LiteOS-M    | Mini        |
+| [rk3568](https://gitee.com/openharmony/vendor_hihope/blob/master/rk3568/config.json)                        | rk3568          | Rockchip    | Linux  | Standard |
+| [rk3568_mini_system](https://gitee.com/openharmony/vendor_hihope/blob/master/rk3568_mini_system/config.json)            | rk3568          | Rockchip | Linux  | Standard |
+| [bearpi_hm_micro](https://gitee.com/openharmony/vendor_bearpi/blob/master/bearpi_hm_micro/config.json)               | bearpi_hm_micro | STM32MP1xx | LiteOS-A    | small       |
+| [bearpi_hm_nano](https://gitee.com/openharmony/vendor_bearpi/blob/master/bearpi_hm_nano/config.json)                | bearpi_hm_nano  | Hi3861 V100 | LiteOS-M    | Mini        |
+| [wifiiot_hispark_pegasus](https://gitee.com/openharmony/vendor_hisilicon/blob/master/hispark_pegasus/config.json)       | hispark_pegasus | Hi3861 V100 | LiteOS-M    | Mini        |
+| [ipcamera_hispark_aries](https://gitee.com/openharmony/vendor_hisilicon/blob/master/hispark_aries/config.json)        | hispark_aries   | hi3518ev300 | LiteOS-A    | Small  |
+| [ipcamera_hispark_taurus](https://gitee.com/openharmony/vendor_hisilicon/blob/master/hispark_taurus/config.json)       | hispark_taurus  | Hi3516D V300 | LiteOS-A    | Small  |
+| [ipcamera_hispark_taurus_linux](https://gitee.com/openharmony/vendor_hisilicon/blob/master/hispark_taurus_linux/config.json) | hispark_taurus  | Hi3516D V300 | Linux  | Small       |
+| [hispark_taurus_standard](https://gitee.com/openharmony/vendor_hisilicon/blob/master/hispark_taurus_standard/config.json)       | hispark_taurus  | Hi3516D V300 | Linux  | Standard |
+| [watchos](https://gitee.com/openharmony/vendor_hisilicon/blob/master/watchos/config.json)                       | hispark_taurus  | Hi3516D V300 | Linux  | Standard |
+| [hispark_phoenix](https://gitee.com/openharmony/vendor_hisilicon/blob/master/hispark_phoenix/config.json)               | hispark_phoenix | hi3751v350  | Linux  | Standard |
+| [hispark_taurus_mini_system](https://gitee.com/openharmony/vendor_hisilicon/blob/master/hispark_taurus_mini_system/config.json)    | hispark_taurus  | Hi3516D V300 | LiteOS-A    | Mini        |
+| [hispark_pegasus_mini_system](https://gitee.com/openharmony/vendor_hisilicon/blob/master/hispark_pegasus_mini_system/config.json)   | hispark_pegasus | Hi3861 V100 | LiteOS-M    | Mini    |
+| [gr5515_sk_iotlink_demo](https://gitee.com/openharmony/vendor_goodix/blob/master/gr5515_sk_iotlink_demo/config.json)        | gr5515_sk       | GR551x | LiteOS-M    | Mini    |
+| [gr5515_sk_xts_demo](https://gitee.com/openharmony/vendor_goodix/blob/master/gr5515_sk_xts_demo/config.json)            | gr5515_sk       | GR551x | LiteOS-M    | Mini    |
+| [wifi_demo](https://gitee.com/openharmony/vendor_asrmicro/blob/master/wifi_demo/config.json)                     | dev_wifi_a      | ASR582X | LiteOS-M    | Mini    |
+| [xts_demo](https://gitee.com/openharmony/vendor_asrmicro/blob/master/xts_demo/config.json)                      | dev_wifi_a      | ASR582X | LiteOS-M    | Mini    |
+| [display_demo](https://gitee.com/openharmony/vendor_bestechnic/blob/master/display_demo/config.json)                  | v200zr          | BES2600 | LiteOS-M    | Mini    |
+| [xts_demo](https://gitee.com/openharmony/vendor_bestechnic/blob/master/xts_demo/config.json)                      | v200zr          | BES2600  | LiteOS-M    | Mini    |
+| [iotlink_demo](https://gitee.com/openharmony/vendor_bestechnic/blob/master/iotlink_demo/config.json)                  | v200zr          | BES2600 | LiteOS-M    | Mini    |
+| [mini_distributed_music_player](https://gitee.com/openharmony/vendor_bestechnic/blob/master/mini_distributed_music_player/config.json) | v200zr          | BES2600 | LiteOS-M    | Mini    |
+| [niobe407](https://gitee.com/openharmony/vendor_talkweb/blob/master/niobe407/config.json)                      | niobe407        | stm32f4xx   | LiteOS-M    | Mini    |
+| [qemu_mini_system_demo](https://gitee.com/openharmony/vendor_ohemu/blob/master/qemu_mini_system_demo/config.json)         | arm_mps2_an386  | QEMU        | LiteOS-M    | Mini    |
+| [qemu_cksy_mini_system_demo](https://gitee.com/openharmony/vendor_ohemu/blob/master/qemu_csky_mini_system_demo/config.json)    | SmartL_E802     | QEMU    | LiteOS-M    | Mini    |
+| [qemu_cm55_mini_system_demo](https://gitee.com/openharmony/vendor_ohemu/blob/master/qemu_cm55_mini_system_demo/config.json)    | arm_mps3_an547  | QEMU    | LiteOS-M    | Mini    |
+| [qemu_xtensa_mini_system_demo](https://gitee.com/openharmony/vendor_ohemu/blob/master/qemu_xtensa_mini_system_demo/config.json)  | esp32           | QEMU    | LiteOS-M    | Mini    |
+| [qemu_riscv_mini_system_demo](https://gitee.com/openharmony/vendor_ohemu/blob/master/qemu_riscv32_mini_system_demo/config.json)   | ricsv32_virt    | QEMU    | LiteOS-M    | Mini    |
+| [qemu_ca7_mini_system_demo](https://gitee.com/openharmony/vendor_ohemu/blob/master/qemu_ca7_mini_system_demo/config.json)     | arm_virt        | QEMU    | LiteOS-A    | Small       |
+| [qemu_small_system_demo](https://gitee.com/openharmony/vendor_ohemu/blob/master/qemu_small_system_demo/config.json)        | arm_virt        | QEMU    | LiteOS-A    | Small       |
+| [qemu_arm_linux_min](https://gitee.com/openharmony/vendor_ohemu/blob/master/qemu_arm_linux_min/config.json)            | qemu-arm-linux  | QEMU    | Linux  | Standard |
+| [qemu_arm_linux_headless](https://gitee.com/openharmony/vendor_ohemu/blob/master/qemu_arm_linux_headless/config.json)       | qemu-arm-linux  | QEMU    | Linux  | Standard    |
+| [iotlink_demo](https://gitee.com/openharmony/vendor_chipsea/blob/master/iotlink_demo/config.json)                  | cst85_wblink    | Chipsea     | LiteOS-M    | Mini    |
+| [dsoftbus_demo](https://gitee.com/openharmony/vendor_chipsea/blob/master/dsoftbus_demo/config.json)                 | cst85_wblink    | Chipsea | LiteOS-M    | Mini    |
+| [xts_demo](https://gitee.com/openharmony/vendor_chipsea/blob/master/xts_demo/config.json)                      | cst85_wblink    | Chipsea | LiteOS-M    | Mini    |

en/device-dev/quick-start/quickstart-standard-ide-directory.md

 ## Getting Started with Standard System (IDE Mode)
 - [Standard System Overview](quickstart-ide-standard-overview.md)
-    - Environment Preparation
-        - [Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-standard-env-setup-win-ubuntu.md)
-        - [Obtaining Source Code](quickstart-ide-standard-sourcecode-acquire.md)
-    - [Creating a Source Code Project](quickstart-ide-standard-create-project.md)
-    - Running a Hello World Program
-        - Hi3516 Development Board
-            - [Writing a Hello World Program](quickstart-ide-standard-running-hi3516-create.md)
-            - [Building](quickstart-ide-standard-running-hi3516-build.md)
-            - [Burning](quickstart-ide-standard-running-hi3516-burning.md)
-            - [Running](quickstart-ide-standard-running-hi3516-running.md)
-        - RK3568 Development Board
-            - [Writing a Hello World Program](quickstart-ide-standard-running-rk3568-create.md)
-            - [Building](quickstart-ide-standard-running-rk3568-build.md)
-            - [Burning](quickstart-ide-standard-running-rk3568-burning.md)
-            - [Running](quickstart-ide-standard-running-rk3568-running.md)
-    - Appendix
-        - Introduction to Development Boards
-            - [Introduction to the Hi3516 Development Board](quickstart-ide-standard-board-introduction-hi3516.md)
-            - [Introduction to the RK3568 Development Board](quickstart-ide-standard-board-introduction-rk3568.md)
-        - [Getting Started with Mini and Small Systems (Installation Package Mode)](quickstart-lite-package-directory.md)
+- Environment Preparation
+    - [Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-standard-env-setup-win-ubuntu.md)
+    - [Obtaining Source Code](quickstart-ide-standard-sourcecode-acquire.md)
+- [Creating a Source Code Project](quickstart-ide-standard-create-project.md)
+- Running a Hello World Program
+    - Hi3516 Development Board
+        - [Writing a Hello World Program](quickstart-ide-standard-running-hi3516-create.md)
+        - [Building](quickstart-ide-standard-running-hi3516-build.md)
+        - [Burning](quickstart-ide-standard-running-hi3516-burning.md)
+        - [Running](quickstart-ide-standard-running-hi3516-running.md)
+    - RK3568 Development Board
+        - [Writing a Hello World Program](quickstart-ide-standard-running-rk3568-create.md)
+        - [Building](quickstart-ide-standard-running-rk3568-build.md)
+        - [Burning](quickstart-ide-standard-running-rk3568-burning.md)
+        - [Running](quickstart-ide-standard-running-rk3568-running.md)
+- Appendix
+    - [Introduction to the Hi3516 Development Board](quickstart-ide-standard-board-introduction-hi3516.md)
+    - [Introduction to the RK3568 Development Board](quickstart-ide-standard-board-introduction-rk3568.md)
+    - [Overall Description of Compilation Form Factors](quickstart-build.md)
+

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

@@ -3,7 +3,7 @@
 - [Setting Up Environments for Standard System](quickstart-standard-env-setup.md)
 - Running a Hello World Program
     - Hi3516 Development Board
-        - [Writing a Hello World Program](quickstart-standard-running-hi3516-create.md)
+        - [Writing a Hello World Program](quickstart-std-3516-create.md)
         - [Building](quickstart-standard-running-hi3516-build.md)
         - [Burning](quickstart-standard-running-hi3516-burning.md)
         - [Running](quickstart-standard-running-hi3516-running.md)
@@ -20,5 +20,5 @@
     - Introduction to Development Boards
         - [Introduction to the Hi3516 Development Board](quickstart-standard-board-introduction-hi3516.md)
         - [Introduction to the RK3568 Development Board](quickstart-standard-board-introduction-rk3568.md)
-    - [Getting Started with Standard System (IDE Mode)](quickstart-standard-ide-directory.md)
+        - [Overall Description of Compilation Form Factors](quickstart-build.md)
     - [Reference](quickstart-standard-reference.md)

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

@@ -3,7 +3,6 @@
 -   **[Startup](subsys-boot-overview.md)**  
 -   **[init Module](subsys-boot-init.md)**  
 -   **[appspawn Module](subsys-boot-appspawn.md)**
--   **[appspawn Module for the Standard System](subsys-boot-appspawn-standard.md)**  
 -   **[bootstrap Module](subsys-boot-bootstrap.md)**  
 -   **[syspara Module](subsys-boot-syspara.md)**  
 -   **[FAQs](subsys-boot-faqs.md)**  

en/device-dev/subsystems/subsys-build-gn-kconfig-visual-config-guide.md

@@ -5,12 +5,12 @@
 ### Kconfig Visual Configuration
 Kconfig visual configuration is implemented on [Kconfiglib](https://github.com/ulfalizer/Kconfiglib) and [Kconfig](https://www.kernel.org/doc/html/latest/kbuild/kconfig-language.html#introduction). It allows customized configuration of OpenHarmony subsystem components.
 
-This function has the following advantages:
+Kconfig visual configuration has the following advantages:
 
 - Intuitive display of software component options
 - High reliability (Linux kernel and Buildroot use Kconfig for visualized configuration)
 
-### Key Concepts
+### Basic Concepts
 
 - [Kconfig](https://www.kernel.org/doc/html/latest/kbuild/kconfig-language.html#introduction): a visual configuration file format for Linux.
 
@@ -22,20 +22,20 @@ This function has the following advantages:
 
 - [Config format conversion](https://gitee.com/openharmony/build/blob/master/tools/component_tools/parse_kconf.py): converts the **config** file generated on the GUI to the standard format for compilation and build.
 
-## Procedure
+## Operation Guide
 
 1. Obtain the source code.
 
-   For details, see [Obtaining Source Code](https://gitee.com/openharmony/docs/blob/master/en/device-dev/get-code/sourcecode-acquire.md).
+   For details, see [Obtaining Source Code](../get-code/sourcecode-acquire.md).
 
 2. Set up the environment.
 
-   The Kconfiglib required for environment configuration has been embedded in the OpenHarmony hb tool. For details about how to install the hb tool, see [Install hb](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-env-setup.md#install-hb).
+   The Kconfiglib required for environment configuration has been embedded in the OpenHarmony hb tool. For details about how to install the hb tool, see [Installing hb](../quick-start/quickstart-lite-env-setup.md).
 
 3. Open the Kconfig configuration interface.
 
    ```shell
-   #Go to the build repository directory.
+   # Go to the build repository directory.
    cd build/tools/component_tools
    menuconfig kconfig
    ```
@@ -68,7 +68,7 @@ This function has the following advantages:
 
    Example:
 
-   1. Perform a global build.
+   1. Perform a full build.
 
       ```shell
       cp productdefine/common/base/base_product.json productdefine/common/products/ohos-arm64.json
@@ -91,23 +91,23 @@ This function has the following advantages:
 
       By default, the file **product.json** is generated in the current directory. You can also use `python3 parse_kconf.py --out="example/out.json"` to specify the file path.
 
-      For more operations, see `python3 parse_kconf.py -h`.
+      For more operations, run `python3 parse_kconf.py -h`.
 
 ​	
 
 ## FAQs
 
-### The latest component information is missing from the menu.
+### Latest Components Not Displayed in the Menu List
 
-The component list [productdefine/common/base/base_product.json](https://gitee.com/openharmony/productdefine_common/blob/master/base/base_product.json) is updated with product updates and iterations. As a result, the Kconfig menu does not contain the latest components.
+The component list [productdefine/common/base/base_product.json](https://gitee.com/openharmony/productdefine_common/blob/master/base/base_product.json) is updated with product updates and iterations. The Kconfig menu does not contain the latest components.
 
-Solution:
+**Solution**
 
-- Update the [Kconfig file](https://gitee.com/openharmony/build/blob/master/tools/component_tools/kconfig).
+Update the [Kconfig file](https://gitee.com/openharmony/build/blob/master/tools/component_tools/kconfig).
 
-  ```shell
-  cd build/tools/component_tools
-  python3 generate_kconfig.py
-  ```
+```shell
+cd build/tools/component_tools
+python3 generate_kconfig.py
+```
 
-  For more details, see `python3 generate_kconfig.py -h`.
+You can run `python3 generate_kconfig.py -h` to view more options.

en/device-dev/subsystems/subsys-dfx-hisysevent-overview.md

+# HiSysEvent Overview
+
+
+## Introduction
+
+HiSysEvent provides event logging APIs for OpenHarmony to record important information of key processes during system running, helping you locate faults. In addition, you can upload the log data to the cloud for big data analytics.
+
+The key modules of HiSysEvent are described as follows:
+
+- Event configuration: enables you to define HiSysEvent events in YAML files.
+
+- Trace point configuration: provides trace point APIs and supports flushing of HiSysEvent events to disks.
+
+- Event subscription: provides APIs for you to subscribe to HiSysEvent events by event domain and event name.
+
+- Event query: provides APIs for you to query HiSysEvent events by event domain and event name.
+
+- Event debugging tool: allows you to subscribe to real-time HiSysEvent events and query historical HiSysEvent events.
+
+## Reference
+
+For more information about the source code and usage of HiSysEvent, access the [HiSysEvent code repository](https://gitee.com/openharmony/hiviewdfx_hisysevent).

en/device-dev/subsystems/subsys-dfx-hisysevent.md

 # HiSysEvent Development<a name="EN-US_TOPIC_0000001195021448"></a>
 
+-   **[HiSysEvent Overview](subsys-dfx-hisysevent-overview.md)**
+
 -   **[HiSysEvent Logging Configuration](subsys-dfx-hisysevent-logging-config.md)**
 
 -   **[HiSysEvent Logging](subsys-dfx-hisysevent-logging.md)**  

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

@@ -12,6 +12,7 @@ The DFX subsystem provides the following functions:
 - HiChecker: implements defect scanning. It is applicable to standard-system devices \(reference memory ≥ 128 MiB\).
 - HiDumper: exports system information. It is applicable to standard-system devices \(reference memory ≥ 128 MiB\).
 - FaultLogger: implements crash detection. It is applicable to standard-system devices \(reference memory ≥ 128 MiB\).
+- Hiview: implements device maintenance across different platforms. It is applicable to standard-system devices \(reference memory ≥ 128 MiB\).
 
 ## Basic Concepts<a name="section5635178134811"></a>
 

en/device-dev/subsystems/subsys-dfx.md

@@ -8,3 +8,4 @@
 - **[HiSysEvent Development](subsys-dfx-hisysevent.md)**
 - **[HiDumper Development](subsys-dfx-hidumper.md)**
 - **[HiChecker Development](subsys-dfx-hichecker.md)**
+- **[Hiview Development](subsys-dfx-hiview.md)**

en/device-dev/website.md

@@ -463,7 +463,6 @@
     - [Startup](subsystems/subsys-boot-overview.md)
     - [init Module](subsystems/subsys-boot-init.md)
     - [appspawn Module](subsystems/subsys-boot-appspawn.md)
-    - [appspawn Module for the Standard System](subsystems/subsys-boot-appspawn-standard.md)
     - [bootstrap Module](subsystems/subsys-boot-bootstrap.md)
     - [syspara Module](subsystems/subsys-boot-syspara.md)
     - [FAQs](subsystems/subsys-boot-faqs.md)

en/glossary.md

@@ -29,9 +29,9 @@
 
 ## D
 
-- ### DevEco Studio for Embedded
+- ### DevEco Device Tool
 
-    Integrated development environment (IDE) for developing embedded devices.
+    A one-stop development environment and all-in-one resource platform for smart device developers. Its comprehensive capabilities span the entire process of device development, from chip template project creation and custom development resource selection to code editing, build, debugging, and burning. 
 
 - ### DMS
 

en/readme/SAMGR.md

-# System Ability Manager(<a name="EN-US_TOPIC_0000001115719369"></a>)
+# System Ability Manager<a name="EN-US_TOPIC_0000001115719369"></a>
 
 ## Introduction<a name="section11660541593"></a>
 

en/readme/user-iam.md

-# User IAM Subsystem
+# User IAM
 
 ## Introduction
 
-The user identity and access management (IAM) subsystem provides a unified framework for user credential management and user identity authentication in OpenHarmony. It allows multiple users to set their own authentication credential information and authenticates their identities based on the information set. This subsystem is widely used in security-sensitive scenarios such as screen lock. The subsystem also provides APIs for third-party developers to call the identity authentication capabilities to control user access.
+The user identity and access management (IAM) subsystem provides a unified framework for user credential management and user identity authentication in OpenHarmony. It allows multiple users to set their own authentication credential information and authenticates their identities based on the information set. 
+
+This subsystem is widely used in security-sensitive scenarios such as screen lock. It also provides APIs for developers to call the identity authentication capabilities to control user access.
 
 **Figure 1** Subsystem architecture
 

en/third-party-components/third-party-components-introduction.md

 # OpenHarmony Third-Party Components
 
-OpenHarmony third-party components are verified software that work with the OpenHarmony system to facilitate your development of OpenHarmony devices or applications. Depending on the programming language they use, these components are classified as JS/TS third-party components or C/C++ third-party components. JS/TS third-party components use JavaScript or TypeScript and are usually imported as source code or OpenHarmony npm packages. They are used in application development. C/C++ third-party components use the programming language C/C++ and are usually imported as source code or OpenHarmony hpm packages. They are used as native APIs during application development or directly compiled in the OpenHarmony OS image during device development.
+OpenHarmony third-party components are verified software that work with the OpenHarmony system to facilitate your development of OpenHarmony devices or applications. Depending on the programming language they use, these components are classified as JS/TS third-party components or C/C++ third-party components. JS/TS third-party components use the JavaScript or TypeScript programming language and are usually imported as source code or OpenHarmony npm packages. They are used in application development. C/C++ third-party components use the C/C++ programming language and are usually imported as source code or OpenHarmony hpm packages. They are used as native APIs during application development or directly compiled in the OpenHarmony OS image during device development.
 
 Currently, OpenHarmony provides UI, animation, image, multimedia, file, network, security, tool, and other third-party components.

zh-cn/application-dev/Readme-CN.md

@@ -42,8 +42,8 @@
     - [示例代码](https://gitee.com/openharmony/app_samples/blob/master/README_zh.md)
     - [Codelabs](https://gitee.com/openharmony/codelabs/blob/master/README.md)
 - API参考
-    - [组件参考（基于JS扩展的类Web开发范式）](reference/arkui-js/Readme-CN.md)
     - [组件参考（基于TS扩展的声明式开发范式）](reference/arkui-ts/Readme-CN.md)
+    - [组件参考（基于JS扩展的类Web开发范式）](reference/arkui-js/Readme-CN.md)
     - 接口
       -   [JS及TS API参考](reference/apis/Readme-CN.md)
       -   Native API