diff --git a/en/application-dev/application-models/abilitystage.md b/en/application-dev/application-models/abilitystage.md
index 4e0a273f850b4919d0964580ebed89c053c273f7..2f44f69d5810bbddf8128777f63360a1cb196fa3 100644
--- a/en/application-dev/application-models/abilitystage.md
+++ b/en/application-dev/application-models/abilitystage.md
@@ -12,7 +12,7 @@ AbilityStage is not automatically generated in the default project of DevEco Stu
 
 1. In the **ets** directory of the **Module** project, right-click and choose **New > Directory** to create a directory named **myabilitystage**.
 
-2. In the **myabilitystage** directory, right-click and choose **New > ts File** to create a file named **MyAbilityStage.ts**.
+2. In the **myabilitystage** directory, right-click and choose **New > TypeScript File** to create a file named **MyAbilityStage.ts**.
 
 3. Open the **MyAbilityStage.ts** file, and import the dependency package of AbilityStage. Customize a class that inherits from AbilityStage, and add the required lifecycle callbacks. The following code snippet adds the **onCreate()** lifecycle callback.
    
@@ -20,16 +20,27 @@ AbilityStage is not automatically generated in the default project of DevEco Stu
    import AbilityStage from '@ohos.app.ability.AbilityStage';
    
    export default class MyAbilityStage extends AbilityStage {
-       onCreate() {
-           // When the HAP of the application is loaded for the first time, initialize the module.
-       }
-       onAcceptWant(want) {
-           // Triggered only for the ability with the specified launch type.
-           return "MyAbilityStage";
-       }
+     onCreate() {
+       // When the HAP of the application is loaded for the first time, initialize the module.
+     }
+     onAcceptWant(want) {
+       // Triggered only for the ability with the specified launch type.
+       return "MyAbilityStage";
+     }
+   }
+   ```
+   
+4. Set **srcEntry** in the [module.json5 file](../quick-start/module-configuration-file.md) to the code path of the module.
+   ```json
+   {
+     "module": {
+       "name": "entry",
+       "type": "entry",
+       "srcEntry": "./ets/myabilitystage/MyAbilityStage.ts",
+       // ...
+     }
    }
    ```
-
 
 [AbilityStage](../reference/apis/js-apis-app-ability-abilityStage.md) has the lifecycle callback [onCreate()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageoncreate) and the event callbacks [onAcceptWant()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonacceptwant), [onConfigurationUpdated()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonconfigurationupdate), and [onMemoryLevel()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonmemorylevel).
 
@@ -49,9 +60,8 @@ When an application is switched to the background, it is cached in the backgroun
   import AbilityStage from '@ohos.app.ability.AbilityStage';
   
   export default class MyAbilityStage extends AbilityStage {
-      onMemoryLevel(level) {
-          // Release unnecessary memory based on the change of available system memory.
-      }
+    onMemoryLevel(level) {
+      // Release unnecessary memory based on the change of available system memory.
+    }
   }
   ```
-
diff --git a/en/application-dev/application-models/accessibilityextensionability.md b/en/application-dev/application-models/accessibilityextensionability.md
index 4c912d5e58a1b8083ba1037cccf449dd953d245c..688eaefa4bc10723d23f880dfbb4c1502cb42053 100644
--- a/en/application-dev/application-models/accessibilityextensionability.md
+++ b/en/application-dev/application-models/accessibilityextensionability.md
@@ -12,10 +12,13 @@ The **AccessibilityExtensionAbility** module provides accessibility extension ca
 
 This document is organized as follows:
 
-- [Creating an AccessibilityExtAbility File](#creating-an-accessibility-extension-service)
-- [Processing an Accessibility Event](#processing-an-accessibility-event)
-- [Declaring Capabilities of Accessibility Extension Services](#declaring-capabilities-of-accessibility-extension-services)
-- [Enabling a Custom Accessibility Extension Service](#enabling-a-custom-accessibility-extension-service)
+- [AccessibilityExtensionAbility Development](#accessibilityextensionability-development)
+  - [Creating an Accessibility Extension Service](#creating-an-accessibility-extension-service)
+    - [Creating a Project](#creating-a-project)
+    - [Creating an AccessibilityExtAbility File](#creating-an-accessibilityextability-file)
+  - [Processing an Accessibility Event](#processing-an-accessibility-event)
+  - [Declaring Capabilities of Accessibility Extension Services](#declaring-capabilities-of-accessibility-extension-services)
+  - [Enabling a Custom Accessibility Extension Service](#enabling-a-custom-accessibility-extension-service)
 
 ## Creating an Accessibility Extension Service
 
@@ -79,13 +82,13 @@ You can also process physical key events in the accessibility extension service.
 
 ## Declaring Capabilities of Accessibility Extension Services
 
-After developing the custom logic for an accessibility extension service, you must add the configuration information of the service to the corresponding module-level **module.json5** file in the project directory. In the file, the **srcEntrance** tag indicates the path to the accessibility extension service. Make sure the value of the **type** tag is fixed at **accessibility**. Otherwise, the connection to the service will fail.
+After developing the custom logic for an accessibility extension service, you must add the configuration information of the service to the corresponding module-level **module.json5** file in the project directory. In the file, the **srcEntry** tag indicates the path to the accessibility extension service. Make sure the value of the **type** tag is fixed at **accessibility**. Otherwise, the connection to the service will fail.
 
 ```json
 "extensionAbilities": [
   {
     "name": "AccessibilityExtAbility",
-    "srcEntrance": "./ets/AccessibilityExtAbility/AccessibilityExtAbility.ts",
+    "srcEntry": "./ets/AccessibilityExtAbility/AccessibilityExtAbility.ts",
     "label": "$string:MainAbility_label",
     "description": "$string:MainAbility_desc",
     "type": "accessibility",
diff --git a/en/application-dev/application-models/application-context-stage.md b/en/application-dev/application-models/application-context-stage.md
index aa40d3aedf9dbb3db775a634dbd81f60f22fed51..84188352e2b224ba24e9121dce147e39553ce61c 100644
--- a/en/application-dev/application-models/application-context-stage.md
+++ b/en/application-dev/application-models/application-context-stage.md
@@ -187,13 +187,13 @@ The base class **Context** provides [createBundleContext(bundleName:string)](../
   > **NOTE**
   >
   > To obtain the context of another application:
-  >
+  > 
   > - Request the **ohos.permission.GET_BUNDLE_INFO_PRIVILEGED** permission. For details, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file).
-  >
+  > 
   > - This is a system API and cannot be called by third-party applications.
 
   For example, application information displayed on the home screen includes the application name and icon. The home screen application calls the foregoing method to obtain the context information, so as to obtain the resource information including the application name and icon.
-
+  
   ```ts
   import UIAbility from '@ohos.app.ability.UIAbility';
   
@@ -248,7 +248,7 @@ The base class **Context** provides [createBundleContext(bundleName:string)](../
 
 In the DFX statistics scenario of an application, if you need to collect statistics on the stay duration and access frequency of a page, you can subscribe to UIAbility lifecycle changes in a process.
 
-[ApplicationContext](../reference/apis/js-apis-inner-application-applicationContext) provides APIs for subscribing to UIAbility lifecycle changes in a process. When the UIAbility lifecycle changes in a process, for example, being created or destroyed, becoming visible or invisible, or gaining or losing focus, the corresponding callback is triggered. Each time the callback is registered, a listener lifecycle ID is returned, with the value incremented by 1 each time. When the number of listeners exceeds the upper limit (2^63-1), **-1** is returned. The following uses [UIAbilityContext](../reference/apis/js-apis-inner-application-uiAbilityContext.md) as an example.
+[ApplicationContext](../reference/apis/js-apis-inner-application-applicationContext.md) provides APIs for subscribing to UIAbility lifecycle changes in a process. When the UIAbility lifecycle changes in a process, for example, being created or destroyed, becoming visible or invisible, or gaining or losing focus, the corresponding callback is triggered. Each time the callback is registered, a listener lifecycle ID is returned, with the value incremented by 1 each time. When the number of listeners exceeds the upper limit (2^63-1), **-1** is returned. The following uses [UIAbilityContext](../reference/apis/js-apis-inner-application-uiAbilityContext.md) as an example.
 
 
 ```ts
@@ -308,7 +308,7 @@ export default class EntryAbility extends UIAbility {
     // Obtain the application context.
     let applicationContext = this.context.getApplicationContext();
     // Register the application lifecycle callback.
-    this.lifecycleId = applicationContext.on('Lifecycle', abilityLifecycleCallback);
+    this.lifecycleId = applicationContext.on('abilityLifecycle', abilityLifecycleCallback);
     console.log(TAG, `register callback number: ${this.lifecycleId}`);
   }
 
diff --git a/en/application-dev/application-models/arkts-ui-widget-update-by-status.md b/en/application-dev/application-models/arkts-ui-widget-update-by-status.md
index 154eb03701ba2a1589c5ca81fd4d8e9edcf0865b..8952b8dff4ecdd3acad6b1a65513d8e529c4dc70 100644
--- a/en/application-dev/application-models/arkts-ui-widget-update-by-status.md
+++ b/en/application-dev/application-models/arkts-ui-widget-update-by-status.md
@@ -74,7 +74,7 @@ Multiple widgets of the same application can be configured to implement differen
         }
   
         Row() {// Content that is updated only in state A
-          Text('状态A: ')
+          Text('State A: ')
           Text(this.textA)
         }
   
diff --git a/en/application-dev/application-models/common-event-static-subscription.md b/en/application-dev/application-models/common-event-static-subscription.md
index 013d7709e8c1588571e5c53f2a60ea012ee4f1fa..a545f6464b052cb20bd931b21820d623ad13f9c6 100644
--- a/en/application-dev/application-models/common-event-static-subscription.md
+++ b/en/application-dev/application-models/common-event-static-subscription.md
@@ -22,8 +22,6 @@ A static subscriber is started once it receives a target event published by the
 
    You can implement service logic in the **onReceiveEvent** callback.
 
-   
-
 2. Project Configuration for a Static Subscriber
 
    After writing the static subscriber code, configure the subscriber in the **module.json5** file. The configuration format is as follows:
@@ -35,12 +33,12 @@ A static subscriber is started once it receives a target event published by the
        "extensionAbilities": [
          {
            "name": "StaticSubscriber",
-           "srcEntrance": "./ets/StaticSubscriber/StaticSubscriber.ts",
+           "srcEntry": "./ets/StaticSubscriber/StaticSubscriber.ts",
            "description": "$string:StaticSubscriber_desc",
            "icon": "$media:icon",
            "label": "$string:StaticSubscriber_label",
            "type": "staticSubscriber",
-           "visible": true,
+           "exported": true,
            "metadata": [
              {
                "name": "ohos.extension.staticSubscriber",
@@ -56,7 +54,7 @@ A static subscriber is started once it receives a target event published by the
 
    Pay attention to the following fields in the JSON file:
 
-   - **srcEntrance**: entry file path of the ExtensionAbility, that is, the file path of the static subscriber declared in Step 2.
+   - **srcEntry**: entry file path of the ExtensionAbility, that is, the file path of the static subscriber declared in Step 2.
 
    - **type**: ExtensionAbility type. For a static subscriber, set this field to **staticSubscriber**.
 
@@ -98,5 +96,5 @@ A static subscriber is started once it receives a target event published by the
         "ohos.extension.staticSubscriber",
         "xxx"
     }
-    ```
+   ```
 
diff --git a/en/application-dev/application-models/datashareextensionability.md b/en/application-dev/application-models/datashareextensionability.md
index f671848f890277af92fc23869c5db0d57b02a316..bea3de69c6d7ad375206fb1d53bcc36c2624989d 100644
--- a/en/application-dev/application-models/datashareextensionability.md
+++ b/en/application-dev/application-models/datashareextensionability.md
@@ -1,4 +1,4 @@
 # DataShareExtensionAbility (for System Applications Only)
 
 
-DataShareExtensionAbility provides the data sharing capability. System applications can implement a DataShareExtensionAbility or access an existing DataShareExtensionAbility in the system. Third-party applications can only access an existing DataShareExtensionAbility. For details, see [DataShare Development](../database/database-datashare-guidelines.md).
+DataShareExtensionAbility provides the data sharing capability. System applications can implement a DataShareExtensionAbility or access an existing DataShareExtensionAbility in the system. Third-party applications can only access an existing DataShareExtensionAbility. For details, see [Cross-Application Data Sharing Overview](../database/share-device-data-across-apps-overview.md).
diff --git a/en/application-dev/application-models/enterprise-extensionAbility.md b/en/application-dev/application-models/enterprise-extensionAbility.md
index 18d5ec828126a2d11b57bf4dd482c4af56fa14bc..da8054e54284cc3a32af5ea6acaafc9eabc01561 100644
--- a/en/application-dev/application-models/enterprise-extensionAbility.md
+++ b/en/application-dev/application-models/enterprise-extensionAbility.md
@@ -2,12 +2,11 @@
 
 ## Introduction to EnterpriseAdminExtensionAbility
 
-EnterpriseAdminExtensionAbility is a mandatory component for Mobile Device Management (MDM) applications. When developing MDM applications for enterprises, you need to inherit EnterpriseAdminExtensionAbility and implement MDM service logic in the EnterpriseAdminExtensionAbility instance. EnterpriseAdminExtensionAbility implements notifications of system management status changes and defines the callbacks when a device administrator application is enabled or disabled or an application is installed or uninstalled.
+EnterpriseAdminExtensionAbility is a mandatory component for Mobile Device Management (MDM) applications. When developing MDM applications for enterprises, you need to inherit EnterpriseAdminExtensionAbility and implement MDM service logic in the EnterpriseAdminExtensionAbility instance. EnterpriseAdminExtensionAbility implements notifications of system management status changes and defines the callbacks for when a device administrator application is enabled or disabled or an application is installed or uninstalled.
 
 ## Constraints
 
-  EnterpriseAdminExtensionAbility is applicable only to enterprise administrator applications.
-  
+EnterpriseAdminExtensionAbility is applicable only to enterprise administrator applications.
 
 ## Observing Activation/Deactivation of a Device Administrator Application and Installation/Removal of an Application
 
@@ -24,59 +23,59 @@ EnterpriseAdminExtensionAbility is a mandatory component for Mobile Device Manag
 ### Available APIs
 
 | Class                           | API                                 | Description                        |
-| :------------------------------ | ----------------------------------------- | ---------------------------- |
+| ------------------------------ | ----------------------------------------- | ---------------------------- |
+| EnterpriseAdminExtensionAbility | onAdminEnabled(): void                    | Called when a device administrator application is activated.  |
 | EnterpriseAdminExtensionAbility | onAdminDisabled(): void                   | Called when a device administrator application is deactivated.|
 | EnterpriseAdminExtensionAbility | onBundleAdded(bundleName: string): void   | Called when an application is installed on a device.            |
-| EnterpriseAdminExtensionAbility | onAdminEnabled(): void                    | Called when a device administrator application is activated.  |
 | EnterpriseAdminExtensionAbility | onBundleRemoved(bundleName: string): void | Called when an application is removed from a device.            |
 
 ### How to Develop
 
 To implement EnterpriseAdminExtensionAbility, you need to activate the device administrator application and create **ExtensionAbility** in the code directory of the device administrator application. The procedure is as follows:
 
-1. In the **ets** directory of the **Module** project, right-click and choose **New > Directory** to create a directory named **EnterpriseExtAbility**.
+1. In the **ets** directory of the target module, right-click and choose **New > Directory** to create a directory named **EnterpriseExtAbility**.
 2. Right-click the **EnterpriseExtAbility** directory, and choose **New > TypeScript File** to create a file named **EnterpriseExtAbility.ts**.
 3. Open the **EnterpriseExtAbility.ts** file and import the **EnterpriseAdminExtensionAbility** module. Inherit the **EnterpriseAdminExtensionAbility** module to the custom class and add application notification callbacks, such as **onAdminEnabled()** and **onAdminDisabled()**. When the device administrator application is activated or deactivated, the device administrator can receive notifications.
 
-```ts
-import EnterpriseAdminExtensionAbility from '@ohos.enterprise.EnterpriseAdminExtensionAbility';
-
-export default class EnterpriseAdminAbility extends EnterpriseAdminExtensionAbility {
-
-    onAdminEnabled() {
-        console.info("onAdminEnabled");
-    }
-
-    onAdminDisabled() {
-        console.info("onAdminDisabled");
-    }
-    
-    onBundleAdded(bundleName: string) {
-        console.info("EnterpriseAdminAbility onBundleAdded bundleName:" + bundleName)
-    }
-
-    onBundleRemoved(bundleName: string) {
-        console.info("EnterpriseAdminAbility onBundleRemoved bundleName" + bundleName)
-    }
-};
-```
-
-​	4. Register **ServiceExtensionAbility** in the [**module.json5**](../quick-start/module-configuration-file.md) file corresponding to the project module. Set **type** to **enterpriseAdmin** and **srcEntrance** to the path of the ExtensionAbility code.
-
-```ts
-"extensionAbilities": [
-      {
-        "name": "ohos.samples.enterprise_admin_ext_ability",
-        "type": "enterpriseAdmin",
-        "visible": true,
-        "srcEntrance": "./ets/enterpriseextability/EnterpriseAdminAbility.ts"
-      }
-    ]
-```
+   ```ts
+   import EnterpriseAdminExtensionAbility from '@ohos.enterprise.EnterpriseAdminExtensionAbility';
+
+   export default class EnterpriseAdminAbility extends EnterpriseAdminExtensionAbility {
+
+       onAdminEnabled() {
+           console.info("onAdminEnabled");
+       }
+
+       onAdminDisabled() {
+           console.info("onAdminDisabled");
+       }
+       
+       onBundleAdded(bundleName: string) {
+           console.info("EnterpriseAdminAbility onBundleAdded bundleName:" + bundleName)
+       }
+
+       onBundleRemoved(bundleName: string) {
+           console.info("EnterpriseAdminAbility onBundleRemoved bundleName" + bundleName)
+       }
+   };
+   ```
+
+4. Register **ServiceExtensionAbility** in the [**module.json5**](../quick-start/module-configuration-file.md) file corresponding to the project module. Set **type** to **enterpriseAdmin** and **srcEntry** to the path of the ExtensionAbility code.
+
+   ```ts
+   "extensionAbilities": [
+         {
+           "name": "ohos.samples.enterprise_admin_ext_ability",
+           "type": "enterpriseAdmin",
+           "exported": true,
+           "srcEntry": "./ets/enterpriseextability/EnterpriseAdminAbility.ts"
+         }
+       ]
+   ```
 
 ## Example
 
-Use **subscribeManagedEvent()** and **unsubscribeManagedEvent()** in the @ohos.enterprise.adminManager module to subscribe to application installation and removal events. When an application is installed or removed, the MDM application is notified of the event. Then, the MDM application reports the event in the callback to notify the enterprise administrator.
+Use **subscribeManagedEvent** in the **@ohos.enterprise.adminManager** module to subscribe to application installation and removal events. When an application is installed or removed, the MDM application is notified of the event. Then, the MDM application reports the event in the callback to notify the enterprise administrator. To unsubscribe from events, use **unsubscribeManagedEvent**.
 
 ```ts
   @State managedEvents: Array<adminManager.ManagedEvent> = [0,1]
@@ -105,3 +104,4 @@ Use **subscribeManagedEvent()** and **unsubscribeManagedEvent()** in the @ohos.e
     })
   }
 ```
+
diff --git a/en/application-dev/application-models/figures/standard-mode.png b/en/application-dev/application-models/figures/standard-mode.png
deleted file mode 100644
index fc903e6c1be80d3c00281d00d9ab0a1e334d7724..0000000000000000000000000000000000000000
Binary files a/en/application-dev/application-models/figures/standard-mode.png and /dev/null differ
diff --git a/en/application-dev/application-models/figures/uiability-launch-type1.gif b/en/application-dev/application-models/figures/uiability-launch-type1.gif
new file mode 100644
index 0000000000000000000000000000000000000000..d31a51a1aa97d32ee0ee7df4803378c1b7124119
Binary files /dev/null and b/en/application-dev/application-models/figures/uiability-launch-type1.gif differ
diff --git a/en/application-dev/application-models/figures/uiability-launch-type1.png b/en/application-dev/application-models/figures/uiability-launch-type1.png
deleted file mode 100644
index c4f5aa4b9a988d8e7148b504c4dcc163961cb103..0000000000000000000000000000000000000000
Binary files a/en/application-dev/application-models/figures/uiability-launch-type1.png and /dev/null differ
diff --git a/en/application-dev/application-models/figures/uiability-launch-type2.gif b/en/application-dev/application-models/figures/uiability-launch-type2.gif
new file mode 100644
index 0000000000000000000000000000000000000000..ecb3c413e3af2f92ef6834024d0d413e30c2419f
Binary files /dev/null and b/en/application-dev/application-models/figures/uiability-launch-type2.gif differ
diff --git a/en/application-dev/application-models/figures/uiability-launch-type2.png b/en/application-dev/application-models/figures/uiability-launch-type2.png
deleted file mode 100644
index 6f0e43d24f745aee41601cc48f4bc138572fbeb5..0000000000000000000000000000000000000000
Binary files a/en/application-dev/application-models/figures/uiability-launch-type2.png and /dev/null differ
diff --git a/en/application-dev/application-models/figures/uiability-launch-type3.gif b/en/application-dev/application-models/figures/uiability-launch-type3.gif
new file mode 100644
index 0000000000000000000000000000000000000000..029e8ba7e90eb836f8466c604d4fcf8171ffec6e
Binary files /dev/null and b/en/application-dev/application-models/figures/uiability-launch-type3.gif differ
diff --git a/en/application-dev/application-models/hop-multi-device-collaboration.md b/en/application-dev/application-models/hop-multi-device-collaboration.md
index 7cf66fbab7a98b109de3f9ffcc2fc7b7a2ecd127..721e135179810539bf6782489b67d2619536e8d2 100644
--- a/en/application-dev/application-models/hop-multi-device-collaboration.md
+++ b/en/application-dev/application-models/hop-multi-device-collaboration.md
@@ -187,7 +187,7 @@ On device A, touch the **Start** button provided by the initiator application to
    
    // ...
    
-   // context is the UIAbilityContext of the initiator UIAbility.
+   // context is the AbilityContext of the initiator UIAbility.
    this.context.startAbilityForResult(want).then((data) => {
        if (data?.resultCode === RESULT_CODE) {
            // Parse the information returned by the target UIAbility.
@@ -384,12 +384,12 @@ The following describes how to implement multi-device collaboration through cros
        ```json
        "abilities":[{
            "name": ".CalleeAbility",
-           "srcEntrance": "./ets/CalleeAbility/CalleeAbility.ts",
+           "srcEnty": "./ets/CalleeAbility/CalleeAbility.ts",
            "launchType": "singleton",
            "description": "$string:CalleeAbility_desc",
            "icon": "$media:icon",
            "label": "$string:CalleeAbility_label",
-           "visible": true
+           "exported": true
        }]
        ```
 
@@ -459,7 +459,7 @@ The following describes how to implement multi-device collaboration through cros
        
            onDestroy() {
                try {
-                this.callee.off(MSG_SEND_METHOD)
+                   this.callee.off(MSG_SEND_METHOD)
                } catch (error) {
                    console.error(TAG, `${MSG_SEND_METHOD} unregister failed with error ${JSON.stringify(error)}`)
                }
@@ -491,7 +491,7 @@ The following describes how to implement multi-device collaboration through cros
                if (data != null) {
                    caller = data
                    console.info('get remote caller success')
-                   // Register the onRelease listener of the CallerAbility.
+                   // Register the onRelease() listener of the CallerAbility.
                    caller.onRelease((msg) => {
                        console.info(`remote caller onRelease is called ${msg}`)
                    })
diff --git a/en/application-dev/application-models/inputmethodextentionability.md b/en/application-dev/application-models/inputmethodextentionability.md
index 8a7856f402bf30b1610521e3cf05dda7145c3509..2b3910707ecdb6f964822380a85b14857ec8fd29 100644
--- a/en/application-dev/application-models/inputmethodextentionability.md
+++ b/en/application-dev/application-models/inputmethodextentionability.md
@@ -54,7 +54,7 @@ The minimum template contains four files: **KeyboardController.ts**, **InputMeth
 
 1. **InputMethodService.ts** file:
 
-   In this file, add the dependency package for importing InputMethodExtensionAbility. Customize a class that inherits from InputMethodExtensionAbility and add the required lifecycle callbacks.
+   In the **InputMethodService.ts** file, add the dependency package for importing InputMethodExtensionAbility. Customize a class that inherits from InputMethodExtensionAbility and add the required lifecycle callbacks.
 
    ```ts
    import InputMethodExtensionAbility from '@ohos.InputMethodExtensionAbility';
@@ -233,7 +233,7 @@ The minimum template contains four files: **KeyboardController.ts**, **InputMeth
 
    Add the path to this file to the **src** field in the **resources/base/profile/main_pages.json** file.
 
-   ```ets
+   ```ts
    import { numberSourceListData, sourceListType } from './keyboardKeyData'
    
    @Component
@@ -342,7 +342,7 @@ The minimum template contains four files: **KeyboardController.ts**, **InputMeth
    }
    ```
 
-   Register the InputMethodExtensionAbility in the [module.json5 file](../quick-start/module-configuration-file.md) corresponding to the target module. Set **type** to **"inputMethod"** and **srcEntrance** to the code path of the InputMethodExtensionAbility component.
+   Register the InputMethodExtensionAbility in the [module.json5 file](../quick-start/module-configuration-file.md) corresponding to the target module. Set **type** to **"inputMethod"** and **srcEntry** to the code path of the InputMethodExtensionAbility component.
 
    ```ts
    {
@@ -353,9 +353,9 @@ The minimum template contains four files: **KeyboardController.ts**, **InputMeth
            "description": "inputMethod",
            "icon": "$media:icon",
            "name": "InputMethodExtAbility",
-           "srcEntrance": "./ets/inputmethodextability/InputMethodService.ts",
+           "srcEntry": "./ets/inputmethodextability/InputMethodService.ts",
            "type": "inputMethod",
-           "visible": true,
+           "exported": true,
          }
        ]
      }
diff --git a/en/application-dev/application-models/lifecycleapp-switch.md b/en/application-dev/application-models/lifecycleapp-switch.md
index 892a8915bfed9927c2707364bdaffa1547f71bf6..9d89597ef5a77246ec7450261916061062d24d8d 100644
--- a/en/application-dev/application-models/lifecycleapp-switch.md
+++ b/en/application-dev/application-models/lifecycleapp-switch.md
@@ -1,17 +1,17 @@
 # LifecycleApp Switching
 
 
-  | API in the FA Model| Corresponding d.ts File in the Stage Model| Corresponding API in the Stage Model| 
+| API in the FA Model| Corresponding d.ts File in the Stage Model| Corresponding API in the Stage Model|
 | -------- | -------- | -------- |
 | onShow?(): void; | \@ohos.window.d.ts | [on(eventType: 'windowStageEvent', callback: Callback&lt;WindowStageEventType&gt;): void;](../reference/apis/js-apis-window.md#onwindowstageevent9)<br>Listens for the switching to the [foreground](../reference/apis/js-apis-window.md#windowstageeventtype9).|
 | onHide?(): void; | \@ohos.window.d.ts | [on(eventType: 'windowStageEvent', callback: Callback&lt;WindowStageEventType&gt;): void;](../reference/apis/js-apis-window.md#onwindowstageevent9)<br>Listens for the switching to the [background](../reference/apis/js-apis-window.md#windowstageeventtype9).|
-| onDestroy?(): void; | \@ohos.app.ability.UIAbility.d.ts | [onDestroy(): void;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityondestroy) | 
+| onDestroy?(): void; | \@ohos.app.ability.UIAbility.d.ts | [onDestroy(): void;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityondestroy) |
 | onCreate?(): void; | \@ohos.app.ability.UIAbility.d.ts | [onCreate(want: Want, param: AbilityConstant.LaunchParam): void;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncreate) |
 | onWindowDisplayModeChanged?(isShownInMultiWindow: boolean, newConfig: resourceManager.Configuration): void; | There is no corresponding API in the stage model.| No corresponding API is provided.|
 | onStartContinuation?(): boolean; | There is no corresponding API in the stage model.| In the stage model, an application does not need to detect whether the continuation is successful (detected when the application initiates the continuation request). Therefore, the **onStartContinuation()** callback is deprecated.|
 | onSaveData?(data: Object): boolean; | \@ohos.app.ability.UIAbility.d.ts | [onContinue(wantParam : {[key: string]: any}): AbilityConstant.OnContinueResult;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncontinue) |
 | onCompleteContinuation?(result: number): void; | application\ContinueCallback.d.ts | [onContinueDone(result: number): void;](../reference/apis/js-apis-distributedMissionManager.md#continuecallback) |
-| onRestoreData?(data: Object): void; | \@ohos.app.ability.UIAbility.d.ts | [onCreate(want: Want, param: AbilityConstant.LaunchParam): void;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncreate)<br>[onNewWant(want: Want, launchParams: AbilityConstant.LaunchParam): void;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityonnewwant)<br>In standard or singleton mode, the target ability completes data restoration in the **onCreate()** callback. In the callback, **launchParam.launchReason** is used to determine whether it is a continuation-based launch scenario. If it is, the data saved before continuation can be obtained from the **want** parameter.|
+| onRestoreData?(data: Object): void; | \@ohos.app.ability.UIAbility.d.ts | [onCreate(want: Want, param: AbilityConstant.LaunchParam): void;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncreate)<br>[onNewWant(want: Want, launchParams: AbilityConstant.LaunchParam): void;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityonnewwant)<br>In multiton or singleton mode, the target ability completes data restoration in the **onCreate()** callback. In the callback, **launchParam.launchReason** is used to determine whether it is a continuation-based launch scenario. If it is, the data saved before continuation can be obtained from the **want** parameter.|
 | onRemoteTerminated?(): void; | application\ContinueCallback.d.ts | [onContinueDone(result: number): void;](../reference/apis/js-apis-distributedMissionManager.md#continuecallback) |
 | onSaveAbilityState?(outState: PacMap): void; | \@ohos.app.ability.UIAbility.d.ts | [onSaveState(reason: AbilityConstant.StateType, wantParam : {[key: string]: any}): AbilityConstant.OnSaveResult;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityonsavestate) |
 | onRestoreAbilityState?(inState: PacMap): void; | \@ohos.app.ability.UIAbility.d.ts | [onCreate(want: Want, param: AbilityConstant.LaunchParam): void;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncreate)<br>After the application is restarted, the **onCreate()** callback is triggered. In the callback, **launchParam.launchReason** is used to determine whether it is a self-recovery scenario. If it is, the data saved before the restart can be obtained from the **want** parameter.|
diff --git a/en/application-dev/application-models/mission-management-launch-type.md b/en/application-dev/application-models/mission-management-launch-type.md
index 72b6dbf80df2628119ebcc29339ed7e4b70e9a50..6bad0ba0079e7087406000cd1a5e5ffb54a4f17c 100644
--- a/en/application-dev/application-models/mission-management-launch-type.md
+++ b/en/application-dev/application-models/mission-management-launch-type.md
@@ -8,16 +8,19 @@ The following describes how the mission list manager manages the UIAbility insta
 - **singleton**: Only one UIAbility instance exists for an application.
   
   **Figure 1** Missions and singleton mode
+  
   ![mission-and-singleton](figures/mission-and-singleton.png)
   
-- **standard**: Each time **startAbility()** is called, a UIAbility instance is created in the application process.
+- **multiton**: Each time **startAbility()** is called, a **UIAbility** instance is created in the application process.
+  
+  **Figure 2** Missions and multiton mode
   
-  **Figure 2** Missions and standard mode
-  ![mission-and-standard](figures/mission-and-standard.png)
+  ![mission-and-multiton](figures/mission-and-standard.png)
   
-- **specified**: The ([onAcceptWant](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonacceptwant)) method of [AbilityStage](abilitystage.md) determines whether to create an instance.
+- **specified**: The ([onAcceptWant()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonacceptwant)) method of [AbilityStage](abilitystage.md) determines whether to create an instance.
   
   **Figure 3** Missions and specified mode
+  
   ![mission-and-specified](figures/mission-and-specified.png)
 
 
diff --git a/en/application-dev/application-models/mission-management-overview.md b/en/application-dev/application-models/mission-management-overview.md
index e371e8380fbd7e181e13f1d5f5e7487b15eb9ff1..8d219cf935b0f4cae4093b33ed760a3603538ecc 100644
--- a/en/application-dev/application-models/mission-management-overview.md
+++ b/en/application-dev/application-models/mission-management-overview.md
@@ -13,6 +13,7 @@ Before getting started with the development of mission management, be familiar w
 - MissionListManager: system mission management module that maintains all the MissionLists and is consistent with the list in **Recents**.
   
   **Figure 1** Mission management 
+  
   ![mission-list-manager](figures/mission-list-manager.png)
 
 
diff --git a/en/application-dev/application-models/module-switch.md b/en/application-dev/application-models/module-switch.md
index f3d5bd1c643a21945c06bdda69657ff823168907..f86d416597febe296adf6bd38b6a3d87a86fdda7 100644
--- a/en/application-dev/application-models/module-switch.md
+++ b/en/application-dev/application-models/module-switch.md
@@ -8,7 +8,7 @@ When switching an application from the FA model to the stage model, you must mig
 | Field Name in the FA Model| Field Description| Field Name in the Stage Model| Difference|
 | -------- | -------- | -------- | -------- |
 | mainAbility | Ability displayed on the Service Center icon. When the resident process is started, the **mainAbility** is started.| mainElement | The field name is changed, and the stage mode does not use the period (.) in ability names.|
-| package | Package name of the HAP file, which must be unique in the application.| / | The stage model uses **name** to ensure application uniqueness. To ensure a successful switching from the FA model to the stage model, **name** in the stage model must be the same as **package** in the FA model.|
+| package | Package name of the HAP file, which must be unique in the application.| / | The stage model uses **name** to ensure application uniqueness. |
 | name | Class name of the HAP file.| / | This configuration is not enabled in the FA model, and the stage model does not have such a field.|
 | supportedModes | Modes supported by the application. Currently, only the **drive** mode is defined.| / | This configuration is deprecated in the stage model.|
 | moduleName in the distro object| Name of the current HAP file.<br>moduleName in the distro object.| name | The field name is changed.|
@@ -21,11 +21,12 @@ When switching an application from the FA model to the stage model, you must mig
 | shortcuts | Shortcuts of the application.| shortcut_config.json| In the stage model, the **shortcut_config.json** file is defined in **resources/base/profile** in the development view.|
 | reqPermissions | Permissions that the application requests from the system when it is running.| requestPermissions | The field name is changed.|
 | colorMode | Color mode of the application.| / | This configuration is not supported in the stage model.|
-| distroFilter | Distribution rules of the application.| distroFilter_config.json| In the stage model, the **distroFilter_config.json** file is defined in **resources/base/profile** in the development view.|
+| distributionFilter | Distribution rules of the application.| distroFilter_config.json| In the stage model, the **distroFilter_config.json** file is defined in **resources/base/profile** in the development view.|
 | reqCapabilities | Device capabilities required for running the application.| / | This configuration is not supported in the stage model.|
 | commonEvents | Common events.| common_event_config.json| In the stage model, the **common_event_config.json** file is defined in **resources/base/profile** in the development view.|
 | entryTheme | Keyword of an OpenHarmony internal theme.| / | This configuration is not supported in the stage model.|
 
+
 ### Table 2 metaData Comparison
 
 | Field Name Under metaData in the FA Model| Field Description| Field Name Under metaData in the Stage Model| Difference|
@@ -40,7 +41,8 @@ When switching an application from the FA model to the stage model, you must mig
 | -------- | -------- | -------- | -------- |
 | name | Key name that identifies a data item. The value is a string with a maximum of 255 bytes.| name | None.|
 | value | Value of the data item. The value is a string with a maximum of 255 bytes.| value | None.|
-| extra | Format of the current custom data. The value is the resource value of **extra**.| resource | The field name is changed. For details, see [Table 4](#table-4-metadata-examples).|
+| extra | Format of the current custom data. The value is the resource value of **extra**.| resource | The field name is changed. For details, see [Table 4](#table 4-metadata-examples).|
+
 
 ### Table 4 metaData Examples
 
@@ -69,5 +71,5 @@ When switching an application from the FA model to the stage model, you must mig
 | formsEnabled | Whether the ability can provide widgets.| / | This configuration is not supported in the stage model.|
 | forms | Information about the widgets used by the ability. This field is valid only when **formsEnabled** is set to **true**.| form_config.json| In the stage model, the **form_config.json** file is defined in **resources/base/profile** in the development view.|
 | srcLanguage | Programming language used to develop the ability.| / | This configuration is not supported in the stage model.|
-| srcPath | Path of the JS component code corresponding to the ability.| srcEntrance | Path of the JS code corresponding to the ability.|
+| srcPath | Path of the JS component code corresponding to the ability.| srcEnty | Path of the JS code corresponding to the ability.|
 | uriPermission | Application data that the ability can access.| / | This configuration is not supported in the stage model.|
diff --git a/en/application-dev/application-models/pageability-launch-type.md b/en/application-dev/application-models/pageability-launch-type.md
index 5241a7cabefbf3e68e6a3f413b8892ef5f6ff8d3..3b75ff6a60899f19f08aad5235fb3dc49632cb01 100644
--- a/en/application-dev/application-models/pageability-launch-type.md
+++ b/en/application-dev/application-models/pageability-launch-type.md
@@ -5,10 +5,10 @@ Depending on the launch type, the action performed when the PageAbility starts d
 
 **Table 1** PageAbility launch types
 
-| Launch Type| Description|
-| -------- | -------- |
-| singleton | Each time **startAbility()** is called, if an ability instance of this type already exists in the application process, the instance is reused. There is only one ability instance of this type in **Recents**.<br>A typical scenario is as follows: When a user opens a video playback application and watches a video, returns to the home screen, and opens the video playback application again, the video that the user watched before returning to the home screen is still played.|
-| standard | Default type. Each time **startAbility()** is called, a new ability instance is created in the application process. Multiple ability instances of this type are displayed in **Recents**.<br>A typical scenario is as follows: When a user opens a document application and touches **New**, a new document task is created. Multiple new document missions are displayed in **Recents**.|
+| Launch Type| Meaning        | Description|
+| -------- | -------- | -------- |
+| singleton | Singleton mode| Each time **startAbility()** is called, if an ability instance of this type already exists in the application process, the instance is reused. There is only one ability instance of this type in **Recents**.<br>A typical scenario is as follows: When a user opens a video playback application and watches a video, returns to the home screen, and opens the video playback application again, the video that the user watched before returning to the home screen is still played.|
+| standard | Multiton mode| Default type. Each time **startAbility()** is called, a new ability instance is created in the application process. Multiple ability instances of this type are displayed in **Recents**.<br>A typical scenario is as follows: When a user opens a document application and touches **New**, a new document task is created. Multiple new document missions are displayed in **Recents**.|
 
 
 You can set **launchType** in the **config.json** file to configure the launch type. The sample code is as follows:
@@ -19,8 +19,8 @@ You can set **launchType** in the **config.json** file to configure the launch t
     // ...
     "abilities": [
       {
-        // singleton mode.
-        // standard mode.
+        // singleton means the singleton mode.
+        // standard means the multiton mode.
         "launchType": "standard",
         // ...
       }
@@ -30,7 +30,8 @@ You can set **launchType** in the **config.json** file to configure the launch t
 ```
 
 
-When the PageAbility is started for the first time (either in standard or singleton mode), the [PageAbility lifecycle callbacks](pageability-lifecycle.md#table13118194914476) are triggered. When it is not started for the first time in singleton mode, the **onNewWant()** callback (as described in the table below) is triggered, but the **onCreate()** callback is not.
+When the PageAbility is started in multiton mode or it is started in singleton mode for the first time, the [PageAbility lifecycle callbacks](pageability-lifecycle.md#table13118194914476) are triggered. When it is not started for the first time in singleton mode, the **onNewWant()** callback (as described in the table below) is triggered, but the **onCreate()** callback is not.
+
 
 **Table 2** Callbacks specific to the singleton mode
 
diff --git a/en/application-dev/application-models/process-model-stage.md b/en/application-dev/application-models/process-model-stage.md
index bbfa0602aecb127c5e484f0ebbdcb166f81310f7..03da480722de124a1ede58da52e74cd48c5f23f0 100644
--- a/en/application-dev/application-models/process-model-stage.md
+++ b/en/application-dev/application-models/process-model-stage.md
@@ -15,7 +15,8 @@ The OpenHarmony process model is shown below.
 
 > NOTE
 >
-> You can create ServiceExtensionAbility and DataShareExtensionAbility only for system applications.
+> - You can create ServiceExtensionAbility and DataShareExtensionAbility only for system applications.
+> - To view information about all running processes, run the **hdc shell** command to enter the shell CLI of the device, and run the **ps -ef** command.
 
 A system application can apply for multi-process permissions (as shown in the following figure) and configure a custom process for an HAP. UIAbility, DataShareExtensionAbility, and ServiceExtensionAbility in the HAP run in the custom process. Different HAPs run in different processes by configuring different process names.
 
diff --git a/en/application-dev/application-models/redirection-rules.md b/en/application-dev/application-models/redirection-rules.md
index d7456653640942bca333a28f7f6d5262ec4d63f3..12926c13985dbc2a535206aa4f998df2c44b2ecb 100644
--- a/en/application-dev/application-models/redirection-rules.md
+++ b/en/application-dev/application-models/redirection-rules.md
@@ -7,13 +7,14 @@ Generally, UI redirection within an application is triggered by users. However,
 The PageAbility has a UI. It can use **startAbility()** to start an ability that has a UI and is visible to users.
 
 
-The **visible** field under **abilities** in the **config.json** file specifies whether an ability can be started by other application components.
+The **exported** field under **abilities** in the **config.json** file specifies whether an ability can be started by other application components.
 
-**Table 1** Description of visible
+
+**Table 1** Description of exported
 
 | Name| Description| Initial Value Allowed|
 | -------- | -------- | -------- |
-| visible | Whether the ability can be called by other applications.<br>**true**: The ability can be called by any application.<br>**false**: The ability can be called only by other components of the same application.| Yes (initial value: **false**)|
+| exported | Whether the ability can be called by other applications.<br>**true**: The ability can be called by any application.<br>**false**: The ability can be called only by other components of the same application.| Yes (initial value: **false**)|
 
 
 To enable an ability to be called by any application, configure the **config.json** file as follows:
@@ -24,7 +25,7 @@ To enable an ability to be called by any application, configure the **config.jso
     // ...
     "abilities": [
       {
-        "visible": "true",
+        "exported": "true",
         // ...
       }
     ]
@@ -33,4 +34,4 @@ To enable an ability to be called by any application, configure the **config.jso
 ```
 
 
-If the ability contains **skills**, you are advised to set **visible** to **true** so that the ability can be [implicitly started](explicit-implicit-want-mappings.md#matching-rules-of-implicit-want) by other applications. If this attribute is set to **false**, the system returns **PERMISSION_DENIED** when other applications attempt to start the ability. In this case, a system application can request the [START_INVISIBLE_ABILITY](../security/permission-list.md) permission to start the ability. Example abilities with **visible** set to **false** are home screen, voice assistant, or search assistant.
+If the ability contains **skills**, you are advised to set **exported** to **true** so that the ability can be [implicitly started](explicit-implicit-want-mappings.md#matching-rules-of-implicit-want) by other applications. If this attribute is set to **false**, the system returns **PERMISSION_DENIED** when other applications attempt to start the ability. In this case, a system application can request the [START_INVISIBLE_ABILITY](../security/permission-list.md) permission to start the ability. Example abilities with **exported** set to **false** are home screen, voice assistant, or search assistant.
diff --git a/en/application-dev/application-models/serviceextensionability.md b/en/application-dev/application-models/serviceextensionability.md
index 9ff7a0ae5d6df7574da19565c81411236dba3dda..2e9aaeb48100d86d0cd1c7a0e69ea01bf4ef2340 100644
--- a/en/application-dev/application-models/serviceextensionability.md
+++ b/en/application-dev/application-models/serviceextensionability.md
@@ -1,125 +1,151 @@
 # ServiceExtensionAbility
 
+## Overview
 
-[ServiceExtensionAbility](../reference/apis/js-apis-app-ability-serviceExtensionAbility.md) is an ExtensionAbility component of the service type that provides extension capabilities related to background services.
+[ServiceExtensionAbility](../reference/apis/js-apis-app-ability-serviceExtensionAbility.md) is an ExtensionAbility component of the SERVICE type that provides capabilities related to background services. It holds an internal [ServiceExtensionContext](../reference/apis/js-apis-inner-application-serviceExtensionContext.md), through which a variety of APIs are provided for external systems.
 
+In this document, the started ServiceExtensionAbility component is called the server, and the component that starts ServiceExtensionAbility is called the client.
 
-ServiceExtensionAbility can be started or connected by other application components to process transactions in the background based on the request of the caller. System applications can call the [startServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstartserviceextensionability) method to start background services or call the [connectServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextconnectserviceextensionability) method to connect to background services. Third-party applications can call only **connectServiceExtensionAbility()** to connect to background services. The differences between starting and connecting to background services are as follows:
+A ServiceExtensionAbility can be started or connected by other components to process transactions in the background based on the request of the caller. System applications can call the [startServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartserviceextensionability) method to start background services or call the [connectServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextconnectserviceextensionability) method to connect to background services. Third-party applications can call only **connectServiceExtensionAbility()** to connect to background services. The differences between starting and connecting to background services are as follows:
 
+- **Starting**: In the case that AbilityA starts ServiceB, they are weakly associated. After AbilityA exits, ServiceB can still exist.
 
-- In the case that AbilityA starts ServiceB, they are weakly associated. After AbilityA exits, ServiceB can still exist.
+- **Connecting**: In the case that AbilityA connects to ServiceB, they are strongly associated. After AbilityA exits, ServiceB also exits.
 
-- In the case that AbilityA connects to ServiceB, they are strongly associated. After AbilityA exits, ServiceB also exits.
+Note the following:
 
+- If a ServiceExtensionAbility is started only by means of connecting, its lifecycle is controlled by the client. A new connection is set up each time the client calls the [connectServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextconnectserviceextensionability) method. When the client exits or calls the [disconnectServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextdisconnectserviceextensionability) method, the connection is disconnected. After all connections are disconnected, the ServiceExtensionAbility automatically exits.
 
-Each type of ExtensionAbility has its own context. ServiceExtensionAbility has [ServiceExtensionContext](../reference/apis/js-apis-inner-application-serviceExtensionContext.md). In this document, the started ServiceExtensionAbility component is called the server, and the component that starts ServiceExtensionAbility is called the client.
-
-
-This topic describes how to use ServiceExtensionAbility in the following scenarios:
-
-
-- [Implementing a Background Service (for System Applications Only)](#implementing-a-background-service-for-system-applications-only)
-
-- [Starting a Background Service (for System Applications Only)](#starting-a-background-service-for-system-applications-only)
-
-- [Connecting to a Background Service](#connecting-to-a-background-service)
-
+- Once a ServiceExtensionAbility is started by means of starting, it will not exit automatically. System applications can call the [stopServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstopserviceextensionability) method to stop it.
 
 > **NOTE**
-> - OpenHarmony does not support third-party applications in implementing ServiceExtensionAbility. If you want to implement transaction processing in the background, use background tasks. For details, see [Background Task](../task-management/background-task-overview.md).
-> 
+>
+> - Currently, third-party applications cannot implement ServiceExtensionAbility. If you want to implement transaction processing in the background, use background tasks. For details, see [Background Task](../task-management/background-task-overview.md).
 > - UIAbility of a third-party application can connect to ServiceExtensionAbility provided by the system through the context.
-> 
 > - Third-party applications can connect to ServiceExtensionAbility provided by the system only when they gain focus in the foreground.
 
-
-## Implementing a Background Service (for System Applications Only)
+## Lifecycle
 
 [ServiceExtensionAbility](../reference/apis/js-apis-app-ability-serviceExtensionAbility.md) provides the callbacks **onCreate()**, **onRequest()**, **onConnect()**, **onDisconnect()**, and **onDestory()**. Override them as required. The following figure shows the lifecycle of ServiceExtensionAbility.
 
-  **Figure 1** ServiceExtensionAbility lifecycle
+**Figure 1** ServiceExtensionAbility lifecycle
 ![ServiceExtensionAbility-lifecycle](figures/ServiceExtensionAbility-lifecycle.png)
 
 - **onCreate**
-
-  This callback is triggered when a service is created for the first time. You can perform initialization operations, for example, registering a common event listener.
+  
+  This callback is triggered when a ServiceExtensionAbility is created for the first time. You can perform initialization operations, for example, registering a common event listener.
 
   > **NOTE**
   >
-  > If a service has been created, starting it again does not trigger the **onCreate()** callback.
+  > If a ServiceExtensionAbility has been created, starting it again does not trigger the **onCreate()** callback.
 
 - **onRequest**
-
-  This callback is triggered when another component calls the **startServiceExtensionAbility()** method to start the service. After being started, the service runs in the background.
+  
+  This callback is triggered when another component calls the [startServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartserviceextensionability) method to start a ServiceExtensionAbility. After being started, the ServiceExtensionAbility runs in the background. This callback is triggered each time the [startServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartserviceextensionability) method is called.
 
 - **onConnect**
-
-  This callback is triggered when another component calls the **connectServiceExtensionAbility()** method to connect to the service. In this method, a remote proxy object (IRemoteObject) is returned, through which the client communicates with the server by means of RPC.
+  
+  This callback is triggered when another component calls the [connectServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextconnectserviceextensionability) method to connect to a ServiceExtensionAbility. In this method, a remote proxy object (IRemoteObject) is returned, through which the client communicates with the server by means of RPC. At the same time, the system stores the remote proxy object (IRemoteObject). If another component calls the [connectServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextconnectserviceextensionability) method to connect to this ServiceExtensionAbility, the system directly returns the saved remote proxy object (IRemoteObject) and does not trigger the callback.
 
 - **onDisconnect**
-
-  This callback is triggered when a component calls the **disconnectServiceExtensionAbility()** method to disconnect from the service.
+  
+  This callback is triggered when the last connection is disconnected. A connection is disconnected when the client exits or the [disconnectServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextdisconnectserviceextensionability) method is called.
 
 - **onDestroy**
   
-  This callback is triggered when the service is no longer used and the instance is ready for destruction. You can clear resources in this callback, for example, deregister the listener.
+  This callback is triggered when ServiceExtensionAbility is no longer used and the instance is ready for destruction. You can clear resources in this callback, for example, deregister the listener.
 
+## Implementing a Background Service (for System Applications Only)
 
-## How to Develop
+### Preparations
 
-To implement a background service, manually create a ServiceExtensionAbility component in DevEco Studio. The procedure is as follows:
+Only system applications can implement ServiceExtensionAbility. You must make the following preparations before development:
 
-1. In the **ets** directory of the **Module** project, right-click and choose **New > Directory** to create a directory named **serviceextability**.
+- **Switching to the full SDK**: All APIs related to ServiceExtensionAbility are marked as system APIs and hidden by default. Therefore, you must manually obtain the full SDK from the mirror and switch to it in DevEco Studio. For details, see [Guide to Switching to Full SDK](../quick-start/full-sdk-switch-guide.md).
 
-2. In the **serviceextability** directory, right-click and choose **New > TypeScript File** to create a file named **ServiceExtAbility.ts**.
+- **Requesting the AllowAppUsePrivilegeExtension privilege**: Only applications with the **AllowAppUsePrivilegeExtension** privilege can develop ServiceExtensionAbility. For details about how to request the privilege, see [Application Privilege Configuration Guide](../../device-dev/subsystems/subsys-app-privilege-config-guide.md).
 
-3. Open the **ServiceExtAbility.ts** file, import the [RPC module](../reference/apis/js-apis-rpc.md), and reload the **onRemoteMessageRequest()** method to receive messages from the client and return the processing result to the client. **REQUEST_VALUE** is used to verify the service request code sent by the client.
-   
-   ```ts
-   import rpc from '@ohos.rpc';
-   
-   const REQUEST_CODE = 99;
-   
-   class StubTest extends rpc.RemoteObject {
-     constructor(des) {
-       super(des);
-     }
-     
-     // Receive a message from the client and return the processing result to the client.
-     onRemoteMessageRequest(code, data, reply, option) {
-       if (code === REQUEST_CODE) {
-         // Receive data from the client.
-         // If the client calls data.writeInt() multiple times to write multiple pieces of data, the server can call data.readInt() multiple times to receive all the data.
-         let optFir = data.readInt();
-         let optSec = data.readInt();
-         // The server returns the data processing result to the client.
-         // In the example, the server receives two pieces of data and returns the sum of the two pieces of data to the client.
-         reply.writeInt(optFir + optSec);
-       }
-       return true;
-     }
-   
-     // Send messages to the client in synchronous or asynchronous mode.
-     sendRequest(code, data, reply, options) {
-       return null;
-     }
-   }
-   ```
+### Defining IDL Interfaces
+
+As a background service, ServiceExtensionAbility needs to provide interfaces that can be called by external systems. You can define the interfaces in IDL files and use the [IDL tool](../IDL/idl-guidelines.md) to generate proxy and stub files. The following demonstrates how to define a file named **IIdlServiceExt.idl**:
+
+```cpp
+interface OHOS.IIdlServiceExt {
+  int ProcessData([in] int data);
+  void InsertDataToMap([in] String key, [in] int val);
+}
+```
+
+Create the **IdlServiceExt** directory in the **ets** directory corresponding to the module of the DevEco Studio project, and copy the files generated by the [IDL tool](../IDL/idl-guidelines.md) to this directory. Then create a file named **idl_service_ext_impl.ts** to implement the IDL interfaces.
+
+```
+├── ets
+│ ├── IdlServiceExt
+│ │   ├── i_idl_service_ext.ts      # File generated.
+│ │   ├── idl_service_ext_proxy.ts  # File generated.
+│ │   ├── idl_service_ext_stub.ts   # File generated.
+│ │   ├── idl_service_ext_impl.ts   # Custom file used to implement IDL interfaces.
+│ └
+└
+```
+
+An example of **idl_service_ext_impl.ts** is as follows:
+
+```ts
+import {processDataCallback} from './i_idl_service_ext';
+import {insertDataToMapCallback} from './i_idl_service_ext';
+import IdlServiceExtStub from './idl_service_ext_stub';
+
+const ERR_OK = 0;
+const TAG: string = "[IdlServiceExtImpl]";
+
+// You need to implement interfaces in this type.
+export default class ServiceExtImpl extends IdlServiceExtStub {
+  processData(data: number, callback: processDataCallback): void {
+    // Implement service logic.
+    console.info(TAG, `processData: ${data}`);
+    callback(ERR_OK, data + 1);
+  }
+
+  insertDataToMap(key: string, val: number, callback: insertDataToMapCallback): void {
+    // Implement service logic.
+    console.log(TAG, `insertDataToMap, key: ${key}  val: ${val}`);
+    callback(ERR_OK);
+  }
+}
+```
+
+### Creating a ServiceExtensionAbility
+
+To manually create a ServiceExtensionAbility in the DevEco Studio project, perform the following steps:
+
+1. In the **ets** directory of the **Module** project, right-click and choose **New > Directory** to create a directory named **ServiceExtAbility**.
+
+2. In the **ServiceExtAbility** directory, right-click and choose **New > TypeScript File** to create a file named **ServiceExtAbility.ts**.
+
+    ```
+    ├── ets
+    │ ├── IdlServiceExt
+    │ │   ├── i_idl_service_ext.ts      # File generated.
+    │ │   ├── idl_service_ext_proxy.ts  # File generated.
+    │ │   ├── idl_service_ext_stub.ts   # File generated.
+    │ │   ├── idl_service_ext_impl.ts   # Custom file used to implement IDL interfaces.
+    │ ├── ServiceExtAbility
+    │ │   ├── ServiceExtAbility.ts
+    └
+    ```
+
+3. In the **ServiceExtAbility.ts** file, add the dependency package for importing ServiceExtensionAbility. Customize a class that inherits from ServiceExtensionAbility and implement the lifecycle callbacks, and return the previously defined **ServiceExtImpl** object in the **onConnect** lifecycle callback.
 
-4. In the **ServiceExtAbility.ts** file, add the dependency package for importing ServiceExtensionAbility. Customize a class that inherits from ServiceExtensionAbility and add the required lifecycle callbacks.
-   
    ```ts
    import ServiceExtensionAbility from '@ohos.app.ability.ServiceExtensionAbility';
-   import rpc from '@ohos.rpc';
-   
-   const TAG: string = "[Example].[Entry].[ServiceExtAbility]";
-   const REQUEST_CODE = 99;
+   import ServiceExtImpl from '../IdlServiceExt/idl_service_ext_impl';
    
-   class StubTest extends rpc.RemoteObject {
-     // ...
-   }
+   const TAG: string = "[ServiceExtAbility]";
    
    export default class ServiceExtAbility extends ServiceExtensionAbility {
+     serviceExtImpl = new ServiceExtImpl("ExtImpl");
+
      onCreate(want) {
        console.info(TAG, `onCreate, want: ${want.abilityName}`);
      }
@@ -130,7 +156,8 @@ To implement a background service, manually create a ServiceExtensionAbility com
    
      onConnect(want) {
        console.info(TAG, `onConnect, want: ${want.abilityName}`);
-       return new StubTest("test");
+       // Return the ServiceExtImpl object, through which the client can communicate with the ServiceExtensionAbility.
+       return this.serviceExtImpl;
      }
    
      onDisconnect(want) {
@@ -143,8 +170,8 @@ To implement a background service, manually create a ServiceExtensionAbility com
    }
    ```
 
-5. Register ServiceExtensionAbility in the [module.json5 file](../quick-start/module-configuration-file.md) corresponding to the **Module** project. Set **type** to **"service"** and **srcEntrance** to the code path of the ExtensionAbility component.
-   
+4. Register ServiceExtensionAbility in the [module.json5 file](../quick-start/module-configuration-file.md) corresponding to the **Module** project. Set **type** to **"service"** and **srcEntry** to the code path of the ServiceExtensionAbility component.
+
    ```json
    {
      "module": {
@@ -155,15 +182,14 @@ To implement a background service, manually create a ServiceExtensionAbility com
            "icon": "$media:icon",
            "description": "service",
            "type": "service",
-           "visible": true,
-           "srcEntrance": "./ets/serviceextability/ServiceExtAbility.ts"
+           "exported": true,
+           "srcEntry": "./ets/ServiceExtAbility/ServiceExtAbility.ts"
          }
        ]
      }
    }
    ```
 
-
 ## Starting a Background Service (for System Applications Only)
 
 A system application uses the [startServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstartserviceextensionability) method to start a background service. The [onRequest()](../reference/apis/js-apis-app-ability-serviceExtensionAbility.md#serviceextensionabilityonrequest) callback is invoked, and the **Want** object passed by the caller is received through the callback. After the background service is started, its lifecycle is independent of that of the client. In other words, even if the client is destroyed, the background service can still run. Therefore, the background service must be stopped by calling [terminateSelf()](../reference/apis/js-apis-inner-application-serviceExtensionContext.md#serviceextensioncontextterminateself) when its work is complete. Alternatively, another component can call [stopServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstopserviceextensionability) to stop the background service.
@@ -173,7 +199,7 @@ A system application uses the [startServiceExtensionAbility()](../reference/apis
 > [startServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstartserviceextensionability), [stopServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstopserviceextensionability), and [terminateSelf()](../reference/apis/js-apis-inner-application-serviceExtensionContext.md#serviceextensioncontextterminateself) of ServiceExtensionContext are system APIs and cannot be called by third-party applications.
 
 1. Start a new ServiceExtensionAbility in a system application. For details about how to obtain the context, see [Obtaining the Context of UIAbility](uiability-usage.md#obtaining-the-context-of-uiability).
-   
+
    ```ts
    let want = {
        "deviceId": "",
@@ -188,7 +214,7 @@ A system application uses the [startServiceExtensionAbility()](../reference/apis
    ```
 
 2. Stop ServiceExtensionAbility in the system application.
-   
+
    ```ts
    let want = {
        "deviceId": "",
@@ -203,7 +229,7 @@ A system application uses the [startServiceExtensionAbility()](../reference/apis
    ```
 
 3. ServiceExtensionAbility stops itself.
-   
+
    ```ts
    // this is the current ServiceExtensionAbility component.
    this.context.terminateSelf().then(() => {
@@ -213,35 +239,71 @@ A system application uses the [startServiceExtensionAbility()](../reference/apis
    })
    ```
 
-
 > **NOTE**
 >
 > Background services can run in the background for a long time. To minimize resource usage, destroy it in time when a background service finishes the task of the requester. A background service can be stopped in either of the following ways:
 >
 > - The background service calls the [terminateSelf()](../reference/apis/js-apis-inner-application-serviceExtensionContext.md#serviceextensioncontextterminateself) method to automatically stop itself.
->
 > - Another component calls the [stopServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstopserviceextensionability) method to stop the background service.
->
 > After either method is called, the system destroys the background service.
 
-
 ## Connecting to a Background Service
 
-Either a system application or a third-party application can connect to a service (service specified in the **Want** object) through [connectServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextconnectserviceextensionability). The [onConnect()](../reference/apis/js-apis-app-ability-serviceExtensionAbility.md#serviceextensionabilityonconnect) callback is invoked, and the **Want** object passed by the caller is received through the callback. In this way, a persistent connection is established.
+Either a system application or a third-party application can connect to a ServiceExtensionAbility (specified in the **Want** object) through [connectServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextconnectserviceextensionability). The [onConnect()](../reference/apis/js-apis-app-ability-serviceExtensionAbility.md#serviceextensionabilityonconnect) callback is invoked, and the **Want** object passed by the caller is received through the callback. In this way, a persistent connection is established.
 
 The ServiceExtensionAbility component returns an IRemoteObject in the **onConnect()** callback. Through this IRemoteObject, you can define communication interfaces for RPC interaction between the client and server. Multiple clients can connect to the same background service at the same time. After a client finishes the interaction, it must call [disconnectServiceExtensionAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextdisconnectserviceextensionability) to disconnect from the service. If all clients connected to a background service are disconnected, the system destroys the service.
 
 - Call **connectServiceExtensionAbility()** to establish a connection to a background service. For details about how to obtain the context, see [Obtaining the Context of UIAbility](uiability-usage.md#obtaining-the-context-of-uiability).
   
   ```ts
-  import rpc from '@ohos.rpc';
-  
-  const REQUEST_CODE = 99;
   let want = {
       "deviceId": "",
       "bundleName": "com.example.myapplication",
       "abilityName": "ServiceExtAbility"
   };
+  let options = {
+      onConnect(elementName, remote) {
+          /* The input parameter remote is the object returned by ServiceExtensionAbility in the onConnect lifecycle callback.
+           * This object is used for communication with ServiceExtensionAbility. For details, see the section below.
+           */
+          console.info('onConnect callback');
+          if (remote === null) {
+              console.info(`onConnect remote is null`);
+              return;
+          }
+      },
+      onDisconnect(elementName) {
+          console.info('onDisconnect callback')
+      },
+      onFailed(code) {
+          console.info('onFailed callback')
+      }
+  }
+  // The ID returned after the connection is set up must be saved. The ID will be passed for service disconnection.
+  let connectionId = this.context.connectServiceExtensionAbility(want, options);
+  ```
+
+- Use **disconnectServiceExtensionAbility()** to disconnect from the background service.
+  
+  ```ts
+  // connectionId is returned when connectServiceExtensionAbility is called and needs to be manually maintained.
+  this.context.disconnectServiceExtensionAbility(connectionId).then((data) => {
+      console.info('disconnectServiceExtensionAbility success');
+  }).catch((error) => {
+      console.error('disconnectServiceExtensionAbility failed');
+  })
+  ```
+
+## Communication Between the Client and Server
+
+After obtaining the [rpc.RemoteObject](../reference/apis/js-apis-rpc.md#iremoteobject) object from the **onConnect()** callback, the client can communicate with ServiceExtensionAbility in either of the following ways:
+
+- Using the IDL interface provided by the server for communication (recommended)
+
+  ```ts
+  // The client needs to import idl_service_ext_proxy.ts provided by the server for external systems to the local project.
+  import IdlServiceExtProxy from '../IdlServiceExt/idl_service_ext_proxy';
+
   let options = {
       onConnect(elementName, remote) {
           console.info('onConnect callback');
@@ -249,23 +311,54 @@ The ServiceExtensionAbility component returns an IRemoteObject in the **onConnec
               console.info(`onConnect remote is null`);
               return;
           }
+          let serviceExtProxy = new IdlServiceExtProxy(remote);
+          // Communication is carried out by interface calling, without exposing RPC details.
+          serviceExtProxy.processData(1, (errorCode, retVal) => {
+              console.log(`processData, errorCode: ${errorCode}, retVal: ${retVal}`);
+          });
+          serviceExtProxy.insertDataToMap('theKey', 1, (errorCode) => {
+              console.log(`insertDataToMap, errorCode: ${errorCode}`);
+          })
+      },
+      onDisconnect(elementName) {
+          console.info('onDisconnect callback')
+      },
+      onFailed(code) {
+          console.info('onFailed callback')
+      }
+  }
+  ```
+
+- Calling [sendMessageRequest](../reference/apis/js-apis-rpc.md#sendmessagerequest9) to send messages to the server (not recommended)
+
+  ```ts
+  import rpc from '@ohos.rpc';
+
+  const REQUEST_CODE = 1;
+  let options = {
+      onConnect(elementName, remote) {
+          console.info('onConnect callback');
+          if (remote === null) {
+              console.info(`onConnect remote is null`);
+              return;
+          }
+          // Directly call the RPC interface to send messages to the server. The client needs to serialize the input parameters and deserialize the return values. The process is complex.
           let option = new rpc.MessageOption();
-          let data = new rpc.MessageParcel();
-          let reply = new rpc.MessageParcel();
+          let data = new rpc.MessageSequence();
+          let reply = new rpc.MessageSequence();
           data.writeInt(100);
-          data.writeInt(200);
-  
+
           // @param code Indicates the service request code sent by the client.
-          // @param data Indicates the {@link MessageParcel} object sent by the client.
+          // @param data Indicates the {@link MessageSequence} object sent by the client.
           // @param reply Indicates the response message object sent by the remote service.
           // @param options Specifies whether the operation is synchronous or asynchronous.
           // 
           // @return Returns {@code true} if the operation is successful; returns {@code false} otherwise.
-          remote.sendRequest(REQUEST_CODE, data, reply, option).then((ret) => {
+          remote.sendMessageRequest(REQUEST_CODE, data, reply, option).then((ret) => {
               let msg = reply.readInt();
-              console.info(`sendRequest ret:${ret} msg:${msg}`);
+              console.info(`sendMessageRequest ret:${ret} msg:${msg}`);
           }).catch((error) => {
-              console.info('sendRequest failed');
+              console.info('sendMessageRequest failed');
           });
       },
       onDisconnect(elementName) {
@@ -275,18 +368,90 @@ The ServiceExtensionAbility component returns an IRemoteObject in the **onConnec
           console.info('onFailed callback')
       }
   }
-  // The ID returned after the connection is set up must be saved. The ID will be passed for service disconnection.
-  let connectionId = this.context.connectServiceExtensionAbility(want, options);
   ```
 
-- Use **disconnectServiceExtensionAbility()** to disconnect from the background service.
-  
+## Client Identity Verification by the Server
+
+When ServiceExtensionAbility is used to provide sensitive services, the client identity must be verified. You can implement the verification on the stub of the IDL interface. For details about the IDL interface implementation, see [Defining IDL Interfaces](#defining-idl-interfaces). Two verification modes are recommended:
+
+- **Verifying the client identity based on callerUid**
+
+  Call the [getCallingUid()](../reference/apis/js-apis-rpc.md#getcallinguid) method to obtain the UID of the client, and then call the [getBundleNameByUid()](../reference/apis/js-apis-bundleManager.md#bundlemanagergetbundlenamebyuid) method to obtain the corresponding bundle name. In this way, the client identify is verified. Note that [getBundleNameByUid()](../reference/apis/js-apis-bundleManager.md#bundlemanagergetbundlenamebyuid) is asynchronous, and therefore the server cannot return the verification result to the client. This verification mode applies when the client sends an asynchronous task execution request to the server. The sample code is as follows:
+
   ```ts
-  let connectionId = 1 // ID returned when the service is connected through connectServiceExtensionAbility.
-  this.context.disconnectServiceExtensionAbility(connectionId).then((data) => {
-      console.info('disconnectServiceExtensionAbility success');
-  }).catch((error) => {
-      console.error('disconnectServiceExtensionAbility failed');
-  })
+  import rpc from '@ohos.rpc';
+  import bundleManager from '@ohos.bundle.bundleManager';
+  import {processDataCallback} from './i_idl_service_ext';
+  import {insertDataToMapCallback} from './i_idl_service_ext';
+  import IdlServiceExtStub from './idl_service_ext_stub';
+
+  const ERR_OK = 0;
+  const ERR_DENY = -1;
+  const TAG: string = "[IdlServiceExtImpl]";
+
+  export default class ServiceExtImpl extends IdlServiceExtStub {
+    processData(data: number, callback: processDataCallback): void {
+      console.info(TAG, `processData: ${data}`);
+
+      let callerUid = rpc.IPCSkeleton.getCallingUid();
+      bundleManager.getBundleNameByUid(callerUid).then((callerBundleName) => {
+        console.info(TAG, 'getBundleNameByUid: ' + callerBundleName);
+        // Identify the bundle name of the client.
+        if (callerBundleName != 'com.example.connectextapp') {  // The verification fails.
+          console.info(TAG, 'The caller bundle is not in whitelist, reject');
+          return;
+        }
+        // The verification is successful, and service logic is executed normally.
+      }).catch(err => {
+        console.info(TAG, 'getBundleNameByUid failed: ' + err.message);
+      });
+    }
+
+    insertDataToMap(key: string, val: number, callback: insertDataToMapCallback): void {
+      // Implement service logic.
+      console.log(TAG, `insertDataToMap, key: ${key}  val: ${val}`);
+      callback(ERR_OK);
+    }
+  }
+  ```
+
+- **Verifying the client identity based on callerTokenId**
+
+  Call the [getCallingTokenId()](../reference/apis/js-apis-rpc.md#getcallingtokenid) method to obtain the token ID of the client, and then call the [verifyAccessTokenSync()](../reference/apis/js-apis-abilityAccessCtrl.md#verifyaccesstokensync) method to check whether the client has a specific permission. Currently, OpenHarmony does not support permission customization. Therefore, only [system-defined permissions](../security/permission-list.md) can be verified. The sample code is as follows:
+
+  ```ts
+  import rpc from '@ohos.rpc';
+  import abilityAccessCtrl from '@ohos.abilityAccessCtrl';
+  import {processDataCallback} from './i_idl_service_ext';
+  import {insertDataToMapCallback} from './i_idl_service_ext';
+  import IdlServiceExtStub from './idl_service_ext_stub';
+
+  const ERR_OK = 0;
+  const ERR_DENY = -1;
+  const TAG: string = "[IdlServiceExtImpl]";
+
+  export default class ServiceExtImpl extends IdlServiceExtStub {
+    processData(data: number, callback: processDataCallback): void {
+      console.info(TAG, `processData: ${data}`);
+
+      let callerTokenId = rpc.IPCSkeleton.getCallingTokenId();
+      let accessManger = abilityAccessCtrl.createAtManager();
+      // The permission to be verified varies depending on the service requirements. ohos.permission.SET_WALLPAPER is only an example.
+      let grantStatus =
+          accessManger.verifyAccessTokenSync(callerTokenId, "ohos.permission.SET_WALLPAPER");
+      if (grantStatus === abilityAccessCtrl.GrantStatus.PERMISSION_DENIED) {
+          console.info(TAG, `PERMISSION_DENIED`);
+          callback(ERR_DENY, data);   // The verification fails and an error is returned.
+          return;
+      }
+      callback(ERR_OK, data + 1);     // The verification is successful, and service logic is executed normally.
+    }
+
+    insertDataToMap(key: string, val: number, callback: insertDataToMapCallback): void {
+      // Implement service logic.
+      console.log(TAG, `insertDataToMap, key: ${key}  val: ${val}`);
+      callback(ERR_OK);
+    }
+  }
   ```
 
diff --git a/en/application-dev/application-models/start-page.md b/en/application-dev/application-models/start-page.md
index 58966d93cba037eaad141caaed0feaaaa672cde1..4296d832fdaafaba67544e8e62b5c7c08395ecdf 100644
--- a/en/application-dev/application-models/start-page.md
+++ b/en/application-dev/application-models/start-page.md
@@ -12,7 +12,7 @@ import featureAbility from '@ohos.ability.featureAbility';
 async function restartAbility() {
     let wantInfo = {
         bundleName: "com.sample.MyApplication",
-        abilityName: "EntryAbility",
+        abilityName: "MainAbility",
         parameters: {
             page: "pages/second"
         }
@@ -70,7 +70,7 @@ struct Index {
 ```
 
 
-When the launch type of a PageAbility is set to **standard** or when the PageAbility with the launch type set to **singleton** is started for the first time, you can use the **parameters** parameter in **want** to transfer the pages information and use the **startAbility()** method to start the PageAbility. For details about the launch type, see [PageAbility Launch Type](pageability-launch-type.md). The target PageAbility can use the **featureAbility.getWant()** method in **onCreate** to obtain the **want** parameter, and then call **router.push** to start a specified page.
+When a PageAbility in multiton mode is started or when the PageAbility in singleton mode is started for the first time, you can use the **parameters** parameter in **want** to transfer the pages information and use the **startAbility()** method to start the PageAbility. For details about the launch type, see [PageAbility Launch Type](pageability-launch-type.md). The target PageAbility can use the **featureAbility.getWant()** method in **onCreate** to obtain the **want** parameter, and then call **router.push** to start a specified page.
 
 
 When a user touches the button on the page of the caller PageAbility, the **startAbility()** method is called to start the target PageAbility. The **want** parameter in **startAbility()** carries the specified page information.
@@ -89,7 +89,7 @@ struct Index {
         featureAbility.startAbility({
           want: {
             bundleName: "com.exm.myapplication",
-            abilityName: "com.exm.myapplication.EntryAbility",
+            abilityName: "com.exm.myapplication.MainAbility",
             parameters: { page: "pages/page1" }
           }
         }).then((data) => {
@@ -104,7 +104,7 @@ struct Index {
         featureAbility.startAbility({
           want: {
             bundleName: "com.exm.myapplication",
-            abilityName: "com.exm.myapplication.EntryAbility",
+            abilityName: "com.exm.myapplication.MainAbility",
             parameters: { page: "pages/page2" }
           }
         }).then((data) => {
diff --git a/en/application-dev/application-models/thread-model-stage.md b/en/application-dev/application-models/thread-model-stage.md
index deaab60b7bd7549dcb96bc00d7896d5c67e5c5d2..4ca9fb3ed369f78cf12054c7b6da085b8640b1db 100644
--- a/en/application-dev/application-models/thread-model-stage.md
+++ b/en/application-dev/application-models/thread-model-stage.md
@@ -2,19 +2,14 @@
 
 For an OpenHarmony application, each process has a main thread to provide the following functionalities:
 
-- Manage other threads.
-
-- Enable multiple UIAbility components of the same application to share the same main thread.
-
-- Distribute input events.
-
 - Draw the UI.
-
-- Invoke application code callbacks (event processing and lifecycle callbacks).
-
+- Manage the ArkTS engine instance of the main thread so that multiple UIAbility components can run on it.
+- Manage ArkTS engine instances of other threads (such as the worker thread), for example, starting and terminating other threads.
+- Distribute interaction events.
+- Process application code callbacks (event processing and lifecycle management).
 - Receive messages sent by the worker thread.
 
-In addition to the main thread, there is an independent thread, named worker. The worker thread is mainly used to perform time-consuming operations. It cannot directly operate the UI. The worker thread is created in the main thread and is independent of the main thread. A maximum of seven worker threads can be created.
+In addition to the main thread, there is an independent thread, named worker. The worker thread is mainly used to perform time-consuming operations. The worker thread is created in the main thread and is independent from the main thread. It cannot directly operate the UI. A maximum of seven worker threads can be created. 
 
 ![thread-model-stage](figures/thread-model-stage.png)
 
@@ -22,4 +17,5 @@ Based on the OpenHarmony thread model, different services run on different threa
 
 > **NOTE**
 > 
-> The stage model provides only the main thread and worker thread. Emitter is mainly used for event synchronization within the main thread or between the main thread and worker thread.
+> - The stage model provides only the main thread and worker thread. Emitter is mainly used for event synchronization within the main thread or between the main thread and worker thread.
+> - To view thread information about an application process, run the **hdc shell** command to enter the shell CLI of the device, and then run the **ps -p *<pid>* -T command**, where *<pid>* indicates the ID of the application process.
diff --git a/en/application-dev/application-models/uiability-intra-device-interaction.md b/en/application-dev/application-models/uiability-intra-device-interaction.md
index 5ea819219e45d219e68aee7f34988f4822dda5a9..148e804f48531f286ecfe395d1ecd03464a5eb45 100644
--- a/en/application-dev/application-models/uiability-intra-device-interaction.md
+++ b/en/application-dev/application-models/uiability-intra-device-interaction.md
@@ -38,7 +38,7 @@ Assume that your application has two UIAbility components: EntryAbility and Func
            info: 'From the Index page of EntryAbility',
        },
    }
-   // context is the UIAbilityContext of the initiator UIAbility.
+   // context is the AbilityContext of the initiator UIAbility.
    this.context.startAbility(wantInfo).then(() => {
        // ...
    }).catch((err) => {
@@ -65,7 +65,7 @@ Assume that your application has two UIAbility components: EntryAbility and Func
 3. To stop the **UIAbility** instance after the FuncAbility service is complete, call **terminateSelf()** in FuncAbility.
    
    ```ts
-   // context is the UIAbilityContext of the UIAbility instance to stop.
+   // context is the AbilityContext of the UIAbility instance to stop.
    this.context.terminateSelf((err) => {
        // ...
    });
@@ -88,7 +88,7 @@ When starting FuncAbility from EntryAbility, you want the result to be returned
            info: 'From the Index page of EntryAbility',
        },
    }
-   // context is the UIAbilityContext of the initiator UIAbility.
+   // context is the AbilityContext of the initiator UIAbility.
    this.context.startAbilityForResult(wantInfo).then((data) => {
        // ...
    }).catch((err) => {
@@ -124,7 +124,7 @@ When starting FuncAbility from EntryAbility, you want the result to be returned
    
    // ...
    
-   // context is the UIAbilityContext of the initiator UIAbility.
+   // context is the AbilityContext of the initiator UIAbility.
    this.context.startAbilityForResult(want).then((data) => {
        if (data?.resultCode === RESULT_CODE) {
            // Parse the information returned by the target UIAbility.
@@ -187,7 +187,7 @@ This section describes how to start the UIAbility of another application through
        entities: ['entity.system.default'],
    }
    
-   // context is the UIAbilityContext of the initiator UIAbility.
+   // context is the AbilityContext of the initiator UIAbility.
    this.context.startAbility(wantInfo).then(() => {
        // ...
    }).catch((err) => {
@@ -251,7 +251,7 @@ If you want to obtain the return result when using implicit Want to start the UI
        entities: ['entity.system.default'],
    }
    
-   // context is the UIAbilityContext of the initiator UIAbility.
+   // context is the AbilityContext of the initiator UIAbility.
    this.context.startAbilityForResult(wantInfo).then((data) => {
        // ...
    }).catch((err) => {
@@ -289,7 +289,7 @@ If you want to obtain the return result when using implicit Want to start the UI
      // Want parameter information.
    };
    
-   // context is the UIAbilityContext of the initiator UIAbility.
+   // context is the AbilityContext of the initiator UIAbility.
    this.context.startAbilityForResult(want).then((data) => {
        if (data?.resultCode === RESULT_CODE) {
            // Parse the information returned by the target UIAbility.
@@ -322,7 +322,7 @@ let wantInfo = {
         router: 'funcA',
     },
 }
-// context is the UIAbilityContext of the initiator UIAbility.
+// context is the AbilityContext of the initiator UIAbility.
 this.context.startAbility(wantInfo).then(() => {
     // ...
 }).catch((err) => {
@@ -500,12 +500,12 @@ For the CalleeAbility, implement the callback to receive data and the methods to
    ```json
    "abilities":[{
      "name": ".CalleeAbility",
-     "srcEntrance": "./ets/CalleeAbility/CalleeAbility.ts",
+     "srcEnty": "./ets/CalleeAbility/CalleeAbility.ts",
      "launchType": "singleton",
      "description": "$string:CalleeAbility_desc",
      "icon": "$media:icon",
      "label": "$string:CalleeAbility_label",
-     "visible": true
+     "exported": true
    }]
    ```
 
@@ -596,7 +596,7 @@ For the CalleeAbility, implement the callback to receive data and the methods to
 
 2. Obtain the caller interface.
 
-   The **UIAbilityContext** attribute implements **startAbilityByCall** to obtain the caller object for communication. The following example uses **this.context** to obtain the **UIAbilityContext**, uses **startAbilityByCall** to start the CalleeAbility, obtain the caller object, and register the **onRelease** listener of the CallerAbility. You need to implement processing based on service requirements.
+   The **context** attribute of the UIAbility implements **startAbilityByCall** to obtain the caller object for communication. The following example uses **this.context** to obtain the **context** attribute of the UIAbility, uses **startAbilityByCall** to start the CalleeAbility, obtain the caller object, and register the **onRelease** listener of the CallerAbility. You need to implement processing based on service requirements.
 
    
    ```ts
diff --git a/en/application-dev/application-models/uiability-launch-type.md b/en/application-dev/application-models/uiability-launch-type.md
index cf185cd9dad9593534afef59babe5cbf37585cae..ff904d4f60918a5ceed622840d5a153e52f8d1a4 100644
--- a/en/application-dev/application-models/uiability-launch-type.md
+++ b/en/application-dev/application-models/uiability-launch-type.md
@@ -6,7 +6,7 @@ The launch type of the UIAbility component refers to the state of the UIAbility
 
 - [Singleton](#singleton)
 
-- [Standard](#standard)
+- [Multiton](#multiton)
 
 - [Specified](#specified)
 
@@ -18,8 +18,7 @@ The launch type of the UIAbility component refers to the state of the UIAbility
 Each time [startAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartability) is called, if a UIAbility instance of this type already exists in the application process, the instance is reused. Therefore, only one UIAbility instance of this type exists in the system, that is, displayed in **Recents**.
 
 **Figure 1** Demonstration effect in singleton mode 
-
-![uiability-launch-type1](figures/uiability-launch-type1.png)
+![uiability-launch-type1](figures/uiability-launch-type1.gif)  
 
 > **NOTE**
 >
@@ -43,15 +42,15 @@ To use the singleton mode, set **launchType** in the [module.json5 configuration
 ```
 
 
-## Standard
+## Multiton
 
-In standard mode, each time [startAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartability) is called, a new UIAbility instance of this type is created in the application process. Multiple UIAbility instances of this type are displayed in **Recents**.  
+In multiton mode, each time [startAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartability) is called, a new UIAbility instance of this type is created in the application process. Multiple UIAbility instances of this type are displayed in **Recents**.  
 
-**Figure 2** Demonstration effect in standard mode 
+**Figure 2** Demonstration effect in multiton mode
 
-![standard-mode](figures/standard-mode.png)
+![uiability-launch-type2](figures/uiability-launch-type2.gif)  
 
-To use the standard mode, set **launchType** in the [module.json5 configuration file](../quick-start/module-configuration-file.md) to **standard**.
+To use the multiton mode, set **launchType** in the [module.json5 file](../quick-start/module-configuration-file.md) to **multiton**.
 
 
 ```json
@@ -60,7 +59,7 @@ To use the standard mode, set **launchType** in the [module.json5 configuration
     // ...
     "abilities": [
       {
-        "launchType": "standard",
+        "launchType": "multiton",
         // ...
       }
     ]
@@ -73,14 +72,13 @@ To use the standard mode, set **launchType** in the [module.json5 configuration
 
 The **specified** mode is used in some special scenarios. For example, in a document application, you want a document instance to be created each time you create a document, but you want to use the same document instance when you repeatedly open an existing document.
 
-**Figure 3** Demonstration effect in specified mode 
-
-![uiability-launch-type2](figures/uiability-launch-type2.png)
+**Figure 3** Demonstration effect in specified mode
+![uiability-launch-type3](figures/uiability-launch-type3.gif)  
 
 For example, there are two UIAbility components: EntryAbility and SpecifiedAbility (with the launch type **specified**). You are required to start SpecifiedAbility from EntryAbility.
 
 1. In SpecifiedAbility, set the **launchType** field in the [module.json5 file](../quick-start/module-configuration-file.md) to **specified**.
-   
+
    ```json
    {
      "module": {
@@ -95,8 +93,8 @@ For example, there are two UIAbility components: EntryAbility and SpecifiedAbili
    }
    ```
 
-2. Create a unique string key for the instance. Each time [startAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartability) is called, the application, based on the key, identifies the UIAbility instance used to respond to the request. In EntryAbility, add a custom parameter, for example, **instanceKey**, to the [want](want-overview.md) parameter in [startAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartability) to distinguish the UIAbility instance.
-   
+2. Create a unique string key for the instance. Each time [startAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartability) is called, the application, based on the key, identifies the UIAbility instance used to respond to the request. In EntryAbility, add a custom parameter, for example, **instanceKey**, to the **want** parameter in [startAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartability) to distinguish the UIAbility instance.
+
    ```ts
    // Configure an independent key for each UIAbility instance.
    // For example, in the document usage scenario, use the document path as the key.
@@ -120,10 +118,11 @@ For example, there are two UIAbility components: EntryAbility and SpecifiedAbili
        // ...
    })
    ```
-   
-3. During running, the internal service of UIAbility determines whether to create multiple instances. If the key is matched, the UIAbility instance bound to the key is started. Otherwise, a new UIAbility instance is created.
-   The launch type of SpecifiedAbility is set to **specified**. Before SpecifiedAbility is started, the [onAcceptWant()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonacceptwant) callback of the corresponding AbilityStage instance is invoked to parse the input **want** parameter and obtain the custom parameter **instanceKey**. A string key identifier is returned through the [onAcceptWant()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonacceptwant) callback of the AbilityStage instance. [If the returned key corresponds to a started UIAbility instance](mission-management-launch-type.md#fig14520125175314), that UIAbility instance is switched to the foreground and gains focus again. Otherwise, a new instance is created and started.
-   
+
+3. Before SpecifiedAbility is started, the [onAcceptWant()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonacceptwant) callback of the corresponding AbilityStage instance is invoked to obtain the key of the UIAbility, because the launch type of SpecifiedAbility is set to **specified**. If a UIAbility instance matching the key exists, the system starts the UIAbility instance and invokes its [onNewWant()](../reference/apis/js-apis-app-ability-uiAbility.md#abilityonnewwant) callback. Otherwise, the system creates a new UIAbility instance and invokes its [onCreate()](../reference/apis/js-apis-app-ability-uiAbility.md#uiabilityoncreate) and [onWindowStageCreate()](../reference/apis/js-apis-app-ability-uiAbility.md#uiabilityonwindowstagecreate) callbacks.
+
+   In the sample code, the [onAcceptWant()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonacceptwant) callback parses the **want** parameter to obtain the custom parameter **instanceKey**. The service logic returns a key string based on **instanceKey** parameter to identify the UIAbility instance. If the returned key maps to a started UIAbility instance, the system pulls the UIAbility instance back to the foreground and obtains the focus. If the returned key does not map to a started UIAbility instance, the system creates a new UIAbility instance and starts it.
+
    ```ts
    import AbilityStage from '@ohos.app.ability.AbilityStage';
    
@@ -140,12 +139,12 @@ For example, there are two UIAbility components: EntryAbility and SpecifiedAbili
        }
    }
    ```
-   
+
    > **NOTE**
    >
    > 1. Assume that the application already has a UIAbility instance created, and the launch type of the UIAbility instance is set to **specified**. If [startAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartability) is called again to start the UIAbility instance, and the [onAcceptWant()](../reference/apis/js-apis-app-ability-abilityStage.md#abilitystageonacceptwant) callback of [AbilityStage](../reference/apis/js-apis-app-ability-abilityStage.md) matches a created UIAbility instance, the original UIAbility instance is started, and no new UIAbility instance is created. In this case, the [onNewWant()](../reference/apis/js-apis-app-ability-uiAbility.md#abilityonnewwant) callback is invoked, but the [onCreate()](../reference/apis/js-apis-app-ability-uiAbility.md#uiabilityoncreate) and [onWindowStageCreate()](../reference/apis/js-apis-app-ability-uiAbility.md#uiabilityonwindowstagecreate) callbacks are not.
    > 2. AbilityStage is not automatically generated in the default project of DevEco Studio. For details about how to create an AbilityStage file, see [AbilityStage Component Container](abilitystage.md).
-   
+
    For example, in the document application, different keys are bound to different document instances. Each time a document is created, a new key (for example, file path) is passed, and a new UIAbility instance is created when UIAbility is started in AbilityStage. However, when you open an existing document, the same UIAbility instance is started again in AbilityStage.
 
    The following steps are used as an example.
@@ -153,6 +152,4 @@ For example, there are two UIAbility components: EntryAbility and SpecifiedAbili
    1. Open file A. A UIAbility instance, for example, UIAbility instance 1, is started.
    2. Close the process of file A in **Recents**. UIAbility instance 1 is destroyed. Return to the home screen and open file A again. A new UIAbility instance is started, for example, UIAbility instance 2.
    3. Return to the home screen and open file B. A new UIAbility instance is started, for example, UIAbility instance 3.
-   4. Return to the home screen and open file A again. UIAbility instance 2 is started.
-
- 
\ No newline at end of file
+   4. Return to the home screen and open file A again. UIAbility instance 2 is started. This is because the system automatically matches the key of the UIAbility instance and starts the UIAbility instance that has a matching key. In this example, UIAbility instance 2 has the same key as file A. Therefore, the system pulls back UIAbility instance 2 and focuses it without creating a new instance.
diff --git a/en/application-dev/application-models/uiability-overview.md b/en/application-dev/application-models/uiability-overview.md
index cd059b9555bfd80c02c9bce66f4c50cd58fff568..7862f2038fc6c353629bcdc9b3e51cfb5bedb046 100644
--- a/en/application-dev/application-models/uiability-overview.md
+++ b/en/application-dev/application-models/uiability-overview.md
@@ -37,7 +37,7 @@ To enable an application to properly use a UIAbility component, declare the UIAb
     "abilities": [
       {
         "name": "EntryAbility", // Name of the UIAbility component.
-        "srcEntrance": "./ets/entryability/EntryAbility.ts", // Code path of the UIAbility component.
+        "srcEnty": "./ets/entryability/EntryAbility.ts", // Code path of the UIAbility component.
         "description": "$string:EntryAbility_desc", // Description of the UIAbility component.
         "icon": "$media:icon", // Icon of the UIAbility component.
         "label": "$string:EntryAbility_label", // Label of the UIAbility component.
diff --git a/en/application-dev/application-models/widget-development-fa.md b/en/application-dev/application-models/widget-development-fa.md
index 062f1950d13f31f7eacfbb6470d005ad90c7de43..73cf20e0ce6ab82ae9e775dd8fb8f43922218b48 100644
--- a/en/application-dev/application-models/widget-development-fa.md
+++ b/en/application-dev/application-models/widget-development-fa.md
@@ -364,7 +364,7 @@ You can use the web-like paradigm (HML+CSS+JSON) to develop JS widget pages. Thi
 
 > **NOTE**
 >
-> Only the JavaScript-based web-like development paradigm is supported when developing the widget UI.
+> In the FA model, only the JavaScript-based web-like development paradigm is supported when developing the widget UI.
 
 - HML: uses web-like paradigm components to describe the widget page information.
   
@@ -452,7 +452,7 @@ You can set router and message events for components on a widget. The router eve
 
 2. Set the router event.
    - **action**: **"router"**, which indicates a router event.
-   - **abilityName**: name of the ability to redirect to (PageAbility component in the FA model and UIAbility component in the stage model). For example, the default MainAbility name created by DevEco Studio in the FA model is com.example.entry.MainAbility.
+   - **abilityName**: name of the ability to redirect to (PageAbility component in the FA model and UIAbility component in the stage model). For example, the default UIAbility name created by DevEco Studio in the FA model is com.example.entry.MainAbility.
    - **params**: custom parameters passed to the target ability. Set them as required. The value can be obtained from **parameters** in **want** used for starting the target ability. For example, in the lifecycle function **onCreate** of the MainAbility in the FA model, **featureAbility.getWant()** can be used to obtain **want** and its **parameters** field.
 
 3. Set the message event.
@@ -543,4 +543,3 @@ The following is an example:
     }
   }
   ```
-
diff --git a/en/application-dev/application-models/widget-switch.md b/en/application-dev/application-models/widget-switch.md
index 8d9823385a8a05f71c742327dc966054427a6718..0de83a6593f521e3b51b84dea5ff275e7ee5450f 100644
--- a/en/application-dev/application-models/widget-switch.md
+++ b/en/application-dev/application-models/widget-switch.md
@@ -11,7 +11,7 @@ Widget switching involves the following parts:
 | Configuration Item          | FA Model                                     | Stage Model                                                   |
 | ---------------- | ------------------------------------------- | ------------------------------------------------------------ |
 | Configuration item location      | **formAbility** and **forms** are in the **config.json** file.| **extensionAbilities** (configuration for **formExtensionAbility**) is in the **module.json5** file in the level-1 directory, and **forms** (configuration for **forms** contained in **formExtensionAbility**) is in the **form_config.json** file in the level-2 directory.|
-| Widget code path    | Specified by **srcPath**, without the file name.                        | Specified by **srcEntrance**, with the file name.                                       |
+| Widget code path    | Specified by **srcPath**, without the file name.                        | Specified by **srcEnty**, with the file name.                                          |
 | Programming language            | **srcLanguage** can be set to **js** or **ets**.               | This configuration item is unavailable. Only ets is supported.                                       |
 | Whether to enable widgets    | formsEnabled                                | This configuration item is unavailable. The setting of **type** set to **form** means that the widgets are enabled.                              |
 | Ability type     | type: service                              | type: form                                                  |
@@ -32,7 +32,7 @@ Figure 2 Widget configuration differences
 
 | Item| FA Model| Stage Model|
 | -------- | -------- | -------- |
-| Entry file| **form.ts** in the directory pointed to by **srcPath**| File pointed to by **srcEntrance**|
+| Entry file| **form.ts** in the directory pointed to by **srcPath**| File pointed to by **srcEnty**|
 | Lifecycle| export default| import FormExtension from '\@ohos.app.form.FormExtensionAbility';<br>export default class FormAbility extends FormExtension|
 
 
diff --git a/en/application-dev/application-models/windowextensionability.md b/en/application-dev/application-models/windowextensionability.md
index bdbcb65ffca3aa635146cdb8dfa97763ce99d652..a307a1da5e1c21e11b71d054b8300bb35ddf0522 100644
--- a/en/application-dev/application-models/windowextensionability.md
+++ b/en/application-dev/application-models/windowextensionability.md
@@ -1,5 +1,6 @@
 # WindowExtensionAbility
 
+
 [WindowExtensionAbility](../reference/apis/js-apis-application-windowExtensionAbility.md) is a type of ExtensionAbility component that allows a system application to be embedded in and displayed over another application.
 
 
@@ -14,7 +15,7 @@ the context is [WindowExtensionContext](../reference/apis/js-apis-inner-applicat
 >
 
 
-## Setting an Embedded Ability (for System Applications Only)
+## Setting an Embedded UIAbility (for System Applications Only)
 
 The **WindowExtensionAbility** class provides **onConnect()**, **onDisconnect()**, and **onWindowReady()** lifecycle callbacks, which can be overridden.
 
@@ -58,7 +59,7 @@ To implement an embedded application, manually create a WindowExtensionAbility i
     }
    ```
 
-4. Register the WindowExtensionAbility in the [module.json5 file](../quick-start/module-configuration-file.md) corresponding to the **Module** project. Set **type** to **"window"** and **srcEntrance** to the code path of the ExtensionAbility component.
+4. Register the WindowExtensionAbility in the [module.json5 file](../quick-start/module-configuration-file.md) corresponding to the **Module** project. Set **type** to **"window"** and **srcEnty** to the code path of the ExtensionAbility component.
 
    ```json
    {
@@ -66,11 +67,11 @@ To implement an embedded application, manually create a WindowExtensionAbility i
        "extensionAbilities": [
             {
                 "name": "WindowExtAbility",
-                "srcEntrance": "./ets/WindowExtAbility/WindowExtAbility.ts",
+                "srcEnty": "./ets/WindowExtAbility/WindowExtAbility.ts",
                 "icon": "$media:icon",
                 "description": "WindowExtension",
                 "type": "window",
-                "visible": true,
+                "exported": true,
             }
         ],
      }
@@ -78,7 +79,7 @@ To implement an embedded application, manually create a WindowExtensionAbility i
    ```
 
 
-## Starting an Embedded Ability (for System Applications Only)
+## Starting an Embedded UIAbility (for System Applications Only)
 
 System applications can load the created WindowExtensionAbility through the AbilityComponent.
 
diff --git a/en/application-dev/database/data-persistence-by-kv-store.md b/en/application-dev/database/data-persistence-by-kv-store.md
index 804fb6b12764b95cec9566bdc165234284d32a8d..2337702fb79b1d2c53154181362b393211f90f50 100644
--- a/en/application-dev/database/data-persistence-by-kv-store.md
+++ b/en/application-dev/database/data-persistence-by-kv-store.md
@@ -21,13 +21,13 @@ The key-value (KV) database stores data in the form of KV pairs. You can use KV
 
 The following table lists the APIs used for KV data persistence. Most of the APIs are executed asynchronously, using a callback or promise to return the result. The following table uses the callback-based APIs as an example. For more information about the APIs, see [Distributed KV Store](../reference/apis/js-apis-distributedKVStore.md).
 
-| API| Description|
+| API| Description| 
 | -------- | -------- |
-| createKVManager(config: KVManagerConfig): KVManager | Creates a **KvManager** instance to manage database objects.|
-| getKVStore&lt;T&gt;(storeId: string, options: Options, callback: AsyncCallback&lt;T&gt;): void | Creates and obtains a KV store of the specified type.|
-| put(key: string, value: Uint8Array\|string\|number\|boolean, callback: AsyncCallback&lt;void&gt;): void | Adds a KV pair of the specified type to this KV store.|
-| get(key: string, callback: AsyncCallback&lt;Uint8Array\|string\|boolean\|number&gt;): void | Obtains the value of the specified key.|
-| delete(key: string, callback: AsyncCallback&lt;void&gt;): void | Deletes a KV pair based on the specified key.|
+| createKVManager(config: KVManagerConfig): KVManager | Creates a **KvManager** instance to manage database objects.| 
+| getKVStore&lt;T&gt;(storeId: string, options: Options, callback: AsyncCallback&lt;T&gt;): void | Creates and obtains a KV store of the specified type.| 
+| put(key: string, value: Uint8Array\|string\|number\|boolean, callback: AsyncCallback&lt;void&gt;): void | Adds a KV pair of the specified type to this KV store.| 
+| get(key: string, callback: AsyncCallback&lt;Uint8Array\|string\|boolean\|number&gt;): void | Obtains the value of the specified key.| 
+| delete(key: string, callback: AsyncCallback&lt;void&gt;): void | Deletes a KV pair based on the specified key.| 
 
 
 ## How to Develop
@@ -35,10 +35,9 @@ The following table lists the APIs used for KV data persistence. Most of the API
 1. Create a **KvManager** instance to manage database objects. 
 
    Example:
-
    Stage model:
 
-
+     
    ```js
    // Import the module.
    import distributedKVStore from '@ohos.data.distributedKVStore';
@@ -69,7 +68,7 @@ The following table lists the APIs used for KV data persistence. Most of the API
 
    FA model:
 
-
+     
    ```js
    // Import the module.
    import distributedKVStore from '@ohos.data.distributedKVStore';
@@ -93,14 +92,13 @@ The following table lists the APIs used for KV data persistence. Most of the API
    ```
 
 2. Create and obtain a KV store. 
-
+     
    Example:
-
    ```js
    try {
      const options = {
        createIfMissing: true, // Whether to create a KV store when the database file does not exist. By default, a KV store is created.
-       createIfMissing: true, // Whether to encrypt database files. By default, database files are not encrypted.
+       encrypt: false, // Whether to encrypt the KV store. By default, KV stores are not encrypted.
        backup: false, // Whether to back up database files. By default, the database files are backed up.
        autoSync: true, // Whether to automatically synchronize database files. The value **true** means to automatically synchronize database files; the value **false** (default) means the opposite.
        kvStoreType: distributedKVStore.KVStoreType.SINGLE_VERSION, // Type of the KV store to create. By default, a device KV store is created.
@@ -121,9 +119,8 @@ The following table lists the APIs used for KV data persistence. Most of the API
    ```
 
 3. Use **put()** to add data to the KV store. 
-
+     
    Example:
-
    ```js
    const KEY_TEST_STRING_ELEMENT = 'key_test_string';
    const VALUE_TEST_STRING_ELEMENT = 'value_test_string';
@@ -145,9 +142,8 @@ The following table lists the APIs used for KV data persistence. Most of the API
    > The **put()** method adds a KV pair if the specified key does not exists and changes the value if the the specified key already exists.
 
 4. Use **get()** to obtain the value of a key. 
-
+     
    Example:
-
    ```js
    const KEY_TEST_STRING_ELEMENT = 'key_test_string';
    const VALUE_TEST_STRING_ELEMENT = 'value_test_string';
@@ -172,9 +168,8 @@ The following table lists the APIs used for KV data persistence. Most of the API
    ```
 
 5. Use **delete()** to delete the data of the specified key. 
-
+     
    Example:
-
    ```js
    const KEY_TEST_STRING_ELEMENT = 'key_test_string';
    const VALUE_TEST_STRING_ELEMENT = 'value_test_string';
diff --git a/en/application-dev/database/data-sync-of-rdb-store.md b/en/application-dev/database/data-sync-of-rdb-store.md
index d3f5f42c5a5338f24698f35c0e7fced1c5447643..444c5ab1ffadf09cfea56732e417df660c20ca8d 100644
--- a/en/application-dev/database/data-sync-of-rdb-store.md
+++ b/en/application-dev/database/data-sync-of-rdb-store.md
@@ -3,7 +3,7 @@
 
 ## When to Use
 
-When creating a data table, you can set the table to support cross-device access. You can also use APIs to move the data to be accessed across devices to a distributed data.
+You can synchronize the application data in a local RDB store on a device to other divices that form a Super Device.
 
 
 ## Basic Concepts
@@ -51,14 +51,14 @@ When data is added, deleted, or modified, a notification is sent to the subscrib
 
 The following table lists the APIs for cross-device data synchronization of RDB stores. Most of the APIs are executed asynchronously, using a callback or promise to return the result. The following table uses the callback-based APIs as an example. For more information about the APIs, see [RDB Store](../reference/apis/js-apis-data-relationalStore.md).
 
-| API| Description| 
+| API| Description|
 | -------- | -------- |
-| setDistributedTables(tables: Array&lt;string&gt;, callback: AsyncCallback&lt;void&gt;): void | Sets the distributed tables to be synchronized.| 
-| sync(mode: SyncMode, predicates: RdbPredicates, callback: AsyncCallback&lt;Array&lt;[string, number]&gt;&gt;): void | Synchronizes data across devices.| 
-| on(event: 'dataChange', type: SubscribeType, observer: Callback&lt;Array&lt;string&gt;&gt;): void | Subscribes to changes in the distributed data.| 
-| off(event:'dataChange', type: SubscribeType, observer: Callback&lt;Array&lt;string&gt;&gt;): void | Unsubscribe from changes in the distributed data.| 
-| obtainDistributedTableName(device: string, table: string, callback: AsyncCallback&lt;string&gt;): void; | Obtains the table name on the specified device based on the local table name.| 
-| remoteQuery(device: string, table: string, predicates: RdbPredicates, columns: Array&lt;string&gt; , callback: AsyncCallback&lt;ResultSet&gt;): void | Queries data from the RDB store of a remote device based on specified conditions.| 
+| setDistributedTables(tables: Array&lt;string&gt;, callback: AsyncCallback&lt;void&gt;): void | Sets the distributed tables to be synchronized.|
+| sync(mode: SyncMode, predicates: RdbPredicates, callback: AsyncCallback&lt;Array&lt;[string, number]&gt;&gt;): void | Synchronizes data across devices.|
+| on(event: 'dataChange', type: SubscribeType, observer: Callback&lt;Array&lt;string&gt;&gt;): void | Subscribes to changes in the distributed data.|
+| off(event:'dataChange', type: SubscribeType, observer: Callback&lt;Array&lt;string&gt;&gt;): void | Unsubscribe from changes in the distributed data.|
+| obtainDistributedTableName(device: string, table: string, callback: AsyncCallback&lt;string&gt;): void; | Obtains the table name on the specified device based on the local table name.|
+| remoteQuery(device: string, table: string, predicates: RdbPredicates, columns: Array&lt;string&gt; , callback: AsyncCallback&lt;ResultSet&gt;): void | Queries data from the RDB store of a remote device based on specified conditions.|
 
 
 ## How to Develop
@@ -68,7 +68,7 @@ The following table lists the APIs for cross-device data synchronization of RDB
 > The data on a device can be synchronized only to the devices whose data security labels are not higher than the security level of the device. For details, see [Access Control Mechanism in Cross-Device Synchronization](sync-app-data-across-devices-overview.md#access-control-mechanism-in-cross-device-synchronization).
 
 1. Import the module.
-     
+   
    ```js
    import relationalStore from '@ohos.data.relationalStore';
    ```
@@ -79,7 +79,7 @@ The following table lists the APIs for cross-device data synchronization of RDB
    2. Display a dialog box to ask authorization from the user when the application is started for the first time. For details, see [Requesting User Authorization](../security/accesstoken-guidelines.md#requesting-user-authorization).
 
 3. Create an RDB store and set a table for distributed synchronization.
-     
+   
    ```js
    const STORE_CONFIG = {
      name: 'RdbTest.db', // Database file name.
@@ -95,7 +95,7 @@ The following table lists the APIs for cross-device data synchronization of RDB
    ```
 
 4. Synchronize data across devices. After **sync()** is called to trigger a synchronization, data is synchronized from the local device to all other devices on the network.
-     
+   
    ```js
    // Construct the predicate object for synchronizing the distributed table.
    let predicates = new relationalStore.RdbPredicates('EMPLOYEE');
@@ -114,7 +114,7 @@ The following table lists the APIs for cross-device data synchronization of RDB
    ```
 
 5. Subscribe to changes in the distributed data. The data synchronization triggers the **observer** callback registered in **on()**. The input parameter of the callback is the ID of the device whose data changes.
-     
+   
    ```js
    let observer = function storeObserver(devices) {
      for (let i = 0; i < devices.length; i++) {
@@ -144,7 +144,7 @@ The following table lists the APIs for cross-device data synchronization of RDB
    >
    > **deviceIds** is obtained by using [devManager.getTrustedDeviceListSync](../reference/apis/js-apis-device-manager.md#gettrusteddevicelistsync). The APIs of the **deviceManager** module are all system interfaces and available only to system applications.
 
-     
+   
    ```js
    // Obtain device IDs.
    import deviceManager from '@ohos.distributedHardware.deviceManager';
diff --git a/en/application-dev/database/sync-app-data-across-devices-overview.md b/en/application-dev/database/sync-app-data-across-devices-overview.md
index 875b70fef7d4b3bcd6b78a2102ec40c80d7da5f9..c2f6361786325ccd753aa8fa4afa3446d37b6e89 100644
--- a/en/application-dev/database/sync-app-data-across-devices-overview.md
+++ b/en/application-dev/database/sync-app-data-across-devices-overview.md
@@ -36,14 +36,4 @@ Strong consistency has high requirements on distributed data management and may
 
 ## Access Control Mechanism in Cross-Device Synchronization
 
-In the application data synchronization across devices, data access is controlled based on the device level and [data security label](access-control-by-device-and-data-level.md#data-security-labels). In principle, data can be synchronized only to the devices whose data security labels are not higher than the device's security level. The access control matrix is as follows:
-
-|Device Security Level|Data Security Labels of the Synchornizable Device|
-|---|---|
-|SL1|S1|
-|SL2|S1 to S2|
-|SL3|S1 to S3|
-|SL4|S1 to S4|
-|SL5|S1 to S4| 
-
-For example, the security level of development boards RK3568 and Hi3516 is SL1. The database with data security label S1 can be synchronized with RK3568 and Hi3516, but the database with database labels S2-S4 cannot.
+When data is synchronized across devices, access control is performed based on the device level and data security label. For details, see [Access Control Mechanism in Cross-Device Synchronization](access-control-by-device-and-data-level.md#access-control-mechanism-in-cross-device-synchronization).
diff --git a/en/application-dev/faqs/Readme-EN.md b/en/application-dev/faqs/Readme-EN.md
index 872f525dc191173b3c7052b8f2b9b134926b1ceb..b9bde5d6ebd9c35e203d4f08ccb0e551c9eb6ad1 100644
--- a/en/application-dev/faqs/Readme-EN.md
+++ b/en/application-dev/faqs/Readme-EN.md
@@ -1,11 +1,19 @@
 # FAQs
 
-- [Ability Framework Development](faqs-ability.md)
-- [Resource Management Development](faqs-globalization.md)
+- [Ability Development](faqs-ability.md)
+- [Bundle Management Development](faqs-bundle-management.md)
+- [Resource Manager Development](faqs-globalization.md)
 - [Common Event and Notification Development](faqs-event-notification.md)
-- [Graphics and Image Development](faqs-graphics.md)
+- [Graphics Development](faqs-graphics.md)
+- [Window Management Development](faqs-window-manager.md)
+- [Multimedia Development](faqs-multimedia.md)
+- [Basic Security Capability Development](faqs-security.md)
+- [Ability Access Control Development](faqs-ability-access-control.md)
+- [Data Management Development](faqs-distributed-data-management.md)
 - [File Management Development](faqs-file-management.md)
 - [Network Management Development](faqs-network-management.md)
 - [DFX Development](faqs-dfx.md)
+- [Pan-Sensor Development](faqs-sensor.md)
 - [Startup Development](faqs-startup.md)
-- [Usage of Third- and Fourth-Party Libraries](faqs-third-fourth-party-library.md)
\ No newline at end of file
+- [Distributed Device Development](faqs-distributed-device-profile.md)
+- [Usage of Third- and Fourth-Party Libraries](faqs-third-fourth-party-library.md)
diff --git a/en/application-dev/faqs/faqs-ability-access-control.md b/en/application-dev/faqs/faqs-ability-access-control.md
new file mode 100644
index 0000000000000000000000000000000000000000..f336120a2b131eb75604fa3e51b1b8ff0130072e
--- /dev/null
+++ b/en/application-dev/faqs/faqs-ability-access-control.md
@@ -0,0 +1,7 @@
+# Application Access Control Development
+
+## Can the app listen for the permission change after its permission is modified in Settings?
+
+Applicable to: OpenHarmony 3.1 Beta 5 (API version 9)
+
+Third-party apps cannot listen for the permission change.
diff --git a/en/application-dev/faqs/faqs-ability.md b/en/application-dev/faqs/faqs-ability.md
index aab3ecc19aff704dbc34b9f7aa4d174344735453..b6901e40e6d84c622c41e487e30c62ba87a28ff4 100644
--- a/en/application-dev/faqs/faqs-ability.md
+++ b/en/application-dev/faqs/faqs-ability.md
@@ -1,68 +1,124 @@
-# Ability Framework Development
+# Ability Development
 
-## Is a guide similar to the Data ability development in the FA model available for the stage model?
+## How do I obtain a notification when the device orientation changes?
 
-Applicable to: OpenHarmony SDK 3.2.3.5, stage model of API version 9
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
-A guide is available for the **DataShareExtensionAbility** class, which provides APIs for sharing data with other applications and managing the data, in the stage model.
+**Solution**
 
-Reference: [DataShare Development](../database/database-datashare-guidelines.md)
+Use the **UIAbility.onConfigurationUpdate\(\)** callback to subscribe to system environment variable changes (including the language, color mode, and screen orientation).
 
-## What should I do if the UI does not respond when an ability is started?
+**Reference**
 
-Applicable to: OpenHarmony SDK 3.2.5.3, stage model of API version 9
+[Subscribing to System Environment Variable Changes](../application-models/subscribe-system-environment-variable-changes.md#using-uiability-for-subscription)
 
-1. If the ability is started using **startAbility**, check whether the **abilityName** field in **want** uses the bundle name as the prefix. If yes, delete the bundle name.
+## How do I redirect a user to a specified page after they touch a service widget?
 
-2. Make sure the ability's home page file configured by **onWindowStageCreate** in the **MainAbility.ts** file is defined in the **main_pages.json** file.
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
-3. You are advised to use the SDK and OpenHarmony SDK versions released on the same day.
+**Solution**
 
-Reference: [Release Testing Version](https://gitee.com/openharmony-sig/oh-inner-release-management/blob/master/Release-Testing-Version.md)
+Configure a widget event with the redirected-to UIAbility specified, and call **loadContent** in the **onWindowStageCreate\(\)** callback of the target UIAbility to redirect to the specified page.
 
-## How do I set the UI of an ability to transparent?
+**Reference**
 
-Applicable to: OpenHarmony SDK 3.2.3.5, stage model of API version 9
+[Developing Widget Events](../application-models/arkts-ui-widget-configuration.md)
 
-Set the background color of the top container component to transparent, and then set the **opacity** attribute of the XComponent to **0.01**.
+## How do I create a background service in the stage model?
 
-Example:
+Applicable to: OpenHarmony 3.2 Beta5
 
-```
-build() {
-  Stack() {
-    XComponent({
-    id: 'componentId',
-    type: 'surface',
-    })
-    .width('100%')
-    .height('100%')
-    .opacity(0.01)
-    // Page content
-  }
-  .width('100%')
-  .height('100%')
-  .backgroundColor('rgba(255,255,255, 0)')
-}
-```
+**Symptom**
+
+**ServiceExtensionAbility** in the stage model is a system API. Therefore, third-party applications cannot use it to create a background service.
+
+**Solution**
+
+Create a background task to provide the background service.
+
+**Reference**
+
+[Background Task](../task-management/background-task-overview.md)
+
+## Can I create a UIAbility and specify the process to run the UIAbility in the FA and Stage models?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+Yes.
+
+-   FA model
+
+    The FA model supports multiple processes. By default, all components of an application run in the same process. This default scenario is suitable for most applications. To run a specific component in an independent process, configure the **process** tag under **ability** in the configuration file. Note that this tag is available only for system applications.
+
+-   Stage model
+
+    The stage model supports multiple processes. The process model is defined by the system, and third-party applications cannot be configured with multiple processes. To customize an independent process, you must request special permissions, and then specify the **process** tag under **module** in the configuration file. This tag specifies the process in which all the abilities in an HAP run. If this tag is not set, the bundle name is used as the process name by default.
+
+
+## What are the differences between the stage model and the FA model in intra-process object sharing?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+-   In the stage model, multiple application components share the same ArkTS engine instance. Therefore, they can easily share objects and state with each other. This also reduces the memory usage of complex applications.
+-   In the FA model, each application component exclusively uses an ArkTS engine instance. Therefore, you are advised to use the stage model when developing complex applications in distributed scenarios.
+
+**Reference**
+
+[Data Synchronization Between UIAbility and UI](../application-models/uiability-data-sync-with-ui.md)
+
+## How do I use the lifecycle functions of AbilityStage?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+Add the field **"srcEntry": "./ets/myabilitystage/MyAbilityStage.ts"** under **module** in the **module.json5** file.
+
+**Reference**
+
+[AbilityStage Component Container](../application-models/abilitystage.md)
+
+
+## How do I delete the mission snapshot in Recents after terminateself is called in the multiton scenario?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+You can set **removeMissionAfterTerminate** to **true** in the **module.json5** file.
+
+## Why can't I start a UIAbility instance by using startAbility\(\)?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+-   If the UIAbility is started using **startAbility**, check whether the **abilityName** field in **want** uses the bundle name as the prefix. If yes, delete the bundle name.
+-   Make sure the UIAbility's home page file configured by **onWindowStageCreate** in the **MainAbility.ts** file is defined in the **main\_pages.json** file. You are advised to use the SDK and OpenHarmony SDK versions released on the same day.
 
 ## How do I prevent "this" in a method from changing to "undefined" when the method is called?
 
-Applicable to: OpenHarmony SDK 3.2.5.3, stage model of API version 9
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
 
-Method 1: Add **.bind(this)** when calling the method.
+Method 1: Add **.bind\(this\)** when calling the method.
 
 Method 2: Use the arrow function.
 
-## What should I do when the message "must have required property 'startWindowIcon'" is displayed?
+## What should I do when the error message "must have required property 'startWindowIcon'" is displayed during the UIAbility startup?
 
-Applicable to: OpenHarmony SDK 3.2.3.5, stage model of API version 9
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
-Configure the **startWindowIcon** attribute under **abilities** in the **module.json5** file.
+**Solution**
 
-Reference: [Application Package Structure (Stage Model)](../quick-start/module-configuration-file.md)
+Configure the **startWindowIcon** attribute under **abilities** in the **module.json5** file.
 
-Example:
+**Example**
 
 ```
 {
@@ -77,138 +133,226 @@ Example:
 }
 ```
 
-## How do I obtain a notification when the device orientation changes?
-
-Applicable to: OpenHarmony SDK 3.2.3.5, stage model of API version 9
+**Reference**
 
-Implement the **onConfigurationUpdated** callback in the **Ability** class. The callback is triggered when the system language, color mode, or display parameters (such as the orientation and density) change.
+[module.json5 Configuration File](../quick-start/module-configuration-file.md)
 
 ## Can I obtain the context through globalThis in the stage model?
 
-Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+Do not use **globalThis** to obtain the context in the stage model.
+
+This is because all the processes of an application share a JS VM instance in the stage model. Multiple abilities can run on these processes and share the same global object. If **globalThis** is used, the context of different abilities of the same JS VM instance may be returned.
+
+**Reference**
+
+[Data Synchronization Between UIAbility and UI](../application-models/uiability-data-sync-with-ui.md)
 
-Do not use **globalThis** to obtain the context in the stage model. This is because all the processes of an application share a JS VM instance in the stage model. Multiple abilities can run on these processes and share the same global object. If **globalThis** is used, the context of different abilities of the same JS VM instance may be returned.
+## What should I do when an error indicating too large size is reported during HAP deployment?
 
-Reference of the recommended operation: [Context (Stage Model)](../application-models/application-context-stage.md)
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
-## How do I obtain the HAP installation path of application B from application A?
+**Symptom**
 
-Applicable to: OpenHarmony SDK 3.0 or later, stage model of API version 9
+During HAP deployment, the following error message is displayed:
 
-First, request the system permission. For details, see [Having Your App Automatically Signed](https://developer.harmonyos.com/en/docs/documentation/doc-guides/ohos-auto-configuring-signature-information-0000001271659465). Then, import the **bundle** module, and call **bundle.getApplicationInfo()** to obtain application information based on the bundle name. Finally, use **application.moduleSourceDirs** to obtain the application storage path.
+Failure\[INSTALL\_FAILED\_SIZE\_TOO\_LARGE\] error while deploying hap?
+
+**Solution**
+
+You can split the HAP into multiple HAPs.
 
 ## How is data returned when startAbilityForResult is called?
 
-Applicable to: OpenHarmony SDK3.0, stage model of API version 9
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
-The callee uses **AbilityContext.terminateSelfWithResult** to destroy its ability and pass parameters to **startAbilityForResult**. For details, see [AbilityContext](../reference/apis/js-apis-ability-context.md#abilitycontextterminateselfwithresult).
+**Solution**
 
-## Can the lifecycle callback of a released FA widget be triggered when the widget is displayed in the service center so that the user login information can be obtained without opening the FA application?
+The target UIAbilities uses **AbilityContext.terminateSelfWithResult** to terminate itselef and pass the result to **startAbilityForResult**.
 
-Applicable to: OpenHarmony SDK 3.2.5.5, FA model of API version 8
+**Reference**
 
-After a widget is added, the **oncreate()** lifecycle is triggered so that related user information (silent login) can be displayed even when the application is not started. However, users must manually add the widget after the application is installed.
+[Starting UIAbility in the Same Application and Obtaining the Return Result](../application-models/uiability-intra-device-interaction.md)
 
-## How do I obtain the context?
 
-Applicable to: OpenHarmony SDK 3.2.7.5, stage model of API version 9
+## How do I obtain the system timestamp?
 
-You can use **this.context** to obtain the context in the **MainAbility.ts** file or call **getContext(this)** to obtain the context on the component page.
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
-## What should I do when undefined is displayed for the calling of **abilityAccessCtrl.grantUserGrantedPermission** during API version 8 syntax verification?
+**Solution**
 
-Applicable to: OpenHarmony SDK 3.0, FA model of API version 8
+Use **getCurrentTime** of **@ohos.systemDateTime** to obtain the system time and time zone.
 
-**abilityAccessCtrl.grantUserGrantedPermission** is a system API. It is not available in the public SDK, which is provided as default on DevEco Studio. To use system APIs, switch to the full SDK. For details, see [Guide to Switching to Full SDK](../quick-start/full-sdk-switch-guide.md).
+**Example**
 
-## Which of the following Extension abilities are available in the public SDK: ServiceExtensionAbility, FormExtensionAbility, and DataShareExtensionAbility?
+Use the **@ohos.systemDateTime** API as follows:
 
-Applicable to: OpenHarmony SDK 3.2.5.6, stage model of API version 9
+    ```
+    try {
+      systemDateTime.getCurrentTime(true, (error, time) => {
+        if (error) {
+          console.info(`Failed to get currentTime. message: ${error.message}, code: ${error.code}`);
+          return;
+        }
+        console.info(`Succeeded in getting currentTime : ${time}`);
+      });
+    } catch(e) {
+      console.info(`Failed to get currentTime. message: ${e.message}, code: ${e.code}`);
+    }
+    ```
 
-Among the aforementioned Extension abilities, only **FormExtensionAbility** is available in the public SDK. **ServiceExtensionAbility** and **DataShareExtensionAbility** are system APIs and available only in the full SDK.
 
-Public SDK: intended for application developers and does not contain system APIs that require system permissions.
+**Reference**
 
-Full SDK: intended for original equipment manufacturers (OEMs) and contains system APIs that require system permissions.
+[System time and time zone] (../reference/apis/js-apis-system-date-time.md#systemdatetimegetcurrenttime)
 
-## Why can't I play GIF images cyclically on the widget?
+## How do I obtain the cache directory of the current application?
 
-Applicable to: OpenHarmony SDK 3.2.5.6, stage model of API version 9
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
-The system does not support the display of GIF images on the widget.
+**Solution**
 
-## How do I implement service login by touching a widget?
+Use **Context.cacheDir** to obtain the cache directory of the application.
 
-Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9
+**Reference**
 
-You can start an ability upon the touch and implement service login in the ability.
+[Obtaining the Application Development Path](../application-models/application-context-stage.md#obtaining-the-application-development-path)
 
-## How do I redirect to the application details page in Settings?
+## In which JS file is the service widget lifecycle callback invoked?
 
-Applicable to: OpenHarmony SDK 3.2.6.5
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
-Refer to the following code:
+**Solution**
 
-```
-this.context.startAbility(
-{
-  action: "action.settings.app.info",
-  parameters: { "settingsParamBundleName": "your app bundlename" }
-})
-```
+When a widget is created, a **FormAblity.ts** file is generated, which contains the widget lifecycle.
 
-## How do I listen for screen rotation events?
+**Reference**
 
-Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9
+[FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md)
 
-Refer to the following code:
+## What should I do when the compilation on DevEco Studio fails while ServiceExtensionAbility and DataShareExtensionAbility APIs are used?
 
-```
-let listener = mediaquery.matchMediaSync('(orientation: landscape)')
-onPortrait(mediaQueryResult) {
-if (mediaQueryResult.matches) {
-// Do something here.
-    } else {
-// Do something here.
-    }
-}
-listener.on('change', onPortrait)
-```
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Symptom**
+
+After the **ServiceExtensionAbility** and **DataShareExtensionAbility** APIs are used, DevEco Studio reports an error indicating that the compilation fails.
+
+**Cause**
+
+The following types of SDKs are provided:
+
+-   Public SDK: intended for application developers and does not contain system APIs that require system permissions.
+-   Full SDK: intended for original equipment manufacturers (OEMs) and contains system APIs that require system permissions.
+
+The SDK downloaded using DevEco Studio is the public SDK.
+
+**Solution**
+
+Third-party application cannot use **ServiceExtensionAbility** and **DataShareExtensionAbility**. To develop a system application, first [download the full SDK](../quick-start/full-sdk-switch-guide.md).
+
+## How do I obtain the temp and files paths at the application level?
+
+Applicable to: OpenHarmony 3.2 Beta5
+
+**Solution**
+
+Obtain them from the application context. Specifically, use **this.context.getApplicationContext.tempDir** i to obtain the **temp** path, and use **this.context.getApplicationContext.filesDir** to obtain the **files** path.
+
+**Reference**
+
+[Obtaining the Application Development Path](../application-models/application-context-stage.md#obtaining-the-application-development-path)
+
+
+## Can the lifecycle callback of a released FA widget be triggered when the widget is displayed in the service center so that the user login information can be obtained without opening the FA application? 
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
-## How do I control the shadow background size during checkbox selection?
+**Solution**
 
-Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9
+After a widget is added, the **onCreate()** lifecycle is triggered so that related user information (silent login) can be displayed even when the application is not started. However, users must manually add the widget after the application is installed.
 
-Set the **padding** attribute of the **\<checkbox>** component to control the shadow size.
+## How do I implement service login by touching a widget?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+To create a service widget in the FA model, perform the following steps:
+
+1. Implement lifecycle callbacks for the widget.
+
+2. Configure the widget configuration file.
+
+3. Persistently store widget data.
 
-## How do I set the widget background to transparent?
+4. Update widget data.
 
-Applicable to: OpenHarmony SDK 3.2.5.5
+5. Develop the widget UI page.
 
-1. Create the **widget/resources/styles/default.json** file in the root directory of the widget.
+6. Develop a widget event. You can start a UIAbility upon the touch and implement service login in the UIAbility.
 
-2. Add the following code to the **default.json** file:
+**Reference**
+
+[Widget Development in the FA Model](../application-models/widget-development-fa.md)
+
+## How do I redirect to the application details page in Settings?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+Refer to the following code:
 
 ```
-{  
- "style": {   
-      "app_background": "#00000000"   
-   } 
-}
+this.context.startAbility(
+{
+  action: "action.settings.app.info",
+  parameters: { "settingsParamBundleName": "your app bundlename" }
+})
 ```
 
-## How do I pass parameters for FA widgets?
-
-Applicable to: OpenHarmony SDK 3.2.5.5
+## How do I get UIAbilityContext within the @Component component in the stage model?
 
-Use **featureAbility.getWant()** and **featureAbility.getContext()** to send data through **router** in the JSON file and use **featureAbility** to receive data in the JS file.
+Applicable to: OpenHarmony 3.2 Beta5 (API version 9)
 
-## How do I trigger router.disableAlertBeforeBackPage and router.enableAlertBeforeBackPage?
+**Solution**
 
-Applicable to: OpenHarmony SDK 3.2.5.5
+You can use **UIAbility.Context** to obtain the context.
 
-The following conditions must be met:
+**Example**
 
-1. Before the redirection to the previous page, a confirm dialog box will be displayed. Note that **router.disableAlertBeforeBackPage** is used to disable the display of a confirm dialog box before returning to the previous page (default), and **router.enableAlertBeforeBackPage** is used to enable the display.
+```
+import UIAbility from '@ohos.app.ability.UIAbility';
+
+let UIAbilityContext = UIAbility.context;
+let ApplicationContext = UIAbility.context.getApplicationContext();
+@Entry
+@Component
+struct AbilityContextTest {
+  // abilityContext
+  @State UIabilityInfo: string = 'Obtaining abilityInfo'
+  UIabilityContext: UIAbilityContext
+
+  aboutToAppear() {
+    // Use getContext to obtain the context and convert it to abilityContext.
+    this.UIabilityContext = getContext(this) as UIAbilityContext
+  }
 
-2. The system return key is used.
+  build() {
+    Row() {
+      Column({ space: 20 }) {
+        Text(this.abilityInfo)
+          .fontSize(20)
+          .onClick(()=>{
+            this.UIabilityInfo = JSON.stringify(this.UIabilityContext.UIabilityInfo)
+            console.log(`ContextDemo abilityInfo= ${this.UIabilityInfo}`)
+          })
+      }
+      .width('100%')
+    }
+    .height('100%')
+  }
+}
+```
diff --git a/en/application-dev/faqs/faqs-bundle-management.md b/en/application-dev/faqs/faqs-bundle-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..71b1e01ffcffea415266fb90213fc722e4f5b628
--- /dev/null
+++ b/en/application-dev/faqs/faqs-bundle-management.md
@@ -0,0 +1,126 @@
+# Bundle Management Development
+
+## How do I determine whether an application is a system application?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+Use **bundleManager.getApplicationInfo** (available only for system applications) to obtain application information, and check the value of **systemApp** in the information. The application is a system application if the value is **true**.
+
+**Reference**
+
+[bundleManager](../reference/apis/js-apis-bundleManager.md)
+
+## How do I obtain the version code and version name of an application?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+Use **bundleManager.getBundleInfoForSelf\(\)** to obtain the bundle information, which contains the version code (specified by **BundleInfo.versionCode**) and version name (specified by **BundleInfo.versionName**) .
+
+**Example**
+
+```
+import bundleManager from '@ohos.bundle.bundleManager';
+import hilog from '@ohos.hilog';
+let bundleFlags = bundleManager.BundleFlag.GET_BUNDLE_INFO_DEFAULT;
+try {
+  bundleManager.getBundleInfoForSelf(bundleFlags).then((data) => {
+    const versionCode = data.versionCode;
+    const versionName = data.versionName;
+    hilog.info(0x0000, 'testTag', `successfully. versionCode: ${versionCode}, versionName: ${versionName}`);    
+  }).catch(err => {
+    hilog.error(0x0000, 'testTag', 'failed. Cause: %{public}s', err.message);
+  });
+} catch (err) {
+  hilog.error(0x0000, 'testTag', 'failed: %{public}s', err.message);
+}
+```
+
+**Reference**
+
+[getBundleInfoForSelf](../reference/apis/js-apis-bundleManager.md#bundlemanagergetbundleinfoforself)
+
+## How do I obtain the bundle name of the current application?
+
+Applicable to: OpenHarmony 3.2 Beta5 (API version 9)
+
+**Solution**
+
+Obtain the bundle name from **UIAbilityContext.abilityInfo.bundleName**.
+
+**Example**
+
+```
+import common from '@ohos.app.ability.common';
+const context = getContext(this) as common.UIAbilityContext
+console.log(`bundleName: ${context.abilityInfo.bundleName}`)
+```
+
+**Reference**
+
+[UIAbilityContext](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontext) and [AbilityInfo](../reference/apis/js-apis-bundleManager-abilityInfo.md#abilityinfo)
+
+## How do I obtain the application version number, version name, and screen resolution?
+
+Applicable to: OpenHarmony 3.2 Beta5
+
+**Solution**
+
+1.  Obtain the bundle information from the **@ohos.bundle.bundleManager** module.
+
+    The bundle information contains the application version number and version name.
+
+    ```
+    import bundleManager from '@ohos.bundle.bundleManager';
+    ...
+    bundleManager.getBundleInfoForSelf(bundleManager.BundleFlag.GET_BUNDLE_INFO_WITH_APPLICATION).then((bundleInfo)=>{
+      let versionName = bundleInfo.versionName; // Application version name.
+      let versionNo = bundleInfo.versionCode; // Application version number.
+    }).catch((error)=>{
+      console.error("get bundleInfo failed,error is "+error)
+    })
+    ```
+
+2.  Obtain **screenDensity** from the **@ohos.app.ability.Configuration** module. **screenDensity** contains the screen resolution information.
+
+    ```
+    import common from '@ohos.app.ability.common';
+    ...
+    let context = getContext(this) as common.UIAbilityContext;
+    let screenDensity = context.config.screenDensity;
+    ```
+
+
+## How do I obtain the source file path of the current application?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+-   Method 1: Use the application context to obtain the source file path.
+
+    ```
+    this.uiAbilityContext.abilityInfo.applicationInfo.codePath
+    ```
+
+-   Method 2: Use **@ohos.bundle.bundleManager** to obtain the source file path.
+
+    1.  Import the **@ohos.bundle.bundleManager** module and use **bundleManager.getBundleInfoForSelf\(\)** to obtain the bundle information.
+    2.  Obtain the source file path from **bundleInfo.appInfo.codePath**.
+
+    ```
+    import bundleManager from '@ohos.bundle.bundleManager';
+    bundleManager.getBundleInfoForSelf(bundleManager.BundleFlag.GET_BUNDLE_INFO_WITH_APPLICATION).then((bundleInfo)=>{
+      this.sourcePath = bundleInfo.appInfo.codePath;
+    })
+    ```
+
+
+## Can I obtain the HAP information of other applications from the current application?
+
+Applicable to: OpenHarmony 3.2 Beta (API version 9)
+
+According to the OpenHarmony security design specifications, the SDK does not provide APIs for third-party applications to obtain bundle information (including but not limited to the application name and version number) of other applications.
diff --git a/en/application-dev/faqs/faqs-bundle.md b/en/application-dev/faqs/faqs-bundle.md
deleted file mode 100644
index fda41c42bccc357d6b8800ce3f5401e1e2abbceb..0000000000000000000000000000000000000000
--- a/en/application-dev/faqs/faqs-bundle.md
+++ /dev/null
@@ -1,31 +0,0 @@
-# Bundle Management Development
-
-## How do I obtain the version code and version name of an application?
-
-Applicable to: OpenHarmony SDK 3.2.3.5, stage model of API version 9
-
-Use **bundle.getBundleInfo()** to obtain the bundle information, which contains the version code and version name.
-
-Reference: [Bundle](../reference/apis/js-apis-Bundle.md#bundlegetbundleinfo)
-
-## How do I obtain the bundle name of an application?
-
-Applicable to: OpenHarmony SDK 3.2.3.5, stage model of API version 9
-
-Obtain the bundle name through **context.abilityInfo.bundleName**.
-
-Reference: [AbilityInfo](../reference/apis/js-apis-bundle-AbilityInfo.md)
-
-## How do I obtain an application icon?
-
-Applicable to: OpenHarmony SDK 3.2.3.5, stage model of API version 9
-
-Use **bundle.getAbilityIcon** to obtain the application icon. To use this API, you must configure the permission **ohos.permission.GET_BUNDLE_INFO**.
-
-Reference: [Bundle](../reference/apis/js-apis-Bundle.md#bundlegetbundleinfo)
-
-## How do I determine whether an application is a system application?
-
-Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9
-
-Use **bundle.getApplicationInfo** to obtain the application information, and then check the value of **systemApp** in the information. The application is a system application if the value is **true**.
diff --git a/en/application-dev/faqs/faqs-distributed-data-management.md b/en/application-dev/faqs/faqs-distributed-data-management.md
new file mode 100644
index 0000000000000000000000000000000000000000..c44b7b254ae85280e00430621845dd82d7e2fca6
--- /dev/null
+++ b/en/application-dev/faqs/faqs-distributed-data-management.md
@@ -0,0 +1,101 @@
+# Data Management Development
+
+
+## How do I encrypt an RDB store?
+
+Applicable to: OpenHarmony 3.1 Beta 5 (API version 9)
+
+**Solution**
+
+To encrypt an RDB store, set **encrypt** in **StoreConfig** to **true** when creating the RDB store.
+
+**Reference**
+
+[RDB Store](../reference/apis/js-apis-data-relationalStore.md#storeconfig)
+
+## What if I failed to clear a table in an RDB store using TRUNCATE TABLE?
+
+Applicable to: OpenHarmony SDK 3.2.9.2 (API version 9)
+
+**Symptom**
+
+An error is reported when the **TRUNCATE TABLE** statement is used to clear table data.
+
+**Solution**
+
+The RDB store uses SQLite and does not support the **TRUNCATE TABLE** statement. To clear a table in an RDB store, use the **DELETE** statement, for example, **DELETE FROM sqlite\_sequence WHERE name = 'table\_name'**.
+
+
+
+## What data types does an RDB store support?
+
+Applicable to: OpenHarmony SDK 3.0 or later, API version 9 stage model
+
+**Solution**
+
+An RDB store supports data of the number, string, and Boolean types. The number type supports data of the Double, Long, Float, Int, or Int64 type, with a maximum precision of 17 decimal digits.
+
+## How do I save pixel map data to a database? 
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Symptom**
+
+Pixel map data fails to be stored.
+
+**Solution**
+
+Convert the pixel map data into an **ArrayBuffer** and save the **ArrayBuffer** to your database.
+
+**Reference**
+
+[readPixelsToBuffer](../reference/apis/js-apis-image.md#readpixelstobuffer7-1)
+
+## How do I obtain RDB store files?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+The RDB store files are stored in **/data/app/el2/100/database/*Bundle_name*/entry/rdb/**. You can use the hdc command to copy the file from the directory and use a SQLite tool to open the file.
+
+Example:
+
+```
+ hdc file recv /data/app/el2/100/database/<bundleName>/entry/db/<tableName>  ./<path>
+```
+
+## Do the OpenHarmony databases have a lock mechanism?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+The distributed data service (DDS), RDB store, and preferences provided OpenHarmony have a lock mechanism. You do not need to bother with the lock mechanism during the development.
+
+## What if I failed to use get() to obtain the data saved by @ohos.data.storage put()?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Symptom**
+
+After @ohos.data.storage **put()** is called to save data, **get()** is called to obtain the data. However, the data fails to be obtained.
+
+**Solution**
+
+The **put()** method provided by **@ohos.data.storage** saves data in the memory. When the application exits, the data in the memory will be cleared. If you want to persist the data, you need to call **flush()** or **flushSync()** after **put()**. After data is persisted, you can use **get()** to obtain the data after the application is restarted.
+
+
+## What if a large text file fails to be saved in an RDB store?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Symptom**
+
+In API version 8, large text files cannot be saved in RDB stores.
+
+**Solution**
+
+In versions earlier than API version 9, the maximum length of a text file is 1024 bytes. If the text file exceeds 1024 bytes, it cannot be saved.
+
+The limit on the text file size has been removed since API9 version.
diff --git a/en/application-dev/faqs/faqs-distributed-device-profile.md b/en/application-dev/faqs/faqs-distributed-device-profile.md
new file mode 100644
index 0000000000000000000000000000000000000000..8473e3d4bfcb36c02d3260312cf5379cb436d8a6
--- /dev/null
+++ b/en/application-dev/faqs/faqs-distributed-device-profile.md
@@ -0,0 +1,9 @@
+# Distributed Device Development
+
+## How do I view the IMEI of an OpenHarmony device?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+Obtain the device IMEI from the **HUKS\_TAG\_ATTESTATION\_ID\_IMEI** parameter of the **HuksTag** API. [Reference](../reference/apis/js-apis-huks.md)
diff --git a/en/application-dev/faqs/faqs-file-management.md b/en/application-dev/faqs/faqs-file-management.md
index 6214cbc6b61aadc0e7501fbf3166d050b46500cb..85763b7eb00f9b8805786e80c208ea4059e8bb0e 100644
--- a/en/application-dev/faqs/faqs-file-management.md
+++ b/en/application-dev/faqs/faqs-file-management.md
@@ -1,107 +1,21 @@
 # File Management Development
 
-## Does fileio.rmdir Delete Files Recursively?
+## How do I obtain the path of system screenshots?
 
-Applicable to: OpenHarmony SDK 3.2.6.3, stage model of API version 9
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
-Yes. **fileio.rmdir** deletes files recursively.
+**Solution**
 
-## How Do I Create a File That Does Not Exist?
+The screenshots are stored in **/storage/media/100/local/files/Pictures/Screenshots/**.
 
-Applicable to: OpenHarmony SDK 3.2.6.3, stage model of API version 9
+## How do I change the permissions on a directory to read/write on a device?
 
-You can use **fileio.open(filePath, 0o100, 0o666)**. The second parameter **0o100** means to create a file if it does not exist. The third parameter **mode** must also be specified.
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
 
-## What If "call fail callback fail, code: 202, data: json arguments illegal" Is Displayed?
+**Symptom**
 
-Applicable to: OpenHarmony SDK 3.2.6.3, stage model of API version 9
+When the hdc command is used to send a file to a device, "permission denied" is displayed.
 
-When the **fileio** module is used to copy files, the file path cannot start with "file:///".
+**Solution**
 
-## How Do I Read Files Outside the App Sandbox?
-
-Applicable to: OpenHarmony SDK 3.2.6.5, stage model of API version 9
-
-If the input parameter of the **fileio** API is **path**, only the sandbox directory of the current app obtained from the context can be accessed. To access data in other directories such as the user data, images, and videos, open the file as the data owner and operate with the file descriptor (FD) returned.
-
-For example, to read or write a file in Media Library, perform the following steps:
-
-1. Use **getFileAssets()** to obtain the **fileAsset** object.
-
-2. Use **fileAsset.open()** to obtain the FD.
-
-3. Use the obtained FD as the **fileIo** API parameter to read and write the file.
-
-## What If the File Contains Garbled Characters?
-
-Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9
-
-Read the file content from the buffer, and decode the file content using **util.TextDecoder**.
-
-Example:
-
-```
-import util from '@ohos.util' 
-async function readFile(path) { 
-  let stream = fileio.createStreamSync(path, "r+"); 
-  let readOut = await stream.read(new ArrayBuffer(4096)); 
-  let textDecoder = new util.TextDecoder("utf-8", { ignoreBOM: true }); 
-  let buffer = new Uint8Array(readOut.buffer)
-  let readString = textDecoder.decode(buffer, { stream: false }); 
-  console.log ("[Demo] File content read: "+ readString);
-}
-```
-
-## What Should I Do If There Is No Return Value or Error Captured After getAlbums Is Called?
-
-Applicable to: OpenHarmony SDK 3.2.5.3, stage model of API version 9
-
-The **ohos.permission.READ_MEDIA** is required for using **getAlbums()**. In addition, this permission needs user authorization. For details, see [OpenHarmony Permission List](../security/permission-list.md).
-
-1. Configure the required permission in the **module.json5** file.
-  
-   ```
-   "requestPermissions": [
-     {
-       "name": "ohos.permission.READ_MEDIA"
-     }
-   ]
-   ```
-
-2. Add the code for user authorization before the **MainAbility.ts -> onWindowStageCreate** page is loaded.
-  
-   ```
-   import abilityAccessCtrl from '@ohos.abilityAccessCtrl.d.ts';
-   
-   private requestPermissions() {
-   let permissionList: Array<string> = [
-     "ohos.permission.READ_MEDIA"
-   ];
-   let atManager = abilityAccessCtrl.createAtManager();
-   atManager.requestPermissionsFromUser(this.context, permissionList)
-     .then(data => {
-       console.info(`request permission data result = ${data.authResults}`)
-     })
-     .catch(err => {
-       console.error(`fail to request permission error:${err}`)
-     })
-   }
-   ```
-
-## What Do I Do If the App Crashes When FetchFileResult() Is Called Multiple Times?
-
-Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9
-
-Each time after the **FetchFileResult** object is called, call **FetchFileResult.close()** to release and invalidate the **FetchFileResult** object .
-
-## What If An Error Is Reported by IDE When mediaLibrary.getMediaLibrary() Is Called in the Stage Model?
-
-Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9
-
-In the stage model, use **mediaLibrary.getMediaLibrary(context: Context)** to obtain the media library instance.
-
-## How Do I Sort the Data Returned by mediaLibrary.getFileAssets()?
-
-Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9
-
-Use the **order** attribute in **[MediaFetchOptions](../reference/apis/js-apis-medialibrary.md#mediafetchoptions7)** to sort the data returned.
+Run the **hdc shell mount -o remount,rw /** command to grant the read/write permissions.
diff --git a/en/application-dev/faqs/faqs-graphics.md b/en/application-dev/faqs/faqs-graphics.md
index 7eeba0644721dbf77174680f3c6c6d0ac0db05cf..9469a35736ef859342d2c24bdcb9780e94445bf8 100644
--- a/en/application-dev/faqs/faqs-graphics.md
+++ b/en/application-dev/faqs/faqs-graphics.md
@@ -1,90 +1,92 @@
-# Graphics and Image Development
+# Graphics Development
 
-## Why do the isStatusBarLightIcon and isNavigationBarLightIcon attributes not take effect when window.setSystemBarProperties() is called?
+## How do I obtain the DPI of a device?
 
-Applicable to: OpenHarmony SDK 3.2.5.3, stage model of API version 9
+Applicable to: OpenHarmony 3.2 Beta5 (API version 9, stage model)
 
-In effect, the **isStatusBarLightIcon** and **isNavigationBarLightIcon** attributes turn the font white when set to **true**. If **statusBarContentColor** is also set in **window.setSystemBarProperties()**, the **isStatusBarLightIcon** attribute does not take effect. Similarly, if **navigationBarContentColor** is set, the **isNavigationBarLightIcon** attribute does not take effect.
+**Solution**
 
-## How do I set the style of the system bar?
+Import the **@ohos.display** module and call the **getDefaultDisplaySync\(\)** API.
 
-Applicable to: OpenHarmony SDK 3.2.3.5, stage model of API version 9
+**Example**
 
-Import the **\@ohos.window** module, and call **window.setSystemBarProperties()**.
+```
+import display from '@ohos.display'; 
+let displayClass = null;
+try {
+  displayClass = display.getDefaultDisplaySync();
+  console.info('Test densityDPI:' + JSON.stringify(displayClass.densityDPI));
+} catch (exception) {
+  console.error('Failed to obtain the default display object. Code: ' + JSON.stringify(exception));
+}
+```
 
 ## How do I hide the status bar to get the immersive effect?
 
-Applicable to: OpenHarmony SDK 3.2.6.3, stage model of API version 9
-
-1. Use the **onWindowStageCreate** to obtain a **windowClass** object.
-   
-   ```ts
-   onWindowStageCreate(windowStage) {
-     // When the main window is created, set the main page for this ability.
-     console.log("[Demo] EntryAbility onWindowStageCreate")
-     windowStage.getMainWindow((err, data) => {
-       if (err.code) {
-         console.error('Failed to obtain the main window.')
-         return;
-       }
-       // Obtain a windowClass object.
-       globalThis.windowClass = data; 
-     })
-   }
-   ```
-
-2. Enable the full-screen mode for the window and hide the status bar.
-   
-   ```ts
-    globalThis.windowClass.setFullScreen(isFullScreen, (err, data) => {
-     if (err.code) {
-       console.error('Failed to enable the full-screen mode. Cause:' + JSON.stringify(err));
-       return;
-     }
-       console.info('Succeeded in enabling the full-screen mode. Data: ' + JSON.stringify(data));
-     });
-   ```
+Applicable to: OpenHarmony 3.2 Beta5 (API version 9, stage model) 
+
+**Solution**
+
+1.  Use **onWindowStageCreate** to obtain a **windowClass** object.
+
+    ```
+    onWindowStageCreate(windowStage) {
+      // When the main window is created, set the main page for this ability.
+      console.log("[Demo] MainAbility onWindowStageCreate")
+      windowStage.getMainWindow((err, data) => {
+        if (err.code) {
+          console.error('Failed to obtain the main window.')
+          return;
+        }
+        // Obtain a windowClass object.
+        globalThis.windowClass = data; 
+      })
+    }
+    ```
+
+2.  Enable the full-screen mode for the window and hide the status bar.
+
+    ```
+     globalThis.windowClass.setFullScreen(isFullScreen, (err, data) => {
+      if (err.code) {
+        console.error('Failed to enable the full-screen mode. Cause:' + JSON.stringify(err));
+        return;
+      }
+        console.info('Succeeded in enabling the full-screen mode. Data: ' + JSON.stringify(data));
+      });
+    ```
+
 
 ## How do I obtain the window width and height?
 
-Applicable to: OpenHarmony SDK 3.2.3.5, stage model of API version 9
+Applicable to: OpenHarmony SDK 3.2 Beta5 (API version 9, stage model) 
 
-Use **window.getProperties()** to obtain the window properties. The **windowRect** field in the properties specifies the window width and height.
+**Solution**
 
-Example:
+Import the **@ohos.window** module, obtain a **Window** object, and use **getWindowProperties\(\)** of the object to obtain the window properties. The **windowRect** field in the properties specifies the window width and height.
 
+**Example**
 
-```ts
-let promise = windowClass.getProperties();
-promise.then((data)=> {
-  console.info('Succeeded in obtaining the window properties. Data: ' + JSON.stringify(data.windowRect));
-}).catch((err)=>{
-  console.error('Failed to obtain the window properties. Cause: ' + JSON.stringify(err));
-});
 ```
-
-## How do I set the color of the system bar?
-
-Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9
-
-Refer to the following code:
-
-
-```ts
-window.getTopWindow(globalThis.mainContext).then(win => {
-  var systemBarProperties = {
-    statusBarColor: '#19B6FF', // Set the background color of the status bar.
-    navigationBarColor: '#19B6FF', // Set the background color of the navigation bar.
-    isStatusBarLightIcon: false, // Set the icon on the status bar not to be highlighted.
-    isNavigationBarLightIcon: true, // Set the icon on the navigation bar to be highlighted.
-    statusBarContentColor: '#0D0500', // Set the text color of the status bar.
-    navigationBarContentColor: '#FFA500' // Set the text color of the navigation bar.
-  };
-  win.setSystemBarProperties(systemBarProperties).catch(err => {
-    INDEX_LOGGER.info(`set System Bar Properties failed:${err}`)
-  })
-})
-.catch(err => {
-  INDEX_LOGGER.info(`get top window failed:${err}`)
-})
+import window from '@ohos.window';
+let windowClass = null;
+try {    
+    let promise = window.getLastWindow(this.context);
+    promise.then((data)=> {
+        // Obtain a Window object.
+        windowClass = data;
+        try {
+            // Obtain the window properties.
+            let properties = windowClass.getWindowProperties();
+            let rect = properties.windowRect;
+            // rect.width: window width; rect.height: window height.
+        } catch (exception) {
+             console.error('Failed to obtain the window properties. Cause: ' + JSON.stringify(exception));
+        }
+        console.info('Succeeded in obtaining the top window. Data: ' + JSON.stringify(data));
+    }).catch((err)=>{
+        console.error('Failed to obtain the top window. Cause: ' + JSON.stringify(err));
+    });} catch (exception) {
+    console.error('Failed to obtain the top window. Cause: ' + JSON.stringify(exception));
+}
 ```
diff --git a/en/application-dev/faqs/faqs-multimedia.md b/en/application-dev/faqs/faqs-multimedia.md
new file mode 100644
index 0000000000000000000000000000000000000000..080860a9a5ca913d1d40d9de049f9220a66118da
--- /dev/null
+++ b/en/application-dev/faqs/faqs-multimedia.md
@@ -0,0 +1,135 @@
+# Multimedia Development
+
+## How do I obtain the frame data of a camera when using the XComponent to display the preview output stream of the camera?
+
+Applicable to: OpenHarmony 3.2 (API version 9, stage model)
+
+**Symptom**
+
+Currently, the API does not support real-time preview of the camera frame data. To obtain the frame data, you must bind an action, for example, photographing.
+
+**Solution**
+
+Create a dual-channel preview to obtain the frame data.
+
+1. Use the XComponent to create a preview stream.
+
+    ```
+    // Obtain a PreviewOutput instance.
+    const surfaceId = globalThis.mxXComponentController.getXComponentSurfaceld();
+    this.mPreviewOutput = await Camera.createPreviewOutput(surfaceld) ;
+    ```
+
+2. Use imageReceiver to listen for image information.
+
+    ```
+    // Add dual-channel preview.
+    const fullWidth = this.mFullScreenSize.width;
+    const fullHeight = this.mFullScreenSize.height;
+    const imageReceiver = await image.createImageReceiver(fullwidth, fullHeight, 
+      formatImage, capacityImage) ;
+    const photoSurfaceId = await imageReceiver.getReceivingSurfaceld();
+    this.mPreviewOutputDouble = await Camera.createPreviewOutput ( photoSurfaceld)
+    ```
+
+
+## How do I obtain the preview image of the front camera?
+
+Applicable to: OpenHarmony 3.2 (API version 9, stage model)
+
+**Solution**
+
+1. Use the **@ohos.multimedia.camera** module to obtain the physical camera information.
+
+    ```
+    let cameraManager = await camera.getCameraManager(context);
+    let camerasInfo = await cameraManager.getSupportedCameras();
+    let cameraDevice = this.camerasInfo[0];
+    ```
+
+2. Create and start the input stream channel of the physical camera.
+
+    ```
+    let cameraInput = await cameraManager.createCameraInput(cameraDevice);
+    await this.cameraInput.open();
+    ```
+
+3. Obtain the output formats supported by the camera, and create a preview output channel based on the surface ID provided by the XComponent.
+
+    ```
+    let outputCapability = await this.cameraManager.getSupportedOutputCapability(cameraDevice);
+    let previewProfile = this.outputCapability.previewProfiles[0];
+    let previewOutput = await cameraManager.createPreviewOutput(previewProfile, previewId);
+    ```
+
+4. Create a camera session, add the camera input stream and preview output stream to the session, and start the session. The preview image is displayed on the XComponent.
+
+    ```
+    let captureSession = await cameraManager.createCaptureSession();
+    await captureSession.beginConfig();
+    await captureSession.addInput(cameraInput);
+    await captureSession.addOutput(previewOutput);
+    await this.captureSession.commitConfig()
+    await this.captureSession.start();
+    ```
+
+
+## How do I set the camera focal length?
+
+Applicable to: OpenHarmony 3.2 (API version 9, stage model)
+
+**Solution**
+
+1. Check whether the camera is a front camera. A front camera does not support focal length setting.
+2. Use **captureSession.getZoomRatioRange\(\)** to obtain the focal length range supported by the device.
+3. Check whether the target focal length is within the range obtained. If yes, call **captureSession.setZoomRatio\(\)** to set the focal length.
+
+## How do I play music in the background?
+
+Applicable to: OpenHarmony 3.2 (API version 9, stage model)
+
+**Symptom**
+
+Music cannot be played in the background.
+
+**Solution**
+
+**AVSession** controls media playback. When a third-party application switches to the background or encounters a screen lock event, media playback is forcibly paused and the application is unaware of the pause. To enable the application to continue the playback in the background, request a continuous task and access the AVSession capability, which allows Control Panel to control the playback behavior of third-party applications.
+
+**Reference**
+
+[Continuous Task Development](../task-management/continuous-task-dev-guide.md)
+
+[AVSession Development](../media/using-avsession-developer.md)
+
+
+## What should I do when multiple video components cannot be used for playback?
+
+Applicable to: OpenHarmony 3.2 (API version 9, stage model)
+
+**Symptom**
+
+A large number of video components are created. They cannot play media normally or even crash.
+
+**Solution**
+
+A maximum of 13 media player instances can be created.
+
+
+## How do I invoke the image library directly?
+
+Applicable to: OpenHarmony 3.2 (API version 9, stage model)
+
+**Solution**
+
+```
+let want = {
+  bundleName: 'com.ohos.photos',
+  abilityName: 'com.ohos.photos.MainAbility',
+  parameters: {
+ uri: 'detail'
+  }
+};
+let context = getContext(this) as common.UIAbilityContext;
+context.startAbility(want);
+```
diff --git a/en/application-dev/faqs/faqs-security.md b/en/application-dev/faqs/faqs-security.md
new file mode 100644
index 0000000000000000000000000000000000000000..691739a0c288a3315e27e1f54700ba4e2637ddb3
--- /dev/null
+++ b/en/application-dev/faqs/faqs-security.md
@@ -0,0 +1,41 @@
+# Basic Security Capability Development
+
+## What is the maximum number of bytes that can be encrypted at a time in AES GCM mode in HUKS?
+
+Applicable to: OpenHarmony 3.1 Beta 5 (API version 9)
+
+**Solution**
+
+In HUKS, a maximum of 64 bytes can be encrypted at a time in AES GCM mode.
+
+**Example**
+
+```
+/* Encrypt the key. */
+await huks.init(srcKeyAlias, encryptOptions).then((data) => {
+ console.info(`test init data: ${JSON.stringify(data)}`);
+ handle = data.handle;
+}).catch((err) => {
+ console.info('test init err information: ' + JSON.stringify(err));
+});
+encryptOptions.inData = aesCipherStringToUint8Array(cipherInData.slice (0,64)); // Take 64 bytes.
+await huks.update(handle, encryptOptions).then(async (data) => {
+ console.info(`test update data ${JSON.stringify(data)}`);
+ encryptUpdateResult = Array.from(data.outData);
+}).catch((err) => {
+ console.info('test update err information: ' + err);
+});
+encryptOptions.inData = aesCipherStringToUint8Array(cipherInData.slice (64,80)); // Remaining data
+```
+
+## What if garbled characters are returned by **digest()** of **Md** in Crypto framework?
+
+Applicable to: OpenHarmony 3.1 Beta 5 (API version 9)
+
+**Symptom**
+
+In the CryptoFramework, garbled characters are returned by **digest()** of **Md**.
+
+**Solution**
+
+The DataBlob returned by **digest()** is of the Uint8Array type and needs to be converted into a hexadecimal string before being printed. You can use the online MD5 encryption tool to verify the result.
diff --git a/en/application-dev/faqs/faqs-sensor.md b/en/application-dev/faqs/faqs-sensor.md
new file mode 100644
index 0000000000000000000000000000000000000000..3932b223fb5c6af755c9eae019851e37edfa6ef4
--- /dev/null
+++ b/en/application-dev/faqs/faqs-sensor.md
@@ -0,0 +1,7 @@
+# Pan-Sensor Development
+
+## Are the APIs used for obtaining PPG and ECG sensor data open to individual developers?
+
+Applicable to: OpenHarmony 3.1 Beta 5 (API version 9)
+
+Data collected by the PPG and ECG sensors of wearable devices is personal privacy data. Therefore, relative APIs are not open to individual developers.
diff --git a/en/application-dev/faqs/faqs-third-fourth-party-library.md b/en/application-dev/faqs/faqs-third-fourth-party-library.md
index 898055cd200805d8df549b33bb2c5f3b4b05bca6..045a3f5efe77b0ad16b64960bbf015b62b07d46f 100644
--- a/en/application-dev/faqs/faqs-third-fourth-party-library.md
+++ b/en/application-dev/faqs/faqs-third-fourth-party-library.md
@@ -1,74 +1,69 @@
 # Usage of Third- and Fourth-Party Libraries
 
-## What does the following error message mean: "Stage model module... does not support including OpenHarmony npm packages or modules in FA model. OpenHarmony build tasks will not be executed, and OpenHarmony resources will not be packed."  
+## How do I obtain available third-party libraries?
 
-Applicable to: OpenHarmony SDK 3.2.5.3, stage model of API version 9
+Applicable to: OpenHarmony 3.1 Beta 5 (API version 9)
 
-The third- and fourth-party libraries are not yet compatible with the stage model of API version 9 and cannot be used.
+The three-party and four-party libraries that can be obtained through ohpm are summarized in the [OpenHarmony-TPC/tpc_resource repository](https://gitee.com/openharmony-tpc/tpc_resource). You can access this repository, and find the desired component based on the directory index.
 
-## Can I transfer project-level dependencies?
+## Which third-party libraries are related to network requests?
 
-Applicable to: OpenHarmony SDK 3.2.5.3, stage model of API version 9
+Applicable to: OpenHarmony 3.1 Beta 5 (API version 9)
 
-For example, if project A depends on project B and project B depends on project C, can project A directly use the APIs provided by project C?
+The following third-party libraries are related to network requests: [Axios](https://gitee.com/openharmony-sig/axios), httpclient, and okdownload. For details, see the [OpenHarmony-TPC/tpc_resource repository](https://gitee.com/openharmony-tpc/tpc_resource).
 
-No. Project A cannot directly use the APIs provided by project C. The project packing tool NPM does not support dependency transfer. To use the APIs provided by project C, you can add the dependency of project C to project A.
+## How do I use ohpm to import third- and fourth-party libraries?
 
-## How do I obtain available third-party libraries?
+Applicable to: OpenHarmony 3.1 Beta 5 (API version 9)
 
-Applicable to: OpenHarmony SDK 3.2.6.5, stage model of API version 9
+**Solution**
 
-For details, see [Third-Party Components That Can Be Directly Used on OpenHarmony](https://gitee.com/openharmony-sig/third_party_app_libs).
+-   Method 1:
+    1.  Open the **Terminal** window and run the following command to go to the **entry** directory:
 
-## Which third-party libraries are related to network requests?
+        ```
+        cd entry
+        ```
+
+    2.  Run the following command to install a third-party library, for example, **dayjs**:
+
+        ```
+        ohpm install dayjs
+        ```
+
+    3.  Add the following statement in the .js file to import the third-party library:
+
+        ```
+        import dayjs from 'dayjs'; 
+        ```
 
-Applicable to: OpenHarmony SDK 3.2.6.5, stage model of API version 9
-
-The [Axios](https://gitee.com/openharmony-sig/axios) library is related to network requests.
-
-## How do I use NPM to import third- and fourth-party libraries?
-
-Applicable to: OpenHarmony SDK 3.2.5.5, stage model of API version 9
-- Method 1:
-  1. Open the **Terminal** window and run the following command to go to the **entry** directory:
-     
-      ```
-      cd entry
-      ```
-  2. Run the following command to install a third-party package, for example, **dayjs**:
-     
-      ```
-      npm install dayjs --save
-      ```
-  3. Add the following statement in the .js file to import the package:
-     
-      ```
-      import dayjs from 'dayjs'; 
-      ```
-
-- Method 2:
-  1. Enter the **entry** directory of the project and open the **package.json** file.
-  2. Write the third-party NPM package to be installed (for example, **dayjs**) in the **package.json** file.
-     
-      ```
-      {
-        "dependencies": {
-          "dayjs": "^1.10.4",
+
+-   Method 2:
+    1.  Enter the **entry** directory of the project and open the **oh-package.json5** file.
+    2.  Write the third-party library to be installed (for example, **dayjs**) in the **oh-package.json5** file.
+
+        ```
+        {
+          "dependencies": {
+            "dayjs": "^1.10.4",
+          }
         }
-      }
-      ```
-  3. Open the **Terminal** window and run the following command to go to the **entry** directory:
-     
-      ```
-      cd entry
-      ```
-  4. Run the following command to install NPM:
-     
-      ```
-      npm install
-      ```
-  5. Add the following statement in the .js file to import the package:
-     
-      ```
-      import dayjs from 'dayjs'; 
-      ```
+        ```
+
+    3.  Open the **Terminal** window and run the following command to go to the **entry** directory:
+
+        ```
+        cd entry
+        ```
+
+    4.  Run the following command to install the third-party library:
+
+        ```
+        ohpm install
+        ```
+
+    5.  Add the following statement in the .js file to import the third-party library:
+
+        ```
+        import dayjs from 'dayjs'; 
+        ```
diff --git a/en/application-dev/faqs/faqs-window-manager.md b/en/application-dev/faqs/faqs-window-manager.md
new file mode 100644
index 0000000000000000000000000000000000000000..7368ec7cbb95ee0235810464d822554cf2b1880d
--- /dev/null
+++ b/en/application-dev/faqs/faqs-window-manager.md
@@ -0,0 +1,64 @@
+# Window Management Development
+
+## How do I obtain the height of the status bar and navigation bar?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+Before the window content is loaded, enable listening for the **systemAvoidAreaChange** event.
+
+**Example**
+
+```
+// MainAbility.ts
+import window from '@ohos.window';
+
+/**
+ * Set the immersive window and obtain the height of the status bar and navigation bar.
+ * @param mainWindow Indicates the main window.
+ */
+async function enterImmersion(mainWindow: window.Window) { 
+  mainWindow.on("systemBarTintChange", (data) => {
+    let avoidAreaRect = data.regionTint[0].region; // data.regionTint is an array that contains the rectangle coordinates of the status bar and navigation bar.
+  })
+  await mainWindow.setFullScreen(true)
+  await mainWindow.setSystemBarEnable(["status", "navigation"])
+  await mainWindow.systemBarProperties({
+    navigationBarColor: "#00000000",
+    statusBarColor: "#00000000",
+    navigationBarContentColor: "#FF0000",
+    statusBarContentColor: "#FF0000"
+  })
+}
+export default class MainAbility extends Ability {
+  // Do something.
+  async onWindowStageCreate(windowStage: window.WindowStage) {
+    let mainWindow = await windowStage.getMainWindow()
+    await enterImmersion(mainWindow)
+    windowStage.loadContent('pages/index')
+  }
+  // Do something.
+}
+```
+
+## How do I hide the status bar on the top of an application?
+
+Applicable to: OpenHarmony 3.2 Beta 5 (API version 9)
+
+**Solution**
+
+Use **setWindowSystemBarEnable** in the **onWindowStageCreate** lifecycle callback of UIAbility.
+
+**Example**
+
+```
+onWindowStageCreate(windowStage){
+  windowStage.getMainWindowSync().setWindowSystemBarEnable([])
+  ......
+}
+```
+
+**Reference**
+
+[Window](../reference/apis/js-apis-window.md)
diff --git a/en/application-dev/file-management/app-sandbox-directory.md b/en/application-dev/file-management/app-sandbox-directory.md
index 7d06b330aa085aa34045c5491b5855160744f44a..3424dfbc9ec457e5ab6839e521fde5caad0dd3ae 100644
--- a/en/application-dev/file-management/app-sandbox-directory.md
+++ b/en/application-dev/file-management/app-sandbox-directory.md
@@ -73,7 +73,7 @@ The following figure shows the application file directories. The path of a file
    | distributedfiles | distributedFilesDir | Distributed file directory| Directory in **el2** for saving the application files that can be directly accessed across devices.<br>This directory is cleared when the application is uninstalled.| 
    | files | filesDir | Application file directory| Directory for saving the application's persistent files on the device.<br>This directory is cleared when the application is uninstalled.| 
    | cache | cacheDir | Application cache file directory| Directory for caching the downloaded files of the application or saving the cache files regenerated on the device.<br>This directory is automatically cleared when the size of the **cache** directory reaches the quota or the system storage space reaches a certain threshold. The user can also clear this directory by using a system space management application. <br>The application needs to check whether the file still exists and determine whether to cache the file again.| 
-   | preferences | preferencesDir | Preferences file directory| Directory for saving common application configuration and user preference data managed by using database APIs.<br>This directory is cleared when the application is uninstalled. For details, see [Data Persistence by User Preferences](../database/data-persistence-by-preferences.md).| 
+   | preferences | preferencesDir | Preferences file directory| Directory for saving common application configuration and user preference data managed by using database APIs.<br>This directory is cleared when the application is uninstalled. For details, see [Persisting Preferences Data](../database/data-persistence-by-preferences.md).| 
    | temp | tempDir | Temporary file directory| Directory for saving the files generated and required during the application's runtime on the device. <br>This directory is cleared when the application exits.| 
 
    The application file paths are used in the following scenarios:
@@ -92,5 +92,3 @@ The following figure shows the application file directories. The path of a file
       Used to store application preferences data, including preference files and configuration files. This directory applied to storing only a small amount of data.
    - Temporary file directory<br>
       Used to store temporarily generated data of an application, including cached database data and images, temporary log files, downloaded application installation package files. The data stored in this directory is deleted after being used.
-
-<!--no_check-->
\ No newline at end of file
diff --git a/en/application-dev/file-management/file-management-overview.md b/en/application-dev/file-management/file-management-overview.md
index a159a3348eb7892a68a334c64ae0b69288e24d1d..2fbd4b4a036de1f20f8aa64825ab1dcb60f23414 100644
--- a/en/application-dev/file-management/file-management-overview.md
+++ b/en/application-dev/file-management/file-management-overview.md
@@ -23,6 +23,3 @@ The file systems can be classified into the following types based on the file st
 **Figure 1** Files in an OS
 
 ![File classification model](figures/file-classification-model.png)
-
-
-<!--no_check-->
\ No newline at end of file
diff --git a/en/application-dev/file-management/select-user-file.md b/en/application-dev/file-management/select-user-file.md
index 77fc2dd23c080c357d1749df4bb3ca551cba3a0d..c87015b50235ff9c54721668c019caea9119a5ae 100644
--- a/en/application-dev/file-management/select-user-file.md
+++ b/en/application-dev/file-management/select-user-file.md
@@ -63,7 +63,11 @@ The **FilePicker** provides the following interfaces by file type:
    ```
 
 3. Create a **documentViewPicker** instance, and call [**select()**](../reference/apis/js-apis-file-picker.md#select-3) to open the **FilePicker** page for the user to select documents.
+
      After the documents are selected successfully, a result set containing the file URIs is returned. Further operations can be performed on the documents based on the file URIs.
+
+   For example, you can use [file management APIs](../reference/apis/js-apis-file-fs.md) to obtain file attribute information, such as the file size, access time, and last modification time, based on the URI. If you need to obtain the file name, use [startAbilityForResult](../../application-dev/application-models/uiability-intra-device-interaction.md).
+
    > **NOTE**
    >
    > Currently, **DocumentSelectOptions** is not configurable. By default, all types of user files are selected.
@@ -80,6 +84,32 @@ The **FilePicker** provides the following interfaces by file type:
      })
    ```
 
+   > **NOTE**
+   >
+   > Currently, **DocumentSelectOptions** does not provide the method for obtaining the file name. To obtain the file name, use **startAbilityForResult()**.
+
+   ```ts
+   let config = {
+     action: 'ohos.want.action.OPEN_FILE',
+     parameters: {
+       startMode: 'choose',
+     }
+   }
+   try {
+     let result = await context.startAbilityForResult(config, {windowMode: 1});
+     if (result.resultCode !== 0) {
+       console.error(`DocumentPicker.select failed, code is ${result.resultCode}, message is ${result.want.parameters.message}`);
+       return;
+     }
+     // Obtain the URI of the document.
+     let select_item_list = result.want.parameters.select_item_list;
+     // Obtain the name of the document.
+     let file_name_list = result.want.parameters.file_name_list;
+   } catch (err) {
+     console.error(`Invoke documentPicker.select failed, code is ${err.code}, message is ${err.message}`);
+   }
+   ```
+
 ## Selecting an Audio File
 
 1. Import the **FilePicker** module.
diff --git a/en/application-dev/file-management/set-security-label.md b/en/application-dev/file-management/set-security-label.md
index 94ad527767e443b532330e207a45653980cdfa71..af819fba397d47f81b0ebe005e67f9e6c8ebef39 100644
--- a/en/application-dev/file-management/set-security-label.md
+++ b/en/application-dev/file-management/set-security-label.md
@@ -1,6 +1,6 @@
 # Setting the Security Level of a Distributed File
 
-The security capabilities vary with devices. For example, small embedded devices provide fewer security capabilities than tablets. The security requirements also vary with data. For example, personal health information and bank card information are not expected to be accessed by devices of lower security levels. OpenHarmony provides a complete set of standards for data and device classification and custom data transfer policies for different devices. For details, see [Data and Device Security Classification](../database/access-control-by-device-and-data-level.md).
+The security capabilities vary with devices. For example, small embedded devices provide fewer security capabilities than tablets. The security requirements also vary with data. For example, personal health information and bank card information are not expected to be accessed by devices of lower security levels. OpenHarmony provides a complete set of standards for data and device classification and custom data transfer policies for different devices. For details, see [Data Security Labels and Device Security Levels](../database/access-control-by-device-and-data-level.md).
 
 ## Available APIs
 
@@ -39,4 +39,3 @@ securityLabel.setSecurityLabel(filePath, 's0').then(() => {
   console.error(`Failed to setSecurityLabel. Code: ${err.code}, message: ${err.message}`);
 });
 ```
-<!--no_check-->
\ No newline at end of file
diff --git a/en/application-dev/file-management/share-app-file.md b/en/application-dev/file-management/share-app-file.md
index d9ee1d90904f5cdb43cd1987a66b09668200bc81..4261861bad51dc312d0ccfc5ab0a7f4d8f404426 100644
--- a/en/application-dev/file-management/share-app-file.md
+++ b/en/application-dev/file-management/share-app-file.md
@@ -6,13 +6,13 @@ The file of an application can be shared with another application based on the f
 
 - You can also use **open()** of the ohos.file.fs module to share an application file with the specified permissions to another application based on the FD. After parsing the FD from **Want**, the target application can read and write the file by using **read()** and **write()** APIs of ohos.file.fs.
 
-You can use the related APIs to [share a file with another application](#sharing-a-file-with-another-application) or [use shared application files](#using-shared-files).
+You can use the related APIs to [share a file with another application](#sharing-a-file-with-another-application) or [use shared application files](#using-shared-application-files).
 
 ## File URI Specifications
 
 The file URIs are in the following format:
 
-  file://&lt;bundleName&gt;/&lt;path&gt;/\#networkid=&lt;networkid&gt;
+  file://&lt;bundleName&gt;/&lt;path&gt;
 
 - **file**: indicates a file URI.
 
@@ -20,8 +20,6 @@ The file URIs are in the following format:
 
 - *path*: specifies the application sandbox path of the file.
 
-- *networkid* (optional): specifies the device to which the file belongs in a distributed file system. Leave this parameter unspecified if the file location does not need to be set.
-
 ## Sharing a File with Another Application
 
 Before sharing application files, you need to [obtain the application file path](../application-models/application-context-stage.md#obtaining-the-application-development-path).
diff --git a/en/application-dev/media/using-avsession-developer.md b/en/application-dev/media/using-avsession-developer.md
index 07bd4bf1297f3afc5352d30e9acd674fe056f815..077f0b956a5fb6abaf26c647132bdbb81e78fc63 100644
--- a/en/application-dev/media/using-avsession-developer.md
+++ b/en/application-dev/media/using-avsession-developer.md
@@ -88,7 +88,7 @@ To enable an audio and video application to access the AVSession service as a pr
    ```ts
    // It is assumed that an AVSession object has been created. For details about how to create an AVSession object, see the node snippet above.
    let session: AVSessionManager.AVSession = ALLREADY_CREATE_A_SESSION;
-   let wantAgentInfo: {
+   let wantAgentInfo = {
        wants: [
            {
                bundleName: "com.example.musicdemo",
diff --git a/en/application-dev/quick-start/arkts-basic-syntax-overview.md b/en/application-dev/quick-start/arkts-basic-syntax-overview.md
index 59dd8e9e0ebb02f4f76b59985fe45e2e6b1f4cdd..885acf30122e0b2971ee51a4e0f399f63ab0f1c2 100644
--- a/en/application-dev/quick-start/arkts-basic-syntax-overview.md
+++ b/en/application-dev/quick-start/arkts-basic-syntax-overview.md
@@ -23,9 +23,9 @@ In this example, the basic composition of ArkTS is as follows.
 
 - [Custom component](arkts-create-custom-components.md): reusable UI unit, which can be combined with other components, such as the struct **Hello** decorated by @Component.
 
-- Built-in component: default basic or container component preset in ArkTS, which can be directly invoked, such as** \<Column>**,** \<Text>**, **\<Divider>**, and **\<Button>** components in the sample code.
+- Built-in component: default basic or container component preset in ArkTS, which can be directly invoked, such as **\<Column>**, **\<Text>**, **\<Divider>**, and **\<Button>** components in the sample code.
 
-- Attribute method: method used to configure component attributes, such as **fontSize()**, **width()**, **height()**, and **color()**. You can configure multiple attributes of a component in method chaining mode.
+- Attribute method: method used to configure component attributes, such as **fontSize()**, **width()**, **height()**, and **backgroundColor()**. You can configure multiple attributes of a component in method chaining mode.
 
 - Event method: method used to add the logic for a component to respond to an event. In the sample code, **onClick()** following **Button** is an event method. You can configure response logic for multiple events in method chaining mode.
 
diff --git a/en/application-dev/quick-start/atomicService.md b/en/application-dev/quick-start/atomicService.md
index 2b099a0a37c9eec4185fef8f1796243e282dd473..11c72a89e180c02454ee4d5a15af474620fc194f 100644
--- a/en/application-dev/quick-start/atomicService.md
+++ b/en/application-dev/quick-start/atomicService.md
@@ -77,7 +77,7 @@ Pre-loading is triggered after the first frame of the newly accessed module is r
   "module": {
     "name": "entry",
     "type": "entry",
-    "srcEnty": "./ets/Application/MyAbilityStage.ts",
+    "srcEntry": "./ets/Application/MyAbilityStage.ts",
     "description": "$string:entry_desc",
     "mainElement": "MainAbility",
     "deviceTypes": [
@@ -97,7 +97,7 @@ Pre-loading is triggered after the first frame of the newly accessed module is r
     "abilities": [
       {
         "name": "MainAbility",
-        "srcEnty": "./ets/MainAbility/MainAbility.ts",
+        "srcEntry": "./ets/MainAbility/MainAbility.ts",
         "description": "$string:MainAbility_desc",
         "icon": "$media:icon",
         "label": "$string:MainAbility_label",
@@ -169,7 +169,7 @@ import router from '@ohos.router';
 @Entry
 @Component
 struct Index {
-    @State message: string = 'Hello World'
+    @State message: string = 'Hello World';
 
     build() {
     Row() {
@@ -209,10 +209,10 @@ struct Index {
 ```
 
 The input parameter **url** of the **router.pushUrl** API is as follows:
-```ets
+```ts
 '@bundle:com.example.hmservice/library/ets/pages/menu'
 ```
 The **url** content template is as follows:
-```ets
+```ts
 '@bundle:bundle name/module name/path/page file name (without the extension .ets)'
 ```
diff --git a/en/application-dev/quick-start/figures/01.png b/en/application-dev/quick-start/figures/01.png
deleted file mode 100644
index 8342856ec6643e20a941187852e6aef3ead11010..0000000000000000000000000000000000000000
Binary files a/en/application-dev/quick-start/figures/01.png and /dev/null differ
diff --git a/en/application-dev/quick-start/figures/02.png b/en/application-dev/quick-start/figures/02.png
deleted file mode 100644
index eef374a1fd63f2b1e4d72e3323e7f4c23f5705fb..0000000000000000000000000000000000000000
Binary files a/en/application-dev/quick-start/figures/02.png and /dev/null differ
diff --git a/en/application-dev/quick-start/figures/04.png b/en/application-dev/quick-start/figures/04.png
deleted file mode 100644
index 1190d1e5aa631b12171632d258e4c4fae32e9bba..0000000000000000000000000000000000000000
Binary files a/en/application-dev/quick-start/figures/04.png and /dev/null differ
diff --git a/en/application-dev/quick-start/figures/07.png b/en/application-dev/quick-start/figures/07.png
deleted file mode 100644
index 17f2b060d300667ff250935b6a37485843e854ce..0000000000000000000000000000000000000000
Binary files a/en/application-dev/quick-start/figures/07.png and /dev/null differ
diff --git a/en/application-dev/quick-start/figures/chooseFAModel_ets.png b/en/application-dev/quick-start/figures/chooseFAModel_ets.png
new file mode 100644
index 0000000000000000000000000000000000000000..784659f8b0efaf71620d06dd0df5c58d22ac47f4
Binary files /dev/null and b/en/application-dev/quick-start/figures/chooseFAModel_ets.png differ
diff --git a/en/application-dev/quick-start/figures/chooseFAModel_js.png b/en/application-dev/quick-start/figures/chooseFAModel_js.png
new file mode 100644
index 0000000000000000000000000000000000000000..4d121aa3a9a1e3ba68cc5f70f6944fcfa3cef792
Binary files /dev/null and b/en/application-dev/quick-start/figures/chooseFAModel_js.png differ
diff --git a/en/application-dev/quick-start/figures/chooseStageModel.png b/en/application-dev/quick-start/figures/chooseStageModel.png
new file mode 100644
index 0000000000000000000000000000000000000000..3125c8ba0591ce0c53344f35fb780eb956601624
Binary files /dev/null and b/en/application-dev/quick-start/figures/chooseStageModel.png differ
diff --git a/en/application-dev/quick-start/figures/createProject.png b/en/application-dev/quick-start/figures/createProject.png
new file mode 100644
index 0000000000000000000000000000000000000000..7a56a44e0e7f80671b86c521792352db625ccad7
Binary files /dev/null and b/en/application-dev/quick-start/figures/createProject.png differ
diff --git a/en/application-dev/quick-start/figures/09.png b/en/application-dev/quick-start/figures/secondPage.png
similarity index 100%
rename from en/application-dev/quick-start/figures/09.png
rename to en/application-dev/quick-start/figures/secondPage.png
diff --git a/en/application-dev/quick-start/figures/06.png b/en/application-dev/quick-start/figures/signConfig.png
similarity index 100%
rename from en/application-dev/quick-start/figures/06.png
rename to en/application-dev/quick-start/figures/signConfig.png
diff --git a/en/application-dev/quick-start/in-app-hsp.md b/en/application-dev/quick-start/in-app-hsp.md
index cdd06b5dfb59a2c9609a7f327c95bae710943d3d..4c0cc3c7dffc1c41d0011dd644a94a84424808dc 100644
--- a/en/application-dev/quick-start/in-app-hsp.md
+++ b/en/application-dev/quick-start/in-app-hsp.md
@@ -1,7 +1,7 @@
 # In-Application HSP Development
 
 An in-application Harmony Shared Package (HSP) is a file used for code and resource sharing within an application (called the host application) and can only be invoked by a HAP or HSP of the same application.
-The in-application HSP is released with the Application Package (App Pack) of the host application and has the same bundle name and lifecycle as the host application.
+The in-application HSP is released with the Application Package (App Pack) of the host application, shares a process with the host application, and has the same bundle name and lifecycle as the host application.
 
 ## Developing an In-Application HSP
 
@@ -151,3 +151,59 @@ struct Index {
   }
 }
 ```
+
+### Redirecting to a Page in Another Bundle
+
+If you want to add a button in the **entry** module to jump to the menu page (**library/src/main/ets/pages/menu.ets**) in the **library** module, you can write the following code in the **entry/src/main/ets/MainAbility/Index.ets** file of the **entry** module:
+```ts
+import router from '@ohos.router';
+
+@Entry
+@Component
+struct Index {
+    @State message: string = 'Hello World'
+
+    build() {
+    Row() {
+        Column() {
+        Text(this.message)
+            .fontSize(50)
+            .fontWeight(FontWeight.Bold)
+        // Add a button to respond to user clicks.
+        Button() {
+            Text('click to menu')
+            .fontSize(30)
+            .fontWeight(FontWeight.Bold)
+        }
+        .type(ButtonType.Capsule)
+        .margin({
+            top: 20
+        })
+        .backgroundColor('#0D9FFB')
+        .width('40%')
+        .height('5%')
+        // Bind click events.
+        .onClick(() => {
+            router.pushUrl({
+              url: '@bundle:com.example.hmservice/library/ets/pages/menu'
+            }).then(() => {
+              console.log("push page success");
+            }).catch(err => {
+              console.error(`pushUrl failed, code is ${err.code}, message is ${err.message}`);
+            })
+        })
+      .width('100%')
+    }
+    .height('100%')
+    }
+  }
+}
+```
+The input parameter **url** of the **router.pushUrl** API is as follows:
+```ets
+'@bundle:com.example.hmservice/library/ets/pages/menu'
+```
+The **url** content template is as follows:
+```ets
+'@bundle:bundle name/module name/path/page file name (without the extension .ets)'
+```
diff --git a/en/application-dev/quick-start/module-configuration-file.md b/en/application-dev/quick-start/module-configuration-file.md
index 2d72ba6841b495a2d16fd50b9eac8f8d5b0eb6c0..58342507a06818c5cdb84996d63fe777c9eb34a5 100644
--- a/en/application-dev/quick-start/module-configuration-file.md
+++ b/en/application-dev/quick-start/module-configuration-file.md
@@ -1,7 +1,7 @@
 # module.json5 Configuration File
 
 
-This document gives an overview of the **module.json5** configuration file. To start with, let's go through an example of what this file contains.
+This topic gives an overview of the **module.json5** configuration file. To start with, let's go through an example of what this file contains.
 
 ```json
 {
@@ -79,7 +79,7 @@ As shown above, the **module.json5** file contains several tags.
 | mainElement | Name of the entry UIAbility or ExtensionAbility of the module. The value is a string with a maximum of 255 bytes.| String| Yes (initial value: left empty)|
 | [deviceTypes](#devicetypes) | Type of the device on which the module can run.| String array| No (can be left empty)|
 | deliveryWithInstall | Whether the HAP file of the module will be installed when the user installs the application.<br>- **true**: The HAP file will be installed when the user installs the application.<br>- **false**: The HAP file will not be installed when the user installs the application.| Boolean| No|
-| installationFree | Whether the module supports the installation-free feature.<br>- **true**: The module supports the installation-free feature and meets installation-free constraints.<br>- **false**: The module does not support the installation-free feature.<br>**NOTE**<br>- If this tag is set to **true** for an entry-type module, it must also be set to **true** for feature-type modules of the same application.<br>- If this tag is set to **false** for an entry-type module, it can be set to **true** or **false** for feature-type modules of the same application based on service requirements.| Boolean| No|
+| installationFree | Whether the module supports the installation-free feature.<br>- **true**: The module supports the installation-free feature and meets installation-free constraints.<br>- **false**: The module does not support the installation-free feature.<br>**NOTE**<br>If this tag is set to **true** for an entry-type module, it must also be set to **true** for feature-type modules of the same application.<br>If this tag is set to **false** for an entry-type module, it can be set to **true** or **false** for feature-type modules of the same application based on service requirements.| Boolean| No|
 | virtualMachine | Type of the target virtual machine (VM) where the module runs. It is used for cloud distribution, such as distribution by the application market and distribution center.<br> If the target VM type is ArkTS engine, the value is **ark**+*version number*.| String| Yes (initial value: automatically inserted when DevEco Studio builds the HAP file)|
 | [pages](#pages)| Profile that represents information about each page in the current module. The value can contain a maximum of 255 bytes.| String| No in the UIAbility scenario|
 | [metadata](#metadata)| Custom metadata of the module. The setting is valid only for the current module, UIAbility, or ExtensionAbility.| Object array| Yes (initial value: left empty)|
@@ -133,8 +133,21 @@ The **pages** tag is a profile that represents information about specified pages
 }
 ```
 
-Define the **main_pages.json** file under **resources/base/profile** in the development view. The base name of the file (**main_pages** in this example) can be customized, but must be consistent with the information specified by the **pages** tag. The file lists the page information of the current application.
+Define the **main_pages.json** file under **resources/base/profile** in the development view. The file name (**main_pages** in this example) can be customized, but must be consistent with the information specified by the **pages** tag. The file lists the page information of the current application, including the route information and the window-related configuration.
 
+  **Table 3** Tags in the pages configuration file
+
+| Name| Description| Data Type| Initial Value Allowed|
+| -------- | -------- | -------- | -------- |
+| src | Route information about all pages in the JavaScript module, including the page path and page name. The value is an array, each element of which represents a page and the first element represents the home page.| String array| No|
+| window | Window-related configuration.	 | Object| Yes (initial value: left empty)|
+
+  **Table 4** window tag in the pages configuration file
+
+| Name| Description| Data Type| Initial Value Allowed|
+| -------- | -------- | -------- | -------- |
+| designWidth | Baseline width for page design. The size of an element is scaled by the actual device width.| Number| Yes (initial value: **720px**)|
+| autoDesignWidth | Whether to automatically calculate the baseline width for page design. If it is set to **true**, the **designWidth** attribute becomes invalid. The baseline width is calculated based on the device width and screen density.| Boolean| Yes (initial value: **false**)|
 
 ```json
 {
@@ -143,7 +156,11 @@ Define the **main_pages.json** file under **resources/base/profile** in the deve
     "pages/second/payment",
     "pages/third/shopping_cart",
     "pages/four/owner"
-  ]
+  ],
+  "window": {
+    "designWidth": 720,
+    "autoDesignWidth": false
+  }
 }
 ```
 
@@ -152,7 +169,7 @@ Define the **main_pages.json** file under **resources/base/profile** in the deve
 
 The **metadata** tag represents the custom metadata of the HAP file. The tag value is an array and contains three subtags: **name**, **value**, and **resource**.
 
-**Table 3** metadata
+**Table 5** metadata
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
@@ -271,7 +288,7 @@ Set **icon**, **label**, and **skills** under **abilities** in the **module.json
 ![Application details screen](figures/application_details.jpg)
 
 
-  **Table 4** abilities
+  **Table 6** abilities
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
@@ -280,7 +297,7 @@ Set **icon**, **label**, and **skills** under **abilities** in the **module.json
 | [launchType](../application-models/uiability-launch-type.md) | Launch type of the UIAbility component. The options are as follows:<br>- **multiton**: A new UIAbility instance is created each time the UIAbility component is started.<br>- **singleton**: A new UIAbility instance is created only when the UIAbility component is started for the first time.<br>- **specified**: You can determine whether to create a new UIAbility instance when the application is running.| String| Yes (initial value: **"singleton"**)|
 | description | Description of the UIAbility component. The value is a string with a maximum of 255 bytes or a resource index to the description in multiple languages.| String| Yes (initial value: left empty)|
 | icon | Icon of the UIAbility component. The value is an icon resource index.| String| Yes (initial value: left empty)<br>If **UIAbility** is set to **MainElement**, this attribute is mandatory.|
-| label | Name of the UIAbility component displayed to users. The value is a string resource index.<br>If **UIAbility** is set to **MainElement** of the current module, this attribute is mandatory and its value must be unique in the application.| String| No|
+| label | Name of the UIAbility component displayed to users. The value is a string resource index.| String| Yes (initial value: left empty)<br>If **UIAbility** is set to **MainElement**, this attribute is mandatory.|
 | permissions | Permissions required for another application to access the UIAbility component.<br>The value is an array of permission names predefined by the system, generally in the reverse domain name notation. It contains a maximum of 255 bytes.| String array| Yes (initial value: left empty)|
 | [metadata](#metadata)| Metadata information of the UIAbility component.| Object array| Yes (initial value: left empty)|
 | exported | Whether the UIAbility component can be called by other applications.<br>- **true**: The UIAbility component can be called by other applications.<br>- **false**: The UIAbility component cannot be called by other applications.| Boolean| Yes (initial value: **false**)|
@@ -292,14 +309,14 @@ Set **icon**, **label**, and **skills** under **abilities** in the **module.json
 | removeMissionAfterTerminate | Whether to remove the relevant task from the task list after the UIAbility component is destroyed.<br>- **true**: Remove the relevant task from the task list after the UIAbility component is destroyed.<br>- **false**: Do not remove the relevant task from the task list after the UIAbility component is destroyed.| Boolean| Yes (initial value: **false**)|
 | orientation | Orientation of the UIAbility component when it is started. The options are as follows:<br>- **unspecified**: automatically determined by the system.<br>- **landscape**: landscape mode.<br>- **portrait**: portrait mode.<br>- **landscape_inverted**: inverted landscape mode.<br>- **portrait_inverted**: inverted portrait mode.<br>- **auto_rotation**: determined by the sensor.<br>- **auto_rotation_landscape**: determined by the sensor in the horizontal direction, including landscape and inverted landscape modes.<br>- **auto_rotation_portrait**: determined by the sensor in the vertical direction, including portrait and inverted portrait modes.<br>- **auto_rotation_restricted**: determined by the sensor when the sensor switch is enabled.<br>- **auto_rotation_landscape_restricted**: determined by the sensor in the horizontal direction, including landscape and inverted landscape modes, when the sensor switch is enabled.<br>- **auto_rotation_portrait_restricted**: determined by the sensor in the vertical direction, including portrait and inverted portrait modes, when the sensor switch is enabled.<br>- **locked**: auto rotation disabled.| String| Yes (initial value: **"unspecified"**)|
 | supportWindowMode | Window mode supported by the UIAbility component. The options are as follows:<br>- **fullscreen**: full-screen mode.<br>- **split**: split-screen mode.<br>- **floating**: floating window mode.| String array| Yes (initial value:<br>["fullscreen", "split", "floating"])|
-| priority | Priority of the UIAbility component. In the case of [implicit query](../application-models/explicit-implicit-want-mappings.md), UIAbility components with a higher priority are at the higher place of the returned list. The value is an integer ranging from 0 to 10. The greater the value, the higher the priority.<br>**NOTE**<br>This tag applies only to system applications and does not take effect for third-party applications.| Number| Yes (initial value: **0**)|
+| priority | Priority of the UIAbility component. In the case of [implicit query](../application-models/explicit-implicit-want-mappings.md), UIAbility components with a higher priority are at the higher place of the returned list. The value is an integer ranging from 0 to 10. The greater the value, the higher the priority.<br>**NOTE**<br>This attribute applies only to system applications and does not take effect for third-party applications.| Number| Yes (initial value: **0**)|
 | maxWindowRatio | Maximum aspect ratio supported by the UIAbility component. The minimum value is 0.| Number| Yes (initial value: maximum aspect ratio supported by the platform)|
 | minWindowRatio | Minimum aspect ratio supported by the UIAbility component. The minimum value is 0.| Number| Yes (initial value: minimum aspect ratio supported by the platform)|
 | maxWindowWidth | Maximum window width supported by the UIAbility component, in vp. The minimum value is 0, and the value cannot be less than the value of **minWindowWidth** or greater than the maximum window width allowed by the platform. For details about the window size, see [Constraints](../windowmanager/window-overview.md#constraints).| Number| Yes (initial value: maximum window width supported by the platform)|
 | minWindowWidth | Minimum window width supported by the UIAbility component, in vp. The minimum value is 0, and the value cannot be less than the minimum window width allowed by the platform or greater than the value of **maxWindowWidth**. For details about the window size, see [Constraints](../windowmanager/window-overview.md#constraints).| Number| Yes (initial value: minimum window width supported by the platform)|
 | maxWindowHeight | Maximum window height supported by the UIAbility component, in vp. The minimum value is 0, and the value cannot be less than the value of **minWindowHeight** or greater than the maximum window height allowed by the platform. For details about the window size, see [Constraints](../windowmanager/window-overview.md#constraints).| Number| Yes (initial value: maximum window height supported by the platform)|
 | minWindowHeight | Minimum window height supported by the UIAbility component, in vp. The minimum value is 0, and the value cannot be less than the minimum window height allowed by the platform or greater than the value of **maxWindowHeight**. For details about the window size, see [Constraints](../windowmanager/window-overview.md#constraints).| Number| Yes (initial value: minimum window height supported by the platform)|
-| excludeFromMissions | Whether the UIAbility component is displayed in the recent task list.<br>- **true**: displayed in the recent task list.<br>- **false**: not displayed in the recent task list.<br>**NOTE**<br>This tag applies only to system applications and does not take effect for third-party applications.| Boolean| Yes (initial value: **false**)|
+| excludeFromMissions | Whether the UIAbility component is displayed in the recent task list.<br>- **true**: displayed in the recent task list.<br>- **false**: not displayed in the recent task list.<br>**NOTE**<br>This attribute applies only to system applications and does not take effect for third-party applications.| Boolean| Yes (initial value: **false**)|
 
 Example of the **abilities** structure:
 
@@ -354,7 +371,7 @@ Example of the **abilities** structure:
 
 The **skills** tag represents the feature set of [wants](../application-models/want-overview.md) that can be received by the UIAbility or ExtensionAbility component.
 
-  **Table 5** skills
+  **Table 7** skills
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
@@ -362,7 +379,7 @@ The **skills** tag represents the feature set of [wants](../application-models/w
 | entities | [Entities](../application-models/actions-entities.md) of wants that can be received.| String array| Yes (initial value: left empty)|
 |uris | URIs that match the wants.| Object array| Yes (initial value: left empty)|
 
-  **Table 6** uris
+  **Table 8** Internal structure of the uris tag
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
@@ -403,12 +420,11 @@ Example of the **skills** structure:
 }
 ```
 
-
 ## extensionAbilities
 
 The **extensionAbilities** tag represents the configuration of extensionAbilities, which is valid only for the current extensionAbility.
 
-  **Table 7** extensionAbilities
+  **Table 9** extensionAbilities
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
@@ -419,8 +435,8 @@ The **extensionAbilities** tag represents the configuration of extensionAbilitie
 | label | Name of the ExtensionAbility component displayed to users. The value is a string resource index.<br>**NOTE**<br>If **ExtensionAbility** is set to **MainElement** of the current module, this attribute is mandatory and its value must be unique in the application.| String| No|
 | type | Type of the ExtensionAbility component. The options are as follows:<br>- **form**: ExtensionAbility of a widget.<br>- **workScheduler**: ExtensionAbility of a Work Scheduler task.<br>- **inputMethod**: ExtensionAbility of an input method.<br>- **service**: service component running in the background.<br>- **accessibility**: ExtensionAbility of an accessibility feature.<br>- **dataShare**: ExtensionAbility for data sharing.<br>- **fileShare**: ExtensionAbility for file sharing.<br>- **staticSubscriber**: ExtensionAbility for static broadcast.<br>- **wallpaper**: ExtensionAbility of the wallpaper.<br>- **backup**: ExtensionAbility for data backup.<br>- **window**: ExtensionAbility of a window. This type of ExtensionAbility creates a window during startup for which you can develop the GUI. The window is then combined with other application windows through **abilityComponent**.<br>- **thumbnail**: ExtensionAbility for obtaining file thumbnails. You can provide thumbnails for files of customized file types.<br>- **preview**: ExtensionAbility for preview. This type of ExtensionAbility can parse the file and display it in a window. You can combine the window with other application windows.<br>**NOTE**<br>The **service** and **dataShare** types apply only to system applications and do not take effect for third-party applications. | String| No|
 | permissions | Permissions required for another application to access the ExtensionAbility component.<br>The value is generally in the reverse domain name notation and contains a maximum of 255 bytes. It is an array of permission names predefined by the system or customized. The name of a customized permission must be the same as the **name** value of a permission defined in the **defPermissions** attribute.| String array| Yes (initial value: left empty)|
-| uri | Data URI provided by the ExtensionAbility component. The value is a string with a maximum of 255 bytes, in the reverse domain name notation.<br>**NOTE**<br>This attribute is mandatory when the type of the **ExtensionAbility** component is set to **dataShare**. | String| Yes (initial value: left empty)|
-|skills | Feature set of [wants](../application-models/want-overview.md) that can be received by the ExtensionAbility component.<br>Configuration rule: In an entry package, you can configure multiple **skills** attributes with the entry capability. (A **skills** attribute with the entry capability is the one that has **ohos.want.action.home** and **entity.system.home** configured.) The **label** and **icon** in the first ExtensionAbility that has **skills** configured are used as the **label** and **icon** of the entire OpenHarmony service/application.<br>**NOTE**<br>The **skills** attribute with the entry capability can be configured for the feature-type package of an OpenHarmony application, but not for an OpenHarmony service. | Array| Yes (initial value: left empty)|
+| uri | Data URI provided by the ExtensionAbility component. The value is a string with a maximum of 255 bytes, in the reverse domain name notation.<br>**NOTE**<br>This attribute is mandatory when the type of the ExtensionAbility component is set to **dataShare**.| String| Yes (initial value: left empty)|
+|skills | Feature set of [wants](../application-models/want-overview.md) that can be received by the ExtensionAbility component.<br>Configuration rule: In an entry package, you can configure multiple **skills** attributes with the entry capability. (A **skills** attribute with the entry capability is the one that has **ohos.want.action.home** and **entity.system.home** configured.) The **label** and **icon** in the first ExtensionAbility that has **skills** configured are used as the **label** and **icon** of the entire OpenHarmony service/application.<br>**NOTE**<br>The **skills** attribute with the entry capability can be configured for the feature package of an OpenHarmony application, but not for an OpenHarmony service.| Array| Yes (initial value: left empty)|
 | [metadata](#metadata)| Metadata of the ExtensionAbility component.| Object| Yes (initial value: left empty)|
 | exported | Whether the ExtensionAbility component can be called by other applications. <br>- **true**: The ExtensionAbility component can be called by other applications.<br>- **false**: The UIAbility component cannot be called by other applications.| Boolean| Yes (initial value: **false**)|
 
@@ -468,12 +484,12 @@ The **requestPermissions** tag represents a set of permissions that the applicat
 > - The permission settings configured in the **requestPermissions** tag apply to the entire application.
 > - If your application needs to subscribe to an event published by itself and the permissions required for accessing the application are set in the **permissions** tag under **extensionAbilities**, then the application must register the related permissions in the **requestPermissions** tag to receive the event.
 
-**Table 8** requestPermissions
+**Table 10** requestPermissions
 
 | Name| Description| Data Type| Value Range| Default Value|
 | -------- | -------- | -------- | -------- | -------- |
 | name | Permission name. This attribute is mandatory.| String| Custom| –|
-| reason | Reason for requesting the permission. This attribute is mandatory when the permission to request is **user_grant**.<br>**NOTE**<br>If the permission to request is **user_grant**, this attribute is required for the application to be released to the application market, and multi-language adaptation is required.| String| Resource reference of the string type in $string: \*\*\* format| A null value|
+| reason | Reason for requesting the permission. This attribute is mandatory when the permission to request is **user_grant**.<br>**NOTE**<br>If the permission to request is **user_grant**, this attribute is required for the application to be released to the application market. Multi-language adaptation is required.| String| Resource reference of the string type in $string: \*\*\* format| A null value|
 | usedScene | Scene under which the permission is used. It consists of the **abilities** and **when** sub-attributes. Multiple abilities can be configured.<br>**NOTE**<br>This attribute is optional by default. If the permission to request is **user_grant**, the **abilities** sub-attribute is mandatory and **when** is optional.| **abilities**: string array<br>**when**: string| **abilities**: array of names of UIAbility or ExtensionAbility components<br>**when**: **inuse** or **always**| **abilities**: null<br>**when**: null|
 
 Example of the **requestPermissions** structure:
@@ -508,7 +524,9 @@ The **shortcut** information is identified in **metadata**, where:
 - **name** indicates the name of the shortcut, identified by **ohos.ability.shortcuts**.
 
 - **resource** indicates where the resources of the shortcut are stored.
-  
+
+**Table 11** shortcuts
+
 | Name| Description| Data Type | Default Value|
 | -------- | -------- | -------- | -------- |
 | shortcutId | ID of the shortcut. The value is a string with a maximum of 63 bytes.| String| No|
@@ -518,7 +536,7 @@ The **shortcut** information is identified in **metadata**, where:
 
 
 1. Configure the **shortcuts_config.json** file in **/resource/base/profile/**.
-   
+
    ```json
    {
      "shortcuts": [
@@ -538,7 +556,7 @@ The **shortcut** information is identified in **metadata**, where:
    ```
 
 2. In the **abilities** tag of the **module.json5** file, configure the **metadata** tag for the UIAbility component to which a shortcut needs to be added so that the shortcut configuration file takes effect for the UIAbility.
-   
+
    ```json
    {
      "module": {
@@ -573,9 +591,9 @@ The **shortcut** information is identified in **metadata**, where:
 
 ## distributionFilter
 
-The **distributionFilter** tag defines the rules for distributing HAP files based on different device specifications, so that precise matching can be performed when the application market distributes applications. Distribution rules cover five factors: API version, screen shape, screen size, screen resolution, and country code. During distribution, a unique HAP is determined based on the mapping between **deviceType** and these five factors. This tag must be configured in the **/resource/profile resource** directory. Its sub-tags are optional.
+The **distributionFilter** tag defines the rules for distributing HAP files based on different device specifications, so that precise matching can be performed when the application market distributes applications. Distribution rules cover the following factors: screen shape, screen size, screen resolution, and country/region code. During distribution, a unique HAP is determined based on the mapping between **deviceType** and these five factors. This tag must be configured in the **/resource/profile resource** directory. Its sub-tags are optional.
 
-  **Table 9** distributionFilter
+  **Table 12** distributionFilter
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
@@ -585,28 +603,28 @@ The **distributionFilter** tag defines the rules for distributing HAP files base
 | countryCode | Code of the country or region to which the application is to be distributed. The value is subject to the ISO-3166-1 standard. Enumerated definitions of multiple countries and regions are supported.| Object array| Yes (initial value: left empty)|
 
 
-  **Table 10** screenShape
+  **Table 13** Internal structure of the screenShape tag
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
 | policy | Rule for the sub-attribute value. Set this attribute to **exclude** or **include**.<br>- **exclude**: Exclude the matches of the sub-attribute value.<br>- **include**: Include the matches of the sub-attribute value.| String| No|
 | value | Screen shapes. The value can be **circle**, **rect**, or both. Example: Different HAP files can be provided for a smart watch with a circular face and that with a rectangular face.| String array| No|
 
-  **Table 11** screenWindow
+  **Table 14** Internal structure of the screenWindow tag
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
 | policy | Rule for the sub-attribute value. Set this attribute to **exclude** or **include**.<br>- **exclude**: Exclude the matches of the sub-attribute value.<br>- **include**: Include the matches of the sub-attribute value.| String| No|
 | value | Screen width and height, in pixels. The value an array of supported width and height pairs, each in the "width * height" format, for example, **"454 * 454"**.| String array| No|
 
-  **Table 12** screenDensity
+  **Table 15** Internal structure of the screenDensity tag
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
 | policy | Rule for the sub-attribute value. Set this attribute to **exclude** or **include**.<br>- **exclude**: Exclude the matches of the sub-attribute value.<br>- **include**: Include the matches of the sub-attribute value.| String| No|
 | value | Pixel density of the screen, in DPI.| String array| No|
 
-  **Table 13** countryCode
+  **Table 16** Internal structure of the countryCode tag
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
@@ -673,7 +691,7 @@ Configure **metadata** in the **module** tag in the **module.json5** file.
 
 The **testRunner** tag represents the supported test runner.
 
-**Table 14** testRunner
+**Table 17** Internal structure of the testRunner tag
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
diff --git a/en/application-dev/quick-start/module-structure.md b/en/application-dev/quick-start/module-structure.md
index 31c244336ebc458997e4e3fd8ce8914896df40df..a18a1eae33ac116e9bb829b2d30dc34e344b935f 100644
--- a/en/application-dev/quick-start/module-structure.md
+++ b/en/application-dev/quick-start/module-structure.md
@@ -20,7 +20,7 @@ The **module** tag contains the HAP configuration.
 | shortcuts | Shortcuts of the application. The value is an array of objects, each of which represents a shortcut object.| Object array| Yes (initial value: left empty)|
 | reqPermissions | Permissions that the application requests from the system when it is running.| Object array| Yes (initial value: left empty)|
 | colorMode | Color mode of the application. The options are as follows:<br>- **dark**: Resources applicable for the dark mode are used.<br>- **light**: Resources applicable for the light mode are used.<br>- **auto**: Resources are used based on the color mode of the system.| String| Yes (initial value: **auto**)|
-| distroFilter | Distribution rules of the application. This attribute defines the rules for distributing HAP files based on different device specifications, so that precise matching can be performed when the application market distributes applications. Distribution rules cover three factors: API version, screen shape, and screen resolution. During distribution, a unique HAP is determined based on the mapping between **deviceType** and these three factors.| Object| Yes (initial value: left empty) Set this attribute when an application has multiple entry modules.|
+| distributionFilter | Distribution rules of the application. This attribute defines the rules for distributing HAP files based on different device specifications, so that precise matching can be performed when the application market distributes applications. Distribution rules cover three factors: API version, screen shape, and screen resolution. During distribution, a unique HAP is determined based on the mapping between **deviceType** and these three factors.| Object| Yes (initial value: left empty) Set this attribute when an application has multiple entry modules.|
 |commonEvents | Information about the common event static subscriber, which must contain the subscriber name, required permissions, and list of the common events subscribed to. When a subscribed event is sent, the static subscriber is started. Unlike the dynamic subscriber, the static subscriber does not need to proactively call the common event subscription API in the service code, and may not be running when the common event is published.| Object array| Yes (initial value: left empty)|
 | entryTheme | Keyword of an OpenHarmony internal theme. Set it to the resource index of the name.| String| Yes (initial value: left empty)|
 |testRunner | Test runner configuration.| Object| Yes (initial value: left empty)|
@@ -268,7 +268,7 @@ Note: The label displayed on the application details screen may be different fro
 | name | Ability name. The value can be a reverse domain name, in the format of "*bundleName*.*className*", for example, **"com.example.myapplication.EntryAbility"**. Alternatively, the value can start with a period (.) followed by the class name, for example, **".EntryAbility"**.<br>The ability name must be unique in an application. Note: If you use DevEco Studio to create the project, an ability named **EntryAbility** will be created by default, and its configuration will be saved to the **config.json** file. If you use other IDEs, the value of this attribute can be customized. The value can contain a maximum of 127 bytes.| String| No|
 | description | Description of the ability. The value can be a string or a resource index to descriptions in multiple languages. The value can contain a maximum of 255 bytes.| String| Yes (initial value: left empty)|
 | icon | Index to the ability icon file. Example value: **$media:ability_icon**. In the **skills** attribute of the ability, if the **actions** value contains **action.system.home** and the **entities** value contains **entity.system.home**, the icon of the ability is also used as the icon of the application. If multiple abilities address this condition, the icon of the first candidate ability is used as the application icon.<br>Note: The **icon** and **label** values of an application are visible to users. Ensure that at least one of them is different from any existing icons or labels.| String| Yes (initial value: left empty)|
-| label | Ability name displayed to users. The value can be a name string or a resource index to names in multiple languages. In the **skills** attribute of the ability, if the **actions** value contains **action.system.home** and the **entities** value contains **entity.system.home**, the label of the ability is also used as the label of the application. If multiple abilities address this condition, the label of the first candidate ability is used as the application label.<br>Note: The **icon** and **label** values of an application are visible to users. Ensure that at least one of them is different from any existing icons or labels. The value can be a reference to a string defined in a resource file or a string enclosed in brackets ({}). The value can contain a maximum of 255 characters.| String| Yes (initial value: left empty)|
+| label | Ability name displayed to users. The value can be a name string or a resource index to names in multiple languages, for example, **$string:ability_label**. In the **skills** attribute of the ability, if the **actions** value contains **action.system.home** and the **entities** value contains **entity.system.home**, the label of the ability is also used as the label of the application. If multiple abilities address this condition, the label of the first candidate ability is used as the application label.<br>Note: The **icon** and **label** values of an application are visible to users. Ensure that at least one of them is different from any existing icons or labels. The value can be a reference to a string defined in a resource file or a string enclosed in brackets ({}). The value can contain a maximum of 255 characters.| String| Yes (initial value: left empty)|
 | uri | Uniform Resource Identifier (URI) of the ability. The value can contain a maximum of 255 bytes.| String| Yes (No for abilities using the Data template)|
 | launchType | Launch type of the ability. The value can be **standard** or **singleton**.<br>**standard**: Multiple **Ability** instances can be created during startup. Most abilities can use this type.<br>**singleton**: Only a single **Ability** instance can be created across all task stacks during startup. For example, a globally unique incoming call screen uses the singleton launch type. This attribute applies only to the default, tablet, smart TV, head unit, and wearable device types.| String| Yes (initial value: **"singleton"**)|
 | visible | Whether the ability can be called by other applications.<br>**true**: The ability can be called by other applications.<br>**false**: The ability cannot be called by other applications.| Boolean| Yes (initial value: **false**)|
@@ -380,7 +380,7 @@ Example of the **abilities** attribute structure:
 | -------- | -------- | -------- | -------- |
 | actions | Actions of the **want** that can be accepted by the ability. Generally, the value is an **action** value predefined in the system.| String array| Yes (initial value: left empty)|
 | entities | Entities of the **want** that can be accepted by the ability, such as video and home applications.| String array| Yes (initial value: left empty)|
-| uris | Data specifications to be added to the want filter. The specification can be of data type only (**mimeType** attribute), URI only, or both.<br>The URI is specified by separate attributes of each part: &lt;scheme&gt;://&lt;host&gt;:&lt;port&gt;[&lt;path&gt;\|&lt;pathStartWith&gt;\|&lt;pathRegex&gt;].  <br>**scheme** is mandatory when the specification is of the URI type and is optional when the specification is of data type only.| Object array| Yes (initial value: left empty)|
+| uris | Data specifications to be added to the want filter. The specification is a data type (using the **mimeType** attribute), a URI, or both a data type and a URI.<br>The URI is specified by separate attributes of each part: &lt;scheme&gt;://&lt;host&gt;:&lt;port&gt;[&lt;path&gt;\|&lt;pathStartWith&gt;\|&lt;pathRegex&gt;].  <br>**scheme** is mandatory when the specification is of the URI type and is optional when the specification is a data type. | Object array| Yes (initial value: left empty)|
 
 ## Internal Structure of the uris Attribute
 
@@ -614,9 +614,9 @@ Example of the **forms** attribute structure:
 ]
 ```
 
-## Internal Structure of the distroFilter Attribute
+## Internal Structure of the distributionFilter Attribute
 
-**Table 21** Internal structure of the distroFilter attribute
+**Table 21** Internal structure of the distributionFilter attribute
 
 | Name| Description| Data Type| Initial Value Allowed|
 | -------- | -------- | -------- | -------- |
diff --git a/en/application-dev/quick-start/multi-hap-objective.md b/en/application-dev/quick-start/multi-hap-objective.md
index ad43c84fd7799be1e3277400c6c5dfb1926d5b7c..cd84de76fefb92a5094ae69051ea906d821593c7 100644
--- a/en/application-dev/quick-start/multi-hap-objective.md
+++ b/en/application-dev/quick-start/multi-hap-objective.md
@@ -1,10 +1,8 @@
 # Multi-HAP Design Objectives
 
 
-- Modular management: A well-designed application is generally managed in a modular manner, where modules are loosely coupled. In light of this, the multi-HAP mechanism is designed, allowing you to divide services into multiple modules and store each module in an independent HAP file. For example, If you are developing a payment application and its home screen consists of multiple modules, such as the scan, pay, messaging, and finance modules, you can implement the logic of the home screen for managing other modules in the entry-type HAP file, and implement specific modules in feature-type HAP files. The feature-type HAP files are independent. You can develop and test each of them separately, and then integrate them with the entry-type HAP file.
+- Modular management: A well-designed application is generally managed in a modular manner, where modules are loosely coupled. In light of this, the multi-HAP mechanism is designed, allowing you to divide services into multiple modules and store each module in an independent HAP file. For example, if you are developing a payment application whose home screen consists of multiple modules, such as the scan, pay, messaging, and finance modules, you can implement the HAP files as follows: (1) In the entry-type HAP file, implement the home screen logic for managing modules; (2) in feature-type HAP files, implement specific modules. The feature-type HAP files are independent of each other. You can develop and test each of them separately, and then integrate them with the entry-type HAP file.
 
-- Flexible deployment: You can combine multiple HAP files and deploy them on different devices. Assume that an application contains one entry-type HAP file (**Entry.hap**) and two feature-type HAP files (**Feature1.hap** and **Feature2.hap**). The **Entry.hap** file can be deployed on device A and device B, the **Feature1.hap** file can be deployed only on device A, and the **Feature2.hap** can be deployed only on device B. In this way, you can easily combine the **Entry.hap** and **Feature1.hap** files and deploy them on device A, and combine the **Entry.hap** and **Feature2.hap** files and deploy them on device B.
+- Flexible deployment: You can flexibly combine HAP files for device-specific deployment. Assume that an application contains one entry-type HAP file (**entry.hap**) and two feature-type HAP files (**Feature1.hap** and **Feature2.hap**). The **Entry.hap** file can be deployed on device A and device B, the **Feature1.hap** file can be deployed only on device A, and the **Feature2.hap** can be deployed only on device B. This means that you can combine the **Entry.hap** and **Feature1.hap** files and deploy them on device A, and combine the **Entry.hap** and **Feature2.hap** files and deploy them on device B.
 
-- On-demand loading: You can load modules only when they are needed, reducing the package size. Specifically, you can configure some HAP files of an application to be loaded on demand. For example, if some features are not used during application startup, you can configure them to be loaded only when they are needed, rather than being loaded at startup. This can reduce the size of the application package to some extent.
-
-- Easier resource sharing: The resources (including public resource files and public pages) and shared objects (.so library files) required by multiple HAP files can be stored in an independent HAP file. In this way, other HAP files can obtain the resources and files by accessing the HAP, which reduces the size of the application package to some extent.
+- On-demand loading: You can load modules only when they are needed, reducing the package size. Specifically, you can configure some HAP files of your application to be loaded on demand. For example, if some features are not used during application startup, you can configure them to be loaded only when they are needed, rather than being loaded at startup. This can reduce the size of the application package to some extent.
diff --git a/en/application-dev/quick-start/quickfix-debug.md b/en/application-dev/quick-start/quickfix-debug.md
index b7cdf872c72198e796be1f1b65e635cb52ce04e6..8756bb5afe6037cf499962c95aabb797bd64cc94 100644
--- a/en/application-dev/quick-start/quickfix-debug.md
+++ b/en/application-dev/quick-start/quickfix-debug.md
@@ -46,7 +46,7 @@ The command contains the following options:
 
 With the preceding **patch.json**, .abc, and .so files, run the following command to generate an .hqf file using the **app_packing_tool.jar** tool in the **toolchains** folder in the local OpenHarmony SDK path:
 ```shell
-$ java -jar app_packing_tool.jar --mode hqf --json-path patch.json --lib-path libs --ets-patch patchs --out-path entry-default-unsigned.hqf --force true
+$ java -jar app_packing_tool.jar --mode hqf --json-path patch.json --lib-path libs --ets-path patchs --out-path entry-default-unsigned.hqf --force true
 ```
 
 The command contains the following options.
diff --git a/en/application-dev/quick-start/quickfix-principles.md b/en/application-dev/quick-start/quickfix-principles.md
index 4c0a1f684cfc1ff71c5ad9a2594ae8823e178e82..53cb1c3fa2848cb4576a12838d45313d9005c6ed 100644
--- a/en/application-dev/quick-start/quickfix-principles.md
+++ b/en/application-dev/quick-start/quickfix-principles.md
@@ -18,7 +18,7 @@ Quick fix is a technical means provided by the OpenHarmony system for developers
 <br>The preceding figure shows the structure of the quick fix package released by an OpenHarmony application.
 * As shown in the figure, the quick fix package comes in two formats:
     * .appqf (Application Quick Fix)
-    <br> There is a one-to-one mapping between the .appqf file and App Pack of an application. For details, see [Application Package Structure in Stage Model](application-package-structure-stage).
+    <br> There is a one-to-one mapping between the .appqf file and App Pack of an application. For details, see [Application Package Structure in Stage Model](application-package-structure-stage.md).
         * The .appqf file is used to release OpenHarmony applications to the application market and cannot be directly installed on devices.
         * An .appqf file consists of one or more .hqf (Harmony Ability Package Quick Fix) files, which are extracted from the .appqf file by the application market and then distributed to specific devices.
         * The .appqf file must contain the developer's signature information before being released to the application market. For details about how to sign the file, see [hapsigner Overview](../security/hapsigntool-overview.md).
diff --git a/en/application-dev/quick-start/shared-guide.md b/en/application-dev/quick-start/shared-guide.md
index 650d401fcd0319605c020a53bb71566eb3cfd36a..2a7ed0b4b5fafa4e1afcebca5c6799239b6f814c 100644
--- a/en/application-dev/quick-start/shared-guide.md
+++ b/en/application-dev/quick-start/shared-guide.md
@@ -8,13 +8,11 @@ Both the HAR and HSP are used to share code and resources and can contain code,
 
 ![in-app-hsp-har](figures/in-app-hsp-har.png)
 
-The HSP is designed to solve the following issues with the HAR:
-- When multiple HAPs reference the same HAR, the size of the App Pack swells.
-- When multiple HAPs reference the same HAR, some state variables in the HAR cannot be shared.
+The HSP aims to resolve the App Pack bloat resulting from multiple HAP files referencing the same HAR.
 
 Restrictions on the HSP:
 - The HSP and its invoking modules must be in the stage model.
-- The HSP and its invoking modules must use the **esmodule **compilation mode.
+- The HSP and its invoking modules must use the **esmodule** compilation mode.
 - The HSP does not support the declaration of **abilities** and **extensionAbilities** in its configuration file.
 
 The HSP can be classified as [in-application HSP](in-app-hsp.md) or inter-application HSP, which will be supported in later versions.
diff --git a/en/application-dev/quick-start/start-overview.md b/en/application-dev/quick-start/start-overview.md
index fd04d4b1e0e2551d2b2885f0314b39204692fc40..deb8f8029bc24a78a362f0babdaf5e85c2e000f3 100644
--- a/en/application-dev/quick-start/start-overview.md
+++ b/en/application-dev/quick-start/start-overview.md
@@ -41,6 +41,6 @@ To help you better understand the preceding basic concepts and application devel
 
 1. Download the latest version of [DevEco Studio](https://developer.harmonyos.com/cn/develop/deveco-studio).
 
-2. Install DevEco Studio and configure the development environment. For details, see [Setting Up the Development Environment](https://developer.harmonyos.com/en/docs/documentation/doc-guides/ohos-setting-up-environment-0000001263160443).
+2. Install DevEco Studio and configure the development environment. For details, see [Setting Up the Development Environment](https://developer.harmonyos.com/en/docs/documentation/doc-guides-V3/environment_config-0000001052902427-V3).
 
 When you are done, follow the instructions in [Getting Started with ArkTS in Stage Model](start-with-ets-stage.md), [Getting Started with ArkTS in FA Model](start-with-ets-fa.md), and [Getting Started with JavaScript in FA Model](start-with-js-fa.md).
diff --git a/en/application-dev/quick-start/start-with-ets-fa.md b/en/application-dev/quick-start/start-with-ets-fa.md
index c85c215057926bd8078496e61ee356c143d324aa..019490d354b8d7c6b6ff7771065aae1b7534b76c 100644
--- a/en/application-dev/quick-start/start-with-ets-fa.md
+++ b/en/application-dev/quick-start/start-with-ets-fa.md
@@ -5,18 +5,18 @@
 >
 >  To use ArkTS, your DevEco Studio must be V3.0.0.601 Beta1 or later.
 >
->  For best possible results, use [DevEco Studio V3.1.0.100](https://developer.harmonyos.com/cn/develop/deveco-studio) for your development.
+>  For best possible results, use [DevEco Studio 3.1 Beta2](https://developer.harmonyos.com/cn/develop/deveco-studio) for your development.
 
 
 ## Creating an ArkTS Project
 
-1. If you are opening DevEco Studio for the first time, click **Create Project**. If a project is already open, choose **File** > **New** > **Create Project** from the menu bar. On the **OpenHarmony** tab of the **Choose Your Ability Template** page, select **Empty Ability** and click **Next**.
+1. If you are opening DevEco Studio for the first time, click **Create Project**. If a project is already open, choose **File** > **New** > **Create Project** from the menu bar. On the **Choose Your Ability Template** page, select **Application** (or **Atomic Service**, depending on your project), select **Empty Ability** as the template, and click Next.
 
-   ![01](figures/01.png)
+   ![createProject](figures/createProject.png)
 
 2. In the project configuration page, set **Compile SDK** to **8** or **9** (in the latter case, you also need to set **Model** to **FA**) and **Language** to **ArkTS** and retain the default values for other parameters.
 
-   ![02](figures/02.png)
+   ![chooseFAModel_ets](figures/chooseFAModel_ets.png)
 
    > **NOTE**
    > 
@@ -27,6 +27,7 @@
    > To use the low-code development mode, turn on **Enable Super Visual** on the page shown above.
 
 3. Click **Finish**. DevEco Studio will automatically generate the sample code and resources that match your project type. Wait until the project is created.
+4. After the project is created, in the **entry** > **build-profile.json5** file, change **runtimeOS** under **targets** to **OpenHarmony**, and click **Sync Now** in the upper right corner to start development.
 
 
 ## ArkTS Project Directory Structure (FA Model)
@@ -41,11 +42,9 @@
   - **src > main > ets > MainAbility > app.ets**: ability lifecycle file.
   - **src > main > resources**: a collection of resource files used by your application/service, such as graphics, multimedia, character strings, and layout files. For details about resource files, see [Resource Categories and Access](resource-categories-and-access.md#resource-categories).
   - **src > main > config.json**: module configuration file. This file describes the global configuration information of the application/service, the device-specific configuration information, and the configuration information of the HAP file. For details, see [Application Configuration File Overview (FA Model)](application-configuration-file-overview-fa.md).
-  - **build-profile.json5**: current module information and build configuration options, including **buildOption** and **targets**.
+  - **build-profile.json5**: current module information and build configuration options, including **buildOption** and **targets**. Under **targets**, you can set **runtimeOS** to **HarmonyOS** (default) or **OpenHarmony**, depending on the OS of your application.
   - **hvigorfile.ts**: module-level build script. You can customize related tasks and code implementation.
-
 - **build-profile.json5**: application-level configuration information, including the signature and product configuration.
-
 - **hvigorfile.ts**: application-level build script.
 
 
@@ -291,7 +290,7 @@ You can implement page redirection through the [page router](../reference/apis/j
 
 2. Choose **File** > **Project Structure...** > **Project** > **SigningConfigs**, and select **Automatically generate signature**. Wait until the automatic signing is complete, and click **OK**. See the following figure.
 
-   ![06](figures/06.png)
+   ![signConfig](figures/signConfig.png)
 
 3. On the toolbar in the upper right corner of the editing window, click ![en-us_image_0000001364054485](figures/en-us_image_0000001364054485.png). The display effect is shown in the figure below.
 
diff --git a/en/application-dev/quick-start/start-with-ets-stage.md b/en/application-dev/quick-start/start-with-ets-stage.md
index f8408868d046d87cb87b6ae9fddc268612ea768b..d18a01875cf2e52abd45b493f8223c596912276d 100644
--- a/en/application-dev/quick-start/start-with-ets-stage.md
+++ b/en/application-dev/quick-start/start-with-ets-stage.md
@@ -5,18 +5,18 @@
 > 
 > To use ArkTS, your DevEco Studio must be V3.0.0.900 Beta3 or later.
 > 
-> For best possible results, use [DevEco Studio V3.1.0.100](https://developer.harmonyos.com/cn/develop/deveco-studio) for your development.
+> For best possible results, use [DevEco Studio 3.1 Beta2](https://developer.harmonyos.com/cn/develop/deveco-studio) for your development.
 
 
 ## Creating an ArkTS Project
 
-1. If you are opening DevEco Studio for the first time, click **Create Project**. If a project is already open, choose **File** > **New** > **Create Project** from the menu bar. On the **OpenHarmony** tab of the **Choose Your Ability Template** page, select **Empty Ability** and click **Next**.
+1. If you are opening DevEco Studio for the first time, click **Create Project**. If a project is already open, choose **File** > **New** > **Create Project** from the menu bar. On the **Choose Your Ability Template** page, select **Application** (or **Atomic Service**, depending on your project), select **Empty Ability** as the template, and click Next.
 
-   ![01](figures/01.png)
+   ![createProject](figures/createProject.png)
 
 2. On the project configuration page, set **Compile SDK** to **9**, **Model** to **Stage**, and retain the default values for other parameters.
 
-   ![07](figures/07.png)
+   ![chooseStageModel](figures/chooseStageModel.png)
 
    > **NOTE**
    >
@@ -28,22 +28,24 @@
    
 3. Click **Finish**. DevEco Studio will automatically generate the sample code and resources that match your project type. Wait until the project is created.
 
+4. After the project is created, in the **entry** > **build-profile.json5** file, change **runtimeOS** under **targets** to **OpenHarmony**, and click **Sync Now** in the upper right corner to start development.
+
 
 ## ArkTS Project Directory Structure (Stage Model)
 
 ![en-us_image_0000001364054489](figures/en-us_image_0000001364054489.png)
 
+- **AppScope** > **app.json5**: global configuration of your application.
 - **entry**: OpenHarmony project module, which can be built into an OpenHarmony Ability Package ([HAP](../../glossary.md#hap)).
+- **oh_modules**: third-party library dependency information. For details about how to adapt a historical npm project to ohpm, see [Manually Migrating Historical Projects](https://developer.harmonyos.com/cn/docs/documentation/doc-guides-V3/project_overview-0000001053822398-V3#section108143331212).
   - **src > main > ets**: a collection of ArkTS source code.
   - **src > main > ets > entryability**: entry to your application/service.
   - **src > main > ets > pages**: pages included in your application/service.
   - **src > main > resources**: a collection of resource files used by your application/service, such as graphics, multimedia, character strings, and layout files. For details about resource files, see [Resource Categories and Access](resource-categories-and-access.md#resource-categories).
   - **src > main > module.json5**: module configuration file. This file describes the global configuration information of the application/service, the device-specific configuration information, and the configuration information of the HAP file. For details, see [module.json5 Configuration File](module-configuration-file.md).
-  - **build-profile.json5**: current module information and build configuration options, including **buildOption** and **targets**.
-  - **hvigorfile.ts**: module-level build script. You can customize related tasks and code implementation.
-
+  - **build-profile.json5**: current module information and build configuration options, including **buildOption** and **targets**. Under **targets**, you can set **runtimeOS** to **HarmonyOS** (default) or **OpenHarmony**, depending on the OS of your application.
+- **hvigorfile.ts**: module-level build script. You can customize related tasks and code implementation.
 - **build-profile.json5**: application-level configuration information, including the signature and product configuration.
-
 - **hvigorfile.ts**: application-level build script.
 
 
@@ -123,7 +125,7 @@
 
    - Create the second page file: In the **Project** window, choose **entry** > **src** > **main** > **ets**. Right-click the **pages** folder, choose **New** > **ArkTS File**, name the page **Second**, and click **Finish**. Below is the structure of the **Second** folder.
 
-      ![09](figures/09.png)
+      ![secondPage](figures/secondPage.png)
 
       > **NOTE**
       >
@@ -281,7 +283,7 @@ You can implement page redirection through the [page router](../reference/apis/j
 
 2. Choose **File** > **Project Structure...** > **Project** > **SigningConfigs**, and select **Automatically generate signature**. Wait until the automatic signing is complete, and click **OK**. See the following figure.
 
-   ![06](figures/06.png)
+   ![signConfig](figures/signConfig.png)
 
 3. On the toolbar in the upper right corner of the editing window, click ![en-us_image_0000001364054485](figures/en-us_image_0000001364054485.png). The display effect is shown in the figure below.
 
diff --git a/en/application-dev/quick-start/start-with-js-fa.md b/en/application-dev/quick-start/start-with-js-fa.md
index d854f1a024362a31082c3c9ade34374b654ea84d..abb27d9fb942a406e22d98285626984bdc63d197 100644
--- a/en/application-dev/quick-start/start-with-js-fa.md
+++ b/en/application-dev/quick-start/start-with-js-fa.md
@@ -3,18 +3,18 @@
 
 > **NOTE**
 >
-> For best possible results, use [DevEco Studio V3.0.0.993](https://developer.harmonyos.com/cn/develop/deveco-studio#download) for your development.
+> For best possible results, use [DevEco Studio 3.1 Beta2](https://developer.harmonyos.com/cn/develop/deveco-studio#download) for your development.
 
 
 ## Creating a JavaScript Project
 
-1. If you are opening DevEco Studio for the first time, click **Create Project**. If a project is already open, choose **File** > **New** > **Create Project** from the menu bar. On the **OpenHarmony** tab of the **Choose Your Ability Template** page, select **Empty Ability** and click **Next**.
+1. If you are opening DevEco Studio for the first time, click **Create Project**. If a project is already open, choose **File** > **New** > **Create Project** from the menu bar. On the **Choose Your Ability Template** page, select **Application** (or **Atomic Service**, depending on your project), select **Empty Ability** as the template, and click Next.
 
-   ![01](figures/01.png)
+   ![createProject](figures/createProject.png)
 
 2. In the project configuration page, set **Compile SDK** to **8** or **9** (in the latter case, you also need to set **Model** to **FA**) and **Language** to **JS** and retain the default values for other parameters.
 
-   ![04](figures/04.png)
+   ![chooseFAModel_js](figures/chooseFAModel_js.png)
 
    > **NOTE**
    > 
@@ -26,6 +26,8 @@
 
 3. Click **Finish**. DevEco Studio will automatically generate the sample code and resources that match your project type. Wait until the project is created.
 
+4. After the project is created, in the **entry** > **build-profile.json5** file, change **runtimeOS** under **targets** to **OpenHarmony**, and click **Sync Now** in the upper right corner to start development.
+
 
 ## JavaScript Project Directory Structure
 
@@ -40,7 +42,7 @@
 
   - **src > main > resources**: a collection of resource files used by your application/service, such as graphics, multimedia, character strings, and layout files. For details about resource files, see [Resource Limitations and Access](../ui/js-framework-resource-restriction.md).
   - **src > main > config.json**: module configuration file. This file describes the global configuration information of the application/service, the device-specific configuration information, and the configuration information of the HAP file. For details, see [Application Configuration File Overview (FA Model)](application-configuration-file-overview-fa.md).
-  - **build-profile.json5**: current module information and build configuration options, including **buildOption** and **targets**.
+  - **build-profile.json5**: current module information and build configuration options, including **buildOption** and **targets**. Under **targets**, you can set **runtimeOS** to **HarmonyOS** (default) or **OpenHarmony**, depending on the OS of your application.
   - **hvigorfile.ts**: module-level build script. You can customize related tasks and code implementation.
 
 - **build-profile.json5**: application-level configuration information, including the signature and product configuration.
@@ -226,7 +228,7 @@ You can implement page redirection through the [page router](../reference/apis/j
 
 2. Choose **File** > **Project Structure...** > **Project** > **Signing Configs**, and select **Automatically generate signature**. Wait until the automatic signing is complete, and click **OK**. See the following figure.
 
-   ![06](figures/06.png)
+   ![signConfig](figures/signConfig.png)
 
 3. On the toolbar in the upper right corner of the editing window, click ![en-us_image_0000001364054485](figures/en-us_image_0000001364054485.png). The display effect is shown in the figure below.
 
diff --git a/en/application-dev/reference/apis/js-apis-ability-ability.md b/en/application-dev/reference/apis/js-apis-ability-ability.md
index fe5b7cfde18961802383469c3d2558f8c8381f67..80610df7f925ac5a5d29744b48179488e8efc7f6 100644
--- a/en/application-dev/reference/apis/js-apis-ability-ability.md
+++ b/en/application-dev/reference/apis/js-apis-ability-ability.md
@@ -15,15 +15,15 @@ import ability from '@ohos.ability.ability';
 
 **System capability**: SystemCapability.Ability.AbilityBase
 
-| Name        | Type                | Mandatory| Description                                                        |
-| ----------- | -------------------- | ---- | ------------------------------------------------------------ |
-| DataAbilityHelper    | [DataAbilityHelper](js-apis-inner-ability-dataAbilityHelper.md)               | No  | Level-2 module **DataAbilityHelper**.                               |
-| PacMap   | [PacMap](js-apis-inner-ability-dataAbilityHelper.md#PacMap)               | No  | Level-2 module **PacMap**.|
-| DataAbilityOperation   | [DataAbilityOperation](js-apis-inner-ability-dataAbilityOperation.md)               | No  | Level-2 module **DataAbilityOperation**.|
-| DataAbilityResult   | [DataAbilityResult](js-apis-inner-ability-dataAbilityResult.md)               | No  | Level-2 module **DataAbilityResult**.|
-| AbilityResult   | [AbilityResult](js-apis-inner-ability-abilityResult.md)               | No  | Level-2 module **AbilityResult**.|
-| ConnectOptions   | [ConnectOptions](js-apis-inner-ability-connectOptions.md)               | No  | Level-2 module **ConnectOptions**.|
-| StartAbilityParameter   | [StartAbilityParameter](js-apis-inner-ability-startAbilityParameter.md)               | No  | Level-2 module **StartAbilityParameter**.|
+| Name        | Type                | Description                                                        |
+| ----------- | -------------------- | ------------------------------------------------------------ |
+| DataAbilityHelper    | [DataAbilityHelper](js-apis-inner-ability-dataAbilityHelper.md)               | Level-2 module **DataAbilityHelper**.                               |
+| PacMap   | [PacMap](js-apis-inner-application-pacMap.md)               | Level-2 module **PacMap**.|
+| DataAbilityOperation   | [DataAbilityOperation](js-apis-inner-ability-dataAbilityOperation.md)               | Level-2 module **DataAbilityOperation**.|
+| DataAbilityResult   | [DataAbilityResult](js-apis-inner-ability-dataAbilityResult.md)               | Level-2 module **DataAbilityResult**.|
+| AbilityResult   | [AbilityResult](js-apis-inner-ability-abilityResult.md)               | Level-2 module **AbilityResult**.|
+| ConnectOptions   | [ConnectOptions](js-apis-inner-ability-connectOptions.md)               | Level-2 module **ConnectOptions**.|
+| StartAbilityParameter   | [StartAbilityParameter](js-apis-inner-ability-startAbilityParameter.md)               | Level-2 module **StartAbilityParameter**.|
 
 **Example**
 ```ts
diff --git a/en/application-dev/reference/apis/js-apis-app-ability-missionManager.md b/en/application-dev/reference/apis/js-apis-app-ability-missionManager.md
index 9a657faa2f5ba6d1655a0439df016d086be098c3..52affe8697553612a047f74114e588619fd0f130 100644
--- a/en/application-dev/reference/apis/js-apis-app-ability-missionManager.md
+++ b/en/application-dev/reference/apis/js-apis-app-ability-missionManager.md
@@ -3,7 +3,7 @@
 The **missionManager** module provides APIs to lock, unlock, and clear missions, and switch a mission to the foreground.
 
 > **NOTE**
->
+> 
 > The initial APIs of this module are supported since API version 9. Newly added APIs will be marked with a superscript to indicate their earliest API version.
 
 ## Modules to Import
@@ -32,7 +32,7 @@ Registers a listener to observe the mission status.
 
   | Name| Type| Mandatory| Description|
   | -------- | -------- | -------- | -------- |
-  | listener | [MissionListener](js-apis-inner-application-missionListener.md) | Yes| Mission status listener to register.|
+  | listener | [MissionListener](js-apis-inner-application-missionListener.md) | Yes| Listener to register.|
 
 **Return value**
 
@@ -79,7 +79,7 @@ export default class EntryAbility extends UIAbility {
     }
 
     onWindowStageCreate(windowStage) {
-        // Main window is created, set main page for this ability
+        // The main window is created. Set a main page for this ability.
         console.log('[Demo] EntryAbility onWindowStageCreate');
         try {
             listenerId = missionManager.on('mission', listener);
@@ -107,7 +107,7 @@ export default class EntryAbility extends UIAbility {
 
 off(type: 'mission', listenerId: number, callback: AsyncCallback&lt;void&gt;): void;
 
-Deregisters a mission status listener.
+Deregisters a mission status listener. This API uses an asynchronous callback to return the result.
 
 **Required permissions**: ohos.permission.MANAGE_MISSIONS
 
@@ -122,6 +122,14 @@ Deregisters a mission status listener.
   | listenerId | number | Yes| Index of the mission status listener to deregister. It is returned by **registerMissionListener()**.|
   | callback | AsyncCallback&lt;void&gt; | Yes| Callback used to return the result.|
 
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 16300002 | Input error. The specified mission listener does not exist. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```ts
@@ -161,7 +169,7 @@ export default class EntryAbility extends UIAbility {
     }
 
     onWindowStageCreate(windowStage) {
-        // Main window is created, set main page for this ability
+        // The main window is created. Set a main page for this ability.
         console.log('[Demo] EntryAbility onWindowStageCreate');
         try {
             listenerId = missionManager.on('mission', listener);
@@ -205,9 +213,17 @@ Deregisters a mission status listener. This API uses a promise to return the res
 
 **Return value**
 
-  | Type| Description|
+  | Type| Description| 
   | -------- | -------- |
-  | Promise&lt;void&gt; | Promise used to return the result.|
+  | Promise&lt;void&gt; | Promise used to return the result.| 
+  
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 16300002 | Input error. The specified mission listener does not exist. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
 
 **Example**
 
@@ -248,7 +264,7 @@ export default class EntryAbility extends UIAbility {
     }
 
     onWindowStageCreate(windowStage) {
-        // Main window is created, set main page for this ability
+        // The main window is created. Set a main page for this ability.
         console.log('[Demo] EntryAbility onWindowStageCreate');
         try {
             listenerId = missionManager.on('mission', listener);
@@ -631,6 +647,14 @@ Locks a given mission. This API uses an asynchronous callback to return the resu
   | missionId | number | Yes| Mission ID.|
   | callback | AsyncCallback&lt;void&gt; | Yes| Callback used to return the result.|
 
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 16300001 | Mission not found. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
   ```ts
@@ -673,9 +697,17 @@ Locks a given mission. This API uses a promise to return the result.
 
 **Return value**
 
-  | Type| Description|
+  | Type| Description| 
   | -------- | -------- |
-  | Promise&lt;void&gt; | Promise used to return the result.|
+  | Promise&lt;void&gt; | Promise used to return the result.| 
+
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 16300001 | Mission not found. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
 
 **Example**
 
@@ -719,6 +751,14 @@ Unlocks a given mission. This API uses an asynchronous callback to return the re
 | missionId | number | Yes| Mission ID.|
 | callback | AsyncCallback&lt;void&gt; | Yes| Callback used to return the result.|
 
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 16300001 | Mission not found. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
   ```ts
@@ -761,9 +801,17 @@ Unlocks a given mission. This API uses a promise to return the result.
 
 **Return value**
 
-  | Type| Description|
+  | Type| Description| 
   | -------- | -------- |
-  | Promise&lt;void&gt; | Promise used to return the result.|
+  | Promise&lt;void&gt; | Promise used to return the result.| 
+
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 16300001 | Mission not found. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
 
 **Example**
 
@@ -852,9 +900,9 @@ Clears a given mission, regardless of whether it is locked. This API uses a prom
 
 **Return value**
 
-  | Type| Description|
+  | Type| Description| 
   | -------- | -------- |
-  | Promise&lt;void&gt; | Promise used to return the result.|
+  | Promise&lt;void&gt; | Promise used to return the result.| 
 
 **Example**
 
@@ -916,9 +964,9 @@ Clears all unlocked missions. This API uses a promise to return the result.
 
 **Return value**
 
-  | Type| Description|
+  | Type| Description| 
   | -------- | -------- |
-  | Promise&lt;void&gt; | Promise used to return the result.|
+  | Promise&lt;void&gt; | Promise used to return the result.| 
 
 **Example**
 
@@ -949,6 +997,14 @@ Switches a given mission to the foreground. This API uses an asynchronous callba
   | missionId | number | Yes| Mission ID.|
   | callback | AsyncCallback&lt;void&gt; | Yes| Callback used to return the result.|
 
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 16000009 | An ability cannot be started or stopped in Wukong mode. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
   ```ts
@@ -991,6 +1047,14 @@ Switches a given mission to the foreground, with the startup parameters for the
   | options | [StartOptions](js-apis-app-ability-startOptions.md) | Yes| Startup parameters, which are used to specify the window mode and device ID for switching the mission to the foreground.|
   | callback | AsyncCallback&lt;void&gt; | Yes| Callback used to return the result.|
 
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 16000009 | An ability cannot be started or stopped in Wukong mode. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
   ```ts
@@ -1034,9 +1098,17 @@ Switches a given mission to the foreground, with the startup parameters for the
 
 **Return value**
 
-  | Type| Description|
+  | Type| Description| 
   | -------- | -------- |
-  | Promise&lt;void&gt; | Promise used to return the result.|
+  | Promise&lt;void&gt; | Promise used to return the result.| 
+
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 16000009 | An ability cannot be started or stopped in Wukong mode. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
 
 **Example**
 
diff --git a/en/application-dev/reference/apis/js-apis-app-ability-quickFixManager.md b/en/application-dev/reference/apis/js-apis-app-ability-quickFixManager.md
index ac26642228b5cdc386b65d8c9e2e1c429fdb9819..9566c02484933d236a62f248ed4faf97696d2f71 100644
--- a/en/application-dev/reference/apis/js-apis-app-ability-quickFixManager.md
+++ b/en/application-dev/reference/apis/js-apis-app-ability-quickFixManager.md
@@ -62,6 +62,25 @@ Applies a quick fix patch. This API uses an asynchronous callback to return the
 | hapModuleQuickFixFiles | Array\<string> | Yes| Quick fix patch files, each of which must contain a valid file path.|
 | callback | AsyncCallback\<void> | Yes| Callback used to return the result.|
 
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 18500002 | Copy file failed, maybe not exist or inaccessible. |
+| 18500008 | Internal error. |
+
+If an error occurs during patch installation, the error code and message are returned through the common event [COMMON_EVENT_QUICK_FIX_APPLY_RESULT](commonEvent-definitions.md#common_event_quick_fix_apply_result9). The table below lists the possible error codes and messages.
+
+| ID| Error Message|
+| ------- | -------- |
+| 18500003 | Deploy hqf failed. |
+| 18500004 | Switch hqf failed. |
+| 18500005 | Delete hqf failed. |
+| 18500006 | Load patch failed. |
+| 18500007 | Unload patch failed. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 > **NOTE**
 >
 > The file path passed in the API must be an application sandbox path. For details about how to obtain the sandbox path, see [Obtaining the Sandbox Path](js-apis-bundle-BundleInstaller.md#obtaining-the-sandbox-path). The path mapped to the device is **/proc/<*applicationProcessId*>/root/*sandboxPath***.
@@ -109,6 +128,25 @@ Applies a quick fix patch. This API uses a promise to return the result.
 | -------- | -------- |
 | Promise\<void> | Promise used to return the result.|
 
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 18500002 | Copy file failed, maybe not exist or inaccessible. |
+| 18500008 | Internal error. |
+
+If an error occurs during patch installation, the error code and message are returned through the common event [COMMON_EVENT_QUICK_FIX_APPLY_RESULT](commonEvent-definitions.md#common_event_quick_fix_apply_result9). The table below lists the possible error codes and messages.
+
+| ID| Error Message|
+| ------- | -------- |
+| 18500003 | Deploy hqf failed. |
+| 18500004 | Switch hqf failed. |
+| 18500005 | Delete hqf failed. |
+| 18500006 | Load patch failed. |
+| 18500007 | Unload patch failed. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```ts
@@ -145,6 +183,15 @@ Obtains the quick fix information of the application. This API uses an asynchron
 | bundleName | string | Yes|Bundle name. |
 | callback | AsyncCallback\<[ApplicationQuickFixInfo](#applicationquickfixinfo)> | Yes| Callback used to return the quick fix information.|
 
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 18500001 | The bundle is not exist. |
+| 18500008 | Internal error. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```ts
@@ -188,6 +235,15 @@ Obtains the quick fix information of the application. This API uses a promise to
 | -------- | -------- |
 | Promise\<[ApplicationQuickFixInfo](#applicationquickfixinfo)> | Promise used to return the quick fix information.|
 
+**Error codes**
+
+| ID| Error Message|
+| ------- | -------- |
+| 18500001 | The bundle is not exist. |
+| 18500008 | Internal error. |
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
     
   ```ts 
diff --git a/en/application-dev/reference/apis/js-apis-app-ability-wantAgent.md b/en/application-dev/reference/apis/js-apis-app-ability-wantAgent.md
index f65d9971dc55689ee2df76bdc32cf80ffb1e010d..f775c26b85ffdff0459be155839dee93b424d897 100644
--- a/en/application-dev/reference/apis/js-apis-app-ability-wantAgent.md
+++ b/en/application-dev/reference/apis/js-apis-app-ability-wantAgent.md
@@ -1,6 +1,6 @@
 # @ohos.app.ability.wantAgent (WantAgent)
 
-The **WantAgent** module provides APIs for creating and comparing **WantAgent** objects, and obtaining the user ID and bundle name of a **WantAgent** object. You are advised to use this module, since it will replace the [@ohos.wantAgent](js-apis-wantAgent.md) module in the near future.
+The **WantAgent** module provides APIs for triggering, canceling, and comparing **WantAgent** objects. You can use the APIs to create a **WantAgent** object, and obtain the user ID, bundle name, and want information of the object.
 
 > **NOTE**
 > 
@@ -24,9 +24,18 @@ Obtains a **WantAgent** object. This API uses an asynchronous callback to return
 
 | Name    | Type                      | Mandatory| Description                   |
 | -------- | -------------------------- | ---- | ----------------------- |
-| info     | [WantAgentInfo](js-apis-inner-wantAgent-wantAgentInfo.md)              | Yes  | Information about the **WantAgent** object to obtain.          |
+| info     | WantAgentInfo              | Yes  | Information about the **WantAgent** object to obtain.          |
 | callback | AsyncCallback\<WantAgent\> | Yes  | Callback used to return the **WantAgent** object.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
@@ -93,6 +102,15 @@ Obtains a **WantAgent** object. This API uses a promise to return the result. If
 | ----------------------------------------------------------- | ------------------------------------------------------------ |
 | Promise\<WantAgent\> | Promise used to return the **WantAgent** object.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
@@ -153,16 +171,25 @@ Obtains the bundle name of a **WantAgent** object. This API uses an asynchronous
 | agent    | WantAgent               | Yes  | Target **WantAgent** object.                    |
 | callback | AsyncCallback\<string\> | Yes  | Callback used to return the bundle name.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
 import WantAgent from '@ohos.app.ability.wantAgent';
 
 
-// wantAgent object
+// WantAgent object
 let wantAgent;
 
-//getWantAgent callback
+// getWantAgent callback
 function getWantAgentCallback(err, data) {
 	console.info('==========================>getWantAgentCallback=======================>');
     if (err.code == 0) {
@@ -234,16 +261,25 @@ Obtains the bundle name of a **WantAgent** object. This API uses a promise to re
 | ----------------------------------------------------------- | ------------------------------------------------------------ |
 | Promise\<string\> | Promise used to return the bundle name.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
 import WantAgent from '@ohos.app.ability.wantAgent';
 
 
-// wantAgent object
+// WantAgent object
 let wantAgent;
 
-//WantAgentInfo object
+// WantAgentInfo object
 let wantAgentInfo = {
     wants: [
         {
@@ -302,13 +338,22 @@ Obtains the user ID of a **WantAgent** object. This API uses an asynchronous cal
 | agent    | WantAgent               | Yes  | Target **WantAgent** object.                      |
 | callback | AsyncCallback\<number\> | Yes  | Callback used to return the user ID.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
 import WantAgent from '@ohos.app.ability.wantAgent';
 
 
-// wantAgent object
+// WantAgent object
 let wantAgent;
 
 // getWantAgent callback
@@ -383,13 +428,22 @@ Obtains the user ID of a **WantAgent** object. This API uses a promise to return
 | ----------------------------------------------------------- | ------------------------------------------------------------ |
 | Promise\<number\> | Promise used to return the user ID.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
 import WantAgent from '@ohos.app.ability.wantAgent';
 
 
-// wantAgent object
+// WantAgent object
 let wantAgent;
 
 // WantAgentInfo object
@@ -453,13 +507,23 @@ Obtains the want in a **WantAgent** object. This API uses an asynchronous callba
 | agent    | WantAgent             | Yes  | Target **WantAgent** object.                  |
 | callback | AsyncCallback\<[Want](js-apis-app-ability-want.md)\> | Yes  | Callback used to return the want.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000015   | Service timeout.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
 import WantAgent from '@ohos.app.ability.wantAgent';
 
 
-// wantAgent object
+// WantAgent object
 let wantAgent;
 
 // getWantAgent callback
@@ -536,13 +600,23 @@ Obtains the want in a **WantAgent** object. This API uses a promise to return th
 | ----------------------------------------------------------- | ------------------------------------------------------------ |
 | Promise\<Want\> | Promise used to return the want.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000015   | Service timeout.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
 import WantAgent from '@ohos.app.ability.wantAgent';
 
 
-// wantAgent object
+// WantAgent object
 let wantAgent;
 
 // WantAgentInfo object
@@ -604,13 +678,22 @@ Cancels a **WantAgent** object. This API uses an asynchronous callback to return
 | agent    | WantAgent             | Yes  | Target **WantAgent** object.              |
 | callback | AsyncCallback\<void\> | Yes  | Callback used to return the result.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
 import WantAgent from '@ohos.app.ability.wantAgent';
 
 
-// wantAgent object
+// WantAgent object
 let wantAgent;
 
 // getWantAgent callback
@@ -685,13 +768,22 @@ Cancels a **WantAgent** object. This API uses a promise to return the result.
 | --------------- | ------------------------------- |
 | Promise\<void\> | Promise used to return the result.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
 import WantAgent from '@ohos.app.ability.wantAgent';
 
 
-// wantAgent object
+// WantAgent object
 let wantAgent;
 
 // WantAgentInfo object
@@ -751,15 +843,16 @@ Triggers a **WantAgent** object. This API uses an asynchronous callback to retur
 | Name       | Type                         | Mandatory| Description                           |
 | ----------- | ----------------------------- | ---- | ------------------------------- |
 | agent       | WantAgent                     | Yes  | Target **WantAgent** object.                  |
-| triggerInfo | TriggerInfo                  | Yes  | **TriggerInfo** object.                |
+| triggerInfo | TriggerInfo                   | Yes  | **TriggerInfo** object.                |
 | callback    | AsyncCallback\<[CompleteData](#completedata)\> | No  | Callback used to return the result.|
 
+**Example**
 
 ```js
 import WantAgent from '@ohos.app.ability.wantAgent';
 
 
-// wantAgent object
+// WantAgent object
 let wantAgent;
 
 // getWantAgent callback
@@ -823,7 +916,7 @@ try {
 
 equal(agent: WantAgent, otherAgent: WantAgent, callback: AsyncCallback\<boolean\>): void
 
-Checks whether two **WantAgent** objects are equal to determine whether the same operation is from the same application. This API uses an asynchronous callback to return the result.
+Checks whether two **WantAgent** objects are equal. This API uses an asynchronous callback to return the result.
 
 **System capability**: SystemCapability.Ability.AbilityRuntime.Core
 
@@ -841,7 +934,7 @@ Checks whether two **WantAgent** objects are equal to determine whether the same
 import WantAgent from '@ohos.app.ability.wantAgent';
 
 
-// wantAgent object
+// WantAgent object
 let wantAgent1;
 let wantAgent2;
 
@@ -902,7 +995,7 @@ try {
 
 equal(agent: WantAgent, otherAgent: WantAgent): Promise\<boolean\>
 
-Checks whether two **WantAgent** objects are equal to determine whether the same operation is from the same application. This API uses a promise to return the result.
+Checks whether two **WantAgent** objects are equal. This API uses a promise to return the result.
 
 **System capability**: SystemCapability.Ability.AbilityRuntime.Core
 
@@ -925,7 +1018,7 @@ Checks whether two **WantAgent** objects are equal to determine whether the same
 import WantAgent from '@ohos.app.ability.wantAgent';
 
 
-// wantAgent object
+// WantAgent object
 let wantAgent1;
 let wantAgent2;
 
@@ -987,12 +1080,22 @@ Obtains the operation type of a **WantAgent** object. This API uses an asynchron
 | agent      | WantAgent                | Yes  | Target **WantAgent** object.                          |
 | callback   | AsyncCallback\<number> | Yes  | Callback used to return the operation type.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000015   | Service timeout.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
 import WantAgent from '@ohos.app.ability.wantAgent';
 
-// wantAgent object
+// WantAgent object
 let wantAgent;
 
 // WantAgentInfo object
@@ -1057,12 +1160,22 @@ Obtains the operation type of a **WantAgent** object. This API uses a promise to
 | ----------------------------------------------------------- | ------------------------------------------------------------ |
 | Promise\<number> | Promise used to return the operation type.|
 
+**Error codes**
+
+| ID   | Error Message           |
+|-----------|--------------------|
+| 16000007   | Service busyness. There are concurrent tasks, waiting for retry.|
+| 16000015   | Service timeout.|
+| 16000151   | Invalid wantagent object.|
+
+For details about the error codes, see [Ability Error Codes](../errorcodes/errorcode-ability.md).
+
 **Example**
 
 ```js
 import WantAgent from '@ohos.app.ability.wantAgent';
 
-// wantAgent object
+// WantAgent object
 let wantAgent;
 
 // WantAgentInfo object
@@ -1153,4 +1266,3 @@ try {
 | finalCode      | number                          | Yes  | Request code that triggers the **WantAgent** object.|
 | finalData      | string                          | Yes  | Final data collected by the common event. |
 | extraInfo      | {[key: string]: any}            | No  | Extra information.              |
-
diff --git a/en/application-dev/reference/apis/js-apis-app-form-formBindingData.md b/en/application-dev/reference/apis/js-apis-app-form-formBindingData.md
index 39cfb8e3349b07ee745c1756cefb4ea66f189b39..dbef711c25369d3eac61ca1b6516a7c43d8ecbc2 100644
--- a/en/application-dev/reference/apis/js-apis-app-form-formBindingData.md
+++ b/en/application-dev/reference/apis/js-apis-app-form-formBindingData.md
@@ -48,20 +48,17 @@ Creates a **FormBindingData** object.
 **Example**
 
 ```ts
-import featureAbility from '@ohos.ability.featureAbility';
-import fileio from '@ohos.fileio';
-let context=featureAbility.getContext();
-context.getOrCreateLocalDir((err,data)=>{
-  let path=data+'/xxx.jpg';
-  let fd = fileio.openSync(path);
+import formBindingData from '@ohos.app.form.formBindingData';
+import fs from '@ohos.file.fs';
+
+try {
+  let fd = fs.openSync('/path/to/form.png');
   let obj = {
     'temperature': '21°',
-    'formImages': {'image': fd}
+    'formImages': { 'image': fd }
   };
-  try {
-    formBindingData.createFormBindingData(obj);
-  } catch (error) {
-    console.log(`catch err->${JSON.stringify(err)}`);
-  }
-})
+  formBindingData.createFormBindingData(obj);
+} catch (error) {
+  console.error(`catch error, code: ${error.code}, message: ${error.message}`);
+}
 ```
diff --git a/en/application-dev/reference/apis/js-apis-app-form-formHost.md b/en/application-dev/reference/apis/js-apis-app-form-formHost.md
index c8c8ca6389aa86a7f2a065c98e125c5b1faaca29..e2141a3702b87fa28ab827deddb1ffab8e739e96 100644
--- a/en/application-dev/reference/apis/js-apis-app-form-formHost.md
+++ b/en/application-dev/reference/apis/js-apis-app-form-formHost.md
@@ -1,6 +1,6 @@
-# @ohos.app.form.formHost (FormHost)
+# @ohos.app.form.formHost (formHost)
 
-The **FormHost** module provides APIs related to the widget host, which is an application that displays the widget content and controls the position where the widget is displayed. You can use the APIs to delete, release, and update widgets installed by the same user, and obtain widget information and status.
+The **formHost** module provides APIs related to the widget host, which is an application that displays the widget content and controls the position where the widget is displayed. You can use the APIs to delete, release, and update widgets installed by the same user, and obtain widget information and status.
 
 > **NOTE**
 >
@@ -34,8 +34,15 @@ Deletes a widget. After this API is called, the application can no longer use th
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 202 | The application is not a system application. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -82,10 +89,17 @@ Deletes a widget. After this API is called, the application can no longer use th
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
-**Parameters**
+**Example**
 
 ```ts
 try {
@@ -121,8 +135,15 @@ Releases a widget. After this API is called, the application can no longer use t
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -161,8 +182,15 @@ Releases a widget. After this API is called, the application can no longer use t
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -194,7 +222,7 @@ Releases a widget. After this API is called, the application can no longer use t
 | Name        | Type    | Mandatory| Description       |
 | -------------- | ------  | ---- | ----------- |
 | formId         | string  | Yes  | Widget ID.    |
-| isReleaseCache | boolean | No  | Whether to release the cache.|
+| isReleaseCache | boolean | No  | Whether to release the cache. The default value is **false**. |
 
 **Return value**
 
@@ -206,8 +234,15 @@ Releases a widget. After this API is called, the application can no longer use t
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -245,8 +280,15 @@ Requests a widget update. This API uses an asynchronous callback to return the r
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -289,8 +331,15 @@ Requests a widget update. This API uses a promise to return the result.
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -329,8 +378,15 @@ Converts a temporary widget to a normal one. This API uses an asynchronous callb
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501002 | The number of forms exceeds upper bound. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -373,8 +429,15 @@ Converts a temporary widget to a normal one. This API uses a promise to return t
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501002 | The number of forms exceeds upper bound. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -412,8 +475,13 @@ Instructs the widget framework to make a widget visible. After this API is calle
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -456,8 +524,13 @@ Instructs the widget framework to make a widget visible. After this API is calle
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -495,8 +568,13 @@ Instructs the widget framework to make a widget invisible. After this API is cal
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -539,8 +617,13 @@ Instructs the widget framework to make a widget invisible. After this API is cal
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -578,8 +661,14 @@ Instructs the widget framework to make a widget updatable. After this API is cal
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -622,8 +711,14 @@ Instructs the widget framework to make a widget updatable. After this API is cal
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -661,8 +756,15 @@ Instructs the widget framework to make a widget not updatable. After this API is
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -705,8 +807,15 @@ Instructs the widget framework to make a widget not updatable. After this API is
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -737,6 +846,14 @@ Checks whether the system is ready. This API uses an asynchronous callback to re
 | ------ | ------ | ---- | ------- |
 | callback | AsyncCallback&lt;void&gt; | Yes| Callback used to return the result. If the check is successful, **error** is undefined; otherwise, **error** is an error object.|
 
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 202 | The application is not a system application.   |
+| 401 | If the input parameter is not valid parameter. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
+
 **Example**
 
 ```ts
@@ -766,6 +883,13 @@ Checks whether the system is ready. This API uses a promise to return the result
 | -------- | -------- |
 | Promise&lt;void&gt; | Promise that returns no value.|
 
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 202 | The application is not a system application.   |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
+
 **Example**
 
 ```ts
@@ -791,6 +915,18 @@ Obtains the widget information provided by all applications on the device. This
 
 **System capability**: SystemCapability.Ability.Form
 
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
+| 401 | If the input parameter is not valid parameter. |
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
+
 **Parameters**
 
 | Name| Type   | Mandatory| Description   |
@@ -823,6 +959,17 @@ Obtains the widget information provided by all applications on the device. This
 
 **System capability**: SystemCapability.Ability.Form
 
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
+
 **Return value**
 
 | Type                                                        | Description                               |
@@ -858,14 +1005,20 @@ Obtains the widget information provided by a given application on the device. Th
 | Name| Type   | Mandatory| Description   |
 | ------ | ------ | ---- | ------- |
 | bundleName | string | Yes| Bundle name of the application.|
-| callback | AsyncCallback&lt;Array&lt;[formInfo.FormInfo](js-apis-app-form-formInfo.md)&gt;&gt; | Yes| Callback used to return the result. If the widget information is obtained, **error** is undefined and **data** is the information obtained; otherwise, **error** is an error object.|
+| callback | AsyncCallback&lt;Array&lt;[FormInfo](js-apis-app-form-formInfo.md)&gt;&gt; | Yes| Callback used to return the result. If the widget information is obtained, **error** is undefined and **data** is the information obtained; otherwise, **error** is an error object.|
 
 **Error codes**
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -899,14 +1052,20 @@ Obtains the widget information provided by a given application on the device. Th
 | ------ | ------ | ---- | ------- |
 | bundleName | string | Yes| Bundle name of the application.|
 | moduleName | string | Yes|  Module name.|
-| callback | AsyncCallback&lt;Array&lt;[formInfo.FormInfo](js-apis-app-form-formInfo.md)&gt;&gt; | Yes| Callback used to return the result. If the widget information is obtained, **error** is undefined and **data** is the information obtained; otherwise, **error** is an error object.|
+| callback | AsyncCallback&lt;Array&lt;[FormInfo](js-apis-app-form-formInfo.md)&gt;&gt; | Yes| Callback used to return the result. If the widget information is obtained, **error** is undefined and **data** is the information obtained; otherwise, **error** is an error object.|
 
 **Error codes**
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -939,7 +1098,7 @@ Obtains the widget information provided by a given application on the device. Th
 | Name| Type   | Mandatory| Description   |
 | ------ | ------ | ---- | ------- |
 | bundleName | string | Yes| Bundle name of the application.|
-| moduleName | string | No|  Module name.|
+| moduleName | string | No|  Module name. By default, no value is passed.|
 
 **Return value**
 
@@ -951,8 +1110,14 @@ Obtains the widget information provided by a given application on the device. Th
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -985,6 +1150,18 @@ Deletes invalid widgets from the list. This API uses an asynchronous callback to
 | formIds | Array&lt;string&gt; | Yes  | List of valid widget IDs.|
 | callback | AsyncCallback&lt;number&gt; | Yes| Callback used to return the result. If the invalid widgets are deleted, **error** is undefined and **data** is the number of widgets deleted; otherwise, **error** is an error object.|
 
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
+| 401 | If the input parameter is not valid parameter. |
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
+
 **Example**
 
 ```ts
@@ -1024,6 +1201,18 @@ Deletes invalid widgets from the list. This API uses a promise to return the res
 | :------------ | :---------------------------------- |
 | Promise&lt;number&gt; | Promise used to return the number of widgets deleted.|
 
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
+| 401 | If the input parameter is not valid parameter. |
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
+
 **Example**
 
 ```ts
@@ -1054,14 +1243,20 @@ Obtains the widget state. This API uses an asynchronous callback to return the r
 | Name| Type   | Mandatory| Description   |
 | ------ | ------ | ---- | ------- |
 | want | [Want](js-apis-application-want.md) | Yes  | **Want** information carried to query the widget state. The information must contain the bundle name, ability name, module name, widget name, and widget dimensions.|
-| callback | AsyncCallback&lt;[FormInfo](js-apis-app-form-formInfo.md#formstateinfo)&gt; | Yes| Callback used to return the result. If the widget state is obtained, **error** is undefined and **data** is the widget state obtained; otherwise, **error** is an error object.|
+| callback | AsyncCallback&lt;[FormStateInfo](js-apis-app-form-formInfo.md#formstateinfo)&gt; | Yes| Callback used to return the result. If the widget state is obtained, **error** is undefined and **data** is the widget state obtained; otherwise, **error** is an error object.|
 
 **Error codes**
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -1115,8 +1310,14 @@ Obtains the widget state. This API uses a promise to return the result.
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -1157,6 +1358,14 @@ Subscribes to widget uninstall events. This API uses an asynchronous callback to
 | type | string | Yes  | Event type. The value **'formUninstall'** indicates a widget uninstallation event.|
 | callback | Callback&lt;string&gt; | Yes| Callback used to return the widget ID.|
 
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 202 | The application is not a system application. |
+| 401 | If the input parameter is not valid parameter. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
+
 **Example**
 
 ```ts
@@ -1181,6 +1390,14 @@ Unsubscribes from widget uninstall events. This API uses an asynchronous callbac
 | type | string | Yes  | Event type. The value **'formUninstall'** indicates a widget uninstallation event.|
 | callback | Callback&lt;string&gt; | No| Callback used to return the widget ID. If it is left unspecified, it indicates the callback for all the events that have been subscribed.<br> The value must be the same as that in **on('formUninstall')**.|
 
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 202 | The application is not a system application. |
+| 401 | If the input parameter is not valid parameter. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
+
 **Example**
 
 ```ts
@@ -1212,8 +1429,14 @@ Instructs the widgets to make themselves visible. This API uses an asynchronous
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -1257,8 +1480,14 @@ Instructs the widgets to make themselves visible. This API uses a promise to ret
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -1297,8 +1526,14 @@ Instructs the widgets to enable or disable updates. This API uses an asynchronou
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -1342,8 +1577,14 @@ Instructs the widgets to enable or disable updates. This API uses a promise to r
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -1381,9 +1622,14 @@ Shares a specified widget with a remote device. This API uses an asynchronous ca
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
-
+| 16500050 | An IPC connection error happened. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -1428,8 +1674,14 @@ Shares a specified widget with a remote device. This API uses a promise to retur
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -1461,11 +1713,78 @@ Notifies that the privacy protection status of the specified widgets changes. Th
 
 | Name| Type   | Mandatory| Description   |
 | ------ | ------ | ---- | ------- |
-| formId | string | Yes  | Widget ID.|
-| deviceId | string | Yes   | Remote device ID. |
+| formIds | Array\<string\> | Yes  | ID of the widgets.|
+| isProtected | boolean | Yes  | Whether privacy protection is enabled.|
+| callback | AsyncCallback\<void> | Yes| Callback used to return the result. If privacy protection is set successfully, **error** is undefined; otherwise, **error** is an error object.|
+
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
+| 401 | If the input parameter is not valid parameter. |
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|                    |
+
+**Example**
 
 ```ts
-var formIds = new Array('12400633174999288', '12400633174999289');
+import formHost from '@ohos.app.form.formHost';
+
+let formIds = new Array('12400633174999288', '12400633174999289');
+try {
+  formHost.notifyFormsPrivacyProtected(formIds, true, (error) => {
+    if (error) {
+      console.error(`error, code: ${error.code}, message: ${error.message}`);
+    }
+  });
+} catch(error) {
+  console.error(`catch error, code: ${error.code}, message: ${error.message}`);
+}
+```
+
+## notifyFormsPrivacyProtected
+
+function notifyFormsPrivacyProtected(formIds: Array\<string\>, isProtected: boolean): Promise\<void\>;
+
+Notifies that the privacy protection status of the specified widgets changes. This API uses a promise to return the result.
+
+**Required permissions**: ohos.permission.REQUIRE_FORM
+
+**System capability**: SystemCapability.Ability.Form
+
+**Parameters**
+
+| Name     | Type           | Mandatory| Description                            |
+| ----------- | --------------- | ---- | -------------------------------- |
+| formIds     | Array\<string\> | Yes  | ID of the widgets.|
+| isProtected | boolean         | Yes  | Whether privacy protection is enabled.              |
+
+**Return value**
+
+| Type               | Description                     |
+| ------------------- | ------------------------- |
+| Promise&lt;void&gt; | Promise that returns no value.|
+
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 201 | Permissions denied. |
+| 202 | The application is not a system application. |
+| 401 | If the input parameter is not valid parameter. |
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16501000 | An internal functional error occurred. |
+| For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|                    |
+
+```ts
+import formHost from '@ohos.app.form.formHost';
+
+let formIds = new Array('12400633174999288', '12400633174999289');
 try {
   formHost.notifyFormsPrivacyProtected(formIds, true).then(() => {
     console.log('formHost shareForm success');
diff --git a/en/application-dev/reference/apis/js-apis-app-form-formProvider.md b/en/application-dev/reference/apis/js-apis-app-form-formProvider.md
index 793e2a8895d451e230757a1d1deb06042b1cfdcb..18f56ff493a1b6c5973c12a22645b06b0ec4c04c 100644
--- a/en/application-dev/reference/apis/js-apis-app-form-formProvider.md
+++ b/en/application-dev/reference/apis/js-apis-app-form-formProvider.md
@@ -1,4 +1,4 @@
-# @ohos.app.form.formProvider (FormProvider)
+# @ohos.app.form.formProvider (formProvider)
 
 The **FormProvider** module provides APIs related to the widget provider. You can use the APIs to update a widget, set the next refresh time for a widget, obtain widget information, and request a widget release.
 
@@ -32,19 +32,26 @@ Sets the next refresh time for a widget. This API uses an asynchronous callback
 | Error Code ID| Error Message|
 | -------- | -------- |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501002 | The number of forms exceeds upper bound. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
 ```ts
 var formId = '12400633174999288';
 try {
-  formProvider.setFormNextRefreshTime(formId, 5, (error, data) => {
+  formProvider.setFormNextRefreshTime(formId, 5, (error) => {
     if (error) {
       console.log('formProvider setFormNextRefreshTime, error:' + JSON.stringify(error));
-    } else {
-      console.log(`formProvider setFormNextRefreshTime success`);
+      return;
     }
+    console.log(`formProvider setFormNextRefreshTime success`);
   });
 } catch (error) {
     console.log('error' + JSON.stringify(error))
@@ -77,7 +84,14 @@ Sets the next refresh time for a widget. This API uses a promise to return the r
 | Error Code ID| Error Message|
 | -------- | -------- |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501002 | The number of forms exceeds upper bound. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -115,7 +129,13 @@ Updates a widget. This API uses an asynchronous callback to return the result.
 | Error Code ID| Error Message|
 | -------- | -------- |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -124,12 +144,12 @@ import formBindingData from '@ohos.application.formBindingData';
 var formId = '12400633174999288';
 try {
   let obj = formBindingData.createFormBindingData({temperature:'22c', time:'22:00'});
-  formProvider.updateForm(formId, obj, (error, data) => {
+  formProvider.updateForm(formId, obj, (error) => {
     if (error) {
       console.log('formProvider updateForm, error:' + JSON.stringify(error));
-    } else {
-      console.log(`formProvider updateForm success`);
+      return;
     }
+    console.log(`formProvider updateForm success`);
   });
 } catch (error) {
   console.log(`catch err->${JSON.stringify(error)}`);
@@ -162,7 +182,13 @@ Updates a widget. This API uses a promise to return the result.
 | Error Code ID| Error Message|
 | -------- | -------- |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500060 | A service connection error happened, please try again later. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+| 16501001 | The ID of the form to be operated does not exist. |
+| 16501003 | The form can not be operated by the current application. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -196,11 +222,13 @@ Obtains the application's widget information on the device. This API uses an asy
 | callback | AsyncCallback&lt;Array&lt;[FormInfo](js-apis-app-form-formInfo.md)&gt;&gt; | Yes| Callback used to return the information obtained.|
 
 **Error codes**
-
 | Error Code ID| Error Message|
 | -------- | -------- |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 
 **Example**
@@ -210,9 +238,9 @@ try {
   formProvider.getFormsInfo((error, data) => {
     if (error) {
       console.log('formProvider getFormsInfo, error:' + JSON.stringify(error));
-    } else {
-      console.log('formProvider getFormsInfo, data:' + JSON.stringify(data));
+      return;
     }
+    console.log('formProvider getFormsInfo, data:' + JSON.stringify(data));
   });
 } catch (error) {
     console.log(`catch err->${JSON.stringify(error)}`);
@@ -238,7 +266,10 @@ Obtains the application's widget information that meets a filter criterion on th
 | Error Code ID| Error Message|
 | -------- | -------- |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -253,9 +284,9 @@ try {
   formProvider.getFormsInfo(filter, (error, data) => {
     if (error) {
       console.log('formProvider getFormsInfo, error:' + JSON.stringify(error));
-    } else {
-      console.log('formProvider getFormsInfo, data:' + JSON.stringify(data));
+      return;
     }
+    console.log('formProvider getFormsInfo, data:' + JSON.stringify(data));
   });
 } catch(error) {
   console.log(`catch err->${JSON.stringify(error)}`);
@@ -274,7 +305,7 @@ Obtains the application's widget information on the device. This API uses a prom
 
 | Name| Type   | Mandatory| Description   |
 | ------ | ------ | ---- | ------- |
-| filter | [formInfo.FormInfoFilter](js-apis-app-form-formInfo.md#forminfofilter) | No| Filter criterion.|
+| filter | [formInfo.FormInfoFilter](js-apis-app-form-formInfo.md#forminfofilter) | No| Filter criterion. |
 
 **Return value**
 
@@ -287,7 +318,10 @@ Obtains the application's widget information on the device. This API uses a prom
 | Error Code ID| Error Message|
 | -------- | -------- |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -324,15 +358,19 @@ Requests to publish a widget carrying data to the widget host. This API uses an
 | Name| Type                                                                   | Mandatory| Description            |
 | ------ | ---------------------------------------------------------------------- | ---- | ---------------- |
 | want | [Want](js-apis-application-want.md)                           | Yes  | Request used for publishing. The following fields must be included:<br>Information about the target widget.<br>**abilityName**: ability of the target widget.<br>**parameters**:<br>'ohos.extra.param.key.form_dimension'<br>'ohos.extra.param.key.form_name'<br>'ohos.extra.param.key.module_name' |
-| formBindingData.FormBindingData | [FormBindingData](js-apis-app-form-formBindingData.md#formbindingdata) | Yes  | Data used for creating the widget.|
+| formBindingData.FormBindingData | [FormBindingData](js-apis-app-form-formBindingData.md#formbindingdata)  | Yes  | Data used for creating the widget.|
 | callback | AsyncCallback&lt;string&gt; | Yes| Callback used to return the widget ID.|
 
 **Error codes**
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -351,9 +389,9 @@ try {
   formProvider.requestPublishForm(want, obj, (error, data) => {
     if (error) {
       console.log('formProvider requestPublishForm, error: ' + JSON.stringify(error));
-    } else {
-      console.log('formProvider requestPublishForm, form ID is: ' + JSON.stringify(data));
+      return;
     }
+    console.log('formProvider requestPublishForm, form ID is: ' + JSON.stringify(data));
   });
 } catch (error) {
   console.log(`catch err->${JSON.stringify(error)}`);
@@ -381,8 +419,12 @@ Requests to publish a widget to the widget host. This API uses an asynchronous c
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -399,9 +441,9 @@ try {
   formProvider.requestPublishForm(want, (error, data) => {
     if (error) {
       console.log('formProvider requestPublishForm, error: ' + JSON.stringify(error));
-    } else {
-      console.log('formProvider requestPublishForm, form ID is: ' + JSON.stringify(data));
+      return;
     }
+    console.log('formProvider requestPublishForm, form ID is: ' + JSON.stringify(data));
   });
 } catch (error) {
   console.log(`catch err->${JSON.stringify(error)}`);
@@ -424,7 +466,7 @@ Requests to publish a widget to the widget host. This API uses a promise to retu
 | Name         | Type                                                        | Mandatory| Description                                                        |
 | --------------- | ------------------------------------------------------------ | ---- | ------------------------------------------------------------ |
 | want            | [Want](js-apis-application-want.md)                          | Yes  | Request used for publishing. The following fields must be included:<br>Information about the target widget.<br>**abilityName**: ability of the target widget.<br>**parameters**:<br>'ohos.extra.param.key.form_dimension'<br>'ohos.extra.param.key.form_name'<br>'ohos.extra.param.key.module_name' |
-| formBindingData.FormBindingData | [FormBindingData](js-apis-app-form-formBindingData.md#formbindingdata) | No  | Data used for creating the widget.                                          |
+| formBindingData.FormBindingData | [FormBindingData](js-apis-app-form-formBindingData.md#formbindingdata) | No  | Data used for creating the widget. By default, no value is passed, indicating that no data is provided.                                     |
 
 **Return value**
 
@@ -436,8 +478,12 @@ Requests to publish a widget to the widget host. This API uses a promise to retu
 
 | Error Code ID| Error Message|
 | -------- | -------- |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+| 16500050 | An IPC connection error happened. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
 
 **Example**
 
@@ -477,6 +523,16 @@ Checks whether a widget can be published to the widget host. This API uses an as
 | ------ | ------ | ---- | ------- |
 | callback | AsyncCallback&lt;boolean&gt; | Yes| Callback used to return whether the widget can be published to the widget host.|
 
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 202 | The application is not a system application. |
+| 401 | If the input parameter is not valid parameter. |
+| 16500050 | An IPC connection error happened. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
+
 **Example**
 
 ```ts
@@ -530,6 +586,15 @@ Checks whether a widget can be published to the widget host. This API uses a pro
 | :------------ | :---------------------------------- |
 | Promise&lt;boolean&gt; | Promise used to return whether the widget can be published to the widget host.|
 
+**Error codes**
+
+| Error Code ID| Error Message|
+| -------- | -------- |
+| 202 | The application is not a system application. |
+| 16500050 | An IPC connection error happened. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).||
+
 **Example**
 
 ```ts
diff --git a/en/application-dev/reference/apis/js-apis-arraylist.md b/en/application-dev/reference/apis/js-apis-arraylist.md
index 283786a82fd1ce50d7632b9354b99f32ff4419fb..0cd79c938c8bb74f7fb919c7e6dc2e1afaa97cd8 100644
--- a/en/application-dev/reference/apis/js-apis-arraylist.md
+++ b/en/application-dev/reference/apis/js-apis-arraylist.md
@@ -1,8 +1,5 @@
 # @ohos.util.ArrayList (Linear Container ArrayList)
 
-> **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.
-
 **ArrayList** is a linear data structure that is implemented based on arrays. **ArrayList** can dynamically adjust the capacity based on project requirements. It increases the capacity by 50% each time.
 
 Similar to **ArrayList**, **[Vector](js-apis-vector.md)** is also implemented based on arrays and can dynamically adjust the capacity. It increases the capability by 100% each time.
@@ -14,6 +11,11 @@ When compared with **[LinkedList](js-apis-linkedlist.md)**, **ArrayList** is mor
 This topic uses the following to identify the use of generics:
 - T: Type
 
+> **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
 
 ```ts
@@ -160,9 +162,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let arrayList = new ArrayList();
-let result = arrayList.has("squirrel");
 arrayList.add("squirrel");
-let result1 = arrayList.has("squirrel");
+let result = arrayList.has("squirrel");
 ```
 
 ### getIndexOf
@@ -535,9 +536,7 @@ arrayList.add(2);
 arrayList.add(4);
 arrayList.add(5);
 arrayList.add(4);
-let result1 = arrayList.subArrayList(2, 4);
-let result2 = arrayList.subArrayList(4, 3);
-let result3 = arrayList.subArrayList(2, 6);
+let result = arrayList.subArrayList(2, 4);
 ```
 
 ### clear
diff --git a/en/application-dev/reference/apis/js-apis-audio.md b/en/application-dev/reference/apis/js-apis-audio.md
index db559d0ef3d858958e0353a13baa14f684201158..48c6c93fd80e0f8ed762e2cf096dfbcfc7958c65 100644
--- a/en/application-dev/reference/apis/js-apis-audio.md
+++ b/en/application-dev/reference/apis/js-apis-audio.md
@@ -483,8 +483,8 @@ Enumerates the audio channels.
 
 | Name     |  Value      | Description    |
 | --------- | -------- | -------- |
-| CHANNEL_1 | 0x1 << 0 | Mono.|
-| CHANNEL_2 | 0x1 << 1 | Dual-channel.|
+| CHANNEL_1 | 0x1 << 0 | Channel 1. |
+| CHANNEL_2 | 0x1 << 1 | Channel 2. |
 
 ## AudioSamplingRate<sup>8+</sup>
 
diff --git a/en/application-dev/reference/apis/js-apis-buffer.md b/en/application-dev/reference/apis/js-apis-buffer.md
index 72e65e53e63380ef4ea0aa9b33796e236bc7ee84..5a014e7cfe5618c7e31741b43d32ce743d86a0b2 100644
--- a/en/application-dev/reference/apis/js-apis-buffer.md
+++ b/en/application-dev/reference/apis/js-apis-buffer.md
@@ -54,7 +54,7 @@ Creates and initializes a **Buffer** instance of the specified length.
 
 | Type| Description|
 | -------- | -------- |
-| Buffer | Initialized **Buffer** instance.|
+| Buffer | **Buffer** instance created.|
 
 **Example**
 
@@ -417,11 +417,11 @@ Checks whether the specified object is a **Buffer** instance.
 ```ts
 import buffer from '@ohos.buffer';
 
-buffer.isBuffer(buffer.alloc(10)); // true
-buffer.isBuffer(buffer.from('foo')); // true
-buffer.isBuffer('a string'); // false
-buffer.isBuffer([]); // false
-buffer.isBuffer(new Uint8Array(1024)); // false
+let result = buffer.isBuffer(buffer.alloc(10)); // true
+let result1 = buffer.isBuffer(buffer.from('foo')); // true
+let result2 = buffer.isBuffer('a string'); // false
+let result3 = buffer.isBuffer([]); // false
+let result4 = buffer.isBuffer(new Uint8Array(1024)); // false
 ```
 
 ## buffer.isEncoding
@@ -436,7 +436,7 @@ Checks whether the encoding format is supported.
 
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
-| encoding | string | Yes| Encoding format to check. |
+| encoding | string | Yes| Encoding format.|
 
 **Return value**
 
@@ -838,7 +838,7 @@ console.log(buf.lastIndexOf('buffer').toString());	// Print: 17
 
 readBigInt64BE(offset?: number): bigint
 
-Reads a signed, big-endian 64-bit integer from this **Buffer** instance at the specified offset.
+Reads a signed, big-endian 64-bit big integer from this **Buffer** instance at the specified offset.
 
 **System capability**: SystemCapability.Utils.Lang
 
@@ -852,7 +852,7 @@ Reads a signed, big-endian 64-bit integer from this **Buffer** instance at the s
 
 | Type| Description|
 | -------- | -------- |
-| bigint | A signed, big-endian 64-bit Big integer. |
+| bigint | Data read.|
 
 **Error codes**
 
@@ -872,14 +872,14 @@ let buf = buffer.from([0x63, 0x64, 0x65, 0x66, 0x67, 0x68, 0x69, 0x70,
 console.log(buf.readBigInt64BE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(8);
-buf1.writeBigInt64BE(0x0102030405060708n, 0);
+let result = buf1.writeBigInt64BE(0x0102030405060708n, 0);
 ```
 
 ### readBigInt64LE
 
 readBigInt64LE(offset?: number): bigint
 
-Reads a signed, little-endian 64-bit Big integer from this **Buffer** instance at the specified offset.
+Reads a signed, little-endian 64-bit big integer from this **Buffer** instance at the specified offset.
 
 **System capability**: SystemCapability.Utils.Lang
 
@@ -893,7 +893,7 @@ Reads a signed, little-endian 64-bit Big integer from this **Buffer** instance a
 
 | Type| Description|
 | -------- | -------- |
-| bigint | A signed, little-endian 64-bit Big integer. |
+| bigint | Data read.|
 
 **Error codes**
 
@@ -913,14 +913,14 @@ let buf = buffer.from([0x63, 0x64, 0x65, 0x66, 0x67, 0x68, 0x69, 0x70,
 console.log(buf.readBigInt64LE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(8);
-buf1.writeBigInt64BE(0x0102030405060708n, 0);
+let result = buf1.writeBigInt64BE(0x0102030405060708n, 0);
 ```
 
 ### readBigUInt64BE
 
 readBigUInt64BE(offset?: number): bigint
 
-Reads an unsigned, big-endian 64-bit Big integer from this **Buffer** instance at the specified offset.
+Reads an unsigned, big-endian 64-bit big integer from this **Buffer** instance at the specified offset.
 
 **System capability**: SystemCapability.Utils.Lang
 
@@ -934,7 +934,7 @@ Reads an unsigned, big-endian 64-bit Big integer from this **Buffer** instance a
 
 | Type| Description|
 | -------- | -------- |
-| bigint | An unsigned, big-endian 64-bit Big integer. |
+| bigint | Data read.|
 
 **Error codes**
 
@@ -954,14 +954,14 @@ let buf = buffer.from([0x63, 0x64, 0x65, 0x66, 0x67, 0x68, 0x69, 0x70,
 console.log(buf.readBigUInt64BE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(8);
-buf1.writeBigUInt64BE(0xdecafafecacefaden, 0);
+let result = buf1.writeBigUInt64BE(0xdecafafecacefaden, 0);
 ```
 
 ### readBigUInt64LE
 
 readBigUInt64LE(offset?: number): bigint
 
-Reads an unsigned, little-endian 64-bit Big integer from this **Buffer** instance at the specified offset.
+Reads an unsigned, little-endian 64-bit big integer from this **Buffer** instance at the specified offset.
 
 **System capability**: SystemCapability.Utils.Lang
 
@@ -975,7 +975,7 @@ Reads an unsigned, little-endian 64-bit Big integer from this **Buffer** instanc
 
 | Type| Description|
 | -------- | -------- |
-| bigint | An unsigned, little-endian 64-bit Big integer. |
+| bigint | Data read.|
 
 **Error codes**
 
@@ -995,14 +995,14 @@ let buf = buffer.from([0x63, 0x64, 0x65, 0x66, 0x67, 0x68, 0x69, 0x70,
 console.log(buf.readBigUInt64LE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(8);
-buf1.writeBigUInt64BE(0xdecafafecacefaden, 0);
+let result = buf1.writeBigUInt64BE(0xdecafafecacefaden, 0);
 ```
 
 ### readDoubleBE
 
 readDoubleBE(offset?: number): number
 
-Reads a big-endian double-precision floating-point number from this **Buffer** instance at the specified offset.
+Reads a 64-bit, big-endian floating-point number from this **Buffer** instance at the specified offset.
 
 **System capability**: SystemCapability.Utils.Lang
 
@@ -1016,7 +1016,7 @@ Reads a big-endian double-precision floating-point number from this **Buffer** i
 
 | Type| Description|
 | -------- | -------- |
-| number | A big-endian double-precision floating-point number. |
+| number | Data read.|
 
 **Error codes**
 
@@ -1035,14 +1035,14 @@ let buf = buffer.from([1, 2, 3, 4, 5, 6, 7, 8]);
 console.log(buf.readDoubleBE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(8);
-buf1.writeDoubleBE(123.456, 0);
+let result = buf1.writeDoubleBE(123.456, 0);
 ```
 
 ### readDoubleLE
 
 readDoubleLE(offset?: number): number
 
-Reads a little-endian double-precision floating-point number from this **Buffer** instance at the specified offset.
+Reads a 64-bit, little-endian floating-point number from this **Buffer** instance at the specified offset.
 
 **System capability**: SystemCapability.Utils.Lang
 
@@ -1056,7 +1056,7 @@ Reads a little-endian double-precision floating-point number from this **Buffer*
 
 | Type| Description|
 | -------- | -------- |
-| number | A little-endian double-precision floating-point number. |
+| number | Data read.|
 
 **Error codes**
 
@@ -1075,14 +1075,14 @@ let buf = buffer.from([1, 2, 3, 4, 5, 6, 7, 8]);
 console.log(buf.readDoubleLE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(8);
-buf1.writeDoubleLE(123.456, 0);
+let result = buf1.writeDoubleLE(123.456, 0);
 ```
 
 ### readFloatBE
 
 readFloatBE(offset?: number): number
 
-Reads a big-endian single-precision floating-point number from this **Buffer** instance at the specified offset.
+Reads a 32-bit, big-endian floating-point number from this **Buffer** instance at the specified offset.
 
 **System capability**: SystemCapability.Utils.Lang
 
@@ -1096,7 +1096,7 @@ Reads a big-endian single-precision floating-point number from this **Buffer** i
 
 | Type| Description|
 | -------- | -------- |
-| number | A big-endian single-precision floating-point number. |
+| number | Data read.|
 
 **Error codes**
 
@@ -1115,14 +1115,14 @@ let buf = buffer.from([1, 2, 3, 4, 5, 6, 7, 8]);
 console.log(buf.readFloatBE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(4);
-buf1.writeFloatBE(0xcabcbcbc, 0);
+let result = buf1.writeFloatBE(0xcabcbcbc, 0);
 ```
 
 ### readFloatLE
 
 readFloatLE(offset?: number): number
 
-Reads a little-endian single-precision floating-point number from this **Buffer** instance at the specified offset.
+Reads a 32-bit, little-endian floating-point number from this **Buffer** instance at the specified offset.
 
 **System capability**: SystemCapability.Utils.Lang
 
@@ -1136,7 +1136,7 @@ Reads a little-endian single-precision floating-point number from this **Buffer*
 
 | Type| Description|
 | -------- | -------- |
-| number | A little-endian single-precision floating-point number. |
+| number | Data read.|
 
 **Error codes**
 
@@ -1155,7 +1155,7 @@ let buf = buffer.from([1, 2, 3, 4, 5, 6, 7, 8]);
 console.log(buf.readFloatLE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(4);
-buf1.writeFloatLE(0xcabcbcbc, 0);
+let result = buf1.writeFloatLE(0xcabcbcbc, 0);
 ```
 
 ### readInt8
@@ -1176,7 +1176,7 @@ Reads a signed 8-bit integer from this **Buffer** instance at the specified offs
 
 | Type| Description|
 | -------- | -------- |
-| number | A signed 8-bit integer. |
+| number | Data read.|
 
 **Error codes**
 
@@ -1196,7 +1196,7 @@ console.log(buf.readInt8(0).toString());	// Print: -1
 console.log(buf.readInt8(1).toString());	// Print: 5
 
 let buf1 = buffer.allocUninitializedFromPool(2);
-buf1.writeInt8(0x12);
+let result = buf1.writeInt8(0x12);
 ```
 
 ### readInt16BE
@@ -1217,7 +1217,7 @@ Reads a signed, big-endian 16-bit integer from this **Buffer** instance at the s
 
 | Type| Description|
 | -------- | -------- |
-| number | A signed, big-endian 16-bit integer.|
+| number | Data read.|
 
 **Error codes**
 
@@ -1236,7 +1236,7 @@ let buf = buffer.from([0, 5]);
 console.log(buf.readInt16BE(0).toString());	// Print: 5
 
 let buf1 = buffer.alloc(2);
-buf1.writeInt16BE(0x1234, 0);
+let result = buf1.writeInt16BE(0x1234, 0);
 ```
 
 ### readInt16LE
@@ -1257,7 +1257,7 @@ Reads a signed, little-endian 16-bit integer from this **Buffer** instance at th
 
 | Type| Description|
 | -------- | -------- |
-| number | A signed, little-endian 16-bit integer.|
+| number | Data read.|
 
 **Error codes**
 
@@ -1276,7 +1276,7 @@ let buf = buffer.from([0, 5]);
 console.log(buf.readInt16LE(0).toString());	// Print: 1280
 
 let buf1 = buffer.alloc(2);
-buf1.writeInt16BE(0x1234, 0);
+let result = buf1.writeInt16BE(0x1234, 0);
 ```
 
 ### readInt32BE
@@ -1297,7 +1297,7 @@ Reads a signed, big-endian 32-bit integer from this **Buffer** instance at the s
 
 | Type| Description|
 | -------- | -------- |
-| number | A signed, big-endian 32-bit integer.|
+| number | Data read.|
 
 **Error codes**
 
@@ -1316,7 +1316,7 @@ let buf = buffer.from([0, 0, 0, 5]);
 console.log(buf.readInt32BE(0).toString());	// Print: 5
 
 let buf1 = buffer.alloc(4);
-buf1.writeInt32BE(0x12345678, 0);
+let result = buf1.writeInt32BE(0x12345678, 0);
 ```
 
 ### readInt32LE
@@ -1337,7 +1337,7 @@ Reads a signed, little-endian 32-bit integer from this **Buffer** instance at th
 
 | Type| Description|
 | -------- | -------- |
-| number | A signed, little-endian 32-bit integer.|
+| number | Data read.|
 
 **Error codes**
 
@@ -1356,7 +1356,7 @@ let buf = buffer.from([0, 0, 0, 5]);
 console.log(buf.readInt32LE(0).toString());	// Print: 83886080
 
 let buf1 = buffer.alloc(4);
-buf1.writeInt32BE(0x12345678, 0);
+let result = buf1.writeInt32BE(0x12345678, 0);
 ```
 
 ### readIntBE
@@ -1399,7 +1399,7 @@ let num = buf.readIntBE(0, 1);
 console.log(num.toString()); // 97
 
 let buf1 = buffer.allocUninitializedFromPool(6);
-buf1.writeIntBE(0x123456789011, 0, 6);
+let result = buf1.writeIntBE(0x123456789011, 0, 6);
 ```
 
 
@@ -1442,7 +1442,7 @@ let buf = buffer.from([0x12, 0x34, 0x56, 0x78, 0x90, 0xab]);
 console.log(buf.readIntLE(0, 6).toString(16));
 
 let buf1 = buffer.allocUninitializedFromPool(6);
-buf1.writeIntLE(0x123456789011, 0, 6);
+let result = buf1.writeIntLE(0x123456789011, 0, 6);
 ```
 
 ### readUInt8
@@ -1464,7 +1464,7 @@ Reads an unsigned 8-bit integer from this **Buffer** instance at the specified o
 
 | Type| Description|
 | -------- | -------- |
-| number | An unsigned 8-bit integer.|
+| number | Data read.|
 
 **Error codes**
 
@@ -1484,7 +1484,7 @@ console.log(buf.readUInt8(0).toString());
 console.log(buf.readUInt8(1).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(4);
-buf1.writeUInt8(0x42);
+let result = buf1.writeUInt8(0x42);
 ```
 
 ### readUInt16BE
@@ -1506,7 +1506,7 @@ Reads an unsigned, big-endian 16-bit integer from this **Buffer** instance at th
 
 | Type| Description|
 | -------- | -------- |
-| number | An unsigned, big-endian 16-bit integer.|
+| number | Data read.|
 
 **Error codes**
 
@@ -1526,7 +1526,7 @@ console.log(buf.readUInt16BE(0).toString(16));
 console.log(buf.readUInt16BE(1).toString(16));
 
 let buf1 = buffer.allocUninitializedFromPool(4);
-buf1.writeUInt16BE(0x1234, 0);
+let result = buf1.writeUInt16BE(0x1234, 0);
 ```
 
 ### readUInt16LE
@@ -1548,7 +1548,7 @@ Reads an unsigned, little-endian 16-bit integer from this **Buffer** instance at
 
 | Type| Description|
 | -------- | -------- |
-| number | An unsigned, little-endian 16-bit integer.|
+| number | Data read.|
 
 **Error codes**
 
@@ -1568,7 +1568,7 @@ console.log(buf.readUInt16LE(0).toString(16));
 console.log(buf.readUInt16LE(1).toString(16));
 
 let buf1 = buffer.allocUninitializedFromPool(4);
-buf1.writeUInt16LE(0x1234, 0);
+let result = buf1.writeUInt16LE(0x1234, 0);
 ```
 
 ### readUInt32BE
@@ -1590,7 +1590,7 @@ Reads an unsigned, big-endian 32-bit integer from this **Buffer** instance at th
 
 | Type| Description|
 | -------- | -------- |
-| number | An unsigned, big-endian 32-bit integer.|
+| number | Data read.|
 
 **Error codes**
 
@@ -1609,7 +1609,7 @@ let buf = buffer.from([0x12, 0x34, 0x56, 0x78]);
 console.log(buf.readUInt32BE(0).toString(16));
 
 let buf1 = buffer.allocUninitializedFromPool(4);
-buf1.writeUInt32BE(0x12345678, 0);
+let result = buf1.writeUInt32BE(0x12345678, 0);
 ```
 
 ### readUInt32LE
@@ -1631,7 +1631,7 @@ Reads an unsigned, little-endian 32-bit integer from this **Buffer** instance at
 
 | Type| Description|
 | -------- | -------- |
-| number | An unsigned, little-endian 32-bit integer.|
+| number | Data read.|
 
 **Error codes**
 
@@ -1650,7 +1650,7 @@ let buf = buffer.from([0x12, 0x34, 0x56, 0x78]);
 console.log(buf.readUInt32LE(0).toString(16));
 
 let buf1 = buffer.allocUninitializedFromPool(4);
-buf1.writeUInt32LE(0x12345678, 0);
+let result = buf1.writeUInt32LE(0x12345678, 0);
 ```
 
 ### readUIntBE
@@ -1692,7 +1692,7 @@ let buf = buffer.from([0x12, 0x34, 0x56, 0x78, 0x90, 0xab]);
 console.log(buf.readUIntBE(0, 6).toString(16));
 
 let buf1 = buffer.allocUninitializedFromPool(4);
-buf1.writeUIntBE(0x13141516, 0, 4);
+let result = buf1.writeUIntBE(0x13141516, 0, 4);
 ```
 
 ### readUIntLE
@@ -1715,7 +1715,7 @@ Reads the specified number of bytes from this **Buffer** instance at the specifi
 
 | Type| Description|
 | -------- | -------- |
-| number | A signed, big-endian 64-bit integer.|
+| number | Data read.|
 
 **Error codes**
 
@@ -1734,7 +1734,7 @@ let buf = buffer.from([0x12, 0x34, 0x56, 0x78, 0x90, 0xab]);
 console.log(buf.readUIntLE(0, 6).toString(16));
 
 let buf1 = buffer.allocUninitializedFromPool(4);
-buf1.writeUIntLE(0x13141516, 0, 4);
+let result = buf1.writeUIntLE(0x13141516, 0, 4);
 ```
 
 ### subarray
@@ -2045,7 +2045,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-buf.writeBigInt64BE(0x0102030405060708n, 0);
+let result = buf.writeBigInt64BE(0x0102030405060708n, 0);
 ```
 
 ### writeBigInt64LE
@@ -2084,7 +2084,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-buf.writeBigInt64LE(0x0102030405060708n, 0);
+let result = buf.writeBigInt64LE(0x0102030405060708n, 0);
 ```
 
 ### writeBigUInt64BE
@@ -2123,7 +2123,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-buf.writeBigUInt64BE(0xdecafafecacefaden, 0);
+let result = buf.writeBigUInt64BE(0xdecafafecacefaden, 0);
 ```
 
 ### writeBigUInt64LE
@@ -2162,7 +2162,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-buf.writeBigUInt64LE(0xdecafafecacefaden, 0);
+let result = buf.writeBigUInt64LE(0xdecafafecacefaden, 0);
 ```
 
 ### writeDoubleBE
@@ -2201,7 +2201,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-buf.writeDoubleBE(123.456, 0);
+let result = buf.writeDoubleBE(123.456, 0);
 ```
 
 ### writeDoubleLE
@@ -2240,7 +2240,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-buf.writeDoubleLE(123.456, 0);
+let result = buf.writeDoubleLE(123.456, 0);
 ```
 
 ### writeFloatBE
@@ -2279,7 +2279,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-buf.writeFloatBE(0xcafebabe, 0);
+let result = buf.writeFloatBE(0xcafebabe, 0);
 ```
 
 
@@ -2319,7 +2319,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-buf.writeFloatLE(0xcafebabe, 0);
+let result = buf.writeFloatLE(0xcafebabe, 0);
 ```
 
 ### writeInt8
@@ -2358,8 +2358,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(2);
-buf.writeInt8(2, 0);
-buf.writeInt8(-2, 1);
+let result = buf.writeInt8(2, 0);
+let result1 = buf.writeInt8(-2, 1);
 ```
 
 
@@ -2399,7 +2399,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(2);
-buf.writeInt16BE(0x0102, 0);
+let result = buf.writeInt16BE(0x0102, 0);
 ```
 
 
@@ -2439,7 +2439,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(2);
-buf.writeInt16LE(0x0304, 0);
+let result = buf.writeInt16LE(0x0304, 0);
 ```
 
 ### writeInt32BE
@@ -2478,7 +2478,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(4);
-buf.writeInt32BE(0x01020304, 0);
+let result = buf.writeInt32BE(0x01020304, 0);
 ```
 
 
@@ -2518,7 +2518,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(4);
-buf.writeInt32LE(0x05060708, 0);
+let result = buf.writeInt32LE(0x05060708, 0);
 ```
 
 ### writeIntBE
@@ -2558,7 +2558,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(6);
-buf.writeIntBE(0x1234567890ab, 0, 6);
+let result = buf.writeIntBE(0x1234567890ab, 0, 6);
 ```
 
 
@@ -2599,7 +2599,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(6);
-buf.writeIntLE(0x1234567890ab, 0, 6);
+let result = buf.writeIntLE(0x1234567890ab, 0, 6);
 ```
 
 ### writeUInt8
@@ -2638,10 +2638,10 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(4);
-buf.writeUInt8(0x3, 0);
-buf.writeUInt8(0x4, 1);
-buf.writeUInt8(0x23, 2);
-buf.writeUInt8(0x42, 3);
+let result = buf.writeUInt8(0x3, 0);
+let result1 = buf.writeUInt8(0x4, 1);
+let result2 = buf.writeUInt8(0x23, 2);
+let result3 = buf.writeUInt8(0x42, 3);
 ```
 
 ### writeUInt16BE
@@ -2680,8 +2680,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(4);
-buf.writeUInt16BE(0xdead, 0);
-buf.writeUInt16BE(0xbeef, 2);
+let result = buf.writeUInt16BE(0xdead, 0);
+let result1 = buf.writeUInt16BE(0xbeef, 2);
 ```
 
 ### writeUInt16LE
@@ -2720,8 +2720,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(4);
-buf.writeUInt16LE(0xdead, 0);
-buf.writeUInt16LE(0xbeef, 2);
+let result = buf.writeUInt16LE(0xdead, 0);
+let result1 = buf.writeUInt16LE(0xbeef, 2);
 ```
 
 ### writeUInt32BE
@@ -2760,7 +2760,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(4);
-buf.writeUInt32BE(0xfeedface, 0);
+let result = buf.writeUInt32BE(0xfeedface, 0);
 ```
 
 ### writeUInt32LE
@@ -2799,7 +2799,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(4);
-buf.writeUInt32LE(0xfeedface, 0);
+let result = buf.writeUInt32LE(0xfeedface, 0);
 ```
 
 ### writeUIntBE
@@ -2839,7 +2839,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(6);
-buf.writeUIntBE(0x1234567890ab, 0, 6);
+let result = buf.writeUIntBE(0x1234567890ab, 0, 6);
 ```
 
 ### writeUIntLE
@@ -2879,7 +2879,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(6);
-buf.writeUIntLE(0x1234567890ab, 0, 6);
+let result = buf.writeUIntLE(0x1234567890ab, 0, 6);
 ```
 
 ## Blob
@@ -2906,7 +2906,7 @@ A constructor used to create a **Blob** instance.
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
 | sources | string[]&nbsp;\|&nbsp;ArrayBuffer[]&nbsp;\|&nbsp;TypedArray[]&nbsp;\|&nbsp;DataView[]&nbsp;\|&nbsp;Blob[] | Yes| Data sources of the **Blob** instance.|
-| options | Object | No| options:<br>- **endings**: 'transparent' or 'native'.<br>- **type**: type of the data in **Blob**.|
+| options | Object | No| options:<br>- **endings**: specifies how the terminator **'\n'** is output. The value can be **'native'** or **'transparent'**. **'native'** means that the terminator follows the system. **'transparent'** means that the terminator stored in the **Blob** instance remains unchanged. The default value is **'transparent'**.<br>- **type**: type of the data in the **Blob** instance. This type represents the MIME type of the data. However, it is not used for type format validation. The default value is **''**.|
 
 
 **Example**
@@ -2951,9 +2951,9 @@ Creates a **Blob** instance by copying specified data from this **Blob** instanc
 
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
-| start | number | No| Offset to the start position of the data to copy.|
-| end | number | No| Offset to the end position of the data to copy.|
-| type | string | No| Type of the data in the new **Blob** instance.|
+| start | number | No| Offset to the start position of the data to copy. The default value is **0**.|
+| end | number | No| Offset to the end position of the data to copy. The default value is the data length in the original **Blob** instance.|
+| type | string | No| Type of the data in the new **Blob** instance. The default value is **''**.|
 
 **Return value**
 | Type| Description|
diff --git a/en/application-dev/reference/apis/js-apis-bundleManager.md b/en/application-dev/reference/apis/js-apis-bundleManager.md
index b7bf94d4b06a10e3f99a4430bfda097fe661204f..5008358c021f3498d81b71c4696c38f8fe073603 100644
--- a/en/application-dev/reference/apis/js-apis-bundleManager.md
+++ b/en/application-dev/reference/apis/js-apis-bundleManager.md
@@ -389,7 +389,6 @@ For details about the error codes, see [Bundle Error Codes](../errorcodes/errorc
 | ID| Error Message                             |
 | -------- | ------------------------------------- |
 | 17700001 | The specified bundleName is not found. |
-| 17700004 | The specified user ID is not found.    |
 | 17700026 | The specified bundle is disabled.      |
 
 **Example**
@@ -575,7 +574,6 @@ For details about the error codes, see [Bundle Error Codes](../errorcodes/errorc
 | ID| Error Message                            |
 | -------- | --------------------------------------|
 | 17700001 | The specified bundleName is not found. |
-| 17700004 | The specified user ID is not found.     |
 | 17700026 | The specified bundle is disabled.      |
 
 **Example**
@@ -725,14 +723,6 @@ Obtains the information about all bundles based on the given bundle flags. This
 | bundleFlags | [number](#bundleflag) | Yes  | Type of the bundle information to obtain.  |
 | callback | AsyncCallback<Array\<[BundleInfo](js-apis-bundleManager-bundleInfo.md)>> | Yes| Callback used to return the result. If the operation is successful, **err** is **null** and **data** is the array of bundle information obtained. Otherwise, **err** is an error object.|
 
-**Error codes**
-
-For details about the error codes, see [Bundle Error Codes](../errorcodes/errorcode-bundle.md).
-
-| ID| Error Message                        |
-| -------- | ---------------------------------- |
-| 17700004 | The specified user ID is not found. |
-
 **Example**
 
 ```ts
@@ -872,14 +862,6 @@ Obtains the information about all applications based on the given application fl
 | appFlags | [number](#applicationflag) | Yes  | Type of the application information to obtain.                      |
 | callback | AsyncCallback<Array\<[ApplicationInfo](js-apis-bundleManager-applicationInfo.md)>> | Yes| Callback used to return the result. If the operation is successful, **err** is **null** and **data** is the array of application information obtained. Otherwise, **err** is an error object.|
 
-**Error codes**
-
-For details about the error codes, see [Bundle Error Codes](../errorcodes/errorcode-bundle.md).
-
-| ID| Error Message                        |
-| -------- | ---------------------------------- |
-| 17700004 | The specified user ID is not found. |
-
 **Example**
 
 ```ts
@@ -1038,7 +1020,6 @@ For details about the error codes, see [Bundle Error Codes](../errorcodes/errorc
 | -------- | -------------------------------------- |
 | 17700001 | The specified bundleName is not found. |
 | 17700003 | The specified ability is not found.    |
-| 17700004 | The specified userId is invalid.       |
 | 17700026 | The specified bundle is disabled.      |
 | 17700029 | The specified ability is disabled.     |
 
@@ -1235,7 +1216,6 @@ For details about the error codes, see [Bundle Error Codes](../errorcodes/errorc
 | -------- | -------------------------------------------- |
 | 17700001 | The specified bundleName is not found.       |
 | 17700003 | The specified extensionAbility is not found. |
-| 17700004 | The specified userId is invalid.       |
 | 17700026 | The specified bundle is disabled.            |
 
 **Example**
@@ -2159,7 +2139,6 @@ For details about the error codes, see [Bundle Error Codes](../errorcodes/errorc
 | ID| Error Message                            |
 | -------- | --------------------------------------|
 | 17700001 | The specified bundleName is not found. |
-| 17700004 | The specified user ID is not found.     |
 | 17700026 | The specified bundle is disabled.      |
 
 **Example**
diff --git a/en/application-dev/reference/apis/js-apis-commonEventManager.md b/en/application-dev/reference/apis/js-apis-commonEventManager.md
index ded3d353d53f58e3dd59b3818029839da90cfcaa..225bd59b0ae8e7fa2b33b50efaa875bdb82705be 100644
--- a/en/application-dev/reference/apis/js-apis-commonEventManager.md
+++ b/en/application-dev/reference/apis/js-apis-commonEventManager.md
@@ -36,12 +36,13 @@ Publishes a common event. This API uses an asynchronous callback to return the r
 **Error codes**
 For details about the error codes, see [Event Error Codes](../errorcodes/errorcode-CommonEventService.md).
 
-|ID   |Error Message           |
-|-----------|--------------------|
-|1500004    |not System services or System app|
-|1500007    |message send error|
-|1500008    |CEMS error|
-|1500009    |system error|
+| ID| Error Message                           |
+| -------- | ----------------------------------- |
+| 401  | The parameter check failed.             |
+| 1500004  | not System services.                |
+| 1500007  | error sending message to Common Event Service. |
+| 1500008  | Common Event Service does not complete initialization. |
+| 1500009  | error obtaining system parameters.  |
 
 **Example**
 
@@ -80,17 +81,16 @@ Publishes a common event with given attributes. This API uses an asynchronous ca
 | callback | syncCallback\<void>   | Yes  | Callback used to return the result. |
 
 **Error codes**
-|ID   |Error Message           |
-|-----------|--------------------|
-|1500004    |not System services or System app|
-|1500007    |message send error|
-|1500008    |CEMS error|
-|1500009    |system error|
-
+| ID| Error Message                           |
+| -------- | ----------------------------------- |
+| 401  | The parameter check failed.             |
+| 1500004  | not System services.                |
+| 1500007  | error sending message to Common Event Service. |
+| 1500008  | Common Event Service does not complete initialization. |
+| 1500009  | error obtaining system parameters.  |
 
 **Example**
 
-
 ```ts
 // Attributes of a common event.
 var options = {
@@ -137,12 +137,14 @@ Publishes a common event to a specific user. This API uses an asynchronous callb
 | callback | AsyncCallback\<void> | Yes  | Callback used to return the result.            |
 
 **Error codes**
-|ID   |Error Message           |
-|-----------|--------------------|
-|1500004    |not System services or System app|
-|1500007    |message send error|
-|1500008    |CEMS error|
-|1500009    |system error|
+| ID| Error Message                           |
+| -------- | ----------------------------------- |
+| 202  | not system app.                         |
+| 401  | The parameter check failed.             |
+| 1500004  | not System services.                |
+| 1500007  | error sending message to Common Event Service. |
+| 1500008  | Common Event Service does not complete initialization. |
+| 1500009  | error obtaining system parameters.  |
 
 **Example**
 
@@ -189,16 +191,17 @@ Publishes a common event with given attributes to a specific user. This API uses
 | callback | AsyncCallback\<void>   | Yes  | Callback used to return the result. |
 
 **Error codes**
-|ID   |Error Message           |
-|-----------|--------------------|
-|1500004    |not System services or System app|
-|1500007    |message send error|
-|1500008    |CEMS error|
-|1500009    |system error|
+| ID| Error Message                           |
+| -------- | ----------------------------------- |
+| 202  | not system app.                         |
+| 401  | The parameter check failed.             |
+| 1500004  | not System services.                |
+| 1500007  | error sending message to Common Event Service. |
+| 1500008  | Common Event Service does not complete initialization. |
+| 1500009  | error obtaining system parameters.  |
 
 **Example**
 
-
 ```ts
 // Attributes of a common event.
 var options = {
@@ -243,6 +246,14 @@ Creates a subscriber. This API uses an asynchronous callback to return the resul
 | subscribeInfo | [CommonEventSubscribeInfo](./js-apis-inner-commonEvent-commonEventSubscribeInfo.md)        | Yes  | Subscriber information.            |
 | callback      | AsyncCallback\<[CommonEventSubscriber](./js-apis-inner-commonEvent-commonEventSubscriber.md)> | Yes  | Callback used to return the result.|
 
+**Error codes**
+
+ For details about the error codes, see [Event Error Codes](../errorcodes/errorcode-CommonEventService.md).
+
+| ID| Error Message                           |
+| -------- | ----------------------------------- |
+| 401  | The parameter check failed.             |
+
 **Example**
 
 
@@ -293,6 +304,14 @@ Creates a subscriber. This API uses a promise to return the result.
 | --------------------------------------------------------- | ---------------- |
 | Promise\<[CommonEventSubscriber](./js-apis-inner-commonEvent-commonEventSubscriber.md)> | Promise used to return the subscriber object.|
 
+**Error codes**
+
+ For details about the error codes, see [Event Error Codes](../errorcodes/errorcode-CommonEventService.md).
+
+| ID| Error Message                           |
+| -------- | ----------------------------------- |
+| 401  | The parameter check failed.             |
+
 **Example**
 
 ```ts
@@ -334,6 +353,17 @@ Subscribes to common events. This API uses an asynchronous callback to return th
 | subscriber | [CommonEventSubscriber](./js-apis-inner-commonEvent-commonEventSubscriber.md)     | Yes  | Subscriber object.                |
 | callback   | AsyncCallback\<[CommonEventData](./js-apis-inner-commonEvent-commonEventData.md)> | Yes  | Callback used to return the result.|
 
+**Error codes**
+
+ For details about the error codes, see [Event Error Codes](../errorcodes/errorcode-CommonEventService.md).
+
+| ID| Error Message                           |
+| -------- | ----------------------------------- |
+| 401  | The parameter check failed.             |
+| 801  | capability not supported.               |
+| 1500007  | error sending message to Common Event Service. |
+| 1500008  | Common Event Service does not complete initialization. |
+
 **Example**
 
 ```ts
@@ -395,6 +425,17 @@ Unsubscribes from common events. This API uses an asynchronous callback to retur
 | subscriber | [CommonEventSubscriber](./js-apis-inner-commonEvent-commonEventSubscriber.md) | Yes  | Subscriber object.        |
 | callback   | AsyncCallback\<void>                            | No  | Callback used to return the result.|
 
+**Error codes**
+
+ For details about the error codes, see [Event Error Codes](../errorcodes/errorcode-CommonEventService.md).
+
+| ID| Error Message                           |
+| -------- | ----------------------------------- |
+| 401  | The parameter check failed.             |
+| 801  | capability not supported.               |
+| 1500007  | error sending message to Common Event Service. |
+| 1500008  | Common Event Service does not complete initialization. |
+
 **Example**
 
 ```ts
@@ -465,6 +506,19 @@ Obtains the result code of this common event. This API uses an asynchronous call
 | -------- | ---------------------- | ---- | ------------------ |
 | callback | AsyncCallback\<number> | Yes  | Callback used to return the result.|
 
+**Error codes**
+
+ For details about the error codes, see [Event Error Codes](../errorcodes/errorcode-CommonEventService.md).
+
+| ID| Error Message                           |
+| -------- | ----------------------------------- |
+| 201  | The application dose not have permission to call the interface. |
+| 202  | not system app.                         |
+| 401  | The parameter check failed.             |
+| 1500004  | not system service.                 |
+| 1500007  | The message send error.             |
+| 1500008  | The CEMS error.                     |
+
 **Example**
 
 ```ts
@@ -495,6 +549,19 @@ Obtains the result code of this common event. This API uses a promise to return
 | ---------------- | -------------------- |
 | Promise\<number> | Promise used to return the result.|
 
+**Error codes**
+
+ For details about the error codes, see [Event Error Codes](../errorcodes/errorcode-CommonEventService.md).
+
+| ID| Error Message                           |
+| -------- | ----------------------------------- |
+| 201  | The application dose not have permission to call the interface. |
+| 202  | not system app.                         |
+| 401  | The parameter check failed.             |
+| 1500004  | not system service.                 |
+| 1500007  | The message send error.             |
+| 1500008  | The CEMS error.                     |
+
 **Example**
 
 ```ts
diff --git a/en/application-dev/reference/apis/js-apis-deque.md b/en/application-dev/reference/apis/js-apis-deque.md
index 46d97bd96c27c9d3f05d519ebde6ff1ed8d3e4c5..7242e7dabbf12e7e44a98fa23bc44b9ead440a1e 100644
--- a/en/application-dev/reference/apis/js-apis-deque.md
+++ b/en/application-dev/reference/apis/js-apis-deque.md
@@ -156,9 +156,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let deque = new Deque();
-let result = deque.has("squirrel");
 deque.insertFront("squirrel");
-let result1 = deque.has("squirrel");
+let result = deque.has("squirrel");
 ```
 
 ### popFirst
diff --git a/en/application-dev/reference/apis/js-apis-fileAccess.md b/en/application-dev/reference/apis/js-apis-fileAccess.md
index da1aebc3030e41ff131cf44b496b01c1fff62d1f..f0bfc0da6eaea2f54a31a7a8b49a739c95d08a05 100644
--- a/en/application-dev/reference/apis/js-apis-fileAccess.md
+++ b/en/application-dev/reference/apis/js-apis-fileAccess.md
@@ -1,12 +1,11 @@
 # @ohos.file.fileAccess (User File Access and Management)
 
-The **fileAccess** module is a framework for accessing and operating user files based on the Extension ability mechanism. This module interacts with diverse file management services, such as the media library and external storage management service, and provides a set of file access and management APIs for system applications. The media library service allows access to user files on local devices and distributed devices. The external storage management service allows access to the user files stored on devices such as shared disks, USB flash drives, and SD cards.
+The **fileAccess** module provides a framework for accessing and operating user files based on the ExtensionAbility mechanism. This module interacts with file management services, such as the media library and external storage management service, and provides a set of unified interfaces for system applications to access and manage files. The media library service allows access to user files on local and distributed devices. The external storage management service allows access to the user files stored on devices, such as shared disks, USB flash drives, and SD cards.
 
 >**NOTE**
 >
->- The initial APIs of this module are supported since API version 9. Newly added APIs will be marked with a superscript to indicate their earliest API version.
->- The APIs provided by this module are system APIs and cannot be called by third-party applications. Currently, the APIs can be called only by **FilePicker** and **Files**.
->- The APIs of this module support processing of error codes. For details, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
+> - The initial APIs of this module are supported since API version 9. Newly added APIs will be marked with a superscript to indicate their earliest API version.
+> - The APIs provided by this module are system APIs and cannot be called by third-party applications. Currently, the APIs can be called only by **FilePicker** and **FileManager**.
 
 ## Modules to Import
 
@@ -16,9 +15,11 @@ import fileAccess from '@ohos.file.fileAccess';
 
 ## fileAccess.getFileAccessAbilityInfo
 
-getFileAccessAbilityInfo( ) : Promise&lt;Array&lt;Want&gt;&gt;
+getFileAccessAbilityInfo() : Promise&lt;Array&lt;Want&gt;&gt;
 
-Obtains information about all wants with **extension** set to **fileAccess** in the system. A want is a basic communication component used to start services. This API uses a promise to return the result.
+Obtains information about all Wants with **extension** set to **fileAccess** in the system. A Want contains information for starting an ability. This API uses a promise to return the result.
+
+**Model restriction**: This API can be used only in the stage model.
 
 **System capability**: SystemCapability.FileManagement.UserFileService
 
@@ -26,9 +27,13 @@ Obtains information about all wants with **extension** set to **fileAccess** in
 
 **Return value**
 
-| Type| Description|
-| --- | -- |
-| Promise&lt;Array&lt;Want&gt;&gt; | Promise used to return the **want** information obtained.|
+  | Type| Description|
+  | --- | -- |
+  | Promise&lt;Array&lt;[Want](js-apis-app-ability-want.md)&gt;&gt; | Promise used to return the Want information obtained.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -46,9 +51,11 @@ Obtains information about all wants with **extension** set to **fileAccess** in
 
 ## fileAccess.getFileAccessAbilityInfo
 
-getFileAccessAbilityInfo(callback: AsyncCallback&lt;Array&lt;Want&gt;&gt;): void;
+getFileAccessAbilityInfo(callback: AsyncCallback&lt;Array&lt;Want&gt;&gt;): void
+
+Obtains information about all Wants with **extension** set to **fileAccess** in the system. A Want contains information for starting an ability. This API uses an asynchronous callback to return the result.
 
-Obtains information about all wants with **extension** set to **fileAccess** in the system. A want is a basic communication component used to start services. This API uses an asynchronous callback to return the result.
+**Model restriction**: This API can be used only in the stage model.
 
 **System capability**: SystemCapability.FileManagement.UserFileService
 
@@ -56,9 +63,13 @@ Obtains information about all wants with **extension** set to **fileAccess** in
 
 **Parameters**
 
-| Name| Type| Mandatory| Description|
-| --- | --- | --- | -- |
-| callback | AsyncCallback&lt;Array&lt;Want&gt;&gt; | Yes| Promise used to return the **want** information obtained.|
+  | Name| Type| Mandatory| Description|
+  | --- | --- | --- | -- |
+  | callback | AsyncCallback&lt;Array&lt;[Want](js-apis-app-ability-want.md)&gt;&gt; | Yes| Promise used to return the Want information obtained.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -84,22 +95,28 @@ createFileAccessHelper(context: Context, wants: Array&lt;Want&gt;) : FileAccessH
 
 Synchronously creates a **Helper** object to connect to the specified wants. The **Helper** object provides file access and management capabilities.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER and ohos.permission.GET_BUNDLE_INFO_PRIVILEGED
 
 **Parameters**
 
-| Name| Type| Mandatory| Description|
-| --- | --- | --- | -- |
-| context | Context | Yes| Context of the ability.|
-| wants | Array&lt;Want&gt; | Yes| Wants to connect.|
+  | Name| Type| Mandatory| Description|
+  | --- | --- | --- | -- |
+  | context | [Context](js-apis-inner-application-context.md) | Yes| Context of the ability.|
+  | wants | Array&lt;[Want](js-apis-app-ability-want.md)&gt; | Yes| Wants to connect.|
 
 **Return value**
 
-| Type| Description|
-| --- | -- |
-| FileAccessHelper | **Helper** object created.|
+  | Type| Description|
+  | --- | -- |
+  | [FileAccessHelper](#fileaccesshelper) | **Helper** object created.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -131,21 +148,27 @@ createFileAccessHelper(context: Context) : FileAccessHelper
 
 Synchronously creates a **Helper** object to connect to all file management services in the system.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER and ohos.permission.GET_BUNDLE_INFO_PRIVILEGED
 
 **Parameters**
 
-| Name| Type| Mandatory| Description|
-| --- | --- | --- | -- |
-| context | Context | Yes| Context of the ability.|
+  | Name| Type| Mandatory| Description|
+  | --- | --- | --- | -- |
+  | context | [Context](js-apis-inner-application-context.md) | Yes| Context of the ability.|
 
 **Return value**
 
-| Type| Description|
-| --- | -- |
-| FileAccessHelper | **Helper** object created.|
+  | Type| Description|
+  | --- | -- |
+  | [FileAccessHelper](#fileaccesshelper) | **Helper** object created.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -164,56 +187,90 @@ Synchronously creates a **Helper** object to connect to all file management serv
   }
   ```
 
-## FileAccessHelper.getRoots
+## FileInfo
+
+Provides the file or directory attribute information and APIs.
+
+**Model restriction**: This API can be used only in the stage model.
+
+**System capability**: SystemCapability.FileManagement.UserFileService
 
-getRoots( ) : Promise&lt;RootIterator&gt;
+**Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
+
+### Attributes
 
-Obtains information about the device root nodes of the file management service type connected to the **Helper** object. This API uses a promise to return a **RootIterator** object, which returns [RootInfo](#rootinfo) by using [next()](#rootiteratornext).
+| Name| Type  | Readable| Writable| Description    |
+| ------ | ------ | -------- | ------ | -------- |
+| uri | string | Yes| No| URI of the file or directory.|
+| fileName | string | Yes| No| Name of the file or directory.|
+| mode | number | Yes| No| Permissions on the file or directory.|
+| size | number | Yes| No|  Size of the file or directory.|
+| mtime | number | Yes| No|  Time when the file or directory was last modified.|
+| mimeType | string | Yes| No|  Multipurpose Internet Mail Extensions (MIME) type of the file or directory.|
+
+### listFile
+
+listFile(filter?: Filter) : FileIterator
+
+Synchronously obtains a **FileIterator** object that lists the next-level files (directories) matching the conditions of the filter from a directory and returns [FileInfo](#fileinfo) using [next()](#next). Currently, only built-in storage devices support the file filter.
+
+**Model restriction**: This API can be used only in the stage model.
 
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
 
+**Parameters**
+
+  | Name| Type| Mandatory| Description|
+  | --- | --- | -- | -- |
+  | filter | [Filter](js-apis-file-fs.md#filter) | No| **Filter** object. |
+
 **Return value**
 
-| Type| Description|
-| --- | -- |
-| Promise&lt;RootIterator&gt; | Promise used to return the **RootIterator** object obtained.|
+  | Type| Description|
+  | --- | -- |
+  | [FileIterator](#fileiterator) | **FileIterator** object obtained.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
   ```js
-  async getRoots() {
-    let rootIterator = null;
-    let rootinfos = [];
-    let isDone = false;
-    try {
-      // Obtain fileAccessHelper by referring to the sample code of fileAccess.createFileAccessHelper.
-      rootIterator = await fileAccessHelper.getRoots();
-      if (!rootIterator) {
-        console.error("getRoots interface returns an undefined object");
-        return;
-      }
-      while (!isDone) {
-        let result = rootIterator.next();
-        console.log("next result = " + JSON.stringify(result));
-        isDone = result.done;
-        if (!isDone)
-          rootinfos.push(result.value);
-      }
-    } catch (error) {
-      console.error("getRoots failed, errCode:" + error.code + ", errMessage:" + error.message);
+  // fileInfoDir indicates information about a directory.
+  // let filter = { suffix : [".txt", ".jpg", ".xlsx"] };
+  let fileInfoDir = fileInfos[0];
+  let subfileInfos = [];
+  let isDone = false;
+  try {
+    let fileIterator = fileInfoDir.listFile();
+    // listFile() with the filter implementation.
+    // let fileIterator = rootInfo.listFile(filter);
+    if (!fileIterator) {
+      console.error("listFile interface returns an undefined object");
+      return;
     }
+    while (!isDone) {
+      let result = fileIterator.next();
+      console.log("next result = " + JSON.stringify(result));
+      isDone = result.done;
+      if (!isDone)
+        subfileInfos.push(result.value);
+    }
+  } catch (error) {
+    console.error("listFile failed, errCode:" + error.code + ", errMessage:" + error.message);
   }
   ```
 
-## FileAccessHelper.getRoots
+### scanFile
 
-getRoots(callback:AsyncCallback&lt;RootIterator&gt;) : void;
+scanFile(filter?: Filter) : FileIterator
 
-Obtains information about the device root nodes of the file management service type connected to the **Helper** object. This API uses an asynchronous callback to return the result.
+Synchronously obtains a **FileIterator** object that recursively retrieves the files matching the conditions of the filter from a directory and returns [FileInfo](#fileinfo) using [next()](#next). Currently, this API supports only built-in storage devices.
 
-The callback has a **RootIterator** object, which returns [RootInfo](#rootinfo) through [next()](#rootiteratornext).
+**Model restriction**: This API can be used only in the stage model.
 
 **System capability**: SystemCapability.FileManagement.UserFileService
 
@@ -221,59 +278,126 @@ The callback has a **RootIterator** object, which returns [RootInfo](#rootinfo)
 
 **Parameters**
 
-| Name| Type| Mandatory| Description|
-| --- | --- | --- | -- |
-| callback | AsyncCallback&lt;RootIterator&gt; | Yes| Promise used to return the **RootIterator** object obtained.|
+  | Name| Type| Mandatory| Description|
+  | --- | --- | -- | -- |
+  | filter | [Filter](js-apis-file-fs.md#filter) | No| **Filter** object. |
+
+**Return value**
+
+  | Type| Description|
+  | --- | -- |
+  | [FileIterator](#fileiterator) | **FileIterator** object obtained.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
   ```js
-  async getRoots() {
-    let rootinfos = [];
-    let isDone = false;
-    try {
-      // Obtain fileAccessHelper by referring to the sample code of fileAccess.createFileAccessHelper.
-      fileAccessHelper.getRoots(function (err, rootIterator) {
-        if (err) {
-          console.error("Failed to getRoots in async, errCode:" + err.code + ", errMessage:" + err.message);
-          return;
-        }
-        while (!isDone) {
-          let result = rootIterator.next();
-          console.log("next result = " + JSON.stringify(result));
-          isDone = result.done;
-          if (!isDone)
-            rootinfos.push(result.value);
-        }
-      });
-    } catch (error) {
-      console.error("getRoots failed, errCode:" + error.code + ", errMessage:" + error.message);
+  // fileInfoDir indicates information about a directory.
+  // let filter = {suffix : [".txt", ".jpg", ".xlsx"]};
+  let fileInfoDir = fileInfos[0];
+  let subfileInfos = [];
+  let isDone = false;
+  try {
+    let fileIterator = fileInfoDir.scanFile();
+    // scanFile() with the filter implementation.
+    // let fileIterator = rootInfo.scanFile(filter);
+    if (!fileIterator) {
+      console.error("scanFile interface returns an undefined object");
+      return;
     }
+    while (!isDone) {
+      let result = fileIterator.next();
+      console.log("next result = " + JSON.stringify(result));
+      isDone = result.done;
+      if (!isDone)
+        subfileInfos.push(result.value);
+    }
+  } catch (error) {
+    console.error("scanFile failed, errCode:" + error.code + ", errMessage:" + error.message);
   }
   ```
 
-## RootInfo.listfile
+## FileIterator
 
-listFile(filter?: Filter) : FileIterator
+Provides the **FileIterator** object.
 
-Synchronously obtains the **FileIterator** object of the first-level files (directory) matching the conditions of the filter from the device root node. The **FileIterator** object then returns [FileInfo](#fileinfo) by using [next()](#fileiteratornext).
+**Model restriction**: This API can be used only in the stage model.
 
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
 
-**Parameters**
+### next
 
-| Name| Type| Mandatory| Description|
-| --- | --- | -- | -- |
-| filter | Filter | No| **Filter** object. |
+next() : { value: FileInfo, done: boolean }
+
+Obtains information about the next-level files or directories.
+
+**Model restriction**: This API can be used only in the stage model.
 
+**System capability**: SystemCapability.FileManagement.UserFileService
+
+**Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
 
 **Return value**
 
 | Type| Description|
 | --- | -- |
-| FileIterator | **FileIterator** object obtained.|
+| {value: [FileInfo](#fileinfo), done: boolean} | File or directory information obtained. This method traverses the specified directory until **true** is returned. The **value** field contains the file or directory information obtained.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
+
+## RootInfo
+
+Provides the device's root attribute information and APIs.
+
+**Model restriction**: This API can be used only in the stage model.
+
+**System capability**: SystemCapability.FileManagement.UserFileService
+
+**Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
+
+### Attributes
+
+| Name| Type  | Readable| Writable| Description    |
+| ------ | ------ | -------- | ------ | -------- |
+| deviceType | number | Yes| No|Type of the device.|
+| uri | string | Yes| No| Root directory URI of the device.|
+| displayName | string | Yes| No| Device name.|
+| deviceFlags | number | Yes| No| Capabilities supported by the device.|
+
+### listFile
+
+listFile(filter?: Filter) : FileIterator
+
+Synchronously obtains a **FileIterator** object that lists the first-level files (directories) matching the conditions of the filter from the device root directory and returns [FileInfo](#fileinfo) using [next()](#next). Currently, only built-in storage devices support the file filter.
+
+**Model restriction**: This API can be used only in the stage model.
+
+**System capability**: SystemCapability.FileManagement.UserFileService
+
+**Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
+
+**Parameters**
+
+  | Name| Type| Mandatory| Description|
+  | --- | --- | -- | -- |
+  | filter | [Filter](js-apis-file-fs.md#filter) | No| **Filter** object. |
+
+**Return value**
+
+  | Type| Description|
+  | --- | -- |
+  | [FileIterator](#fileiterator) | **FileIterator** object obtained.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -285,7 +409,7 @@ Synchronously obtains the **FileIterator** object of the first-level files (dire
   let isDone = false;
   try {
     let fileIterator = rootInfo.listFile();
-    // listFile contains the filter implementation.
+    // listFile() with the filter implementation.
     // let fileIterator = rootInfo.listFile(filter);
     if (!fileIterator) {
       console.error("listFile interface returns an undefined object");
@@ -303,11 +427,13 @@ Synchronously obtains the **FileIterator** object of the first-level files (dire
   }
   ```
 
-## RootInfo.scanFile
+### scanFile
 
 scanFile(filter?: Filter) : FileIterator
 
-Recursively obtains the **FileIterator** object of the files matching the conditions of the filter from the device root node synchronously. The **FileIterator** object then returns [FileInfo](#fileinfo) by using [next()](#fileiteratornext).
+Synchronously obtains a **FileIterator** object that recursively retrieves the files matching the conditions of the filter from the device root directory and returns [FileInfo](#fileinfo)using [next()](#next). Currently, this API supports only built-in storage devices.
+
+**Model restriction**: This API can be used only in the stage model.
 
 **System capability**: SystemCapability.FileManagement.UserFileService
 
@@ -315,15 +441,19 @@ Recursively obtains the **FileIterator** object of the files matching the condit
 
 **Parameters**
 
-| Name| Type| Mandatory| Description|
-| --- | --- | -- | -- |
-| filter | Filter | No| **Filter** object. |
+  | Name| Type| Mandatory| Description|
+  | --- | --- | -- | -- |
+  | filter | [Filter](js-apis-file-fs.md#filter) | No| **Filter** object. |
 
 **Return value**
 
-| Type| Description|
-| --- | -- |
-| FileIterator | **FileIterator** object obtained.|
+  | Type| Description|
+  | --- | -- |
+  | [FileIterator](#fileiterator) | **FileIterator** object obtained.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -335,7 +465,7 @@ Recursively obtains the **FileIterator** object of the files matching the condit
   let isDone = false;
   try {
     let fileIterator = rootInfo.scanFile();
-    // scanFile contains the filter implementation.
+    // scanFile with the filter implementation.
     // let fileIterator = rootInfo.scanFile(filter);
     if (!fileIterator) {
       console.error("scanFile interface returns undefined object");
@@ -353,61 +483,106 @@ Recursively obtains the **FileIterator** object of the files matching the condit
   }
   ```
 
-## FileInfo.listfile
+## RootIterator
 
-listFile(filter?: Filter) : FileIterator
+Provides an iterator object of the device root directory.
 
-Synchronously obtains the **FileIterator** object of the next-level files (directories) matching the conditions of the filter from a directory. The **FileIterator** object then returns [FileInfo](#fileinfo) by using [next()](#fileiteratornext).
+**Model restriction**: This API can be used only in the stage model.
 
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
 
-**Parameters**
+### next
 
-| Name| Type| Mandatory| Description|
-| --- | --- | -- | -- |
-| filter | Filter | No| **Filter** object. |
+next() : { value: RootInfo, done: boolean }
+
+Obtains the root directory of the next-level device.
+
+**Model restriction**: This API can be used only in the stage model.
+
+**System capability**: SystemCapability.FileManagement.UserFileService
+
+**Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
 
 **Return value**
 
 | Type| Description|
 | --- | -- |
-| FileIterator | **FileIterator** object obtained.|
+| {value: [RootInfo](#rootinfo), done: boolean} | Root directory information obtained. This method traverses the directory until **true** is returned. The **value** field contains the root directory information.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
+
+## FileAccessHelper
+
+Provides a **FileAccessHelper** object.
+
+**Model restriction**: This API can be used only in the stage model.
+
+**System capability**: SystemCapability.FileManagement.UserFileService
+
+**Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
+
+### getRoots
+
+getRoots() : Promise&lt;RootIterator&gt;
+
+Obtains information about the device root nodes of the file management service connected to the **Helper** object. This API uses a promise to return a **RootIterator** object,
+which returns [RootInfo](#rootinfo) by using [next](#next-1).
+
+**Model restriction**: This API can be used only in the stage model.
+
+**System capability**: SystemCapability.FileManagement.UserFileService
+
+**Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
+
+**Return value**
+
+| Type| Description|
+| --- | -- |
+| Promise&lt;[RootIterator](#rootiterator)&gt; | Promise used to return the **RootIterator** object obtained.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
   ```js
-  // fileInfoDir specifies the target directory.
-  // let filter = { suffix : [".txt", ".jpg", ".xlsx"] };
-  let fileInfoDir = fileInfos[0];
-  let subfileInfos = [];
-  let isDone = false;
-  try {
-    let fileIterator = fileInfoDir.listFile();
-    // listFile contains the filter implementation.
-    // let fileIterator = rootInfo.listFile(filter);
-    if (!fileIterator) {
-      console.error("listFile interface returns an undefined object");
-      return;
-    }
-    while (!isDone) {
-      let result = fileIterator.next();
-      console.log("next result = " + JSON.stringify(result));
-      isDone = result.done;
-      if (!isDone)
-        subfileInfos.push(result.value);
+  async getRoots() {
+    let rootIterator = null;
+    let rootinfos = [];
+    let isDone = false;
+    try {
+      // Obtain fileAccessHelper by referring to the sample code of fileAccess.createFileAccessHelper.
+      rootIterator = await fileAccessHelper.getRoots();
+      if (!rootIterator) {
+        console.error("getRoots interface returns an undefined object");
+        return;
+      }
+      while (!isDone) {
+        let result = rootIterator.next();
+        console.log("next result = " + JSON.stringify(result));
+        isDone = result.done;
+        if (!isDone)
+          rootinfos.push(result.value);
+      }
+    } catch (error) {
+      console.error("getRoots failed, errCode:" + error.code + ", errMessage:" + error.message);
     }
-  } catch (error) {
-    console.error("listFile failed, errCode:" + error.code + ", errMessage:" + error.message);
   }
   ```
 
-## FileInfo.scanfile
+### getRoots
 
-scanFile(filter?: Filter) : FileIterator;
+getRoots(callback:AsyncCallback&lt;RootIterator&gt;) : void
 
-Recursively obtains the **FileIterator** object of the files matching the conditions of the filter from a directory synchronously. The **FileIterator** object then returns [FileInfo](#fileinfo) by using [next()](#fileiteratornext).
+Obtains information about the device root nodes of the file management service connected to the **Helper** object. This API uses an asynchronous callback to return a **RootIterator** object,
+which returns [RootInfo](#rootinfo) by using [next](#next-1).
+
+**Model restriction**: This API can be used only in the stage model.
 
 **System capability**: SystemCapability.FileManagement.UserFileService
 
@@ -416,50 +591,48 @@ Recursively obtains the **FileIterator** object of the files matching the condit
 **Parameters**
 
 | Name| Type| Mandatory| Description|
-| --- | --- | -- | -- |
-| filter | Filter | No| **Filter** object. |
-
+| --- | --- | --- | -- |
+| callback | AsyncCallback&lt;[RootIterator](#rootiterator)&gt; | Yes| Callback invoked to return the **RootIterator** object obtained.|
 
-**Return value**
+**Error codes**
 
-| Type| Description|
-| --- | -- |
-| FileIterator | **FileIterator** object obtained.|
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
   ```js
-  // fileInfoDir specifies the target directory.
-  // let filter = {suffix : [".txt", ".jpg", ".xlsx"]};
-  let fileInfoDir = fileInfos[0];
-  let subfileInfos = [];
-  let isDone = false;
-  try {
-    let fileIterator = fileInfoDir.scanFile();
-    // scanFile contains the filter implementation.
-    // let fileIterator = rootInfo.scanFile(filter);
-    if (!fileIterator) {
-      console.error("scanFile interface returns an undefined object");
-      return;
-    }
-    while (!isDone) {
-      let result = fileIterator.next();
-      console.log("next result = " + JSON.stringify(result));
-      isDone = result.done;
-      if (!isDone)
-        subfileInfos.push(result.value);
+  async getRoots() {
+    let rootinfos = [];
+    let isDone = false;
+    try {
+      // Obtain fileAccessHelper by referring to the sample code of fileAccess.createFileAccessHelper.
+      fileAccessHelper.getRoots(function (err, rootIterator) {
+        if (err) {
+          console.error("Failed to getRoots in async, errCode:" + err.code + ", errMessage:" + err.message);
+          return;
+        }
+        while (!isDone) {
+          let result = rootIterator.next();
+          console.log("next result = " + JSON.stringify(result));
+          isDone = result.done;
+          if (!isDone)
+            rootinfos.push(result.value);
+        }
+      });
+    } catch (error) {
+      console.error("getRoots failed, errCode:" + error.code + ", errMessage:" + error.message);
     }
-  } catch (error) {
-    console.error("scanFile failed, errCode:" + error.code + ", errMessage:" + error.message);
   }
   ```
 
-## FileAccessHelper.createFile
+### createFile
 
 createFile(uri: string, displayName: string) : Promise&lt;string&gt;
 
 Creates a file in a directory. This API uses a promise to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -468,7 +641,7 @@ Creates a file in a directory. This API uses a promise to return the result.
 
 | Name| Type| Mandatory| Description|
 | --- | --- | --- | -- |
-| uri | string | Yes| URI of the parent directory for the file to create.|
+| uri | string | Yes| URI of the destination directory for the file to create.|
 | displayName | string | Yes| Name of the file to create. By default, the name of a local file must contain the file name extension.|
 
 **Return value**
@@ -477,6 +650,10 @@ Creates a file in a directory. This API uses a promise to return the result.
 | --- | -- |
 | Promise&lt;string&gt; | Promise used to return the URI of the file created.|
 
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
+
 **Example**
 
   ```js
@@ -499,12 +676,14 @@ Creates a file in a directory. This API uses a promise to return the result.
   };
   ```
 
-## FileAccessHelper.createFile
+### createFile
 
-createFile(uri: string, displayName: string, callback: AsyncCallback&lt;string&gt;) : void;
+createFile(uri: string, displayName: string, callback: AsyncCallback&lt;string&gt;) : void
 
 Creates a file in a directory. This API uses an asynchronous callback to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -513,9 +692,13 @@ Creates a file in a directory. This API uses an asynchronous callback to return
 
 | Name| Type| Mandatory| Description|
 | --- | --- | --- | -- |
-| uri | string | Yes| URI of the parent directory for the file to create.|
+| uri | string | Yes| URI of the destination directory for the file to create.|
 | displayName | string | Yes| Name of the file to create. By default, the name of a local file must contain the file name extension.|
-| callback | AsyncCallback&lt;string&gt; | Yes| Promise used to return the URI of the file created.|
+| callback | AsyncCallback&lt;string&gt; | Yes| Callback invoked to return the URI of the file created.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -539,12 +722,14 @@ Creates a file in a directory. This API uses an asynchronous callback to return
   };
   ```
 
-## FileAccessHelper.mkDir
+### mkDir
 
 mkDir(parentUri: string, displayName: string) : Promise&lt;string&gt;
 
 Creates a directory. This API uses a promise to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -553,7 +738,7 @@ Creates a directory. This API uses a promise to return the result.
 
 | Name| Type| Mandatory| Description|
 | --- | --- | --- | -- |
-| parentUri | string | Yes| URI of the parent directory for the directory to create.|
+| parentUri | string | Yes| URI of the destination directory for the directory to create.|
 | displayName | string | Yes| Name of the directory to create.|
 
 **Return value**
@@ -562,6 +747,10 @@ Creates a directory. This API uses a promise to return the result.
 | --- | -- |
 | Promise&lt;string&gt; | Promise used to return the URI of the directory created.|
 
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
+
 **Example**
 
   ```js
@@ -584,12 +773,14 @@ Creates a directory. This API uses a promise to return the result.
   };
   ```
 
-## FileAccessHelper.mkDir
+### mkDir
 
-mkDir(parentUri: string, displayName: string, callback: AsyncCallback&lt;string&gt;) : void;
+mkDir(parentUri: string, displayName: string, callback: AsyncCallback&lt;string&gt;) : void
 
 Creates a directory. This API uses an asynchronous callback to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -598,9 +789,13 @@ Creates a directory. This API uses an asynchronous callback to return the result
 
 | Name| Type| Mandatory| Description|
 | --- | --- | --- | -- |
-| parentUri | string | Yes| URI of the parent directory for the directory to create.|
+| parentUri | string | Yes| URI of the destination directory for the directory to create.|
 | displayName | string | Yes| Name of the directory to create.|
-| callback | AsyncCallback&lt;string&gt; | Yes| Promise used to return the URI of the directory created.|
+| callback | AsyncCallback&lt;string&gt; | Yes| Callback invoked to return the URI of the directory created.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -624,12 +819,14 @@ Creates a directory. This API uses an asynchronous callback to return the result
   };
   ```
 
-## FileAccessHelper.openFile
+### openFile
 
 openFile(uri: string, flags: OPENFLAGS) : Promise&lt;number&gt;
 
 Opens a file. This API uses a promise to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -645,7 +842,11 @@ Opens a file. This API uses a promise to return the result.
 
 | Type| Description|
 | --- | -- |
-| Promise&lt;number&gt; | Promise used to return the file descriptor of the file opened.|
+| Promise&lt;number&gt; | Promise used to return the file descriptor (FD) of the file opened.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -662,12 +863,14 @@ Opens a file. This API uses a promise to return the result.
   };
   ```
 
-## FileAccessHelper.openFile
+### openFile
 
-openFile(uri: string, flags: OPENFLAGS, callback: AsyncCallback&lt;number&gt;) : void;
+openFile(uri: string, flags: OPENFLAGS, callback: AsyncCallback&lt;number&gt;) : void
 
 Opens a file. This API uses an asynchronous callback to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -678,7 +881,11 @@ Opens a file. This API uses an asynchronous callback to return the result.
 | --- | --- | --- | -- |
 | uri | string | Yes| URI of the file to open.|
 | flags | [OPENFLAGS](#openflags) | Yes| File open mode.|
-| callback | AsyncCallback&lt;number&gt; | Yes| Callback invoked to return the file descriptor of the file opened.|
+| callback | AsyncCallback&lt;number&gt; | Yes| Callback invoked to return the FD of the file opened.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -701,12 +908,14 @@ Opens a file. This API uses an asynchronous callback to return the result.
   };
   ```
 
-## FileAccessHelper.delete
+### delete
 
 delete(uri: string) : Promise&lt;number&gt;
 
 Deletes a file or directory. This API uses a promise to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -723,6 +932,10 @@ Deletes a file or directory. This API uses a promise to return the result.
 | --- | -- |
 | Promise&lt;number&gt | Promise used to return the result.|
 
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
+
 **Example**
 
   ```js
@@ -740,12 +953,14 @@ Deletes a file or directory. This API uses a promise to return the result.
   };
   ```
 
-## FileAccessHelper.delete
+### delete
 
-delete(uri: string, callback: AsyncCallback&lt;number&gt;) : void;
+delete(uri: string, callback: AsyncCallback&lt;number&gt;) : void
 
 Deletes a file or directory. This API uses an asynchronous callback to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -755,7 +970,11 @@ Deletes a file or directory. This API uses an asynchronous callback to return th
 | Name| Type| Mandatory| Description|
 | --- | --- | --- | -- |
 | uri | string | Yes| URI of the file or directory to delete.|
-| callback | AsyncCallback&lt;number&gt; | Yes| Promise used to return the result.|
+| callback | AsyncCallback&lt;number&gt; | Yes| Callback invoked to return the result.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -778,11 +997,13 @@ Deletes a file or directory. This API uses an asynchronous callback to return th
   };
   ```
 
-## FileAccessHelper.move
+### move
 
 move(sourceFile: string, destFile: string) : Promise&lt;string&gt;
 
-Moves a file or directory. This API uses a promise to return the result.
+Moves a file or directory. This API uses a promise to return the result. Currently, this API does not support move of files or directories across devices.
+
+**Model restriction**: This API can be used only in the stage model.
 
 **System capability**: SystemCapability.FileManagement.UserFileService
 
@@ -793,7 +1014,7 @@ Moves a file or directory. This API uses a promise to return the result.
 | Name| Type| Mandatory| Description|
 | --- | --- | --- | -- |
 | sourceFile | string | Yes| URI of the file or directory to move.|
-| destFile | string | Yes| URI of the directory, to which the file or directory will be moved.|
+| destFile | string | Yes| URI of the destination directory, to which the file or directory will be moved.|
 
 **Return value**
 
@@ -801,6 +1022,10 @@ Moves a file or directory. This API uses a promise to return the result.
 | ----- | ------ |
 | Promise&lt;string&gt; | Promise used to return the URI of the file or directory in the destination directory.|
 
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
+
 **Example**
 
   ```js
@@ -818,11 +1043,13 @@ Moves a file or directory. This API uses a promise to return the result.
   };
   ```
 
-## FileAccessHelper.move
+### move
 
-move(sourceFile: string, destFile: string, callback: AsyncCallback&lt;string&gt;) : void;
+move(sourceFile: string, destFile: string, callback: AsyncCallback&lt;string&gt;) : void
 
-Moves a file or directory. This API uses an asynchronous callback to return the result.
+Moves a file or directory. This API uses an asynchronous callback to return the result. Currently, this API does not support move of files or directories across devices.
+
+**Model restriction**: This API can be used only in the stage model.
 
 **System capability**: SystemCapability.FileManagement.UserFileService
 
@@ -833,8 +1060,12 @@ Moves a file or directory. This API uses an asynchronous callback to return the
 | Name| Type| Mandatory| Description|
 | --- | --- | --- | -- |
 | sourceFile | string | Yes| URI of the file or directory to move.|
-| destFile | string | Yes| URI of the  directory, to which the file or  directory will be moved.|
-| callback | AsyncCallback&lt;string&gt; | Yes| Promise used to return the URI of the file or directory in the destination directory.|
+| destFile | string | Yes| URI of the destination directory, to which the file or directory will be moved.|
+| callback | AsyncCallback&lt;string&gt; | Yes| Callback invoked to return the URI of the file or directory in the destination directory.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -858,12 +1089,14 @@ Moves a file or directory. This API uses an asynchronous callback to return the
   };
   ```
 
-## FileAccessHelper.rename
+### rename
 
 rename(uri: string, displayName: string) : Promise&lt;string&gt;
 
 Renames a file or directory. This API uses a promise to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -881,6 +1114,10 @@ Renames a file or directory. This API uses a promise to return the result.
 | --- | -- |
 | Promise&lt;string&gt; | Promise used to return the URI of the renamed file or directory.|
 
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
+
 **Example**
 
   ```js
@@ -897,12 +1134,14 @@ Renames a file or directory. This API uses a promise to return the result.
   };
   ```
 
-## FileAccessHelper.rename
+### rename
 
-rename(uri: string, displayName: string, callback: AsyncCallback&lt;string&gt;) : void;
+rename(uri: string, displayName: string, callback: AsyncCallback&lt;string&gt;) : void
 
 Renames a file or directory. This API uses an asynchronous callback to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -913,7 +1152,11 @@ Renames a file or directory. This API uses an asynchronous callback to return th
 | --- | --- | --- | -- |
 | uri | string | Yes| URI of the file or directory to rename.|
 | displayName | string | Yes| New name of the file or directory, which can contain the file name extension.|
-| callback | AsyncCallback&lt;string&gt; | Yes| Promise used to return the URI of the renamed file or directory.|
+| callback | AsyncCallback&lt;string&gt; | Yes| Callback invoked to return the URI of the renamed file or directory.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -936,12 +1179,14 @@ Renames a file or directory. This API uses an asynchronous callback to return th
   };
   ```
 
-## FileAccessHelper.access
+### access
 
 access(sourceFileUri: string) : Promise&lt;boolean&gt;
 
 Checks whether a file or directory exists. This API uses a promise to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -958,6 +1203,10 @@ Checks whether a file or directory exists. This API uses a promise to return the
 | --- | -- |
 | Promise&lt;boolean&gt; | Promise used to return the result.|
 
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
+
 **Example**
 
   ```js
@@ -977,12 +1226,14 @@ Checks whether a file or directory exists. This API uses a promise to return the
   };
   ```
 
-## FileAccessHelper.access
+### access
 
-access(sourceFileUri: string, callback: AsyncCallback&lt;boolean&gt;) : void;
+access(sourceFileUri: string, callback: AsyncCallback&lt;boolean&gt;) : void
 
 Checks whether a file or directory exists. This API uses an asynchronous callback to return the result.
 
+**Model restriction**: This API can be used only in the stage model.
+
 **System capability**: SystemCapability.FileManagement.UserFileService
 
 **Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
@@ -992,7 +1243,11 @@ Checks whether a file or directory exists. This API uses an asynchronous callbac
 | Name| Type| Mandatory| Description|
 | --- | --- | --- | -- |
 | sourceFileUri | string | Yes| URI of the file or directory.|
-| callback | AsyncCallback&lt;boolean&gt; | Yes| Promise used to return the result.|
+| callback | AsyncCallback&lt;boolean&gt; | Yes| Callback invoked to return the result.|
+
+**Error codes**
+
+For details about error codes, see [File Management Error Codes](../errorcodes/errorcode-filemanagement.md).
 
 **Example**
 
@@ -1018,74 +1273,6 @@ Checks whether a file or directory exists. This API uses an asynchronous callbac
   };
   ```
 
-## RootIterator.next
-
-next( ) : { value: RootInfo, done: boolean }
-
-Obtains the next-level device root directory. **RootIterator** is an iterator object of the device root directory.
-
-**System capability**: SystemCapability.FileManagement.UserFileService
-
-**Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
-
-**Return value**
-
-| Type| Description|
-| --- | -- |
-| {value: RootInfo, done: boolean} | Root directory information obtained. This API traverses the directory until **done** returns **true**. The **value** field contains the root directory information.|
-
-## FileIterator.next
-
-next( ) : { value: FileInfo, done: boolean }
-
-Obtains the information about the next-level file or directory. **FileIterator** is an iterator object of a directory.
-
-**System capability**: SystemCapability.FileManagement.UserFileService
-
-**Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
-
-**Return value**
-
-| Type| Description|
-| --- | -- |
-| {value: FileInfo, done: boolean} | File or directory information obtained. This API traverses the specified directory until **done** returns **true**. The **value** field contains the file or directory information obtained.|
-
-## RootInfo
-
-Represents the root attribute information and interface capabilities of a device.
-
-**System capability**: SystemCapability.FileManagement.UserFileService
-
-**Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
-
-### Attributes
-
-| Name| Type  | Readable| Writable| Description    |
-| ------ | ------ | -------- | ------ | -------- |
-| deviceType | number | Yes| No|Device type.|
-| uri | string | Yes| No| Root directory URI of the device.|
-| displayName | string | Yes| No| Device name.|
-| deviceFlags | number | Yes| No| Capabilities supported by the device.|
-
-## FileInfo
-
-Represents the file or directory attribute information and interface capabilities.
-
-**System capability**: SystemCapability.FileManagement.UserFileService
-
-**Required permissions**: ohos.permission.FILE_ACCESS_MANAGER
-
-### Attributes
-
-| Name| Type  | Readable| Writable| Description    |
-| ------ | ------ | -------- | ------ | -------- |
-| uri | string | Yes| No| URI of the file or directory.|
-| fileName | string | Yes| No| Name of a file or directory.|
-| mode | number | Yes| No| Permissions on the file or directory.|
-| size | number | Yes| No|  Size of the file or directory.|
-| mtime | number | Yes| No|  Time when the file or directory was last modified.|
-| mimeType | string | Yes| No|  MIME type of the file or directory.|
-
 ## OPENFLAGS
 
 Enumerates the modes for opening a file.
diff --git a/en/application-dev/reference/apis/js-apis-hashmap.md b/en/application-dev/reference/apis/js-apis-hashmap.md
index 807394ad4538e34997ac5b5eb917e47aad295161..c880644673fd9a8cd9d15ac05ec01afc9785bf3e 100644
--- a/en/application-dev/reference/apis/js-apis-hashmap.md
+++ b/en/application-dev/reference/apis/js-apis-hashmap.md
@@ -119,9 +119,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let hashMap = new HashMap();
-let result = hashMap.hasKey("squirrel");
 hashMap.set("squirrel", 123);
-let result1 = hashMap.hasKey("squirrel");
+let result = hashMap.hasKey("squirrel");
 ```
 
 
@@ -157,9 +156,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let hashMap = new HashMap();
-let result = hashMap.hasValue(123);
 hashMap.set("squirrel", 123);
-let result1 = hashMap.hasValue(123);
+let result = hashMap.hasValue(123);
 ```
 
 
@@ -230,6 +228,7 @@ let hashMap = new HashMap();
 hashMap.set("squirrel", 123);
 hashMap.set("sparrow", 356);
 let newHashMap = new HashMap();
+newHashMap.set("newMap", 99);
 hashMap.setAll(newHashMap);
 ```
 
diff --git a/en/application-dev/reference/apis/js-apis-hashset.md b/en/application-dev/reference/apis/js-apis-hashset.md
index 8d21ef6d1994144aeb89be8d226ef041bdbdb95a..df65bfcb4a3167ed9c9f2292065554a505e9f4e1 100644
--- a/en/application-dev/reference/apis/js-apis-hashset.md
+++ b/en/application-dev/reference/apis/js-apis-hashset.md
@@ -1,8 +1,5 @@
 # @ohos.util.HashSet (Nonlinear Container HashSet)
 
-> **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.
-
 **HashSet** is implemented based on [HashMap](js-apis-hashmap.md). In **HashSet**, only the **value** object is processed.
 
 Unlike [TreeSet](js-apis-treeset.md), which stores and accesses data in sorted order, **HashSet** stores data in a random order. This means that **HashSet** may use a different order when storing and accessing elements. Both of them allows only unique elements. However, null values are allowed in **HashSet**, but not allowed in **TreeSet**.
@@ -12,6 +9,11 @@ Unlike [TreeSet](js-apis-treeset.md), which stores and accesses data in sorted o
 This topic uses the following to identify the use of generics:
 - T: Type
 
+> **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
 
 ```ts
@@ -125,9 +127,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let hashSet = new HashSet();
-let result = hashSet.has("squirrel");
 hashSet.add("squirrel");
-let result1 = hashSet.has("squirrel");
+let result = hashSet.has("squirrel");
 ```
 
 
diff --git a/en/application-dev/reference/apis/js-apis-inner-application-formExtensionContext.md b/en/application-dev/reference/apis/js-apis-inner-application-formExtensionContext.md
index 0af6842eb5b369526b917c076953489a94dd2fad..3f839c466dbdcb72fe43b5fbb369116269388a42 100644
--- a/en/application-dev/reference/apis/js-apis-inner-application-formExtensionContext.md
+++ b/en/application-dev/reference/apis/js-apis-inner-application-formExtensionContext.md
@@ -9,6 +9,12 @@ You can use the APIs of this module to start FormExtensionAbilities.
 > The initial APIs of this module are supported since API version 9. Newly added APIs will be marked with a superscript to indicate their earliest API version.
 > The APIs of this module can be used only in the stage model.
 
+## Modules to Import
+
+```ts
+import common from '@ohos.app.ability.common';
+```
+
 ## Usage
 
 Before using the **ServiceExtensionContext** module, you must first obtain a **FormExtensionAbility** instance.
@@ -18,7 +24,7 @@ import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
 import formBindingData from '@ohos.app.form.formBindingData';
 export default class MyFormExtensionAbility extends FormExtensionAbility {
     onAddForm() {
-        let formContext = this.context; // 获取FormExtensionContext
+        let formContext = this.context; // ��ȡFormExtensionContext
         // ...
         let dataObj1 = {
             temperature:'11c',
@@ -40,6 +46,18 @@ Starts an ability. This API uses an asynchronous callback to return the result.
 
 **System capability**: SystemCapability.Ability.Form
 
+**Error codes**
+
+| ID| Error Message|
+| -------- | -------- |
+| 202 | The application is not a system application. |
+| 401 | If the input parameter is not valid parameter. |
+| 16500050 | An IPC connection error happened. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16500101 | The application is not a system application. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+
 **Parameters**
 
 | Name|                Type              | Mandatory|              Description              |
@@ -60,7 +78,7 @@ let want = {
     uri: 'key={true,true,false}',
     parameters: {}
 };
-this.context.startAbility(want, (error, data) => {
+this.context.startAbility(want, (error) => {
     if (error) {
       console.log('FormExtensionContext startAbility, error:' + JSON.stringify(error));
     } else {
@@ -91,6 +109,18 @@ Starts an ability. This API uses a promise to return the result.
 | ------------ | ---------------------------------- |
 | Promise&lt;void&lt; | Promise that returns no value.|
 
+**Error codes**
+
+| ID| Error Message|
+| -------- | -------- |
+| 202 | The application is not a system application. |
+| 401 | If the input parameter is not valid parameter. |
+| 16500050 | An IPC connection error happened. |
+| 16500100 | Failed to obtain the configuration information. |
+| 16500101 | The application is not a system application. |
+| 16501000 | An internal functional error occurred. |
+|For details about the error codes, see [Form Error Codes](../errorcodes/errorcode-form.md).|
+
 **Example**
 
 ```ts
diff --git a/en/application-dev/reference/apis/js-apis-inputmethod.md b/en/application-dev/reference/apis/js-apis-inputmethod.md
index d3f74a40338d31b4355efe795199fb865e8bb6a6..5d6b85f2bf376847699ff87684aebb5f55b461ed 100644
--- a/en/application-dev/reference/apis/js-apis-inputmethod.md
+++ b/en/application-dev/reference/apis/js-apis-inputmethod.md
@@ -1,6 +1,6 @@
 # @ohos.inputMethod (Input Method Framework)
 
-The **inputMethod** module provides an input method framework, which can be used to hide the keyboard, obtain the list of installed input methods, display the dialog box for input method selection, and more.
+The **inputMethod** module is oriented to common foreground applications (third-party applications and system applications such as Notes, Messaging, and Settings). It provides input method control and management capabilities, including displaying or hiding the soft keyboard, switching between input methods, and obtaining the list of all input methods.
 
 > **NOTE**
 >
@@ -102,7 +102,7 @@ switchInputMethod(target: InputMethodProperty, callback: AsyncCallback&lt;boolea
 
 Switches to another input method. This API uses an asynchronous callback to return the result.
 
-**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (available only to system applications)
+**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (for system applications only)
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
@@ -154,21 +154,21 @@ switchInputMethod(target: InputMethodProperty): Promise&lt;boolean&gt;
 
 Switches to another input method. This API uses a promise to return the result.
 
-**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (available only to system applications)
+**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (for system applications only)
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
 **Parameters**
 
-  | Name| Type| Mandatory| Description|
-  | -------- | -------- | -------- | -------- |
-  |target |  [InputMethodProperty](#inputmethodproperty8)| Yes| Input method to switch to.|
+| Name| Type| Mandatory| Description|
+| -------- | -------- | -------- | -------- |
+|target |  [InputMethodProperty](#inputmethodproperty8)| Yes| Input method to switch to.|
 
 **Return value**
 
-  | Type                                     | Description                        |
-  | ----------------------------------------- | ---------------------------- |
-  | Promise\<boolean> | Promise used to return the result. The value **true** means that the switching is successful, and **false** means the opposite.|
+| Type                                     | Description                        |
+| ----------------------------------------- | ---------------------------- |
+| Promise\<boolean> | Promise used to return the result. The value **true** means that the switching is successful, and **false** means the opposite.|
 
 **Error codes**
 
@@ -231,7 +231,7 @@ switchCurrentInputMethodSubtype(target: InputMethodSubtype, callback: AsyncCallb
 
 Switches to another subtype of the current input method. This API uses an asynchronous callback to return the result.
 
-**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (available only to system applications)
+**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (for system applications only)
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
@@ -287,7 +287,7 @@ switchCurrentInputMethodSubtype(target: InputMethodSubtype): Promise&lt;boolean&
 
 Switches to another subtype of the current input method. This API uses a promise to return the result.
 
-**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (available only to system applications)
+**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (for system applications only)
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
@@ -366,7 +366,7 @@ switchCurrentInputMethodAndSubtype(inputMethodProperty: InputMethodProperty, inp
 
 Switches to a specified subtype of a specified input method. This API uses an asynchronous callback to return the result.
 
-**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (available only to system applications)
+**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (for system applications only)
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
@@ -415,7 +415,7 @@ switchCurrentInputMethodAndSubtype(inputMethodProperty: InputMethodProperty, inp
 
 Switches to a specified subtype of a specified input method. This API uses a promise to return the result.
 
-**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (available only to system applications)
+**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (for system applications only)
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
@@ -603,7 +603,7 @@ showSoftKeyboard(callback: AsyncCallback&lt;void&gt;): void
 
 Shows this soft keyboard. This API must be used with the input text box and works only when the input text box is activated. This API uses an asynchronous callback to return the result.
 
-**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (available only to system applications)
+**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (for system applications only)
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
@@ -640,7 +640,7 @@ showSoftKeyboard(): Promise&lt;void&gt;
 
 Shows this soft keyboard. This API must be used with the input text box and works only when the input text box is activated. This API uses a promise to return the result.
 
-**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (available only to system applications)
+**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (for system applications only)
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
@@ -675,7 +675,7 @@ hideSoftKeyboard(callback: AsyncCallback&lt;void&gt;): void
 
 Hides this soft keyboard. This API must be used with the input text box and works only when the input text box is activated. This API uses an asynchronous callback to return the result.
 
-**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (available only to system applications)
+**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (for system applications only)
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
@@ -712,7 +712,7 @@ hideSoftKeyboard(): Promise&lt;void&gt;
 
 Hides this soft keyboard. This API must be used with the input text box and works only when the input text box is activated. This API uses a promise to return the result.
 
-**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (available only to system applications)
+**Required permissions**: ohos.permission.CONNECT_IME_ABILITY (for system applications only)
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
diff --git a/en/application-dev/reference/apis/js-apis-inputmethodengine.md b/en/application-dev/reference/apis/js-apis-inputmethodengine.md
index 21df48e1434ae937a5515a6af4285504c0a0c17d..ecdfc7d180b05f69f9357ac1c8bf9470970961c7 100644
--- a/en/application-dev/reference/apis/js-apis-inputmethodengine.md
+++ b/en/application-dev/reference/apis/js-apis-inputmethodengine.md
@@ -1,6 +1,6 @@
 # @ohos.inputMethodEngine (Input Method Service)
 
-The **inputMethodEngine** module streamlines the interactions between input methods and applications. By calling APIs of this module, applications can be bound to input method services to accept text input, request the keyboard to display or hide, listen for the input method status, and much more.
+The **inputMethodEngine** module is oriented to input method applications (including system and third-party input method applications). With the APIs of this module, input method applications are able to create soft keyboard windows, insert or delete characters, select text, and listen for physical keyboard events.
 
 > **NOTE**
 >
@@ -56,7 +56,7 @@ Provides the constant values of function keys, edit boxes, and the cursor.
 
 getInputMethodAbility(): InputMethodAbility
 
-Obtains an **InputMethodEngine** instance.
+Obtains an [InputMethodAbility](#inputmethodability) instance for the input method. The input method can use the obtained instance to subscribe to a soft keyboard display/hide request event, create/destroy an input method panel, and the like.
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
@@ -64,7 +64,7 @@ Obtains an **InputMethodEngine** instance.
 
 | Type                                   | Description        |
 | --------------------------------------- | ------------ |
-| [InputMethodAbility](#inputmethodability) | **InputMethodEngine** instance obtained.|
+| [InputMethodAbility](#inputmethodability) | **InputMethodAbility** instance.|
 
 **Example**
 
@@ -76,7 +76,7 @@ let InputMethodAbility = inputMethodEngine.getInputMethodAbility();
 
 getKeyboardDelegate(): KeyboardDelegate
 
-Obtains a **KeyboardDelegate** instance.
+Obtains a [KeyboardDelegate](#keyboarddelegate) instance for the input method. The input method can use the obtained instance to subscribe to a physical keyboard event, text selection change event, and more.
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
@@ -84,7 +84,7 @@ Obtains a **KeyboardDelegate** instance.
 
 | Type                                 | Description            |
 | ------------------------------------- | ---------------- |
-| [KeyboardDelegate](#keyboarddelegate) | **KeyboardDelegate** instance obtained.|
+| [KeyboardDelegate](#keyboarddelegate) | **KeyboardDelegate** instance.|
 
 **Example**
 
@@ -96,7 +96,7 @@ let KeyboardDelegate = inputMethodEngine.getKeyboardDelegate();
 
 getInputMethodEngine(): InputMethodEngine
 
-Obtains an **InputMethodEngine** instance.
+Obtains an [InputMethodEngine](#inputmethodengine) instance for the input method. The input method can use the obtained instance to subscribe to a soft keyboard display/hide request event.
 
 > **NOTE**
 >
@@ -108,7 +108,7 @@ Obtains an **InputMethodEngine** instance.
 
 | Type                                   | Description        |
 | --------------------------------------- | ------------ |
-| [InputMethodEngine](#inputmethodengine-1) | **InputMethodEngine** instance obtained.|
+| [InputMethodEngine](#inputmethodengine) | **InputMethodAbility** instance.|
 
 **Example**
 
@@ -120,7 +120,7 @@ let InputMethodEngine = inputMethodEngine.getInputMethodEngine();
 
 createKeyboardDelegate(): KeyboardDelegate
 
-Obtains a **KeyboardDelegate** instance.
+Obtains a [KeyboardDelegate](#keyboarddelegate) instance for the input method. The input method can use the obtained instance to subscribe to a physical keyboard event, text selection change event, and more.
 
 > **NOTE**
 >
@@ -132,7 +132,7 @@ Obtains a **KeyboardDelegate** instance.
 
 | Type                                 | Description            |
 | ------------------------------------- | ---------------- |
-| [KeyboardDelegate](#keyboarddelegate) | **KeyboardDelegate** instance obtained.|
+| [KeyboardDelegate](#keyboarddelegate) | **KeyboardDelegate** instance.|
 
 **Example**
 
@@ -157,7 +157,7 @@ Enables listening for the input method binding event. This API uses an asynchron
 | Name  | Type                           | Mandatory| Description                                                        |
 | -------- | ------------------------------- | ---- | ------------------------------------------------------------ |
 | type     | string                        | Yes  | Listening type.<br>The value **'inputStart'** indicates the input method binding event.|
-| callback | (kbController: [KeyboardController](#keyboardcontroller), textInputClient: [TextInputClient](#textinputclient)) => void | Yes| Callback used to return the **KeyboardController** and **TextInputClient** instances.|
+| callback | (kbController: [KeyboardController](#keyboardcontroller), textInputClient: [TextInputClient](#textinputclientdeprecated)) => void | Yes| Callback used to return the **KeyboardController** and **TextInputClient** instances.|
 
 **Example**
 
@@ -181,7 +181,7 @@ Cancels listening for the input method binding event.
 | Name  | Type                | Mandatory| Description                    |
 | -------- | -------------------- | ---- | ------------------------ |
 | type | string                                                       | Yes  | Listening type.<br>The value **'inputStart'** indicates the input method binding event.|
-| callback | (kbController: [KeyboardController](#keyboardcontroller), textInputClient: [TextInputClient](#textinputclient)) => void | No| Callback used to return the **KeyboardController** and **TextInputClient** instances.|
+| callback | (kbController: [KeyboardController](#keyboardcontroller), textInputClient: [TextInputClient](#textinputclientdeprecated)) => void | No| Callback used to return the **KeyboardController** and **TextInputClient** instances.|
 
 **Example**
 
@@ -195,7 +195,7 @@ inputMethodEngine.getInputMethodEngine().off('inputStart', (kbController, textIn
 
 on(type: 'keyboardShow'|'keyboardHide', callback: () => void): void
 
-Enables listening for a keyboard event. This API uses an asynchronous callback to return the result.
+Enables listening for a keyboard visibility event. This API uses an asynchronous callback to return the result.
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
@@ -221,7 +221,7 @@ inputMethodEngine.getInputMethodEngine().on('keyboardHide', () => {
 
 off(type: 'keyboardShow'|'keyboardHide', callback?: () => void): void
 
-Disables listening for a keyboard event. This API uses an asynchronous callback to return the result.
+Disables listening for a keyboard visibility event. This API uses an asynchronous callback to return the result.
 
 **System capability**: SystemCapability.MiscServices.InputMethodFramework
 
diff --git a/en/application-dev/reference/apis/js-apis-lightweightmap.md b/en/application-dev/reference/apis/js-apis-lightweightmap.md
index 057dc7e3f1f52f8d491ed1edf35037d42c7ee337..ed1848ad8df12b8a5526699908347ade635a9041 100644
--- a/en/application-dev/reference/apis/js-apis-lightweightmap.md
+++ b/en/application-dev/reference/apis/js-apis-lightweightmap.md
@@ -1,8 +1,5 @@
 # @ohos.util.LightWeightMap (Nonlinear Container LightWeightMap) 
 
-> **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.
-
 **LightWeightMap** stores key-value (KV) pairs. Each key must be unique and have only one value.
 
 **LightWeightMap** is based on generics and uses a lightweight structure. Its default initial capacity is 8, and it has the capacity doubled in each expansion.
@@ -17,6 +14,11 @@ This topic uses the following to identify the use of generics:
 - K: Key
 - V: Value
 
+> **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
 
 ```ts
@@ -197,9 +199,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let lightWeightMap = new LightWeightMap();
-let result = lightWeightMap.hasValue(123);
 lightWeightMap.set("squirrel", 123);
-let result1 = lightWeightMap.hasValue(123);
+let result = lightWeightMap.hasValue(123);
 ```
 
 
diff --git a/en/application-dev/reference/apis/js-apis-lightweightset.md b/en/application-dev/reference/apis/js-apis-lightweightset.md
index 47295b0dd86d5b805607850b92a9692f71940dc7..05eba80d96783d32a427f1181bdc5b71bdab596b 100644
--- a/en/application-dev/reference/apis/js-apis-lightweightset.md
+++ b/en/application-dev/reference/apis/js-apis-lightweightset.md
@@ -1,8 +1,5 @@
 # @ohos.util.LightWeightSet (Nonlinear Container LightWeightSet)
 
-> **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.
-
 **LightWeightSet** stores a set of values, each of which must be unique.
 
 **LightWeightSet** is based on generics and uses a lightweight structure. Its default initial capacity is 8, and it has the capacity doubled in each expansion.
@@ -16,6 +13,11 @@ Compared with **[HashSet](js-apis-hashset.md)**, which can also store values, **
 This topic uses the following to identify the use of generics:
 - T: Type
 
+> **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
 
 ```ts
@@ -227,9 +229,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let lightWeightSet = new LightWeightSet();
-let result = lightWeightSet.has(123);
 lightWeightSet.add(123);
-result = lightWeightSet.has(123);
+let result = lightWeightSet.has(123);
 ```
 
 
@@ -267,7 +268,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 let lightWeightSet = new LightWeightSet();
 lightWeightSet.add("squirrel");
 lightWeightSet.add("sparrow");
-let obj = ["squirrel", "sparrow"];
+let obj = ["sparrow", "squirrel"];
 let result = lightWeightSet.equal(obj);
 ```
 
diff --git a/en/application-dev/reference/apis/js-apis-linkedlist.md b/en/application-dev/reference/apis/js-apis-linkedlist.md
index ceb144301277ac8cdd08f52713ae6cf576817a18..14382577e7b3fb1881e74527b8ec31ab87a89169 100644
--- a/en/application-dev/reference/apis/js-apis-linkedlist.md
+++ b/en/application-dev/reference/apis/js-apis-linkedlist.md
@@ -198,7 +198,6 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let linkedList = new LinkedList();
-let result1 = linkedList.has("squirrel");
 linkedList.add("squirrel");
 let result = linkedList.has("squirrel");
 ```
@@ -802,7 +801,7 @@ linkedList.add(2);
 linkedList.add(4);
 linkedList.add(5);
 linkedList.add(4);
-linkedList.getLast();
+let result = linkedList.getLast();
 ```
 
 ### [Symbol.iterator]
diff --git a/en/application-dev/reference/apis/js-apis-list.md b/en/application-dev/reference/apis/js-apis-list.md
index 295824f50139aca548f3dcd5952ce75c2bec7cfc..b7618d64c1d61a52324ada111347f666e7095c73 100644
--- a/en/application-dev/reference/apis/js-apis-list.md
+++ b/en/application-dev/reference/apis/js-apis-list.md
@@ -13,6 +13,7 @@ This topic uses the following to identify the use of generics:
 >
 > 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
 
 ```ts
@@ -160,9 +161,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let list = new List();
-let result = list.has("squirrel");
 list.add("squirrel");
-let result1 = list.has("squirrel");
+let result = list.has("squirrel");
 ```
 
 ### get
@@ -288,7 +288,6 @@ list.add(2);
 list.add(1);
 list.add(2);
 list.add(4);
-list.getIndexOf(2);
 let result = list.getIndexOf(2);
 ```
 
@@ -327,14 +326,11 @@ let list = new List();
 list.add(2);
 list.add(4);
 list.add(5);
-list.add(2);
-let obj1 = new List();
-obj1.add(2);
-obj1.add(4);
-obj1.add(5);
-list.equal(obj1);
-let obj2 = {name : "Dylon", age : "13"};
-let result = list.equal(obj2);
+let obj = new List();
+obj.add(2);
+obj.add(4);
+obj.add(5);
+let result = list.equal(obj);
 ```
 
 ### removeByIndex
@@ -457,11 +453,9 @@ list.add(2);
 list.add(4);
 list.add(5);
 list.add(4);
-list.replaceAllElements((value: number, index: number) => {
-  return value = 2 * value;
-});
-list.replaceAllElements((value: number, index: number) => {
-  return value = value - 2;
+list.replaceAllElements((value) => {
+  // Add the user operation logic based on the actual scenario.
+  return value;
 });
 ```
 
@@ -589,9 +583,7 @@ list.add(2);
 list.add(4);
 list.add(5);
 list.add(4);
-let result = list.getSubList(2, 4);
-let result1 = list.getSubList(4, 3);
-let result2 = list.getSubList(2, 6);
+let result = list.getSubList(1, 3);
 ```
 
 ### clear
@@ -659,7 +651,7 @@ list.add(2);
 list.add(4);
 list.add(5);
 list.add(4);
-list.set(2, "b");
+let result = list.set(2, "b");
 ```
 
 ### convertToArray
diff --git a/en/application-dev/reference/apis/js-apis-measure.md b/en/application-dev/reference/apis/js-apis-measure.md
index 6095a5e68ed87bc8c92fe3198e36ac4982fe70a7..b1e3699e9cbac290f6cf53d75c8c20d9f57544a4 100644
--- a/en/application-dev/reference/apis/js-apis-measure.md
+++ b/en/application-dev/reference/apis/js-apis-measure.md
@@ -15,7 +15,7 @@ import measure from '@ohos.measure'
 
 ## measure.measureText
 
-measureText(options: MeasureOptions): double
+measureText(options: MeasureOptions): number
 
 Measures the width of the given single-line text.
 
@@ -31,7 +31,7 @@ Measures the width of the given single-line text.
 
 | Type         | Description      |
 | ------------  | --------- |
-| double        | Text width.<br>The unit is px.|
+| number        | Text width.<br>The unit is px.|
 
 
 **Example**
diff --git a/en/application-dev/reference/apis/js-apis-mediaquery.md b/en/application-dev/reference/apis/js-apis-mediaquery.md
index 132b435812b19c1ee9843c29861e99d30c00e8c4..7cf762140445fab786d6a5437bf5b97fba64c538 100644
--- a/en/application-dev/reference/apis/js-apis-mediaquery.md
+++ b/en/application-dev/reference/apis/js-apis-mediaquery.md
@@ -26,7 +26,7 @@ Sets the media query condition. This API returns the corresponding media query l
 
 | Name      | Type    | Mandatory  | Description                                      |
 | --------- | ------ | ---- | ---------------------------------------- |
-| condition | string | Yes   | Media query condition. For details, see [Syntax of Media Query Conditions](../../ui/ui-ts-layout-mediaquery.md#syntax).|
+| condition | string | Yes   | Media query condition. For details, see [Syntax of Media Query Conditions](../../ui/arkts-layout-development-media-query.md#syntax).|
 
 **Return value**
 
diff --git a/en/application-dev/reference/apis/js-apis-notificationManager.md b/en/application-dev/reference/apis/js-apis-notificationManager.md
index 2da6864b94f7e0068fb592202b1c51d5bb565b10..875b6129d039e09172fa9a1e366bd48a813749fc 100644
--- a/en/application-dev/reference/apis/js-apis-notificationManager.md
+++ b/en/application-dev/reference/apis/js-apis-notificationManager.md
@@ -33,6 +33,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                 |
 | -------- | ----------------------------------------- |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -88,6 +89,8 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                 |
 | -------- | ----------------------------------------- |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -142,6 +145,8 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                 |
 | -------- | ----------------------------------------- |
+| 202      | Not system application to call the interface.   |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -203,6 +208,8 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                 |
 | -------- | ----------------------------------------- |
+| 201      | Permission denied.                        |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -256,6 +263,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -298,6 +306,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -334,6 +343,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -369,6 +379,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -409,6 +420,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -448,6 +460,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -496,6 +511,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -535,6 +553,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -575,6 +594,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -614,6 +634,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -666,6 +689,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -709,6 +735,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -756,6 +783,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -791,6 +819,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -831,6 +860,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -866,6 +896,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -907,6 +938,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -942,6 +974,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -975,6 +1008,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1015,6 +1049,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1063,6 +1100,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1106,6 +1146,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1159,6 +1202,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1201,6 +1247,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1251,6 +1300,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1292,6 +1344,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1340,6 +1395,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1383,6 +1441,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1436,6 +1497,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1452,9 +1516,7 @@ Notification.isBadgeDisplayed(bundle).then((data) => {
 });
 ```
 
-
-
-## Notification.setSlotByBundle
+## notificationManager.setSlotByBundle
 
 setSlotByBundle(bundle: BundleOption, slot: NotificationSlot, callback: AsyncCallback\<void\>): void
 
@@ -1480,6 +1542,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1533,6 +1598,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1579,6 +1647,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1632,6 +1703,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1675,6 +1749,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1728,6 +1805,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1771,6 +1851,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1815,6 +1898,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1849,6 +1935,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1889,6 +1976,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1923,6 +2011,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1963,6 +2052,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1998,6 +2088,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2040,6 +2131,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2081,6 +2173,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -2130,6 +2225,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -2172,6 +2270,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2222,6 +2323,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2266,6 +2370,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2320,6 +2427,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2366,6 +2476,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2410,6 +2523,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2448,6 +2564,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2501,6 +2620,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2541,6 +2663,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2585,6 +2710,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2620,6 +2748,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2668,6 +2797,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2705,6 +2835,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2739,6 +2870,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2778,6 +2910,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2825,6 +2960,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2861,6 +2999,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2902,6 +3041,7 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2933,7 +3073,7 @@ Sets whether a specified application supports distributed notifications. This AP
 
 | Name  | Type                    | Mandatory| Description                      |
 | -------- | ------------------------ | ---- | -------------------------- |
-| bundle   | [BundleOption](#bundleoption)             | Yes  | Bundle information of the application.                  |
+| bundle   | [BundleOption](./js-apis-inner-notification-notificationCommonDef.md#bundleoption)             | Yes  | Bundle information of the application.                  |
 | enable   | boolean                  | Yes  | Whether the application supports distributed notifications.                      |
 | callback | AsyncCallback\<void\> | Yes  | Callback used to return the result.|
 
@@ -2943,6 +3083,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -2996,6 +3139,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3041,6 +3187,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3097,6 +3246,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3140,6 +3292,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3184,6 +3339,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3224,6 +3382,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                 |
 | -------- | ----------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -3290,6 +3451,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                 |
 | -------- | ----------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -3352,6 +3516,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3405,6 +3572,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3451,6 +3621,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3501,6 +3674,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3544,6 +3720,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3598,6 +3777,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3640,6 +3822,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3694,6 +3879,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3738,6 +3926,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3790,6 +3981,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201      | Permission denied.                        |
+| 202      | Not system application to call the interface. |
+| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
diff --git a/en/application-dev/reference/apis/js-apis-notificationSubscribe.md b/en/application-dev/reference/apis/js-apis-notificationSubscribe.md
index 7acde9a1548e1ec17f5294e7e7e2d845d58a030e..4380c521dc82bf34771c17e238e4a7b56809276a 100644
--- a/en/application-dev/reference/apis/js-apis-notificationSubscribe.md
+++ b/en/application-dev/reference/apis/js-apis-notificationSubscribe.md
@@ -40,6 +40,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201  | Permission denied.                      |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.             |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -92,6 +95,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201  | Permission denied.                      |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.             |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -142,6 +148,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201  | Permission denied.                      |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.             |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -187,6 +196,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201  | Permission denied.                      |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.             |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -234,6 +246,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201  | Permission denied.                      |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.             |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -279,6 +294,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201  | Permission denied.                           |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -325,7 +343,7 @@ Removes a notification for a specified application. This API uses a promise to r
 | Name           | Type           | Mandatory| Description      |
 | --------------- | --------------- | ---- | ---------- |
 | bundle          | [BundleOption](js-apis-inner-notification-notificationCommonDef.md#bundleoption)    | Yes  | Bundle information of the application.|
-| notificationKey | [NotificationKey](js-apis-notification.md#notificationkey)) | Yes  | Notification key.  |
+| notificationKey | [NotificationKey](js-apis-notification.md#notificationkey) | Yes  | Notification key.  |
 | reason          | [RemoveReason](#removereason) | Yes  | Reason for removing the notification.        |
 
 **Error codes**
@@ -334,6 +352,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201  | Permission denied.                           |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -382,6 +403,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201  | Permission denied.                           |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -428,6 +452,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201  | Permission denied.                           |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -459,7 +486,7 @@ Removes all notifications for a specified application. This API uses an asynchro
 
 | Name    | Type                 | Mandatory| Description                        |
 | -------- | --------------------- | ---- | ---------------------------- |
-| bundle   | [BundleOption](js-apis-inner-notification-notificationCommonDef.md#bundleoption))          | Yes  | Bundle information of the application.                  |
+| bundle   | [BundleOption](js-apis-inner-notification-notificationCommonDef.md#bundleoption)          | Yes  | Bundle information of the application.                  |
 | callback | AsyncCallback\<void\> | Yes  | Callback used to return the result.|
 
 **Error codes**
@@ -468,6 +495,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201  | Permission denied.                           |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -513,6 +543,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201  | Permission denied.                           |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -547,7 +580,7 @@ Removes all notifications for a specified application. This API uses a promise t
 
 | Name  | Type        | Mandatory| Description      |
 | ------ | ------------ | ---- | ---------- |
-| bundle | [BundleOption](js-apis-inner-notification-notificationCommonDef.md#bundleoption)) | No  | Bundle information of the application.|
+| bundle | [BundleOption](js-apis-inner-notification-notificationCommonDef.md#bundleoption) | No  | Bundle information of the application.|
 
 **Error codes**
 
@@ -555,6 +588,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                                |
 | -------- | ---------------------------------------- |
+| 201  | Permission denied.                           |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -594,6 +630,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201  | Permission denied.                           |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -639,6 +678,9 @@ For details about the error codes, see [Notification Error Codes](../errorcodes/
 
 | ID| Error Message                           |
 | -------- | ----------------------------------- |
+| 201  | Permission denied.                           |
+| 202  | Not system application to call the interface. |
+| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -662,7 +704,7 @@ notificationSubscribe.removeAll(userId, removeAllCallback);
 
 ## NotificationSubscriber
 
-Provides callbacks for receiving or removing notifications and serves as the input parameter of [subscribe](#notificationsubscribe).
+Provides callbacks for receiving or removing notifications and serves as the input parameter of [subscribe](#notificationsubscribesubscribe).
 
 **System API**: This is a system API and cannot be called by third-party applications.
 
@@ -670,7 +712,7 @@ Provides callbacks for receiving or removing notifications and serves as the inp
 
 onConsume?: (data: [SubscribeCallbackData](js-apis-notification.md#subscribecallbackdata)) => void
 
-Callback for receiving notifications.
+Called when a notification is received.
 
 **System capability**: SystemCapability.Notification.Notification
 
@@ -710,7 +752,7 @@ notificationSubscribe.subscribe(subscriber, subscribeCallback);
 
 onCancel?:(data: [SubscribeCallbackData](js-apis-notification.md#subscribecallbackdata)) => void
 
-Callback for canceling notifications.
+Called when a notification is canceled.
 
 **System capability**: SystemCapability.Notification.Notification
 
@@ -750,7 +792,7 @@ notificationSubscribe.subscribe(subscriber, subscribeCallback);
 
 onUpdate?:(data: [NotificationSortingMap](js-apis-notification.md#notificationsortingmap)) => void
 
-Callback for notification sorting updates.
+Called when the notification sorting list is updated.
 
 **System capability**: SystemCapability.Notification.Notification
 
@@ -788,7 +830,7 @@ notificationSubscribe.subscribe(subscriber, subscribeCallback);
 
 onConnect?:() => void
 
-Callback for subscription.
+Called when subscription is complete.
 
 **System capability**: SystemCapability.Notification.Notification
 
@@ -820,7 +862,7 @@ notificationSubscribe.subscribe(subscriber, subscribeCallback);
 
 onDisconnect?:() => void
 
-Callback for unsubscription.
+Called when unsubscription is complete.
 
 **System capability**: SystemCapability.Notification.Notification
 
@@ -898,7 +940,7 @@ notificationSubscribe.subscribe(subscriber, subscribeCallback);
 
 onDoNotDisturbDateChange?:(mode: notification.[DoNotDisturbDate](js-apis-notificationManager.md#donotdisturbdate)) => void
 
-Callback for DND time setting updates.
+Called when the DND time setting is updated.
 
 **System capability**: SystemCapability.Notification.Notification
 
@@ -935,7 +977,7 @@ notificationSubscribe.subscribe(subscriber, subscribeCallback);
 
 ### onEnabledNotificationChanged
 
-onEnabledNotificationChanged?:(callbackData: [EnabledNotificationCallbackData](js-apis-notification.md#enablednotificationcallbackdata)) => void
+onEnabledNotificationChanged?:(callbackData: [EnabledNotificationCallbackData](js-apis-notification.md#enablednotificationcallbackdata8)) => void
 
 Listens for the notification enabled status changes. This API uses an asynchronous callback to return the result.
 
@@ -947,7 +989,7 @@ Listens for the notification enabled status changes. This API uses an asynchrono
 
 | Name| Type| Mandatory| Description|
 | ------------ | ------------------------ | ---- | -------------------------- |
-| callback | AsyncCallback\<[EnabledNotificationCallbackData](js-apis-notification.md#enablednotificationcallbackdata)\> | Yes| Callback used to return the result.|
+| callback | AsyncCallback\<[EnabledNotificationCallbackData](js-apis-notification.md#enablednotificationcallbackdata8)\> | Yes| Callback used to return the result.|
 
 **Example**
 
@@ -973,47 +1015,6 @@ let subscriber = {
 notificationSubscribe.subscribe(subscriber, subscribeCallback);
 ```
 
-### onBadgeChanged<sup>10+</sup>
-
- onBadgeChanged?:(data: [BadgeNumberCallbackData](#badgenumbercallbackdata)) => void
-
-Listens for the change of the notification badge number.
-
-**System capability**: SystemCapability.Notification.Notification
-
-**System API**: This is a system API and cannot be called by third-party applications.
-
-**Parameters**
-
-| Name  | Type                                                        | Mandatory| Description                      |
-| -------- | ------------------------------------------------------------ | ---- | -------------------------- |
-| callback | AsyncCallback\<[BadgeNumberCallbackData](#badgenumbercallbackdata)\> | Yes  | Callback used to return the result.|
-
-**Example**
-
-```javascript
-function subscribeCallback(err) {
-    if (err) {
-        console.error(`subscribe failed, code is ${err.code}, message is ${err.message}`);
-    } else {
-        console.info("subscribeCallback");
-    }
-};
-
-function onBadgeChangedCallback(data) {
-    console.info("bundle: ", data.bundle);
-    console.info("uid: ", data.uid);
-    console.info("badgeNumber: ", data.badgeNumber);
-};
-
-let subscriber = {
-    onBadgeChanged: onBadgeChangedCallback
-};
-
-notificationSubscribe.subscribe(subscriber, subscribeCallback);
-```
-
-
 ## RemoveReason
 
 **System capability**: SystemCapability.Notification.Notification
@@ -1024,15 +1025,3 @@ notificationSubscribe.subscribe(subscriber, subscribeCallback);
 | -------------------- | --- | -------------------- |
 | CLICK_REASON_REMOVE  | 1   | The notification is removed after a click on it.   |
 | CANCEL_REASON_REMOVE | 2   | The notification is removed by the user.        |
-
-## BadgeNumberCallbackData<sup>10+</sup>
-
-**System capability**: SystemCapability.Notification.Notification
-
-**System API**: This is a system API and cannot be called by third-party applications.
-
-| Name       | Type  | Readable| Writable| Description        |
-| ----------- | ------ | ---- | ---- | ------------ |
-| bundle      | string | Yes  | No  | Bundle name of the application.|
-| uid         | number | Yes  | No  | UID of the application. |
-| badgeNumber | number | Yes  | No  | Notification badge number.  |
diff --git a/en/application-dev/reference/apis/js-apis-plainarray.md b/en/application-dev/reference/apis/js-apis-plainarray.md
index 387577bb2409ae399f46a225e53e3d00db9035e6..14f73f6d4b11059551b376f7fcb9e56ee4e1ab84 100644
--- a/en/application-dev/reference/apis/js-apis-plainarray.md
+++ b/en/application-dev/reference/apis/js-apis-plainarray.md
@@ -1,8 +1,5 @@
 # @ohos.util.PlainArray (Nonlinear Container PlainArray) 
 
-> **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.
-
 **PlainArray** stores key-value (KV) pairs. Each key must be unique, be of the number type, and have only one value.
 
 **PlainArray** is based on generics and uses a lightweight structure. Keys in the array are searched using binary search and are mapped to values in other arrays.
@@ -14,6 +11,11 @@ Both **PlainArray** and **[LightWeightMap](js-apis-lightweightmap.md)** are used
 This topic uses the following to identify the use of generics:
 - T: Type
 
+> **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
 
 ```ts
@@ -21,7 +23,6 @@ import PlainArray from '@ohos.util.PlainArray';
 ```
 
 
-
 ## PlainArray
 
 ### Attributes
@@ -118,9 +119,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let plainArray = new PlainArray();
-plainArray.has(1);
 plainArray.add(1, "squirrel");
-let result1 = plainArray.has(1);
+let result = plainArray.has(1);
 ```
 
 
diff --git a/en/application-dev/reference/apis/js-apis-queue.md b/en/application-dev/reference/apis/js-apis-queue.md
index 56bb71d5b88e93c2364c23176543f131d134e9f2..c926b741543cd384f6c4b7649c2e8f1881883a55 100644
--- a/en/application-dev/reference/apis/js-apis-queue.md
+++ b/en/application-dev/reference/apis/js-apis-queue.md
@@ -1,8 +1,5 @@
 # @ohos.util.Queue (Linear Container Queue)
 
-> **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.
-
 **Queue** follows the principle of First In First Out (FIFO). It supports insertion of elements at the end and removal from the front of the queue. **Queue** is implemented based on the queue data structure.
 
 Unlike **[Deque](js-apis-deque.md)**, which supports insertion and removal at both the ends, **Queue** supports insertion at one end and removal at the other end.
@@ -12,6 +9,11 @@ Unlike **[Deque](js-apis-deque.md)**, which supports insertion and removal at bo
 This topic uses the following to identify the use of generics:
 - T: Type
 
+> **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
 
 ```ts
diff --git a/en/application-dev/reference/apis/js-apis-resourceschedule-workScheduler.md b/en/application-dev/reference/apis/js-apis-resourceschedule-workScheduler.md
index 3bc7d33f43bb947212cc25a94f69f02f56e430ec..967001b4652718a2ba0b2d368b2e366fa4d66daa 100644
--- a/en/application-dev/reference/apis/js-apis-resourceschedule-workScheduler.md
+++ b/en/application-dev/reference/apis/js-apis-resourceschedule-workScheduler.md
@@ -130,7 +130,7 @@ Obtains the latest task status. This API uses an asynchronous callback to return
 | Name     | Type                                   | Mandatory  | Description                                      |
 | -------- | ------------------------------------- | ---- | ---------------------------------------- |
 | workId   | number                                | Yes   | Task ID.                                |
-| callback | AsyncCallback\<[WorkInfo](#workinfo)> | Yes   | Callback used to return the result. Returns the task status obtained from the **WorkSchedulerService** if the specified task ID is valid; returns **null** otherwise.|
+| callback | AsyncCallback\<[WorkInfo](#workinfo)> | Yes   | Callback used to return the result. Returns the task status obtained from the **WorkSchedulerService** if the specified task ID is valid; throws an exception otherwise. |
 
 **Error codes**
 
@@ -178,7 +178,7 @@ Obtains the latest task status. This API uses a promise to return the result.
 
 | Type                             | Description                                      |
 | ------------------------------- | ---------------------------------------- |
-| Promise\<[WorkInfo](#workinfo)> | Promise used to return the result. Returns the task status obtained from the **WorkSchedulerService** if the specified task ID is valid; returns **null** otherwise.|
+| Promise\<[WorkInfo](#workinfo)> | Promise used to return the result. Returns the task status obtained from the **WorkSchedulerService** if the specified task ID is valid; throws an exception otherwise. |
 
 **Error codes**
 
diff --git a/en/application-dev/reference/apis/js-apis-router.md b/en/application-dev/reference/apis/js-apis-router.md
index da1dc64c53625de97aa0747164a33f10f35623af..1262a1f285121357f67991b3bec06af8a2fbc24d 100644
--- a/en/application-dev/reference/apis/js-apis-router.md
+++ b/en/application-dev/reference/apis/js-apis-router.md
@@ -380,6 +380,7 @@ router.replaceUrl({
   }
   console.info('replaceUrl success');
 });
+
 ```
 
 ## router.back
@@ -394,7 +395,7 @@ Returns to the previous page or a specified page.
 
 | Name | Type                           | Mandatory| Description                                                        |
 | ------- | ------------------------------- | ---- | ------------------------------------------------------------ |
-| options | [RouterOptions](#routeroptions) | No  | Description of the page. The **url** parameter indicates the URL of the page to return to. If the specified page does not exist in the page stack, the application does not respond. If no URL is set, the previous page is returned, and the page in the page stack is not reclaimed. It will be reclaimed after being popped up.|
+| options | [RouterOptions](#routeroptions) | No  | Description of the page. The **url** parameter indicates the URL of the page to return to. If the specified page does not exist in the page stack, the application does not respond. If no URL is set, the application returns to the previous page, and the page is not rebuilt. The page in the page stack is not reclaimed. It will be reclaimed after being popped up.|
 
 **Example**
 
@@ -573,8 +574,8 @@ Enumerates the routing modes.
 
 | Name    | Description                                                        |
 | -------- | ------------------------------------------------------------ |
-| Standard | Standard mode.<br>The target page is added to the top of the page stack, regardless of whether a page with the same URL exists in the stack.<br>**NOTE**<br>If the routing mode is not used, the page is redirected to in standard mode.|
-| Single   | Singleton mode.<br>If the URL of the target page already exists in the page stack, the page closest to the top of the stack is moved as a new page to the top of the stack.<br>If the URL of the target page does not exist in the page stack, the page is redirected to in standard mode.|
+| Standard | Multi-instance mode. It is the default routing mode.<br>The target page is added to the top of the page stack, regardless of whether a page with the same URL exists in the stack.<br>**NOTE**<br>If the routing mode is not used, the page is redirected to in multi-instance mode.|
+| Single   | Singleton mode.<br>If the URL of the target page already exists in the page stack, the page closest to the top of the stack is moved to the top and becomes a new page.<br>If the URL of the target page does not exist in the page stack, the page is redirected to in multi-instance mode.|
 
 ## Examples
 
@@ -659,7 +660,7 @@ import router from '@ohos.router'
 struct Second {
   private content: string = "This is the second page."
   @State text: string = router.getParams()['text']
-  @State data: any = router.getParams()['data']
+  @State data: object = router.getParams()['data']
   @State secondData : string = ''
   
   build() {
@@ -670,7 +671,7 @@ struct Second {
       Text(this.text)
         .fontSize(30)
         .onClick(()=>{
-          this.secondData = (this.data.array[1]).toString()
+          this.secondData = (this.data.['array'][1]).toString()
         })
       .margin({top:20})
       Text(`This is the data passed from the first page: ${this.secondData}`)
diff --git a/en/application-dev/reference/apis/js-apis-sensor.md b/en/application-dev/reference/apis/js-apis-sensor.md
index e0438820b47438b2fa545723003edc91b7eef3f5..6927a99fd2cbcbc1fac05349c64b34106ba50104 100644
--- a/en/application-dev/reference/apis/js-apis-sensor.md
+++ b/en/application-dev/reference/apis/js-apis-sensor.md
@@ -3906,7 +3906,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.AC
 | options  | [Options](#options)                                          | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_ACCELEROMETER_UNCALIBRATED,function(data){
       console.info('X-coordinate component: ' + data.x);
@@ -3939,7 +3938,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.GR
 | options  | [Options](#options)                                 | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_GRAVITY,function(data){
       console.info('X-coordinate component: ' + data.x);
@@ -3971,7 +3969,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.GY
 | options  | [Options](#options)                                     | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_GYROSCOPE,function(data){
       console.info('X-coordinate component: ' + data.x);
@@ -4003,7 +4000,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.GY
 | options  | [Options](#options)                                          | No        | Interval at which the callback is invoked to return the sensor data. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_GYROSCOPE_UNCALIBRATED,function(data){
       console.info('X-coordinate component: ' + data.x);
@@ -4036,7 +4032,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.SI
 | options  | [Options](#options)                                          | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_SIGNIFICANT_MOTION,function(data){
       console.info('Scalar data: ' + data.scalar);
@@ -4066,7 +4061,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.PE
 | options  | [Options](#options)                                          | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_PEDOMETER_DETECTION,function(data){
       console.info('Scalar data: ' + data.scalar);
@@ -4096,7 +4090,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.PE
 | options  | [Options](#options)                                     | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_PEDOMETER,function(data){
       console.info('Steps: ' + data.steps);
@@ -4131,7 +4124,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.AM
   },
       {interval: 10000000}
   );
-
   ```
 
 ### MAGNETIC_FIELD<sup>(deprecated)</sup>
@@ -4162,7 +4154,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.MA
   },
       {interval: 10000000}
   );
-
   ```
 
 ### MAGNETIC_FIELD_UNCALIBRATED<sup>(deprecated)</sup>
@@ -4184,7 +4175,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.MA
 | options  | [Options](#options)                                          | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_MAGNETIC_FIELD_UNCALIBRATED,function(data){
       console.info('X-coordinate component: ' + data.x);
@@ -4196,7 +4186,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.MA
   },
       {interval: 10000000}
   );
-
   ```
 
 ### PROXIMITY<sup>(deprecated)</sup>
@@ -4218,14 +4207,12 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.PR
 | options  | [Options](#options)                                     | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_PROXIMITY,function(data){
       console.info('Distance: ' + data.distance);
   },
       {interval: 10000000}
   );
-
   ```
 
 ### HUMIDITY<sup>(deprecated)</sup>
@@ -4254,7 +4241,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.HU
   },
       {interval: 10000000}
   );
-
   ```
 
 ### BAROMETER<sup>(deprecated)</sup>
@@ -4283,7 +4269,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.BA
   },
       {interval: 10000000}
   );
-
   ```
 
 ### HALL<sup>(deprecated)</sup>
@@ -4305,14 +4290,12 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.HA
 | options  | [Options](#options)                           | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_HALL,function(data){
       console.info('Status: ' + data.status);
   },
       {interval: 10000000}
   );
-
   ```
 
 ### AMBIENT_LIGHT<sup>(deprecated)</sup>
@@ -4341,7 +4324,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.AM
   },
       {interval: 10000000}
   );
-
   ```
 
 ### ORIENTATION<sup>(deprecated)</sup>
@@ -4363,7 +4345,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.OR
 | options  | [Options](#options)                                         | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_ORIENTATION,function(data){
       console.info('The device rotates at an angle around the X axis: ' + data.beta);
@@ -4372,7 +4353,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.OR
   },
       {interval: 10000000}
   );
-
   ```
 
 ### HEART_RATE<sup>(deprecated)</sup>
@@ -4413,7 +4393,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.RO
 | options  | [Options](#options)                                          | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_ROTATION_VECTOR,function(data){
       console.info('X-coordinate component: ' + data.x);
@@ -4423,7 +4402,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.RO
   },
       {interval: 10000000}
   );
-
   ```
 
 ### WEAR_DETECTION<sup>(deprecated)</sup>
@@ -4445,14 +4423,12 @@ This API is deprecated since API version 9. You are advised to use [sensor.on.WE
 | options  | [Options](#options)                                          | No        | Interval at which the callback is invoked to return the sensor data. The default value is 200,000,000 ns. |
 
 **Example**
-
   ```js
   sensor.on(sensor.SensorType.SENSOR_TYPE_ID_WEAR_DETECTION,function(data){
       console.info('Wear status: ' + data.value);
   },
       {interval: 10000000}
   );
-
   ```
 
 ## sensor.once<sup>(deprecated)</sup>
@@ -4477,7 +4453,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[AccelerometerResponse](#accelerometerresponse)&gt; | Yes       | One-shot callback used to return the acceleration sensor data. The reported data type in the callback is **AccelerometerResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_ACCELEROMETER,function(data){
       console.info('X-coordinate component: ' + data.x);
@@ -4485,7 +4460,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
       console.info('Z-coordinate component: ' + data.z);
     }
   );
-
   ```
 
 ### LINEAR_ACCELERATION<sup>(deprecated)</sup>
@@ -4527,7 +4501,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[AccelerometerUncalibratedResponse](#accelerometeruncalibratedresponse)&gt; | Yes       | One-shot callback used to return the uncalibrated acceleration sensor data. The reported data type in the callback is **AccelerometerUncalibratedResponse**. |
 
 **Example**
-
   ```
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_ACCELEROMETER_UNCALIBRATED, function(data) {
       console.info('X-coordinate component: ' + data.x);
@@ -4538,7 +4511,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
       console.info('Z-coordinate bias: ' + data.biasZ);
     }
   );
-
   ```
 
 ### GRAVITY<sup>(deprecated)</sup>
@@ -4559,7 +4531,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[GravityResponse](#gravityresponse)&gt; | Yes       | One-shot callback used to return the gravity sensor data. The reported data type in the callback is **GravityResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_GRAVITY, function(data) {
       console.info('X-coordinate component: ' + data.x);
@@ -4567,7 +4538,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
       console.info('Z-coordinate component: ' + data.z);
     }
   );
-
   ```
 
 ### GYROSCOPE<sup>(deprecated)</sup>
@@ -4590,7 +4560,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[GyroscopeResponse](#gyroscoperesponse)&gt; | Yes       | One-shot callback used to return the gyroscope sensor data. The reported data type in the callback is **GyroscopeResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_GYROSCOPE, function(data) {
       console.info('X-coordinate component: ' + data.x);
@@ -4598,7 +4567,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
       console.info('Z-coordinate component: ' + data.z);
     }
   );
-
   ```
 
 ### GYROSCOPE_UNCALIBRATED<sup>(deprecated)</sup>
@@ -4621,7 +4589,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[GyroscopeUncalibratedResponse](#gyroscopeuncalibratedresponse)&gt; | Yes       | One-shot callback used to return the uncalibrated gyroscope sensor data. The reported data type in the callback is **GyroscopeUncalibratedResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_GYROSCOPE_UNCALIBRATED, function(data) {
       console.info('X-coordinate component: ' + data.x);
@@ -4632,7 +4599,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
       console.info('Z-coordinate bias: ' + data.biasZ);
     }
   );
-
   ```
 
 ### SIGNIFICANT_MOTION<sup>(deprecated)</sup>
@@ -4653,13 +4619,11 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[SignificantMotionResponse](#significantmotionresponse)&gt; | Yes       | One-shot callback used to return the significant motion sensor data. The reported data type in the callback is **SignificantMotionResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_SIGNIFICANT_MOTION, function(data) {
       console.info('Scalar data: ' + data.scalar);
     }
   );
-
   ```
 
 ### PEDOMETER_DETECTION<sup>(deprecated)</sup>
@@ -4682,13 +4646,11 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[PedometerDetectionResponse](#pedometerdetectionresponse)&gt; | Yes       | One-shot callback used to return the pedometer detection sensor data. The reported data type in the callback is **PedometerDetectionResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_PEDOMETER_DETECTION, function(data) {
       console.info('Scalar data: ' + data.scalar);
     }
   );
-
   ```
 
 ### PEDOMETER<sup>(deprecated)</sup>
@@ -4711,13 +4673,11 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[PedometerResponse](#pedometerresponse)&gt; | Yes       | One-shot callback used to return the pedometer sensor data. The reported data type in the callback is **PedometerResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_PEDOMETER, function(data) {
       console.info('Steps: ' + data.steps);
     }
   );
-
   ```
 
 ### AMBIENT_TEMPERATURE<sup>(deprecated)</sup>
@@ -4738,13 +4698,11 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[AmbientTemperatureResponse](#ambienttemperatureresponse)&gt; | Yes       | One-shot callback used to return the ambient temperature sensor data. The reported data type in the callback is **AmbientTemperatureResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_AMBIENT_TEMPERATURE, function(data) {
       console.info('Temperature: ' + data.temperature);
     }
   );
-
   ```
 
 ### MAGNETIC_FIELD<sup>(deprecated)</sup>
@@ -4765,7 +4723,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[MagneticFieldResponse](#magneticfieldresponse)&gt; | Yes       | One-shot callback used to return the magnetic field sensor data. The reported data type in the callback is **MagneticFieldResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_MAGNETIC_FIELD, function(data) {
       console.info('X-coordinate component: ' + data.x);
@@ -4773,7 +4730,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
       console.info('Z-coordinate component: ' + data.z);
     }
   );
-
   ```
 
 ### MAGNETIC_FIELD_UNCALIBRATED<sup>(deprecated)</sup>
@@ -4794,7 +4750,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[MagneticFieldUncalibratedResponse](#magneticfielduncalibratedresponse)&gt; | Yes       | One-shot callback used to return the uncalibrated magnetic field sensor data. The reported data type in the callback is **MagneticFieldUncalibratedResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_MAGNETIC_FIELD_UNCALIBRATED, function(data) {
       console.info('X-coordinate component: ' + data.x);
@@ -4805,7 +4760,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
       console.info('Z-coordinate bias: ' + data.biasZ);
     }
   );
-
   ```
 
 ### PROXIMITY<sup>(deprecated)</sup>
@@ -4826,13 +4780,11 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[ProximityResponse](#proximityresponse)&gt; | Yes       | One-shot callback used to return the proximity sensor data. The reported data type in the callback is **ProximityResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_PROXIMITY, function(data) {
       console.info('Distance: ' + data.distance);
     }
   );
-
   ```
 
 ### HUMIDITY<sup>(deprecated)</sup>
@@ -4853,13 +4805,11 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[HumidityResponse](#humidityresponse)&gt; | Yes       | One-shot callback used to return the humidity sensor data. The reported data type in the callback is **HumidityResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_HUMIDITY, function(data) {
       console.info('Humidity: ' + data.humidity);
     }
   );
-
   ```
 
 ### BAROMETER<sup>(deprecated)</sup>
@@ -4880,13 +4830,11 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[BarometerResponse](#barometerresponse)&gt; | Yes       | One-shot callback used to return the barometer sensor data. The reported data type in the callback is **BarometerResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_BAROMETER, function(data) {
       console.info('Atmospheric pressure: ' + data.pressure);
     }
   );
-
   ```
 
 ### HALL<sup>(deprecated)</sup>
@@ -4907,13 +4855,11 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[HallResponse](#hallresponse)&gt; | Yes       | One-shot callback used to return the Hall effect sensor data. The reported data type in the callback is **HallResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_HALL, function(data) {
       console.info('Status: ' + data.status);
     }
   );
-
   ```
 
 ### AMBIENT_LIGHT<sup>(deprecated)</sup>
@@ -4940,7 +4886,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
       console.info(' Illumination: ' + data.intensity);
     }
   );
-
   ```
 
 ### ORIENTATION<sup>(deprecated)</sup>
@@ -4961,7 +4906,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[OrientationResponse](#orientationresponse)&gt; | Yes       | One-shot callback used to return the orientation sensor data. The reported data type in the callback is **OrientationResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_ORIENTATION, function(data) {
       console.info('The device rotates at an angle around the X axis: ' + data.beta);
@@ -4969,7 +4913,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
       console.info('The device rotates at an angle around the Z axis: ' + data.alpha);
     }
   );
-
   ```
 
 ### ROTATION_VECTOR<sup>(deprecated)</sup>
@@ -4990,7 +4933,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[RotationVectorResponse](#rotationvectorresponse)&gt; | Yes       | One-shot callback used to return the rotation vector sensor data. The reported data type in the callback is **RotationVectorResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_ROTATION_VECTOR, function(data) {
       console.info('X-coordinate component: ' + data.x);
@@ -4999,7 +4941,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
       console.info('Scalar quantity: ' + data.w);
     }
   );
-
   ```
 
 ### HEART_RATE<sup>(deprecated)</sup>
@@ -5039,13 +4980,11 @@ This API is deprecated since API version 9. You are advised to use [sensor.once.
 | callback | Callback&lt;[WearDetectionResponse](#weardetectionresponse)&gt; | Yes       | One-shot callback used to return the wear detection sensor data. The reported data type in the callback is **WearDetectionResponse**. |
 
 **Example**
-
   ```js
   sensor.once(sensor.SensorType.SENSOR_TYPE_ID_WEAR_DETECTION, function(data) {
       console.info("Wear status: "+ data.value);
     }
   );
-
   ```
 
 ## sensor.off<sup>(deprecated)</sup>
@@ -5078,7 +5017,6 @@ function callback(data) {
     console.info('Z-coordinate component: ' + data.z);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_ACCELEROMETER, callback);
-
 ```
 
 ### ACCELEROMETER_UNCALIBRATED<sup>(deprecated)</sup>
@@ -5112,7 +5050,6 @@ function callback(data) {
     console.info('Z-coordinate bias: ' + data.biasZ);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_ACCELEROMETER_UNCALIBRATED, callback);
-
 ```
 
 ### AMBIENT_LIGHT<sup>(deprecated)</sup>
@@ -5139,7 +5076,6 @@ function callback(data) {
     console.info(' Illumination: ' + data.intensity);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_AMBIENT_LIGHT, callback);
-
 ```
 
 ### AMBIENT_TEMPERATURE<sup>(deprecated)</sup>
@@ -5166,7 +5102,6 @@ function callback(data) {
      console.info('Temperature: ' + data.temperature);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_AMBIENT_TEMPERATURE, callback);
-
 ```
 
 ### BAROMETER<sup>(deprecated)</sup>
@@ -5193,7 +5128,6 @@ function callback(data) {
      console.info('Atmospheric pressure: ' + data.pressure);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_BAROMETER, callback);
-
 ```
 
 ### GRAVITY<sup>(deprecated)</sup>
@@ -5222,7 +5156,6 @@ function callback(data) {
     console.info('Z-coordinate component: ' + data.z);
 }
 sensor.off( sensor.SensorType.SENSOR_TYPE_ID_GRAVITY, callback);
-
 ```
 
 ### GYROSCOPE<sup>(deprecated)</sup>
@@ -5253,7 +5186,6 @@ function callback(data) {
     console.info('Z-coordinate component: ' + data.z);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_GYROSCOPE, callback);
-
 ```
 
 ### GYROSCOPE_UNCALIBRATED<sup>(deprecated)</sup>
@@ -5284,7 +5216,6 @@ function callback(data) {
     console.info('Z-coordinate component: ' + data.z);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_GYROSCOPE_UNCALIBRATED, callback);
-
 ```
 
 ### HALL<sup>(deprecated)</sup>
@@ -5311,7 +5242,6 @@ function callback(data) {
     console.info('Status: ' + data.status);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_HALL, callback);
-
 ```
 
 ### HEART_RATE<sup>(deprecated)</sup>
@@ -5357,7 +5287,6 @@ function callback(data) {
     console.info('Humidity: ' + data.humidity);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_HUMIDITY, callback);
-
 ```
 
 ### LINEAR_ACCELERATION<sup>(deprecated)</sup>
@@ -5405,7 +5334,6 @@ function callback(data) {
     console.info('Z-coordinate component: ' + data.z);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_MAGNETIC_FIELD, callback);
-
 ```
 
 ### MAGNETIC_FIELD_UNCALIBRATED<sup>(deprecated)</sup>
@@ -5437,7 +5365,6 @@ function callback(data) {
     console.info('Z-coordinate bias: ' + data.biasZ);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_MAGNETIC_FIELD_UNCALIBRATED, callback);
-
 ```
 
 ### ORIENTATION<sup>(deprecated)</sup>
@@ -5466,7 +5393,6 @@ function callback(data) {
     console.info('The device rotates at an angle around the Z axis: ' + data.alpha);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_ORIENTATION, callback);
-
 ```
 
 ### PEDOMETER<sup>(deprecated)</sup>
@@ -5495,7 +5421,6 @@ function callback(data) {
     console.info('Steps: ' + data.steps);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_PEDOMETER, callback);
-
 ```
 
 ### PEDOMETER_DETECTION<sup>(deprecated)</sup>
@@ -5524,7 +5449,6 @@ function callback(data) {
     console.info('Scalar data: ' + data.scalar);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_PEDOMETER_DETECTION, callback);
-
 ```
 
 ### PROXIMITY<sup>(deprecated)</sup>
@@ -5551,7 +5475,6 @@ function callback(data) {
     console.info('Distance: ' + data.distance);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_PROXIMITY, callback);
-
 ```
 
 ### ROTATION_VECTOR<sup>(deprecated)</sup>
@@ -5581,7 +5504,6 @@ function callback(data) {
     console.info('Scalar quantity: ' + data.w);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_ROTATION_VECTOR, callback);
-
 ```
 
 ### SIGNIFICANT_MOTION<sup>(deprecated)</sup>
@@ -5608,7 +5530,6 @@ function callback(data) {
     console.info('Scalar data: ' + data.scalar);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_SIGNIFICANT_MOTION, callback);
-
 ```
 
 ### WEAR_DETECTION<sup>(deprecated)</sup>
@@ -5635,7 +5556,6 @@ function accCallback(data) {
     console.info('Wear status: ' + data.value);
 }
 sensor.off(sensor.SensorType.SENSOR_TYPE_ID_WEAR_DETECTION, accCallback);
-
 ```
 
 ## sensor.transformCoordinateSystem<sup>(deprecated)</sup>
@@ -5664,14 +5584,12 @@ sensor.transformCoordinateSystem([1, 0, 0, 0, 1, 0, 0, 0, 1], {x:2, y:3}, functi
         console.error("Operation failed. Error code: " + err.code + ", message: " + err.message);
         return;
     }
-    console.info("Operation successed. Data obtained: " + data);
+    console.info("Operation succeeded. Data obtained: " + data);
     for (var i=0; i < data.length; i++) {
         console.info("transformCoordinateSystem data[ " + i + "] = " + data[i]);
     }
  })
-
 ```
-
 ## sensor.transformCoordinateSystem<sup>(deprecated)</sup>
 
 transformCoordinateSystem(inRotationVector: Array&lt;number&gt;, coordinates: CoordinatesOptions): Promise&lt;Array&lt;number&gt;&gt;
@@ -5700,14 +5618,13 @@ This API is deprecated since API version 9. You are advised to use [sensor.trans
 ```js
 const promise = sensor.transformCoordinateSystem([1, 0, 0, 0, 1, 0, 0, 0, 1], {x:2, y:3});
     promise.then((data) => {
-        console.info("Operation successed.");
+        console.info("Operation succeeded.");
         for (var i=0; i < data.length; i++) {
             console.info("transformCoordinateSystem data[ " + i + "] = " + data[i]);
         }
     }).catch((err) => {
            console.info("Operation failed");
 })
-
 ```
 
 ## sensor.getGeomagneticField<sup>(deprecated)</sup>
@@ -5729,7 +5646,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.getGe
 | callback        | AsyncCallback&lt;[GeomagneticResponse](#geomagneticresponse)&gt; | Yes       | Callback used to return the geomagnetic field.               |
 
 **Example**
-
 ```js
 sensor.getGeomagneticField({latitude:80, longitude:0, altitude:0}, 1580486400000, function(err, data)  {
     if (err) {
@@ -5740,9 +5656,7 @@ sensor.getGeomagneticField({latitude:80, longitude:0, altitude:0}, 1580486400000
 	             data.z + ',geomagneticDip: ' + data.geomagneticDip + ',deflectionAngle: ' + data.deflectionAngle +
 		     ',levelIntensity: ' + data.levelIntensity + ',totalIntensity: ' + data.totalIntensity);
 });
-
 ```
-
 ## sensor.getGeomagneticField<sup>(deprecated)</sup>
 
 getGeomagneticField(locationOptions: LocationOptions, timeMillis: number): Promise&lt;GeomagneticResponse&gt;
@@ -5767,7 +5681,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.getGe
 | Promise&lt;[GeomagneticResponse](#geomagneticresponse)&gt; | Promise used to return the geomagnetic field. |
 
 **Example**
-
   ```js
   const promise = sensor.getGeomagneticField({latitude:80, longitude:0, altitude:0}, 1580486400000);
       promise.then((data) => {
@@ -5777,7 +5690,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.getGe
       }).catch((reason) => {
           console.info('Operation failed.');
   })
-
   ```
 
 ## sensor.getAltitude<sup>(deprecated)</sup>
@@ -5807,9 +5719,8 @@ This API is deprecated since API version 9. You are advised to use [sensor.getDe
   "Operation failed. Error code: " + err.code + ", message: " + err.message);
           return;
       }
-          console.info("Successed to get getAltitude interface get data: " + data);
+          console.info("Succeeded to get getAltitude interface get data: " + data);
   });
-
   ```
 
 ## sensor.getAltitude<sup>(deprecated)</sup>
@@ -5844,7 +5755,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.getDe
       }).catch((err) => {
           console.error("Operation failed");
   })
-
   ```
 
 
@@ -5874,9 +5784,8 @@ This API is deprecated since API version 9. You are advised to use [sensor.getIn
                         err.message);
           return;
       }
-          console.info("Successed to get getGeomagneticDip interface get data: " + data);
+          console.info("Succeeded to get getGeomagneticDip interface get data: " + data);
   })
-
   ```
 
 ## sensor.getGeomagneticDip<sup>(deprecated)</sup>
@@ -5906,11 +5815,10 @@ This API is deprecated since API version 9. You are advised to use [sensor.getIn
   ```js
   const promise = sensor.getGeomagneticDip([1, 0, 0, 0, 1, 0, 0, 0, 1]);
       promise.then((data) => {
-          console.info('getGeomagneticDip_promise successed', data);
+          console.info('getGeomagneticDip_promise succeeded', data);
       }).catch((err) => {
            console.error("Operation failed");
   })
-
   ```
 
 ## sensor. getAngleModify<sup>(deprecated)</sup>
@@ -5944,7 +5852,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.getAn
           console.info("data[" + i + "]: " + data[i]);
       }
   })
-
   ```
 
 
@@ -5976,14 +5883,13 @@ This API is deprecated since API version 9. You are advised to use [sensor.getAn
   ```js
   const promise = sensor.getAngleModify([1,0,0,0,1,0,0,0,1], [1,0,0,0,0.87,-0.50,0,0.50,0.87]);
       promise.then((data) => {
-          console.info('getAngleModifiy_promise success');
+          console.info('getAngleModify_promise success');
           for (var i=0; i < data.length; i++) {
               console.info("data[" + i + "]: " + data[i]);
           }
       }).catch((reason) => {
           console.info("promise::catch", reason);
   })
-
   ```
 
 
@@ -6017,7 +5923,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.getRo
           console.info("data[" + i + "]: " + data[i]);
       }
   })
-
   ```
 
 
@@ -6055,7 +5960,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.getRo
       }).catch((reason) => {
           console.info("promise::catch", reason);
   })	
-
   ```
 
 
@@ -6089,7 +5993,6 @@ This API is deprecated since API version 9. You are advised to use [sensor.getQu
           console.info("data[" + i + "]: " + data[i]);
       }
   })
-
   ```
 
 
@@ -6120,14 +6023,13 @@ This API is deprecated since API version 9. You are advised to use [sensor.getQu
   ```js
   const promise = sensor.createQuaternion([0.20046076, 0.21907, 0.73978853, 0.60376877]);
       promise.then((data) => {
-          console.info('createQuaternion_promise successed');
+          console.info('createQuaternion_promise succeeded');
           for (var i=0; i < data.length; i++) {
               console.info("data[" + i + "]: " + data[i]);
           }
       }).catch((err) => {
           console.info('promise failed');
   })
-
   ```
 
 
@@ -6157,12 +6059,11 @@ This API is deprecated since API version 9. You are advised to use [sensor.getOr
                         err.message);
           return;
       }
-      console.info("SensorJsAPI--->Successed to get getDirection interface get data: " + data);
+      console.info("SensorJsAPI--->Succeeded to get getDirection interface get data: " + data);
       for (var i = 1; i < data.length; i++) {
           console.info("sensor_getDirection_callback" + data[i]);
       }
   })
-
   ```
 
 
diff --git a/en/application-dev/reference/apis/js-apis-stack.md b/en/application-dev/reference/apis/js-apis-stack.md
index 46b06f608af9615bbb138bc54d82cab7f566c0fa..9ecf69bced25271e1c68299bb78e2a19bbaab756 100644
--- a/en/application-dev/reference/apis/js-apis-stack.md
+++ b/en/application-dev/reference/apis/js-apis-stack.md
@@ -1,8 +1,5 @@
 # @ohos.util.Stack (Linear Container Stack)
 
-> **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.
-
 **Stack** is implemented based on the array data structure. It follows the principle Last Out First In (LOFI) and supports data insertion and removal at one end.
 
 Unlike **[Queue](js-apis-queue.md)**, which is implemented based on the queue data structure and supports insertion at one end and removal at the other end, **Stack** supports insertion and removal at the same end.
@@ -12,6 +9,11 @@ Unlike **[Queue](js-apis-queue.md)**, which is implemented based on the queue da
 This topic uses the following to identify the use of generics:
 - T: Type
 
+> **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
 
 ```ts
diff --git a/en/application-dev/reference/apis/js-apis-stationary.md b/en/application-dev/reference/apis/js-apis-stationary.md
index e065e9478c631af8cc3cfe125ac71f29e2b9dadb..6c2ec0a365b1224274e760a8bc5dcbea97aa176d 100644
--- a/en/application-dev/reference/apis/js-apis-stationary.md
+++ b/en/application-dev/reference/apis/js-apis-stationary.md
@@ -123,7 +123,7 @@ Unsubscribes from the device status.
 | -------------------- | -------------------------------------------------- | ---- | ---------------------------- |
 | activity  | [ActivityType](#activitytype)  | Yes  | Device status type.             |
 | event  | [ActivityEvent](#activityevent)  | Yes  | Event type.             |
-| callback             | Callback<[ActivityResponse](#activityresponse)\>  | No  | Callback used to receive reported data.   |
+| callback             | Callback<[ActivityResponse](#activityresponse)\>  | No  | Callback used to receive reported data, if the callback parameter is not passed, all callbacks subscribed to this type under this process will be removed.   |
 
 **Example**
 
diff --git a/en/application-dev/reference/apis/js-apis-treemap.md b/en/application-dev/reference/apis/js-apis-treemap.md
index 473b5cb99e94c1ab84069d23591b63555bfcb7d5..f05edc6533e92d21c49cf1dd2c91b7e9aa12ff0a 100644
--- a/en/application-dev/reference/apis/js-apis-treemap.md
+++ b/en/application-dev/reference/apis/js-apis-treemap.md
@@ -18,6 +18,7 @@ This topic uses the following to identify the use of generics:
 >
 > 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
 
 ```ts
@@ -126,9 +127,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let treeMap = new TreeMap();
-let result = treeMap.hasKey("squirrel");
 treeMap.set("squirrel", 123);
-let result1 = treeMap.hasKey("squirrel");
+let result = treeMap.hasKey("squirrel");
 ```
 
 
@@ -164,9 +164,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let treeMap = new TreeMap();
-let result = treeMap.hasValue(123);
 treeMap.set("squirrel", 123);
-let result1 = treeMap.hasValue(123);
+let result = treeMap.hasValue(123);
 ```
 
 
@@ -304,7 +303,7 @@ let map = new TreeMap();
 map.set("demo", 12);
 map.setAll(treeMap); // Add all elements in the treeMap to the map.
 map.forEach((value, key) => {
-    console.log("test" + value, key); // Print result: 12 demo, 356 sparrow, and 123 squirrel
+  console.log("value" + value, "key" + key); // Print result: 12 demo, 356 sparrow, and 123 squirrel
 })
 ```
 
@@ -380,7 +379,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 let treeMap = new TreeMap();
 treeMap.set("squirrel", 123);
 treeMap.set("sparrow", 356);
-treeMap.remove("sparrow");
+let result = treeMap.remove("sparrow");
 ```
 
 
diff --git a/en/application-dev/reference/apis/js-apis-treeset.md b/en/application-dev/reference/apis/js-apis-treeset.md
index 5ca493adcae4ff144341f04d9d1641035ae98db8..b3259d3ccbf19fab20c027accad98c6519bf7f52 100644
--- a/en/application-dev/reference/apis/js-apis-treeset.md
+++ b/en/application-dev/reference/apis/js-apis-treeset.md
@@ -14,6 +14,7 @@ This topic uses the following to identify the use of generics:
 >
 > 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
 
 ```ts
@@ -122,9 +123,8 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 
 ```ts
 let treeSet = new TreeSet();
-treeSet.has(123);
 treeSet.add(123);
-let result1 = treeSet.has(123);
+let result = treeSet.has(123);
 ```
 
 
diff --git a/en/application-dev/reference/apis/js-apis-uri.md b/en/application-dev/reference/apis/js-apis-uri.md
index a8aed60f4a0bf23080f223eec440742847a258aa..78711db7ce38b363f068e679ce9c25187ebb414c 100644
--- a/en/application-dev/reference/apis/js-apis-uri.md
+++ b/en/application-dev/reference/apis/js-apis-uri.md
@@ -145,7 +145,7 @@ Obtains the query string applicable to this URI.
 
 ```js
 const result = new uri.URI('https://username:password@host:8080/directory/file?query=pppppp#qwer=da');
-result.toString()
+let result1 = result.toString();
 ```
 
 
@@ -205,7 +205,7 @@ Checks whether this URI is the same as another URI object.
 ```js
 const uriInstance = new uri.URI('https://username:password@host:8080/directory/file?query=pppppp#qwer=da');
 const uriInstance1 = new uri.URI('https://username:password@host:8080/directory/file?query=pppppp#qwer=da');
-uriInstance.equalsTo(uriInstance1);
+let result = uriInstance.equalsTo(uriInstance1);
 ```
 
 ### checkIsAbsolute
diff --git a/en/application-dev/reference/apis/js-apis-url.md b/en/application-dev/reference/apis/js-apis-url.md
index 6430002af209a0035cc65548c2d6cfaefcc58c7e..baeb122c19fccf1a1005b46e98604cb883976256 100755
--- a/en/application-dev/reference/apis/js-apis-url.md
+++ b/en/application-dev/reference/apis/js-apis-url.md
@@ -225,7 +225,7 @@ Checks whether a key has a value.
 ```js
 let urlObject = Url.URL.parseURL('https://developer.exampleUrl/?fod=1&bard=2');
 let paramsObject = new Url.URLParams(urlObject.search.slice(1)); 
-paramsObject.has('bard') === true;
+let result = paramsObject.has('bard');
 ```
 
 
@@ -336,7 +336,7 @@ Obtains an ES6 iterator. Each item of the iterator is a JavaScript array, and th
 
 ```js
 const paramsObject = new Url.URLParams('fod=bay&edg=bap');
-for (const [name, value] of paramsObject) {
+for (const [name, value] of paramsObject[Symbol.iterator]()) {
     console.log(name, value); 
 } 
 ```
@@ -460,7 +460,7 @@ For details about the error codes, see [Utils Error Codes](../errorcodes/errorco
 ```js
 let mm = 'https://username:password@host:8080';
 let url = Url.URL.parseURL(mm); 
-url.toString(); // Output 'https://username:password@host:8080/';
+let result = url.toString(); // Output 'https://username:password@host:8080/'
 ```
 
 ### tostring
@@ -481,7 +481,7 @@ Converts the parsed URL into a string.
 
 ```js
 const url = Url.URL.parseURL('https://username:password@host:8080/directory/file?query=pppppp#qwer=da');
-url.toString();
+let result = url.toString();
 ```
 
 ### toJSON
@@ -501,7 +501,7 @@ Converts the parsed URL into a JSON string.
 **Example**
 ```js
 const url = Url.URL.parseURL('https://username:password@host:8080/directory/file?query=pppppp#qwer=da');
-url.toJSON();
+let result = url.toJSON();
 ```
 
 ## URLSearchParams<sup>(deprecated)</sup>
diff --git a/en/application-dev/reference/apis/js-apis-usbManager.md b/en/application-dev/reference/apis/js-apis-usbManager.md
index b4dd81002e3cd18ffbbd6ab0af635ccd8d23a6c4..5121c3945dc9736acbfde49f6d351be870c58371 100644
--- a/en/application-dev/reference/apis/js-apis-usbManager.md
+++ b/en/application-dev/reference/apis/js-apis-usbManager.md
@@ -30,7 +30,7 @@ Obtains the list of USB devices connected to the host. If no device is connected
 
 ```js
 let devicesList = usb.getDevices();
-cconsole.log(`devicesList = ${devicesList}`);
+console.log(`devicesList = ${devicesList}`);
 // devicesList is a list of USB devices.
 // A simple example of devicesList is provided as follows:
 [
@@ -210,7 +210,7 @@ Removes the permission for the application to access a USB device.
 
 ```js
 let devicesName="1-1";
-if usb.removeRight(devicesName) {
+if (usb.removeRight(devicesName)) {
   console.log(`Succeed in removing right`);
 }
 ```
@@ -245,7 +245,7 @@ Adds the permission for the application to access a USB device.
 ```js
 let devicesName = "1-1";
 let bundleName = "com.example.hello";
-if usb.addRight(bundleName, devicesName) {
+if (usb.addRight(bundleName, devicesName)) {
   console.log(`Succeed in adding right`);
 }
 ```
@@ -454,7 +454,14 @@ Before you do this, call [usb.getDevices](#usbgetdevices) to obtain the USB devi
 **Example**
 
 ```js
-let param = new usb.USBControlParams();
+let param = {
+  request: 0,
+  reqType: 0,
+  target:0,
+  value: 0,
+  index: 0,
+  data: null
+};
 usb.controlTransfer(devicepipe, param).then((ret) => {
  console.log(`controlTransfer = ${ret}`);
 })
@@ -579,7 +586,7 @@ Converts the USB function list in the numeric mask format to a string in Device
 **Example**
 
 ```js
-let funcs = usb.ACM | usb.ECM;
+let funcs = usb.FunctionType.ACM | usb.FunctionType.ECM;
 let ret = usb.usbFunctionsToString(funcs);
 ```
 
@@ -608,7 +615,7 @@ Sets the current USB function list in Device mode.
 **Example**
 
 ```js
-let funcs = usb.HDC;
+let funcs = usb.FunctionType.HDC;
 usb.setCurrentFunctions(funcs).then(() => {
     console.info('usb setCurrentFunctions successfully.');
 }).catch(err => {
diff --git a/en/application-dev/reference/apis/js-apis-util.md b/en/application-dev/reference/apis/js-apis-util.md
index 16a80bd27e4c9b89397afcaaa83d098fe91eaa10..1a60dc51ae1404aee3947f799c166180ac13dde2 100755
--- a/en/application-dev/reference/apis/js-apis-util.md
+++ b/en/application-dev/reference/apis/js-apis-util.md
@@ -1,6 +1,6 @@
 # @ohos.util (util)
 
-The **util** module provides common utility functions, such as **TextEncoder** and **TextDecoder** for string encoding and decoding, **RationalNumber** for rational number operations, **LruBuffer** for buffer management, **Scope** for range determination, **Base64** for Base64 encoding and decoding, and **Types** for checks of built-in object types.
+The **util** module provides common utility functions, such as [TextEncoder](#textencoder) and [TextDecoder](#textdecoder) for string encoding and decoding, [RationalNumber<sup>8+</sup>](#rationalnumber8) for rational number operations, [LRUCache<sup>9+</sup>](#lrucache9) for cache management, [ScopeHelper<sup>9+</sup>](#scopehelper9) for range determination, [Base64Helper<sup>9+</sup>](#base64helper9) for Base64 encoding and decoding, and [types<sup>8+</sup>](#types8) for built-in object type check.
 
 > **NOTE**
 >
@@ -337,6 +337,8 @@ Processes an asynchronous function and returns a promise.
 
 ## TextDecoder
 
+Provides APIs to decode byte arrays into strings. It supports multiple formats, including UTF-8, UTF-16LE, UTF-16BE, ISO-8859, and Windows-1251.
+
 ### Attributes
 
 **System capability**: SystemCapability.Utils.Lang
@@ -367,15 +369,15 @@ Creates a **TextDecoder** object. It provides the same function as the deprecate
 
 | Name  | Type  | Mandatory| Description                                            |
 | -------- | ------ | ---- | ------------------------------------------------ |
-| encoding | string | No  | Encoding format.                                      |
+| encoding | string | No  | Encoding format. The default format is **'utf-8'**.                     |
 | options  | Object | No  | Encoding-related options, which include **fatal** and **ignoreBOM**.|
 
 **Table 1.1** options
 
 | Name     | Type| Mandatory| Description              |
 | --------- | -------- | ---- | ------------------ |
-| fatal     | boolean  | No  | Whether to display fatal errors.|
-| ignoreBOM | boolean  | No  | Whether to ignore the BOM. |
+| fatal     | boolean  | No  | Whether to display fatal errors. The default value is **false**.|
+| ignoreBOM | boolean  | No  | Whether to ignore the BOM. The default value is **false**. |
 
 **Example**
 
@@ -443,15 +445,15 @@ A constructor used to create a **TextDecoder** object.
 
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
-| encoding | string | No| Encoding format.|
+| encoding | string | No| Encoding format. The default format is **'utf-8'**.|
 | options | Object | No| Encoding-related options, which include **fatal** and **ignoreBOM**.|
 
   **Table 1** options
 
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
-| fatal | boolean | No| Whether to display fatal errors.|
-| ignoreBOM | boolean | No| Whether to ignore the BOM.|
+| fatal | boolean | No| Whether to display fatal errors. The default value is **false**.|
+| ignoreBOM | boolean | No| Whether to ignore the BOM. The default value is **false**.|
 
 **Example**
 
@@ -508,13 +510,15 @@ Decodes the input content.
 
 ## TextEncoder
 
+Provides APIs to encode strings into byte arrays. It supports multiple formats, including UTF-8, UTF-16LE, and UTF-16BE. When **TextEncoder** is used for encoding, the number of bytes occupied by a character varies according to the encoding format. For example, a Chinese character usually occupies three bytes in UTF-8 encoding format but two bytes in UTF-16LE or UTF-16BE encoding format. Therefore, when using **TextEncoder**, you must explicitly specify the encoding format to obtain the required encoding result.
+
 ### Attributes
 
 **System capability**: SystemCapability.Utils.Lang
 
 | Name| Type| Readable| Writable| Description|
 | -------- | -------- | -------- | -------- | -------- |
-| encoding | string | Yes| No| Encoding format. The default format is **utf-8**.|
+| encoding | string | Yes| No| Encoding format. The default format is **'utf-8'**.|
 
 
 ### constructor
@@ -679,6 +683,8 @@ Encodes the input content.
 
 ## RationalNumber<sup>8+</sup>
 
+Provides APIs to compare rational numbers and obtain numerators and denominators. For example, the **toString()** API can be used to convert a rational number into a strings.
+
 ### constructor<sup>9+</sup>
 
 constructor()
@@ -1063,6 +1069,8 @@ let result = util.RationalNumber.getCommonDivisor(4,6);
 
 ## LRUCache<sup>9+</sup>
 
+Provides APIs to discard the least recently used data to make rooms for new elements when the cache is full. This class uses the Least Recently Used (LRU) algorithm, which believes that the recently used data may be accessed again in the near future and the least accessed data is the least valuable data and should be removed from the cache.
+
 ### Attributes
 
 **System capability**: SystemCapability.Utils.Lang
@@ -1119,7 +1127,7 @@ Changes the **LruCache** capacity. If the new capacity is less than or equal to
 
 ```js
 let pro = new util.LRUCache();
-let result = pro.updateCapacity(100);
+pro.updateCapacity(100);
 ```
 
 
@@ -1668,6 +1676,8 @@ Defines the type of values in a **Scope** object.
 
 ## ScopeHelper<sup>9+</sup>
 
+Provides APIs to define the valid range of a field. The constructor of this class creates comparable objects with lower and upper limits.
+
 ### constructor<sup>9+</sup>
 
 constructor(lowerObj: ScopeType, upperObj: ScopeType)
@@ -1954,7 +1964,7 @@ let tempLower = new Temperature(30);
 let tempUpper = new Temperature(40);
 let tempMiDF = new Temperature(35);
 let range = new util.ScopeHelper(tempLower, tempUpper);
-range.contains(tempMiDF);
+let result = range.contains(tempMiDF);
   ```
 
 
@@ -2023,6 +2033,8 @@ let result = range.clamp(tempMiDF);
 
 ## Base64Helper<sup>9+</sup>
 
+The Base64 encoding table contains 62 characters, which are the uppercase letters (A-Z), lowercase letters (a-z), digits (0-9), and the special characters plus sign (+) and slash (/). During encoding, the original data is divided into groups of three bytes, and each group contains a 6-bit number. Then, the corresponding characters in the Base64 encoding table are used to represent these numbers. If the last group contains only one or two bytes, the equal sign (=) is used for padding.
+
 ### constructor<sup>9+</sup>
 
 constructor()
@@ -2224,6 +2236,8 @@ that.decode(array).then(val=>{
 
 ## types<sup>8+</sup>
 
+Provides APIs to check different types of built-in objects, such as ArrayBuffer, Map, and Set, so as to avoid exceptions or crashes caused by type errors.
+
 ### constructor<sup>8+</sup>
 
 constructor()
diff --git a/en/application-dev/reference/apis/js-apis-zlib.md b/en/application-dev/reference/apis/js-apis-zlib.md
index d46de34f5ea8479c56fe9e0ef37fc1b8bb331a3c..454cca88f82548b86ba2a9b4209c1782cc0eaa8f 100644
--- a/en/application-dev/reference/apis/js-apis-zlib.md
+++ b/en/application-dev/reference/apis/js-apis-zlib.md
@@ -232,9 +232,9 @@ Decompresses a file. This API uses an asynchronous callback to return the result
 | Name                 | Type               | Mandatory| Description                                                        |
 | ----------------------- | ------------------- | ---- | ------------------------------------------------------------ |
 | inFile                  | string              | Yes  | Path of the file to decompress. For details about the path, see [FA Model](js-apis-inner-app-context.md) and [Stage Model](js-apis-inner-application-context.md).|
-| outFile                 | string              | Yes  | Path of the decompressed file.                                    |
+| outFile                 | string              | Yes  | Path of the decompressed file. The path must exist in the system. Otherwise, the decompression fails. The path must be an application sandbox path, which can be obtained from the context. For details about the context, see [FA Model](js-apis-inner-app-context.md) and [Stage Model](js-apis-inner-application-context.md).|
 | options                 | [Options](#options) | Yes  | Decompression parameters.                                            |
-| AsyncCallback<**void**> | callback            | No  | Callback used to return the result. If the operation is successful, **null** is returned; otherwise, a specific error code is returned.                                          |
+| AsyncCallback<**void**> | callback            | No  | Callback used to return the result. If the operation is successful, **null** is returned; otherwise, a specific error code is returned.                                            |
 
 **Error codes**
 
@@ -283,8 +283,8 @@ Decompresses a file. This API uses a promise to return the result.
 | Name | Type               | Mandatory| Description                                                        |
 | ------- | ------------------- | ---- | ------------------------------------------------------------ |
 | inFile  | string              | Yes  | Path of the file to decompress. For details about the path, see [FA Model](js-apis-inner-app-context.md) and [Stage Model](js-apis-inner-application-context.md).|
-| outFile | string              | Yes  | Path of the decompressed file.                                      |
-| options | [Options](#options) | Yes  | Decompression parameters.                                            |
+| outFile | string              | Yes  | Path of the decompressed file. The path must exist in the system. Otherwise, the decompression fails. The path must be an application sandbox path, which can be obtained from the context. For details about the context, see [FA Model](js-apis-inner-app-context.md) and [Stage Model](js-apis-inner-application-context.md).|
+| options | [Options](#options) | Yes  | Decompression parameters.                                          |
 
 **Error codes**
 
diff --git a/en/application-dev/reference/arkui-ts/Readme-EN.md b/en/application-dev/reference/arkui-ts/Readme-EN.md
index 9d70349a99bd77bc8a32d353c85770bda41355aa..e94a5832f701d6a44b0ba6252e6011a2711fd403 100644
--- a/en/application-dev/reference/arkui-ts/Readme-EN.md
+++ b/en/application-dev/reference/arkui-ts/Readme-EN.md
@@ -124,6 +124,7 @@
   - [Swiper](ts-container-swiper.md)
   - [Tabs](ts-container-tabs.md)
   - [TabContent](ts-container-tabcontent.md)
+  - [WaterFlow](ts-container-waterflow.md)
 - Media Components
   - [Video](ts-media-components-video.md)
 - Drawing Components
diff --git a/en/application-dev/reference/arkui-ts/figures/en-us_image_0000001232775585.gif b/en/application-dev/reference/arkui-ts/figures/en-us_image_0000001232775585.gif
new file mode 100644
index 0000000000000000000000000000000000000000..36e5cf928d08d719eab8bb0c417da0bc23472798
Binary files /dev/null and b/en/application-dev/reference/arkui-ts/figures/en-us_image_0000001232775585.gif differ
diff --git a/en/application-dev/reference/arkui-ts/figures/en-us_image_0000001256978369.gif b/en/application-dev/reference/arkui-ts/figures/en-us_image_0000001256978369.gif
deleted file mode 100644
index 070ae9d042d5211b2ccc6c187ec0f87a90d2c963..0000000000000000000000000000000000000000
Binary files a/en/application-dev/reference/arkui-ts/figures/en-us_image_0000001256978369.gif and /dev/null differ
diff --git a/en/application-dev/reference/arkui-ts/ts-basic-components-image.md b/en/application-dev/reference/arkui-ts/ts-basic-components-image.md
index a53546a07c3a570f44824f72114f300ad8f60d3c..ef42e734ffcbfe7d5b6b961c3ac2df4278cc5a1e 100644
--- a/en/application-dev/reference/arkui-ts/ts-basic-components-image.md
+++ b/en/application-dev/reference/arkui-ts/ts-basic-components-image.md
@@ -27,33 +27,34 @@ Since API version 9, this API is supported in ArkTS widgets.
 
 **Parameters**
 
-| Name| Type                                                    | Mandatory| Description                                                    |
-| ------ | ------------------------------------------------------------ | ---- | ------------------------------------------------------------ |
-| src    | string\| [PixelMap](../apis/js-apis-image.md#pixelmap7) \| [Resource](ts-types.md#resource) | Yes  | Image source. Both local and online images are supported.<br>When using an image referenced using a relative path, for example, **Image("common/test.jpg")**, the **\<Image>** component cannot be called across bundles or modules. Therefore, you are advised to use **\$r** to reference image resources that need to be used globally.<br>- The following image formats are supported: PNG, JPG, BMP, SVG, GIF.<br>\- Base64 strings are supported. The value format is data:image/[png\|jpeg\|bmp\|webp];base64,[base64 data], where [base64 data] is a Base64 string.<br/>\- Strings with the **datashare://** path prefix are supported, which are used to access the image path provided by a Data ability. Before loading images, the application must [request the required permissions](../../file-management/medialibrary-overview.md#requesting-permissions).<br/>\- Strings with the **file:///data/storage** prefix are supported, which are used to read image resources in the **files** folder in the installation directory of the application. Ensure that the application has the read permission to the files in the specified path.<br/>- ArkTS widgets do not support the **http://**, **datashare://**, or **file://data/storage** path prefixes.<br>- ArkTS widgets do not support the [PixelMap](../apis/js-apis-image.md#pixelmap7) type.|
+| Name | Type                                    | Mandatory  | Description                                    |
+| ---- | ---------------------------------------- | ---- | ---------------------------------------- |
+| src  | [PixelMap](../apis/js-apis-image.md#pixelmap7) \| [Resource](ts-types.md#resource) | Yes   | Image source. Both local and online images are supported.<br>When using an image referenced using a relative path, for example, **Image("common/test.jpg")**, the **\<Image>** component cannot be called across bundles or modules. Therefore, you are advised to use **\$r** to reference image resources that need to be used globally.<br>- The following image formats are supported: PNG, JPG, BMP, SVG, GIF.<br>\- Base64 strings are supported. The value format is data:image/[png\|jpeg\|bmp\|webp];base64,[base64 data], where [base64 data] is a Base64 string.<br/>\- Strings with the **datashare://** path prefix are supported, which are used to access the image path provided by a Data ability.<br/>\- Strings with the **file:///data/storage** prefix are supported, which are used to read image resources in the **files** folder in the installation directory of the application. Ensure that the application has the read permission to the files in the specified path.<br/>**NOTE**<br/>- ArkTS widgets support GIF images, but the images are played only once when they are displayed.<br/>- ArkTS widgets do not support the **http://**, **datashare://**, or **file://data/storage** path prefixes.<br>- ArkTS widgets do not support the [PixelMap](../apis/js-apis-image.md#pixelmap7) type. |
 
 ## Attributes
 
 In addition to the [universal attributes](ts-universal-attributes-size.md), the following attributes are supported.
 
-| Name                 | Type                                               | Description                                                        |
-| --------------------- | ------------------------------------------------------- | ------------------------------------------------------------ |
-| alt                   | string \| [Resource](ts-types.md#resource)| Placeholder image displayed during loading. Local images are supported.<br>Since API version 9, this API is supported in ArkTS widgets.|
-| objectFit             | [ImageFit](ts-appendix-enums.md#imagefit)                           | Image scale mode.<br>Default value: **ImageFit.Cover**<br>Since API version 9, this API is supported in ArkTS widgets.|
-| objectRepeat          | [ImageRepeat](ts-appendix-enums.md#imagerepeat)         | Whether the image is repeated.<br>Default value: **ImageRepeat.NoRepeat**<br>Since API version 9, this API is supported in ArkTS widgets.<br>**NOTE**<br>This attribute is not applicable to SVG images.|
-| interpolation         | [ImageInterpolation](#imageinterpolation)               | Interpolation effect of the image. This attribute is intended to alleviate aliasing that occurs when a low-definition image is zoomed in.<br>Default value: **ImageInterpolation.None**<br>Since API version 9, this API is supported in ArkTS widgets.<br>**NOTE**<br>This attribute is not applicable to SVG images.<br>This attribute is not applicable to **PixelMap** objects.|
-| renderMode            | [ImageRenderMode](#imagerendermode)                     | Rendering mode of the image.<br>Default value: **ImageRenderMode.Original**<br>Since API version 9, this API is supported in ArkTS widgets.<br>**NOTE**<br>This attribute is not applicable to SVG images.|
-| sourceSize            | {<br>width: number,<br>height: number<br>} | Size of the decoded image. The original image is decoded into a **pixelMap** of the specified size, in px.<br>Since API version 9, this API is supported in ArkTS widgets.<br>**NOTE**<br>This attribute is not applicable to **PixelMap** objects or SVG images.|
-| matchTextDirection     | boolean | Whether to display the image in the system language direction. When this parameter is set to true, the image is horizontally flipped in the right-to-left (RTL) language context.<br>Default value: **false**<br>Since API version 9, this API is supported in ArkTS widgets.|
-| fitOriginalSize        | boolean | Whether to fit the component to the original size of the image source when the component size is not set.<br>Default value: **false**<br>Since API version 9, this API is supported in ArkTS widgets.|
-| fillColor              | [ResourceColor](ts-types.md#resourcecolor) | Fill color. This attribute only applies to an SVG image. Once set, the fill color will replace that of the SVG image.<br>Since API version 9, this API is supported in ArkTS widgets.|
-| autoResize             | boolean | Whether to resize the image source used for drawing based on the size of the display area during image decoding. This resizing can help reduce the memory usage.<br>Default value: **true**<br>Since API version 9, this API is supported in ArkTS widgets.|
-| syncLoad<sup>8+</sup> | boolean                                  | Whether to load the image synchronously. By default, the image is loaded asynchronously. During synchronous loading, the UI thread is blocked and the placeholder diagram is not displayed.<br>Default value: **false**<br>Since API version 9, this API is supported in ArkTS widgets.|
-| copyOption<sup>9+</sup> | [CopyOptions](ts-appendix-enums.md#copyoptions9)  | Whether the image can be copied. (SVG images cannot be copied.)<br>When **copyOption** is set to a value other than **CopyOptions.None**, the image can be copied in various manners, such as long pressing, right-clicking, or pressing Ctrl+C.<br>Default value: **CopyOptions.None**<br>This API is supported in ArkTS widgets.|
-| colorFilter<sup>9+</sup> | [ColorFilter](ts-types.md#colorfilter9) | Color filter of the image.<br>This API is supported in ArkTS widgets.|
+| Name                      | Type                                    | Description                                      |
+| ------------------------ | ---------------------------------------- | ---------------------------------------- |
+| alt                      | string \| [Resource](ts-types.md#resource)| Placeholder image displayed during loading. Local images are supported.<br>Since API version 9, this API is supported in ArkTS widgets.|
+| objectFit                | [ImageFit](ts-appendix-enums.md#imagefit) | Image scale mode.<br>Default value: **ImageFit.Cover**<br>Since API version 9, this API is supported in ArkTS widgets.|
+| objectRepeat             | [ImageRepeat](ts-appendix-enums.md#imagerepeat) | Whether the image is repeated.<br>Default value: **ImageRepeat.NoRepeat**<br>Since API version 9, this API is supported in ArkTS widgets.<br>**NOTE**<br>This attribute is not applicable to SVG images.|
+| interpolation            | [ImageInterpolation](#imageinterpolation) | Interpolation effect of the image. This attribute is intended to alleviate aliasing that occurs when a low-definition image is zoomed in.<br>Default value: **ImageInterpolation.None**<br>Since API version 9, this API is supported in ArkTS widgets.<br>**NOTE**<br>This attribute is not applicable to SVG images.<br>This attribute is not applicable to **PixelMap** objects.|
+| renderMode               | [ImageRenderMode](#imagerendermode)      | Rendering mode of the image.<br>Default value: **ImageRenderMode.Original**<br>Since API version 9, this API is supported in ArkTS widgets.<br>**NOTE**<br>This attribute is not applicable to SVG images.|
+| sourceSize               | {<br>width: number,<br>height: number<br>} | Size of the decoded image. The original image is decoded into a **pixelMap** of the specified size, in px.<br>Since API version 9, this API is supported in ArkTS widgets.<br>**NOTE**<br>This attribute is not applicable to **PixelMap** objects or SVG images.|
+| matchTextDirection       | boolean                                  | Whether to display the image in the system language direction. When this parameter is set to true, the image is horizontally flipped in the right-to-left (RTL) language context.<br>Default value: **false**<br>Since API version 9, this API is supported in ArkTS widgets.|
+| fitOriginalSize          | boolean                                  | Whether to fit the component to the original size of the image source when the component size is not set.<br>Default value: **false**<br>Since API version 9, this API is supported in ArkTS widgets.|
+| fillColor                | [ResourceColor](ts-types.md#resourcecolor) | Fill color. This attribute only applies to an SVG image. Once set, the fill color will replace that of the SVG image.<br>Since API version 9, this API is supported in ArkTS widgets.|
+| autoResize               | boolean                                  | Whether to resize the image source used for drawing based on the size of the display area during image decoding. This resizing can help reduce the memory usage.<br>Default value: **true**<br>Since API version 9, this API is supported in ArkTS widgets.|
+| syncLoad<sup>8+</sup>    | boolean                                  | Whether to load the image synchronously. By default, the image is loaded asynchronously. During synchronous loading, the UI thread is blocked and the placeholder diagram is not displayed.<br>Default value: **false**<br>Since API version 9, this API is supported in ArkTS widgets.|
+| copyOption<sup>9+</sup>  | [CopyOptions](ts-appendix-enums.md#copyoptions9) | Whether the image can be copied. (SVG images cannot be copied.)<br>When **copyOption** is set to a value other than **CopyOptions.None**, the image can be copied in various manners, such as long pressing, right-clicking, or pressing Ctrl+C.<br>Default value: **CopyOptions.None**<br>This API is supported in ArkTS widgets.|
+| colorFilter<sup>9+</sup> | [ColorFilter](ts-types.md#colorfilter9)  | Color filter of the image.<br>This API is supported in ArkTS widgets.      |
 
 >  **NOTE**
 >
 >  To use shortcut keys to copy the image, the image must be in focus. To enable the image to gain focus, set both the **focusable** and **focusOnTouch** attributes to **true**.
+>
 >  For SVG images, only the following tags are included in the supported list: **svg**, **rect**, **circle**, **ellipse**, **path**, **line**, **polyline**, **polygon**, and **animate**.
 
 ### ImageInterpolation
@@ -80,11 +81,11 @@ Since API version 9, this API is supported in ArkTS widgets.
 
 In addition to the [universal events](ts-universal-events-click.md), the following events are supported.
 
-| Name                                                         | Description                                                  |
-| ------------------------------------------------------------ | ------------------------------------------------------------ |
-| onComplete(callback: (event?: { width: number, height: number, componentWidth: number,<br> componentHeight: number, loadingStatus: number }) =&gt; void) | Triggered when an image is successfully loaded. The size of the loaded image is returned.<br>- **width**: width of the image, in pixels.<br>- **height**: height of the image, in pixels.<br>- **componentWidth**: width of the container component, in pixels.<br>- **componentHeight**: height of the container component, in pixels.<br>- **loadingStatus**: image loading status. The value **1** means that the image is successfully loaded, and **0** means the opposite.<br>Since API version 9, this API is supported in ArkTS widgets. |
-| onError(callback: (event?: { componentWidth: number, componentHeight: number , message<sup>9+</sup>: string }) =&gt; void) | Triggered when an exception occurs during image loading.<br>- **componentWidth**: width of the container component, in pixels.<br>- **componentHeight**: height of the container component, in pixels.<br>Since API version 9, this API is supported in ArkTS widgets. |
-| onFinish(event: () =&gt; void)                               | Triggered when the animation playback in the loaded SVG image is complete. If the animation is an infinite loop, this callback is not triggered.<br>Since API version 9, this API is supported in ArkTS widgets. |
+| Name                                      | Description                                    |
+| ---------------------------------------- | ---------------------------------------- |
+| onComplete(callback: (event?: { width: number, height: number, componentWidth: number,<br> componentHeight: number, loadingStatus: number }) =&gt; void) | Triggered when an image is successfully loaded. The size of the loaded image is returned.<br>- **width**: width of the image, in pixels.<br>- **height**: height of the image, in pixels.<br>- **componentWidth**: width of the container component, in pixels.<br>- **componentHeight**: height of the container component, in pixels.<br>- **loadingStatus**: image loading status.<br>Since API version 9, this API is supported in ArkTS widgets.<br>**NOTE**<br>The value **1** means that the image is successfully loaded, and **0** means the opposite.|
+| onError(callback: (event?: { componentWidth: number, componentHeight: number , message<sup>9+</sup>: string }) =&gt; void) | Triggered when an exception occurs during image loading.<br>- **componentWidth**: width of the container component, in pixels.<br>- **componentHeight**: height of the container component, in pixels.<br>Since API version 9, this API is supported in ArkTS widgets.|
+| onFinish(event: () =&gt; void) | Triggered when the animation playback in the loaded SVG image is complete. If the animation is an infinite loop, this callback is not triggered.<br>Since API version 9, this API is supported in ArkTS widgets.|
 
 ## Example
 
@@ -162,7 +163,7 @@ struct ImageExample1 {
 
 ### Loading Online Images
 
-The default network timeout period is 5 minutes for loading online images. When using an online image, you are advised to use **alt** to configure the placeholder image displayed during loading. If more flexible network configuration is required, use the [HTTP](../../connectivity/http-request.md) module in the SDK to send a network request, and then decode the returned data into a **PixelMap** in the **\<Image>** component. For details about image development, see [Image Development](../../media/image.md). The code snippet is as follows:
+The default network timeout period is 5 minutes for loading online images. When using an online image, you are advised to use **alt** to configure the placeholder image displayed during loading. If more flexible network configuration is required, you can use the [HTTP](../../connectivity/http-request.md) tool provided in the SDK to send a network request, and then decode the returned data into **PixelMap** objects in the **\<Image>** component. For details about image development, see [Image Processing](../../media/image-overview.md). The code snippet is as follows:
 
 ```tsx
 // @ts-nocheck
@@ -370,7 +371,7 @@ import context from '@ohos.app.ability.common';
 struct LoadImageExample {
   @State resourcesPath: string = ''
   @State sandboxPath: string = ''
-  context: context.UIAbility = getContext(this) as context.UIAbilityContext
+  context: context.UIAbilityContext = getContext(this) as context.UIAbilityContext
 
   build() {
     Column() {
@@ -397,6 +398,12 @@ struct LoadImageExample {
       Image(this.resourcesPath)
         .width(100)
         .height(100)
+        .colorFilter([
+          0.30, 0.59, 0.11, 0, 0,
+          0.30, 0.59, 0.11, 0, 0,
+          0.30, 0.59, 0.11, 0, 0,
+          0, 0, 0, 1.0, 0
+        ])
       Text(`Sandbox image path: ${this.sandboxPath}`)
         .fontSize(20)
         .margin({ bottom: 10 })
@@ -408,3 +415,4 @@ struct LoadImageExample {
   }
 }
 ```
+<!--no_check-->
\ No newline at end of file
diff --git a/en/application-dev/reference/arkui-ts/ts-basic-components-scrollbar.md b/en/application-dev/reference/arkui-ts/ts-basic-components-scrollbar.md
index 962a2de43931dc23157f7d168de50f2843afba06..8411ca984ddf5850abb519cbdcea2113b87a2553 100644
--- a/en/application-dev/reference/arkui-ts/ts-basic-components-scrollbar.md
+++ b/en/application-dev/reference/arkui-ts/ts-basic-components-scrollbar.md
@@ -26,9 +26,9 @@ ScrollBar(value: { scroller: Scroller, direction?: ScrollBarDirection, state?: B
 
 >  **NOTE**
 >
->  The **\<ScrollBar>** component defines the behavior style of the scrollable area, and its subnodes define the behavior style of the scrollbar.
->
->  This component is bound to a scrollable component through **scroller**, and can be used to scroll the scrollable component only when their directions are the same. The **\<ScrollBar>** component can be bound to only one scrollable component, and vice versa.
+> The **\<ScrollBar>** component defines the behavior style of the scrollable area, and its subnodes define the behavior style of the scrollbar.
+> 
+> This component is bound to a scrollable component through **scroller**, and can be used to scroll the scrollable component only when their directions are the same. The **\<ScrollBar>** component can be bound to only one scrollable component, and vice versa.
 
 ## ScrollBarDirection
 
@@ -46,7 +46,7 @@ ScrollBar(value: { scroller: Scroller, direction?: ScrollBarDirection, state?: B
 @Component
 struct ScrollBarExample {
   private scroller: Scroller = new Scroller()
-  private arr: number[] = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9]
+  private arr: number[] = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15]
 
   build() {
     Column() {
@@ -56,8 +56,8 @@ struct ScrollBarExample {
             ForEach(this.arr, (item) => {
               Row() {
                 Text(item.toString())
-                  .width('90%')
-                  .height(100)
+                  .width('80%')
+                  .height(60)
                   .backgroundColor('#3366CC')
                   .borderRadius(15)
                   .fontSize(16)
@@ -65,17 +65,18 @@ struct ScrollBarExample {
                   .margin({ top: 5 })
               }
             }, item => item)
-          }.margin({ right: 52 })
+          }.margin({ right: 15 })
         }
+        .width('90%')
         .scrollBar(BarState.Off)
         .scrollable(ScrollDirection.Vertical)
         ScrollBar({ scroller: this.scroller, direction: ScrollBarDirection.Vertical,state: BarState.Auto }) {
           Text()
-            .width(30)
+            .width(20)
             .height(100)
             .borderRadius(10)
             .backgroundColor('#C0C0C0')
-        }.width(30).backgroundColor('#ededed')
+        }.width(20).backgroundColor('#ededed')
       }
     }
   }
@@ -83,4 +84,4 @@ struct ScrollBarExample {
 ```
 
 
-![en-us_image_0000001256978369](figures/en-us_image_0000001256978369.gif)
+![en-us_image_0000001232775585](figures/en-us_image_0000001232775585.gif)
diff --git a/en/application-dev/reference/arkui-ts/ts-basic-components-stepperitem.md b/en/application-dev/reference/arkui-ts/ts-basic-components-stepperitem.md
index 809b3f114fe2c2b9e0baba64f049d136d689a1cf..7427783669fc717e2b21857f16154c1fa4176817 100644
--- a/en/application-dev/reference/arkui-ts/ts-basic-components-stepperitem.md
+++ b/en/application-dev/reference/arkui-ts/ts-basic-components-stepperitem.md
@@ -28,12 +28,12 @@ StepperItem()
 
 ## ItemState
 
-|   Name   |   Value   | Description|
-| -------- | -------- |-------- |
-| Normal |  0  |The button on the right is clickable and can navigate users to the next **\<StepperItem>** when it is clicked.|
-| Disabled |  1  |The button on the right is disabled.|
-| Waiting |  2  | The button on the right is not displayed, and a progress bar is displayed instead.|
-| Skip |  3  |The button on the right reads "Skip" by default. You can define the processing logic for this state in the **onSkip** callback of the stepper.|
+|   Name   | Description|
+| -------- |-------- |
+| Normal |The button on the right is clickable and can navigate users to the next **\<StepperItem>** when it is clicked.|
+| Disabled |The button on the right is disabled.|
+| Waiting | The button on the right is not displayed, and a progress bar is displayed instead.|
+| Skip |The button on the right reads "Skip" by default. You can define the processing logic for this state in the **onSkip** callback of the stepper.|
 
 
 ## Example
diff --git a/en/application-dev/reference/arkui-ts/ts-components-canvas-lottie.md b/en/application-dev/reference/arkui-ts/ts-components-canvas-lottie.md
index 6bb371dfa5dc1e8cb3c88c9b1618e035caf8294c..58cefdf784cd120789a842d5ec794258dd89ed2a 100644
--- a/en/application-dev/reference/arkui-ts/ts-components-canvas-lottie.md
+++ b/en/application-dev/reference/arkui-ts/ts-components-canvas-lottie.md
@@ -3,7 +3,7 @@
 **Lottie** allows you to implement animation-specific operations.
 
 > **NOTE**
-> 
+>
 > The APIs of this module are supported since API version 8. Updates will be marked with a superscript to indicate their earliest API version.
 
 
@@ -16,9 +16,7 @@ import lottie from '@ohos/lottieETS'
 
 > **NOTE**
 >
-> In the **Terminal** window, run the `npm install @ohos/lottieETS` command to download Lottie. The download requires the related permission.
->
-> To install an OpenHarmony npm third-party package, run the `npm config set @ohos:registry=https://repo.harmonyos.com/npm/` command to set the repository address.
+> To use **Lottie**, download it first by running the **ohpm install @ohos/lottieETS** command in the Terminal window.
 
 
 ## lottie.loadAnimation
@@ -31,15 +29,15 @@ Loads an animation. Before calling this API, declare the **Animator('__lottie_et
 
 **Parameters**
 
-| Name          | Type                       | Mandatory| Description                                                        |
-| -------------- | --------------------------- | ---- | ------------------------------------------------------------ |
-| path           | string                      | Yes  | Path of the animation resource file in the HAP file. The resource file must be in JSON format. Example: **path: "common/lottie/data.json"**|
-| container      | object                      | Yes  | Canvas drawing context. A **CanvasRenderingContext2D** object must be declared in advance.|
-| render         | string                      | Yes  | Rendering type. The value can only be **"canvas"**.                                  |
-| loop           | boolean \| number | No  | If the value is of the Boolean type, this parameter indicates whether to repeat the animation cyclically after the animation ends; the default value is **true**. If the value is of the number type and is greater than or equal to 1, this parameter indicates the number of times the animation plays.|
-| autoplay       | boolean                     | No   | Whether to automatically play the animation.<br>Default value: **true**                          |
-| name           | string                      | No   | Custom animation name. In later versions, the name can be used to reference and control the animation.<br/>Default value: null |
-| initialSegment | [number, number]            | No   | Start frame and end frame of the animation, respectively.            |
+| Name            | Type                         | Mandatory  | Description                                      |
+| -------------- | --------------------------- | ---- | ---------------------------------------- |
+| path           | string                      | Yes   | Path of the animation resource file in the HAP file. The resource file must be in JSON format. Example: **path: "common/lottie/data.json"**|
+| container      | object                      | Yes   | Canvas drawing context. A **CanvasRenderingContext2D** object must be declared in advance.|
+| render         | string                      | Yes   | Rendering type. The value can only be **"canvas"**.                       |
+| loop           | boolean \| number | No   | If the value is of the Boolean type, this parameter indicates whether to repeat the animation cyclically after the animation ends. If the value is of the number type and is greater than or equal to 1, this parameter indicates the number of times the animation plays.<br>Default value: **true**|
+| autoplay       | boolean                     | No   | Whether to automatically play the animation<br>Default value: **true**                       |
+| name           | string                      | No   | Custom animation name. In later versions, the name can be used to reference and control the animation. <br>Default value: **""**       |
+| initialSegment | [number, number]       | No   | Start frame and end frame of the animation, respectively.                |
 
 
 ## lottie.destroy
@@ -52,10 +50,9 @@ Destroys the animation. This API must be called when a page exits. This API can
 
 | Name  | Type    | Mandatory  | Description                                      |
 | ---- | ------ | ---- | ---------------------------------------- |
-| name | string | Yes   | Name of the animation to destroy, which is the same as the **name** in the **loadAnimation** API. By default, all animations are destroyed. |
+| name | string | Yes   | Name of the animation to destroy, which is the same as the **name** in the **loadAnimation** API. By default, all animations are destroyed.|
 
 **Example** 
-
   ```ts
   // xxx.ets
   import lottie from '@ohos/lottieETS'
@@ -134,7 +131,7 @@ Plays a specified animation.
 
 | Name  | Type    | Mandatory  | Description                                      |
 | ---- | ------ | ---- | ---------------------------------------- |
-| name | string | Yes   | Name of the animation to play, which is the same as the **name** in the **loadAnimation** API. By default, all animations are played. |
+| name | string | Yes   | Name of the animation to play, which is the same as the **name** in the **loadAnimation** API. By default, all animations are played.|
 
 **Example**
 
@@ -153,7 +150,7 @@ Pauses a specified animation. The next time **lottie.play()** is called, the ani
 
 | Name  | Type    | Mandatory  | Description                                      |
 | ---- | ------ | ---- | ---------------------------------------- |
-| name | string | Yes   | Name of the animation to pause, which is the same as the **name** in the **loadAnimation** API. By default, all animations are paused. |
+| name | string | Yes   | Name of the animation to pause, which is the same as the **name** in the **loadAnimation** API. By default, all animations are paused.|
 
 **Example**
 
@@ -172,7 +169,7 @@ Pauses or plays a specified animation. This API is equivalent to the switching b
 
 | Name  | Type    | Mandatory  | Description                                      |
 | ---- | ------ | ---- | ---------------------------------------- |
-| name | string | Yes   | Name of the target animation, which is the same as the **name** in the **loadAnimation** API. By default, all animations are paused or played. |
+| name | string | Yes   | Name of the target animation, which is the same as the **name** in the **loadAnimation** API. By default, all animations are paused or played.|
 
 **Example**
 
@@ -191,7 +188,7 @@ Stops the specified animation. The next time **lottie.play()** is called, the an
 
 | Name  | Type    | Mandatory  | Description                                      |
 | ---- | ------ | ---- | ---------------------------------------- |
-| name | string | Yes   | Name of the target animation, which is the same as the **name** in the **loadAnimation** API. By default, all animations are stopped. |
+| name | string | Yes   | Name of the target animation, which is the same as the **name** in the **loadAnimation** API. By default, all animations are stopped.|
 
 **Example**
 
@@ -210,8 +207,8 @@ Sets the playback speed of the specified animation.
 
 | Name   | Type    | Mandatory  | Description                                      |
 | ----- | ------ | ---- | ---------------------------------------- |
-| speed | number | Yes   | Playback speed. The value is a floating-point number. If the value is greater than 0, the animation plays in forward direction. If the value is less than 0, the animation plays in reversed direction. If the value is **0**, the animation is paused. If the value is **1.0** or **-1.0**, the animation plays at the normal speed. |
-| name  | string | Yes   | Name of the target animation, which is the same as the **name** in the **loadAnimation** API. By default, all animations are set. |
+| speed | number | Yes   | Playback speed. The value is a floating-point number. If the value is greater than 0, the animation plays in forward direction. If the value is less than 0, the animation plays in reversed direction. If the value is **0**, the animation is paused. If the value is **1.0** or **-1.0**, the animation plays at the normal speed.|
+| name  | string | Yes   | Name of the target animation, which is the same as the **name** in the **loadAnimation** API. By default, all animations are set.|
 
 **Example**
 
@@ -231,7 +228,7 @@ Sets the direction in which the specified animation plays.
 | Name       | Type                | Mandatory  | Description                                      |
 | --------- | ------------------ | ---- | ---------------------------------------- |
 | direction | AnimationDirection | Yes   | Direction in which the animation plays. **1**: forwards; **-1**: backwards. When set to play backwards, the animation plays from the current playback progress to the first frame. When this setting is combined with **loop** being set to **true**, the animation plays backwards continuously. When the value of **speed** is less than 0, the animation also plays backwards.<br>AnimationDirection: 1 \| -1 |
-| name      | string             | Yes   | Name of the target animation, which is the same as the **name** in the **loadAnimation** API. By default, all animations are set. |
+| name      | string             | Yes   | Name of the target animation, which is the same as the **name** in the **loadAnimation** API. By default, all animations are set.|
 
 **Example**
 
@@ -254,18 +251,18 @@ Defines an **AnimationItem** object, which is returned by the **loadAnimation**
 | totalFrames       | number                                   | Total number of frames in the animation segment that is being played.                             |
 | frameRate         | number                                   | Frame rate (frame/s).                      |
 | frameMult         | number                                   | Frame rate (frame/ms).                     |
-| playSpeed         | number                                   | Playback speed. The value is a floating-point number. If the value is greater than 0, the animation plays forward. If the value is less than 0, the animation plays backward. If the value is **0**, the animation is paused. If the value is **1.0** or **-1.0**, the animation plays at the normal speed. |
-| playDirection     | number                                   | Playback direction.<br>**1**: forward.<br/>**-1**: backward. |
+| playSpeed         | number                                   | Playback speed. The value is a floating-point number. If the value is greater than 0, the animation plays forward. If the value is less than 0, the animation plays backward. If the value is **0**, the animation is paused. If the value is **1.0** or **-1.0**, the animation plays at the normal speed.|
+| playDirection     | number                                   | Playback direction.<br>**1**: forward.<br/>**-1**: backward.            |
 | playCount         | number                                   | Number of times the animation plays.                              |
 | isPaused          | boolean                                  | Whether the current animation is paused. The value **true** means that the animation is paused.            |
-| autoplay          | boolean                                  | Whether to automatically play the animation upon completion of the loading. The value **false** means that the **play()** API needs to be called to start playing. |
-| loop              | boolean \| number                        | If the value is of the Boolean type, this parameter indicates whether to repeat the animation cyclically after the animation ends. If the value is of the number type and is greater than or equal to 1, this parameter indicates the number of times the animation plays. |
+| autoplay          | boolean                                  | Whether to automatically play the animation upon completion of the loading. The value **false** means that the **play()** API needs to be called to start playing.|
+| loop              | boolean \| number              | If the value is of the Boolean type, this parameter indicates whether to repeat the animation cyclically after the animation ends. If the value is of the number type and is greater than or equal to 1, this parameter indicates the number of times the animation plays. |
 | renderer          | any                                      | Animation rendering object, which depends on the rendering type.                  |
 | animationID       | string                                   | Animation ID.                                   |
 | timeCompleted     | number                                   | Number of frames that are played for an animation sequence. The value is affected by the setting of **AnimationSegment** and is the same as the value of **totalFrames**.|
 | segmentPos        | number                                   | ID of the current animation segment. The value is a positive integer greater than or equal to 0.            |
 | isSubframeEnabled | boolean                                  | Whether the precision of **currentFrame** is a floating point number.               |
-| segments          | AnimationSegment \| AnimationSegment[]   | Current segment of the animation.                              |
+| segments          | AnimationSegment \| AnimationSegment[] | Current segment of the animation.                              |
 
 
 ## AnimationItem.play
@@ -278,7 +275,7 @@ Plays an animation.
 
 | Name  | Type    | Mandatory  | Description             |
 | ---- | ------ | ---- | --------------- |
-| name | string | No   | Name of the target animation. By default, the value is null.|
+| name | string | No   | Name of the target animation.<br>Default value: **""** |
 
 **Example**
 
@@ -373,7 +370,7 @@ Sets the playback speed of an animation.
 
 | Name   | Type    | Mandatory  | Description                                      |
 | ----- | ------ | ---- | ---------------------------------------- |
-| speed | number | Yes   | Playback speed. The value is a floating-point number. If the value is greater than 0, the animation plays forward. If the value is less than 0, the animation plays backward. If the value is **0**, the animation is paused. If the value is **1.0** or **-1.0**, the animation plays at the normal speed. |
+| speed | number | Yes   | Playback speed. The value is a floating-point number. If the value is greater than 0, the animation plays forward. If the value is less than 0, the animation plays backward. If the value is 0, the animation is paused. If the value is **1.0** or **-1.0**, the animation plays at the normal speed.|
 
 **Example**
 
@@ -412,8 +409,8 @@ Sets the animation to stop at the specified frame or time.
 | Name     | Type     | Mandatory  | Description                                      |
 | ------- | ------- | ---- | ---------------------------------------- |
 | value   | number  | Yes   | Frame ID (greater than or equal to 0) or time progress (ms) at which the animation will stop.                    |
-| isFrame | boolean | No    | Whether to set the animation to stop at the specified frame. The value **true** means to set the animation to stop at the specified frame, and **false** means to set the animation to stop at the specified time progress.<br/>Default value: **false** |
-| name    | string  | No    | Name of the target animation. By default, the value is null.                         |
+| isFrame | boolean | No   | Whether to set the animation to stop at the specified frame. The value **true** means to set the animation to stop at the specified frame, and **false** means to set the animation to stop at the specified time progress.<br>Default value: **false**|
+| name    | string  | No   | Name of the target animation. By default, the value is null.                         |
 
 **Example**
 
@@ -436,8 +433,8 @@ Sets the animation to start from the specified frame or time progress.
 | Name     | Type     | Mandatory  | Description                                      |
 | ------- | ------- | ---- | ---------------------------------------- |
 | value   | number  | Yes   | Frame ID (greater than or equal to 0) or time progress (ms) at which the animation will start.                     |
-| isFrame | boolean | Yes   | Whether to set the animation to start from the specified frame. The value **true** means to set the animation to start from the specified frame, and **false** means to set the animation to start from the specified time progress.<br/>Default value: **false** |
-| name    | string  | No    | Name of the target animation.<br/>Default value: null      |
+| isFrame | boolean | Yes   | Whether to set the animation to start from the specified frame. The value **true** means to set the animation to start from the specified frame, and **false** means to set the animation to start from the specified time progress.<br>Default value: **false**|
+| name    | string  | No   | Name of the target animation.<br>Default value: **""**                     |
 
 **Example**
 
@@ -460,7 +457,7 @@ Sets the animation to play only the specified segment.
 | Name       | Type                                      | Mandatory  | Description                                      |
 | --------- | ---------------------------------------- | ---- | ---------------------------------------- |
 | segments  | AnimationSegment = [number, number] \| AnimationSegment[] | Yes   | Segment or segment list.<br>If all segments in the segment list are played, only the last segment is played in the next cycle.|
-| forceFlag | boolean                                                   | Yes   | Whether the settings take effect immediately. The value **true** means the settings take effect immediately, and **false** means the settings take effect until the current cycle of playback is completed.          |
+| forceFlag | boolean                                  | Yes   | Whether the settings take effect immediately. The value **true** means the settings take effect immediately, and **false** means the settings take effect until the current cycle of playback is completed.          |
 
 **Example**
 
@@ -533,7 +530,7 @@ Obtains the duration (irrelevant to the playback speed) or number of frames for
 
 | Name      | Type     | Mandatory  | Description                                      |
 | -------- | ------- | ---- | ---------------------------------------- |
-| inFrames | boolean | No   | Whether to obtain the duration or number of frames.<br>**true**: number of frames.<br>**false**: duration, in ms.<br/>Default value: **false** |
+| inFrames | boolean | No   | Whether to obtain the duration or number of frames.<br>**true**: number of frames.<br>**false**: duration, in ms.<br>Default value: **false**|
 
 **Example**
 
@@ -579,7 +576,7 @@ Removes an event listener.
 | Name      | Type                             | Mandatory  | Description                                      |
 | -------- | ------------------------------- | ---- | ---------------------------------------- |
 | name     | AnimationEventName              | Yes   | Animation event type. The available options are as follows:<br>'enterFrame', 'loopComplete', 'complete', 'segmentStart', 'destroy', 'config_ready', 'data_ready', 'DOMLoaded', 'error', 'data_failed', 'loaded_images'|
-| callback | AnimationEventCallback&lt;T&gt; | No    | Custom callback. By default, the value is null, meaning that all callbacks of the event will be removed.           |
+| callback | AnimationEventCallback&lt;T&gt; | No   | Custom callback. By default, the value is null, meaning that all callbacks of the event will be removed.           |
 
 **Example**
 
diff --git a/en/application-dev/reference/arkui-ts/ts-components-summary.md b/en/application-dev/reference/arkui-ts/ts-components-summary.md
index 5bc9050761a4e913be7d1df70a4f4361cb70b468..19bc1f97eec987ec2e7b97f4507b3e8fc107f29d 100644
--- a/en/application-dev/reference/arkui-ts/ts-components-summary.md
+++ b/en/application-dev/reference/arkui-ts/ts-components-summary.md
@@ -69,6 +69,12 @@
 - [Swiper](ts-container-swiper.md)
 
     A container that is able to display child components in looping mode.
+- [WaterFlow](ts-container-waterflow.md)
+
+    A container that consists of cells formed by rows and columns and arranges items of different sizes from top to bottom according to the preset rules.
+- [FlowItem](ts-container-flowitem.md)
+
+    A child component of the **\<WaterFlow>** container that is used to display specific items in the container layout.
 
 
 ## Navigation
diff --git a/en/application-dev/reference/arkui-ts/ts-container-flowitem.md b/en/application-dev/reference/arkui-ts/ts-container-flowitem.md
new file mode 100644
index 0000000000000000000000000000000000000000..71a0bf73f8e45100ea0ae7a5f4a5533486c056b4
--- /dev/null
+++ b/en/application-dev/reference/arkui-ts/ts-container-flowitem.md
@@ -0,0 +1,31 @@
+# FlowItem
+
+
+**\<FlowItem>** is a child component of the [\<WaterFlow>](ts-container-waterflow.md) container and is used to display specific items in the container layout.
+
+
+> **NOTE**
+>
+> This component is supported since API version 9. Updates will be marked with a superscript to indicate their earliest API version.
+
+
+## Child Components
+
+
+This component supports only one child component.
+
+
+## APIs
+
+FlowItem()
+
+Ceates a child component in the **\<WaterFlow>** layout.
+
+
+## Attributes
+
+None
+
+## Example
+
+See [WaterFlow](ts-container-waterflow.md#example).
diff --git a/en/application-dev/reference/arkui-ts/ts-container-panel.md b/en/application-dev/reference/arkui-ts/ts-container-panel.md
index f67b201b355af588018e87b35e84844762444ee2..5b7e99a535dcff03853c0009140c2be50d205e87 100644
--- a/en/application-dev/reference/arkui-ts/ts-container-panel.md
+++ b/en/application-dev/reference/arkui-ts/ts-container-panel.md
@@ -11,6 +11,10 @@ The **<Panel\>** component is a slidable panel that presents lightweight content
 
 Supported
 
+>  **NOTE**
+>
+>  Built-in components and custom components are allowed, with support for ([if/else](../../quick-start/arkts-rendering-control-ifelse.md), [ForEach](../../quick-start/arkts-rendering-control-foreach.md), and [LazyForEach](../../quick-start/arkts-rendering-control-lazyforeach.md)) rendering control.
+
 
 ## APIs
 
@@ -20,19 +24,20 @@ Panel(show: boolean)
 
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
-| show | boolean | Yes| Whether the panel is shown.|
-
+| show | boolean | Yes| Whether the panel is shown.<br>**NOTE**<br>The panel is hidden and does not take up space in the layout if this parameter is set to **false** or [Visible.None](ts-universal-attributes-visibility.md) is set.|
 
 ## Attributes
 
+In addition to the [universal attributes](ts-universal-attributes-size.md), the following attributes are supported.
+
 | Name| Type| Description|
 | -------- | -------- | -------- |
 | type | [PanelType](#paneltype)| Type of the panel.<br>Default value: **PanelType.Foldable**|
-| mode | [PanelMode](#panelmode) | Initial status of the panel.|
+| mode | [PanelMode](#panelmode) | Initial status of the panel.<br>Default value for the Minibar type: **PanelMode.Mini**<br/>Default value for other types: **PanelMode.Half** |
 | dragBar | boolean | Whether to enable a drag bar. The value **true** means that the drag bar will be displayed, and **false** means the opposite.<br>Default value: **true**|
-| fullHeight | string \| number | Panel height in the **PanelMode.Full** mode.|
-| halfHeight | string \| number | Panel height in the **PanelMode.Half** mode. The default value is half of the screen height.|
-| miniHeight | string \| number | Panel height in the **PanelMode.Mini** mode.|
+| fullHeight | string \| number | Panel height in the **PanelMode.Full** mode.<br>Default value: main axis height of the panel minus 8 vp<br>**NOTE**<br>This attribute cannot be set in percentage.|
+| halfHeight | string \| number | Panel height in the **PanelMode.Half** mode.<br>Default value: half of the main axis height of the panel<br>**NOTE**<br>This attribute cannot be set in percentage.|
+| miniHeight | string \| number | Panel height in the **PanelMode.Mini** mode.<br>Default value: **48**<br>Unit: vp<br>**NOTE**<br>This attribute cannot be set in percentage.|
 | show | boolean | Whether to show the panel.|
 | backgroundMask<sup>9+</sup>|[ResourceColor](ts-types.md#resourcecolor)|Background mask of the panel.|
 
@@ -52,9 +57,10 @@ Panel(show: boolean)
 | Half | Displays a **foldable** or **temporary** panel in a medium-sized (halfscreen-like) area. This attribute does not take effect for **minibar** panels.|
 | Full | Displays a panel in a large (fullscreen-like) area.|
 
-
 ## Events
 
+In addition to the [universal events](ts-universal-events-click.md), the following events are supported.
+
 | Name| Description|
 | -------- | -------- |
 | onChange(event: (width: number, height: number, mode: PanelMode) =&gt; void) | Triggered when the status of the panel changes. The returned height value is the height of the content area. When the value of **dragBar** is **true**, the panel height is the sum of the drag bar height and content area height.|
diff --git a/en/application-dev/reference/arkui-ts/ts-container-refresh.md b/en/application-dev/reference/arkui-ts/ts-container-refresh.md
index a455e001f3ea2289ed24daa9cbe269c4cc1e0bd5..a5f390b8c9c020bf72546013671c3d37cb9ddc4a 100644
--- a/en/application-dev/reference/arkui-ts/ts-container-refresh.md
+++ b/en/application-dev/reference/arkui-ts/ts-container-refresh.md
@@ -16,31 +16,35 @@ Refresh\(value: \{ refreshing: boolean, offset?:  number | string , friction?: n
 
 **Parameters**
 
-| Name| Value Type| Mandatory| Description|
-| -------- | -------- | -------- | -------- |
-| refreshing | boolean | Yes| Whether the current component is being refreshed.<br>This parameter supports [$$](../../quick-start/arkts-restrictions-and-extensions.md#two-way-binding-of-variables) for two-way binding of variables.|
-| offset | string \| number | No| Distance from the pull-down starting point to the top of the component.<br>Default value: **16**, in vp<br>**NOTE**<br>The value cannot be a percentage or a negative number.|
-| friction | number \| string | No| Coefficient of friction, which indicates the **<Refresh\>** component's sensitivity to the pull-down gesture. The value ranges from 0 to 100.<br>Default value: **62**<br>- **0** indicates that the **\<Refresh>** component is not sensitive to the pull-down gesture.<br>- **100** indicates that the **\<Refresh>** component is highly sensitive to the pull-down gesture.<br>- A larger value indicates a more sensitive response of the **\<Refresh>** component to the pull-down gesture.|
+| Name        | Value Type                                     | Mandatory  | Description                                    |
+| ---------- | ---------------------------------------- | ---- | ---------------------------------------- |
+| refreshing | boolean                                  | Yes   | Whether the current component is being refreshed.<br>This parameter supports [$$](../../quick-start/arkts-two-way-sync.md) for two-way binding of variables.|
+| offset     | string \| number               | No   | Distance from the pull-down starting point to the top of the component.<br>Default value: **16**, in vp<br>**NOTE**<br>The value cannot be a percentage or a negative number.|
+| friction   | number \| string               | No   | Coefficient of friction, which indicates the **<Refresh\>** component's sensitivity to the pull-down gesture. The value ranges from 0 to 100.<br>Default value: **62**<br>- **0** indicates that the **\<Refresh>** component is not sensitive to the pull-down gesture.<br>- **100** indicates that the **\<Refresh>** component is highly sensitive to the pull-down gesture.<br>- A larger value indicates a more sensitive response of the **\<Refresh>** component to the pull-down gesture.|
 
+## Attributes
 
+The [universal attributes](ts-universal-attributes-size.md) are supported.
 
 ## Events
 
+In addition to the [universal events](ts-universal-events-click.md), the following events are supported.
 
-| Name| Description|
-| -------- | -------- |
+
+| Name                                      | Description                                    |
+| ---------------------------------------- | -------------------------------------- |
 | onStateChange(callback: (state: [RefreshStatus](#refreshstatus)) => void)| Triggered when the refresh status changes.<br>- **state**: refresh status.|
-| onRefreshing(callback: () => void)| Triggered when the component enters the refresh state.|
+| onRefreshing(callback: () => void)       | Triggered when the component enters the refresh state.                          |
 
 ## RefreshStatus
 
-| Name| Description|
-| -------- | -------- |
-| Inactive | The component is not pulled down. This is the default value.|
-| Drag | The component is being pulled down, but the pulled distance is shorter than the minimum length required to trigger the refresh.|
-| OverDrag | The component is being pulled down, and the pulled distance exceeds the minimum length required to trigger the refresh.|
-| Refresh | The pull-down ends, and the component rebounds to the minimum length required to trigger the refresh and enters the refresh state.|
-| Done | The refresh is complete, and the component returns to the initial state (top).|
+| Name      | Description                  |
+| -------- | -------------------- |
+| Inactive | The component is not pulled down. This is the default value.            |
+| Drag     | The component is being pulled down, but the pulled distance is shorter than the minimum length required to trigger the refresh.     |
+| OverDrag | The component is being pulled down, and the pulled distance exceeds the minimum length required to trigger the refresh.     |
+| Refresh  | The pull-down ends, and the component rebounds to the minimum length required to trigger the refresh and enters the refresh state.|
+| Done     | The refresh is complete, and the component returns to the initial state (top).    |
 
 
 ## Example
diff --git a/en/application-dev/reference/arkui-ts/ts-container-scroll.md b/en/application-dev/reference/arkui-ts/ts-container-scroll.md
index 4ad560e029ae6ad0ab5573beb62b774b995c52ce..d54ecbf1d4a50be563e2c712648ae0a56dc19daa 100644
--- a/en/application-dev/reference/arkui-ts/ts-container-scroll.md
+++ b/en/application-dev/reference/arkui-ts/ts-container-scroll.md
@@ -31,9 +31,9 @@ In addition to the [universal attributes](ts-universal-attributes-size.md), the
 | Name            | Type                                    | Description       |
 | -------------- | ---------------------------------------- | --------- |
 | scrollable     | [ScrollDirection](#scrolldirection)                        | Scroll direction.<br>Default value: **ScrollDirection.Vertical**|
-| scrollBar      | [BarState](ts-appendix-enums.md#barstate) | Scrollbar status.<br>Default value: **BarState.Auto**|
+| scrollBar      | [BarState](ts-appendix-enums.md#barstate) | Scrollbar status.<br>Default value: **BarState.Auto**<br>**NOTE**<br>If the container component cannot be scrolled, the scrollbar is not displayed. If the size of a child component of a container component is infinite, the scrollbar cannot be dragged or scrolled with the child component.|
 | scrollBarColor | string \| number \| [Color](ts-appendix-enums.md#color)   | Color of the scrollbar.|
-| scrollBarWidth | string \| number         | Width of the scrollbar.|
+| scrollBarWidth | string \| number         | Width of the scrollbar. This attribute cannot be set in percentage.<br>Default value: **4**<br>Unit: vp<br>**NOTE**<br>If the width of the scrollbar exceeds its height, it will change to the default value.|
 | edgeEffect     | [EdgeEffect](ts-appendix-enums.md#edgeeffect)            | Scroll effect. For details, see **EdgeEffect**.<br>Default value: **EdgeEffect.None**|
 
 ## ScrollDirection
@@ -42,18 +42,18 @@ In addition to the [universal attributes](ts-universal-attributes-size.md), the
 | Horizontal | Only horizontal scrolling is supported.    |
 | Vertical   | Only vertical scrolling is supported.    |
 | None       | Scrolling is disabled.              |
-| Free<sup>(deprecated)</sup> | Vertical or horizontal scrolling is supported.<br>This API is deprecated since API version 9. |
+| Free<sup>(deprecated)</sup> | Vertical or horizontal scrolling is supported.<br>This API is deprecated since API version 9.|
 
 ## Events
 
 | Name                                                        | Description                                                    |
 | ------------------------------------------------------------ | ------------------------------------------------------------ |
-| onScrollFrameBegin<sup>9+</sup>(event: (offset: number, state: ScrollState) => { offsetRemain }) | Triggered when each frame scrolling starts. The input parameters indicate the amount by which the **\<Scroll>** component will scroll. The event handler then works out the amount by which the component needs to scroll based on the real-world situation and returns the result.<br>\- **offset**: amount to scroll by.<br>\- **state**: current scrolling status.<br>- **offsetRemain**: actual amount by which the component scrolls.|
-| onScroll(event: (xOffset: number, yOffset: number) => void)  | Triggered to return the horizontal and vertical offsets during scrolling when the specified scroll event occurs.         |
-| onScrollEdge(event: (side: Edge) => void)                    | Triggered when scrolling reaches the edge.                                        |
-| onScrollEnd<sup>(deprecated) </sup>(event: () => void)                               | Triggered when scrolling stops.<br>This event is deprecated since API version 9. Use the **onScrollStop** event instead.    |
-| onScrollStart<sup>9+</sup>(event: () => void) | Triggered when scrolling starts and is initiated by the user's finger dragging the **\<Scroll>** component or its scrollbar. This event is also triggered when the animation contained in the scrolling triggered by [Scroller](#scroller) starts.|
-| onScrollStop<sup>9+</sup>(event: () => void) | Triggered when scrolling stops after the user's finger leaves the screen. This event is also triggered when the animation contained in the scrolling triggered by [Scroller](#scroller) stops.|
+| onScrollFrameBegin<sup>9+</sup>(event: (offset: number, state: ScrollState) => { offsetRemain }) | Triggered when each frame scrolling starts. The input parameters indicate the amount by which the **\<Scroll>** component will scroll. The event handler then works out the amount by which the component needs to scroll based on the real-world situation and returns the result.<br>\- **offset**: amount to scroll by.<br>\- **state**: current scrolling status.<br>- **offsetRemain**: actual amount by which the component scrolls.<br>**NOTE**<br>1. This event is triggered when scrolling is started by the **\<Scroll>** component or other input settings, such as keyboard and mouse operations.<br>2. This event is not triggered when the controller API is called.<br>3. No out-of-bounds bounce effect is triggered.<br>**NOTE**<br>The value of **offsetRemain** can be a negative value.<br>If the **onScrollFrameBegine** event and **scrollBy** method are used to implement nested scrolling, set the **edgeEffect** attribute of the scrollable child component to **None**. For example, if a **\<List>** is nested in the **\<Scroll>** component, **edgeEffect** of the **\<List>** must be set to **EdgeEffect.None**.|
+| onScroll(event: (xOffset: number, yOffset: number) => void)  | Triggered to return the horizontal and vertical offsets during scrolling when the specified scroll event occurs.<br>**NOTE**<br>1. This event is triggered when scrolling is started by the **\<Scroll>** component or other input settings, such as keyboard and mouse operations.<br>2. This event is triggered when the controller API is called.<br>3. The out-of-bounds bounce effect is triggered.|
+| onScrollEdge(event: (side: Edge) => void)                    | Triggered when scrolling reaches the edge.<br>**NOTE**<br>1. This event is triggered when scrolling reaches the edge after being started by the **\<Scroll>** component or other input settings, such as keyboard and mouse operations.<br>2. This event is triggered when the controller API is called.<br>3. The out-of-bounds bounce effect is triggered.|
+| onScrollEnd<sup>(deprecated) </sup>(event: () => void)       | Triggered when scrolling stops.<br>This event is deprecated since API version 9. Use the **onScrollStop** event instead.<br>**NOTE**<br>1. This event is triggered when scrolling is stopped by the **\<Scroll>** component or other input settings, such as keyboard and mouse operations.<br>2. This event is triggered when the controller API is called, accompanied by a transition animation.|
+| onScrollStart<sup>9+</sup>(event: () => void)                | Triggered when scrolling starts and is initiated by the user's finger dragging the **\<Scroll>** component or its scrollbar. This event is also triggered when the animation contained in the scrolling triggered by [Scroller](#scroller) starts.<br>**NOTE**<br>1. This event is triggered when scrolling is started by the **\<Scroll>** component or other input settings, such as keyboard and mouse operations.<br>2. This event is triggered when the controller API is called, accompanied by a transition animation.|
+| onScrollStop<sup>9+</sup>(event: () => void)                 | Triggered when scrolling stops after the user's finger leaves the screen. This event is also triggered when the animation contained in the scrolling triggered by [Scroller](#scroller) stops.<br>**NOTE**<br>1. This event is triggered when scrolling is stopped by the **\<Scroll>** component or other input settings, such as keyboard and mouse operations.<br>2. This event is triggered when the controller API is called, accompanied by a transition animation.|
 
 >  **NOTE**
 >
@@ -61,7 +61,7 @@ In addition to the [universal attributes](ts-universal-attributes-size.md), the
 
 ## Scroller
 
-Implements a controller for a scrollable container component. You can bind this component to a container component and use it to control the scrolling of that component. One controller can control only one container component. The supported container components are **\<List>**, **\<Scroll>**, **\<ScrollBar>**, **\<Grid>**.
+Implements a controller for a scrollable container component. You can bind this component to a container component and use it to control the scrolling of that component. One controller can control only one container component. The supported container components are **\<List>**, **\<Scroll>**, **\<ScrollBar>**, **\<Grid>**, and **\<WaterFlow>**.
 
 
 ### Objects to Import
@@ -82,9 +82,9 @@ Scrolls to the specified position.
 
 | Name   | Type                                                    | Mandatory| Description                                                    |
 | --------- | ------------------------------------------------------------ | ---- | ------------------------------------------------------------ |
-| xOffset   | number | string                                              | Yes  | Horizontal scrolling offset.                                              |
-| yOffset   | number | string                                              | Yes  | Vertical scrolling offset.                                              |
-| animation | {<br>duration: number,<br>curve: [Curve](ts-appendix-enums.md#curve)<br>} | No  | Animation configuration, which includes the following:<br>- **duration**: scrolling duration.<br>- **curve**: scrolling curve.|
+| xOffset   | number \| string                                   | Yes  | Horizontal scrolling offset.<br>**NOTE**<br>This parameter cannot be set in percentage.<br>This parameter is valid only when the scroll axis is the x-axis.|
+| yOffset   | number \| string                                   | Yes  | Vertical scrolling offset.<br>**NOTE**<br>This parameter cannot be set in percentage.<br>This parameter is valid only when the scroll axis is the y-axis.|
+| animation | {<br>duration: number,<br>curve: [Curve](ts-appendix-enums.md#curve)<br>} | No  | Animation configuration, which includes the following:<br>- **duration**: scrolling duration.<br>- **curve**: scrolling curve.<br>Default value:<br>{<br>duration: 0,<br>curve: Curve.Ease<br>}<br>**NOTE**<br>A value less than 0 evaluates to the default value.|
 
 
 ### scrollEdge
@@ -124,9 +124,9 @@ Obtains the scrolling offset.
 
 **Return value**
 
-| Type                                      | Description                                      |
-| ---------------------------------------- | ---------------------------------------- |
-| {<br>xOffset: number,<br>yOffset: number<br>} | **xOffset**: horizontal scrolling offset.<br>**yOffset**: vertical scrolling offset.|
+| Type                                                      | Description                                                        |
+| ---------------------------------------------------------- | ------------------------------------------------------------ |
+| {<br>xOffset: number,<br>yOffset: number<br>} | **xOffset**: horizontal scrolling offset.<br>**yOffset**: vertical scrolling offset.<br>**NOTE**<br>The unit of the return value is vp.|
 
 
 ### scrollToIndex
@@ -198,7 +198,7 @@ struct ScrollExample {
       .scrollable(ScrollDirection.Vertical)  // The scrollbar scrolls in the vertical direction.
       .scrollBar(BarState.On)  // The scrollbar is always displayed.
       .scrollBarColor(Color.Gray)  // Color of the scrollbar.
-      .scrollBarWidth(30) // Width of the scrollbar.
+      .scrollBarWidth(10) // The scrollbar width is 10.
       .edgeEffect(EdgeEffect.None)
       .onScroll((xOffset: number, yOffset: number) => {
         console.info(xOffset + ' ' + yOffset)
@@ -211,21 +211,25 @@ struct ScrollExample {
       })
 
       Button('scroll 150')
+        .height('5%')
         .onClick(() => { // Click to scroll down to 150.0 vp.
           this.scroller.scrollBy(0,150)
         })
         .margin({ top: 10, left: 20 })
       Button('scroll 100')
+        .height('5%')
         .onClick(() => { // Click to scroll down by 100.0 vp.
           this.scroller.scrollTo({ xOffset: 0, yOffset: this.scroller.currentOffset().yOffset + 100 })
         })
         .margin({ top: 60, left: 20 })
       Button('back top')
+        .height('5%')
         .onClick(() => { // Click to go back to the top.
           this.scroller.scrollEdge(Edge.Top)
         })
         .margin({ top: 110, left: 20 })
       Button('next page')
+        .height('5%')
         .onClick(() => { // Click to go to the next page.
           this.scroller.scrollPage({ next: true })
         })
diff --git a/en/application-dev/reference/arkui-ts/ts-container-sidebarcontainer.md b/en/application-dev/reference/arkui-ts/ts-container-sidebarcontainer.md
index e8f57f0aebcdf81b7f4a5227b76e8795d79543fb..3a1ef0bfa62a2081886367baef187b963490d8bb 100644
--- a/en/application-dev/reference/arkui-ts/ts-container-sidebarcontainer.md
+++ b/en/application-dev/reference/arkui-ts/ts-container-sidebarcontainer.md
@@ -11,6 +11,12 @@ The **\<SideBarContainer>** component contains a sidebar and content area as its
 
 Supported
 
+>  **NOTE**
+>
+>  - Built-in components and custom components are allowed, without support for ([if/else](../../quick-start/arkts-rendering-control-ifelse.md), [ForEach](../../quick-start/arkts-rendering-control-foreach.md), and [LazyForEach](../../quick-start/arkts-rendering-control-lazyforeach.md)) rendering control.
+>  - This component must contain two child components.
+>  - If there are three or more child components, only the first and second child components are displayed. If there is only one child component, the sidebar is displayed, and the content area is blank.
+
 
 ## APIs
 
@@ -22,7 +28,7 @@ SideBarContainer( type?: SideBarContainerType )
 | -------- | -------- | -------- | -------- |
 | type | SideBarContainerType | No| Display type of the sidebar.<br>Default value: **SideBarContainerType.Embed**|
 
-## SideBarContainerType enums
+## SideBarContainerType
 
 | Name| Description|
 | -------- | -------- |
@@ -31,26 +37,28 @@ SideBarContainer( type?: SideBarContainerType )
 
 ## Attributes
 
+In addition to the [universal attributes](ts-universal-attributes-size.md), the following attributes are supported.
+
 | Name| Type| Description|
 | -------- | -------- | -------- |
-| showSideBar | boolean | Whether to display the sidebar.<br>Default value: **true**|
-| controlButton | ButtonStyle                                                | Attributes of the sidebar control button.|
+| showSideBar | boolean | Whether to display the sidebar.<br>Default value: **true** |
+| controlButton | [ButtonStyle](#buttonstyle)                            | Attributes of the sidebar control button.|
 | showControlButton | boolean | Whether to display the sidebar control button.<br>Default value: **true**|
-| sideBarWidth | number \| Length<sup>9+</sup> | Width of the sidebar.<br>Default value: **200**, in vp|
-| minSideBarWidth | number \| Length<sup>9+</sup> | Minimum width of the sidebar.<br>Default value: **200**, in vp|
-| maxSideBarWidth | number \| Length<sup>9+</sup> | Maximum width of the sidebar.<br>Default value: **280**, in vp|
-| autoHide<sup>9+</sup> | boolean | Whether to automatically hide the sidebar when it is dragged to be smaller than the minimum width.<br>Default value: **true**|
+| sideBarWidth | number \| Length<sup>9+</sup> | Width of the sidebar.<br>Default value: **200**<br>Unit: vp<br>**NOTE**<br>A value less than 0 evaluates to the default value.<br>The value must comply with the width constraints. If it is not within the valid range, the value closest to the set one is used.<br>When set, the width of the sidebar takes precedence over that of the sidebar child components. If it is not set, however, the width of the sidebar child component takes precedence.|
+| minSideBarWidth | number \| Length<sup>9+</sup> | Minimum width of the sidebar.<br>Default value: **200**, in vp<br>**NOTE**<br>A value less than 0 evaluates to the default value.<br>The value cannot exceed the width of the sidebar container itself. Otherwise, the width of the sidebar container itself is used.<br>When set, the minimum width of the sidebar takes precedence over that of the sidebar child components. If it is not set, however, the minimum width of the sidebar child component takes precedence.|
+| maxSideBarWidth | number \| Length<sup>9+</sup> | Maximum width of the sidebar.<br>Default value: **280**, in vp<br>**NOTE**<br>A value less than 0 evaluates to the default value.<br>The value cannot exceed the width of the sidebar container itself. Otherwise, the width of the sidebar container itself is used.<br>When set, the maximum width of the sidebar takes precedence over that of the sidebar child components. If it is not set, however, the maximum width of the sidebar child component takes precedence.|
+| autoHide<sup>9+</sup> | boolean | Whether to automatically hide the sidebar when it is dragged to be smaller than the minimum width.<br>Default value: **true**<br>**NOTE**<br>The value is subject to the **minSideBarWidth** attribute method. If it is not set in **minSideBarWidth**, the default value is used.<br>Whether the sidebar should be hidden is determined when it is being dragged. When its width is less than the minimum width, the damping effect is required to trigger hiding (a distance out of range).|
 | sideBarPosition<sup>9+</sup> | SideBarPosition | Position of the sidebar.<br>Default value: **SideBarPosition.Start**|
 
 ## ButtonStyle
 
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
-| left | number | No| Spacing between the sidebar control button and the left of the container.<br>Default value: **16**, in vp|
-| top | number | No| Spacing between the sidebar control button and the top of the container.<br>Default value: **48**, in vp|
-| width | number | No| Width of the sidebar control button.<br>Default value: **32**, in vp|
-| height | number | No| Height of the sidebar control button.<br>Default value: **32**, in vp|
-| icons | {<br>shown: string \| PixelMap \| [Resource](ts-types.md) ,<br>hidden: string \| PixelMap \| [Resource](ts-types.md) ,<br>switching?: string \| PixelMap \| [Resource](ts-types.md) <br>} | No| Icons of the sidebar control button.<br> </p> - **shown**: icon of the control button when the sidebar is shown.<br>- **hidden**: icon of the control button when the sidebar is hidden.<br>- **switching**: icon of the control button when the sidebar is switching between the shown and hidden states.|
+| left | number | No| Spacing between the sidebar control button and the left of the container.<br>Default value: **16**<br>Unit: vp|
+| top | number | No| Spacing between the sidebar control button and the top of the container.<br>Default value: **48**<br>Unit: vp|
+| width | number | No| Width of the sidebar control button.<br>Default value: **32**<br>Unit: vp|
+| height | number | No| Height of the sidebar control button.<br>Default value: **32**<br>Unit: vp|
+| icons | {<br>shown: string \| PixelMap \| [Resource](ts-types.md) ,<br>hidden: string \| PixelMap \| [Resource](ts-types.md) ,<br>switching?: string \| PixelMap \| [Resource](ts-types.md) <br>} | No| Icons of the sidebar control button.<br> </p> - **shown**: icon of the control button when the sidebar is shown.<br>**NOTE**<br>When an error occurs during resource obtaining, the default icon is used.<br>- **hidden**: icon of the control button when the sidebar is hidden.<br>- **switching**: icon of the control button when the sidebar is switching between the shown and hidden states.|
 
 ## SideBarPosition<sup>9+</sup>
 
@@ -61,9 +69,11 @@ SideBarContainer( type?: SideBarContainerType )
 
 ## Events
 
+In addition to the [universal events](ts-universal-events-click.md), the following events are supported.
+
 | Name| Description|
 | -------- | -------- |
-| onChange(callback: (value: boolean) =&gt; void) | Triggered when the status of the sidebar switches between shown and hidden. <p>The value **true** means that the sidebar is shown, and **false** means the opposite.|
+| onChange(callback: (value: boolean) =&gt; void) | Triggered when the status of the sidebar switches between shown and hidden. The value **true** means that the sidebar is displayed, and **false** means the opposite.<br>This event is triggered when any of the following conditions is met:<br>1. The value of **showSideBar** changes.<br>2. The **showSideBar** attribute adapts to behavior changes.<br>3. The **autoHide** API is triggered when the divider is dragged.|
 
 
 ## Example
@@ -73,14 +83,13 @@ SideBarContainer( type?: SideBarContainerType )
 @Entry
 @Component
 struct SideBarContainerExample {
-  normalIcon : Resource = $r("app.media.icon")
+  normalIcon: Resource = $r("app.media.icon")
   selectedIcon: Resource = $r("app.media.icon")
   @State arr: number[] = [1, 2, 3]
   @State current: number = 1
 
   build() {
-    SideBarContainer(SideBarContainerType.Embed)
-    {
+    SideBarContainer(SideBarContainerType.Embed) {
       Column() {
         ForEach(this.arr, (item, index) => {
           Column({ space: 5 }) {
@@ -105,6 +114,13 @@ struct SideBarContainerExample {
       }
       .margin({ top: 50, left: 20, right: 30 })
     }
+    .controlButton({
+      icons: {
+        hidden: $r('app.media.drawer'),
+        shown: $r('app.media.drawer'),
+        switching: $r('app.media.drawer')
+      }
+    })
     .sideBarWidth(150)
     .minSideBarWidth(50)
     .maxSideBarWidth(300)
diff --git a/en/application-dev/reference/arkui-ts/ts-container-swiper.md b/en/application-dev/reference/arkui-ts/ts-container-swiper.md
index 2f224afc0377281c20ee36a638b5862a39096106..7cd62c1323780d8ea22835b7ae8cdebac7952a5b 100644
--- a/en/application-dev/reference/arkui-ts/ts-container-swiper.md
+++ b/en/application-dev/reference/arkui-ts/ts-container-swiper.md
@@ -11,6 +11,10 @@
 
 This component can contain child components.
 
+>  **NOTE**
+>
+>  Built-in components and custom components are allowed, with support for ([if/else](../../quick-start/arkts-rendering-control-ifelse.md), [ForEach](../../quick-start/arkts-rendering-control-foreach.md), and [LazyForEach](../../quick-start/arkts-rendering-control-lazyforeach.md)) rendering control.
+
 
 ## APIs
 
@@ -29,21 +33,21 @@ In addition to the [universal attributes](ts-universal-attributes-size.md), the
 
 | Name                         | Type                              | Description                                      |
 | --------------------------- | ---------------------------------------- | ---------------------------------------- |
-| index                       | number                                   | Index of the child component currently displayed in the container.<br>Default value: **0**                    |
-| autoPlay                    | boolean                                  | Whether to enable automatic playback for child component switching.<br>Default value: **false**   |
+| index                       | number                                   | Index of the child component currently displayed in the container.<br>Default value: **0**<br>**NOTE**<br>If the value is less than 0 or greater than or equal to the number of child components, the default value **0** is used.<br>Since API version 10, this attribute supports [$$](../../quick-start/arkts-two-way-sync.md) for two-way binding of variables.|
+| autoPlay                    | boolean                                  | Whether to enable automatic playback for child component switching.<br>Default value: **false**<br>**NOTE**<br>If **loop** is set to **false**, the rotation stops when the last page is displayed. The playback continues when the page is not the last page after a swipe gesture. |
 | interval                    | number                                   | Interval for automatic playback, in ms.<br>Default value: **3000**                   |
 | indicator                   | boolean                                  | Whether to enable the navigation dots indicator.<br>Default value: **true**                             |
 | loop                        | boolean                                  | Whether to enable loop playback.<br>The value **true** means to enable loop playback. When LazyForEach is used, it is recommended that the number of the components to load exceed 5.<br>Default value: **true**|
 | duration                    | number                                   | Duration of the animation for switching child components, in ms.<br>Default value: **400**                       |
 | vertical                    | boolean                                  | Whether vertical swiping is used.<br>Default value: **false**                                |
-| itemSpace                   | number \| string          | Space between child components.<br>Default value: **0**                          |
+| itemSpace                   | number \| string                         | Space between child components.<br>Default value: **0**<br>**NOTE**<br>This parameter cannot be set in percentage.|
 | displayMode                 | SwiperDisplayMode                        | Mode in which elements are displayed along the main axis. This attribute takes effect only when **displayCount** is not set.<br>Default value: **SwiperDisplayMode.Stretch**|
 | cachedCount<sup>8+</sup>    | number                                   | Number of child components to be cached.<br>Default value: **1**                             |
 | disableSwipe<sup>8+</sup>   | boolean                                  | Whether to disable the swipe feature.<br>Default value: **false**                             |
 | curve<sup>8+</sup>          | [Curve](ts-appendix-enums.md#curve)  \| string | Animation curve. The ease-in/ease-out curve is used by default. For details about common curves, see [Curve](ts-appendix-enums.md#curve). You can also create custom curves (interpolation curve objects) by using the API provided by the [interpolation calculation](../apis/js-apis-curve.md) module.<br>Default value: **Curve.Ease**|
 | indicatorStyle<sup>8+</sup> | {<br>left?: [Length](ts-types.md#length),<br>top?: [Length](ts-types.md#length),<br>right?: [Length](ts-types.md#length),<br>bottom?: [Length](ts-types.md#length),<br>size?: [Length](ts-types.md#length),<br>mask?: boolean,<br>color?: [ResourceColor](ts-types.md),<br>selectedColor?: [ResourceColor](ts-types.md)<br>} | Style of the navigation dots indicator.<br>\- **left**: distance between the navigation dots indicator and the left edge of the **\<Swiper>** component.<br>\- **top**: distance between the navigation dots indicator and the top edge of the **\<Swiper>** component.<br>\- **right**: distance between the navigation dots indicator and the right edge of the **\<Swiper>** component.<br>\- **bottom**: distance between the navigation dots indicator and the bottom edge of the **\<Swiper>** component.<br>\- **size**: diameter of the navigation dots indicator.<br>\- **mask**: whether to enable the mask for the navigation dots indicator.<br>\- **color**: color of the navigation dots indicator.<br>\- **selectedColor**: color of the selected navigation dot.|
-| displayCount<sup>8+</sup>   | number\|string                                               | Number of elements to display per page.<br>Default value: **1**                                          |
-| effectMode<sup>8+</sup>     | [EdgeEffect](ts-appendix-enums.md#edgeeffect)  | Swipe effect. For details, see **EdgeEffect**.<br>Default value: **EdgeEffect.Spring**|
+| displayCount<sup>8+</sup>   | number\|string                                               | Number of elements to display per page.<br>Default value: **1** |
+| effectMode<sup>8+</sup>     | [EdgeEffect](ts-appendix-enums.md#edgeeffect)  | Swipe effect. For details, see **EdgeEffect**.<br>Default value: **EdgeEffect.Spring** |
 
 ## SwiperDisplayMode
 
@@ -60,13 +64,13 @@ Controller of the **\<Swiper>** component. You can bind this object to the **\<S
 
 showNext(): void
 
-Turns to the next page.
+Turns to the next page. Page turning occurs with the animation, whose duration is specified by **duration**.
 
 ### showPrevious
 
 showPrevious(): void
 
-Turns to the previous page.
+Turns to the previous page. Page turning occurs with the animation, whose duration is specified by **duration**.
 
 ### finishAnimation
 
@@ -76,28 +80,20 @@ Stops an animation.
 
 **Parameters**
 
-| Name   | Type  | Mandatory | Description|
+| Name   | Type  | Mandatory.| Description|
 | --------- | ---------- | ------ | -------- |
 | callback  | () => void | No    | Callback invoked when the animation stops.|
 
-## Events
-
-### onChange
-
-onChange(event: (index: number) => void)
 
-Triggered when the index of the currently displayed child component changes.
-
-> **NOTE**
-> 
-> When the **\<Swiper>** component is used together with **LazyForEach**, the subpage UI cannot be refreshed in the **onChange** event.
-
-**Return value**
+## Events
 
-| Name   |   Type   | Description|
-| --------- | ---------- | -------- |
-| index     | number    | Index of the currently displayed element.|
+In addition to the [universal events](ts-universal-events-click.md), the following events are supported.
 
+| Name                                                        | Description                                                    |
+| ------------------------------------------------------------ | ------------------------------------------------------------ |
+| onChange(event: (index: number) => void)                     | Triggered when the index of the currently displayed child component changes.<br>- **index**: index of the currently displayed element.<br>**NOTE**<br>When the **\<Swiper>** component is used together with **LazyForEach**, the subpage UI update cannot be triggered in the **onChange** event.|
+| onAnimationStart<sup>9+</sup>(event: (index: number) => void) | Triggered when the switching animation starts.<br>- **index**: index of the currently displayed element.<br>**NOTE**<br>The **index** parameter indicates the index before the animation starts (not the one after). When the **\<Swiper>** component contains multiple columns, the index is of the leftmost element.|
+| onAnimationEnd<sup>9+</sup>(event: (index: number) => void)  | Triggered when the switching animation ends.<br>- **index**: index of the currently displayed element.<br>**NOTE**<br>This event is triggered when the animation ends regardless of whether it is due to a user gesture or invocation of **finishAnimation** through **SwiperController**. The **index** parameter indicates the index after the animation ends. When the **\<Swiper>** component contains multiple columns, the index is of the leftmost element.|
 
 ## Example
 
diff --git a/en/application-dev/reference/arkui-ts/ts-container-tabcontent.md b/en/application-dev/reference/arkui-ts/ts-container-tabcontent.md
index ff7e048c992348673f69adf93414d58a841f52f8..34f2591ee877919152d8f502c916d78ef450154e 100644
--- a/en/application-dev/reference/arkui-ts/ts-container-tabcontent.md
+++ b/en/application-dev/reference/arkui-ts/ts-container-tabcontent.md
@@ -13,7 +13,8 @@ This component supports only one child component.
 
 >  **NOTE**
 >
->  System components and custom components can be built in, and rendering control types ([if/else](../../quick-start/arkts-rendering-control-ifelse.md), [ForEach](../../quick-start/arkts-rendering-control-foreach.md), and [LazyForEach](../../quick-start/arkts-rendering-control-lazyforeach.md)) are supported.
+>  Built-in components and custom components are allowed, with support for ([if/else](../../quick-start/arkts-rendering-control-ifelse.md), [ForEach](../../quick-start/arkts-rendering-control-foreach.md), and [LazyForEach](../../quick-start/arkts-rendering-control-lazyforeach.md)) rendering control.
+
 
 ## APIs
 
@@ -26,14 +27,15 @@ In addition to the [universal attributes](ts-universal-attributes-size.md), the
 
 | Name| Type| Description|
 | -------- | -------- | -------- |
-| tabBar | string \| Resource \| {<br>icon?: string \| Resource,<br>text?: string \| Resource<br>}<br>\| [CustomBuilder](ts-types.md)<sup>8+</sup> | Content displayed on the tab bar.<br>**CustomBuilder**: builder, to which components can be passed (applicable to API version 8 and later versions).<br>**NOTE**<br>If an icon uses an SVG image, the width and height attributes of the SVG image must be deleted. Otherwise, the icon size will be determined by the width and height attributes of the SVG image. |
-| tabBar<sup>9+</sup> | [SubTabBarStyle](#subtabbarstyle9) \| [BottomTabBarStyle](#bottomtabbarstyle9) | Content displayed on the tab bar.<br>**SubTabBarStyle**: subtab style. It takes text as its input parameter.<br>**BottomTabBarStyle**: bottom and side tab style. It takes text and images as its input parameters.|
+| tabBar | string \| Resource \| {<br>icon?: string \| Resource,<br>text?: string \| Resource<br>}<br>\| [CustomBuilder](ts-types.md)<sup>8+</sup> | Content displayed on the tab bar.<br>**CustomBuilder**: builder, to which components can be passed (applicable to API version 8 and later versions).<br>**NOTE**<br>If an icon uses an SVG image, the width and height attributes of the SVG image must be deleted. Otherwise, the icon size will be determined by the width and height attributes of the SVG image.<br>If the content set exceeds the space provided by the tab bar, it will be clipped.|
+| tabBar<sup>9+</sup> | [SubTabBarStyle](#subtabbarstyle9) \| [BottomTabBarStyle](#bottomtabbarstyle9) | Content displayed on the tab bar.<br>**SubTabBarStyle**: subtab style. It takes text as its input parameter.<br>**BottomTabBarStyle**: bottom and side tab style. It takes text and images as its input parameters.<br>**NOTE**<br>The bottom tab style does not include an underline.<br>When an icon display error occurs, a gray blank block is displayed.|
 
 >  **NOTE**
-> - The **\<TabContent>** component does not support setting of the common width attribute. By default, its width is the same as that of the parent **\<Tabs>** component.
-> - The **\<TabContent>** component does not support setting of the common height attribute. Its height is determined by the height of the parent **\<Tabs>** component and the **\<TabBar>** component.
+>
+>  - The **\<TabContent>** component does not support setting of the common width attribute. By default, its width is the same as that of the parent **\<Tabs>** component.
+>  - The **\<TabContent>** component does not support setting of the common height attribute. Its height is determined by the height of the parent **\<Tabs>** component and the **\<TabBar>** component.
 >  - If the **vertical** attribute is **false**, the width and height descriptions are swapped in the preceding two restrictions.
-> - **\<TabContent>** does not support page scrolling. If page scrolling is required, consider nesting a list.
+>  - **\<TabContent>** does not support page scrolling. If page scrolling is required, consider nesting a list.
 
 ## SubTabBarStyle<sup>9+</sup>
 
@@ -49,7 +51,8 @@ Constructor used to create a **SubTabBarStyle** instance.
 
 | Name| Type        | Mandatory| Description|
 | -------- | -------- | -------- | -------- |
-| content | string \| [Resource](ts-types.md#resource) | Yes| Text for the tab.|
+| content | string \| [Resource](ts-types.md#resource) | Yes| Text for the tab. Since API version 10, the type of **content** is **ResourceStr**.|
+
 
 ## BottomTabBarStyle<sup>9+</sup>
 
@@ -65,8 +68,9 @@ A constructor used to create a **BottomTabBarStyle** instance.
 
 | Name| Type        | Mandatory| Description|
 | -------- | -------- | -------- | -------- |
-| icon | string \| [Resource](ts-types.md#resource) | Yes| Image for the tab.|
-| text | string \| [Resource](ts-types.md#resource) | Yes| Text for the tab.|
+| icon | string \| [Resource](ts-types.md#resource) | Yes| Image for the tab. Since API version 10, the type of **icon** is **ResourceStr**.|
+| text | string \| [Resource](ts-types.md#resource) | Yes| Text for the tab. Since API version 10, the type of **text** is **ResourceStr**.|
+
 
 ## Example
 
diff --git a/en/application-dev/reference/arkui-ts/ts-container-tabs.md b/en/application-dev/reference/arkui-ts/ts-container-tabs.md
index e7d048e01f1d75095485d79e689d29ef6090c276..1d6faaf26b82ba9f31cbf9e659c2acee4e1f5d56 100644
--- a/en/application-dev/reference/arkui-ts/ts-container-tabs.md
+++ b/en/application-dev/reference/arkui-ts/ts-container-tabs.md
@@ -18,11 +18,11 @@ Tabs(value?: {barPosition?: BarPosition, index?: number, controller?: [TabsContr
 
 **Parameters**
 
-| Name        | Type                             | Mandatory  | Description                                    |
-| ----------- | --------------------------------- | ---- | ---------------------------------------- |
-| barPosition | BarPosition                       | No   | Position of the **\<Tabs>** component.<br>Default value: **BarPosition.Start**  |
-| index       | number                            | No   | Initial tab index.<br>Default value: **0**<br>**NOTE**<br><br>A value less than 0 evaluates to the default value.<br>The value ranges from 0 to the number of **\<TabContent>** subnodes minus 1.<br>When this parameter is set to different values, the slide animation for tab switching is enabled by default. To disable the animation, set **animationDuration** to **0**.|
-| controller  | [TabsController](#tabscontroller) | No   | Tab controller.                              |
+| Name     | Type                         | Mandatory| Description                                                    |
+| ----------- | --------------------------------- | ---- | ------------------------------------------------------------ |
+| barPosition | BarPosition                       | No  | Position of the **\<Tabs>** component.<br>Default value: **BarPosition.Start**          |
+| index       | number                            | No  | Initial tab index.<br>Default value: **0**<br>**NOTE**<br>A value less than 0 evaluates to the default value.<br>The value ranges from 0 to the number of **\<TabContent>** subnodes minus 1.<br>When this parameter is set to different values, the slide animation for tab switching is enabled by default. To disable the animation, set **animationDuration** to **0**. |
+| controller  | [TabsController](#tabscontroller) | No  | Tab controller.                                            |
 
 ## BarPosition
 
@@ -147,4 +147,3 @@ struct TabsExample {
 ```
 
 ![tabs2](figures/tabs2.gif)
-<!--no_check-->
\ No newline at end of file
diff --git a/en/application-dev/reference/arkui-ts/ts-container-waterflow.md b/en/application-dev/reference/arkui-ts/ts-container-waterflow.md
new file mode 100644
index 0000000000000000000000000000000000000000..76507f08dfd3debfb83504d54ce4344e870e0524
--- /dev/null
+++ b/en/application-dev/reference/arkui-ts/ts-container-waterflow.md
@@ -0,0 +1,291 @@
+# WaterFlow
+
+
+The **\<WaterFlow>** component is a container that consists of cells formed by rows and columns and arranges items of different sizes from top to bottom according to the preset rules.
+
+
+> **NOTE**
+>
+> This component is supported since API version 9. Updates will be marked with a superscript to indicate their earliest API version.
+
+
+## Child Components
+
+
+The [\<FlowItem>](ts-container-flowitem.md) child component is supported.
+
+
+## APIs
+
+
+WaterFlow(options?: {footer?: CustomBuilder, scroller?: Scroller})
+
+**Parameters**
+
+| Name    | Type                                       | Mandatory| Description                                    |
+| ---------- | ----------------------------------------------- | ------ | -------------------------------------------- |
+| footer |  [CustomBuilder](ts-types.md#custombuilder8) | No  | Footer of the **\<WaterFlow>** component. |
+| scroller | [Scroller](ts-container-scroll.md#scroller) | No  | Controller, which can be bound to scrollable components.<br>The **\<WaterFlow>** component supports only the **scrollToIndex** API of the **\<Scroller>** component.|
+
+
+## Attributes
+
+
+In addition to the [universal attributes](ts-universal-attributes-size.md), the following attributes are supported.
+
+| Name| Type| Description|
+| -------- | -------- | -------- |
+| columnsTemplate | string | Number of columns in the layout. If this attribute is not set, one column is used by default.<br>For example, **'1fr 1fr 2fr'** indicates three columns, with the first column taking up 1/4 of the parent component's full width, the second column 1/4, and the third column 2/4. This attribute supports [auto-fill](#auto-fill).<br>Default value: **'1fr'**|
+| rowsTemplate | string | Number of rows in the layout. If this attribute is not set, one row is used by default.<br>For example, **'1fr 1fr 2fr'** indicates three rows, with the first row taking up 1/4 of the parent component's full height, the second row 1/4, and the third row 2/4. This attribute supports [auto-fill](#auto-fill).<br>Default value: **'1fr'**|
+| itemConstraintSize | [ConstraintSizeOptions](ts-types.md#constraintsizeoptions) | Size constraints of the child components during layout.              |
+| columnsGap | Length |Gap between columns.<br>Default value: **0**|
+| rowsGap | Length |Gap between rows.<br> Default value: **0**|
+| layoutDirection | [FlexDirection](ts-appendix-enums.md#flexdirection) |Main axis direction of the layout.<br>Default value: **FlexDirection.Column**|
+
+The priority of **layoutDirection** is higher than that of **rowsTemplate** and **columnsTemplate**. Depending on the **layoutDirection** settings, there are three layout modes:
+
+- **layoutDirection** is set to **FlexDirection.Column** or **FlexDirection.ColumnReverse**
+
+	In this case, **columnsTemplate** is valid. If it is not set, the default value is used. For example, if **columnsTemplate** is set to **"1fr 1fr"** and **rowsTemplate** **"1fr 1fr 1fr"**, child components are arranged in vertical layout, with the cross axis equally divided into two columns.
+
+- **layoutDirection** set to **FlexDirection.Row** or **FlexDirection.RowReverse**
+
+	In this case, **rowsTemplate** is valid. If it is not set, the default value is used. For example, if **columnsTemplate** is set to **"1fr 1fr"** and **rowsTemplate** **"1fr 1fr 1fr"**, child components are arranged in horizontal layout, with the cross axis equally divided into three columns.
+
+- **layoutDirection** is not set
+
+	In this case, the default value of **layoutDirection** is used, which is **FlexDirection.Column**, and **columnsTemplate** is valid. For example, if **columnsTemplate** is set to **"1fr 1fr"** and **rowsTemplate** **"1fr 1fr 1fr"**, child components are arranged in vertical layout, with the cross axis equally divided into two columns.
+
+## Events
+
+
+In addition to the [universal events](ts-universal-events-click.md), the following events are supported.
+
+
+| Name| Description|
+| -------- | -------- |
+| onReachStart(event: () => void) | Triggered when the component reaches the start.|
+| onReachEnd(event: () => void)   | Triggered when the component reaches the end.|
+
+
+## auto-fill
+
+The **columnsTemplate** and **rowsTemplate** attributes supports **auto-fill** in the following format:
+
+```css
+repeat(auto-fill, track-size)
+```
+
+Where, **repeat** and **auto-fill** are keywords, and **track-size** indicates the row height or column width. The supported units include px, vp, %, and digits. The value of **track-size** must contain at least one valid row height or column width.
+
+
+## Example
+
+
+```ts
+// WaterFlowDataSource.ets
+
+// Object that implements the IDataSource API, which is used by the <WaterFlow> component to load data.
+export class WaterFlowDataSource implements IDataSource {
+
+  private dataArray: number[] = []
+  private listeners: DataChangeListener[] = []
+
+  constructor() {
+      for (let i = 0; i < 100; i++) {
+          this.dataArray.push(i)
+      }
+  }
+
+  // Obtain the data corresponding to the specified index.
+  public getData(index: number): any {
+      return this.dataArray[index]
+  }
+
+  // Notify the controller of data reloading.
+  notifyDataReload(): void {
+      this.listeners.forEach(listener => {
+          listener.onDataReloaded()
+      })
+  }
+
+  // Notify the controller of data addition.
+  notifyDataAdd(index: number): void {
+      this.listeners.forEach(listener => {
+          listener.onDataAdded(index)
+      })
+  }
+
+  // Notify the controller of data changes.
+  notifyDataChange(index: number): void {
+      this.listeners.forEach(listener => {
+          listener.onDataChanged(index)
+      })
+  }
+
+  // Notify the controller of data deletion.
+  notifyDataDelete(index: number): void {
+      this.listeners.forEach(listener => {
+          listener.onDataDeleted(index)
+      })
+  }
+
+  // Notify the controller of the data location change.
+  notifyDataMove(from: number, to: number): void {
+      this.listeners.forEach(listener => {
+          listener.onDataMoved(from, to)
+      })
+  }
+
+  // Obtain the total number of data records.
+  public totalCount(): number {
+      return this.dataArray.length
+  }
+
+  // Register the data change listener.
+  registerDataChangeListener(listener: DataChangeListener): void {
+      if (this.listeners.indexOf(listener) < 0) {
+          this.listeners.push(listener)
+      }
+  }
+
+  // Unregister the data change listener.
+  unregisterDataChangeListener(listener: DataChangeListener): void {
+      const pos = this.listeners.indexOf(listener)
+      if (pos >= 0) {
+          this.listeners.splice(pos, 1)
+      }
+  }
+
+  // Add data.
+  public Add1stItem(): void {
+      this.dataArray.splice(0, 0, this.dataArray.length)
+      this.notifyDataAdd(0)
+  }
+
+  // Add an item to the end of the data.
+  public AddLastItem(): void {
+      this.dataArray.splice(this.dataArray.length, 0, this.dataArray.length)
+      this.notifyDataAdd(this.dataArray.length-1)
+  }
+
+  // Add an item to the position corresponding to the specified index.
+  public AddItem(index: number): void {
+      this.dataArray.splice(index, 0, this.dataArray.length)
+      this.notifyDataAdd(index)
+  }
+
+  // Delete the first item.
+  public Delete1stItem(): void {
+      this.dataArray.splice(0, 1)
+      this.notifyDataDelete(0)
+  }
+
+  // Delete the second item.
+  public Delete2ndItem(): void {
+      this.dataArray.splice(1, 1)
+      this.notifyDataDelete(1)
+  }
+
+  // Delete the last item.
+  public DeleteLastItem(): void {
+      this.dataArray.splice(-1, 1)
+      this.notifyDataDelete(this.dataArray.length)
+  }
+
+  // Reload data.
+  public Reload(): void {
+      this.dataArray.splice(1, 1)
+      this.dataArray.splice(3, 2)
+      this.notifyDataReload()
+  }
+}
+```
+
+```ts
+// WaterflowDemo.ets
+import { WaterFlowDataSource } from './WaterFlowDataSource'
+
+@Entry
+@Component
+struct WaterflowDemo {
+  @State minSize: number = 50
+  @State maxSize: number = 100
+  @State fontSize: number = 24
+  @State colors: number[] = [0xFFC0CB, 0xDA70D6, 0x6B8E23, 0x6A5ACD, 0x00FFFF, 0x00FF7F]
+  scroller: Scroller = new Scroller()
+  datasource: WaterFlowDataSource = new WaterFlowDataSource()
+  private itemWidthArray: number[] = []
+  private itemHeightArray: number[] = []
+
+  // Calculate the width and height of a flow item. 
+  getSize() {
+    let ret = Math.floor(Math.random() * this.maxSize)
+    return (ret > this.minSize ? ret : this.minSize)
+  }
+
+  // Save the width and height of the flow item.  
+  getItemSizeArray() {
+    for (let i = 0; i < 100; i++) {
+      this.itemWidthArray.push(this.getSize())
+      this.itemHeightArray.push(this.getSize())
+    }
+  }
+    
+  aboutToAppear() {
+    this.getItemSizeArray()
+  }
+    
+  @Builder itemFoot() {
+    Column() {
+      Text(`Footer`)
+        .fontSize(10)
+        .backgroundColor(Color.Red)
+        .width(50)
+        .height(50)
+        .align(Alignment.Center)
+        .margin({ top: 2 })
+    }
+  }
+
+  build() {
+    Column({ space: 2 }) {
+      WaterFlow({ footer: this.itemFoot.bind(this), scroller: this.scroller }) {
+        LazyForEach(this.datasource, (item: number) => {
+          FlowItem() {
+            Column() {
+              Text("N" + item).fontSize(12).height('16')
+              Image('res/waterFlowTest(' + item % 5 + ').jpg')
+                .objectFit(ImageFit.Fill)
+            }
+          }
+          .width(this.itemWidthArray[item])
+          .height(this.itemHeightArray[item])
+          .backgroundColor(this.colors[item % 5])
+        }, item => item)
+      }
+      .columnsTemplate("1fr 1fr 1fr 1fr")
+      .itemConstraintSize({
+        minWidth: 0,
+        maxWidth: '100%',
+        minHeight: 0,
+        maxHeight: '100%'
+      })
+      .columnsGap(10)
+      .rowsGap(5)
+      .onReachStart(() => {
+        console.info("onReachStart")
+      })
+      .onReachEnd(() => {
+        console.info("onReachEnd")
+      })
+      .backgroundColor(0xFAEEE0)
+      .width('100%')
+      .height('80%')
+      .layoutDirection(FlexDirection.Column)
+    }
+  }
+}
+```
+
+![en-us_image_WaterFlow.gif](figures/waterflow.gif)
diff --git a/en/application-dev/reference/arkui-ts/ts-media-components-video.md b/en/application-dev/reference/arkui-ts/ts-media-components-video.md
index 0c143bd234578db616fb7a86fccca80cb592b983..e5cedbf9e226c3b37ce9c0a525c70376075f6187 100644
--- a/en/application-dev/reference/arkui-ts/ts-media-components-video.md
+++ b/en/application-dev/reference/arkui-ts/ts-media-components-video.md
@@ -22,12 +22,12 @@ Video(value: {src?: string | Resource, currentProgressRate?: number | string | P
 
 **Parameters**
 
-| Name                | Type                                    | Mandatory  | Description                                    |
-| ------------------- | ---------------------------------------- | ---- | ---------------------------------------- |
-| src                 | string \| [Resource](ts-types.md)        | No   | Path of the video source, which can be a local path or a URL.<br>The video resources can be stored in the **video** or **rawfile** folder under **resources**.<br>The path can include a **dataability://** prefix, which indicates that the path is provided by a Data ability. For details about the path, see [Data Ability Development](../../application-models/dataability-overview.md).<br>**NOTE**<br>The supported video formats are MP4, MKV, WebM, and TS. |
-| currentProgressRate | number \| string \| PlaybackSpeed<sup>8+</sup> | No   | Video playback speed.<br>**NOTE**<br>The value of the number type can only be **0.75**, **1.0**, **1.25**, **1.75**, or **2.0**.<br>Default value: **1.0** \| **PlaybackSpeed.Speed_Forward_1_00_X** |
-| previewUri          | string \| PixelMap<sup>8+</sup> \| [Resource](ts-types.md) | No   | Path of the preview image.                          |
-| controller          | [VideoController](#videocontroller)      | No   | Video controller.                                |
+| Name             | Type                                                    | Mandatory| Description                                                    |
+| ------------------- | ------------------------------------------------------------ | ---- | ------------------------------------------------------------ |
+| src                 | string \| [Resource](ts-types.md)                            | No  | Path of the video source, which can be a local path or a URL.<br>The video resources can be stored in the **video** or **rawfile** folder under **resources**.<br>The path can include a **dataability://** prefix, which indicates that the path is provided by a Data ability. For details about the path, see [Data Ability Development](../../application-models/dataability-overview.md).<br>**NOTE**<br>The supported video formats are MP4, MKV, WebM, and TS.|
+| currentProgressRate | number \| string \| PlaybackSpeed<sup>8+</sup> | No  | Video playback speed.<br>**NOTE**<br>The value of the number type can only be **0.75**, **1.0**, **1.25**, **1.75**, or **2.0**.<br>Default value: 1.0 \| PlaybackSpeed.Speed_Forward_1_00_X |
+| previewUri          | string \|PixelMap \| [Resource](ts-types.md)  | No  | Path of the preview image. (The PixelMap type is not supported currently.)        |
+| controller          | [VideoController](#videocontroller)                          | No  | Video controller.                                            |
 
 ## PlaybackSpeed<sup>8+</sup>
 
@@ -55,16 +55,16 @@ In addition to the [universal attributes](ts-universal-attributes-size.md), the
 
 In addition to the [universal events](ts-universal-events-click.md), the following events are supported.
 
-| Name                                      | Description                                    |
-| ---------------------------------------- | ---------------------------------------- |
-| onStart(event:() =&gt; void)   | Triggered when the video is played.                               |
-| onPause(event:() =&gt; void)   | Triggered when the video playback is paused.                               |
-| onFinish(event:() =&gt; void)  | Triggered when the video playback is finished.                             |
-| onError(event:() =&gt; void)   | Triggered when the video playback fails.                             |
+| Name                                                        | Description                                                    |
+| ------------------------------------------------------------ | ------------------------------------------------------------ |
+| onStart(event:() =&gt; void)                       | Triggered when the video is played.                                          |
+| onPause(event:() =&gt; void)                       | Triggered when the video playback is paused.                                          |
+| onFinish(event:() =&gt; void)                      | Triggered when the video playback is finished.                                      |
+| onError(event:() =&gt; void)                       | Triggered when the video playback fails.                                      |
 | onPrepared(callback:(event?: { duration: number }) =&gt; void) | Triggered when video preparation is complete. The video duration (in seconds) is obtained from **duration**.|
-| onSeeking(callback:(event?: { time: number }) =&gt; void) | Triggered to report the time (in seconds) when the progress bar is being dragged.                    |
-| onSeeked(callback:(event?: { time: number }) =&gt; void) | Triggered to report the playback time (in seconds) when the user finishes dragging the progress bar.                 |
-| onUpdate(callback:(event?: { time: number }) =&gt; void) | Triggered once per 250 ms when the playback progress changes. The unit of the current playback time is second.         |
+| onSeeking(callback:(event?: { time: number }) =&gt; void) | Triggered to report the time (in seconds) when the progress bar is being dragged.                     |
+| onSeeked(callback:(event?: { time: number }) =&gt; void) | Triggered to report the playback time (in seconds) when the user finishes dragging the progress bar.               |
+| onUpdate(callback:(event?: { time: number }) =&gt; void) | Triggered when the playback progress changes. The unit of the playback time is second.                         |
 | onFullscreenChange(callback:(event?: { fullscreen: boolean }) =&gt; void) | Triggered when the playback mode is switched between full-screen mode and non-full-screen mode. The value **true** means that the playback is in full-screen mode, and **false** means that the playback is non-full-screen mode.|
 
 
diff --git a/en/application-dev/reference/arkui-ts/ts-methods-custom-dialog-box.md b/en/application-dev/reference/arkui-ts/ts-methods-custom-dialog-box.md
index cdf79922c3d5a05a663dc59d9f7fadb1eca515b9..4b326869620b8db4032f7e37345da899c2d52bf7 100644
--- a/en/application-dev/reference/arkui-ts/ts-methods-custom-dialog-box.md
+++ b/en/application-dev/reference/arkui-ts/ts-methods-custom-dialog-box.md
@@ -11,20 +11,20 @@ A custom dialog box is a dialog box you customize by using APIs of the **CustomD
 
 ## APIs
 
-CustomDialogController(value:{builder: CustomDialog, cancel?: () =&gt; void, autoCancel?: boolean, alignment?: DialogAlignment, offset?: Offset, customStyle?: boolean, gridCount?: number, maskColor?: ResourceColor, openAnimation?: AnimateParam, closeAniamtion?: AnimateParam})
+CustomDialogController(value:{builder: CustomDialog, cancel?: () =&gt; void, autoCancel?: boolean, alignment?: DialogAlignment, offset?: Offset, customStyle?: boolean, gridCount?: number, maskColor?: ResourceColor, openAnimation?: AnimateParam, closeAniamtion?: AnimateParam, showInSubWindow?: boolean})
 
 
 **Parameters**
 
-| Name                   | Type                                    | Mandatory                 | Description                  |
-| ---------------------- | ---------------------------------------- | ------------------------- | ---------------------- |
-| builder                | [CustomDialog](../../quick-start/arkts-dynamic-ui-elememt-building.md#customdialog) | Yes    | Constructor of the custom dialog box content.           |
-| cancel                 | () =&gt; void                            | No             | Callback invoked when the dialog box is closed after the overlay exits.          |
-| autoCancel             | boolean                                            | No             | Whether to allow users to click the overlay to exit.<br>Default value: **true**          |
-| alignment              | [DialogAlignment](ts-methods-alert-dialog-box.md#dialogalignment)           | No             | Alignment mode of the dialog box in the vertical direction.<br>Default value: **DialogAlignment.Default**       |
-| offset                 | [Offset](ts-types.md#offset) | No   | Offset of the dialog box relative to the alignment position.|
-| customStyle            | boolean                                  | No                   | Whether to use a custom style for the dialog box.<br>Default value: **false**, which means that the dialog box automatically adapts its width to the grid system and its height to the child components; the maximum height is 90% of the container height; the rounded corner is 24 vp.          |
-| gridCount<sup>8+</sup> | number                                   | No                   | Number of [grid columns](../../ui/ui-ts-layout-grid-container-new.md) occupied by the dialog box.<br>The default value is 4, and the maximum value is the maximum number of columns supported by the system. If this parameter is set to an invalid value, the default value is used.|
+| Name                          | Type                                    | Mandatory  | Description                                    |
+| ----------------------------- | ---------------------------------------- | ---- | ---------------------------------------- |
+| builder                       | CustomDialog                             | Yes   | Constructor of the custom dialog box content.                             |
+| cancel                        | () =&gt; void                  | No   | Callback invoked when the dialog box is closed after the overlay exits.                            |
+| autoCancel                    | boolean                                  | No   | Whether to allow users to click the overlay to exit.<br>Default value: **true**                |
+| alignment                     | [DialogAlignment](ts-methods-alert-dialog-box.md#dialogalignment) | No   | Alignment mode of the dialog box in the vertical direction.<br>Default value: **DialogAlignment.Default**|
+| offset                        | [Offset](ts-types.md#offset)             | No   | Offset of the dialog box relative to the alignment position.                  |
+| customStyle                   | boolean                                  | No   | Whether to use a custom style for the dialog box.<br>Default value: **false**, which means that the dialog box automatically adapts its width to the grid system and its height to the child components; the maximum height is 90% of the container height; the rounded corner is 24 vp.|
+| gridCount<sup>8+</sup>        | number                                   | No   | Number of [grid columns](../../ui/arkts-layout-development-grid-layout.md) occupied by the dialog box.<br>The default value is 4, and the maximum value is the maximum number of columns supported by the system. If this parameter is set to an invalid value, the default value is used.|
 
 ## CustomDialogController
 
@@ -34,7 +34,7 @@ CustomDialogController(value:{builder: CustomDialog, cancel?: () =&gt; void, aut
 dialogController : CustomDialogController = new CustomDialogController(value:{builder: CustomDialog, cancel?: () => void, autoCancel?: boolean})
 ```
 > **NOTE**
-> 
+>
 > **CustomDialogController** is valid only when it is a member variable of the **@CustomDialog** and **@Component** decorated struct and is defined in the **@Component** decorated struct. For details, see the following example.
 
 ### open()
diff --git a/en/application-dev/reference/arkui-ts/ts-universal-attributes-focus.md b/en/application-dev/reference/arkui-ts/ts-universal-attributes-focus.md
index 363bb92058913192b1353e819c27eb74bc0cdb63..a41f5a3d6a02527531695897e673047045c75d28 100644
--- a/en/application-dev/reference/arkui-ts/ts-universal-attributes-focus.md
+++ b/en/application-dev/reference/arkui-ts/ts-universal-attributes-focus.md
@@ -11,10 +11,10 @@ Focus control attributes set whether a component is focusable, how it participat
 
 | Name              | Type| Description                                  |
 | -------------------- | -------- | ---------------------------------------- |
-| focusable            | boolean  | Whether the current component is focusable.<br>**NOTE**<br>Components that have default interaction logic, such as **\<Button>** and **\<TextInput>**, are focusable by default. Other components, such as **\<Text>** and **\<Image>**, are not focusable by default. Only focusable components can trigger a [focus event](ts-universal-focus-event.md). |
+| focusable            | boolean  | Whether the current component is focusable.<br>**NOTE**<br>Components that have default interaction logic, such as **\<Button>** and **\<TextInput>**, are focusable by default. Other components, such as **\<Text>** and **\<Image>**, are not focusable by default. Only focusable components can trigger a [focus event](ts-universal-focus-event.md).|
 | tabIndex<sup>9+</sup> | number   | How the current component participates in sequential keyboard navigation.<br>- **tabIndex** >= 0: The component is focusable in sequential keyboard navigation, with its order defined by the value. A component with a larger value gains focus later than one with a smaller value. If multiple components share the same **tabIndex** value, their focus order follows their position in the component tree.<br>- **tabIndex** < 0 (usually **tabIndex** = -1): The component is focusable, but cannot be reached through sequential keyboard navigation.<br>Default value: **0**|
 | defaultFocus<sup>9+</sup> | boolean  | Whether to set the current component as the default focus of the page. This attribute takes effect only when the page is new and accessed for the first time.<br>Default value: **false**|
-| groupDefaultFocus<sup>9+</sup> | boolean  | Whether to set the current component as the default focus of the parent container. This attribute takes effect only when the container is new and has focus for the first time.<br>Default value: **false**<br>**NOTE**<br>This attribute must be used together with **tabIndex**. When **tabIndex** is set for a container and **groupDefaultFocus** is set for a component in the container, the focus is automatically shifted to that component when the container obtains the focus for the first time. |
+| groupDefaultFocus<sup>9+</sup> | boolean  | Whether to set the current component as the default focus of the parent container. This attribute takes effect only when the container is new and has focus for the first time.<br>Default value: **false**<br>**NOTE**<br>This attribute must be used together with **tabIndex**. When **tabIndex** is set for a container and **groupDefaultFocus** is set for a component in the container, the focus is automatically shifted to that component when the container obtains the focus for the first time.|
 | focusOnTouch<sup>9+</sup> | boolean | Whether the current component is focusable on touch.<br>Default value: **false**<br>**NOTE**<br>The component can obtain focus only when it is touchable or clickable.|
 
 ## focusControl<sup>9+</sup>
@@ -39,7 +39,7 @@ Requests the focus to move to the specified component. This API can be used in g
 
 >  **NOTE**
 >
->  The following components support focus control: **\<Button>**, **\<Text>**, **\<Image>**, **\<List>**, and **\<Grid>**. Currently, the running effect of the focus event can be displayed only on a real device.
+>  The following components support focus control: **\<TextInput>**, **\<TextArea>**, **\<Search>**, **\<Button>**, **\<Text>**, **\<Image>**, **\<List>**, and **\<Grid>**. Currently, the running effect of the focus event can be displayed only on a real device.
 
 ## Example
 
diff --git a/en/application-dev/reference/arkui-ts/ts-universal-attributes-popup.md b/en/application-dev/reference/arkui-ts/ts-universal-attributes-popup.md
index 4bb9ffdcc334869e7a7d862e4c6a095887ad74ea..614faeb3055349f54006933512feb2c4bd54f520 100644
--- a/en/application-dev/reference/arkui-ts/ts-universal-attributes-popup.md
+++ b/en/application-dev/reference/arkui-ts/ts-universal-attributes-popup.md
@@ -10,35 +10,34 @@ You can bind a popup to a component, specifying its content, interaction logic,
 ## APIs
 
 
-| Name          | Type                            | Description                                       |
-| ---------- | ------------------------------------- | --------------------------------------- |
-| bindPopup  | show: boolean,<br>popup: [PopupOptions](#popupoptions) \| [CustomPopupOptions](#custompopupoptions8)<sup>8+</sup> | Binds a popup to the component.<br>**show**: whether to show the popup. The default value is **false**, indicating that the popup is hidden.<br>**popup**: parameters of the popup.|
+| Name       | Type                                    | Description                                      |
+| --------- | ---------------------------------------- | ---------------------------------------- |
+| bindPopup | show: boolean,<br>popup: [PopupOptions](#popupoptions) \| [CustomPopupOptions](#custompopupoptions8)<sup>8+</sup> | Binds a popup to the component.<br>**show**: whether to show the popup. The default value is **false**, indicating that the popup is hidden.<br>**popup**: parameters of the popup.|
 
 ## PopupOptions
 
-| Name                     | Type                                               | Mandatory   | Description                                         |
-| -------------------------| ------------------------------------------------| -----| ----------------------------------------- |
-| message                      | string                                                | Yes | Content of the popup message.                                    |
-| placementOnTop               | boolean                                               | No  | Whether to display the popup above the component.<br/>Default value: **false**            |
-| primaryButton                | {<br>value: string,<br>action: () =&gt; void<br>}     | No  | Primary button.<br>**value**: text of the primary button in the popup.<br>**action**: callback for clicking the primary button.|
-| secondaryButton              | {<br>value: string,<br>action: () =&gt; void<br>}     | No  | Secondary button.<br>**value**: text of the secondary button in the popup.<br>**action**: callback for clicking the secondary button.|
-| onStateChange                | (event: { isVisible: boolean }) =&gt; void            | No  | Callback for the popup status change event.<br/>**isVisible**: whether the popup is visible. |
-| arrowOffset<sup>9+</sup>     | [Length](ts-types.md#length)                          | No  | Offset of the popup arrow relative to the popup. <br>When the arrow is at the top or bottom of the popup: The value **0** indicates that the arrow is located on the leftmost, and any other value indicates the distance from the arrow to the leftmost; the arrow is centered by default. <br/>When the arrow is on the left or right side of the popup: The value indicates the distance from the arrow to the top; the arrow is centered by default. <br/>When the popup is displayed on either edge of the screen, it will automatically deviate leftward or rightward to stay within the safe area. When the value is **0**, the arrow always points to the bound component. |
-| showInSubWindow<sup>9+</sup> | boolean                                               | No  | Whether to show the popup in the subwindow. <br/>Default value: **false** |
-
+| Name                                 | Type                                                        | Mandatory| Description                                                        |
+| ------------------------------------- | ------------------------------------------------------------ | ---- | ------------------------------------------------------------ |
+| message                               | string                                                       | Yes  | Content of the popup message.                                              |
+| placementOnTop | boolean                                                      | No  | Whether to display the popup above the component.<br>Default value: **false** |
+| primaryButton                         | {<br>value: string,<br>action: () =&gt; void<br>} | No  | Primary button.<br>**value**: text of the primary button in the popup.<br>**action**: callback for clicking the primary button.|
+| secondaryButton                       | {<br>value: string,<br>action: () =&gt; void<br>} | No  | Secondary button.<br>**value**: text of the secondary button in the popup.<br>**action**: callback for clicking the secondary button.|
+| onStateChange                         | (event: { isVisible: boolean }) =&gt; void | No  | Callback for the popup status change event.<br>**isVisible**: whether the popup is visible. |
+| arrowOffset<sup>9+</sup>              | [Length](ts-types.md#length)                                 | No  | Offset of the popup arrow relative to the popup.<br>When the arrow is at the top or bottom of the popup: The value **0** indicates that the arrow is located on the leftmost, and any other value indicates the distance from the arrow to the leftmost; the arrow is centered by default.<br>When the arrow is on the left or right side of the popup: The value indicates the distance from the arrow to the top; the arrow is centered by default.<br/>When the popup is displayed on either edge of the screen, it will automatically deviate leftward or rightward to stay within the safe area. When the value is **0**, the arrow always points to the bound component. |
+| showInSubWindow<sup>9+</sup>          | boolean                                                      | No  | Whether to show the popup in the subwindow.<br/>Default value: **false**                 |
 
 ## CustomPopupOptions<sup>8+</sup>
 
-| Name                      | Type                      | Mandatory    | Description                                                |
-| -------------------------| ------------------------- | ---- | ---------------------------------------------------- |
-| builder                  | [CustomBuilder](ts-types.md#custombuilder8)  | Yes  | Popup builder.                                         |
-| placement                | [Placement](ts-appendix-enums.md#placement8) | No  | Preferred position of the popup. If the set position is insufficient for holding the popup, it will be automatically adjusted.<br>Default value: **Placement.Bottom**    |
-| popupColor               | [ResourceColor](ts-types.md#resourcecolor)  | No  | Color of the popup.                                              |
-| enableArrow              | boolean                                      | No  | Whether to display an arrow.<br>Since API version 9, if the position set for the popup is not large enough, the arrow will not be displayed. For example, if **placement** is set to **Left**, but the popup height (80 vp) is less than the sum of the arrow width (32 vp) and diameter of popup rounded corner (48 vp), the arrow will not be displayed.<br>Default value: **true**|
-| autoCancel               | boolean                                      | No  | Whether to automatically close the popup when an operation is performed on the page.<br>Default value: **true**                       |
-| onStateChange            | (event: { isVisible: boolean }) =&gt; void | No   | Callback for the popup status change event.<br>**isVisible**: whether the popup is visible. |
-| arrowOffset<sup>9+</sup>     | [Length](ts-types.md#length)                 | No  | Offset of the popup arrow relative to the popup. <br/>When the arrow is at the top or bottom of the popup: The value **0** indicates that the arrow is located on the leftmost, and any other value indicates the distance from the arrow to the leftmost; the arrow is centered by default. <br/>When the arrow is on the left or right side of the popup: The value indicates the distance from the arrow to the top; the arrow is centered by default. <br/>When the popup is displayed on either edge of the screen, it will automatically deviate leftward or rightward to stay within the safe area. When the value is **0**, the arrow always points to the bound component. |
-| showInSubWindow<sup>9+</sup> | boolean                                      | No  | Whether to show the popup in the subwindow.<br/>Default value: **false** |
+| Name                          | Type                                      | Mandatory  | Description                                      |
+| ---------------------------- | ---------------------------------------- | ---- | ---------------------------------------- |
+| builder                      | [CustomBuilder](ts-types.md#custombuilder8) | Yes   | Popup builder.                             |
+| placement                    | [Placement](ts-appendix-enums.md#placement8) | No   | Preferred position of the popup. If the set position is insufficient for holding the popup, it will be automatically adjusted.<br>Default value: **Placement.Bottom**|
+| popupColor                   | [ResourceColor](ts-types.md#resourcecolor) | No   | Color of the popup.                                |
+| enableArrow                  | boolean                                  | No   | Whether to display an arrow.<br>Since API version 9, if the position set for the popup is not large enough, the arrow will not be displayed. For example, if **placement** is set to **Left**, but the popup height (80 vp) is less than the sum of the arrow width (32 vp) and diameter of popup rounded corner (48 vp), the arrow will not be displayed.<br>Default value: **true**|
+| autoCancel                   | boolean                                  | No   | Whether to automatically close the popup when an operation is performed on the page.<br>Default value: **true**           |
+| onStateChange                | (event: { isVisible: boolean }) =&gt; void | No   | Callback for the popup status change event.<br>**isVisible**: whether the popup is visible.          |
+| arrowOffset<sup>9+</sup>     | [Length](ts-types.md#length)             | No   | Offset of the popup arrow relative to the popup.<br>When the arrow is at the top or bottom of the popup: The value **0** indicates that the arrow is located on the leftmost, and any other value indicates the distance from the arrow to the leftmost; the arrow is centered by default.<br/>When the arrow is on the left or right side of the popup: The value indicates the distance from the arrow to the top; the arrow is centered by default.<br/>When the popup is displayed on either edge of the screen, it will automatically deviate leftward or rightward to stay within the safe area. When the value is **0**, the arrow always points to the bound component. |
+| showInSubWindow<sup>9+</sup> | boolean                                  | No   | Whether to show the popup in the subwindow.<br/>Default value: **false**              |
 
 ## Example
 ```ts
@@ -101,7 +100,7 @@ struct PopupExample {
         .bindPopup(this.customPopup, {
           builder: this.popupBuilder,
           placement: Placement.Top,
-          mask: {color: 0x33000000},
+          maskColor: '0x33000000',
           popupColor: Color.Yellow,
           enableArrow: true,
           showInSubWindow: false,
diff --git a/en/application-dev/reference/arkui-ts/ts-universal-attributes-visibility.md b/en/application-dev/reference/arkui-ts/ts-universal-attributes-visibility.md
index 7bf991c7db0e1cd9c291dd740496890f06dc1af6..ffe50fcf4f532d67625d7cd512914469587df77d 100644
--- a/en/application-dev/reference/arkui-ts/ts-universal-attributes-visibility.md
+++ b/en/application-dev/reference/arkui-ts/ts-universal-attributes-visibility.md
@@ -10,7 +10,7 @@ The visibility attribute controls whether a component is visible.
 
 | Name        | Type                       | Description                                        |
 | ---------- | ---------------------------- | ------------------------------------------ |
-| visibility | [Visibility](ts-appendix-enums.md#visibility) | Whether the component is visible. Note that even if a component is invisible, it still needs to be re-created when the page is refreshed. Therefore, you are advised to use [conditional rendering](../../quick-start/arkts-rendering-control.md#conditional-rendering) instead under scenarios where consistently high performance is required.<br>Default value: **Visibility.Visible**<br>Since API version 9, this API is supported in ArkTS widgets.|
+| visibility | [Visibility](ts-appendix-enums.md#visibility) | Whether the component is visible. Note that even if a component is invisible, it still needs to be re-created when the page is refreshed. Therefore, you are advised to use [conditional rendering](../../quick-start/arkts-rendering-control-ifelse.md) instead under scenarios where consistently high performance is required.<br>Default value: **Visibility.Visible**<br>Since API version 9, this API is supported in ArkTS widgets.|
 
 
 ## Example
@@ -23,11 +23,11 @@ struct VisibilityExample {
   build() {
     Column() {
       Column() {
-        // The component is hidden, and no placeholder is used.
+        // The component is hidden and does not take up space in the layout.
         Text('None').fontSize(9).width('90%').fontColor(0xCCCCCC)
         Row().visibility(Visibility.None).width('90%').height(80).backgroundColor(0xAFEEEE)
 
-        // The component is hidden, and a placeholder is used for it in the layout.
+        // The component is hidden but takes up space in the layout.
         Text('Hidden').fontSize(9).width('90%').fontColor(0xCCCCCC)
         Row().visibility(Visibility.Hidden).width('90%').height(80).backgroundColor(0xAFEEEE)
 
diff --git a/en/application-dev/reference/errorcodes/errorcode-request.md b/en/application-dev/reference/errorcodes/errorcode-request.md
index 281c59764eacfc8a2b72ad15adfb8c65362ec19f..04018ff0de783db26d6e550c7543677efc491d0a 100644
--- a/en/application-dev/reference/errorcodes/errorcode-request.md
+++ b/en/application-dev/reference/errorcodes/errorcode-request.md
@@ -34,7 +34,7 @@ This error code is reported when a file path error occurs in invoking the **uplo
 
 **Possible Causes**
 
-The file path is incorrect.
+The file path is incorrect or the file aready exists in the path.
 
 **Solution**
 
diff --git a/en/application-dev/security/permission-list.md b/en/application-dev/security/permission-list.md
index 0258bc1d6eb6fea5a4d0f106d7a37568374f1b4a..296ef7372657da9abe0d0233be061537f1e7f9cb 100644
--- a/en/application-dev/security/permission-list.md
+++ b/en/application-dev/security/permission-list.md
@@ -2,7 +2,7 @@
 
 Before applying for required permissions, read and understand the [permission workflows](accesstoken-overview.md#permission-workflows). Then, determine the permissions required for your application.
 
-For details about how to apply for required permissions, see [Permission Application Guide](accesstoken-guidelines.md).
+For details about how to apply for required permissions, see [Applying for Permissions](accesstoken-guidelines.md).
 
 ## ohos.permission.USE_BLUETOOTH
 
@@ -66,7 +66,7 @@ Allows an application to access the notification policy on the device.
 
 ## ohos.permission.GET_TELEPHONY_STATE
 
-Allows an application to read telephony information.
+Allows an application to read telephony information. 
 
 **Permission level**: system_basic
 
@@ -166,7 +166,7 @@ Allows an application to set the system time zone.
 
 ## ohos.permission.DOWNLOAD_SESSION_MANAGER
 
-Allows an application to manage download sessions.
+Allows an application to manage the download sessions.
 
 **Permission level**: system_core
 
@@ -1577,3 +1577,33 @@ Allows an application to to mute microphones globally.
 **Authorization mode**: system_grant
 
 **Enable via ACL**: TRUE
+
+## ohos.permission.MANAGE_DISTRIBUTED_ACCOUNTS
+
+Allows an application to manage distributed account information.
+
+**Permission level**: system_basic
+
+**Authorization mode**: system_grant
+
+**Enable via ACL**: TRUE
+
+## ohos.permission.GET_DISTRIBUTED_ACCOUNTS
+
+Allows an application to obtain distributed account information.
+
+**Permission level**: system_basic
+
+**Authorization mode**: system_grant
+
+**Enable via ACL**: TRUE
+
+## ohos.permission.GET_LOCAL_ACCOUNTS
+
+Allows an application to obtain local account information.
+
+**Permission level**: system_basic
+
+**Authorization mode**: system_grant
+
+**Enable via ACL**: TRUE
diff --git a/en/application-dev/task-management/figures/bgtask_choice.png b/en/application-dev/task-management/figures/bgtask_choice.png
index f395d0a39d3e516c51d266e1bf52beab8a5d3a8a..386b368a69be56daa08789d415b93ea03bb11bd4 100644
Binary files a/en/application-dev/task-management/figures/bgtask_choice.png and b/en/application-dev/task-management/figures/bgtask_choice.png differ
diff --git a/en/application-dev/ui/arkts-common-components-switch.md b/en/application-dev/ui/arkts-common-components-switch.md
index 9a0b8592315f876c7171b97eff95ae805fe9fdd9..cdeb92ff8435b97400eac43cf04a533ccab024db 100644
--- a/en/application-dev/ui/arkts-common-components-switch.md
+++ b/en/application-dev/ui/arkts-common-components-switch.md
@@ -111,7 +111,7 @@ In this example, the **\<Toggle>** component is used to enable or disable Blueto
 
 ```ts
 // xxx.ets
-import prompt from '@ohos.promptAction';
+import promptAction from '@ohos.promptAction';
 @Entry
 @Component
 struct ToggleExample {
diff --git a/en/application-dev/ui/arkts-graphics-display.md b/en/application-dev/ui/arkts-graphics-display.md
index 504263eba186c5967808cc672548ab250e8c63d3..28279e73f5642f6c32994e4af94edbd87eb755b5 100644
--- a/en/application-dev/ui/arkts-graphics-display.md
+++ b/en/application-dev/ui/arkts-graphics-display.md
@@ -1,7 +1,7 @@
 # Displaying Images
 
 
-More often than not, you may need to display images in applications, for example, logos in buttons, online images, and local images. To display images in applications, you need to use the **\<Image>** component, which supports multiple image formats, including PNG, JPG, BMP, SVG, and GIF. For details, see [Image](../reference/arkui-ts/ts-basic-components-image.md).
+More often than not, you may need to display images in your application, for example, logos in buttons, online images, and local images. To do so, you need to use the **\<Image>** component, which supports a wide range of image formats, including PNG, JPG, BMP, SVG, and GIF. For details, see [Image](../reference/arkui-ts/ts-basic-components-image.md).
 
 
 You can call the API in the following format to create an image:
@@ -13,43 +13,43 @@ Image(src: string | Resource | media.PixelMap)
 ```
 
 
-Obtains images from the image data source. Local images and online images can be rendered and displayed. In the preceding information, src indicates the data source of the image. For details about how to load the data source, see [Loading Image Resources](#loading-image-resources).
+Obtains a local or online image from the image data source specified by **src**. For details about how to load the data source, see [Loading Image Resources](#loading-image-resources).
 
 
 ## Loading Image Resources
 
-The **\<Image>** component supports two types of images: archived images and multimedia pixel images.
+The **\<Image>** component supports two types of images: archived and pixel map.
 
 
 ### Archived Type Data Source
 
-Data sources of the archived type can be classified into local resources, online resources, Resource objects, media library datashare resources, and Base64 resources.
+Data sources of the archived type can be classified into local resources, online resources, **Resource** objects, media library data share resources, and Base64 resources.
 
 - Local resources
-  Create a folder and place the local image in any position in the ets folder.
+  Create a folder and place a local image in any position in the **ets** folder.
 
-  The **\<Image>** component imports the local image path to display the image. The root directory is the ets folder.
+  In the **\<Image>** component, import the local image path to display the image. The root directory is the **ets** folder.
 
   ```ts
   Image('images/view.jpg')
   .width(200)
   ```
 
-- Network resource
-  To use network images, you need to apply for the ohos.permission.INTERNET permission. For details, see [Applying for Permissions](../security/accesstoken-guidelines.md). In this case, the src parameter of the Image component is the link of the network image.
+- Online resources
+  To use online images, first apply for the **ohos.permission.INTERNET** permission. For details, see [Applying for Permissions](../security/accesstoken-guidelines.md). Under this scenario, the **src** parameter of the **\<Image>** component is the URL of the online image.
 
   ```ts
   Image('https://www.example.com/example.JPG') // Replace the URL with the actual URL.
   ```
 
-- Resource
-  The Resource format can be used to import images across bundles or modules. All images in the **resources** folder can be read and converted to the resource format through **$r**.
+- **Resource** objects
+  **Resource** objects can be used to import images across bundles and modules. All images in the **resources** folder can be read and converted to the **Resource** objects through **$r**.
 
-  **Figure 1** Resouces 
+  **Figure 1** resources folder 
 
   ![image-resource](figures/image-resource.jpg)
 
-  Method:
+  API:
 
   ```
   Image($r('app.media.icon'))
@@ -57,20 +57,20 @@ Data sources of the archived type can be classified into local resources, online
 
   You can also place the images in the **rawfile** folder.
 
-  **Figure 2** rawfile 
+  **Figure 2** rawfile folder
 
  ![image-rawfile](figures/image-rawfile.jpg)
 
-  Method:
+  API:
 
   ```
   Image($rawfile('snap'))
   ```
 
-- media library datashare
-  The value is a string that supports the **datashare://** path prefix, which is used to access the image path provided by the media library.
+- Media library data share resources
+  To display images from the media library, use a path string that starts with **datashare://**.
 
-  1. Call the API in to obtain the photo URL in the gallery.
+  1. Call the API to obtain the image URL in the media library.
       ​    
       ```ts
       import picker from '@ohos.file.picker';
@@ -78,9 +78,9 @@ Data sources of the archived type can be classified into local resources, online
       @Entry
       @Component
       struct Index {
-        private imgDatas: string[] = [];
-        // Obtain the photo URL set.
-        async getAllImg() {
+        @State imgDatas: string[] = [];
+        // Obtain the image URL set.
+        getAllImg() {
           let photoPicker = new picker.PhotoViewPicker();
           let result = new Array<string>();
           try {
@@ -89,33 +89,35 @@ Data sources of the archived type can be classified into local resources, online
             PhotoSelectOptions.maxSelectNumber = 5;
             let photoPicker = new picker.PhotoViewPicker();
             photoPicker.select(PhotoSelectOptions).then((PhotoSelectResult) => {
-              result = PhotoSelectResult.photoUris;
+              this.imgDatas = PhotoSelectResult.photoUris;
+              console.info('PhotoViewPicker.select successfully, PhotoSelectResult uri: ' + JSON.stringify(PhotoSelectResult));
             }).catch((err) => {
               console.error(`PhotoViewPicker.select failed with. Code: ${err.code}, message: ${err.message}`);
             });
           } catch (err) {
             console.error(`PhotoViewPicker failed with. Code: ${err.code}, message: ${err.message}`);    }
-          return result;
         }
 
         // Call the preceding function in aboutToAppear to obtain the URLs of all images in the gallery and store the URLs in imgDatas.
         async aboutToAppear() {
-          this.imgDatas = await this.getAllImg();
+          this.getAllImg();
         }
         // Use the URL of imgDatas to load the image.
         build() {
-          Grid() {
-            ForEach(this.imgDatas, item => {
-              GridItem() {
-                Image(item)
-                  .width(200)
-              }
-            }, item => JSON.stringify(item))
-          }
+          Column() {
+            Grid() {
+              ForEach(this.imgDatas, item => {
+                GridItem() {
+                  Image(item)
+                    .width(200)
+                }
+              }, item => JSON.stringify(item))
+            }
+          }.width('100%').height('100%')
         }
       }
       ```
-  2. The format of the URL obtained from the media library is as follows:
+  2. Check the format of the URL obtained from the media library is as follows:
       ​    
       ```ts
       Image('datashare:///media/5')
@@ -123,32 +125,33 @@ Data sources of the archived type can be classified into local resources, online
       ```
 
 - base64
-  The path format is data:image/[png|jpeg|bmp|webp];base64,[base64 data], in which [base64 data] indicates Base64 string data.
 
-  Base64 character strings can be used to store pixel data of images and are widely used on web pages.
+  As shown above, the URL format is data:image/[png|jpeg|bmp|webp];base64,[base64 data], in which **[base64 data]** indicates Base64 string data.
 
+  Base64 strings are widely used on web pages for storing pixel data of images.
 
-### Multimedia Pixel Map
 
-PixelMap is the pixel image after image decoding. For details, see [Image](../media/image.md). In the following example, the data returned by the loaded network image is decoded into the PixelMap format and then displayed on the Image component,
+### Pixel Map
 
-1. Creates a PixelMap state variable.
+A pixel map is a pixel image obtained after image decoding. For details, see [Image Development](../media/image-overview.md). In the following example, the data returned by the loaded online image is decoded into a pixel map, which is then displayed on the **\<Image>** component.
+
+1. Create a **PixelMap** state variable.
 
    ```ts
    @State image: PixelMap = undefined;
    ```
 
-2. Referencing multimedia.
-   Requests network images and decodes and encodes PixelMap.
+2. Reference multimedia.
+   Request an online image and implement transcoding to generate a pixel map.
 
-   1. Reference the network permission and media library permission.
+   1. Reference the network access permission and media library permission.
        ​    
        ```ts
        import http from '@ohos.net.http';
        import ResponseCode from '@ohos.net.http';
        import image from '@ohos.multimedia.image';
        ```
-   2. Enter the network image address.
+   2. Enter the online image address.
        ​    
        ```ts
        http.createHttp().request("https://www.example.com/xxx.png",
@@ -160,24 +163,24 @@ PixelMap is the pixel image after image decoding. For details, see [Image](../me
          }
        )
        ```
-   3. Encode and transcodes the data returned by the network address to the pixelMap image format.
+   3. Transcode the data returned by the online image address to a pixel map.
        ​    
        ```ts
        let code = data.responseCode;
        if(ResponseCode.ResponseCode.OK === code) {
          let imageSource = image.createImageSource(data.result);
          let options = {
-           alphaType: 0,                     // Alpha type
-           editable: false,                  // Whether the image is editable
-           pixelFormat: 3,                   // Pixel format
-           scaleMode: 1,                     // Scale mode
+           alphaType: 0,                     // Alpha type.
+           editable: false,                  // Whether the image is editable.
+           pixelFormat: 3,                   // Pixel format.
+           scaleMode: 1,                     // Scale mode.
            size: {height: 100, width: 100}
           }  // Image size.
            imageSource.createPixelMap(options).then((pixelMap) => {
            this.image = pixelMap
        })
        ```
-   4. Show pictures
+   4. Display the image.
        ​    
        ```ts
        Button ("Get Online Image")
@@ -188,11 +191,11 @@ PixelMap is the pixel image after image decoding. For details, see [Image](../me
        ```
 
 
-## Display Vector Diagram
+## Display the vector image.
 
-The **\<Image>** component can display vector images in SVG format. The supported SVG labels are svg, rect, circle, ellipse, path, line, polyline, polygon, and animate.
+The **\<Image>** component can display vector images in SVG format. The supported SVG labels are **svg**, **rect**, **circle**, **ellipse**, **path**, **line**, **polyline**, **polygon**, and **animate**.
 
-You can use the fillColor attribute to change the drawing color of an SVG image.
+You can use the **fillColor** attribute to change the fill color of an SVG image.
 
 
 ```ts
@@ -201,20 +204,22 @@ Image($r('app.media.cloud')).width(50)
 ```
 
   **Figure 3** Original image 
+
 ![screenshot_20230223_141141](figures/screenshot_20230223_141141.png)
 
-  **Figure 4** SVG image after the drawing color is set 
+  **Figure 4** SVG image after the fill color is set 
+
 ![screenshot_20230223_141404](figures/screenshot_20230223_141404.png)
 
 
 ## Adding Attributes
 
-Setting attributes for the **\<Image>** component can make the image display more flexible and achieve some customized effects. The following are examples of common attributes. For details about attributes, see [Image](../reference/arkui-ts/ts-basic-components-image.md).
+Setting attributes for the **\<Image>** component can spruce up the image with custom effects. The following are examples of common attributes. For details about all attributes, see [Image](../reference/arkui-ts/ts-basic-components-image.md).
 
 
-### Setting the Image Scale Type
+### Setting the Image Scale Mode
 
-The **objectFit** attribute is used to scale an image to a box whose height and width are determined.
+The **objectFit** attribute is used to scale an image to fit it into a container whose height and width are determined.
 
 
 ```ts
@@ -228,7 +233,7 @@ struct MyComponent {
       Row() {
         Image($r('app.media.img_2')).width(200).height(150)
           .border({ width: 1 })
-          .objectFit(ImageFit.Contain).margin(15) // Zoom out or zoom in the image based on the aspect ratio so that the image is completely displayed within the display boundary.
+          .objectFit(ImageFit.Contain).margin(15) // The image is scaled with its aspect ratio retained to fit within the display boundaries.
           .overlay('Contain', { align: Alignment.Bottom, offset: { x: 0, y: 20 } })
         Image($r('app.media.ic_img_2')).width(200).height(150)
           .border({ width: 1 })
@@ -268,7 +273,7 @@ struct MyComponent {
 
 ### Synchronously Loading Images
 
-Generally, the image loading process is performed asynchronously to avoid blocking the main thread and affecting UI interaction. In certain cases, however, the picture flickers when it is refreshed. In this case, you can use the **syncLoad** attribute to load the picture synchronously to avoid flickering. You are not advised to use this function when the image loading takes a long time. Otherwise, the page cannot respond.
+Generally, the image loading process is performed asynchronously to avoid blocking the main thread and to streamline UI interaction. In certain cases, however, the image may flicker when refreshed. If this occurs, you can use the **syncLoad** attribute to load the image synchronously to avoid flickering. You are not advised to use this attribute when the image loading takes a long time. Otherwise, the page may fail to respond.
 
 
 ```ts
@@ -277,9 +282,9 @@ Image($r('app.media.icon'))
 ```
 
 
-## Invoking Events
+## Adding Events
 
-After the **onComplete** event is bound to the Image component, necessary information about the image can be obtained after the image is successfully loaded. If the image fails to be loaded, you can also bind the onError callback function to obtain the result.
+By binding the **onComplete** event to the **\<Image>** component, you can obtain necessary information about the image after the image is successfully loaded. You can also bind the **onError** event to obtain error information when the image fails to be loaded.
 
 
 ```ts
diff --git a/en/application-dev/ui/arkts-layout-development-create-list.md b/en/application-dev/ui/arkts-layout-development-create-list.md
index c8b97ae2e69105e9e9aabd5c51e0ec725750f7a1..21542f53651ea476aa92a04abb98787ca5c3768a 100644
--- a/en/application-dev/ui/arkts-layout-development-create-list.md
+++ b/en/application-dev/ui/arkts-layout-development-create-list.md
@@ -5,7 +5,7 @@
 
 A list is a container that displays a collection of items. If the list items go beyond the screen, the list can scroll to reveal the content off the screen. A list is applicable for presenting similar data types or data type sets, such as images and text. For example, it can be used to present a collection of contacts, songs, and items to shop.
 
-Use lists to easily and efficiently display structured, scrollable information. You can provide a single view of rows or columns by arranging the [\<ListItemGroup>](../reference/arkui-ts/ts-container-listitemgroup.md/) or [\<ListItem>](../reference/arkui-ts/ts-container-listitem.md) child components linearly in a vertical or horizontal direction in the [\<List>](../reference/arkui-ts/ts-container-list.md/) component, or use [ForEach](../quick-start/arkts-rendering-control-foreach.md) to iterate over a group of rows or columns, or mix any number of single views and **ForEach** structures to build a list. The **\<List>** component supports the generation of child components in various [rendering](../quick-start/arkts-rendering-control-overview.md) modes, including conditional rendering, rendering of repeated content, and lazy data loading.
+Use lists to easily and efficiently display structured, scrollable information. You can provide a single view of rows or columns by arranging the [\<ListItemGroup>](../reference/arkui-ts/ts-container-listitemgroup.md) or [\<ListItem>](../reference/arkui-ts/ts-container-listitem.md) child components linearly in a vertical or horizontal direction in the [\<List>](../reference/arkui-ts/ts-container-list.md) component, or use [ForEach](../quick-start/arkts-rendering-control-foreach.md) to iterate over a group of rows or columns, or mix any number of single views and **ForEach** structures to build a list. The **\<List>** component supports the generation of child components in various [rendering](../quick-start/arkts-rendering-control-overview.md) modes, including conditional rendering, rendering of repeated content, and lazy data loading.
 
 
 ## Layout and Constraints
@@ -95,7 +95,7 @@ List() {
 
 The cross axis layout of the **\<List>** component can be set using the **lanes** and **alignListItem** attributes. The **lanes** attribute controls the number of list items along the cross axis, and the **alignListItem** attribute controls the alignment mode of child components along the cross axis.
 
-The **lanes** attribute of the **\<List>** component is useful in building a list that auto-adapts the numbers of rows or columns on devices of different sizes. Its value type is number or [LengthConstrain](../reference/arkui-ts/ts-types.md/#lengthconstrain). If you are building a two-column vertical list shown on the right in Figure 2, set the **lanes** attribute to **2**. The default value of **lanes** is **1**.
+The lanes attribute of the **\<List>** component is useful in building a list that auto-adapts the numbers of rows or columns on devices of different sizes. Its value type is number or [LengthConstrain](../reference/arkui-ts/ts-types.md#lengthconstrain). If you are building a two-column vertical list shown on the right in Figure 2, set the **lanes** attribute to **2**. The default value of **lanes** is **1**.
 
 
 ```ts
@@ -318,7 +318,7 @@ When the total height (width) of list items exceeds the screen height (width), t
 
 ![en-us_image_0000001511740544](figures/en-us_image_0000001511740544.gif)
 
-When using the **\<List>** component, you can use the **scrollBar** attribute to control the display of the list scrollbar. The value type of **scrollBar** is [BarState](../reference/arkui-ts/ts-appendix-enums.md/#barstate). When the value is **BarState.Auto**, the scrollbar is displayed as required: It is displayed when the scrollbar area is touched and becomes thicker when being dragged; it automatically disappears after 2 seconds of inactivity.
+When using the **\<List>** component, you can use the **scrollBar** attribute to control the display of the list scrollbar. The value type of **scrollBar** is [BarState](../reference/arkui-ts/ts-appendix-enums.md#barstate). When the value is **BarState.Auto**, the scrollbar is displayed as required: It is displayed when the scrollbar area is touched and becomes thicker when being dragged; it automatically disappears after 2 seconds of inactivity.
 
 
 ```ts
@@ -478,7 +478,7 @@ In some cases you may want to control the scrolling position of a list. For exam
 
 ![en-us_image_0000001511900520](figures/en-us_image_0000001511900520.gif)
 
-When the **\<List>** component is initialized, you can use the **scroller** parameter to bind a [Scroller](../reference/arkui-ts/ts-container-scroll.md/#scroller) object to control the scrolling of the list. In this example of a news page list, the **scrollToIndex** API of the **Scroller** object is used to scroll the list to the list item with the specified index. This allows the user to return to the top of the list by clicking a specific button.
+When the **\<List>** component is initialized, you can use the **scroller** parameter to bind a [Scroller](../reference/arkui-ts/ts-container-scroll.md#scroller) object to control the scrolling of the list. In this example of a news page list, the **scrollToIndex** API of the **Scroller** object is used to scroll the list to the list item with the specified index. This allows the user to return to the top of the list by clicking a specific button.
 
 First, you need to create a **Scroller** object **listScroller**.
 
@@ -520,7 +520,7 @@ Another common example is a scrolling list working with a multi-level index bar,
 
 ![en-us_image_0000001563060769](figures/en-us_image_0000001563060769.gif)
 
-As shown above, when the contacts list scrolls from group A to B, the alphabetical index bar on the right also changes from A to B. This scenario can be implemented by listening for the **onScrollIndex** event of the **\<List>** component. The alphabet index bar is implemented using the [\<AlphabetIndexer>](../reference/arkui-ts/ts-container-alphabet-indexer.md/) component.
+As shown above, when the contacts list scrolls from group A to B, the alphabetical index bar on the right also changes from A to B. This scenario can be implemented by listening for the **onScrollIndex** event of the **\<List>** component. The alphabet index bar is implemented using the [\<AlphabetIndexer>](../reference/arkui-ts/ts-container-alphabet-indexer.md) component.
 
 When the list scrolls, the **selectedIndex** value of the letter to highlight in the alphabet index bar is recalculated based on the **firstIndex** value of the item to which the list has scrolled. In the **\<AlphabetIndexer>** component, the index of the highlighted item is set through the **selected** attribute. When the value of **selectedIndex** changes, the **\<AlphabetIndexer>** component is re-rendered to highlight the corresponding letter.
 
@@ -566,7 +566,7 @@ struct ContactsList {
 
 Swipe menus are common in many applications. For example, a messaging application generally provides a swipe-to-delete feature for its message list. This feature allows users to delete a message by swiping left on it in the list and touching the delete button, as shown in the following figure.
 
-  **Figure 15** Swipe-to-delete feature 
+**Figure 15** Swipe-to-delete feature 
 
 ![en-us_image_0000001563060773](figures/en-us_image_0000001563060773.gif)
 
@@ -621,7 +621,7 @@ A mark is an intuitive, unintrusive visual indicator to draw attention and conve
 
 ![en-us_image_0000001511580952](figures/en-us_image_0000001511580952.png)
 
-To add a mark, you can use the [\<Badge>](../reference/arkui-ts/ts-container-badge.md/) component in **\<ListItem>**. The **\<Badge>** component is a container that can be attached to another component for tagging.
+To add a mark, you can use the [\<Badge>](../reference/arkui-ts/ts-container-badge.md) component in **\<ListItem>**. The **\<Badge>** component is a container that can be attached to another component for tagging.
 
 In this example, when implementing the **\<Image>** component for presenting the profile picture of a list item, add it to **\<Badge>** as a child component.
 
@@ -643,7 +643,7 @@ Badge({
 
 ## Implementing Pull-Down-to-Refresh and Pull-Up-to-Load
 
-The pull-down-to-refresh and pull-up-to-load features are widely used in mobile applications, such as news applications. In effect, the implementation of these two features follows the same process: (1) As response to a [touch event](../reference/arkui-ts/ts-universal-events-touch.md/), a refresh or load view is displayed at the top or bottom of the page; (2) when the refresh or load is complete, the refresh or load view is hidden.
+The pull-down-to-refresh and pull-up-to-load features are widely used in mobile applications, such as news applications. In effect, the implementation of these two features follows the same process: (1) As response to a [touch event](../reference/arkui-ts/ts-universal-events-touch.md), a refresh or load view is displayed at the top or bottom of the page; (2) when the refresh or load is complete, the refresh or load view is hidden.
 
 The following describes the implementation of the pull-and-refresh feature:
 
@@ -830,12 +830,3 @@ The following uses a vertical list as an example:
 >
 >2. When a list uses data lazy loading, all list items except the list items in the display area and the cached list items are destroyed.
 
-##  
-
- 
-
--  
-
--  
-
--  
diff --git a/en/application-dev/ui/arkts-layout-development-linear.md b/en/application-dev/ui/arkts-layout-development-linear.md
index 4676117a10cb8d522e38922d5d99a14d2e281a26..0a4ee42250a74dacaf1c94edc1664e8cbd000073 100644
--- a/en/application-dev/ui/arkts-layout-development-linear.md
+++ b/en/application-dev/ui/arkts-layout-development-linear.md
@@ -22,11 +22,11 @@ Linear layout is the most frequently used layout in development, built with the
 
 - Layout child element: element inside the layout container.
 
-- Main axis: axis along which child elements are laid out by default in the linear layout container. The main axis is vertical for the **\<Row>** container and horizontal for the **\<Column>** container.
+- Main axis: axis along which child elements are laid out by default in the linear layout container. The main axis is horizontal for the **\<Row>** container and vertical for the **\<Column>** container.
 
-- Cross axis: axis that runs perpendicular to the main axis. The cross axis is horizontal for the **\<Row>** container and vertical for the **\<Column>** container.
+- Cross axis: axis that runs perpendicular to the main axis. The cross axis is vertical for the **\<Row>** container and horizontal for the **\<Column>** container.
 
-- Spacing: vertical distance between layout child elements.
+- Spacing: vertical distance between child elements.
 
 
 ## Spacing of Layout Child Elements in Arrangement Direction
diff --git a/en/application-dev/ui/arkts-performance-improvement-recommendation.md b/en/application-dev/ui/arkts-performance-improvement-recommendation.md
index 8d144767653ac90a89d9e72a83a292228c024a11..a9d8947578c4169b0980b1b719cdc68587b93ca1 100644
--- a/en/application-dev/ui/arkts-performance-improvement-recommendation.md
+++ b/en/application-dev/ui/arkts-performance-improvement-recommendation.md
@@ -219,54 +219,6 @@ struct MyComponent {
 
 ![flex1](figures/flex1.PNG)
 
-## Setting Width and Height for \<List> Components
-
-When a **\<List>** component is nested within a **\<Scroll>** component, all of its content will be loaded if its width and height is not specified, which may result in performance drop.
-
-```ts
-@Entry
-@Component
-struct MyComponent {
-  private arr: number[] = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9];
-
-  build() {
-    Scroll() {
-      List() {
-        ForEach(this.arr, (item) => {
-          ListItem() {
-            Text(`item value: ${item}`).fontSize(30).margin({ left: 10 })
-          }.height(100)
-        }, (item) => item.toString())
-      }
-    }.backgroundColor(Color.Pink)
-  }
-}
-```
-
-Therefore, in the above scenario, you are advised to set the width and height for the **\<List>** component as follows:
-
-```ts
-@Entry
-@Component
-struct MyComponent {
-  private arr: number[] = [0, 1, 2, 3, 4, 5, 6, 7, 8, 9];
-
-  build() {
-    Scroll() {
-      List() {
-        ForEach(this.arr, (item) => {
-          ListItem() {
-            Text(`item value: ${item}`).fontSize(30).margin({ left: 10 })
-          }.height(100)
-        }, (item) => item.toString())
-      }.width('100%').height(500)
-    }.backgroundColor(Color.Pink)
-  }
-}
-```
-
-![list1](figures/list1.gif)
-
 ## Minimizing White Blocks During Swiping
 
 To minimize white blocks during swiping, expand the UI loading range by increasing the value of **cachedCount** for the **\<List>** and **\<Grid>** components. **cachedCount** indicates the number of list or grid items preloaded outside of the screen. 
diff --git a/en/application-dev/ui/figures/arrangement-child-elements-column.png b/en/application-dev/ui/figures/arrangement-child-elements-column.png
new file mode 100644
index 0000000000000000000000000000000000000000..049559f1910fd074ceba79d17c50aea1b71d7916
Binary files /dev/null and b/en/application-dev/ui/figures/arrangement-child-elements-column.png differ
diff --git a/en/application-dev/ui/figures/arrangement-child-elements-row.png b/en/application-dev/ui/figures/arrangement-child-elements-row.png
new file mode 100644
index 0000000000000000000000000000000000000000..d9c027339002e35b3a880fd45fc8e6cf5ea9a3aa
Binary files /dev/null and b/en/application-dev/ui/figures/arrangement-child-elements-row.png differ
diff --git a/en/application-dev/ui/figures/arrangement-direction-column-sample.png b/en/application-dev/ui/figures/arrangement-direction-column-sample.png
new file mode 100644
index 0000000000000000000000000000000000000000..88ed20fb601f1106e5015d94edd2ea8a9aa01826
Binary files /dev/null and b/en/application-dev/ui/figures/arrangement-direction-column-sample.png differ
diff --git a/en/application-dev/ui/figures/arrangement-direction-column.png b/en/application-dev/ui/figures/arrangement-direction-column.png
new file mode 100644
index 0000000000000000000000000000000000000000..2d0d772e2f36c4e822d56565bfbbfa7e840b042b
Binary files /dev/null and b/en/application-dev/ui/figures/arrangement-direction-column.png differ
diff --git a/en/application-dev/ui/figures/arrangement-direction-row.png b/en/application-dev/ui/figures/arrangement-direction-row.png
new file mode 100644
index 0000000000000000000000000000000000000000..d2cd9037542c7700c127a8a4f4631e1e51a080a2
Binary files /dev/null and b/en/application-dev/ui/figures/arrangement-direction-row.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511421240.png b/en/application-dev/ui/figures/en-us_image_0000001511421240.png
new file mode 100644
index 0000000000000000000000000000000000000000..1dcef5d17c1a081235b1ce2fb61878675a1c15ab
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511421240.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511421328.png b/en/application-dev/ui/figures/en-us_image_0000001511421328.png
new file mode 100644
index 0000000000000000000000000000000000000000..b8f18ea013fafc593e6c767d2c68e753167e44e5
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511421328.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511421332.png b/en/application-dev/ui/figures/en-us_image_0000001511421332.png
new file mode 100644
index 0000000000000000000000000000000000000000..6d8fe648cee5e8677c5a58cd699a831c8d504975
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511421332.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511421336.png b/en/application-dev/ui/figures/en-us_image_0000001511421336.png
new file mode 100644
index 0000000000000000000000000000000000000000..eadeec34e24156f33ff55a84c633009ed00ab341
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511421336.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511421344.png b/en/application-dev/ui/figures/en-us_image_0000001511421344.png
new file mode 100644
index 0000000000000000000000000000000000000000..4d97b954671fce83fa8e0728a197c00b0cfb8b16
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511421344.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511421348.png b/en/application-dev/ui/figures/en-us_image_0000001511421348.png
new file mode 100644
index 0000000000000000000000000000000000000000..3dccdeed9c73a367170d4ba028adac0533329514
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511421348.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511421352.png b/en/application-dev/ui/figures/en-us_image_0000001511421352.png
new file mode 100644
index 0000000000000000000000000000000000000000..3e9c6ec747da89479ec2938e66628d515874d2b4
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511421352.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511421356.png b/en/application-dev/ui/figures/en-us_image_0000001511421356.png
new file mode 100644
index 0000000000000000000000000000000000000000..fc6d0fa33e614c536f7f46296becd248e226ed88
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511421356.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511580940.png b/en/application-dev/ui/figures/en-us_image_0000001511580940.png
new file mode 100644
index 0000000000000000000000000000000000000000..9a13e9c6cb2940aac6cddc9e7130d1af77ba0845
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511580940.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511580948.png b/en/application-dev/ui/figures/en-us_image_0000001511580948.png
new file mode 100644
index 0000000000000000000000000000000000000000..a82b4fccd8796009161f3a012c8a34f0dab4a905
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511580948.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511580952.png b/en/application-dev/ui/figures/en-us_image_0000001511580952.png
new file mode 100644
index 0000000000000000000000000000000000000000..30259d8db7a70c2a65673a55b2e2ff9c2f98820a
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511580952.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511580956.png b/en/application-dev/ui/figures/en-us_image_0000001511580956.png
new file mode 100644
index 0000000000000000000000000000000000000000..4b32f138d5ad5ef8dc09d8bcf3624fa18c10fd70
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511580956.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511580960.png b/en/application-dev/ui/figures/en-us_image_0000001511580960.png
new file mode 100644
index 0000000000000000000000000000000000000000..67ff9d87ffc8da866fca5348da01b55c801d3cfc
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511580960.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511580964.png b/en/application-dev/ui/figures/en-us_image_0000001511580964.png
new file mode 100644
index 0000000000000000000000000000000000000000..99b123c307de1a6eae2bdc7e8bb410c4b42bf300
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511580964.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511580968.png b/en/application-dev/ui/figures/en-us_image_0000001511580968.png
new file mode 100644
index 0000000000000000000000000000000000000000..a584b0bdff74f412dc2d219d99e9bbf5d78bf85a
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511580968.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511740460.png b/en/application-dev/ui/figures/en-us_image_0000001511740460.png
new file mode 100644
index 0000000000000000000000000000000000000000..ae0a8c18848c94a7a271a0c0b9424a3fa8ffb930
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511740460.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511740544.gif b/en/application-dev/ui/figures/en-us_image_0000001511740544.gif
new file mode 100644
index 0000000000000000000000000000000000000000..d86e426dcffcd60213f37faf7c9209ca5a45233f
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511740544.gif differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511740548.png b/en/application-dev/ui/figures/en-us_image_0000001511740548.png
new file mode 100644
index 0000000000000000000000000000000000000000..fcbe7db006e11d9ed43284ed0150797c60f62351
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511740548.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511740552.gif b/en/application-dev/ui/figures/en-us_image_0000001511740552.gif
new file mode 100644
index 0000000000000000000000000000000000000000..f6fc004144fec36d4c94abc65ae9e553c859a135
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511740552.gif differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511740556.gif b/en/application-dev/ui/figures/en-us_image_0000001511740556.gif
new file mode 100644
index 0000000000000000000000000000000000000000..6df8e5a53ef683d8a6889b0a447497c7e87f056b
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511740556.gif differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511740564.png b/en/application-dev/ui/figures/en-us_image_0000001511740564.png
new file mode 100644
index 0000000000000000000000000000000000000000..a08497fe9d7337e09524fd998dee304c0d4712dd
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511740564.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511900516.png b/en/application-dev/ui/figures/en-us_image_0000001511900516.png
new file mode 100644
index 0000000000000000000000000000000000000000..136fbcbb5192d5c935f64b4723e72e909c96e4a3
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511900516.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511900520.gif b/en/application-dev/ui/figures/en-us_image_0000001511900520.gif
new file mode 100644
index 0000000000000000000000000000000000000000..875d53e13f92ab953b13ae666c92170afc4fc142
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511900520.gif differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511900524.gif b/en/application-dev/ui/figures/en-us_image_0000001511900524.gif
new file mode 100644
index 0000000000000000000000000000000000000000..80ee68958c80502be31ddcecc22f198c14a4c335
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511900524.gif differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001511900532.png b/en/application-dev/ui/figures/en-us_image_0000001511900532.png
new file mode 100644
index 0000000000000000000000000000000000000000..77dcb681451df58a99e4b8572f6573e12a39d6aa
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001511900532.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562700501.png b/en/application-dev/ui/figures/en-us_image_0000001562700501.png
new file mode 100644
index 0000000000000000000000000000000000000000..ee24968f7a63f08dba9c6eb7b71bdcfe2bf8c736
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562700501.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562700505.png b/en/application-dev/ui/figures/en-us_image_0000001562700505.png
new file mode 100644
index 0000000000000000000000000000000000000000..937a2584e24522a7c38e274cb8031cb796e08b4c
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562700505.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562700509.png b/en/application-dev/ui/figures/en-us_image_0000001562700509.png
new file mode 100644
index 0000000000000000000000000000000000000000..a23476d1a84a709d41ce9a19d17216baae2cfbf2
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562700509.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562700517.png b/en/application-dev/ui/figures/en-us_image_0000001562700517.png
new file mode 100644
index 0000000000000000000000000000000000000000..d830f303086d7ab27244f88cffa7a359ec62f92a
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562700517.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562700521.png b/en/application-dev/ui/figures/en-us_image_0000001562700521.png
new file mode 100644
index 0000000000000000000000000000000000000000..f2a737c020c5ea9c1a9bf4ac73cafe677c73917c
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562700521.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562700525.png b/en/application-dev/ui/figures/en-us_image_0000001562700525.png
new file mode 100644
index 0000000000000000000000000000000000000000..88552579e7181155498b23934ff4707317b1e84e
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562700525.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562820877.gif b/en/application-dev/ui/figures/en-us_image_0000001562820877.gif
new file mode 100644
index 0000000000000000000000000000000000000000..2241c494257d51062dcb4b47911430d49bbadb7b
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562820877.gif differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562820881.png b/en/application-dev/ui/figures/en-us_image_0000001562820881.png
new file mode 100644
index 0000000000000000000000000000000000000000..592e6591f61e6e9d62023849cbcf1a651bb1691c
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562820881.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562820893.png b/en/application-dev/ui/figures/en-us_image_0000001562820893.png
new file mode 100644
index 0000000000000000000000000000000000000000..804c9f6958b6a58b2fad943bcab3149f31820fe0
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562820893.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562820897.png b/en/application-dev/ui/figures/en-us_image_0000001562820897.png
new file mode 100644
index 0000000000000000000000000000000000000000..e3b670e7d9cb1fff6d373323d4ec73740370c052
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562820897.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562940581.png b/en/application-dev/ui/figures/en-us_image_0000001562940581.png
new file mode 100644
index 0000000000000000000000000000000000000000..0b64e7a367f5be3f1b44044cf93fdeb37ed374a1
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562940581.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562940585.png b/en/application-dev/ui/figures/en-us_image_0000001562940585.png
new file mode 100644
index 0000000000000000000000000000000000000000..f6a9c832826019ed0d831c8b513954c87264d3c6
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562940585.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562940589.png b/en/application-dev/ui/figures/en-us_image_0000001562940589.png
new file mode 100644
index 0000000000000000000000000000000000000000..d01c3595f202b50050ff1763293cd7cedba234b6
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562940589.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562940601.png b/en/application-dev/ui/figures/en-us_image_0000001562940601.png
new file mode 100644
index 0000000000000000000000000000000000000000..5631f463b0e3860ddf113c32b138550f765cb0c8
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562940601.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001562940609.gif b/en/application-dev/ui/figures/en-us_image_0000001562940609.gif
new file mode 100644
index 0000000000000000000000000000000000000000..14f3d25cbf137366ce3c2bb93f683d75a9297597
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001562940609.gif differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001563060761.png b/en/application-dev/ui/figures/en-us_image_0000001563060761.png
new file mode 100644
index 0000000000000000000000000000000000000000..9f654bfa110b6116f5957e01b99d34c7cada76ae
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001563060761.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001563060765.png b/en/application-dev/ui/figures/en-us_image_0000001563060765.png
new file mode 100644
index 0000000000000000000000000000000000000000..de4848b9c7750dcef6e9216e9f68604203b1620a
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001563060765.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001563060769.gif b/en/application-dev/ui/figures/en-us_image_0000001563060769.gif
new file mode 100644
index 0000000000000000000000000000000000000000..bb1ac0f266c1e2eaa4756496832bb28beed4bf39
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001563060769.gif differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001563060773.gif b/en/application-dev/ui/figures/en-us_image_0000001563060773.gif
new file mode 100644
index 0000000000000000000000000000000000000000..b1760403750123b2f3c589d0f20697c57080966d
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001563060773.gif differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001563060777.png b/en/application-dev/ui/figures/en-us_image_0000001563060777.png
new file mode 100644
index 0000000000000000000000000000000000000000..bfb4159928f562004b4551d36b4b13e495a4e3c0
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001563060777.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001563060781.png b/en/application-dev/ui/figures/en-us_image_0000001563060781.png
new file mode 100644
index 0000000000000000000000000000000000000000..1216da4afc8b43ab12b27993c33a8078c6a2e44c
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001563060781.png differ
diff --git a/en/application-dev/ui/figures/en-us_image_0000001563060785.png b/en/application-dev/ui/figures/en-us_image_0000001563060785.png
new file mode 100644
index 0000000000000000000000000000000000000000..fc052ef293a27904248d7d6af2a7e13da3be666a
Binary files /dev/null and b/en/application-dev/ui/figures/en-us_image_0000001563060785.png differ
diff --git a/en/application-dev/ui/figures/horizontal-arrangement-child-column.png b/en/application-dev/ui/figures/horizontal-arrangement-child-column.png
new file mode 100644
index 0000000000000000000000000000000000000000..2cc5e50cb9bc992ef155af9d8a8456cc1193b6d8
Binary files /dev/null and b/en/application-dev/ui/figures/horizontal-arrangement-child-column.png differ
diff --git a/en/application-dev/ui/figures/horizontal-arrangement-child-row.png b/en/application-dev/ui/figures/horizontal-arrangement-child-row.png
new file mode 100644
index 0000000000000000000000000000000000000000..b2c1d11e2694a576e4a1cfb19919cb49aafa63c4
Binary files /dev/null and b/en/application-dev/ui/figures/horizontal-arrangement-child-row.png differ
diff --git a/en/application-dev/ui/figures/image-rawfile.jpg b/en/application-dev/ui/figures/image-rawfile.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..1629225e1db6c261156615de42a3ea00d2537f32
Binary files /dev/null and b/en/application-dev/ui/figures/image-rawfile.jpg differ
diff --git a/en/application-dev/ui/figures/image-resource.jpg b/en/application-dev/ui/figures/image-resource.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..3256f3792813e1c34f978f290630cca92485d5d8
Binary files /dev/null and b/en/application-dev/ui/figures/image-resource.jpg differ
diff --git a/en/application-dev/ui/figures/list1.gif b/en/application-dev/ui/figures/list1.gif
deleted file mode 100644
index f421df651539da975e30d2294598e587e44d665e..0000000000000000000000000000000000000000
Binary files a/en/application-dev/ui/figures/list1.gif and /dev/null differ
diff --git a/en/application-dev/ui/figures/screenshot_20230223_141404.png b/en/application-dev/ui/figures/screenshot_20230223_141404.png
new file mode 100644
index 0000000000000000000000000000000000000000..040d48397ab11cb433043ce0b50e8e46cc94476a
Binary files /dev/null and b/en/application-dev/ui/figures/screenshot_20230223_141404.png differ
diff --git a/en/application-dev/ui/figures/vertial-arrangement-child-column.png b/en/application-dev/ui/figures/vertial-arrangement-child-column.png
new file mode 100644
index 0000000000000000000000000000000000000000..dd4e9106e882055dc637bb110508a66b783f7c9d
Binary files /dev/null and b/en/application-dev/ui/figures/vertial-arrangement-child-column.png differ
diff --git a/en/application-dev/ui/figures/vertial-arrangement-child-row.png b/en/application-dev/ui/figures/vertial-arrangement-child-row.png
new file mode 100644
index 0000000000000000000000000000000000000000..160cde8b8a463a3f320764030371baebefbae872
Binary files /dev/null and b/en/application-dev/ui/figures/vertial-arrangement-child-row.png differ
diff --git a/en/application-dev/website.md b/en/application-dev/website.md
index 616b92cf750a8fef188d1219ed94e44352a0c97b..b81c20b8197c08ba9a66ae0d6f1f11e84f5740d9 100644
--- a/en/application-dev/website.md
+++ b/en/application-dev/website.md
@@ -26,8 +26,6 @@
         - [HAR](quick-start/har-package.md)
         - HSP
           - [In-Application HSP Development](quick-start/in-app-hsp.md)
-      - Atomic Service
-        - [Atomic Service Development](quick-start/atomicService.md)
       - Quick Fix
         - [Quick Fix Overview](quick-start/quickfix-principles.md)
         - [CLI-based Quick Fix Development](quick-start/quickfix-debug.md)
@@ -737,6 +735,7 @@
       - [Swiper](reference/arkui-ts/ts-container-swiper.md)
       - [Tabs](reference/arkui-ts/ts-container-tabs.md)
       - [TabContent](reference/arkui-ts/ts-container-tabcontent.md)
+      - [WaterFlow](reference/arkui-ts/ts-container-waterflow.md)
     - Media Component
       - [Video](reference/arkui-ts/ts-media-components-video.md)
     - Drawing Components
@@ -1533,12 +1532,20 @@
 - FAQs
   - [Full SDK Compilation Guide](quick-start/full-sdk-compile-guide.md)
   - [Guide to Switching to Full SDK](quick-start/full-sdk-switch-guide.md)
-  - [Ability Framework Development](faqs/faqs-ability.md)
-  - [Resource Management Development](faqs/faqs-globalization.md)
+  - [Ability Development](faqs/faqs-ability.md)
+  - [Bundle Management Development](faqs/faqs-bundle-management.md)
+  - [Resource Manager Development](faqs/faqs-globalization.md)
   - [Common Event and Notification Development](faqs/faqs-event-notification.md)
-  - [Graphics and Image Development](faqs/faqs-graphics.md)
+  - [Graphics Development](faqs/faqs-graphics.md)
+  - [Window Management Development](faqs/faqs-window-manager.md)
+  - [Multimedia Development](faqs/faqs-multimedia.md)
+  - [Basic Security Capability Development](faqs/faqs-security.md)
+  - [Ability Access Control Development](faqs/faqs-ability-access-control.md)
+  - [Data Management Development](faqs/faqs-distributed-data-management.md)
   - [File Management Development](faqs/faqs-file-management.md)
   - [Network Management Development](faqs/faqs-network-management.md)
   - [DFX Development](faqs/faqs-dfx.md)
+  - [Pan-Sensor Development](faqs/faqs-sensor.md)
   - [Startup Development](faqs/faqs-startup.md)
-  - [Usage of Third- and Fourth-Party Libraries](faqs/faqs-third-fourth-party-library.md)
\ No newline at end of file
+  - [Distributed Device Development](faqs/faqs-distributed-device-profile.md)
+  - [Usage of Third- and Fourth-Party Libraries](faqs/faqs-third-fourth-party-library.md)
diff --git a/en/contribute/OpenHarmony-security-test-guide.md b/en/contribute/OpenHarmony-security-test-guide.md
index 5b6365eaf49d50bb5759a83fb23d5e130bc0587d..fe7bc1c639175637cd14a829fff8cc92b19f3e30 100644
--- a/en/contribute/OpenHarmony-security-test-guide.md
+++ b/en/contribute/OpenHarmony-security-test-guide.md
@@ -8,7 +8,7 @@ With reference to industry standards and best practices, this document provides
 
 - Use the OpenHarmony gated check-in to scan your code and clear all alarms.
 
-- Use the compilation option scanning tool to scan your binary file and ensure that the settings of all the compilation options comply with the [OpenHarmony Compilation Specifications].
+- Use the compilation option scanning tool to scan your binary file and ensure that the settings of all the compilation options comply with the OpenHarmony Compilation Specifications.
 
 - For the module that receives and processes user-mode parameters, develop gray-box and white-box fuzz testing suites according to the [Fuzz Testing Guide](https://gitee.com/openharmony/test_developertest/tree/master/libs/fuzzlib) and complete the tests.
 
diff --git a/en/contribute/Readme-EN.md b/en/contribute/Readme-EN.md
index 24fcbe6d10db5ead1172a88577af8523330e2f1e..0065398b64877b5631e2beae2442b160a4c00c04 100755
--- a/en/contribute/Readme-EN.md
+++ b/en/contribute/Readme-EN.md
@@ -6,7 +6,6 @@
 -   [Contribution Process](contribution-process.md)
 -   [Auto-Test](../readme/test.md)
 -   [Documentation Contribution](documentation-contribution.md)
--   [Writing Instructions](writing-instructions.md)
 -   [Communication in Community](communication-in-community.md)
 -   [FAQs](FAQ.md)
 
diff --git a/en/contribute/documentation-contribution.md b/en/contribute/documentation-contribution.md
index caae52944c7e8b8ea312d094d5b461846d97015c..6e8273f2f4f288e09576cac4d99b8979c8de6fee 100755
--- a/en/contribute/documentation-contribution.md
+++ b/en/contribute/documentation-contribution.md
@@ -5,7 +5,6 @@ You are welcome to make contributions to OpenHarmony documentation, in any of th
 Excellent contributors will be awarded and the contributions will be publicized in the developer community.
 
 -   [Contribution Methods](#contribution-methods)
--   [Writing Instructions](writing-instructions.md)
 
 ## Content Copyright
 
@@ -15,7 +14,7 @@ OpenHarmony has the right to modify the adopted content according to the communi
 
 ## License
 
-[Creative Commons License version 4.0](https://creativecommons.org/licenses/by/4.0/legalcode)
+Creative Commons License version 4.0
 
 ## Contribution Methods
 
@@ -27,9 +26,9 @@ Your feedback matters. Submit issues and leave as detailed information as possib
 2.  Click **New** to submit the issue. The Docs team will confirm the issue.
 
 > **NOTE**
->
-> **How can I provide a high-quality issue?**  
 > 
+> **How can I provide a high-quality issue?**  
+>
 > -   Provide a clear description of the issue, including the missing, outdated, incorrect, or to-be-improved content.
 > -   Explain the impact of this issue on users.
 > -   Limit the scope of the given issue to a specific task. If multiple fields are involved, break the issue down into smaller ones. For example, "Documents need to be optimized" is a broad issue, whereas "XX development guide lacks introduction to step XXX" is specific and operable.
diff --git a/en/contribute/introducing-open-source-software.md b/en/contribute/introducing-open-source-software.md
index 5e6422ec95485848e98dbe9796c96c274f9d5662..ed69407fee9bfb6f366fa299b3608edcbab93ea5 100644
--- a/en/contribute/introducing-open-source-software.md
+++ b/en/contribute/introducing-open-source-software.md
@@ -3,7 +3,7 @@
 ## Purpose
 
 In OpenHarmony, software that meets [The Open Source Definition](https://opensource.org/docs/osd) is recognized as open-source software.
-Providing easy-to-use and quality open-source software for developers across the globe from a wide range of backgrounds is an important goal of the OpenHarmony community. To ensure the overall quality of the OpenHarmony project, this guide is specially formulated for the contributors' reference.
+Providing easy-to-use and quality open-source software for developers across the globe from a wide range of backgrounds is an important goal of the OpenHarmony community. To ensure the overall quality of the OpenHarmony project, this guide is specially formulated for your reference.
 
 ## Scope
 
@@ -11,8 +11,8 @@ This guide applies to all third-party open-source software to be introduced to t
 
 ## Improvements and Revisions
 
-1. This document is drafted and maintained by the OpenHarmony SIG QA. What you are reading now is the latest version of this document.
-     
+1. This document is drafted and maintained by the OpenHarmony QA SIG. What you are reading now is the latest version of this document.
+   
 2. Any addition, modification, or deletion of the principles mentioned in this document can be traced in the tracing system.
 3. The PMC reviews and finalizes the principles after thorough discussion in the community.
 
@@ -40,6 +40,22 @@ For easier maintenance and evolution, comply with the following principles when
 12. If the software you introduce depends on other open-source software, do not nest the dependency software in the subdirectory of the software you introduce. Instead, remove all dependency software items from the software you introduce and place them in an independent repository named in the format of **third_party_*****dependencySoftwareName***. If you nest the dependency software, the same software may have multiple versions, security vulnerabilities in earlier versions may fail to be resolved in a timely manner, and open source compliance issues may arise.
     - Prefix the component names of the dependency software in the **BUILD.gn** file with the name of the software you introduce, for example, part_name = "introducedSoftwareName_dependencySoftwareName".
     - The software you introduce and dependency software are built separately. Use **external_deps** to resolve the inter-component dependency between the two pieces of software.
+13. Comply with the following requirements when archiving third-party open-source software:
+    - In principle, third-party open-source software that meets the OpenHarmony license introduction requirements should be stored in the **third_party** root directory. You can store it in another directory only if you have sufficient reasons.
+    - For third-party open-source software that is introduced by the development board and cannot be incorporated into the OpenHarmony system platform, you can request to create a directory with the name of the open-source software and archive the **README.OpenSource** file in the directory. In addition, the software should use the BUILD.gn mode for independent build and support automatic collection of open-source obligation declaration information.
+
+      ```
+       device/soc/$(SOC_COMPANY)/third_party
+       device/board/$(BOARD_COMPANY)/third_party
+       vendor/$(PRODUCT_COMPANY)/third_party
+      ```
+
+14. Comply with the following requirements for the precompiled binary or toolchain used in the OpenHarmony platform version or version building:
+    - The source code corresponding to the precompiled binary or toolchain must be hosted in the OpenHarmony community, and the corresponding build guide and open-source obligation fulfillment guide must be provided.
+    - Open-source third-party software introduced in the precompiled binary or toolchain must comply with principles 1 to 13.
+    - The file [Prebuilts for Clang/LLVM-based Tools Used in OpenHarmony](./prebuilts-readme-template.md) provides the methods for obtaining the source code, building the source code, and updating the prebuilts. It is archived to the root directory of the corresponding module with the OpenHarmony version or toolchain.
+    - A complete open-source obligation fulfillment statement must be provided in the root directory corresponding to the precompiled binary or toolchain.
+    - If the precompiled file comes from a binary file (such as npm) of the upstream community hosting platform, proceed as follows: In the directory where the binary file is archived, place a **README** file to provide the background description and official hosting address, and a **NOTICE** file to provide the open-source obligation fulfillment statement, including the name, version number, and open-source license agreement of each involved open source software.
 
 ### Software Introduction Process
 
@@ -61,69 +77,69 @@ Follow the process described in the [SIG Management Regulations](https://gitee.c
 
 1. Self-check list
 
-| Check Item| Description| Self-Check Result Example| 
+| Check Item| Description| Self-Check Result Example|
 | :----- | :----- | :----- |
 | Software name| Provide the official name of the software and the repository name to which the software is introduced. The repository name is in the format of **third_party_*****softwareName***.| third_party_**softwarename** |
-| Official website| Provide the official website link of the software.| https://softwaresite |
+| Official website| Provide the official website link of the software.| <https://softwaresite> |
 | Software version| Provide the version number of the software to be introduced. The version number must be an official version number released by the community. Do not modify the version number or introduce a version that is not officially released.| 1.0.0 |
 | Software version release date| Provide the official release date of the software version.| 2021.01.01 |
-| Software version address| Provide the official download URL of the version. Note that the URL must be able to locate the release package of the specific version.| https://gitee.com/softwarecodesite/v1.0.0.zip |
+| Software version address| Provide the official download URL of the version. Note that the URL must be able to locate the release package of the specific version.| <https://gitee.com/softwarecodesite/v1.0.0.zip> |
 | Software license| Provide the official license name of the version and the relative path of the license file. If there are multiple licenses, list them all and describe their relationship, for example, And, Or, or different licenses for different directories.| Apache-2.0 |
 | Software lifecycle| Describe whether the software has an LTS version, how frequent a version is released, code submitted to the community in the last year, issue resolution status, and whether end of maintenance or evolution is notified.| No LTS version; one version released every six months; 10 code submissions in the last six months|
 | Security vulnerabilities| List disclosed security vulnerabilities in the software, including the vulnerability number, severity, link, and whether patches or solutions are available.| No disclosed vulnerabilities.|
 | Service scenario| Describe the repositories where the software is used and the service scenarios where the software is used.| Used by the static link of the *XX* repository to improve the *YYY* capability.|
 | Normalization| Describe whether the likes of the software exist in the OpenHarmony community, what similar software is in the industry, and why the software or version is introduced.| This software has not been introduced to the OpenHarmony community. Similar software in the industry includes B and C. Only this software is license-friendly and has a good ecosystem. Companies such as *X* and *Y* are also using this software.|
 | License compatibility| 1. Describe the processes that use the software, the license of each process, and whether these licenses are compatible with the license of the software to be introduced.<br>2. Use the OAT tool to scan the source code of the software. Attach the scanning report (with all found errors rectified) and the **LicenseFile.txt** file in the request.| 1. This software is used in the user-mode *X* process in static link mode. The process is licensed under Apache-2.0, which is consistent with the software license. There is no compatibility issue.<br>2. **Result.txt** generated by the OAT tool and **LicenseFile.txt**<br> |
-| Owner| Provide the name of the SIG responsible for the software management and the Gitee username and email address of the maintenance owner.| SIG XXX, James, James@example.com|
+| Owner| Provide the name of the SIG responsible for the software management and the Gitee username and email address of the maintenance owner.| SIG XXX, username, username@example.com|
 
 Note:
 
 - For details about how to use the OAT tool, see [OSS Audit Tool](https://gitee.com/openharmony-sig/tools_oat). If you have any suggestions on the tool, submit an issue in the community. You can also fork the repository and improve the tool through pull requests.
 - In principle, the OAT report should contain no errors. The format is as follows:
 
-```
-Invalid File Type Total Count: 0
-License Not Compatible Total Count: 0
-License Header Invalid Total Count: 0
-Copyright Header Invalid Total Count: 0
-No License File Total Count: 0
-No Readme.OpenSource Total Count: 0
-No Readme Total Count: 0
-```
+  ```
+  Invalid File Type Total Count: 0
+  License Not Compatible Total Count: 0
+  License Header Invalid Total Count: 0
+  Copyright Header Invalid Total Count: 0
+  No License File Total Count: 0
+  No Readme.OpenSource Total Count: 0
+  No Readme Total Count: 0
+  ```
 
 - The **LicenseFile.txt** file is located in the **log** directory of the OAT tool running directory. This file records all suspected license files in the scan directory. The format is as follows:
 
-```
-third_party_abcde/ LICENSEFILE LICENSE Apache-2.0
-third_party_abcde/doc/ LICENSEFILE LICENSE Apache-2.0
-```
+  ```
+  third_party_abcde/ LICENSEFILE LICENSE Apache-2.0
+  third_party_abcde/doc/ LICENSEFILE LICENSE Apache-2.0
+  ```
 
 2. **OAT.xml** file
 
-Confirm the issues found by the OAT tool and configure the **OAT.xml** file. For details, see [OSS Audio Tool](https://gitee.com/openharmony-sig/tools_oat/blob/master/README.md). Attach the file in the request. If no issue needs to be confirmed, you do not have to configure the file.
+   Confirm the issues found by the OAT tool and configure the **OAT.xml** file. For details, see [OSS Audio Tool](https://gitee.com/openharmony-sig/tools_oat/blob/master/README.md). Attach the file in the request. If no issue needs to be confirmed, you do not have to configure the file.
 
 3. **README.OpenSource** file of the repository. The format is as follows:
 
-```
-[
-  {
-    "Name": "softwarename",
-    "License": "Apache-2.0",
-    "License File": "LICENSE",
-    "Version Number": "1.0.0",
-    "Owner": "James@example.com",
-    "Upstream URL": "https://gitee.com/softwarecodesite/v1.0.0.zip",
-    "Description": "...."
-  },
-  {
-  ...
-  }// If there are multiple licenses, list them one by one.
-]
-```
-
-#### PMC Review
-
-Refer to the [SIG Management Regulations](https://gitee.com/openharmony/community/tree/master/sig). The PMC will arrange the SIG request review and repository construction based on the received PR.
+   ```
+   [
+     {
+       "Name": "softwarename",
+       "License": "Apache-2.0",
+       "License File": "LICENSE",
+       "Version Number": "1.0.0",
+       "Owner": "James@example.com",
+       "Upstream URL": "https://gitee.com/softwarecodesite/v1.0.0.zip",
+       "Description": "...."
+     },
+     {
+     ...
+     }// If there are multiple licenses, list them one by one.
+   ]
+   ```
+
+#### Reviewing New Third-Party Open-Source Software
+
+The [Architecture SIG](https://gitee.com/openharmony/community/blob/master/sig/sig_architecture/sig_architecture.md) will arrange the construction and review of the repository.
 
 ### License Requirements for Third-Party Open-Source Software
 
@@ -131,66 +147,66 @@ Refer to the [SIG Management Regulations](https://gitee.com/openharmony/communit
 2. The software license must be compatible with the license for the code repository.
 3. The following licenses for third-party open-source software are recommended in the OpenHarmony project:
 
-* Apache License 2.0
-* Mulan Permissive Software License, Version 2
-* BSD 2-clause
-* BSD 3-clause
-* DOM4J License
-* PostgreSQL License
-* Eclipse Distribution License 1.0
-* MIT
-* ISC
-* ICU
-* University of Illinois/NCSA
-* W3C Software License
-* zlib/libpng
-* Academic Free License 3.0
-* Python Software Foundation License
-* Python Imaging Library Software License
-* Boost Software License Version 1.0
-* WTF Public License
-* UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE
-* Zope Public License 2.0
+- Apache License 2.0
+- Mulan Permissive Software License, Version 2
+- BSD 2-clause
+- BSD 3-clause
+- DOM4J License
+- PostgreSQL License
+- Eclipse Distribution License 1.0
+- MIT
+- ISC
+- ICU
+- University of Illinois/NCSA
+- W3C Software License
+- zlib/libpng
+- Academic Free License 3.0
+- Python Software Foundation License
+- Python Imaging Library Software License
+- Boost Software License Version 1.0
+- WTF Public License
+- UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE
+- Zope Public License 2.0
 
 4. The following licenses for third-party open-source software are not recommended in the OpenHarmony project:
 
-* GNU GPL 1, 2, 3
-* GNU Affero GPL 3
-* GNU LGPL 2, 2.1, 3
-* QPL
-* Sleepycat License
-* Server Side Public License (SSPL) version 1
-* Code Project Open License (CPOL)
-* BSD-4-Clause/BSD-4-Clause (University of California-Specific)
-* Facebook BSD+Patents license
-* NPL 1.0/NPL 1.1
-* The Solipsistic Eclipse Public License
-* The "Don't Be A Dick" Public License
-* JSON License
-* Binary Code License (BCL)
-* Intel Simplified Software License
-* JSR-275 License
-* Microsoft Limited Public License
-* Amazon Software License (ASL)
-* Java SDK for Satori RTM license
-* Redis Source Available License (RSAL)
-* Booz Allen Public License
-* Creative Commons Non-Commercial
-* Sun Community Source License 3.0
-* Common Development and Distribution Licenses: CDDL 1.0 and CDDL 1.1
-* Common Public License: CPL 1.0
-* Eclipse Public License: EPL 1.0
-* IBM Public License: IPL 1.0
-* Mozilla Public Licenses: MPL 1.0, MPL 1.1, and MPL 2.0
-* Sun Public License: SPL 1.0
-* Open Software License 3.0
-* Erlang Public License
-* UnRAR License
-* SIL Open Font License
-* Ubuntu Font License Version 1.0
-* IPA Font License Agreement v1.0
-* Ruby License
-* Eclipse Public License 2.0: EPL 2.0
+- GNU GPL 1, 2, 3
+- GNU Affero GPL 3
+- GNU LGPL 2, 2.1, 3
+- QPL
+- Sleepycat License
+- Server Side Public License (SSPL) version 1
+- Code Project Open License (CPOL)
+- BSD-4-Clause/BSD-4-Clause (University of California-Specific)
+- Facebook BSD+Patents license
+- NPL 1.0/NPL 1.1
+- The Solipsistic Eclipse Public License
+- The "Don't Be A Dick" Public License
+- JSON License
+- Binary Code License (BCL)
+- Intel Simplified Software License
+- JSR-275 License
+- Microsoft Limited Public License
+- Amazon Software License (ASL)
+- Java SDK for Satori RTM license
+- Redis Source Available License (RSAL)
+- Booz Allen Public License
+- Creative Commons Non-Commercial
+- Sun Community Source License 3.0
+- Common Development and Distribution Licenses: CDDL 1.0 and CDDL 1.1
+- Common Public License: CPL 1.0
+- Eclipse Public License: EPL 1.0
+- IBM Public License: IPL 1.0
+- Mozilla Public Licenses: MPL 1.0, MPL 1.1, and MPL 2.0
+- Sun Public License: SPL 1.0
+- Open Software License 3.0
+- Erlang Public License
+- UnRAR License
+- SIL Open Font License
+- Ubuntu Font License Version 1.0
+- IPA Font License Agreement v1.0
+- Ruby License
+- Eclipse Public License 2.0: EPL 2.0
 
 If you want to introduce the software that complies with the unrecommended licenses listed in **4** or other licenses that are not mentioned, send an email to oh-legal@openatom.io.
 
diff --git a/en/contribute/licenses-and-special-license-review.md b/en/contribute/licenses-and-special-license-review.md
index 28e285dbc45e4156393a692410c60f7a79a8e65e..01964a17cd7d0d08a2ddbebeb7b9af7514464d3a 100644
--- a/en/contribute/licenses-and-special-license-review.md
+++ b/en/contribute/licenses-and-special-license-review.md
@@ -94,7 +94,7 @@ Licenses compatible with Apache License 2.0 can be accepted. The OpenHarmony pro
 
 - The Romantic WTF public license
 
-- UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND      SOFTWARE
+- UNICODE, INC. LICENSE AGREEMENT - DATA FILES AND SOFTWARE
 
 - Zope Public License 2.0
 
@@ -125,7 +125,7 @@ In principle, the OpenHarmony project will not accept third-party dependencies t
 - Sun Community Source License 3.0
 - GNU GPL 3
 - GNU Affero GPL 3
-- BSD-4-Clause   
+- BSD-4-Clause/BSD-4-Clause (University of California-Specific)    
 - Facebook BSD+Patents license
 - NPL 1.0/NPL 1.1
 - The Solipsistic Eclipse Public License 
@@ -166,4 +166,4 @@ For software modules that use special licenses in the OpenHarmony project, passi
 
 - **Rule 4**: The introduction of third-party dependencies should not affect or change the existing licenses of the related code.
 
-- **Rule 5**: The non-source code (binary code or object code), if involved, should use an open source license and meet the preceding rules. The use of a self-prepared license should be approved by the PMC and further reviewed and approved by the OpenHarmony legal compliance team. (In principle, only special licenses for algorithms and special implementation related to necessary hardware, such as GPU, Wi-Fi firmware, and hardware codec algorithms, can be accepted.)
\ No newline at end of file
+- **Rule 5**: The non-source code (binary code or object code), if involved, should use an open source license and meet the preceding rules. The use of a self-prepared license should be approved by the PMC and further reviewed and approved by the OpenHarmony legal compliance team. (In principle, only special licenses for algorithms and special implementation related to necessary hardware, such as GPU, Wi-Fi firmware, and hardware codec algorithms, can be accepted.)
diff --git a/en/device-dev/device-test/developer_test.md b/en/device-dev/device-test/developer_test.md
index d9e0550b975785a9946c057980c608054e6fdda3..37871b5dc3c6090dc797c71419f63d40559d39b4 100644
--- a/en/device-dev/device-test/developer_test.md
+++ b/en/device-dev/device-test/developer_test.md
@@ -698,7 +698,7 @@ ohos_js_unittest("GetAppInfoJsTest") {
         "description": "$string:mainability_description",
         "label": "MyApplication",
         "type": "page",
-        "launchType": "standard"
+        "launchType": "multiton"
       }
     ],
     "js": [
diff --git a/en/readme/test.md b/en/readme/test.md
index b5171f0388d537e92ecb9418261b30fb2a44d415..f28c5468d5ec67da7f8e16e2e628e3b41907ba06 100644
--- a/en/readme/test.md
+++ b/en/readme/test.md
@@ -3,8 +3,8 @@ OpenHarmony provides a comprehensive auto-test framework for designing test case
 
 This document describes how to use the OpenHarmony test framework.
 ## Setting Up the Environment
-The test framework depends on the Python running environment. Before using the test framework, set up the environment as follows:
- - [Setting Up the Environment](../device-dev/subsystems/subsys-testguide-test.md#setting-up-the-environment)
+The test framework depends on Python. Before using the test framework, set up the environment as follows:
+ - [Setting Up the Environment](../device-dev/subsystems/subsys-testguide-envbuild.md)
  - [Obtaining Source Code](../device-dev/get-code/sourcecode-acquire.md)
 
 
@@ -12,53 +12,55 @@ The test framework depends on the Python running environment. Before using the t
 The directory structure of the test framework is as follows:
 ```
 test # Test subsystem
-├── developertest             # Developer test module
+├── developertest             # Developer test component
 │   ├── aw                    # Static library of the test framework
-│   ├── config  # Test framework configuration
+│   ├── config                # Test framework configuration
 │   │   │ ...
 │   │   └── user_config.xml   # User configuration
-│   ├── examples              # Examples of test cases
+│   ├── examples              # Test case examples
 │   ├── src                   # Source code of the test framework
 │   ├── third_party           # Adaptation code for third-party components on which the test framework depends
 │   ├── reports               # Test reports
 │   ├── BUILD.gn              # Build entry of the test framework
 │   ├── start.bat             # Test entry for Windows
 │   └── start.sh              # Test entry for Linux
-└── xdevice                   # Modules on which the test framework depends
+└── xdevice                   # Component on which the test framework depends
 ```
 ## Writing Test Cases
 ###  Designing the Test Case Directory
 Design the test case directory as follows:
 ```
-subsystem                                # Subsystem
-├── partA                                # Part A
-│   ├── moduleA                          # Module A
+subsystem                                  # Subsystem
+├── partA                                  # Part A
+│   ├── moduleA                            # Module A
 │   │   ├── include       
-│   │   ├── src                          # Service code
-│   │   └── test                         # Test directory
-│   │       ├── unittest                 # Unit test
-│   │       │   ├── common               # Common test cases
-│   │       │   │   ├── BUILD.gn         # Build file of test cases
-│   │       │   │   └── testA_test.cpp   # Source code of unit test cases
-│   │       │   ├── phone                # Test cases for mobile phones
-│   │       │   ├── ivi                  # Test cases for head units
-│   │       │   └── liteos-a             # Test cases for the IP cameras that use the LiteOS kernel
-│   │       ├── moduletest               # Module test
+│   │   ├── src                            # Service code
+│   │   └── test                           # Test directory
+│   │       ├── unittest                   # Unit tests
+│   │       │   ├── common                 # Common test cases
+│   │       │   │   ├── BUILD.gn           # Build file of test cases
+│   │       │   │   └── testA_test.cpp     # Source code of unit test cases
+│   │       │   ├── phone                  # Test cases for smart phones
+│   │       │   ├── ivi                    # Test cases for head units
+│   │       │   └── liteos-a               # Test cases for IP cameras that use the LiteOS kernel
+│   │       ├── moduletest                 # Module tests
 │   │       ...
 │   │            
-│   ├── moduleB                   # Module B  
+│   ├── moduleB                      # Module B   
 │   ├── test               
-│   │   └── resource              # Dependency resources   
-│   │       ├── moduleA           # Module A
-│   │       │   ├── ohos_test.xml # Resource configuration file
-│   │       ... └── 1.txt         # Resource file  
+│   │   └── resource                 # Dependencies    
+│   │       ├── moduleA              # Module A
+│   │       │   ├── ohos_test.xml    # Resource configuration file
+│   │       ... └── 1.txt            # Resource file  
 │   │            
-│   ├── ohos_build                # Build entry configuration 
+│   ├── ohos_build                   # Build entry configuration  
 │   ...
 │
 ...
 ```
-> **NOTE**<br>Test cases are classified into common test cases and device-specific test cases. You are advised to place common test cases in the **common** directory and device-specific test cases in the directories of the related devices.
+> **NOTE** 
+>
+> Test cases are classified into common test cases and device-specific test cases. You are advised to place common test cases in the **common** directory and device-specific test cases in the directories of the related devices.
 
 ###  Writing Test Cases
 This test framework supports test cases written in multiple programming languages and provides different templates for different languages.
@@ -111,7 +113,7 @@ Example:
     
     /**
      * @tc.name: integer_sub_001
-     * @tc.desc: Verify the sub-function.
+     * @tc.desc: Verify the sub function.
      * @tc.type: FUNC
      * @tc.require: Issue Number
      */
@@ -119,7 +121,7 @@ Example:
     {
         // Step 1 Call the function to obtain the result.
         int actual = Sub(4, 0);
-
+    
         // Step 2 Use an assertion to compare the obtained result with the expected result.
         EXPECT_EQ(4, actual);
     }
@@ -130,49 +132,57 @@ Example:
         Enter the header comment in the standard format. For details, see [Code Specifications](https://gitee.com/openharmony/docs/blob/master/en/contribute/code-contribution.md).
 
     2. Add the test framework header file and namespace.
-	    ```
-    	#include <gtest/gtest.h>
-    
-    	using namespace testing::ext;
-    	```
+	
+        ```
+        #include <gtest/gtest.h>
+        	
+        using namespace testing::ext;
+        ```
+	
     3. Add the header file of the test class.
-	    ```
-    	#include "calculator.h"
-    	```
+    
+       ```
+	   #include "calculator.h"
+       ```
+    
     4. Define the test suite (test class).
-	    ```
+        ```
     	class CalculatorSubTest : public testing::Test {
     	public:
-    	    static void SetUpTestCase(void);
-    	    static void TearDownTestCase(void);
-    	    void SetUp();
-    	    void TearDown();
+    	   static void SetUpTestCase(void);
+    	   static void TearDownTestCase(void);
+    	   void SetUp();
+    	   void TearDown();
     	};
-    
+                
     	void CalculatorSubTest::SetUpTestCase(void)
     	{
-    	    // Set a setup function, which will be called before all test cases.
+    	    // input testsuit setup step，setup invoked before all testcases
     	}
-    
+                
     	void CalculatorSubTest::TearDownTestCase(void)
     	{
-    	    // Set a teardown function, which will be called after all test cases.
+    	    // input testsuit teardown step，teardown invoked after all testcases
     	}
-    
+                
     	void CalculatorSubTest::SetUp(void)
     	{
-    	    // Set a setup function, which will be called before each test case.
+    	    // input testcase setup step，setup invoked before each testcases
     	}
+                
+        void CalculatorSubTest::TearDown(void)
+	    {
+	        // input testcase teardown step，teardown invoked after each testcases
+        }
+	    
+        ```
+    
+       > **NOTE**
+       >
+       > When defining a test suite, ensure that the test suite name is the same as the target to build and uses the upper camel case style.
     
-    	void CalculatorSubTest::TearDown(void)
-    	{
-    	    // Set a teardown function, which will be called after each test case.
-    	}
-    	```
-	    > **NOTE**<br>When defining a test suite, ensure that the test suite name is the same as the target to build and uses the upper camel case style.
-
     5. Add implementation of the test cases, including test case comments and logic.
-	    ```
+        ```
     	/**
     	 * @tc.name: integer_sub_001
     	 * @tc.desc: Verify the sub function.
@@ -180,48 +190,52 @@ Example:
     	 * @tc.require: Issue Number
     	 */
     	HWTEST_F(CalculatorSubTest, integer_sub_001, TestSize.Level1)
-    	{
-    	    // Step 1 Call the function to obtain the test result.
-    	    int actual = Sub(4, 0);
-
+		{
+		    // Step 1 Call the function to obtain the test result.
+		    int actual = Sub(4, 0);
+        
     	    // Step 2 Use an assertion to compare the obtained result with the expected result.
-    	    EXPECT_EQ(4, actual);
+        EXPECT_EQ(4, actual);
     	}
-    	```
+		```
 	    The following test case templates are provided for your reference.
 	
-	    |      Template|    Description|
-    	| ------------| ------------|
-    	| HWTEST(A,B,C)| Use this template if the test case execution does not depend on setup or teardown.|
-    	| HWTEST_F(A,B,C)| Use this template if the test case execution (excluding parameters) depends on setup and teardown.|
-    	| HWTEST_P(A,B,C)| Use this template if the test case execution (including parameters) depends on setup and teardown.|
-
+	    | Template        | Description                                                  |
+		| --------------- | ------------------------------------------------------------ |
+		| HWTEST(A,B,C)   | Use this template if the test case execution does not depend on setup or teardown. |
+		| HWTEST_F(A,B,C) | Use this template if the test case execution (excluding parameters) depends on setup and teardown. |
+	   | HWTEST_P(A,B,C) | Use this template if the test case execution (including parameters) depends on setup and teardown. |
+	   
+	   
 	    In the template names: 
-	- *A* indicates the test suite name.
-	- *B* indicates the test case name, which is in the *Function*\_*No.* format. The *No.* is a three-digit number starting from **001**.
-	- *C* indicates the test case level. There are five test case levels: guard-control level 0 and non-guard-control level 1 to level 4. Of levels 1 to 4, a smaller value indicates a more important function verified by the test case.
-
-	    **NOTE**<br>
-	- The expected result of each test case must have an assertion.
-	- The test case level must be specified.
-	- It is recommended that the test be implemented step by step according to the template.
-	- The comment must contain the test case name, description, type, and requirement number, which are in the @tc.*xxx*: *value* format. The test case description must be in the @tc.xxx format. The test case type @tc.type can be any of the following:
-
-	    | Test Case Type|Code|
-    	| ------------|------------|
-    	|Function test     |FUNC|
-        |Performance test     |PERF|
-        |Reliability test   |RELI|
-        |Security test     |SECU|
-        |Fuzz test      |FUZZ|
-    
+       
+	    - *A* indicates the test suite name.
+        - *B* indicates the test case name, which is in the *Function*\_*No.* format. The *No.* is a three-digit number starting from **001**.
+        - *C* indicates the test case level. There are five test case levels: guard-control level 0 and non-guard-control level 1 to level 4. Of levels 1 to 4, a smaller value indicates a more important function verified by the test case.
+       
+    > **NOTE**
+    >
+    > - The expected result of each test case must have an assertion.
+    > - The test case level must be specified.
+    > - It is recommended that the test be implemented step by step according to the template.
+    > - The comment must contain the test case name, description, type, and requirement number, which are in the @tc.*xxx*: *value* format.The test case description must be in the @tc.xxx format. The test case type @tc.type can be any of the following:
+    
+    | Test Case Type   | Code |
+    | ---------------- | ---- |
+    | Function test    | FUNC |
+    | Performance test | PERF |
+    | Reliability test | RELI |
+    | Security test    | SECU |
+    | Fuzz test        | FUZZ |
 
 #### JavaScript Test Case Example
 
 - Naming rules for source files
 
     The source file name of a test case must be in the [Function]\[Sub-function]Test format, and each part must use the upper camel case style. More specific sub-functions can be added as required.
-Example:
+
+    Example:
+
     ```
     AppInfoTest.js
     ```
@@ -262,7 +276,7 @@ Example:
         it("appInfoTest001", 0, function () {
             // Step 1 Call the function to obtain the test result.
             var info = app.getInfo()
-
+    
             // Step 2 Use an assertion to compare the obtained result with the expected result.
             expect(info != null).assertEqual(true)
         })
@@ -276,7 +290,7 @@ Example:
     2. Import the APIs and JSUnit test library to test.
 	    ```
     	import app from '@system.app'
-    
+    	
     	import {describe, beforeAll, beforeEach, afterEach, afterAll, it, expect} from 'deccjsunit/index'
     	```
     3. Define the test suite (test class).
@@ -313,7 +327,7 @@ Example:
     	 it("appInfoTest001", 0, function () {
     	    // Step 1 Call the function to obtain the test result.
             var info = app.getInfo()
-
+    	
             // Step 2 Use an assertion to compare the obtained result with the expected result.
             expect(info != null).assertEqual(true)
     	 })
@@ -326,7 +340,7 @@ When a test case is executed, the test framework searches for the build file of
 The following provides templates for different languages for your reference.
 
 - **Test case build file example (C++)**
-    ```
+    ```c++
     
     import("//build/test.gni")
     
@@ -365,70 +379,90 @@ The following provides templates for different languages for your reference.
         Enter the header comment in the standard format. For details, see [Code Specifications](https://gitee.com/openharmony/docs/blob/master/en/contribute/code-contribution.md).
 
     2. Import the build template.
-	    ```
+	   
+    	```
     	import("//build/test.gni")
     	```
+    	
     3. Specify the file output path.
-    	```
-    	module_output_path = "subsystem_examples/calculator"
-    	```
-    	> **NOTE**<br>The output path is ***Part name*/*Module name***.
+       
+        ```
+       module_output_path = "subsystem_examples/calculator"
+       ```
+    
+       > **NOTE**
+       >
+       > The output path is ***Part name*/*Module name***.
+       
+       
     
     4. Configure the directories for dependencies.
     
-    	```
-    	config("module_private_config") {
-    	  visibility = [ ":*" ]
-    	   
-    	  include_dirs = [ "../../../include" ]
-    	}
-    	```
-    	> **NOTE**<br>Generally, the dependency directories are configured here and directly referenced in the build script of the test case.
+        ```
+        config("module_private_config") {
+            visibility = [ ":*" ]
+             
+            include_dirs = [ "../../../include" ]
+          }
+        ```
     
+        > **NOTE**
+        >
+        > Generally, the dependency directories are configured here and directly referenced in the build script of the test case.
+
     5. Set the output build file for the test cases.
     
-    	```
-    	ohos_unittest("CalculatorSubTest") {
-    	}
-    	```
+       ```
+       ohos_unittest("CalculatorSubTest") {
+         }
+       ```
+
     6. Write the build script (add the source file, configuration, and dependencies) for the test cases.
-    	```
-    	ohos_unittest("CalculatorSubTest") {
-    	  module_out_path = module_output_path
-    	  sources = [
-    	    "../../../include/calculator.h",
-    	    "../../../src/calculator.cpp",
-    	    "../../../test/calculator_sub_test.cpp"
-    	  ]
-    	  sources += [ "calculator_sub_test.cpp" ]
-    	  configs = [ ":module_private_config" ]
-    	  deps = [ "//third_party/googletest:gtest_main" ]
-    	}
-    	```
 
-	    > **NOTE**<br>Set the test type based on actual requirements. The following test types are available:
-    	 >
-    	 > - **ohos_unittest**: unit test
-    	 > - **ohos_moduletest**: module test
-    	 > - **ohos_systemtest**: system test
-    	 > - **ohos_performancetest**: performance test
-    	 > - **ohos_securitytest**: security test
-    	 > - **ohos_reliabilitytest**: reliability test
-         > - **ohos_distributedtest**: distributed test
-    	
+        ```
+        ohos_unittest("CalculatorSubTest") {
+             module_out_path = module_output_path
+             sources = [
+               "../../../include/calculator.h",
+               "../../../src/calculator.cpp",
+               "../../../test/calculator_sub_test.cpp"
+             ]
+             sources += [ "calculator_sub_test.cpp" ]
+             configs = [ ":module_private_config" ]
+             deps = [ "//third_party/googletest:gtest_main" ]
+           }
+        ```
+
+        > **NOTE**
+        >
+        > Set the test type based on actual requirements. The following test types are available:
+        >
+        > - **ohos_unittest**: unit test
+        > - **ohos_moduletest**: module test
+        > - **ohos_systemtest**: system test
+        > - **ohos_performancetest**: performance test
+        > - **ohos_securitytest**: security test
+        > - **ohos_reliabilitytest**: reliability test
+        > - **ohos_distributedtest**: distributed test
+    
     7. Group the test case files by test type.
     
-    	```
-    	group("unittest") {
-    	  testonly = true
-    	  deps = [":CalculatorSubTest"]
-    	}
-    	```
-    	> **NOTE**<br>Grouping test cases by test type allows you to execute a specific type of test cases when required.
+       ```
+       group("unittest") {
+         testonly = true
+         deps = [":CalculatorSubTest"]
+       }
+       ```
+    
+       > **NOTE**
+       >
+       > Grouping test cases by test type allows you to execute a specific type of test cases when required.
+    
+    ​    
     
 - **Test case build file example (JavaScript)**
 
-    ```
+    ```javascript
     
     import("//build/test.gni")
     
@@ -448,32 +482,39 @@ The following provides templates for different languages for your reference.
     ```
 
     The procedure is as follows:
-
+    
     1. Add comment information for the file header.
-
+    
         Enter the header comment in the standard format. For details, see [Code Specifications](https://gitee.com/openharmony/docs/blob/master/en/contribute/code-contribution.md).
-
+    
     2. Import the build template.
     
     	```
     	import("//build/test.gni")
     	```
+    	
     3. Specify the file output path.
     
     	```
     	module_output_path = "subsystem_examples/app_info"
     	```
-    	> **NOTE**<br>The output path is ***Part name*/*Module name***.
+    	> **NOTE**
+    	>
+    	>  The output path is ***Part name*/*Module name***.
     	
     4. Set the output build file for the test cases.
     
-    	```
-    	ohos_js_unittest("GetAppInfoJsTest") {
-    	}
-    	```
-    	> **NOTE**<br>
-    	>- Use the **ohos\_js\_unittest** template to define the JavaScript test suite. Pay attention to the difference between JavaScript and C++.
-    	>- The file generated for the JavaScript test suite must be in .hap format and named after the test suite name defined here. The test suite name must end with **JsTest**.
+        ```
+        ohos_js_unittest("GetAppInfoJsTest") {
+          }
+        ```
+    
+        > **NOTE**
+        >
+        > - Use the **ohos\_js\_unittest** template to define the JavaScript test suite. Pay attention to the difference between JavaScript and C++.
+        > - The file generated for the JavaScript test suite must be in .hap format and named after the test suite name defined here. The test suite name must end with **JsTest**.
+    
+      
     
     5. Configure the **config.json** file and signature file, which are mandatory.
     
@@ -485,7 +526,7 @@ The following provides templates for different languages for your reference.
     	  certificate_profile = "//test/developertest/signature/openharmony_sx.p7b"
     	}
     	```
-    	 **config.json** is the configuration file required for HAP build. You need to set **target** based on the tested SDK version. Default values can be retained for other items. The following is an example:
+    	**config.json** is the configuration file required for HAP build. You need to set **target** based on the tested SDK version. Default values can be retained for other items. The following is an example:
     
     	```
     	{
@@ -530,7 +571,7 @@ The following provides templates for different languages for your reference.
     	        "description": "$string:mainability_description",
     	        "label": "MyApplication",
     	        "type": "page",
-    	        "launchType": "standard"
+    	        "launchType": "multiton"
     	      }
     	    ],
     	    "js": [
@@ -555,8 +596,10 @@ The following provides templates for different languages for your reference.
     	  deps = [ ":GetAppInfoJsTest" ]
     	}
     	```
-    	> **NOTE**<br>Grouping test cases by test type allows you to execute a specific type of test cases when required.
-    
+    	> **NOTE**
+    	>
+    	> Grouping test cases by test type allows you to execute a specific type of test cases when required.
+
 #### Configuring ohos.build
 
 Configure the part build file to associate with specific test cases.
@@ -576,7 +619,9 @@ Configure the part build file to associate with specific test cases.
     ]
  }
 ```
-> **NOTE**<br>**test_list** contains the test cases of the corresponding module.
+> **NOTE**
+>
+>  **test_list** contains the test cases of the corresponding module.
 
 ### Configuring Test Case Resources
 Test case resources include external file resources, such as image files, video files, and third-party libraries, required for test case execution.
@@ -602,8 +647,9 @@ Perform the following steps:
 	  resource_config_file = "//system/subsystem/partA/test/resource/calculator/ohos_test.xml"
 	}
 	```
-	>**NOTE**<br/>
-	>- **target_name** indicates the test suite name defined in the **BUILD.gn** file in the **test** directory.
+	>**NOTE**
+	>
+	>- **target_name** indicates the test suite name defined in the **BUILD.gn** file in the **test** directory. 
 	>- **preparer** indicates the action to perform before the test suite is executed.
 	>- **src="res"** indicates that the test resources are in the **resource** directory under the **test** directory. 
 	>- **src="out"** indicates that the test resources are in the **out/release/$(*part*)** directory.
@@ -657,7 +703,9 @@ Before executing test cases, you need to modify the configuration based on the d
   </NFS>
 </user_config>
 ```
->**NOTE**<br>If HDC is connected to the device before the test cases are executed, you only need to configure the device IP address and port number, and retain the default settings for other parameters.
+>**NOTE**
+>
+>If HDC is connected to the device before the test cases are executed, you only need to configure the device IP address and port number, and retain the default settings for other parameters.
 
 ### Executing Test Cases on Windows
 #### Building Test Cases
@@ -668,17 +716,21 @@ Test cases cannot be built on Windows. You need to run the following command to
 ```
 When the build is complete, the test cases are automatically saved in **out/hispark_taurus/packages/phone/images/tests**.
 
->**NOTE**<br>In the command, **hispark_taurus_standard** indicates the product supported by the current version, and **make_test** indicates all test cases. You can set the build options based on requirements:<br>
-> -  --**product-name**: specifies the name of the product to build. It is mandatory.
-> - --**build-target**: specifies the target to build. It is optional. 
+>**NOTE**
+>
+>In the command, **hispark_taurus_standard** indicates the product supported by the current version, and **make_test** indicates all test cases. You can set the build options based on requirements:
+>
+>-  --**product-name**: specifies the name of the product to build. It is mandatory.
+>- --**build-target**: specifies the target to build. It is optional. 
 
 #### Setting Up the Execution Environment
 1. On Windows, create the **Test** directory in the test framework and then create the **testcase** directory in the **Test** directory.
 
 2. Copy **developertest** and **xdevice** from the Linux environment to the **Test** directory on Windows, and copy the test cases to the **testcase** directory.
 	
->**NOTE**<br>Port the test framework and test cases from the Linux environment to the Windows environment for subsequent execution.
-
+	> **NOTE**
+	>
+	> Port the test framework and test cases from the Linux environment to the Windows environment for subsequent execution.
 3. Modify the **user_config.xml** file.
 	```
 	<build>
@@ -690,7 +742,9 @@ When the build is complete, the test cases are automatically saved in **out/hisp
 	  <dir>D:\Test\testcase\tests</dir>
 	</test_cases>
 	```
-	>**NOTE**<br>`<testcase>` indicates whether to build test cases. `<dir>` indicates the path for searching for test cases.
+	>**NOTE**
+	>
+	>`<testcase>` indicates whether to build test cases. `<dir>` indicates the path for searching for test cases.
 
 #### Executing Test Cases
 1. Start the test framework.
@@ -714,7 +768,7 @@ When the build is complete, the test cases are automatically saved in **out/hisp
 	-tm [TESTMODULE]: specifies the module to test. This parameter must be used together with -tp.
 	-ts [TESTSUITE]: specifies a test suite. This parameter can be used independently.
 	-tc [TESTCASE]: specifies a test case. This parameter must be used together with -ts.
-	You can run -h to display help information.
+	You can run h to display help information.
 	```
 ### Executing Test Cases on Linux
 #### Mapping the Remote Port
@@ -724,13 +778,16 @@ To enable test cases to be executed on a remote Linux server or a Linux VM, map
 	hdc_std kill
 	hdc_std -m -s 0.0.0.0:8710
 	```
-	>**NOTE**<br>The IP address and port number are default values.
-
+	>**NOTE**
+	>
+	>The IP address and port number are default values.
 2. On the HDC client, run the following command:
 	```
 	hdc_std -s xx.xx.xx.xx:8710 list targets
 	```
-	>**NOTE**<br>Enter the IP address of the device to test.
+	>**NOTE**
+	>
+	>Enter the IP address of the device to test.
 
 #### Executing Test Cases
 1. Start the test framework.
@@ -745,7 +802,7 @@ To enable test cases to be executed on a remote Linux server or a Linux VM, map
 
     The test framework locates the test cases based on the command, and automatically builds and executes the test cases.
 	```
-	run -t UT -ts CalculatorSubTest -tc integer_sub_00l
+	run -t UT -ts CalculatorSubTest -tc interger_sub_00l
 	```
 	In the command:
 	```
@@ -765,7 +822,9 @@ You can obtain the test result in the following directory:
 ```
 test/developertest/reports/xxxx_xx_xx_xx_xx_xx
 ```
->**NOTE**<br>The folder for test reports is automatically generated.
+>**NOTE**
+>
+>The folder for test reports is automatically generated.
 
 The folder contains the following files:
 | Type| Description|
diff --git a/en/release-notes/OpenHarmony-v3.2-beta1.md b/en/release-notes/OpenHarmony-v3.2-beta1.md
index 3e97b000bfbea8a53c61e9432394f1c070aea9bc..d091411f069ec488806fc20ae132df1ea43752d2 100644
--- a/en/release-notes/OpenHarmony-v3.2-beta1.md
+++ b/en/release-notes/OpenHarmony-v3.2-beta1.md
@@ -186,26 +186,19 @@ For details about the adaptation status, see [SIG_DevBoard](https://gitee.com/op
 
 | Subsystem| Sample| Introduction| Programming Language|
 | -------- | -------- | -------- | -------- |
-| ArkUI | [MouseEvent](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ETSUI/MouseEvent) | This sample simulates a minesweeper game that calls mouse event-related APIs.| ArkTS |
-| ArkUI | [Vibrator](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/device/Vibrator) | This sample simulates the countdown scenario to show the use of the vibrator APIs.| ArkTS |
-| DFX | [FaultLogger](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/DFX/FaultLogger) | This sample illustrates how to obtain fault information of an application in ArkTS.| ArkTS |
-| ArkUI | [Gallery](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ETSUI/Gallery) | This sample demonstrates the functions of different components such as universal events, universal attributes, and gestures.| ArkTS |
-| Graphics| [JsWebGL](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Graphics/JsWebGL) | This sample shows how to use WebGL APIs to draw pentagrams and rectangles by invoking GPU resources.| JS |
-| ArkUI | [Clock](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Preset/Clock) | This sample exemplifies how to implement a simple clock application using the ArkTS UI capability.| ArkTS |
-| Network management| [Http](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Network/Http) | This sample simulates Postman, which requires the input of an API address and outputs the data obtained, to show the use of the data request APIs.| ArkTS |
-| Network management| [Socket](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Network/Socket) | This sample demonstrates the application of Socket in network communication, including connection authentication and chat communication between two devices.| ArkTS |
-| Distributed data management| [DistributedRdb](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/data/DistributedRdb) | This sample shows how to add, delete, modify, query, and synchronize data in the distributed relational database with ArkTS.| ArkTS |
-| Ability| [BackgroundTaskManager](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ResourcesSchedule/BackgroundTaskManager) | This sample simulates the download function. Being processed by the background task management, a download task can continue after the application exits. It stops until the download is complete.| ArkTS |
-| Ability| [BringApp](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ETSUI/BringApp) | This sample uses the **FeatureAbility** APIs to start a system application based on the application's bundle name and ability name.| ArkTS |
-| Media| [VideoPlayer](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/media/VideoPlayer) | This sample shows how to play a video using the **VideoPlayer** APIs in ArkTS. It also provides an ability that can be invoked by other applications to play the video.| ArkTS |
-| Ability| [DistributeCalc](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Preset/DistributeCalc) | This sample implements a simple calculator application using JS distributed features. The calculator can perform simple numerical calculations and start a remote calculator FA to perform collaborative calculation.| ArkTS |
-| Web | [Browser](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/device/Browser) | This sample uses the stage model and related APIs to show a simple browser.| ArkTS |
-| Ability| [DeviceUsageStatistics](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/device/DeviceUsageStatistics) | This sample shows the device usage statistics.| ArkTS |
-| ArkUI | [AdaptiveCapabilities](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/AdaptiveCapabilities) | This sample shows multi-device adaptation in ArkTS, including resource qualifiers, atomic layouts, and responsive layouts.| ArkTS |
-| ArkUI | [Game2048](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ETSUI/Game2048) | This sample shows how to develop a 2048 game using the **\<Grid>** component.| ArkTS |
-| Window manager| [Window](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Graphics/Window) | This sample shows how to create a window, display an application over another application in the form of a floating window, and display an application on split screens.| ArkTS |
-| Distributed data management| [Preference](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/data/Preferences) | This sample shows the theme switching function of preferences.| ArkTS |
-| Globalization| [International](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/common/International) | This sample shows how to use APIs related to i18n, intl, and resourceManager in ArkTS to set the system language, region, time, and time zone. It also provides locale setting examples.| ArkTS |
+| ArkUI | [Vibrator](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DeviceManagement/Vibrator) | This sample simulates the countdown scenario to show the use of the vibrator APIs.| ArkTS |
+| DFX | [FaultLogger](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DFX/FaultLogger) | This sample illustrates how to obtain fault information of an application in ArkTS.| ArkTS |
+| ArkUI | [Clock](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/Solutions/Tools/ArkTSClock) | This sample exemplifies how to implement a simple clock application using the ArkTS UI capability.| ArkTS |
+| Network management| [Http](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/Connectivity/Http) | This sample simulates Postman, which requires the input of an API address and outputs the data obtained, to show the use of the data request APIs.| ArkTS |
+| Distributed data management| [DistributedRdb](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/DistributedAppDev/DistributedRdb) | This sample shows how to add, delete, modify, query, and synchronize data in the distributed relational database with ArkTS.| ArkTS |
+| Ability| [ArkTSDistributeCalc](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/DistributedAppDev/ArkTSDistributedCalc) | This sample implements a simple calculator application using JS distributed features. The calculator can perform simple numerical calculations and start a remote calculator FA to perform collaborative calculation.| ArkTS |
+| Web | [Browser](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/Web/Browser) | This sample uses the stage model and related APIs to show a simple browser.| ArkTS |
+| Ability| [DeviceUsageStatistics](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DeviceUsageStatistics/DeviceUsageStatistics) | This sample shows the device usage statistics.| ArkTS |
+| ArkUI | [AdaptiveCapabilities](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/AdaptiveCapabilities) | This sample shows multi-device adaptation in ArkTS, including resource qualifiers, atomic layouts, and responsive layouts.| ArkTS |
+| ArkUI | [Game2048](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/Solutions/Game/Game2048) | This sample shows how to develop a 2048 game using the **\<Grid>** component.| ArkTS |
+| Window manager| [WindowManage](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/WindowManagement/WindowManage) | This sample shows how to create a window, display an application over another application in the form of a floating window, and display an application on split screens.| ArkTS |
+| Distributed data management| [Preference](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DataManagement/Preferences) | This sample shows the theme switching function of preferences.| ArkTS |
+| Globalization| [International](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SystemFeature/Internationalnation/International) | This sample shows how to use APIs related to i18n, intl, and resourceManager in ArkTS to set the system language, region, time, and time zone. It also provides locale setting examples.| ArkTS |
 
 For more information, visit [Samples](https://gitee.com/openharmony/applications_app_samples).
 
diff --git a/en/release-notes/OpenHarmony-v3.2-beta3.md b/en/release-notes/OpenHarmony-v3.2-beta3.md
index cf33d4ef26503be58459efdcc573c9671d27cba0..9071a88026f900f16d5749ee202b0832a428bd63 100644
--- a/en/release-notes/OpenHarmony-v3.2-beta3.md
+++ b/en/release-notes/OpenHarmony-v3.2-beta3.md
@@ -190,13 +190,12 @@ For details about the adaptation status, see [SIG_DevBoard](https://gitee.com/op
 
 | Subsystem| Name| Introduction| Programming Language|
 | -------- | -------- | -------- | -------- |
-| ArkUI development framework| [HealthyDiet](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ETSUI/HealthyDiet)| This sample app helps you keep food records and view food information. After you add food records, including the food type, weight, and meal time, the app can calculate nutrition data (calories, proteins, fats, and carbon water) for the meals and display the data in a bar chart.| ArkTS |
-| ArkUI development framework| [MusicAlbum](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/MusicAlbum)| This sample shows the home page of a music album app. The adaptive layout and responsive layout are used to ensure that the app can be properly displayed on devices irrespective of screen sizes.| ArkTS |
-| Ability framework and file management subsystem| [Share](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Share/Share)| Using this sample app, you can share texts, links, and images with third-party applications and display them in these applications.| ArkTS |
-| Ability framework| [GalleryForm](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/GalleryForm)| This sample demonstrates the display of **Gallery** images in a widget and periodic update of the widget.| ArkTS |
-| ArkUI development framework| [AppMarket](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/AppMarket)| This sample shows the home page of an application market, which contains the tab bar, banner, featured apps, and featured games.| ArkTS |
-| ArkUI development framework| [Weather](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/Weather)| This sample demonstrates one-time development for multi-device deployment by showing how to develop a weather app and deploy it across different devices. The demo app includes the following: home page, **Manage City** page, **Add City** page, and **Update Time** page.| ArkTS |
-| Multimedia subsystem| [MediaCollections](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/media/MediaCollections)| This sample shows the capabilities of online streaming, audio and video playback control, and volume adjustment.| ArkTS |
+| ArkUI development framework| [HealthyDiet](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/HealthyDiet)| This sample app helps you keep food records and view food information. After you add food records, including the food type, weight, and meal time, the app can calculate nutrition data (calories, proteins, fats, and carbon water) for the meals and display the data in a bar chart.| ArkTS |
+| ArkUI development framework| [MusicAlbum](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/MusicAlbum)| This sample shows the home page of a music album app. The adaptive layout and responsive layout are used to ensure that the app can be properly displayed on devices irrespective of screen sizes.| ArkTS |
+| Ability framework and file management subsystem| [CustomShare](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/ApplicationModels/CustomShare)| Using this sample app, you can share texts, links, and images with third-party applications and display them in these applications.| ArkTS |
+| ArkUI development framework| [AppMarket](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/AppMarket)| This sample shows the home page of an application market, which contains the tab bar, banner, featured apps, and featured games.| ArkTS |
+| ArkUI development framework| [Weather](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/Weather)| This sample demonstrates one-time development for multi-device deployment by showing how to develop a weather app and deploy it across different devices. The demo app includes the following: home page, **Manage City** page, **Add City** page, and **Update Time** page.| ArkTS |
+| Multimedia subsystem| [MediaCollections](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/FileManagement/MediaCollections)| This sample shows the capabilities of online streaming, audio and video playback control, and volume adjustment.| ArkTS |
 
 For more information, visit [Samples](https://gitee.com/openharmony/applications_app_samples).
 
diff --git a/en/release-notes/OpenHarmony-v3.2-beta4.md b/en/release-notes/OpenHarmony-v3.2-beta4.md
index fa523ca9aa677856547a9181c001ff48b782bc93..dcdf6c5f99a195626b77c6c5854e757d5d676c60 100644
--- a/en/release-notes/OpenHarmony-v3.2-beta4.md
+++ b/en/release-notes/OpenHarmony-v3.2-beta4.md
@@ -196,9 +196,8 @@ The following samples written in ArkTS are added.
 
 | Subsystem | Name| Introduction|
 | -------- | -------- | -------- |
-| Common event and notification subsystem| [Emitter: Prcessing In-Process Events](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Notification/Emitter) | This sample shows the in-process event notification. After a user selects an offering and submits an order, the selected offering is displayed in the order list.|
-| Resource scheduler subsystem| [AlarmClock: Agent-Powered Scheduled Reminder](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Notification/AlarmClock)| This sample uses agent-powered scheduled reminder to create an alarm clock. Agent-powered scheduled reminder ensures that the timing and pop-up notification functions will be performed by the system service agent in the background when the application is frozen or exits. |
-| Window manager| [Window](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Graphics/Window)| This sample shows how to create a window and display an app in a floating window or split-screen mode.|
+| Common event and notification subsystem| [CustomEmitter: Prcessing In-Process Events](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/Notification/CustomEmitter) | This sample shows the in-process event notification. After a user selects an offering and submits an order, the selected offering is displayed in the order list.|
+| Window manager| [WindowManage](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/WindowManagement/WindowManage)| This sample shows how to create a window and display an app in a floating window or split-screen mode.|
 
 For more information, visit [Samples](https://gitee.com/openharmony/applications_app_samples).
 
diff --git a/en/release-notes/api-change/v3.2-beta2/application-sandbox-adaptation-guide.md b/en/release-notes/api-change/v3.2-beta2/application-sandbox-adaptation-guide.md
index c57c81d5415b8dbc0b708cc1eb7ecc86ecb053ed..b0858c5de392f4820f7b0a0c1e2c7bc282f8e6d7 100644
--- a/en/release-notes/api-change/v3.2-beta2/application-sandbox-adaptation-guide.md
+++ b/en/release-notes/api-change/v3.2-beta2/application-sandbox-adaptation-guide.md
@@ -14,7 +14,7 @@
 
 1. Check whether the identified exception is caused by an incorrect access path of the application source code. You can check the correctness of an access path against [Sandbox File Access Specifications](#sandbox-file-access-specifications).
 2. If the application source code accesses an incorrect path, change the path access policy. Specifically, use the **Context** API rather than the absolute path to access the **/data** directory. For details about the **Context** API, see the following documents:
-   https://gitee.com/openharmony/docs/blob/master/zh-cn/application-dev/application-models/application-context-stage.md
+   https://gitee.com/openharmony/docs/blob/master/en/application-dev/application-models/application-context-stage.md
    https://gitee.com/openharmony/docs/blob/master/en/application-dev/reference/apis/js-apis-ability-context.md
    https://gitee.com/OpenHarmony/docs/blob/master/en/application-dev/reference/apis/js-apis-Context.md
 3. If the exception is caused by a third-party module invoked by the application and the application source code does not use an absolute path to access files, proceed as follows:
diff --git a/en/release-notes/changelogs/OpenHarmony_4.0.2.3/changelogs-pasteboard.md b/en/release-notes/changelogs/OpenHarmony_4.0.2.3/changelogs-pasteboard.md
deleted file mode 100644
index 8d8b439cc3a7461162c51abc2f84d09f00412e3d..0000000000000000000000000000000000000000
--- a/en/release-notes/changelogs/OpenHarmony_4.0.2.3/changelogs-pasteboard.md
+++ /dev/null
@@ -1,66 +0,0 @@
-# Pasteboard Subsystem Changelog
-
-OpenHarmony 4.0.3.2 has the following changes in the APIs of the pasteboard subsystem:
-
-## cl.pasteboard.1 convertToTextV9 API Change
-
-Renamed **convertToTextV9** **toPlainText()** and changed the API from asynchronous to synchronous.
-
-**Change Impact**
-
-Applications developed using the **convertToTextV9** API in versions earlier than OpenHarmony 4.0.3.3 cannot be used in OpenHarmony 4.0.3.3 and later versions.
-
-**Key API/Component Changes**
-
-- Involved APIs:
-
-  function convertToTextV9
-
-- Before change:
-
-  ```ts
-  convertToTextV9(callback: AsyncCallback<string>): void;
-  convertToTextV9(): Promise<string>;
-  ```
-
-- After change:
-
-  ```ts
-  toPlainText(): string;
-  ```
-
-
-**Adaptation Guide**
-
-Replace **convertToTextV9**, an asynchronous API, with **toPlainText**, a synchronous API.
-
-## cl.pasteboard.2 ShareOption Enum Name Change
-
-Changed the enum names of **ShareOption** from UpperCamelCase to all caps.
-
-**Change Impact**
-
-Applications developed using the **InApp/LocalDevice/CrossDevice** attributes in versions earlier than OpenHarmony 4.0.3.3 cannot be used in OpenHarmony 4.0.3.3 and later versions.
-
-**Key API/Component Changes**
-
-ShareOption<sup>9+</sup>
-
-Before change:
-| Name| Value| Description               |
-| ---- |---|-------------------|
-| InApp | 0 | Only intra-application pasting is allowed.     |
-| LocalDevice | 1 | Paste is allowed in any application on the local device.|
-| CrossDevice | 2 | Paste is allowed in any application across devices. |
-
-
-After change:
-| Name| Value| Description               |
-| ---- |---|-------------------|
-| INAPP | 0 | Only intra-application pasting is allowed.     |
-| LOCALDEVICE | 1 | Paste is allowed in any application on the local device.|
-| CROSSDEVICE | 2 | Paste is allowed in any application across devices. |
-
-**Adaptation Guide**
-
-Perform adaptation based on the new semantics.
diff --git a/en/release-notes/changelogs/v3.2-beta4/Readme-EN.md b/en/release-notes/changelogs/v3.2-beta4/Readme-EN.md
new file mode 100644
index 0000000000000000000000000000000000000000..ac6eeff37645d7ca227301f1220ad3782b23ffe2
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/Readme-EN.md
@@ -0,0 +1,23 @@
+# Readme
+
+- [Ability framework](changelogs-ability.md)
+- [Account subsystem](changelogs-account_os_account.md)
+- [Multimedia subsystem - camera](changelogs-camera.md)
+- [Device manager](changelogs-device-manager.md)
+- [USB manager](changelogs-device-usb.md)
+- [Distributed scheduler subsystem](changelogs-dmsfwk.md)
+- [DSoftBus subsystem](changelogs-dsoftbus.md)
+- [File management subsystem](changelogs-filemanagement.md)
+- [Location subsystem](changelogs-geolocation.md)
+- [Globalization subsystem](changelogs-global.md)
+- [Multimedia subsystem](changelogs-multimedia.md)
+- [Multimodal input subsystem](changelogs-multimodalinput.md)
+- [Power management subsystem](changelogs-power.md)
+- [Upload and download](changelogs-request.md)
+- [Resource manager subsystem](changelogs-resource-manager.md)
+- [Resource scheduler subsystem](changelogs-resourceschedule.md)
+- [Telephony subsystem](changelogs-telephony.md)
+- [Test subsystem](changelogs-testfwk_arkxtest.md)
+- [User IAM subsystem](changelogs-useriam.md)
+- [Ability framework - WantAgent](changelogs-wantAgent.md)
+- [Communication subsystem - WiFi](changelogs-wifi.md)
diff --git a/en/release-notes/changelogs/v3.2-beta4/Readme.md b/en/release-notes/changelogs/v3.2-beta4/Readme.md
deleted file mode 100644
index fbd75f0d8b94a2bd433825c4315bfba76710d8c0..0000000000000000000000000000000000000000
--- a/en/release-notes/changelogs/v3.2-beta4/Readme.md
+++ /dev/null
@@ -1,8 +0,0 @@
-# Readme
-
-- [Account](changelogs-account_os_account.md)
-- [DSoftBus](changelogs-dsoftbus.md)
-- [File Management](changelogs-filemanagement.md)
-- [Test](changelogs-testfwk_arkxtest.md)
-- [User IAM](changelogs-useriam.md)
-- [Communication-WIFI](changelogs-wifi.md)
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelog-x-x.md b/en/release-notes/changelogs/v3.2-beta4/changelog-x-x.md
new file mode 100644
index 0000000000000000000000000000000000000000..dcc7cd9aabb636ed248b5a37383410d4218b346f
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelog-x-x.md
@@ -0,0 +1,28 @@
+# *Example* Subsystem Changelog
+
+Changes that affect contract compatibility of the last version should be described in the changelog. The changes include but are not limited to those related to API names, parameters, return values, required permissions, call sequence, enumerated values, configuration parameters, and paths. The last version can be an LTS, release, beta, or monthly version, or the like. Contract compatibility, also called semantic compatibility, means that the original program behavior should remain consistent over versions.
+
+## cl.subsystemname.x xxx Function Change (Example: DeviceType Attribute Change or Camera Permission Change. Use a short description.)
+
+Add the number **cl.*subsystemname*.*x*** before each change title, where **cl** is the abbreviation of changelog, *subsystemname* is the standard English name of the subsystem, and *x* indicates the change sequence number (starting from 1 in ascending order).
+Describe the changes in terms of functions. Example: *n* and *m* of the *a* function are changed. Developers need to adapt their applications based on the change description.
+If there is a requirement or design document corresponding to the change, attach the requirement number or design document number in the description.
+
+**Change Impact**
+
+Describe whether released APIs (JS or native APIs) are affected or API behavior is changed.
+Describe whether available applications are affected, that is, whether an adaptation is required for building the application code in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+List the API/component changes involved in the function change.
+
+**Adaptation Guide**
+
+Provide guidance for developers on how to adapt their application to the changes to be compatible with the new version.
+Example:
+Change parameter *n* to *m* in the *a* file.
+
+```
+sample code
+```
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-ability.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-ability.md
new file mode 100644
index 0000000000000000000000000000000000000000..111e725be013af24299c340cd541d385000f182c
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-ability.md
@@ -0,0 +1,375 @@
+# Ability Framework Changelog
+
+## cl.ability.1 Application Component Startup Rule Change
+
+The rules for starting application components are changed in the following scenarios:
+
+ - Start an application component when the application is in the background.
+ - Start an invisible application component across applications.
+ - Start a ServiceAbility and DataAbility of the FA model across applications.
+ - Use the **startAbilityByCall** API.
+
+You need to adapt your application.
+
+
+**Change Impact**
+
+If new rules are not adapted, application components cannot be started in the previous scenarios.
+> **NOTE**
+>
+> Starting application components refers to any behavior starting or connecting to an ability.
+>
+> 1. Start an ability using APIs such as **startAbility**, **startServiceExtensionAbility**, and **startAbilityByCall**.
+> 2. Connect to an ability using APIs such as **connectAbility**, **connectServiceExtensionAbility**, **acquireDataAbilityHelper**, and **createDataShareHelper**.
+
+**Key API/Component Changes**
+
+ - Involved application components
+   - Stage model
+     - Ability
+     - ServiceExtension
+     - DataShareExtension
+   - FA model
+     - PageAbility
+     - ServiceAbility
+     - DataAbility 
+ - Involved APIs
+   - Stage model
+     - startAbility(want: Want, callback: AsyncCallback<void>): void;
+     - startAbility(want: Want, options: StartOptions, callback: AsyncCallback<void>): void;
+     - startAbility(want: Want, options?: StartOptions): Promise<void>;
+     - startAbilityByCall(want: Want): Promise<Caller>;
+     - startAbilityWithAccount(want: Want, accountId: number, callback: AsyncCallback<void>): void;
+     - startAbilityWithAccount(want: Want, accountId: number, options: StartOptions, callback: AsyncCallback<void>): void;
+     - startAbilityWithAccount(want: Want, accountId: number, options?: StartOptions): Promise<void>;
+     - startAbilityForResult(want: Want, callback: AsyncCallback<AbilityResult>): void;
+     - startAbilityForResult(want: Want, options: StartOptions, callback: AsyncCallback<AbilityResult>): void;
+     - startAbilityForResult(want: Want, options?: StartOptions): Promise<AbilityResult>;
+     - startAbilityForResultWithAccount(want: Want, accountId: number, callback: AsyncCallback<AbilityResult>): void;
+     - startAbilityForResultWithAccount(want: Want, accountId: number, options: StartOptions, callback: AsyncCallback<void>): void;
+     - startAbilityForResultWithAccount(want: Want, accountId: number, options?: StartOptions): Promise<AbilityResult>;
+     - startServiceExtensionAbility(want: Want, callback: AsyncCallback<void>): void;
+     - startServiceExtensionAbility(want: Want): Promise<void>;
+     - startServiceExtensionAbilityWithAccount(want: Want, accountId: number, callback: AsyncCallback<void>): void;
+     - startServiceExtensionAbilityWithAccount(want: Want, accountId: number): Promise<void>;
+     - stopServiceExtensionAbility(want: Want, callback: AsyncCallback<void>): void;
+     - stopServiceExtensionAbility(want: Want): Promise<void>;
+     - stopServiceExtensionAbilityWithAccount(want: Want, accountId: number, callback: AsyncCallback<void>): void;
+     - stopServiceExtensionAbilityWithAccount(want: Want, accountId: number): Promise<void>;
+     - connectAbility(want: Want, options: ConnectOptions): number;
+     - connectAbilityWithAccount(want: Want, accountId: number, options: ConnectOptions): number;
+     - createDataShareHelper(context: Context, uri: string, callback: AsyncCallback<DataShareHelper>): void
+   - FA model
+     - startAbility(parameter: StartAbilityParameter, callback: AsyncCallback<number>): void;
+     - startAbility(parameter: StartAbilityParameter): Promise<number>;
+     - startAbilityForResult(parameter: StartAbilityParameter, callback: AsyncCallback<AbilityResult>): void;
+     - startAbilityForResult(parameter: StartAbilityParameter): Promise<AbilityResult>;
+     - acquireDataAbilityHelper(uri: string): DataAbilityHelper;
+     - connectAbility(request: Want, options:ConnectOptions ): number;
+
+**Adaptation Guide**
+
+Startup rules for different scenarios are as follows:
+ - **Starting an application component when the application is in the background**
+   - Rule in OpenHarmony 3.2 Beta3:
+     
+      - There is no restriction.
+   - Rule in OpenHarmony 3.2 Beta4:
+     - Authentication is required. The following permissions must be configured:
+      - ```json
+        {
+            "name": "ohos.permission.START_ABILITIES_FROM_BACKGROUND",
+            "grantMode": "system_grant",
+            "availableLevel": "system_basic",  
+            "provisionEnable": true,
+            "distributedSceneEnable": false
+        }
+        ```
+          > **NOTE**
+          >
+         > 1. Starting an application component of the same application is also restricted by this rule.
+         > 2. For SDKs of API version 8 or earlier, starting a ServiceAbility and DataAbility is not restricted by this rule.
+   
+ - **Starting an invisible application component across applications**
+   
+   - Rule in OpenHarmony 3.2 Beta3:
+     
+     - For applications whose APL is normal, invisible application components cannot be started across applications.
+   - Rule in OpenHarmony 3.2 Beta4:
+     - For all applications, starting an invisible application component across applications requires authentication. The following permissions must be configured:
+     - ```json
+        {
+            "name": "ohos.permission.START_INVISIBLE_ABILITY",
+            "grantMode": "system_grant",
+            "availableLevel": "system_core",
+            "provisionEnable": true,
+            "distributedSceneEnable": false
+        }
+        ```
+
+ - **Starting a ServiceAbility and DataAbility of the FA model across applications**
+
+   - Rule in OpenHarmony 3.2 Beta3:
+     - There is no restriction.
+   - Rule in OpenHarmony 3.2 Beta4:
+     - Associated startup must be configured for the provider of the ServiceAbility and DataAbility. Otherwise, they cannot be started across applications. (Associated startup cannot be configured for common applications.)
+
+
+ - **Using the startAbilityByCall API**
+   - Rule in OpenHarmony 3.2 Beta3:
+     
+     - This is no restriction.
+   - Rule in OpenHarmony 3.2 Beta4:
+     
+     - The **startAbilityByCall** API cannot be called by the same application.
+   - Calling the **startAbilityByCall** API across applications requires authentication. The following permissions must be configured:
+   
+      - ```json
+        {
+            "name": "ohos.permission.ABILITY_BACKGROUND_COMMUNICATION",
+            "grantMode": "system_grant",
+            "availableLevel": "system_basic",
+            "provisionEnable": true,
+            "distributedSceneEnable": false
+        }
+        ```
+        > **NOTE**
+        >
+        > Using the **startAbilityByCall** API is also restricted by the background startup and across-application invisible component startup rules.
+
+## cl.ability.2 Cross-Device Application Component Startup Rule Change (for System Applications Only)
+
+The rules for starting cross-device application components are changed in the following scenarios:
+
+ - Start an application component when the application is in the background.
+ - Start an invisible application component across applications.
+ - Start a ServiceAbility of the FA model across applications.
+
+You need to adapt your application.
+
+
+**Change Impact**
+
+If new rules are not adapted, application components cannot be started in the previous scenarios.
+> **NOTE**
+>
+> Starting application components refers to any behavior starting or connecting to an ability.
+>
+> 1. Start an ability using APIs such as **startAbility**, **startAbilityForResult**, and **startAbilityByCall**.
+> 2. Connect to an ability using APIs such as **connectAbility**.
+
+**Key API/Component Changes**
+
+ - Involved application components
+   - Stage model
+     - Ability
+     - ServiceExtension
+   - FA model
+     - PageAbility
+     - ServiceAbility
+ - Involved APIs
+   - Stage model
+     - startAbility(want: Want, callback: AsyncCallback<void>): void;
+     - startAbilityByCall(want: Want): Promise<Caller>;
+     - startAbilityForResult(want: Want, callback: AsyncCallback<AbilityResult>): void;
+     - connectAbility(want: Want, options: ConnectOptions): number;
+   - FA model
+     - startAbility(parameter: StartAbilityParameter, callback: AsyncCallback<number>): void;
+     - startAbility(parameter: StartAbilityParameter): Promise<number>;
+     - startAbilityForResult(parameter: StartAbilityParameter, callback: AsyncCallback<AbilityResult>): void;
+     - startAbilityForResult(parameter: StartAbilityParameter): Promise<AbilityResult>;
+     - connectAbility(request: Want, options:ConnectOptions ): number;
+
+**Adaptation Guide**
+
+Startup rules for different scenarios are as follows:
+ - **Starting an application component when the application is in the background**
+   - Rule in OpenHarmony 3.2 Beta3:
+     
+      - There is no restriction.
+   - Rule in OpenHarmony 3.2 Beta4:
+     - Authentication is required. The following permissions must be configured:
+      - ```json
+        {
+            "name": "ohos.permission.START_ABILITIES_FROM_BACKGROUND",
+            "grantMode": "system_grant",
+            "availableLevel": "system_basic",  
+            "provisionEnable": true,
+            "distributedSceneEnable": false
+        }
+        ```
+          > **NOTE**
+            1. Starting an application component of the same application is also restricted by this rule.
+                2.  For SDKs of API version 8 or earlier, starting a ServiceAbility is not restricted by this rule. 
+   
+ - **Starting an invisible application component across applications**
+   
+   - Rule in OpenHarmony 3.2 Beta3:
+     
+     - Invisible application components cannot be started across applications.
+   - Rule in OpenHarmony 3.2 Beta4:
+     - Authentication is required. The following permissions must be configured:
+     - ```json
+        {
+            "name": "ohos.permission.START_INVISIBLE_ABILITY",
+            "grantMode": "system_grant",
+            "availableLevel": "system_core",
+            "provisionEnable": true,
+            "distributedSceneEnable": false
+        }
+        ```
+   
+ - **Starting a ServiceAbility of the FA model across applications**
+
+   - Rule in OpenHarmony 3.2 Beta3:
+     
+     - There is no restriction.
+   - Rule in OpenHarmony 3.2 Beta4:
+     - Associated startup needs to be configured for the provider of the ServiceAbility. Otherwise, the ServiceAbility cannot be started across applications. (Associated startup cannot be configured for common applications.)
+     - Configure associated startup as follows:
+     - ```json
+        {
+            "bundleName": "",
+            "app_signature": ["xxxxxxxxxxxxxxxxxxx"],
+            "associatedWakeUp": true
+        }
+        ```
+
+## cl.ability.3 API Exception Handling Method Change
+
+Certain APIs of the ability subsystem use service logic return values to indicate error information, which does not comply with the API error code specifications of OpenHarmony.
+
+**Change Impact**
+
+The application developed based on earlier versions needs to be adapted. Otherwise, the service logic will be affected.
+
+**Key API/Component Changes**
+
+For adaptation to the unified API exception handling mode, certain ability subsystem APIs are deprecated (original APIs in the following table) and corresponding new APIs in the following table are added. (In the following table, original APIs in API version 9 will be deleted, and APIs in API version 8 and earlier will be deprecated.) The newly added APIs support unified error code handling specifications and function the same as the original APIs.
+
+| Original API                                         | New API                                         |
+| ----------------------------------------------- | ----------------------------------------------- |
+| @ohos.ability.wantConstant.d.ts                 | @ohos.app.ability.wantConstant.d.ts             |
+| @ohos.application.Ability.d.ts                  | @ohos.app.ability.UIAbility.d.ts                |
+| @ohos.application.AbilityConstant.d.ts          | @ohos.app.ability.AbilityConstant.d.ts          |
+| @ohos.application.abilityDelegatorRegistry.d.ts | @ohos.app.ability.abilityDelegatorRegistry.d.ts |
+| @ohos.application.AbilityLifecycleCallback.d.ts | @ohos.app.ability.AbilityLifecycleCallback.d.ts |
+| @ohos.application.abilityManager.d.ts           | @ohos.app.ability.abilityManager.d.ts           |
+| @ohos.application.AbilityStage.d.ts             | @ohos.app.ability.AbilityStage.d.ts             |
+| @ohos.application.appManager.d.ts               | @ohos.app.ability.appManager.d.ts               |
+| @ohos.application.Configuration.d.ts            | @ohos.app.ability.Configuration.d.ts            |
+| @ohos.application.ConfigurationConstant.d.ts    | @ohos.app.ability.ConfigurationConstant.d.ts    |
+| @ohos.application.context.d.ts                  | @ohos.app.ability.common.d.ts                   |
+| @ohos.application.EnvironmentCallback.d.ts      | @ohos.app.ability.EnvironmentCallback.d.ts      |
+| @ohos.application.errorManager.d.ts             | @ohos.app.ability.errorManager.d.ts             |
+| @ohos.application.ExtensionAbility.d.ts         | @ohos.app.ability.ExtensionAbility.d.ts         |
+| @ohos.application.formBindingData.d.ts          | @ohos.app.form.formBindingData.d.ts             |
+| @ohos.application.FormExtension.d.ts            | @ohos.app.form.FormExtensionAbility.d.ts        |
+| @ohos.application.formHost.d.ts                 | @ohos.app.form.formHost.d.ts                    |
+| @ohos.application.formInfo.d.ts                 | @ohos.app.form.formInfo.d.ts                    |
+| @ohos.application.formProvider.d.ts             | @ohos.app.form.formProvider.d.ts                |
+| @ohos.application.missionManager.d.ts           | @ohos.app.ability.missionManager.d.ts           |
+| @ohos.application.quickFixManager.d.ts          | @ohos.app.ability.quickFixManager.d.ts          |
+| @ohos.application.ServiceExtensionAbility.d.ts  | @ohos.app.ability.ServiceExtensionAbility.d.ts  |
+| @ohos.application.StartOptions.d.ts             | @ohos.app.ability.StartOptions.d.ts             |
+| @ohos.application.Want.d.ts                     | @ohos.app.ability.Want.d.ts                     |
+| @ohos.wantAgent.d.ts                            | @ohos.app.ability.wantAgent.d.ts                |
+
+**Adaptation Guide**
+
+The original APIs are only moved to the new namespace. Therefore, you can modify **import** to solve the adaptation problem.
+
+If the original API uses **@ohos.application.missionManager**:
+
+```js
+import missionManager from '@ohos.application.missionManager';
+```
+
+You can directly modify **import** to switch to the new namespace:
+
+```js
+import missionManager from '@ohos.app.ability.missionManager';
+```
+
+In addition, exception handling is needed. For details, see the API reference for the new APIs.
+
+## cl.ability.4 API Change
+
+The names of certain ability subsystem APIs are changed.
+
+**Key API/Component Changes**
+
+| Module                                   | Class                   | Method/Attribute/Enum/Constant                                         | Change Type|
+| ----------------------------------------- | ----------------------- | ------------------------------------------------------------ | -------- |
+| @ohos.application.Ability                 | Caller                  | onRelease(callback: OnReleaseCallBack): **void**;            | Deprecated    |
+| @ohos.app.ability.UIAbility               | Caller                  | on(**type**: "release", callback: OnReleaseCallBack): **void**; | Added    |
+| @ohos.application.Ability                 | Ability                 | dump(params: Array<**string**>): Array<**string**>;          | Deprecated    |
+| @ohos.app.ability.UIAbility               | UIAbility               | onDump(params: Array<**string**>): Array<**string**>;        | Added    |
+| @ohos.application.appManager              | appManager              | **function** registerApplicationStateObserver(observer: ApplicationStateObserver): **number**; | Deprecated    |
+| @ohos.application.appManager              | appManager              | **function** registerApplicationStateObserver(observer: ApplicationStateObserver, bundleNameList: Array<**string**>): **number**; | Deprecated    |
+| @ohos.application.appManager              | appManager              | **function** unregisterApplicationStateObserver(observerId: **number**, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| @ohos.application.appManager              | appManager              | **function** unregisterApplicationStateObserver(observerId: **number**): Promise<**void**>; | Deprecated    |
+| @ohos.app.ability.appManager              | appManager              | **function** on(**type**: "applicationState", observer: ApplicationStateObserver): **number**; | Added    |
+| @ohos.app.ability.appManager              | appManager              | **function** on(**type**: "applicationState", observer: ApplicationStateObserver, bundleNameList: Array<**string**>): **number**; | Added    |
+| @ohos.app.ability.appManager              | appManager              | **function** off(**type**: "applicationState", observerId: **number**, callback: AsyncCallback<**void**>): **void**; | Added    |
+| @ohos.app.ability.appManager              | appManager              | **function** off(**type**: "applicationState", observerId: **number**): Promise<**void**>; | Added    |
+| @ohos.application.errorManager            | errorManager            | **function** registerErrorObserver(observer: ErrorObserver): **number**; | Deprecated    |
+| @ohos.application.errorManager            | errorManager            | **function** unregisterErrorObserver(observerId: **number**, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| @ohos.application.errorManager            | errorManager            | **function** unregisterErrorObserver(observerId: **number**): Promise<**void**>; | Deprecated    |
+| @ohos.app.ability.errorManager            | errorManager            | **function** on(**type**: "error", observer: ErrorObserver): **number**; | Added    |
+| @ohos.app.ability.errorManager            | errorManager            | **function** off(**type**: "error", observerId: **number**, callback: AsyncCallback<**void**>): **void**; | Added    |
+| @ohos.app.ability.errorManager            | errorManager            | **function** off(**type**: "error", observerId: **number**): Promise<**void**>; | Added    |
+| @ohos.application.missionManager          | missionManager          | **function** registerMissionListener(listener: MissionListener): **number**; | Deprecated    |
+| @ohos.application.missionManager          | missionManager          | **function** unregisterMissionListener(listenerId: **number**, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| @ohos.application.missionManager          | missionManager          | **function** unregisterMissionListener(listenerId: **number**): Promise<**void**>; | Deprecated    |
+| @ohos.app.ability.missionManager          | missionManager          | **function** on(**type**: "mission", listener: MissionListener): **number**; | Added    |
+| @ohos.app.ability.missionManager          | missionManager          | **function** off(**type**: "mission", listenerId: **number**, callback: AsyncCallback<**void**>): **void**; | Added    |
+| @ohos.app.ability.missionManager          | missionManager          | **function** off(**type**: "mission", listenerId: **number**): Promise<**void**>; | Added    |
+| @ohos.application.FormExtension           | FormExtension           | onCreate(want: Want): formBindingData.FormBindingData;       | Deprecated    |
+| @ohos.application.FormExtension           | FormExtension           | onCastToNormal(formId: **string**): **void**;                | Deprecated    |
+| @ohos.application.FormExtension           | FormExtension           | onUpdate(formId: **string**): **void**;                      | Deprecated    |
+| @ohos.application.FormExtension           | FormExtension           | onVisibilityChange(newStatus: { [key: **string**]: **number** }): **void**; | Deprecated    |
+| @ohos.application.FormExtension           | FormExtension           | onEvent(formId: **string**, message: **string**): **void**;  | Deprecated    |
+| @ohos.application.FormExtension           | FormExtension           | onDestroy(formId: **string**): **void**;                     | Deprecated    |
+| @ohos.application.FormExtension           | FormExtension           | onShare?(formId: **string**): {[key: **string**]: **any**};  | Deprecated    |
+| @ohos.app.form.FormExtensionAbility       | FormExtensionAbility    | onAddForm(want: Want): formBindingData.FormBindingData;      | Added    |
+| @ohos.app.form.FormExtensionAbility       | FormExtensionAbility    | onCastToNormalForm(formId: **string**): **void**;            | Added    |
+| @ohos.app.form.FormExtensionAbility       | FormExtensionAbility    | onUpdateForm(formId: **string**): **void**;                  | Added    |
+| @ohos.app.form.FormExtensionAbility       | FormExtensionAbility    | onChangeFormVisibility(newStatus: { [key: **string**]: **number** }): **void**; | Added    |
+| @ohos.app.form.FormExtensionAbility       | FormExtensionAbility    | onFormEvent(formId: **string**, message: **string**): **void**; | Added    |
+| @ohos.app.form.FormExtensionAbility       | FormExtensionAbility    | onRemoveForm(formId: **string**): **void**;                  | Added    |
+| @ohos.app.form.FormExtensionAbility       | FormExtensionAbility    | onShareForm?(formId: **string**): {[key: **string**]: **any**}; | Added    |
+| @ohos.application.formHost.d.ts           | formHost                | **function** castTempForm(formId: **string**, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| @ohos.application.formHost.d.ts           | formHost                | **function** castTempForm(formId: **string**): Promise<**void**>; | Deprecated    |
+| @ohos.app.form.formHost.d.ts              | formHost                | **function** castToNormalForm(formId: **string**, callback: AsyncCallback<**void**>): **void**; | Added    |
+| @ohos.app.form.formHost.d.ts              | formHost                | **function** castToNormalForm(formId: **string**): Promise<**void**>; | Added    |
+| @ohos.application.ServiceExtensionAbility | ServiceExtensionAbility | dump(params: Array<**string**>): Array<**string**>;          | Deprecated    |
+| @ohos.app.ability.ServiceExtensionAbility | ServiceExtensionAbility | onDump(params: Array<**string**>): Array<**string**>;        | Added    |
+| application/AbilityContext                | AbilityContext          | connectAbility(want: Want, options: ConnectOptions): **number**; | Deprecated    |
+| application/AbilityContext                | AbilityContext          | connectAbilityWithAccount(want: Want, accountId: **number**, options: ConnectOptions): **number**; | Deprecated    |
+| application/AbilityContext                | AbilityContext          | disconnectAbility(connection: **number**, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| application/AbilityContext                | AbilityContext          | disconnectAbility(connection: **number**): Promise<**void**>; | Deprecated    |
+| application/UIAbilityContext              | UIAbilityContext        | connectServiceExtensionAbilityWithAccount(want: Want, accountId: **number**, options: ConnectOptions): **number**; | Added    |
+| application/UIAbilityContext              | UIAbilityContext        | connectServiceExtensionAbilityWithAccount(want: Want, accountId: **number**, options: ConnectOptions): **number**; | Added    |
+| application/UIAbilityContext              | UIAbilityContext        | disconnectServiceExtensionAbility(connection: **number**, callback: AsyncCallback<**void**>): **void**; | Added    |
+| application/UIAbilityContext              | UIAbilityContext        | disconnectServiceExtensionAbility(connection: **number**): Promise<**void**>; | Added    |
+| application/ApplicationContext            | ApplicationContext      | registerAbilityLifecycleCallback(callback: AbilityLifecycleCallback): **number**; | Deprecated    |
+| application/ApplicationContext            | ApplicationContext      | unregisterAbilityLifecycleCallback(callbackId: **number**, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| application/ApplicationContext            | ApplicationContext      | unregisterAbilityLifecycleCallback(callbackId: **number**): Promise<**void**>; | Deprecated    |
+| application/ApplicationContext            | ApplicationContext      | registerEnvironmentCallback(callback: EnvironmentCallback): **number**; | Deprecated    |
+| application/ApplicationContext            | ApplicationContext      | unregisterEnvironmentCallback(callbackId: **number**, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| application/ApplicationContext            | ApplicationContext      | unregisterEnvironmentCallback(callbackId: **number**): Promise<**void**>; | Deprecated    |
+| application/ApplicationContext            | ApplicationContext      | on(**type**: "abilityLifecycle", callback: AbilityLifecycleCallback): **number**; | Added    |
+| application/ApplicationContext            | ApplicationContext      | off(**type**: "abilityLifecycle", callbackId: **number**, callback: AsyncCallback<**void**>): **void**; | Added    |
+| application/ApplicationContext            | ApplicationContext      | off(**type**: "abilityLifecycle", callbackId: **number**): Promise<**void**>; | Added    |
+| application/ApplicationContext            | ApplicationContext      | on(**type**: "environment", callback: EnvironmentCallback): **number**; | Added    |
+| application/ApplicationContext            | ApplicationContext      | off(**type**: "environment", callbackId: **number**, callback: AsyncCallback<**void**>): **void**; | Added    |
+| application/ApplicationContext            | ApplicationContext      | off(**type**: "environment", callbackId: **number**): Promise<**void**>; | Added    |
+| application/ServiceExtensionContext       | ServiceExtensionContext | connectAbility(want: Want, options: ConnectOptions): **number**; | Deprecated    |
+| application/ServiceExtensionContext       | ServiceExtensionContext | connectAbilityWithAccount(want: Want, accountId: **number**, options: ConnectOptions): **number**; | Deprecated    |
+| application/ServiceExtensionContext       | ServiceExtensionContext | disconnectAbility(connection: **number**, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| application/ServiceExtensionContext       | ServiceExtensionContext | disconnectAbility(connection: **number**): Promise<**void**>; | Deprecated    |
+| application/ServiceExtensionContext       | ServiceExtensionContext | connectServiceExtensionAbility(want: Want, options: ConnectOptions): **number**; | Added    |
+| application/ServiceExtensionContext       | ServiceExtensionContext | connectServiceExtensionAbilityWithAccount(want: Want, accountId: **number**, options: ConnectOptions): **number**; | Added    |
+| application/ServiceExtensionContext       | ServiceExtensionContext | disconnectServiceExtensionAbility(connection: **number**, callback: AsyncCallback<**void**>): **void**; | Added    |
+| application/ServiceExtensionContext       | ServiceExtensionContext | disconnectServiceExtensionAbility(connection: **number**): Promise<**void**>; | Added    |
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-arkui.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-arkui.md
new file mode 100644
index 0000000000000000000000000000000000000000..7acdb1c010235634345e80a1605255b2e4fbc5dd
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-arkui.md
@@ -0,0 +1,126 @@
+# ArkUI Subsystem ChangeLog
+
+## cl.arkui.1 xcomponent API Change
+
+Changed the following APIs of the **xcomponent** component of the ArkUI subsystem:
+
+ - **getXComponentSurfaceId** and **setXComponentSurfaceSize**: Removed the **@systemapi** tag.
+ - **getXComponentSurfaceId**, **getXComponentContext**, and **setXComponentSurfaceSize**: Specified the return value type.
+
+You need to adapt your application based on the following information.
+
+
+**Change Impact**
+
+Released JS APIs are affected. The application needs to adapt these APIs so that it can be properly compiled in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+ - **getXComponentSurfaceId**: is changed to a public API, with its return value type specified as string.
+ - **setXComponentSurfaceSize**: is changed to a public API, with its return value type specified as void.
+ - **getXComponentContext**: has its return value type specified as object.
+
+**Adaptation Guide**
+
+Startup rules for different scenarios are as follows:
+Adaptions to be made:
+
+  - **getXComponentSurfaceId**
+    - Rule in OpenHarmony 3.2 Beta3:
+      - System API
+      - No specified return value
+    - OpenHarmony 3.2 Beta4 rules:
+      - Public API
+      - Return value type specified as string
+      - You need to process the return value as a string.
+  - **setXComponentSurfaceSize**
+    - Rule in OpenHarmony 3.2 Beta3:
+      - System API
+      - No specified return value
+    - OpenHarmony 3.2 Beta4 rules:
+      - Public API
+      - Return value type specified as void
+      - You need to process the return value as a void.
+  - **getXComponentContext**
+    - Rule in OpenHarmony 3.2 Beta3:
+      - No specified return value
+    - OpenHarmony 3.2 Beta4 rules:
+      - Return value type specified as object
+      - You need to process the return value as an object.
+        
+## cl.arkui.2 Change of Styles of Popup Component and APIs
+
+Changed the styles of the **alertDialog**, **actionSheet**, and **customDialog** components, as well as the **prompt** and **promptAction** APIs. Specifically speaking:
+
+ - Added the popup background blur effect to **promptAction.showDialog**, **promptAction.showActionMenu**, **alertDialog**, **actionSheet**, and **customDialog**.
+
+**Change Impact**
+
+The popup background blur effect is set by default.
+
+**Key API/Component Changes**
+
+APIs: **promptAction.showDialog** and **promptAction.showActionMenu;**
+Components: **alertDialog**, **actionSheet**, and **customDialog**
+
+**Adaptation Guide**
+
+No adaptation is required.
+
+## cl.arkui.3 Supplementation of the Initialization Mode and Restriction Verification Scenarios of Custom Components' Member Variables
+
+For details, see [Restrictions and Extensions](https://gitee.com/openharmony/docs/blob/master/en/application-dev/quick-start/arkts-restrictions-and-extensions.md).
+
+
+**Change Impact**
+
+If custom components' member variables are initialized or assigned with values not according to the document specifications, an error will be reported during compilation.
+
+**Key API/Component Changes**
+
+N/A.
+
+**Adaptation Guide**
+
+Make modification according to specifications in the above document.
+
+## cl.arkui.4 Supplementation of Verification Scenarios of Value Assignment Restrictions on Member Variables of Custom Parent Components and Child Components
+
+For details, see [Restrictions and Extensions](../../../application-dev/quick-start/arkts-restrictions-and-extensions.md).
+
+
+**Change Impact**
+
+If member variables of the parent component or child component are initialized not according to the document specifications, an error will be reported during compilation.
+
+**Key API/Component Changes**
+
+N/A.
+
+**Adaptation Guide**
+
+Make modification according to specifications in the above document, using other decorators or normal member variables for value assignment.
+
+## cl.arkui.5 Supplementation of Verification for a Single Subcomponent
+
+Added the check rule that allows only one child component to be enabled for the following components: **Button**, **FlowItem**, **GridItem**, **GridCol**, **ListItem**, **Navigator**, **Refresh**, **RichText**, **ScrollBar**, **StepperItem**, and **TabContent**.
+
+
+**Change Impact**
+
+If one of the preceding components contains more than one child component, an error will be reported during compilation.
+
+**Key API/Component Changes**
+
+```js
+RichText('RichText') {
+    Text('Text1')
+    Text('Text2')
+}
+/* ArkTS:ERROR File: /root/newOH/developtools/ace-ets2bundle/compiler/sample/pages/home.ets:25:7
+ The component 'RichText' can only have a single child component. */
+```
+
+**Adaptation Guide**
+
+Make modification based on the error message. Make sure that the specified component contains only one child component.
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-camera.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-camera.md
new file mode 100644
index 0000000000000000000000000000000000000000..f7acbc22c91eed241e6ddfa34e041f87ece63130
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-camera.md
@@ -0,0 +1,781 @@
+# Multimedia Subsystem Changelog
+
+## Camera API Changes
+Some functional APIs are added and some others are deprecated to:
+1. Improve the usability of camera APIs.
+2. Help you quickly understand camera APIs and use them for development.
+3. Facilitate expansion of framework functions in later versions, and reduce coupling between framework modules.
+
+You need to refer to the following change description to adapt your application.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                | Class                   | Method/Attribute/Enum/Constant                                         | Change Type|
+| ---------------------- | ----------------------- | ------------------------------------------------------------ | -------- |
+| ohos.multimedia.camera | Profile                 | readonly format:CameraFormat;                                | Added    |
+| ohos.multimedia.camera | Profile                 | readonly size: Size;                                         | Added    |
+| ohos.multimedia.camera | FrameRateRange          | readonly min: number;                                        | Added    |
+| ohos.multimedia.camera | FrameRateRange          | readonly max: number;                                        | Added    |
+| ohos.multimedia.camera | VideoProfile            | readonly frameRateRange: FrameRateRange;                     | Added    |
+| ohos.multimedia.camera | CameraOutputCapability  | readonly previewProfiles: Array<Profile>;                    | Added    |
+| ohos.multimedia.camera | CameraOutputCapability  | readonly photoProfiles: Array<Profile>;                      | Added    |
+| ohos.multimedia.camera | CameraOutputCapability  | readonly videoProfiles: Array<VideoProfile>;                 | Added    |
+| ohos.multimedia.camera | CameraOutputCapability  | readonly supportedMetadataObjectTypes: Array<MetadataObjectType>; | Added    |
+| ohos.multimedia.camera | CameraManager           | getSupportedCameras(callback: AsyncCallback<Array<CameraDevice>>): void;<br>getSupportedCameras(): Promise<Array<CameraDevice>>; | Added    |
+| ohos.multimedia.camera | CameraManager           | getSupportedOutputCapability(camera: CameraDevice, callback: AsyncCallback<CameraOutputCapability>): void;<br>getSupportedOutputCapability(camera: CameraDevice): Promise<CameraOutputCapability>; | Added    |
+| ohos.multimedia.camera | CameraManager           | isCameraMuted(): boolean;                                    | Added    |
+| ohos.multimedia.camera | CameraManager           | isCameraMuteSupported(): boolean;                            | Added    |
+| ohos.multimedia.camera | CameraManager           | muteCamera(mute: boolean): void;                             | Added    |
+| ohos.multimedia.camera | CameraManager           | createCameraInput(camera: CameraDevice, callback: AsyncCallback<CameraInput>): void;<br>createCameraInput(camera: CameraDevice): Promise<CameraInput>; | Added    |
+| ohos.multimedia.camera | CameraManager           | createPreviewOutput(profile: Profile, surfaceId: string, callback: AsyncCallback<PreviewOutput>): void;<br>createPreviewOutput(profile: Profile, surfaceId: string): Promise<PreviewOutput>; | Added    |
+| ohos.multimedia.camera | CameraManager           | createPhotoOutput(profile: Profile, surfaceId: string, callback: AsyncCallback<PhotoOutput>): void;<br>createPhotoOutput(profile: Profile, surfaceId: string): Promise<PhotoOutput>; | Added    |
+| ohos.multimedia.camera | CameraManager           | createVideoOutput(profile: VideoProfile, surfaceId: string, callback: AsyncCallback<VideoOutput>): void;<br>createVideoOutput(profile: VideoProfile, surfaceId: string): Promise<VideoOutput>; | Added    |
+| ohos.multimedia.camera | CameraManager           | createMetadataOutput(metadataObjectTypes: Array<MetadataObjectType>, callback: AsyncCallback<MetadataOutput>): void;<br>createMetadataOutput(metadataObjectTypes: Array<MetadataObjectType>): Promise<MetadataOutput>; | Added    |
+| ohos.multimedia.camera | CameraManager           | createCaptureSession(callback: AsyncCallback<CaptureSession>): void;<br>createCaptureSession(): Promise<CaptureSession>; | Added    |
+| ohos.multimedia.camera | CameraManager           | on(type: 'cameraMute', callback: AsyncCallback<boolean>): void; | Added    |
+| ohos.multimedia.camera | CameraManager           | getCameras(callback: AsyncCallback<Array<Camera>>): void;<br>getCameras(): Promise<Array<Camera>>; | Deprecated    |
+| ohos.multimedia.camera | CameraManager           | createCameraInput(cameraId: string, callback: AsyncCallback<CameraInput>): void;<br>createCameraInput(cameraId: string): Promise<CameraInput>; | Deprecated    |
+| ohos.multimedia.camera | CameraManager           | createCaptureSession(context: Context, callback: AsyncCallback<CaptureSession>): void;<br>createCaptureSession(context: Context): Promise<CaptureSession>; | Deprecated    |
+| ohos.multimedia.camera | CameraManager           | createPreviewOutput(surfaceId: string, callback: AsyncCallback<PreviewOutput>): void;<br>createPreviewOutput(surfaceId: string): Promise<PreviewOutput>; | Deprecated    |
+| ohos.multimedia.camera | CameraManager           | CreatePhotoOutput(surfaceId: string, callback: AsyncCallback<PhotoOutput>): void;<br>CreatePhotoOutput(surfaceId: string): Promise<PhotoOutput>; | Deprecated    |
+| ohos.multimedia.camera | CameraManager           | createVideoOutput(surfaceId: string, callback: AsyncCallback<VideoOutput>): void;<br>createVideoOutput(surfaceId: string): Promise<VideoOutput>; | Deprecated    |
+| ohos.multimedia.camera | CameraManager           | createMetadataOutput(callback: AsyncCallback<MetadataOutput>): void;<br>createVideoOutput(): Promise<MetadataOutput>; | Deprecated    |
+| ohos.multimedia.camera | CameraStatusInfo        | camera: CameraDevice;                                        | Added    |
+| ohos.multimedia.camera | CameraStatusInfo        | camera: Camera;                                              | Deprecated    |
+| ohos.multimedia.camera | CameraDevice            | interface CameraDevice                                       | Added    |
+| ohos.multimedia.camera | Camera                  | interface Camera                                             | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | open(callback: AsyncCallback<void>): void;<br>open(): Promise<void>; | Added    |
+| ohos.multimedia.camera | CameraInput             | close(callback: AsyncCallback<void>): void;<br>close(): Promise<void>; | Added    |
+| ohos.multimedia.camera | CameraInput             | on(type: 'error', camera: CameraDevice, callback: ErrorCallback<CameraInputError>): void; | Added    |
+| ohos.multimedia.camera | CameraInput             | isFocusModeSupported(afMode: FocusMode, callback: AsyncCallback<boolean>): void;<br>isFocusModeSupported(afMode: FocusMode): Promise<boolean>; | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | getFocusMode(callback: AsyncCallback<FocusMode>): void;<br>getFocusMode(): Promise<FocusMode>; | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | setFocusMode(afMode: FocusMode, callback: AsyncCallback<void>): void;<br>setFocusMode(afMode: FocusMode): Promise<void>; | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | getZoomRatioRange(callback: AsyncCallback<Array<number>>): void;<br>getZoomRatioRange(): Promise<Array<number>>; | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | getZoomRatio(callback: AsyncCallback<number>): void;<br>getZoomRatio(): Promise<number>; | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | setZoomRatio(zoomRatio: number, callback: AsyncCallback<void>): void;<br>setZoomRatio(zoomRatio: number): Promise<void>; | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | getCameraId(callback: AsyncCallback<string>): void;<br>getCameraId(): Promise<string>; | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | getExposurePoint(callback: AsyncCallback<Point>): void;<br>getExposurePoint(): Promise<Point>; | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | setExposurePoint(exposurePoint: Point, callback: AsyncCallback<void>): void;<br>setExposurePoint(exposurePoint: Point): Promise<void>; | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | hasFlash(callback: AsyncCallback<boolean>): void;<br>hasFlash(): Promise<boolean>;                                                                         | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | isFlashModeSupported(flashMode: FlashMode, callback: AsyncCallback<boolean>): void;<br>isFlashModeSupported(flashMode: FlashMode): Promise<boolean>;       | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | getFlashMode(callback: AsyncCallback<FlashMode>): void;<br>getFlashMode(): Promise<FlashMode>;                                                             | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | setFlashMode(flashMode: FlashMode, callback: AsyncCallback<void>): void;<br>setFlashMode(flashMode: FlashMode): Promise<void>;                             | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | isExposureModeSupported(aeMode: ExposureMode, callback: AsyncCallback<boolean>): void;<br>isExposureModeSupported(aeMode: ExposureMode): Promise<boolean>; | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | getExposureMode(callback: AsyncCallback<ExposureMode>): void;<br>getExposureMode(): Promise<ExposureMode>;                                                 | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | setExposureMode(aeMode: ExposureMode, callback: AsyncCallback<void>): void;<br>setExposureMode(aeMode: ExposureMode): Promise<void>;                       | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | getMeteringPoint(callback: AsyncCallback<Point>): void;<br>getMeteringPoint(): Promise<Point>;                                                             | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | setMeteringPoint(point: Point, callback: AsyncCallback<void>): void;<br>setMeteringPoint(point: Point): Promise<void>;                                     | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | getExposureBiasRange(callback: AsyncCallback<Array<number>>): void;<br>getExposureBiasRange(): Promise<Array<number>>;                                     | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | setExposureBias(exposureBias: number, callback: AsyncCallback<void>): void;<br>setExposureBias(exposureBias: number): Promise<void>;                       | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | getExposureValue(callback: AsyncCallback<number>): void;<br>getExposureValue(): Promise<number>;                                                           | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | isFocusModeSupported(afMode: FocusMode, callback: AsyncCallback<boolean>): void;<br>isFocusModeSupported(afMode: FocusMode): Promise<boolean>;             | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | getFocusMode(callback: AsyncCallback<FocusMode>): void;<br>getFocusMode(): Promise<FocusMode>;                                                             | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | setFocusMode(afMode: FocusMode, callback: AsyncCallback<void>): void;<br>setFocusMode(afMode: FocusMode): Promise<void>;                                   | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | setFocusPoint(point: Point, callback: AsyncCallback<void>): void;<br>setFocusPoint(point: Point): Promise<void>;                                           | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | getFocusPoint(callback: AsyncCallback<Point>): void;<br>getFocusPoint(): Promise<Point>;                                                                   | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | getFocalLength(callback: AsyncCallback<number>): void;<br>getFocalLength(): Promise<number>;                                                               | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | getZoomRatioRange(callback: AsyncCallback<Array<number>>): void;<br>getZoomRatioRange(): Promise<Array<number>>;                                           | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | getZoomRatio(callback: AsyncCallback<number>): void;<br>getZoomRatio(): Promise<number>;                                                                   | Deprecated    |
+| ohos.multimedia.camera | CameraInput          | setZoomRatio(zoomRatio: number, callback: AsyncCallback<void>): void;<br>setZoomRatio(zoomRatio: number): Promise<void>;                                   | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | on(type: 'focusStateChange', callback: AsyncCallback<FocusState>): void; | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | on(type: 'exposureStateChange', callback: AsyncCallback<ExposureState>): void; | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | on(type: 'error', callback: ErrorCallback<CameraInputError>): void; | Deprecated    |
+| ohos.multimedia.camera | CameraInputErrorCode    | ERROR_NO_PERMISSION = 0                                      | Added    |
+| ohos.multimedia.camera | CameraInputErrorCode    | ERROR_DEVICE_PREEMPTED = 1                                   | Added    |
+| ohos.multimedia.camera | CameraInputErrorCode    | ERROR_DEVICE_DISCONNECTED = 2                                | Added    |
+| ohos.multimedia.camera | CameraInputErrorCode    | ERROR_DEVICE_IN_USE = 3                                      | Added    |
+| ohos.multimedia.camera | CameraInputErrorCode    | ERROR_DRIVER_ERROR = 4                                       | Added    |
+| ohos.multimedia.camera | CameraFormat            | CAMERA_FORMAT_RGBA_8888 = 3                                  | Added    |
+| ohos.multimedia.camera | ExposureMode            | EXPOSURE_MODE_AUTO = 1                                       | Added    |
+| ohos.multimedia.camera | ExposureMode            | EXPOSURE_MODE_CONTINUOUS_AUTO = 2                            | Added    |
+| ohos.multimedia.camera | ExposureMode            | EXPOSURE_MODE_AUTO                                      | Deprecated    |
+| ohos.multimedia.camera | ExposureMode            | EXPOSURE_MODE_CONTINUOUS_AUTO                          | Deprecated    |
+| ohos.multimedia.camera | VideoStabilizationMode  | LOW = 1                                                      | Added    |
+| ohos.multimedia.camera | VideoStabilizationMode  | MIDDLE = 2                                                   | Added    |
+| ohos.multimedia.camera | VideoStabilizationMode  | HIGH = 3                                                     | Added    |
+| ohos.multimedia.camera | VideoStabilizationMode  | AUTO = 4                                                     | Added    |
+| ohos.multimedia.camera | VideoStabilizationMode  | LOW                                                    | Deprecated    |
+| ohos.multimedia.camera | VideoStabilizationMode  | MIDDLE                                                 | Deprecated    |
+| ohos.multimedia.camera | VideoStabilizationMode  | HIGH                                                     | Deprecated    |
+| ohos.multimedia.camera | VideoStabilizationMode  | AUTO                                                     | Deprecated    |
+| ohos.multimedia.camera | CaptureSession          | addOutput(cameraOutput: CameraOutput, callback: AsyncCallback<void>): void;<br>addOutput(cameraOutput: CameraOutput): Promise<void>; | Added    |
+| ohos.multimedia.camera | CaptureSession          | removeOutput(cameraOutput: CameraOutput, callback: AsyncCallback<void>): void;<br>removeOutput(cameraOutput: CameraOutput): Promise<void>; | Added    |
+| ohos.multimedia.camera | CaptureSession          | isVideoStabilizationModeSupported(vsMode: VideoStabilizationMode, callback: AsyncCallback<boolean>): void;<br>isVideoStabilizationModeSupported(vsMode: VideoStabilizationMode): Promise<boolean>; | Added    |
+| ohos.multimedia.camera | CaptureSession          | getActiveVideoStabilizationMode(callback: AsyncCallback<VideoStabilizationMode>): void;<br>getActiveVideoStabilizationMode(): Promise<VideoStabilizationMode>; | Added    |
+| ohos.multimedia.camera | CaptureSession          | setVideoStabilizationMode(mode: VideoStabilizationMode, callback: AsyncCallback<void>): void;<br>setVideoStabilizationMode(mode: VideoStabilizationMode): Promise<void>; | Added    |
+| ohos.multimedia.camera | CaptureSession          | on(type: 'focusStateChange', callback: AsyncCallback<FocusState>): void; | Added    |
+| ohos.multimedia.camera | CaptureSession          | hasFlash(callback: AsyncCallback<boolean>): void;<br>hasFlash(): Promise<boolean>;                                                                         | Added    |
+| ohos.multimedia.camera | CaptureSession          | isFlashModeSupported(flashMode: FlashMode, callback: AsyncCallback<boolean>): void;<br>isFlashModeSupported(flashMode: FlashMode): Promise<boolean>;       | Added    |
+| ohos.multimedia.camera | CaptureSession          | getFlashMode(callback: AsyncCallback<FlashMode>): void;<br>getFlashMode(): Promise<FlashMode>;                                                             | Added    |
+| ohos.multimedia.camera | CaptureSession          | setFlashMode(flashMode: FlashMode, callback: AsyncCallback<void>): void;<br>setFlashMode(flashMode: FlashMode): Promise<void>;                             | Added    |
+| ohos.multimedia.camera | CaptureSession          | isExposureModeSupported(aeMode: ExposureMode, callback: AsyncCallback<boolean>): void;<br>isExposureModeSupported(aeMode: ExposureMode): Promise<boolean>; | Added    |
+| ohos.multimedia.camera | CaptureSession          | getExposureMode(callback: AsyncCallback<ExposureMode>): void;<br>getExposureMode(): Promise<ExposureMode>;                                                 | Added    |
+| ohos.multimedia.camera | CaptureSession          | setExposureMode(aeMode: ExposureMode, callback: AsyncCallback<void>): void;<br>setExposureMode(aeMode: ExposureMode): Promise<void>;                       | Added    |
+| ohos.multimedia.camera | CaptureSession          | getMeteringPoint(callback: AsyncCallback<Point>): void;<br>getMeteringPoint(): Promise<Point>;                                                             | Added    |
+| ohos.multimedia.camera | CaptureSession          | setMeteringPoint(point: Point, callback: AsyncCallback<void>): void;<br>setMeteringPoint(point: Point): Promise<void>;                                     | Added    |
+| ohos.multimedia.camera | CaptureSession          | getExposureBiasRange(callback: AsyncCallback<Array<number>>): void;<br>getExposureBiasRange(): Promise<Array<number>>;                                     | Added    |
+| ohos.multimedia.camera | CaptureSession          | setExposureBias(exposureBias: number, callback: AsyncCallback<void>): void;<br>setExposureBias(exposureBias: number): Promise<void>;                       | Added    |
+| ohos.multimedia.camera | CaptureSession          | getExposureValue(callback: AsyncCallback<number>): void;<br>getExposureValue(): Promise<number>;                                                           | Added    |
+| ohos.multimedia.camera | CaptureSession          | isFocusModeSupported(afMode: FocusMode, callback: AsyncCallback<boolean>): void;<br>isFocusModeSupported(afMode: FocusMode): Promise<boolean>;             | Added    |
+| ohos.multimedia.camera | CaptureSession          | getFocusMode(callback: AsyncCallback<FocusMode>): void;<br>getFocusMode(): Promise<FocusMode>;                                                             | Added    |
+| ohos.multimedia.camera | CaptureSession          | setFocusMode(afMode: FocusMode, callback: AsyncCallback<void>): void;<br>setFocusMode(afMode: FocusMode): Promise<void>;                                   | Added    |
+| ohos.multimedia.camera | CaptureSession          | setFocusPoint(point: Point, callback: AsyncCallback<void>): void;<br>setFocusPoint(point: Point): Promise<void>;                                           | Added    |
+| ohos.multimedia.camera | CaptureSession          | getFocusPoint(callback: AsyncCallback<Point>): void;<br>getFocusPoint(): Promise<Point>;                                                                   | Added    |
+| ohos.multimedia.camera | CaptureSession          | getFocalLength(callback: AsyncCallback<number>): void;<br>getFocalLength(): Promise<number>;                                                               | Added    |
+| ohos.multimedia.camera | CaptureSession          | getZoomRatioRange(callback: AsyncCallback<Array<number>>): void;<br>getZoomRatioRange(): Promise<Array<number>>;                                           | Added    |
+| ohos.multimedia.camera | CaptureSession          | getZoomRatio(callback: AsyncCallback<number>): void;<br>getZoomRatio(): Promise<number>;                                                                   | Added    |
+| ohos.multimedia.camera | CaptureSession          | setZoomRatio(zoomRatio: number, callback: AsyncCallback<void>): void;<br>setZoomRatio(zoomRatio: number): Promise<void>;                                   | Added    |
+| ohos.multimedia.camera | CaptureSession          | addOutput(previewOutput: PreviewOutput, callback: AsyncCallback<void>): void;<br>addOutput(previewOutput: PreviewOutput): Promise<void>;<br>addOutput(photoOutput: PhotoOutput, callback: AsyncCallback<void>): void;<br>addOutput(photoOutput: PhotoOutput): Promise<void>;<br>addOutput(videoOutput: VideoOutput, callback: AsyncCallback<void>): void;<br>addOutput(videoOutput: VideoOutput): Promise<void>; | Deprecated    |
+| ohos.multimedia.camera | CaptureSession          | removeOutput(previewOutput: PreviewOutput, callback: AsyncCallback<void>): void;<br>removeOutput(previewOutput: PreviewOutput): Promise<void>;<br>removeOutput(photoOutput: PhotoOutput, callback: AsyncCallback<void>): void;<br>removeOutput(photoOutput: PhotoOutput): Promise<void>;removeOutput(videoOutput: VideoOutput, callback: AsyncCallback<void>): void;<br>removeOutput(videoOutput: VideoOutput): Promise<void>;<br>removeOutput(metadataOutput: MetadataOutput, callback: AsyncCallback<void>): void;<br>removeOutput(metadataOutput: MetadataOutput): Promise<void>; | Deprecated    |
+| ohos.multimedia.camera | CaptureSessionErrorCode | ERROR_INSUFFICIENT_RESOURCES = 0                             | Added    |
+| ohos.multimedia.camera | CaptureSessionErrorCode | ERROR_TIMEOUT = 1                                            | Added    |
+| ohos.multimedia.camera | CameraOutput            | release(callback: AsyncCallback<void>): void;<br>release(): Promise<void>; | Added    |
+| ohos.multimedia.camera | PreviewOutput           | start(callback: AsyncCallback<void>): void;<br>start(): Promise<void>; | Added    |
+| ohos.multimedia.camera | PreviewOutput           | stop(callback: AsyncCallback<void>): void;<br>stop(): Promise<void>; | Added    |
+| ohos.multimedia.camera | PreviewOutput           | release(callback: AsyncCallback<void>): void;<br>release(): Promise<void>; | Deprecated    |
+| ohos.multimedia.camera | PhotoOutput             | release(callback: AsyncCallback<void>): void;<br>release(): Promise<void>; | Deprecated    |
+| ohos.multimedia.camera | VideoOutput             | release(callback: AsyncCallback<void>): void;<br>release(): Promise<void>; | Deprecated    |
+| ohos.multimedia.camera | PhotoCaptureSetting     | mirror?: boolean;                                            | Added    |
+| ohos.multimedia.camera | PhotoOutputErrorCode    | ERROR_DRIVER_ERROR = 0                                       | Added    |
+| ohos.multimedia.camera | PhotoOutputErrorCode    | ERROR_INSUFFICIENT_RESOURCES = 1                             | Added    |
+| ohos.multimedia.camera | PhotoOutputErrorCode    | ERROR_TIMEOUT = 2                                            | Added    |
+| ohos.multimedia.camera | VideoOutputErrorCode    | ERROR_DRIVER_ERROR = 0                                       | Added    |
+| ohos.multimedia.camera | MetadataObjectType      | FACE_DETECTION = 0                                           | Added    |
+| ohos.multimedia.camera | MetadataObjectType      | FACE = 0                                                 | Deprecated    |
+| ohos.multimedia.camera | MetadataOutput          | on(type: 'error', callback: ErrorCallback<MetadataOutputError>): void; | Added    |
+| ohos.multimedia.camera | MetadataOutput      | setCapturingMetadataObjectTypes(metadataObjectTypes: Array<MetadataObjectType>, callback: AsyncCallback<void>): void;<br>setCapturingMetadataObjectTypes(metadataObjectTypes: Array<MetadataObjectType>): Promise<void>;    | Deprecated    |
+| ohos.multimedia.camera | MetadataOutput      | getSupportedMetadataObjectTypes(callback: AsyncCallback<Array<MetadataObjectType>>): void;<br>getSupportedMetadataObjectTypes(): Promise<Array<MetadataObjectType>>;    | Deprecated    |
+| ohos.multimedia.camera | MetadataOutputErrorCode | ERROR_UNKNOWN = -1                                           | Added    |
+| ohos.multimedia.camera | MetadataOutputErrorCode | ERROR_INSUFFICIENT_RESOURCES = 0                             | Added    |
+| ohos.multimedia.camera | MetadataOutputError     | code: MetadataOutputErrorCode;                              | Added    |
+
+**Adaptation Guide**
+
+In addition to new APIs and deprecated APIs, you need to adapt your application to changed APIs.
+
+In Beta4 and later versions, the following APIs are changed.
+
+**New APIs**
+
+1. **Profile** API
+
+   Attribute 1: readonly format; type: CameraFormat
+
+   Attribute 2: readonly size; type: Size
+
+2. **FrameRateRange** API
+
+   Attribute 1: readonly min; type: number
+
+   Attribute 2: readonly max; type: number
+
+3. **VideoProfile** API (inherited from **Profile**)
+
+   Attribute: readonly frameRateRange; type: FrameRateRange
+
+4. **CameraOutputCapability** API
+
+   Attribute 1: readonly previewProfiles; type: Array<Profile>
+
+   Attribute 2: readonly photoProfiles; type: Array<Profile>
+
+   Attribute 3: readonly videoProfiles; type: Array<VideoProfile>
+
+   Attribute 4: readonly supportedMetadataObjectTypes; type: Array<MetadataObjectType>
+
+5. The following APIs are added to **CameraManager**:
+
+   getSupportedOutputCapability(camera: CameraDevice, callback: AsyncCallback<CameraOutputCapability>): void;
+
+   getSupportedOutputCapability(camera: CameraDevice): Promise<CameraOutputCapability>;
+
+   The code snippet is as follows:
+
+   ```
+   cameraManager.getSupportedCameras().then((cameras) => {
+       let cameraDevice = cameras[0];
+       cameraManager.getSupportedOutputCapability(cameraDevice, (err, CameraOutputCapability) => {
+           if (err) {
+               console.error(`Failed to get the outputCapability. ${err.message}`);
+               return;
+           }
+           console.log('Callback returned with an array of supported outputCapability');
+       })
+   })
+   ```
+
+   ```
+   cameraManager.getSupportedCameras().then((cameras) => {
+       let cameraDevice = cameras[0];
+       cameraManager.getSupportedOutputCapability(cameraDevice).then((cameraoutputcapability) => {
+           console.log('Promise returned with an array of supported outputCapability');
+       })
+   })
+   ```
+
+6. The **isCameraMuted(): boolean;** API is added to **CameraManager**.
+
+   The code snippet is as follows:
+
+   ```
+   let ismuted = cameraManager.isCameraMuted();
+   ```
+
+7. The **isCameraMuteSupported(): boolean;** API is added to **CameraManager**.
+
+   The code snippet is as follows:
+
+   ```
+   let ismutesuppotred = cameraManager.isCameraMuteSupported();
+   ```
+
+8. The **muteCamera(mute: boolean): void;** API is added to **CameraManager**.
+
+   The code snippet is as follows:
+
+   ```
+   let mute = true;
+   cameraManager.muteCamera(mute);
+   ```
+
+9. The **on(type: 'cameraMute', callback: AsyncCallback<boolean>): void;** API is added to **CameraManager**.
+
+   The code snippet is as follows:
+
+   ```
+   cameraManager.on('cameraMute', (err, curMuetd) => {
+       if (err) {
+           console.error(`Failed to get cameraMute callback. ${err.message}`);
+           return;
+       }
+   })
+   ```
+
+10. The **open(callback: AsyncCallback<void>): void;** and **open(): Promise<void>;** APIs are added to **CameraInput**.
+
+    The code snippet is as follows:
+
+    ```
+    cameraInput.open((err) => {
+        if (err) {
+            console.error(`Failed to open the camera. ${err.message}`);
+            return;
+        }
+        console.log('Callback returned with camera opened.');
+    })
+    ```
+
+    ```
+    cameraInput.open().then(() => {
+        console.log('Promise returned with camera opened.');
+    })
+    ```
+
+11. The **close(callback: AsyncCallback<void>): void;** and **close(): Promise<void>;** APIs are added to **CameraInput**.
+
+    The code snippet is as follows:
+
+    ```
+    cameraInput.close((err) => {
+        if (err) {
+            console.error(`Failed to close the cameras. ${err.message}`);
+            return;
+        }
+        console.log('Callback returned with camera closed.');
+    })
+    ```
+
+    ```
+    cameraInput.close().then(() => {
+        console.log('Promise returned with camera closed.');
+    })
+    ```
+
+12. The following enums are added to **CameraInputErrorCode**:
+
+    Enum: ERROR_NO_PERMISSION; value: 0
+
+    Enum: ERROR_DEVICE_PREEMPTED; value: 1
+
+    Enum: ERROR_DEVICE_DISCONNECTED; value: 2
+
+    Enum: ERROR_DEVICE_IN_USE; value: 3
+
+    Enum: ERROR_DRIVER_ERROR; value: 4
+
+13. The following enum is added to **CameraFormat**:
+
+    Enum: CAMERA_FORMAT_RGBA_8888; value: 3
+
+14. The **getMeteringPoint(callback: AsyncCallback<Point>): void;** and **getMeteringPoint(): Promise<Point>;** APIs are added to **CaptureSession**.
+
+    The code snippet is as follows:
+
+    ```
+    captureSession.getMeteringPoint((err, exposurePoint) => {
+        if (err) {
+            console.log(`Failed to get the current exposure point ${err.message}`);
+            return ;
+        }
+        console.log(`Callback returned with current exposure point: ${exposurePoint}`);
+    })
+    ```
+
+    ```
+    captureSession.getMeteringPoint().then((exposurePoint) => {
+        console.log(`Promise returned with current exposure point : ${exposurePoint}`);
+    })
+    ```
+
+15. The **setMeteringPoint(point: Point, callback: AsyncCallback<void>): void;** and **setMeteringPoint(point: Point): Promise<void>;** APIs are added to **CaptureSession**.
+
+    The code snippet is as follows:
+
+    ```
+    const Point1 = {x: 1, y: 1};
+    
+    captureSession.setMeteringPoint(Point1,(err) => {
+        if (err) {
+            console.log(`Failed to set the exposure point ${err.message}`);
+            return ;
+        }
+        console.log('Callback returned with the successful execution of setMeteringPoint');
+    })
+    ```
+
+    ```
+    const Point2 = {x: 2, y: 2};
+    
+    captureSession.setMeteringPoint(Point2).then(() => {
+        console.log('Promise returned with the successful execution of setMeteringPoint');
+    })
+    ```
+
+16. The following enums are added to **CaptureSessionErrorCode**:
+
+    Enum: ERROR_INSUFFICIENT_RESOURCES; value: 0
+
+    Enum: ERROR_TIMEOUT; value: 1
+
+17. The **CameraOutput** API is added and contains the **release(callback: AsyncCallback<void>): void;** and **release(): Promise<void>;** methods.
+
+    The sample code (for **previewOutput**) is as follows:
+
+    ```
+    previewOutput.release((err) => {
+        if (err) {
+            console.error(`Failed to release the PreviewOutput instance ${err.message}`);
+            return;
+        }
+        console.log('Callback invoked to indicate that the PreviewOutput instance is released successfully.');
+    });
+    ```
+
+    ```
+    previewOutput.release().then(() => {
+        console.log('Promise returned to indicate that the PreviewOutput instance is released successfully.');
+    })
+    ```
+
+18. The **start(callback: AsyncCallback<void>): void;** and **start(): Promise<void>;** APIs are added to **PreviewOutput**.
+
+    The code snippet is as follows:
+
+    ```
+    previewOutput.start((err) => {
+        if (err) {
+            console.error(`Failed to start the previewOutput. ${err.message}`);
+            return;
+        }
+        console.log('Callback returned with previewOutput started.');
+    })
+    ```
+
+    ```
+    previewOutput.start().then(() => {
+        console.log('Promise returned with previewOutput started.');
+    })
+    ```
+
+19. The **stop(callback: AsyncCallback<void>): void;** and **stop(): Promise<void>;** APIs are added to **PreviewOutput**.
+
+    The code snippet is as follows:
+
+    ```
+    previewOutput.stop((err) => {
+        if (err) {
+            console.error(`Failed to stop the previewOutput. ${err.message}`);
+            return;
+        }
+        console.log('Callback returned with previewOutput stopped.');
+    })
+    ```
+
+    ```
+    previewOutput.stop().then(() => {
+        console.log('Callback returned with previewOutput stopped.');
+    })
+    ```
+
+20. **PhotoCaptureSetting** API
+
+    Attribute 1: mirror?; type: boolean
+
+21. The following enums are added to **PhotoOutputErrorCode**:
+
+    Enum: ERROR_DRIVER_ERROR; value: 0
+
+    Enum: ERROR_INSUFFICIENT_RESOURCES; value: 1
+
+    Enum: ERROR_TIMEOUT; value: 2
+
+22. The following enum is added to **VideoOutputErrorCode**:
+
+    Enum: ERROR_DRIVER_ERROR; value: 0
+
+23. The **on(type: 'error', callback: ErrorCallback<MetadataOutputError>): void;** API is added to **MetadataOutput**.
+
+    The code snippet is as follows:
+
+    ```
+    metadataOutput.on('error', (metadataOutputError) => {
+        console.log(`Metadata output error code: ${metadataOutputError.code}`);
+    })
+    ```
+
+24. The following enums are added to **MetadataOutputErrorCode**.
+
+    Enum: ERROR_UNKNOWN; value: -1
+
+    Enum: ERROR_INSUFFICIENT_RESOURCES; value: 0
+
+25. **MetadataOutputError** API
+
+    Attribute: code; value: MetadataOutputErrorCode
+
+**Deprecated APIs**
+
+1. The **on(type: 'exposureStateChange', callback: AsyncCallback<ExposureState>): void;** API in **CameraInput** is deprecated.
+
+2. The **release(callback: AsyncCallback<void>): void;** and **release(): Promise<void>;** APIs in **previewOutput** are deprecated.
+
+3. The following APIs in **metadataOutput** are deprecated:
+
+   setCapturingMetadataObjectTypes(metadataObjectTypes: Array<MetadataObjectType>, callback: AsyncCallback<void>): void;<br>setCapturingMetadataObjectTypes(metadataObjectTypes: Array<MetadataObjectType>): Promise<void>;
+
+4. The following APIs in **metadataOutput** are deprecated:
+
+   getSupportedMetadataObjectTypes(callback: AsyncCallback<Array<MetadataObjectType>>): void;<br>getSupportedMetadataObjectTypes(): Promise<Array<MetadataObjectType>>;
+
+5. The **release(callback: AsyncCallback<void>): void;** and **release(): Promise<void>;** APIs in **PreviewOutput** are deprecated.
+
+6. The **release(callback: AsyncCallback<void>): void;** and **release(): Promise<void>;** APIs in **PhotoOutput** are deprecated.
+
+7. The **release(callback: AsyncCallback<void>): void;** and **release(): Promise<void>;** APIs in **VideoOutput** are deprecated.
+
+8. The **getCameraId(callback: AsyncCallback<string>): void;** and **getCameraId(): Promise<string>;** APIs in **CameraInput** are deprecated.
+
+9. The **getExposurePoint(callback: AsyncCallback<Point>): void;** and **getExposurePoint(): Promise<Point>;** APIs in **CameraInput** are deprecated.
+
+10. The **setExposurePoint(exposurePoint: Point, callback: AsyncCallback<void>): void;** and **setExposurePoint(exposurePoint: Point): Promise<void>;** APIs in **CameraInput** are deprecated.
+
+**Changed APIs**
+
+1. In **CameraManager**, the return value of **getCameras** is changed from **Array<Camera>** to **Array<CameraDevice>**, and the API name is changed from **getCameras** to **getSupportedCameras**. Therefore, the **getCameras(callback: AsyncCallback<Array<Camera>>): void;** and **getCameras(): Promise<Array<Camera>>;** APIs are changed to **getSupportedCameras(callback: AsyncCallback<Array<CameraDevice>>): void** and **getSupportedCameras(): Promise<Array<CameraDevice>>;**.
+
+   The code snippet is as follows:
+
+   ```
+   cameraManager.getSupportedCameras((err, cameras) => {
+       if (err) {
+           console.error(`Failed to get the cameras. ${err.message}`);
+           return;
+       }
+       console.log(`Callback returned with an array of supported cameras: ${cameras.length}`);
+   })
+   ```
+
+   ```
+   cameraManager.getSupportedCameras().then((cameras) => {
+       console.log(`Promise returned with an array of supported cameras: ${cameras.length}`);
+   })
+   ```
+
+2. In **CameraManager**, the input parameter of **createCameraInput** is changed from **cameraId: string** to **camera: CameraDevice**. Therefore, the **createCameraInput(cameraId: string, callback: AsyncCallback<CameraInput>): void;** and **createCameraInput(cameraId: string): Promise<CameraInput>;** APIs are changed to **createCameraInput(camera: CameraDevice, callback: AsyncCallback<CameraInput>): void;** and **createCameraInput(camera: CameraDevice): Promise<CameraInput>;**.
+
+   The code snippet is as follows:
+
+   ```
+   let cameraDevice = cameras[0];
+   cameraManager.createCameraInput(cameraDevice, (err, cameraInput) => {
+       if (err) {
+           console.error(`Failed to create the CameraInput instance. ${err.message}`);
+           return;
+       }
+       console.log('Callback returned with the CameraInput instance.');
+   })
+   ```
+
+   ```
+   let cameraDevice = cameras[0];
+   cameraManager.createCameraInput(cameraDevice).then((cameraInput) => {
+       console.log('Promise returned with the CameraInput instance');
+   })
+   ```
+
+3. In **CameraManager**, the input parameter **profile: Profile** is added to **createPreviewOutput** and the **profile** parameter is obtained by the **getSupportedOutputCapability** API. Therefore, the **createPreviewOutput(surfaceId: string, callback: AsyncCallback<PreviewOutput>): void;** and **createPreviewOutput(surfaceId: string): Promise<PreviewOutput>;** APIs are changed to **createPreviewOutput(profile: Profile, surfaceId: string, callback: AsyncCallback<PreviewOutput>): void;** and **createPreviewOutput(profile: Profile, surfaceId: string): Promise<PreviewOutput>;**.
+
+   The code snippet is as follows:
+
+   ```
+   let profile = cameraoutputcapability.previewProfiles[0];
+   cameraManager.createPreviewOutput(profile, surfaceId, (err, previewOutput) => {
+       if (err) {
+           console.error(`Failed to gcreate previewOutput. ${err.message}`);
+           return;
+       }
+       console.log('Callback returned with previewOutput created.');
+   })
+   ```
+
+   ```
+   let profile = cameraoutputcapability.previewProfiles[0];
+   cameraManager.createPreviewOutput(profile, surfaceId).then((previewOutput) => {
+       console.log('Promise returned with previewOutput created.');
+   })
+   ```
+
+4. In **CameraManager**, the input parameter **profile: Profile** is added to **createPhotoOutput** and the **profile** parameter is obtained by the **getSupportedOutputCapability** API. Therefore, the **CreatePhotoOutput(surfaceId: string, callback: AsyncCallback<PhotoOutput>): void;** and **CreatePhotoOutput(surfaceId: string): Promise<PhotoOutput>;** APIs are changed to **createPhotoOutput(profile: Profile, surfaceId: string, callback: AsyncCallback<PhotoOutput>): void;** and **createPhotoOutput(profile: Profile, surfaceId: string): Promise<PhotoOutput>;**.
+
+   The code snippet is as follows:
+
+   ```
+   let profile = cameraoutputcapability.photoProfiles[0];
+   cameraManager.createPhotoOutput(profile, surfaceId, (err, photoOutput) => {
+       if (err) {
+           console.error(`Failed to create photoOutput. ${err.message}`);
+           return;
+       }
+       console.log('Callback returned with photoOutput created.');
+   })
+   ```
+
+   ```
+   let profile = cameraoutputcapability.photoProfiles[0];
+   cameraManager.createPhotoOutput(profile, surfaceId).then((photoOutput) => {
+       console.log('Promise returned with photoOutput created.');
+   })
+   ```
+
+5. In **CameraManager**, the input parameter **profile: Profile** is added to **createVideoOutput** and the **profile** parameter is obtained by the **getSupportedOutputCapability** API. Therefore, the **createVideoOutput(surfaceId: string, callback: AsyncCallback<VideoOutput>): void;** and **createVideoOutput(surfaceId: string): Promise<VideoOutput>;** APIs are changed to **createVideoOutput(profile: VideoProfile, surfaceId: string, callback: AsyncCallback<VideoOutput>): void;** and **createVideoOutput(profile: VideoProfile, surfaceId: string): Promise<VideoOutput>;**.
+
+   The code snippet is as follows:
+
+   ```
+   let profile = cameraoutputcapability.videoProfiles[0];
+   cameraManager.createVideoOutput(profile, surfaceId, (err, videoOutput) => {
+       if (err) {
+           console.error(`Failed to create videoOutput. ${err.message}`);
+           return;
+       }
+       console.log('Callback returned with an array of supported outputCapability' );
+   })
+   ```
+
+   ```
+   let profile = cameraoutputcapability.videoProfiles[0];
+   cameraManager.createVideoOutput(profile, surfaceId).then((videoOutput) => {
+       console.log('Promise returned with videoOutput created.');
+   })
+   ```
+
+6. In **CameraManager**, the input parameter **metadataObjectTypes: Array<MetadataObjectType>** is added to **createMetadataOutput**, and the **metadataObjectTypes** parameter is obtained by the **getSupportedOutputCapability** API. Therefore, the **function createMetadataOutput(callback: AsyncCallback<MetadataOutput>): void;** and **function createMetadataOutput(): Promise<MetadataOutput>;** APIs are changed to **createMetadataOutput(metadataObjectTypes: Array<MetadataObjectType>, callback: AsyncCallback<MetadataOutput>): void;** and **createMetadataOutput(metadataObjectTypes: Array<MetadataObjectType>): Promise<MetadataOutput>;**.
+
+   The code snippet is as follows:
+
+   ```
+   let metadataObjectTypes = cameraoutputcapability.supportedMetadataObjectTypes;
+   cameraManager.createMetadataOutput(metadataObjectTypes, (err, metadataOutput) => {
+       if (err) {
+           console.error(`Failed to create metadataOutput. ${err.message}`);
+           return;
+       }
+       console.log('Callback returned with metadataOutput created.');
+   })
+   ```
+
+   ```
+   let metadataObjectTypes = cameraoutputcapability.supportedMetadataObjectTypes;
+   cameraManager.createMetadataOutput(metadataObjectTypes).then((metadataOutput) => {
+       console.log('Promise returned with metadataOutput created.');
+   })
+   ```
+   
+7. In **CameraManager**, **createCaptureSession** does not need to consider the context attribute. Therefore, the **createCaptureSession(context: Context, callback: AsyncCallback<CaptureSession>): void;** and **createCaptureSession(context: Context): Promise<CaptureSession>;** APIs are changed to **createCaptureSession(callback: AsyncCallback<CaptureSession>): void;** and **createCaptureSession(): Promise<CaptureSession>;**.
+
+   The code snippet is as follows:
+
+   ```typescript
+   cameraManager.createCaptureSession((err, captureSession) => {
+       if (err) {
+           console.error(`Failed to create captureSession. ${err.message}`);
+           return;
+       }
+       console.log('Callback returned with captureSession created.');
+   })
+   ```
+
+   ```
+   cameraManager.createCaptureSession().then((captureSession) => {
+       console.log('Promise returned with captureSession created.');
+   })
+   ```
+
+8. The type of the **camera** attribute of the **CameraStatusInfo** API is changed from **Camera** to **CameraDevice**.
+
+9. In **CameraInput**, the input parameter **camera: CameraDevice** is added to the **on(type: 'error')** API. Therefore, the **on(type: 'error', callback: ErrorCallback<CameraInputError>): void;** API is changed to **on(type: 'error', camera: CameraDevice, callback: ErrorCallback<CameraInputError>): void;**.
+
+   The code snippet is as follows:
+
+   ```
+   let cameraDevice = cameras[0];
+   cameraInput.on('error', cameraDevice, (cameraInputError) => {
+       console.log(`Camera input error code: ${cameraInputError.code}`);
+   })
+   ```
+	
+10. The following APIs are moved from **CameraInput** to **CaptureSession**:
+
+    hasFlash(callback: AsyncCallback<boolean>): void;<br>hasFlash(): Promise<boolean>;<br>
+
+    isFlashModeSupported(flashMode: FlashMode, callback: AsyncCallback<boolean>): void;<br>isFlashModeSupported(flashMode: FlashMode): Promise<boolean>;<br>
+
+    getFlashMode(callback: AsyncCallback<FlashMode>): void;<br>getFlashMode(): Promise<FlashMode>;<br>
+
+    setFlashMode(flashMode: FlashMode, callback: AsyncCallback<void>): void;<br>setFlashMode(flashMode: FlashMode): Promise<void>;<br>
+
+    isExposureModeSupported(aeMode: ExposureMode, callback: AsyncCallback<boolean>): void;<br>isExposureModeSupported(aeMode: ExposureMode): Promise<boolean>;<br>
+
+    getExposureMode(callback: AsyncCallback<ExposureMode>): void;<br>getExposureMode(): Promise<ExposureMode>;<br>
+
+    setExposureMode(aeMode: ExposureMode, callback: AsyncCallback<void>): void;<br>setExposureMode(aeMode: ExposureMode): Promise<void>;<br>
+
+    getMeteringPoint(callback: AsyncCallback<Point>): void;<br>getMeteringPoint(): Promise<Point>;<br>
+
+    setMeteringPoint(point: Point, callback: AsyncCallback<void>): void;<br>setMeteringPoint(point: Point): Promise<void>;<br>
+
+    getExposureBiasRange(callback: AsyncCallback<Array<number>>): void;<br>getExposureBiasRange(): Promise<Array<number>>;<br>
+
+    setExposureBias(exposureBias: number, callback: AsyncCallback<void>): void;<br>setExposureBias(exposureBias: number): Promise<void>;<br>
+
+    getExposureValue(callback: AsyncCallback<number>): void;<br>getExposureValue(): Promise<number>;<br>
+
+    isFocusModeSupported(afMode: FocusMode, callback: AsyncCallback<boolean>): void;<br>isFocusModeSupported(afMode: FocusMode): Promise<boolean>;<br>
+
+    getFocusMode(callback: AsyncCallback<FocusMode>): void;<br>getFocusMode(): Promise<FocusMode>;<br>
+
+    setFocusMode(afMode: FocusMode, callback: AsyncCallback<void>): void;<br>setFocusMode(afMode: FocusMode): Promise<void>;<br>
+
+    setFocusPoint(point: Point, callback: AsyncCallback<void>): void;<br>setFocusPoint(point: Point): Promise<void>;<br>
+
+    getFocusPoint(callback: AsyncCallback<Point>): void;<br>getFocusPoint(): Promise<Point>;<br>
+
+    getFocalLength(callback: AsyncCallback<number>): void;<br>getFocalLength(): Promise<number>;<br>
+
+    getZoomRatioRange(callback: AsyncCallback<Array<number>>): void;<br>getZoomRatioRange(): Promise<Array<number>>;<br>
+
+    getZoomRatio(callback: AsyncCallback<number>): void;<br>getZoomRatio(): Promise<number>;<br>
+
+    setZoomRatio(zoomRatio: number, callback: AsyncCallback<void>): void;<br>setZoomRatio(zoomRatio: number): Promise<void>;
+	
+11. The **on(type: 'focusStateChange', callback: AsyncCallback<FocusState>): void;** API is moved from **CameraInput** to **CaptureSession**.
+
+    The code snippet is as follows:
+
+    ```
+    captureSession.on('focusStateChange', (focusState) => {
+        console.log(`Focus state  : ${focusState}`);
+    })
+    ```
+
+12. The following enums are added to **ExposureMode**:
+
+    Enum: EXPOSURE_MODE_AUTO; initial value: changed from the default value to **1**
+
+    Enum: EXPOSURE_MODE_CONTINUOUS_AUTO; initial value: changed from the default value to **2**
+
+13. The following enums are added to **VideoStabilizationMode**:
+
+    Enum: LOW; initial value: changed from the default value to **1**
+
+    Enum: MIDDLE; initial value: changed from the default value to **2**
+
+    Enum: HIGH; initial value: changed from the default value to **3**
+
+    Enum: AUTO; initial value: changed from the default value to **4**
+
+14. In **CaptureSession**, the parameter of the **addOutput** API is changed from the original child class type (**PreviewOutput**, **PhotoOutput**, **VideoOutput**, and **MetadataOutput**) to the base class type (**CameraOutput**). After the change, the number of APIs is reduced from 8 to 2.
+
+    APIs before change:
+
+    addOutput(previewOutput: PreviewOutput, callback: AsyncCallback<void>): void;<br>addOutput(previewOutput: PreviewOutput): Promise<void>;<br>addOutput(photoOutput: PhotoOutput, callback: AsyncCallback<void>): void;<br>addOutput(photoOutput: PhotoOutput): Promise<void>;<br>addOutput(videoOutput: VideoOutput, callback: AsyncCallback<void>): void;<br>addOutput(videoOutput: VideoOutput): Promise<void>;<br>addOutput(metadataOutput: MetadataOutput, callback: AsyncCallback<void>): void;<br>addOutput(metadataOutput: MetadataOutput): Promise<void>;
+
+    APIs after change:
+
+    addOutput(cameraOutput: CameraOutput, callback: AsyncCallback<void>): void;<br>addOutput(cameraOutput: CameraOutput): Promise<void>;
+
+    The sample code (for **previewOutput**) is as follows:
+
+    ```
+    captureSession.addOutput(previewOutput, (err) => {
+        if (err) {
+            console.error(`Failed to add output. ${err.message}`);
+            return;
+        }
+        console.log('Callback returned with output added.');
+    })
+    ```
+
+    ```
+    captureSession.addOutput(previewOutput).then(() => {
+        console.log('Promise returned with cameraOutput added.');
+    })
+    ```
+
+15. In **CaptureSession**, the parameter of the **removeOutput** API is changed from the original child class type (**PreviewOutput**, **PhotoOutput**, **VideoOutput**, and **MetadataOutput**) to the base class type (**CameraOutput**). After the change, the number of APIs is reduced from 8 to 2.
+
+    APIs before change:
+
+    removeOutput(previewOutput: PreviewOutput, callback: AsyncCallback<void>): void;<br>removeOutput(previewOutput: PreviewOutput): Promise<void>;<br>removeOutput(photoOutput: PhotoOutput, callback: AsyncCallback<void>): void;<br>removeOutput(photoOutput: PhotoOutput): Promise<void>;<br>removeOutput(videoOutput: VideoOutput, callback: AsyncCallback<void>): void;<br>removeOutput(videoOutput: VideoOutput): Promise<void>;<br>removeOutput(metadataOutput: MetadataOutput, callback: AsyncCallback<void>): void;<br>removeOutput(metadataOutput: MetadataOutput): Promise<void>;
+
+    APIs after change:
+
+    removeOutput(cameraOutput: CameraOutput, callback: AsyncCallback<void>): void;<br>removeOutput(cameraOutput: CameraOutput): Promise<void>;
+
+    The sample code (for **previewOutput**) is as follows:
+
+    ```
+    captureSession.removeOutput(previewOutput, (err) => {
+        if (err) {
+            console.error(`Failed to remove the CameraOutput instance. ${err.message}`);
+            return;
+        }
+        console.log('Callback invoked to indicate that the CameraOutput instance is removed.');
+    });
+    ```
+
+    ```
+    captureSession.removeOutput(previewOutput).then(() => {
+        console.log('Promise returned to indicate that the CameraOutput instance is removed.');
+    })
+    ```
+
+16. The following enum in **MetadataObjectType** is changed:
+
+    The enum value name is changed from **FACE** to **FACE_DETECTION**.
+
+17. The name of the **Camera** API is changed to **CameraDevice**.
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-device-manager.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-device-manager.md
new file mode 100644
index 0000000000000000000000000000000000000000..c9f8f116a957e4955a49a029605022c6ab9ce601
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-device-manager.md
@@ -0,0 +1,106 @@
+# Device Manager ChangeLog
+
+## cl.device_manager.1 Error Information Return Method Change of APIs
+
+The device manager API uses service logic return values to indicate the error information, which does not comply with the API error code specifications of OpenHarmony. The following changes are made in API version 9 and later:
+
+Asynchronous API: An error message is returned via **AsyncCallback** or the **error** object of **Promise**.
+
+Synchronous API: An error message is returned via an exception.
+
+**Change Impact**
+
+The application developed based on earlier versions needs to adapt the method for returning API error information. Otherwise, the original service logic will be affected.
+
+**Key API/Component Changes**
+
+Error code processing is added for the following APIs:
+  - createDeviceManager(bundleName: string, callback: AsyncCallback&lt;DeviceManager&gt;): void;
+  - release(): void;
+  - getTrustedDeviceListSync(): Array&lt;DeviceInfo&gt;
+  - getTrustedDeviceList(callback:AsyncCallback&lt;Array&lt;DeviceInfo&gt;&gt;): void;
+  - getTrustedDeviceList(): Promise&lt;Array&lt;DeviceInfo&gt;&gt;
+  - getLocalDeviceInfoSync(): DeviceInfo;
+  - getLocalDeviceInfo(callback:AsyncCallback&lt;DeviceInfo&gt;): void;
+  - getLocalDeviceInfo(): Promise&lt;DeviceInfo&gt;
+  - startDeviceDiscovery(subscribeInfo: SubscribeInfo): void;
+  - startDeviceDiscovery(subscribeInfo: SubscribeInfo, filterOptions?: string): void;
+  - stopDeviceDiscovery(subscribeId: number): void;
+  - publishDeviceDiscovery(publishInfo: PublishInfo): void;
+  - unPublishDeviceDiscovery(publishId: number): void;
+  - authenticateDevice(deviceInfo: DeviceInfo, authParam: AuthParam, callback: AsyncCallback&lt;{deviceId: string, pinToken ?: number}&gt;): void;
+  - unAuthenticateDevice(deviceInfo: DeviceInfo): void;
+  - verifyAuthInfo(authInfo: AuthInfo, callback: AsyncCallback&lt;{deviceId: string, level: number}&gt;): void;
+  - setUserOperation(operateAction: number, params: string): void;
+  - on(type: 'uiStateChange', callback: Callback&lt;{ param: string}&gt;): void;
+  - off(type: 'uiStateChange', callback?: Callback&lt;{ param: string}&gt;): void;
+  - on(type: 'deviceStateChange',  callback: Callback&lt;{ action: DeviceStateChangeAction, device: DeviceInfo }&gt;): void;
+  - off(type: 'deviceStateChange', callback?: Callback&lt;{ action: DeviceStateChangeAction, device: DeviceInfo }&gt;): void;
+  - on(type: 'deviceFound', callback: Callback&lt;{ subscribeId: number, device: DeviceInfo }&gt;): void;
+  - off(type: 'deviceFound', callback?: Callback&lt;{ subscribeId: number, device: DeviceInfo }&gt;): void;
+  - on(type: 'discoverFail', callback: Callback&lt;{ subscribeId: number, reason: number }&gt;): void;
+  - off(type: 'discoverFail', callback?: Callback&lt;{ subscribeId: number, reason: number }&gt;): void;
+  - on(type: 'publishSuccess', callback: Callback&lt;{ publishId: number }&gt;): void;
+  - off(type: 'publishSuccess', callback?: Callback&lt;{ publishId: number }&gt;): void;
+  - on(type: 'publishFail', callback: Callback&lt;{ publishId: number, reason: number }&gt;): void;
+  - off(type: 'publishFail', callback?: Callback&lt;{ publishId: number, reason: number }&gt;): void;
+  - on(type: 'serviceDie', callback: () =&gt; void): void;
+  - off(type: 'serviceDie', callback?: () =&gt; void): void;
+
+**Adaptation Guide**
+
+The following uses **getTrustedDeviceList** as an example for asynchronous APIs:
+
+```ts
+import account_osAccount from "@ohos.distributedHardware.deviceManager"
+dmInstance.getTrustedDeviceList((err, data) => {
+    console.log("getTrustedDeviceList err: " + JSON.stringify(err));
+    console.log('get trusted device info: ' + JSON.stringify(data));
+});
+
+try {
+  dmInstance.getTrustedDeviceList((err, data) => {
+    if (err) {
+      console.error("getTrustedDeviceList errCode:" + err.code + ",errMessage:" + err.message);
+      return;
+    }
+    console.log('get trusted device info: ' + JSON.stringify(data));
+  });
+} catch (err) {
+  console.error("getTrustedDeviceList errCode:" + err.code + ",errMessage:" + err.message);
+}
+```
+
+The following uses **startDeviceDiscovery** as an example for synchronous APIs:
+
+```ts
+// Automatically generate a unique subscription ID.
+var subscribeId = Math.floor(Math.random() * 10000 + 1000);
+var subscribeInfo = {
+    "subscribeId": subscribeId,
+    "mode": 0xAA, // Active discovery
+    "medium": 0,  // Automatic. Multiple media can be used for device discovery.
+    "freq": 2,    // High frequency
+    "isSameAccount": false,
+    "isWakeRemote": false,
+    "capability": 1
+};
+dmInstance.startDeviceDiscovery(subscribeInfo); // The deviceFound callback is called to notify the application when a device is discovered.
+
+// Automatically generate a unique subscription ID.
+var subscribeId = Math.floor(Math.random() * 10000 + 1000);
+var subscribeInfo = {
+    "subscribeId": subscribeId,
+    "mode": 0xAA, // Active discovery
+    "medium": 0,  // Automatic. Multiple media can be used for device discovery.
+    "freq": 2,    // High frequency
+    "isSameAccount": false,
+    "isWakeRemote": false,
+    "capability": 1
+};
+try {
+  dmInstance.startDeviceDiscovery(subscribeInfo); // The deviceFound callback is called to notify the application when a device is discovered.
+} catch (err) {
+  console.error("startDeviceDiscovery errCode:" + err.code + ",errMessage:" + err.message);
+}
+```
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-dmsfwk.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-dmsfwk.md
new file mode 100644
index 0000000000000000000000000000000000000000..07b84171f802077dd2df61daca34fef744fcafaa
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-dmsfwk.md
@@ -0,0 +1,122 @@
+# Distributed Scheduler Subsystem Changelog
+
+## cl.DistributedManagerService.1 continuationManager on()/off() Changes
+
+- The event types passed to the **continuationManager.on** and **continuationManager.off** APIs do not comply with the OpenHarmony API specifications.
+- The return value of **continuationManager.on** varies with the event type, which does not comply with the OpenHarmony API specifications.
+
+The following changes have been made:
+
+- Changed the event type **deviceConnect** to **deviceSelected** and **deviceDisconnect** to **deviceUnselected** in the **continuationManager.on** and **continuationManager.off** APIs.
+- Changed the return value of **continuationManager.on** to **Callback&lt;Array&lt;ContinuationResult&gt;&gt;** for all events.
+
+**Change Impact**
+
+The application developed based on earlier versions needs to be adapted. Otherwise, the service logic will be affected.
+
+**Key API/Component Changes**
+
+- Involved APIs:
+
+  continuationManager.on;
+  continuationManager.off;
+
+- Before change:
+
+```js
+  function on(type: "deviceConnect", token: number, callback: Callback<Array<ContinuationResult>>): void;
+  function off(type: "deviceConnect", token: number): void;
+  function on(type: "deviceDisconnect", token: number, callback: Callback<Array<string>>): void;
+  function off(type: "deviceDisconnect", token: number): void;
+```
+
+- After change:
+
+```js
+  function on(type: "deviceSelected", token: number, callback: Callback<Array<ContinuationResult>>): void;
+  function off(type: "deviceSelected", token: number): void;
+  function on(type: "deviceUnselected", token: number, callback: Callback<Array<ContinuationResult>>): void;
+  function off(type: "deviceUnselected", token: number): void;
+```
+
+**Adaptation Guide**
+Change the event names. The code snippet is as follows:
+
+Event of device selection in **continuationManager.on**:
+
+```ts
+  let token = 1;
+  try {
+    continuationManager.on("deviceSelected", token, (data) => {
+      console.info('onDeviceSelected len: ' + data.length);
+      for (let i = 0; i < data.length; i++) {
+        console.info('onDeviceSelected deviceId: ' + JSON.stringify(data[i].id));
+        console.info('onDeviceSelected deviceType: ' + JSON.stringify(data[i].type));
+        console.info('onDeviceSelected deviceName: ' + JSON.stringify(data[i].name));
+      }
+    });
+  } catch (err) {
+    console.error('on failed, cause: ' + JSON.stringify(err));
+  }
+```
+
+Event of device selection in **continuationManager.off**:
+
+```ts
+  let token = 1;
+  try {
+    continuationManager.off("deviceSelected", token);
+  } catch (err) {
+    console.error('off failed, cause: ' + JSON.stringify(err));
+  }
+```
+
+Event of device deselection in **continuationManager.on**:
+
+```ts
+  let token = 1;
+  try {
+    continuationManager.on("deviceUnselected", token, (data) => {
+      console.info('onDeviceUnselected len: ' + data.length);
+      for (let i = 0; i < data.length; i++) {
+        console.info('onDeviceUnselected deviceId: ' + JSON.stringify(data[i].id));
+        console.info('onDeviceUnselected deviceType: ' + JSON.stringify(data[i].type));
+        console.info('onDeviceUnselected deviceName: ' + JSON.stringify(data[i].name));
+      }
+      console.info('onDeviceUnselected finished.');
+    });
+  } catch (err) {
+    console.error('on failed, cause: ' + JSON.stringify(err));
+  }
+```
+
+Event of device deselection in **continuationManager.off**:
+
+```ts
+  let token = 1;
+  try {
+    continuationManager.off("deviceUnselected", token);
+  } catch (err) {
+    console.error('off failed, cause: ' + JSON.stringify(err));
+  }
+```
+
+## cl.DistributedManagerService.2 Adding DATASYNC Permission Verification to continuationManager APIs
+
+In earlier versions, the **continuationManager** APIs do not verify the caller, which does not comply with the OpenHarmony API specifications.
+Now, before using a **continuationManager** API, the caller must apply for the **ohos.permission.DISTRIBUTED_DATASYNC** permission.
+
+**Change Impact**
+
+The application developed based on earlier versions needs to apply for the **ohos.permission.DISTRIBUTED_DATASYNC** permission in advance. Otherwise, the service logic will be affected.
+
+**Key API/Component Changes**
+
+Involved APIs:
+
+  - continuationManager.registerContinuation;
+  - continuationManager.on;
+  - continuationManager.off;
+  - continuationManager.unregisterContinuation;
+  - continuationManager.updateContinuationState;
+  - continuationManager.startContinuationDeviceManager;
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-enterprise_device_management.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-enterprise_device_management.md
new file mode 100644
index 0000000000000000000000000000000000000000..dd8eb99aa48bbc0ab5ea2b83e51233a41320b03e
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-enterprise_device_management.md
@@ -0,0 +1,157 @@
+# Customization Subsystem ChangeLog
+
+## cl.Customization.1 Change of the Enterprise Device Management Module Name
+
+Changed **@ohos.enterpriseDeviceManager.d.ts** to **@ohos.enterprise.adminManager.d.ts**.
+
+**Change Impact**
+
+The application developed based on OpenHarmony earlier than 3.2.8.3 must be adapted so that it can be properly compiled in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Original API                            | New API                             |
+| ---------------------------------  | ---------------------------------- |
+| @ohos.enterpriseDeviceManager.d.ts  | @ohos.enterprise.adminManager.d.ts |
+
+**Adaptation Guide**
+
+The original APIs are only moved to the new namespace. Therefore, you can modify **import** to solve the adaptation problem.
+
+If the original API uses **@ohos.enterpriseDeviceManager**:
+
+```js
+import enterpriseDeviceManager from '@ohos.enterpriseDeviceManager';
+```
+
+You can modify **import** to switch to the new namespace:
+
+```js
+import enterpriseDeviceManager from '@ohos.enterprise.adminManager';
+```
+
+## cl.Customization.2 enterpriseDeviceManager/DeviceSettingsManager.d.ts Module Change
+
+Changed **enterpriseDeviceManager/DeviceSettingsManager.d.ts** to **ohos.enterprise.dateTimeManager.d.ts**.
+
+**Change Impact**
+
+The application developed based on OpenHarmony earlier than 3.2.8.3 must be adapted so that it can be properly compiled in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Original API               | Original API Type            | New API             | New API Type               |
+| ---------------------------------  | --------- |  ---------------------------------- | ----- |
+| enterpriseDeviceManager/DeviceSettingsManager.d.ts | interface | @ohos.enterprise.dateTimeManager.d.ts | namespace |
+
+**Adaptation Guide**
+
+If the **setDateTime** API of **enterpriseDeviceManager/DeviceSettingsManager.d.ts** is used:
+
+```js
+import enterpriseDeviceManager from '@ohos.enterpriseDeviceManager'
+
+let wantTemp = {
+    bundleName: "bundleName",
+    abilityName: "abilityName",
+};
+enterpriseDeviceManager.getDeviceSettingsManager((error, mgr) => {
+    if (error) {
+        console.log("error code:" + error.code + " error message:" + error.message);
+        return;
+    }
+    mgr.setDateTime(wantTemp, 1526003846000, (error) => {
+        if (error) {
+            console.log("error code:" + error.code + " error message:" + error.message);
+        }
+    });
+});
+```
+
+You need to import the new namespace for adaptation:
+
+```js
+import dateTimeManager from '@ohos.enterprise.dateTimeManager'
+
+let wantTemp = {
+    bundleName: "bundleName",
+    abilityName: "abilityName",
+};
+dateTimeManager.setDateTime(wantTemp, 1526003846000, (error) => {
+    if (error) {
+        console.log("error code:" + error.code + " error message:" + error.message);
+    }
+})
+```
+
+## cl.Customization.3 System API Change
+
+Changed all enterprise device management APIs to system APIs.
+
+**Change Impact**
+
+All APIs can be called only by system applications.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enum/Constant                                         | Change Type|
+| ------------------------- | ------------------- | ------------------------------------------------------------ | -------- |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, userId: number, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, userId?: number): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, userId: number, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, userId?: number): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableSuperAdmin(bundleName: String, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableSuperAdmin(bundleName: String): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** isAdminEnabled(admin: Want, callback: AsyncCallback<**boolean**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** isAdminEnabled(admin: Want, userId: number, callback: AsyncCallback<**boolean**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** isAdminEnabled(admin: Want, userId?: number): Promise<**boolean**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** getEnterpriseInfo(admin: Want, callback: AsyncCallback<**EnterpriseInfo**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** getEnterpriseInfo(admin: Want): Promise<**EnterpriseInfo**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** setEnterpriseInfo(admin: Want, enterpriseInfo: EnterpriseInfo, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** setEnterpriseInfo(admin: Want, enterpriseInfo: EnterpriseInfo): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** isSuperAdmin(bundleName: String, callback: AsyncCallback<**boolean**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** isSuperAdmin(bundleName: String): Promise<**boolean**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** subscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** subscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** unsubscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** unsubscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>): Promise<**void**>; | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **interface** EnterpriseInfo | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **enum** AdminType | systemapi     |
+| @ohos.enterprise.adminManager        | adminManager        | **enum** ManagedEvent | systemapi     |
+| @ohos.enterprise.dataTimeManager        | dateTimeManager        | **function** setDateTime(admin: Want, time: number, callback: AsyncCallback<**void**>): void; | systemapi     |
+| @ohos.enterprise.dataTimeManager        | dateTimeManager        | **function** setDateTime(admin: Want, time: number): Promise<**void**>; | systemapi     |
+
+## cl.Customization.4 API Permission Change
+
+Added permission verification for some APIs.
+
+**Change Impact**
+
+The application developed based on OpenHarmony earlier than 3.2.8.3 must have the corresponding permission so that it can properly call these APIs.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enum/Constant                                         | New Permission|
+| ------------------------- | ------------------- | ------------------------------------------------------------ | -------- |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, callback: AsyncCallback<**void**>): void; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, userId: number, callback: AsyncCallback<**void**>): void; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** enableAdmin(admin: Want, enterpriseInfo: EnterpriseInfo, type: AdminType, userId?: number): Promise<**void**>; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, callback: AsyncCallback<**void**>): void; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, userId: number, callback: AsyncCallback<**void**>): void; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableAdmin(admin: Want, userId?: number): Promise<**void**>; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableSuperAdmin(bundleName: String, callback: AsyncCallback<**void**>): void; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** disableSuperAdmin(bundleName: String): Promise<**void**>; | ohos.permission.MANAGE_ENTERPRISE_DEVICE_ADMIN     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** setEnterpriseInfo(admin: Want, enterpriseInfo: EnterpriseInfo, callback: AsyncCallback<**void**>): void; | ohos.permission.SET_ENTERPRISE_INFO     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** setEnterpriseInfo(admin: Want, enterpriseInfo: EnterpriseInfo): Promise<**void**>; | ohos.permission.SET_ENTERPRISE_INFO     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** subscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>, callback: AsyncCallback<**void**>): void; | ohos.permission.ENTERPRISE_SUBSCRIBE_MANAGED_EVENT     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** subscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>): Promise<**void**>; | ohos.permission.ENTERPRISE_SUBSCRIBE_MANAGED_EVENT     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** unsubscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>, callback: AsyncCallback<**void**>): void; | ohos.permission.ENTERPRISE_SUBSCRIBE_MANAGED_EVENT     |
+| @ohos.enterprise.adminManager        | adminManager        | **function** unsubscribeManagedEvent(admin: Want, managedEvents: Array<**ManagedEvent**>): Promise<**void**>; | ohos.permission.ENTERPRISE_SUBSCRIBE_MANAGED_EVENT     |
+| @ohos.enterprise.dataTimeManager        | dateTimeManager        | **function** setDateTime(admin: Want, time: number, callback: AsyncCallback<**void**>): void; | ohos.permission.ENTERPRISE_SET_DATETIME     |
+| @ohos.enterprise.dataTimeManager        | dateTimeManager        | **function** setDateTime(admin: Want, time: number): Promise<**void**>; | ohos.permission.ENTERPRISE_SET_DATETIME     |
+
+**Adaptation Guide**
+
+Apply for the corresponding permission to call these APIs properly.
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-inputmethod-framworks.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-inputmethod-framworks.md
new file mode 100644
index 0000000000000000000000000000000000000000..be4a459e4070a68f50a6b68ea019167c70897e02
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-inputmethod-framworks.md
@@ -0,0 +1,242 @@
+# Input Method Framework ChangeLog
+
+## cl.inputmethod_frameworks.1 API Error Information Return Method Change
+
+The internal APIs of the following modules used service logic return values to indicate error information, which did not comply with the error code specifications of OpenHarmony. Therefore, they are modified in API version 9 and later.
+
+ - Input method framework module: system API, @ohos.inputmethod.d.ts
+
+ - Input method service module: system API, @ohos.inputmethodengine.d.ts
+
+ - Input method ExtentionAbility module: system API, @ohos.inputmethodextensionability.d.ts
+
+ - Input method ExtentionContext module: system API, @ohos.inputmethodextensioncontext.d.ts
+
+ - Input method subtype module: system API, @ohos.inputMethodSubtype.d.ts
+
+Asynchronous API: An error message is returned via **AsyncCallback** or the **error** object of **Promise**.
+
+Synchronous API: An error message is returned via an exception.
+
+**Change Impact**
+
+The application developed based on earlier versions needs to adapt the method for returning API error information. Otherwise, the original service logic will be affected.
+
+**Key API/Component Changes**
+
+Error code processing is added for the following APIs:
+  - getSetting(): InputMethodSetting;
+
+  - getController(): InputMethodController;
+
+  - switchInputMethod(target: InputMethodProperty, callback: AsyncCallback\<boolean>): void;
+
+  - switchInputMethod(target: InputMethodProperty): Promise\<boolean>;
+
+  - switchCurrentInputMethodSubtype(target: InputMethodSubtype, callback: AsyncCallback\<boolean>): void;
+
+  - switchCurrentInputMethodSubtype(target: InputMethodSubtype): Promise\<boolean>;
+
+  - switchCurrentInputMethodAndSubtype(inputMethodProperty: InputMethodProperty, inputMethodSubtype: InputMethodSubtype, callback: AsyncCallback\<boolean>): void;
+
+  - switchCurrentInputMethodAndSubtype(inputMethodProperty: InputMethodProperty, inputMethodSubtype: InputMethodSubtype): Promise\<boolean>;
+
+  - listInputMethodSubtype(inputMethodProperty: InputMethodProperty, callback: AsyncCallback<Array\<InputMethodSubtype>>): void;
+
+  - listInputMethodSubtype(inputMethodProperty: InputMethodProperty): Promise<Array\<InputMethodSubtype>>;
+
+  - listCurrentInputMethodSubtype(callback: AsyncCallback<Array\<InputMethodSubtype>>): void;
+
+  - listCurrentInputMethodSubtype(): Promise<Array\<InputMethodSubtype>>;
+
+  - getInputMethods(enable: boolean, callback: AsyncCallback<Array\<InputMethodProperty>>): void;
+
+  - getInputMethods(enable: boolean): Promise<Array\<InputMethodProperty>>;
+
+  - showOptionalInputMethods(callback: AsyncCallback\<boolean>): void;
+
+  - showOptionalInputMethods(): Promise\<boolean>;
+
+  - stopInputSession(callback: AsyncCallback\<boolean>): void;
+
+  - stopInputSession(): Promise\<boolean>;
+
+  - showSoftKeyboard(callback: AsyncCallback\<void>): void;
+
+  - showSoftKeyboard():Promise\<void>;
+
+  - hideSoftKeyboard(callback: AsyncCallback\<void>): void;
+
+  - hideSoftKeyboard():Promise\<void>;
+
+  - hide(callback: AsyncCallback\<void>): void;
+
+  - hide(): Promise\<void>;
+
+  - onCreate(want: Want): void;
+
+  - onDestroy(): void;
+    
+
+  - In **InputClient**: 
+
+    - sendKeyFunction(action: number, callback: AsyncCallback\<boolean>): void;
+
+    - sendKeyFunction(action: number): Promise\<boolean>;
+
+    - deleteForward(length: number, callback: AsyncCallback\<boolean>): void;
+
+    - deleteForward(length: number): Promise\<boolean>;
+
+    - deleteBackward(length: number, callback: AsyncCallback\<boolean>): void;
+
+    - deleteBackward(length: number): Promise\<boolean>;
+
+    - insertText(text: string, callback: AsyncCallback\<boolean>): void;
+
+    - insertText(text: string): Promise\<boolean>;
+
+    - getForward(length: number, callback: AsyncCallback\<string>): void;
+
+    - getForward(length: number): Promise\<string>;
+
+    - getBackward(length: number, callback: AsyncCallback\<string>): void;
+
+    - getBackward(length: number): Promise\<string>;
+
+    - getEditorAttribute(callback: AsyncCallback\<EditorAttribute>): void;
+
+    - getEditorAttribute(): Promise\EditorAttribute>;
+
+    - moveCursor(direction: number, callback: AsyncCallback\<void>): void;
+
+    - moveCursor(direction: number): Promise\<void>;
+    
+- In **InputMethodExtensionAbility**: 
+
+    - onCreate(want: Want): void;
+
+    - onDestroy(): void;
+
+**Adaptation Guide**
+
+The following uses **showOptionalInputMethods** as an example for asynchronous APIs:
+
+Callback mode:
+
+```js
+import inputMethod from '@ohos.inputmethod';
+let inputMethodSetting = inputMethod.getSetting();
+try {
+    inputMethodSetting.showOptionalInputMethods((err, data) => {
+        if (err !== undefined) {
+            console.error('Failed to showOptionalInputMethods: ' + JSON.stringify(err));
+            return;
+        }
+        console.info('Succeeded in showing optionalInputMethods.');
+    });
+} catch (err) {
+    console.error('Failed to showOptionalInputMethods: ' + JSON.stringify(err));
+}
+```
+
+Promise mode:
+
+```js
+import inputMethod from '@ohos.inputmethod';
+let inputMethodSetting = inputMethod.getSetting();
+inputMethodSetting.showOptionalInputMethods().then((data) => {
+    console.info('Succeeded in showing optionalInputMethods.');
+}).catch((err) => {
+    console.error('Failed to showOptionalInputMethods: ' + JSON.stringify(err));
+})
+```
+
+## cl.inputmethod_frameworks.2 Deprecation of Some APIs
+
+Deprecated APIs:
+  - getInputMethodSetting(): InputMethodSetting;
+  - getInputMethodController(): InputMethodController;
+  - listInputMethod(callback: AsyncCallback<Array<InputMethodProperty>>): void;
+  - listInputMethod(): Promise<Array<InputMethodProperty>>;
+  - displayOptionalInputMethod(callback: AsyncCallback<void>): void;
+  - displayOptionalInputMethod(): Promise<void>;
+  - stopInput(callback: AsyncCallback<boolean>): void;
+  - stopInput(): Promise<boolean>;
+    interface InputMethodProperty:
+    - readonly packageName: string;
+	- readonly methodId: string;
+  - getInputMethodEngine(): InputMethodEngine;
+  - createKeyboardDelegate(): KeyboardDelegate;
+  - hideKeyboard(callback: AsyncCallback<void>): void;
+  - hideKeyboard(): Promise<void>;
+
+Substitute APIs:
+  - getSetting(): InputMethodSetting;
+  - getController(): InputMethodController;
+  - getInputMethods(enable: boolean, callback: AsyncCallback<Array<InputMethodProperty>>): void;
+  - getInputMethods(enable: boolean): Promise<Array<InputMethodProperty>>;
+  - showOptionalInputMethods(callback: AsyncCallback<boolean>): void;
+  - showOptionalInputMethods(): Promise<boolean>;
+  - stopInputSession(callback: AsyncCallback<boolean>): void;
+  - stopInputSession(): Promise<boolean>;
+    interface InputMethodProperty:
+    - readonly name: string;
+	- readonly id: string;
+  - getInputMethodAbility(): InputMethodAbility;
+  - getKeyboardDelegate(): KeyboardDelegate;
+  - hide(callback: AsyncCallback<void>): void;
+  - hide(): Promise<void>;
+
+**NOTE**
+    Use the **getInputMethodAbility()** API to obtain an **InputMethodAbility** object, and do not use **getInputMethodEngine()** to obtain an **InputMethodEngine** object.
+	  Use methods in **InputMethodAbility**, and do not use methods in **InputMethodEngine**.
+	  Use the **on('inputStart')** method in **InputMethodAbility** to obtain a **KeyboardController** instance and an **InputClient** instance, and do not use the **on('inputStart')** method in **InputMethodEngine** to obtain a **TextInputClient** instance.
+Before:
+
+```js
+inputMethodEngine.getInputMethodEngine().on('inputStart', (kbController, textClient) => {
+    let keyboardController = kbController;
+    let textInputClient = textClient;  // Obtain a TextInputClient instance.
+});
+```
+
+After:
+```js
+inputMethodEngine.getInputMethodAbility().on('inputStart', (kbController, client) => {
+    let keyboardController = kbController;
+    let inputClient = client;  // // Obtain an InputClient instance.
+});
+```
+
+## cl.inputmethod_frameworks.3 Change of Some APIs
+
+Before change:
+  - listInputMethod(enable: boolean, callback: AsyncCallback<Array<InputMethodProperty>>): void;
+  - listInputMethod(enable: boolean): Promise<Array<InputMethodProperty>>;
+  - terminateSelf(callback: AsyncCallback<void>): void;
+  - terminateSelf(): Promise<void>;
+
+After change:
+  - getInputMethods(enable: boolean, callback: AsyncCallback<Array<InputMethodProperty>>): void;
+  - getInputMethods(enable: boolean): Promise<Array<InputMethodProperty>>;
+  - destroy(callback: AsyncCallback<void>): void;
+  - destroy(): Promise<void>;
+
+Deleted APIs in API version 9:
+  - startAbility(want: Want, callback: AsyncCallback<void>): void;
+  - startAbility(want: Want, options: StartOptions, callback: AsyncCallback<void>): void;
+  - startAbility(want: Want, options?: StartOptions): Promise<void>;
+
+Added APIs:
+  - on(type: 'imeChange', callback: (inputMethodProperty: InputMethodProperty, inputMethodSubtype: InputMethodSubtype) => void): void;
+  - off(type: 'imeChange', callback?: (inputMethodProperty: InputMethodProperty, inputMethodSubtype: InputMethodSubtype) => void): void;
+  - interface InputMethodProperty:
+    - readonly label?: string;
+	- readonly icon?: string;
+	- readonly iconId?: number;
+	- extra: object;
+	
+  - interface InputMethodAbility:
+    - on(type: 'setSubtype', callback: (inputMethodSubtype: InputMethodSubtype) => void): void;
+    - off(type: 'setSubtype', callback?: (inputMethodSubtype: InputMethodSubtype) => void): void;
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-multimedia.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-multimedia.md
new file mode 100644
index 0000000000000000000000000000000000000000..aa585ed0e8922116000a5aa0cf766e1e04a6dcb1
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-multimedia.md
@@ -0,0 +1,262 @@
+# Multimedia Subsystem Changelog
+
+## cl.multimedia.audio.001 Call Mode Change of getRoutingManager()
+
+**getRoutingManager()** is changed from asynchronous to synchronous.
+
+**Change Impact**
+
+If the new mode is not used, an error will be reported during compilation.
+
+**Key API/Component Changes**
+
+Before change:
+```js
+getRoutingManager(callback: AsyncCallback<AudioRoutingManager>): void;
+getRoutingManager(): Promise<AudioRoutingManager>;
+```
+After change:
+```js
+getRoutingManager(): AudioRoutingManager;
+```
+
+
+## cl.multimedia.audio.002 Call Mode Change of getStreamManager()
+
+**getStreamManager()** is changed from asynchronous to synchronous.
+
+**Change Impact**
+
+If the new mode is not used, an error will be reported during compilation.
+
+**Key API/Component Changes**
+
+Before change:
+```js
+getStreamManager(callback: AsyncCallback<AudioStreamManager>): void;
+getStreamManager(): Promise<AudioStreamManager>;
+```
+After change:
+```js
+getStreamManager(): AudioStreamManager;
+```
+
+
+## cl.multimedia.audio.003 Registration Mode Change of micStateChange
+
+In the original **AudioRoutingManager**, the registration mode of the **micStateChange** listener of the **on()** function is changed.
+
+**Change Impact**
+
+If the new mode is not used, an error will be reported during compilation.
+
+**Key API/Component Changes**
+
+Before change:
+
+```js
+interface AudioRoutingManager {
+   on(type: 'micStateChange', callback: Callback<MicStateChangeEvent>): void;
+}
+```
+After change:
+```js
+interface AudioVolumeGroupManager {
+  on(type: 'micStateChange', callback: Callback<MicStateChangeEvent>): void;
+}
+```
+
+
+## cl.multimedia.audio.004 Call Mode Change of getVolumeGroups()
+
+The call mode of **getVolumeGroups()** is changed.
+
+**Change Impact**
+
+If the new mode is not used, an error will be reported during compilation.
+
+**Key API/Component Changes**
+
+Before change:
+```js
+getVolumeGroups(networkId: string, callback:AsyncCallback<VolumeGroupInfos>): void;
+getVolumeGroups(networkId: string): Promise<VolumeGroupInfos>;
+```
+After change:
+```js
+getVolumeManager(): AudioVolumeManager;
+interface AudioVolumeManager{
+  getVolumeGroupInfos(networkId: string, callback: AsyncCallback<VolumeGroupInfos>): void;
+  getVolumeGroupInfos(networkId: string): Promise<VolumeGroupInfos>;
+}
+```
+
+
+## cl.multimedia.audio.005 Call Mode Change of getGroupManager()
+
+The call mode of **getGroupManager()** is changed.
+
+**Change Impact**
+
+If the new mode is not used, an error will be reported during compilation.
+
+**Key API/Component Changes**
+
+Before change:
+```js
+getGroupManager(groupId: number, callback: AsyncCallback<AudioGroupManager>): void;
+getGroupManager(groupId: number): Promise<AudioGroupManager>;
+```
+After change:
+```js
+getVolumeManager(): AudioVolumeManager;
+interface AudioVolumeManager{
+  getVolumeGroupManager(groupId: number, callback: AsyncCallback<AudioVolumeGroupManager>): void;
+  getVolumeGroupManager(groupId: number): Promise<AudioVolumeGroupManager>;
+}
+```
+
+
+## cl.multimedia.audio.006 FocusType Member Name Change
+
+**FOCUS_TYPE_RECORDING** of **FocusType** is renamed as **FOCUS_TYPE_DEFAULT**.
+
+**Change Impact**
+
+If the new mode is not used, an error will be reported during compilation.
+
+**Key API/Component Changes**
+
+Before change:
+```js
+enum FocusType {
+  FOCUS_TYPE_RECORDING = 0,
+}
+```
+After change:
+```js
+enum InterruptRequestType {
+  INTERRUPT_REQUEST_TYPE_DEFAULT = 0,
+}
+```
+
+
+## cl.multimedia.audio.007 Listener Registration Name Change of interrupt
+
+The listener registration name of **interrupt** of the **on()** function in **AudioRenderer** is changed.
+
+**Change Impact**
+
+If the new mode is not used, an error will be reported during compilation.
+
+**Key API/Component Changes**
+
+Before change:
+```js
+interface AudioRenderer {
+    on(type: 'interrupt', callback: Callback<InterruptEvent>): void;
+}
+```
+After change:
+```js
+interface AudioRenderer {
+    on(type: 'audioInterrupt', callback: Callback<InterruptEvent>): void;
+}
+```
+
+
+## cl.multimedia.media.001 Change of VideoRecorder APIs to System APIs
+
+In the MR version, the formal **AVRecorder** APIs (integrating audio and video) will be provided for external use.
+**VideoRecorder** APIs in API version 9 are changed to system APIs, which are available only to system users. In the future, **VideoRecorder** APIs will be deprecated after system users switch to **AVRecorder**.
+
+**Change Impact**
+
+If the **VideoRecorder** caller is not a system user, the call will fail.
+Involved APIs and enums:
+function createVideoRecorder(callback: AsyncCallback<VideoRecorder>): void;
+function createVideoRecorder(): Promise<VideoRecorder>;
+type VideoRecordState = 'idle' | 'prepared' | 'playing' | 'paused' | 'stopped' | 'error';
+interface VideoRecorder{
+    prepare(config: VideoRecorderConfig, callback: AsyncCallback<void>): void;
+    prepare(config: VideoRecorderConfig): Promise<void>;
+    getInputSurface(callback: AsyncCallback<string>): void;
+    getInputSurface(): Promise<string>;
+    start(callback: AsyncCallback<void>): void;
+    start(): Promise<void>;
+    pause(callback: AsyncCallback<void>): void;
+    pause(): Promise<void>;
+    resume(callback: AsyncCallback<void>): void;
+    resume(): Promise<void>;
+    stop(callback: AsyncCallback<void>): void;
+    stop(): Promise<void>;
+    release(callback: AsyncCallback<void>): void;
+    release(): Promise<void>;
+    reset(callback: AsyncCallback<void>): void;
+    reset(): Promise<void>;
+    on(type: 'error', callback: ErrorCallback): void;
+    readonly state: VideoRecordState;
+}
+interface VideoRecorderProfile {
+    readonly audioBitrate: number;
+    readonly audioChannels: number;
+    readonly audioCodec: CodecMimeType;
+    readonly audioSampleRate: number;
+    readonly fileFormat: ContainerFormatType;
+    readonly videoBitrate: number;
+    readonly videoCodec: CodecMimeType;
+    readonly videoFrameWidth: number;
+    readonly videoFrameHeight: number;
+    readonly videoFrameRate: number;  
+}
+enum AudioSourceType {
+    AUDIO_SOURCE_TYPE_DEFAULT = 0,
+    AUDIO_SOURCE_TYPE_MIC = 1,
+}
+enum VideoSourceType {
+    VIDEO_SOURCE_TYPE_SURFACE_YUV = 0,
+    VIDEO_SOURCE_TYPE_SURFACE_ES = 1,
+}
+enum VideoRecorderConfig {
+    audioSourceType?: AudioSourceType;
+    videoSourceType: VideoSourceType;
+    profile: VideoRecorderProfile;
+    url: string;
+    rotation?: number;
+    location?: Location;
+}
+
+## cl.multimedia.media.002 No Externally Provided Bit Rate Selection API in VideoPlayer
+
+In API version 9, **VideoPlayer** does not externally provide the bit rate selection API. Such an API will be provided by **AVPlayer** in the MR version.
+
+**Change Impact**
+
+Bit rate selection cannot be performed in the multi-bit rate scenario of **VideoPlayer**. Relevant functions will be provided by **AVPlayer**.
+
+**Key API/Component Changes**
+
+Deleted APIs:
+interface VideoPlayer {
+    selectBitrate(bitrate: number): Promise<number>;
+    selectBitrate(bitrate: number, callback: AsyncCallback<number>): void;
+    on(type: 'availableBitratesCollect', callback: (bitrates: Array<number>) => void): void;
+}
+
+## cl.multimedia.media.003 Error Information Change of VideoRecorder
+
+Original error codes of **VideoRecorder** are changed because they do not comply with the error code specifications.
+
+**Change Impact**
+
+Error codes returned from **VideoRecorder** are changed.
+
+**Key API/Component Changes**
+
+**VideoRecorder** APIs remain unchanged, but the returned error codes are changed.
+
+**Adaptation Guide**
+
+For details about exception handling, see the following documents:
+https://gitee.com/openharmony/docs/blob/master/zh-cn/application-dev/reference/apis/js-apis-media.md
+https://gitee.com/openharmony/docs/blob/master/zh-cn/application-dev/reference/errorcodes/errorcode-media.md
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-notification.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-notification.md
new file mode 100644
index 0000000000000000000000000000000000000000..b7a670a8a4de3f8674194bd2dcc0cdc13e2e2d17
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-notification.md
@@ -0,0 +1,64 @@
+# Common Event and Notification Subsystem ChangeLog
+
+## cl.notification.1 API Exception Handling Method Changes
+
+Certain event notification APIs use service logic return values to indicate error information, which does not comply with the API error code specifications of OpenHarmony.
+
+**Change Impacts**
+
+The application developed based on earlier versions needs to adapt the new APIs and their method for returning API error information. Otherwise, the original service logic will be affected.
+
+**Key API/Component Changes**
+
+For adaptation to the unified API exception handling mode, certain event notification APIs are deprecated (original APIs in the following table) and corresponding new APIs in the following table are added. The newly added APIs support unified error code handling specifications and function the same as the original APIs.
+
+| Original API                 | New API                          |
+| ----------------------- | -------------------------------- |
+| @ohos.commonEvent.d.ts  | @ohos.commonEventManager.d.ts    |
+| @ohos.notification.d.ts | @ohos.notificationManager.d.ts   |
+| @ohos.notification.d.ts | @ohos.notificationSubscribe.d.ts |
+
+**Adaptation Guide**
+
+The original APIs are only migrated to the new namespace. Therefore, you can modify **import** to solve the adaptation problem.
+
+If the original API uses **@ohos.commonEvent**:
+
+```js
+import commonEvent from '@ohos.commonEvent';
+```
+
+You can directly modify **import** to switch to the new namespace:
+
+```js
+import commonEvent from '@ohos.commonEventManager';
+```
+
+**@ohos.notification** is split into two namespaces. You need to select a new namespace for adaptation.
+
+In addition, exception handling is needed. For details, see the API reference for the new APIs.
+
+## cl.notification.2 API Changes
+
+The names of some event notification APIs are changed.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enumeration/Constant                                         | Change Type|
+| ------------------------- | ------------------- | ------------------------------------------------------------ | -------- |
+| @ohos.notification        | notification        | **function** enableNotification(bundle: BundleOption, enable: boolean, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| @ohos.notification        | notification        | **function** enableNotification(bundle: BundleOption, enable: boolean): Promise<**void**>; | Deprecated    |
+| @ohos.notificationManager | notificationManager | **function** setNotificationEnable(bundle: BundleOption, enable: boolean, callback: AsyncCallback<**void**>): **void**; | Added    |
+| @ohos.notificationManager | notificationManager | **function** setNotificationEnable(bundle: BundleOption, enable: boolean): Promise<**void**>; | Added    |
+| @ohos.notification        | notification        | **function** enableNotificationSlot(bundle: BundleOption, **type**: SlotType, enable: boolean, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| @ohos.notification        | notification        | **function** enableNotificationSlot(bundle: BundleOption, **type**: SlotType, enable: boolean): Promise<**void**>; | Deprecated    |
+| @ohos.notificationManager | notificationManager | **function** setNotificationEnableSlot(bundle: BundleOption, **type**: SlotType, enable: boolean, callback: AsyncCallback<**void**>): **void**; | Added    |
+| @ohos.notificationManager | notificationManager | **function** setNotificationEnableSlot(bundle: BundleOption, **type**: SlotType, enable: boolean): Promise<**void**>; | Added    |
+| @ohos.notification        | notification        | **function** enableDistributed(enable: boolean, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| @ohos.notification        | notification        | **function** enableDistributed(enable: boolean, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| @ohos.notificationManager | notificationManager | **function** setDistributedEnable(enable: boolean, callback: AsyncCallback<**void**>): **void**; | Added    |
+| @ohos.notificationManager | notificationManager | **function** setDistributedEnable(enable: boolean): Promise<**void**>; | Added    |
+| @ohos.notification        | notification        | **function** enableDistributedByBundle(bundle: BundleOption, enable: boolean, callback: AsyncCallback<**void**>): **void**; | Deprecated    |
+| @ohos.notification        | notification        | **function** enableDistributedByBundle(bundle: BundleOption, enable: boolean): Promise<**void**>; | Deprecated    |
+| @ohos.notificationManager | notificationManager | **function** setDistributedEnableByBundle(bundle: BundleOption, enable: boolean, callback: AsyncCallback<**void**>): **void**; | Added    |
+| @ohos.notificationManager | notificationManager | **function** setDistributedEnableByBundle(bundle: BundleOption, enable: boolean): Promise<**void**>; | Added    |
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-request.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-request.md
index 267f199adc558dba33015838a384eba7aed6c8d0..8007fc39779e57d3a3cf776e3146f6bf5f33a8e8 100644
--- a/en/release-notes/changelogs/v3.2-beta4/changelogs-request.md
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-request.md
@@ -1,4 +1,4 @@
-# Upload and Download Subsystem Changelog
+# Upload and Download Changelog
 
 ## cl.request.1 Changes of Error Code Definitions and API Names
 
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-resourceschedule.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-resourceschedule.md
new file mode 100644
index 0000000000000000000000000000000000000000..73ffb069e25875d25b14dd6c199996b4af8cdf2b
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-resourceschedule.md
@@ -0,0 +1,314 @@
+# Resource Scheduler Subsystem Changelog
+
+## cl.resourceschedule.backgroundTaskManager 
+Rectified original APIs of **backgroundTaskManager** of the resource scheduler subsystem. All APIs in API version 8 and earlier versions are deprecated, and original APIs in API version 9 are deleted. New APIs in API version 9 need to be used. The new APIs in API version 9 comply with the error code specifications.
+
+**Change Impact**
+
+The application developed based on the SDK versions of OpenHarmony 3.2.8.2 and later needs to adapt the modules and APIs in API version 9 and their methods for returning API error information. Otherwise, the original service logic will be affected.
+
+**Key API/Component Changes**
+
+The following methods, attributes, enums, and constants are changed in API version 9 and later versions. The **@ohos.backgroundTaskManager.d.ts** file is deprecated and related APIs are moved to the newly added **@ohos.resourceschedule.backgroundTaskManager.d.ts** file.
+
+| Class| API Type| Declaration| Description| 
+|  -- | -- | -- | -- |
+| backgroundTaskManager | namespace | declare namespace backgroundTaskManager | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager | method | function resetAllEfficiencyResources(): void; | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager | method | function applyEfficiencyResources(request: EfficiencyResourcesRequest): bool; | Changed in API version 9 to **function applyEfficiencyResources(request: EfficiencyResourcesRequest): void;** and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager | method | function stopBackgroundRunning(context: Context): Promise<void>; | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager | method | function stopBackgroundRunning(context: Context, callback: AsyncCallback<void>): void; | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager | method | function startBackgroundRunning(context: Context, bgMode: BackgroundMode, wantAgent: WantAgent): Promise<void>; | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager | method | function startBackgroundRunning(context: Context, bgMode: BackgroundMode, wantAgent: WantAgent, callback: AsyncCallback<void>): void; | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager | method | function requestSuspendDelay(reason: string, callback: Callback<void>): DelaySuspendInfo; | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager | method | function getRemainingDelayTime(requestId: number): Promise<number>; | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager | method | function getRemainingDelayTime(requestId: number, callback: AsyncCallback<number>): void; | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager | method | function cancelSuspendDelay(requestId: number): void; | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.BackgroundMode | enum | export enum BackgroundMode | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.BackgroundMode | enum | DATA_TRANSFER = 1 | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.BackgroundMode | enum | AUDIO_PLAYBACK = 2 | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.BackgroundMode | enum | AUDIO_RECORDING = 3 | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.BackgroundMode | enum | LOCATION = 4 | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.BackgroundMode | enum | BLUETOOTH_INTERACTION = 5 | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.BackgroundMode | enum | MULTI_DEVICE_CONNECTION = 6 | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.BackgroundMode | enum | WIFI_INTERACTION = 7 | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.BackgroundMode | enum | VOIP = 8 | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.BackgroundMode | enum | TASK_KEEPING = 9 | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.DelaySuspendInfo | interface | interface DelaySuspendInfo | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.DelaySuspendInfo | field | requestId: number | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.DelaySuspendInfo | field | actualDelayTime: number | Deprecated in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | export enum ResourceType | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | CPU = 1 | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | COMMON_EVENT = 1 << 1 | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | TIMER = 1 << 2 | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | WORK_SCHEDULER = 1 << 3 | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | BLUETOOTH = 1 << 4 | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | GPS = 1 << 5 | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | AUDIO = 1 << 6 | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | interface | export interface EfficiencyResourcesRequest | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | reason: string | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | isProcess?: bool | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | isPersist?: bool | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | timeOut: number | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | isApply: bool | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | resourceTypes: number | Changed in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+
+
+**Adaptation Guide**
+
+Import the **backgroundTaskManager** module.
+```
+import bundle form '@ohos.resourceschedule.backgroundTaskManager'
+```
+Exception handling also needs to be adapted. For details, see the [backgroundTaskManager API reference](../../../application-dev/reference/apis/js-apis-resourceschedule-backgroundTaskManager.md).
+
+## c2.resourceschedule.usageStatistics 
+Rectified original APIs of **deviceUsageStatistics** of the resource scheduler subsystem. All APIs in API version 8 and earlier versions are deprecated, and original APIs in API version 9 are deleted. New APIs in API version 9 need to be used. The new APIs in API version 9 comply with the error code specifications.
+
+**Change Impact**
+
+The application developed based on the SDK versions of OpenHarmony 3.2.8.2 and later needs to adapt the modules and APIs in API version 9 and their methods for returning API error information. Otherwise, the original service logic will be affected.
+
+**Key API/Component Changes**
+
+The following methods, attributes, enums, and constants are changed in API version 9 and later versions. The **@ohos.bundleState.d.ts** file is deprecated, the **@ohos.resourceschedule.usageStatistics.d.ts** file is added, and the class name is changed from **bundleState** to **usageStatistics**.
+
+| Class                                     | API Type | Method/Attribute/Enum/Constant                                         | Change Type                                                    |
+| ----------------------------------------- | --------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| bundleState                               | method    | function isIdleState(bundleName: string, callback: AsyncCallback<boolean>): void; | Deprecated and moved to **usageStatistics.isIdleState**.                     |
+| bundleState                               | method    | function isIdleState(bundleName: string): Promise<boolean>;  | Deprecated and moved to **usageStatistics.isIdleState**.                     |
+| bundleState                               | method    | function queryAppUsagePriorityGroup(callback: AsyncCallback<number>): void; | Deprecated and changed to **function queryAppGroup(callback: AsyncCallback<number>): void;**.|
+| bundleState                               | method    | function queryAppUsagePriorityGroup(): Promise<number>;      | Deprecated and changed to **function queryAppGroup(): Promise<number>;**.      |
+| bundleState                               | method    | function queryBundleStateInfos(begin: number, end: number, callback: AsyncCallback<BundleActiveInfoResponse>): void; | Deprecated and changed to **function queryBundleStatsInfos(begin: number, end: number, callback: AsyncCallback<BundleStatsMap>): void;**.|
+| bundleState                               | method    | function queryBundleStateInfos(begin: number, end: number): Promise<BundleActiveInfoResponse>; | Deprecated and changed to **function queryBundleStatsInfos(begin: number, end: number): Promise<BundleStatsMap>;**.|
+| bundleState                               | method    | function queryBundleStateInfoByInterval(byInterval: IntervalType, begin: number, end: number): Promise<Array<BundleStateInfo>>; | Deprecated and changed to **function queryBundleStatsInfoByInterval(byInterval: IntervalType, begin: number, end: number): Promise<Array<BundleStatsInfo>>;**.|
+| bundleState                               | method    | function queryBundleStateInfoByInterval(byInterval: IntervalType, begin: number, end: number, callback: AsyncCallback<Array<BundleStateInfo>>): void; | Deprecated and changed to **function queryBundleStatsInfoByInterval(byInterval: IntervalType, begin: number, end: number, callback: AsyncCallback<Array<BundleStatsInfo>>): void;**.|
+| bundleState                               | method    | function queryBundleActiveStates(begin: number, end: number): Promise<Array<BundleActiveState>>; | Deprecated and changed to **function queryBundleEvents(begin: number, end: number): Promise<Array<BundleEvents>>;**.|
+| bundleState                               | method    | function queryBundleActiveStates(begin: number, end: number, callback: AsyncCallback<Array<BundleActiveState>>): void; | Deprecated and changed to **function queryBundleEvents(begin: number, end: number, callback: AsyncCallback<Array<BundleEvents>>): void;**.|
+| bundleState                               | method    | function queryCurrentBundleActiveStates(begin: number, end: number): Promise<Array<BundleActiveState>>; | Deprecated and changed to **function queryCurrentBundleEvents(begin: number, end: number): Promise<Array<BundleEvents>>;**.|
+| bundleState                               | method    | function queryCurrentBundleActiveStates(begin: number, end: number, callback: AsyncCallback<Array<BundleActiveState>>): void; | Deprecated and changed to **function queryCurrentBundleEvents(begin: number, end: number, callback: AsyncCallback<Array<BundleEvents>>): void;**.|
+| bundleState                               | method    | function getRecentlyUsedModules(maxNum?: number): Promise<Array<BundleActiveModuleInfo>>; | Deprecated and changed to **function QueryModuleUsageRecords(maxNum: number): Promise<Array<HapModuleInfo>>;** and **function QueryModuleUsageRecords(): Promise<Array<HapModuleInfo>>;**.|
+| bundleState                               | method    | function getRecentlyUsedModules(maxNum?: number, callback: AsyncCallback<Array<BundleActiveModuleInfo>>): void; | Deprecated and changed to **function QueryModuleUsageRecords(maxNum: number, callback: AsyncCallback<Array<HapModuleInfo>>): void;** and **function QueryModuleUsageRecords(callback: AsyncCallback<Array<HapModuleInfo>>): void;**.|
+| bundleState                               | method    | function queryAppUsagePriorityGroup(bundleName? : string): Promise<number>; | Deprecated and changed to **function queryAppGroup(bundleName: string): Promise<number>;**.|
+| bundleState                               | method    | function queryAppUsagePriorityGroup(bundleName? : string, callback: AsyncCallback<number>): void; | Deprecated and changed to **function queryAppGroup(bundleName: string, callback: AsyncCallback<number>): void;**.|
+| bundleState                               | method    | function setBundleGroup(bundleName: string, newGroup: GroupType, callback: AsyncCallback<void>): void; | Deprecated and changed to **function setAppGroup(bundleName: string, newGroup: GroupType, callback: AsyncCallback<void>): void;**.|
+| bundleState                               | method    | function setBundleGroup(bundleName: string, newGroup: GroupType): Promise<void>; | Deprecated and changed to **function setAppGroup(bundleName: string, newGroup: GroupType): Promise<void>;**.|
+| bundleState                               | method    | function registerGroupCallBack(callback: Callback<BundleActiveGroupCallbackInfo>, callback: AsyncCallback<void>): void; | Deprecated and changed to **function registerAppGroupCallBack(callback: Callback<AppGroupCallbackInfo>, callback: AsyncCallback<void>): void;**.|
+| bundleState                               | method    | function registerGroupCallBack(callback: Callback<BundleActiveGroupCallbackInfo>): Promise<void>; | Deprecated and changed to **function registerAppGroupCallBack(callback: Callback<AppGroupCallbackInfo>): Promise<void>;**.|
+| bundleState                               | method    | function unRegisterGroupCallBack(callback: AsyncCallback<void>): void; | Changed to **function unregisterAppGroupCallBack(): Promise<void>;**.|
+| bundleState                               | method    | function unRegisterGroupCallBack(): Promise<void>;           | Changed to **function unregisterAppGroupCallBack(): Promise<void>;**.|
+| bundleState                               | method    | function queryBundleActiveEventStates(begin: number, end: number, callback: AsyncCallback<Array<BundleActiveEventState>>): void; | Changed to **function queryDeviceEventStats(begin: number, end: number, callback: AsyncCallback<Array<DeviceEventStats>>): void;**|
+| bundleState                               | method    | function queryBundleActiveEventStates(begin: number, end: number): Promise<Array<BundleActiveEventState>>; | Changed in API version 9 to **function queryDeviceEventStats(begin: number, end: number): Promise<Array<DeviceEventStats>>;**.|
+| bundleState                               | method    | function queryAppNotificationNumber(begin: number, end: number, callback: AsyncCallback<Array<BundleActiveEventState>>): void; | Changed in API version 9 to **function queryNotificationEventStats(begin: number, end: number, callback: AsyncCallback<Array<NotificationEventStats >>): void;**.|
+| bundleState                               | method    | function queryAppNotificationNumber(begin: number, end: number): Promise<Array<BundleActiveEventState>>; | Changed in API version 9 to **function queryNotificationEventStats(begin: number, end: number): Promise<Array<NotificationEventStats >>;**.|
+| bundleState.BundleActiveGroupCallbackInfo | interface | interface BundleActiveGroupCallbackInfo                      | Moved to **usageStatistics.AppGroupCallbackInfo**.            |
+| bundleState.BundleActiveGroupCallbackInfo | field     | bundleName: string                                           | Moved to **usageStatistics.AppGroupCallbackInfo**.            |
+| bundleState.BundleActiveGroupCallbackInfo | field     | changeReason: number                                         | Moved to **usageStatistics.AppGroupCallbackInfo**.            |
+| bundleState.BundleActiveGroupCallbackInfo | field     | userId: number                                               | Moved to **usageStatistics.AppGroupCallbackInfo**.            |
+| bundleState.BundleActiveGroupCallbackInfo | field     | appUsageNewGroup: number                                     | Deprecated and changed to **appNewGroup**.                                     |
+| bundleState.BundleActiveGroupCallbackInfo | field     | appUsageOldGroup: number                                     | Deprecated and changed to **appOldGroup**.                                     |
+| bundleState.BundleActiveEventState        | interface | interface BundleActiveEventState                             | Deprecated and changed to **usageStatistics.DeviceEventStats**.                |
+| bundleState.BundleActiveEventState        | field     | count: number                                                | Moved to **usageStatistics.DeviceEventStats**.                |
+| bundleState.BundleActiveEventState        | field     | eventId: number                                              | Moved to **usageStatistics.DeviceEventStats**.                |
+| bundleState.BundleActiveEventState        | field     | name: string                                                 | Moved to **usageStatistics.DeviceEventStats**.                |
+| bundleState.BundleActiveModuleInfo        | interface | interface BundleActiveModuleInfo                             | Changed in API version 9 to **usageStatistics.HapModuleInfo**.         |
+| bundleState.BundleActiveModuleInfo        | field     | formRecords: Array<BundleActiveFormInfo>                     | Changed to **formRecords: Array<HapModuleInfo>**.               |
+| bundleState.BundleActiveModuleInfo        | field     | lastModuleUsedTime: number                                   | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.BundleActiveModuleInfo        | field     | launchedCount: number                                        | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.BundleActiveModuleInfo        | field     | abilityIconId?: number                                       | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.BundleActiveModuleInfo        | field     | abilityDescriptionId?: number                                | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.BundleActiveModuleInfo        | field     | abilityLableId?: number                                      | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.BundleActiveModuleInfo        | field     | descriptionId?: number;                                      | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.BundleActiveModuleInfo        | field     | labelId?: number                                             | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.BundleActiveModuleInfo        | field     | appLabelId?: number                                          | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.BundleActiveModuleInfo        | field     | abilityName?: string                                         | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.BundleActiveModuleInfo        | field     | moduleName: string                                           | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.BundleActiveModuleInfo        | field     | bundleName: string                                           | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.BundleActiveModuleInfo        | field     | deviceId?: string                                            | Moved to **usageStatistics.HapModuleInfo**.                   |
+| bundleState.GroupType                     | enum      | enum GroupType                                               | Moved to **usageStatistics.GroupType**.                       |
+| bundleState.GroupType                     | enum      | ACTIVE_GROUP_ALIVE                                           | Deprecated and changed to **ALIVE_GROUP**.                                     |
+| bundleState.GroupType                     | enum      | ACTIVE_GROUP_DAILY                                           | Deprecated and changed to **DAILY_GROUP**.                                     |
+| bundleState.GroupType                     | enum      | ACTIVE_GROUP_FIXED                                           | Deprecated and changed to **FIXED_GROUP**.                                     |
+| bundleState.GroupType                     | enum      | ACTIVE_GROUP_RARE                                            | Deprecated and changed to **RARE_GROUP**.                                      |
+| bundleState.GroupType                     | enum      | ACTIVE_GROUP_LIMIT                                           | Deprecated and changed to **LIMITED_GROUP**.                                   |
+| bundleState.GroupType                     | enum      | ACTIVE_GROUP_NEVER                                           | Deprecated and changed to **NEVER_GROUP**.                                     |
+| bundleState.IntervalType                  | enum      | enum IntervalType                                            | Deprecated and moved to **usageStatistics.IntervalType**.                    |
+| bundleState.IntervalType                  | enum      | BY_OPTIMIZED                                                 | Deprecated and moved to **usageStatistics.IntervalType**.                    |
+| bundleState.IntervalType                  | enum      | BY_DAILY                                                     | Deprecated and moved to **usageStatistics.IntervalType**.                    |
+| bundleState.IntervalType                  | enum      | BY_WEEKLY                                                    | Deprecated and moved to **usageStatistics.IntervalType**.                    |
+| bundleState.IntervalType                  | enum      | BY_MONTHLY                                                   | Deprecated and moved to **usageStatistics.IntervalType**.                    |
+| bundleState.IntervalType                  | enum      | BY_ANNUALLY                                                  | Deprecated and moved to **usageStatistics.IntervalType**.                    |
+| bundleState.BundleActiveInfoResponse      | interface | interface BundleActiveInfoResponse                           | Deprecated and changed to **usageStatistics.BundleStatsMap**.                  |
+| bundleState.BundleActiveState             | interface | interface BundleActiveState                                  | Deprecated and changed to **usageStatistics.BundleEvents**.                    |
+| bundleState.BundleActiveState             | field     | stateType?: number                                           | Deprecated and changed to **eventId**.                                         |
+| bundleState.BundleActiveState             | field     | stateOccurredTime?: number                                   | Deprecated and changed to **eventOccurredTime**.                               |
+| bundleState.BundleActiveState             | field     | nameOfClass?: string                                         | Deprecated and moved to **usageStatistics.BundleEvents**.                    |
+| bundleState.BundleActiveState             | field     | indexOfLink?: string                                         | Deprecated and moved to **usageStatistics.BundleEvents**.                    |
+| bundleState.BundleActiveState             | field     | bundleName?: string                                          | Deprecated and moved to **usageStatistics.BundleEvents**.                    |
+| bundleState.BundleActiveState             | field     | appUsagePriorityGroup?: number                               | Deprecated and changed to **appGroup**.                                        |
+| bundleState.BundleStateInfo               | interface | interface BundleStateInfo                                    | Deprecated and changed to **usageStatistics.BundleStatsInfo**.                 |
+| bundleState.BundleStateInfo               | method    | merge(toMerge: BundleStateInfo): void                        | Deprecated.                                                        |
+| bundleState.BundleStateInfo               | field     | infosEndTime?: number                                        | Deprecated and moved to **usageStatistics.BundleStatsInfo**.                 |
+| bundleState.BundleStateInfo               | field     | infosBeginTime?: number                                      | Deprecated and moved to **usageStatistics.BundleStatsInfo**.                 |
+| bundleState.BundleStateInfo               | field     | fgAbilityPrevAccessTime?: number                             | Deprecated and moved to **usageStatistics.BundleStatsInfo**.                 |
+| bundleState.BundleStateInfo               | field     | fgAbilityAccessTotalTime?: number                            | Deprecated and moved to **usageStatistics.BundleStatsInfo**.                 |
+| bundleState.BundleStateInfo               | field     | bundleName?: string                                          | Deprecated and moved to **usageStatistics.BundleStatsInfo**.                 |
+| bundleState.BundleStateInfo               | field     | abilitySeenTotalTime?: number                                | Deprecated and moved to **usageStatistics.BundleStatsInfo**.                 |
+| bundleState.BundleStateInfo               | field     | abilityPrevSeenTime?: number                                 | Deprecated and moved to **usageStatistics.BundleStatsInfo**.                 |
+| bundleState.BundleStateInfo               | field     | abilityPrevAccessTime?: number                               | Deprecated and moved to **usageStatistics.BundleStatsInfo**.                 |
+| bundleState.BundleStateInfo               | field     | abilityInFgTotalTime?: number                                | Deprecated and moved to **usageStatistics.BundleStatsInfo**.                 |
+| bundleState.BundleStateInfo               | field     | id: number                                                   | Deprecated and moved to **usageStatistics.BundleStatsInfo**.                 |
+| bundleState                               | namespace | declare namespace bundleState                                | Deprecated and changed to **usageStatistics**, and moved to **ohos.resourceschedule.usageStatistics.d.ts**.|
+
+
+**Adaptation Guide**
+
+Import the **usageStatistics** module.
+```
+import bundle form '@ohos.resourceschedule.usageStatistics'
+```
+Exception handling also needs to be adapted. For details, see the [usageStatistics API reference](../../../application-dev/reference/apis/js-apis-resourceschedule-deviceUsageStatistics.md).
+
+
+## c3.resourceschedule.workScheduler 
+Rectified original APIs of **workScheduler** of the resource scheduler subsystem. The original APIs in API version 9 are changed to new APIs in API version 9. The new APIs in API version 9 comply with the error code specifications.
+
+**Change Impact**
+
+The application developed based on the SDK versions of OpenHarmony 3.2.8.2 and later needs to adapt the modules and APIs in API version 9 and their methods for returning API error information. Otherwise, the original service logic will be affected.
+
+**Key API/Component Changes**
+
+The following methods, attributes, enums, and constants are changed in API version 9 and later versions. The **@ohos.workScheduler.d.ts** file is deprecated and related APIs are moved to the newly added **@ohos.resourceschedule.workScheduler.d.ts** file.
+
+| Class| API Type| Declaration| Change Type| 
+|  -- | -- | -- | -- |
+| workScheduler | namespace | declare namespace workScheduler | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | interface | export interface WorkInfo | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | parameters?: {[key: string]: any} | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | idleWaitTime?: number | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | isDeepIdle?: boolean | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | repeatCount?: number | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | isRepeat?: boolean | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | repeatCycleTime?: number | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | storageRequest?: StorageRequest | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | batteryStatus?: BatteryStatus | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | batteryLevel?: number | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | chargerType?: ChargingType | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | isCharging?: boolean | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | networkType?: NetworkType | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | isPersisted?: boolean | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | abilityName: string | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | bundleName: string | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | workId: number | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function isLastWorkTimeOut(workId: number): Promise; | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function isLastWorkTimeOut(workId: number, callback: AsyncCallback<void>): boolean; | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function stopAndClearWorks(): boolean; | Changed in API version 8 to **function stopAndClearWorks(): boolean;** and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function obtainAllWorks(): Promise<Array<WorkInfo>>; | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function obtainAllWorks(callback: AsyncCallback<void>): Array<WorkInfo>; | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function getWorkStatus(workId: number): Promise<WorkInfo>; | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function getWorkStatus(workId: number, callback: AsyncCallback<WorkInfo>): void; | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function stopWork(work: WorkInfo, needCancel?: boolean): boolean; | Changed in API version 8 to **function stopWork(work: WorkInfo, needCancel?: boolean): void;** and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function startWork(work: WorkInfo): boolean; | Changed in API version 9 to **function startWork(work: WorkInfo): void;** and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | export enum NetworkType | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_ANY = 0 | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_MOBILE | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_WIFI | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_BLUETOOTH | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_WIFI_P2P | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_ETHERNET | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.ChargingType | enum | export enum ChargingType | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.ChargingType | enum | CHARGING_PLUGGED_ANY = 0 | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.ChargingType | enum | CHARGING_PLUGGED_AC | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.ChargingType | enum | CHARGING_PLUGGED_USB | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.ChargingType | enum | CHARGING_PLUGGED_WIRELESS | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | export enum BatteryStatus | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | BATTERY_STATUS_LOW = 0 | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | BATTERY_STATUS_OKAY | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | BATTERY_STATUS_LOW_OR_OKAY | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.StorageRequest | enum | export enum StorageRequest | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | STORAGE_LEVEL_LOW = 0 | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | STORAGE_LEVEL_OKAY | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | STORAGE_LEVEL_LOW_OR_OKAY | Changed in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+
+
+**Adaptation Guide**
+
+Import the **workScheduler** module.
+```
+import bundle form '@ohos.resourceschedule.workScheduler'
+```
+Exception handling also needs to be adapted. For details, see the [workScheduler API reference](../../../application-dev/reference/apis/js-apis-resourceschedule-workScheduler.md).
+
+
+## c4.resourceschedule.reminderAgent
+Rectified original APIs of **reminderAgent** of the resource scheduler subsystem. All APIs in API version 8 and earlier versions are deprecated, and original APIs in API version 9 are deleted. New APIs in API version 9 need to be used. The new APIs in API version 9 comply with the error code specifications.
+
+**Change Impact**
+
+The application developed based on the SDK versions of OpenHarmony 3.2.8.2 and later needs to adapt the modules and APIs in API version 9 and their methods for returning API error information. Otherwise, the original service logic will be affected.
+
+**Key API/Component Changes**
+
+The following methods, attributes, enums, and constants are changed in API version 9 and later versions. The **@ohos.reminderAgent.d.ts** file is deprecated, the **@ohos.reminderAgentManager.d.ts** file is added, and the class name is changed from **reminderAgent** to **reminderAgentManager**.
+
+| Class               | API Type       | Method/Attribute/Enum/Constant                                         | Change Type                                                    |
+| --------------------- | ----------- | ------------------------------------------------------------ | ------------------------------------------------------------ |
+| reminderAgent | method | publishReminder(reminderReq: ReminderRequest, callback: AsyncCallback<number>): void; | Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent | method | publishReminder(reminderReq: ReminderRequest): Promise<number>;  | Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent | method | cancelReminder(reminderId: number, callback: AsyncCallback<void>): void; | Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent | method | cancelReminder(reminderId: number): Promise<void>; | Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent | method | getValidReminders(callback: AsyncCallback<Array<ReminderRequest>>): void; | Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent | method | getValidReminders(): Promise<Array<ReminderRequest>>; | Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent | method | cancelAllReminders(callback: AsyncCallback<void>): void; | Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent | method | cancelAllReminders(): Promise<void>; |  Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent | method | addNotificationSlot(slot: NotificationSlot, callback: AsyncCallback<void>): void; | Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent | method | addNotificationSlot(slot: NotificationSlot): Promise<void>; | Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent | method | removeNotificationSlot(slotType: notification.SlotType, callback: AsyncCallback<void>): void; | Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent | method | removeNotificationSlot(slotType: notification.SlotType): Promise<void>; | Deprecated and moved to **reminderAgentManager**.|
+| reminderAgent.ActionButtonType | enum | ACTION_BUTTON_TYPE_CLOSE | Deprecated and moved to **reminderAgentManager.ActionButtonType**.|
+| reminderAgent.ActionButtonType | enum | ACTION_BUTTON_TYPE_SNOOZE |  Deprecated and moved to **reminderAgentManager.ActionButtonType**.|
+| reminderAgent.ReminderType | enum | REMINDER_TYPE_TIMER | Deprecated and moved to **reminderAgentManager.ReminderType**.|
+| reminderAgent.ReminderType | enum | REMINDER_TYPE_CALENDAR | Deprecated and moved to **reminderAgentManager.ReminderType**.|
+| reminderAgent.ReminderType | enum | REMINDER_TYPE_CALENDAR | Deprecated and moved to **reminderAgentManager.ReminderType**.|
+| reminderAgent.ActionButton | field | title:string | Deprecated and moved to **reminderAgentManager.ActionButton**.|
+| reminderAgent.ActionButton | field | type:ActionButtonType | Deprecated and moved to **reminderAgentManager.ActionButton**.|
+| reminderAgent.WantAgent | field | pkgName:string | Deprecated and moved to **reminderAgentManager.WantAgent**.|
+| reminderAgent.WantAgent | field | abilityName:string | Deprecated and moved to **reminderAgentManager.WantAgent**.|
+| reminderAgent.MaxScreenWantAgent | field | pkgName:string | Deprecated and moved to **reminderAgentManager.MaxScreenWantAgent**.|
+| reminderAgent.MaxScreenWantAgent | field | abilityName:string | Deprecated and moved to **reminderAgentManager.MaxScreenWantAgent**.|
+| reminderAgent.ReminderRequest | field | reminderType:ReminderType | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | actionButton?:ActionButton | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | wantAgent?:WantAgent | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | maxScreenWantAgent?:MaxScreenWantAgent | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | ringDuration?:number | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | snoozeTimes?:number | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | timeInterval?:number | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | title?:string | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | content?:string | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | expiredContent?:string | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | snoozeContent?:string | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | notificationId?:number | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequest | field | slotType?:	notification.SlotType | Deprecated and moved to **reminderAgentManager.ReminderRequest**.|
+| reminderAgent.ReminderRequestCalendar | field | dateTime:LocalDateTime | Deprecated and moved to **reminderAgentManager.ReminderRequestCalendar**.|
+| reminderAgent.ReminderRequestCalendar | field | repeatMonths?:Array<number> | Deprecated and moved to **reminderAgentManager.ReminderRequestCalendar**.|
+| reminderAgent.ReminderRequestCalendar | field | repeatDays?:Array<number> | Deprecated and moved to **reminderAgentManager.ReminderRequestCalendar**.|
+| reminderAgent.ReminderRequestAlarm | field | hour:number | Deprecated and moved to **reminderAgentManager.ReminderRequestAlarm**.|
+| reminderAgent.ReminderRequestAlarm | field | minute:number | Deprecated and moved to **reminderAgentManager.ReminderRequestAlarm**.|
+| reminderAgent.ReminderRequestAlarm | field | daysOfWeek?:Array<number> | Deprecated and moved to **reminderAgentManager.ReminderRequestAlarm**.|
+| reminderAgent.ReminderRequestTimer | field | triggerTimeInSeconds:number | Deprecated and moved to **reminderAgentManager.ReminderRequestTimer**.|
+| reminderAgent.LocalDateTime | field | year:number | Deprecated and moved to **reminderAgentManager.LocalDateTime**.|
+| reminderAgent.LocalDateTime | field | month:number | Deprecated and moved to **reminderAgentManager.LocalDateTime**.|
+| reminderAgent.LocalDateTime | field | day:number | Deprecated and moved to **reminderAgentManager.LocalDateTime**.|
+| reminderAgent.LocalDateTime | field | hour:number | Deprecated and moved to **reminderAgentManager.LocalDateTime**.|
+| reminderAgent.LocalDateTime | field | minute:number | Deprecated and moved to **reminderAgentManager.LocalDateTime**.|
+| reminderAgent.LocalDateTime | field | second?:number | Deprecated and moved to **reminderAgentManager.LocalDateTime**.|
+
+
+**Adaptation Guide**
+
+Import the **reminderAgentManager** module.
+```
+import bundle form '@ohos.reminderAgentManager'
+```
+Exception handling also needs to be adapted. For details, see the [reminderAgentManager API reference](../../../application-dev/reference/apis/js-apis-reminderAgentManager.md).
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-theme.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-theme.md
new file mode 100644
index 0000000000000000000000000000000000000000..17621fd618bab7919fc62a78ac5cf2fb21e44246
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-theme.md
@@ -0,0 +1,148 @@
+# Theme Framework ChangeLog
+
+## cl.theme.1 Support of Exception Handling for APIs in API Version 9
+
+The internal APIs of the following modules used service logic return values to indicate error information, which did not comply with the error code specifications of OpenHarmony. Therefore, they are modified in API version 9 and later.
+ - Wallpaper management service: **@ohos.wallpaper.d.ts**
+
+ - Lock screen management service: **@ohos.screenLock.d.ts**
+
+APIs in the preceding modules are changed as follows:
+Synchronous API: An error message is returned via an exception.
+Asynchronous API: A parameter check error is returned synchronously. A service logic error is returned via **AsyncCallback** or the **error** object of **Promise**.
+
+**Change Impacts**
+
+The application developed based on earlier versions needs to adapt the method for returning API error information. Otherwise, the original service logic will be affected.
+
+**Key API/Component Changes**
+
+Deprecated APIs of the wallpaper management service:
+   - getColors(wallpaperType: WallpaperType, callback: AsyncCallback<Array<RgbaColor>>): void;
+   - getColors(wallpaperType: WallpaperType): Promise<Array<RgbaColor>>;
+   - getId(wallpaperType: WallpaperType, callback: AsyncCallback<number>): void;
+   - getId(wallpaperType: WallpaperType): Promise<number>;
+   - getMinHeight(callback: AsyncCallback<number>): void;
+   - getMinHeight(): Promise<number>;
+   - getMinWidth(callback: AsyncCallback<number>): void;
+   - getMinWidth(): Promise<number>;
+   - isChangePermitted(callback: AsyncCallback<boolean>): void;
+   - isChangePermitted(): Promise<boolean>;
+   - isOperationAllowed(callback: AsyncCallback<boolean>): void;
+   - isOperationAllowed(): Promise<boolean>;
+   - reset(wallpaperType: WallpaperType, callback: AsyncCallback<void>): void;
+   - reset(wallpaperType: WallpaperType): Promise<void>;
+   - setWallpaper(source: string | image.PixelMap, wallpaperType: WallpaperType, callback: AsyncCallback<void>): void;
+   - setWallpaper(source: string | image.PixelMap, wallpaperType: WallpaperType): Promise<void>;
+   - getFile(wallpaperType: WallpaperType, callback: AsyncCallback<number>): void;
+   - getFile(wallpaperType: WallpaperType): Promise<number>;
+   - getPixelMap(wallpaperType: WallpaperType, callback: AsyncCallback<image.PixelMap>): void;
+   - getPixelMap(wallpaperType: WallpaperType): Promise<image.PixelMap>;
+
+Substitute APIs of the wallpaper management service:
+   - getColorsSync(wallpaperType: WallpaperType): Array<RgbaColor>;
+   - getIdSync(wallpaperType: WallpaperType): number;
+   - getMinHeightSync(): number;
+   - getMinWidthSync(): number;
+   - isChangeAllowed(): boolean;
+   - isUserChangeAllowed(): boolean;
+   - restore(wallpaperType: WallpaperType, callback: AsyncCallback<void>): void;
+   - restore(wallpaperType: WallpaperType): Promise<void>;
+   - setImage(source: string | image.PixelMap, wallpaperType: WallpaperType, callback: AsyncCallback<void>): void;
+   - setImage(source: string | image.PixelMap, wallpaperType: WallpaperType): Promise<void>;
+   - getFileSync(wallpaperType: WallpaperType): number;
+   - getImage(wallpaperType: WallpaperType, callback: AsyncCallback<image.PixelMap>): void;
+   - getImage(wallpaperType: WallpaperType): Promise<image.PixelMap>;
+
+Changed APIs of the wallpaper management service:
+   - on(type: 'colorChange', callback: (colors: Array<RgbaColor>, wallpaperType: WallpaperType) => void): void
+   - off(type: 'colorChange', callback?: (colors: Array<RgbaColor>, wallpaperType: WallpaperType) => void): void
+
+Deprecated APIs of the lock screen management service:
+   - isScreenLocked(callback: AsyncCallback<boolean>): void;
+   - isScreenLocked(): Promise<boolean>;
+   - isSecureMode(callback: AsyncCallback<boolean>): void;
+   - isSecureMode(): Promise<boolean>;
+   - unlockScreen(callback: AsyncCallback<void>): void;
+   - unlockScreen(): Promise<void>;
+
+Substitute APIs of the lock screen management service:
+   - isLocked(): boolean;
+   - isSecure(): boolean;
+   - unlock(callback: AsyncCallback<boolean>): void;
+   - unlock():Promise<boolean>;
+
+Deleted APIs of the lock screen management service:
+   - lockScreen(callback: AsyncCallback<void>): void;
+   - lockScreen(): Promise<void>;
+
+The following APIs are added for the lock screen management service:
+   - lock(callback: AsyncCallback<boolean>): void;
+   - lock():Promise<boolean>;
+
+Changed APIs of the lock screen management service:
+   - onSystemEvent(callback: Callback<SystemEvent>): boolean;
+   - sendScreenLockEvent(event: String, parameter: number, callback: AsyncCallback<boolean>): void;
+   - sendScreenLockEvent(event: String, parameter: number): Promise<boolean>;
+
+**Adaption Guide for the Wallpaper Management Service**
+
+The following uses **getImage** as an example for asynchronous APIs:
+
+```ts
+import pointer from '@ohos.wallpaper';
+try {
+    wallpaper.getImage(wallpaper.WallpaperType.WALLPAPER_SYSTEM).then((data) => {
+        console.log(`success to getImage: ${JSON.stringify(data)}`);
+    }).catch((error) => {
+        console.error(`failed to getImage because: ${JSON.stringify(error)}`);
+    });
+} catch (err) {
+    console.error(`failed to getImage because: ${JSON.stringify(err)}`);
+}
+
+```
+
+The following uses **getFileSync** as an example for synchronous APIs:
+
+```ts
+import pointer from '@ohos.wallpaper';
+try {
+    let file = wallpaper.getFileSync(wallpaper.WallpaperType.WALLPAPER_SYSTEM);
+} catch (err) {
+    console.error(`failed to getFileSync because: ${err.message}`);
+}
+```
+
+**Adaption Guide for the Lock Screen Management Service**
+
+The following uses **lock** as an example for asynchronous APIs:
+
+```ts
+import screenLock from '@ohos.screenlock';
+try {
+  screenLock.lock((err, data) => {      
+    if (err) {
+        console.error(`Failed to lock the screen, because: ${err.message}`);
+        return;    
+    }
+    console.info(`lock the screen successfully. result: ${data}`);
+  });
+} catch (err) {
+    console.error(`Failed to lock the screen, because: ${err.message}`);
+}
+
+```
+
+The following uses **onSystemEvent** as an example for synchronous APIs:
+
+```ts
+import screenLock from '@ohos.screenlock';
+try {
+   let isSuccess = screenLock.onSystemEvent((event) => {
+       console.log(`Register the system event which related to screenlock successfully. eventType: ${event.eventType}`)
+   });
+} catch (err) {
+   console.error(`Failed to register the system event which related to screenlock, because: ${err.message}`)
+}
+```
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-wantAgent.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-wantAgent.md
new file mode 100644
index 0000000000000000000000000000000000000000..0700c6585be1ac90b3371ba7b230ef821a4d43ee
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-wantAgent.md
@@ -0,0 +1,88 @@
+# WantAgent JS API Changelog
+
+## cl.url.1 Trigger API Changes
+trigger(agent: WantAgent, triggerInfo: TriggerInfo, callback?: Callback<CompleteData>): void ;
+
+This API has been deleted, because some functions have not been implemented. Your application can call the following API:
+
+ trigger(agent: WantAgent, triggerInfo: TriggerInfo, callback?: AsyncCallback<CompleteData>): void 
+
+**Change Impact**
+
+Released JS APIs are affected. The application needs to adapt these APIs so that it can be properly compiled in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| OpenHarmony 3.2.8.1 API                                 | OpenHarmony 3.2.9.1 SP8 API                             |
+| ------------------------------------------------------------ | ------------------------------------------------------------ |
+| trigger(agent: WantAgent, triggerInfo: TriggerInfo, callback?: Callback<CompleteData>): void ; | trigger(agent: WantAgent, triggerInfo: TriggerInfo, callback?: AsyncCallback<CompleteData>): void |
+
+**Adaptation Guide**
+
+The following illustrates how to call the alternative **trigger** API in your application.
+
+Example:
+
+```ts
+import WantAgent from '@ohos.app.ability.wantAgent';
+// WantAgent object
+var wantAgent;
+// triggerInfo
+var triggerInfo = {
+        code: 0
+    }
+// WantAgentInfo object
+var wantAgentInfo = {
+    wants: [
+        {
+            deviceId: "deviceId",
+            bundleName: "com.neu.setResultOnAbilityResultTest1",
+            abilityName: "com.example.test.MainAbility",
+            action: "action1",
+            entities: ["entity1"],
+            type: "MIMETYPE",
+            uri: "key={true,true,false}",
+            parameters:
+            {
+                mykey0: 2222,
+                mykey1: [1, 2, 3],
+                mykey2: "[1, 2, 3]",
+                mykey3: "ssssssssssssssssssssssssss",
+                mykey4: [false, true, false],
+                mykey5: ["qqqqq", "wwwwww", "aaaaaaaaaaaaaaaaa"],
+                mykey6: true,
+            }
+        }
+    ],
+    operationType: WantAgent.OperationType.START_ABILITIES,
+    requestCode: 0,
+    wantAgentFlags:[WantAgent.WantAgentFlags.UPDATE_PRESENT_FLAG]
+}
+
+// getWantAgent callback
+function getWantAgentCallback(err, data) {
+    if (err == undefined) {
+        wantAgent = data;
+    } else {
+        console.info('getWantAgent failed' + JSON.stringify(wantAgent));
+    }
+    // getUid callback
+    function triggerCallback(err, data) {
+        if(err) {
+            console.info('getUid failed!' + JSON.stringify(err.code) + JSON.stringify(err.message));
+        } else {
+            console.info('getUid ok!' + JSON.stringify(data));
+        }
+    }
+    try {
+        WantAgent.trigger(wantAgent, triggerInfo, triggerCallback);
+    } catch(err) {
+        console.info('getUid failed!' + JSON.stringify(err.code) + JSON.stringify(err.message));
+    }
+}
+try{
+    WantAgent.getWantAgent(wantAgentInfo, getWantAgentCallback);
+} catch(err){
+    console.info('getWantAgent failed!' + JSON.stringify(err.code) + JSON.stringify(err.message));
+}
+```
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-web.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-web.md
new file mode 100644
index 0000000000000000000000000000000000000000..a754808f32c35ceab510e8a87150f9ed858b3c48
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-web.md
@@ -0,0 +1,126 @@
+# Web Subsystem ChangeLog
+
+## cl.web.1 Deletion of Unnecessary Error Codes
+
+APIs in the webviewController component of the web subsystem are changed:
+
+ - Deleted **@throws { BusinessError } 17100007 - Invalid back or forward operation** from the **forward**, **backward**, and **backOrForward** APIs.
+ - Deleted **@throws { BusinessError } 17100009 - Cannot zoom in or zoom out** from the **zoom**, **zoomIn**, and **zoomOut** APIs.
+
+You need to adapt your application based on the following information.
+
+**Change Impacts**
+
+Released JS APIs are affected. The application can be properly compiled in the SDK environment of the new version, without any adaptation.
+
+**Key API/Component Changes**
+
+Involved APIs: **forward**, **backward**, **backOrForward**, **zoom**, **zoomIn**, and **zoomOut**
+Involved component: web
+
+**Adaptation Guide**
+
+No adaptation is required.        
+## cl.web.2 setWebController Input Parameter Changes
+
+Some released web controllers are migrated to the webviewController, and the original webController is deprecated. The following changes are made in API version 9 and later:
+The input parameter of **setWebController** is replaced by the new **webviewController**.
+
+**Change Impacts**
+
+Input parameters of JS APIs need to be adapted for applications developed based on earlier versions. Otherwise, relevant functions will be affected.
+
+**Key API/Component Changes**
+
+- Involved API:
+
+  setWebController(controller: WebviewController): void;
+
+- Before change:
+
+```js
+setWebController(controller: WebController): void;
+```
+
+- After change:
+
+```js
+setWebController(controller: WebviewController): void;
+```
+
+**Adaptation Guide**
+
+The sample code is as follows:
+
+Before change:
+
+```js
+// xxx.ets
+@Entry
+@Component
+struct WebComponent {
+  controller:WebController = new WebController()
+  build() {
+    Column() {
+      Web({ src:'www.example.com', controller: this.controller })
+      .multiWindowAccess(true)
+      .onWindowNew((event) => {
+        console.log("onWindowNew...")
+        var popController: WebController = new WebController()
+        event.handler.setWebController(popController)
+      })
+    }
+  }
+}
+```
+
+After change:
+```js
+// xxx.ets
+@Entry
+@Component
+struct WebComponent {
+  controller: web_webview.WebviewController = new web_webview.WebviewController()
+  build() {
+    Column() {
+      Web({ src:'www.example.com', controller: this.controller })
+      .multiWindowAccess(true)
+      .onWindowNew((event) => {
+        console.log("onWindowNew...")
+        var popController: web_webview.WebviewController = new web_webview.WebviewController()
+        event.handler.setWebController(popController)
+      })
+    }
+  }
+}
+```
+
+## cl.web.3 getUnfilterendLinkUrl API Name Change
+
+The **getUnfilterendLinkUrl** API is misspelled and should be changed to **getUnfilteredLinkUrl**.
+
+**Change Impacts**
+
+The JS API name needs to be adapted for applications developed based on earlier versions. Otherwise, relevant functions will be affected.
+
+**Key API/Component Changes**
+
+- Involved API:
+
+  getUnfilteredLinkUrl(): string;
+
+- Before change:
+
+```js
+getUnfilterendLinkUrl(): string;
+```
+
+- After change:
+
+```js
+getUnfilteredLinkUrl(): string;
+```
+
+**Adaptation Guide**
+
+The JS API name needs to be adapted for applications developed based on earlier versions. The new API name is used to replace the original one. Otherwise, relevant functions will be affected.
diff --git a/en/release-notes/changelogs/v3.2-beta4/changelogs-wifi.md b/en/release-notes/changelogs/v3.2-beta4/changelogs-wifi.md
index 8c9636e2be0c2d26182dc1891977c6eace70c13b..d816578bd249824538e557e4427f4d6a95f41002 100644
--- a/en/release-notes/changelogs/v3.2-beta4/changelogs-wifi.md
+++ b/en/release-notes/changelogs/v3.2-beta4/changelogs-wifi.md
@@ -1,4 +1,4 @@
-# Wi-Fi Subsystem Changelog
+# Communication Subsystem - WiFi Changelog
 
 
 ## cl.wifi.1 Moving System APIs and APIs of Version 9 to @ohos.wifiManager.d.ts
diff --git a/en/release-notes/changelogs/v3.2-beta5/Readme-EN.md b/en/release-notes/changelogs/v3.2-beta5/Readme-EN.md
new file mode 100644
index 0000000000000000000000000000000000000000..1a600bb5e27f14dc653be8a1aabd7f2e1f2a9016
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta5/Readme-EN.md
@@ -0,0 +1,22 @@
+# Readme
+
+- [Ability framework](changelogs-ability.md)
+- [Account subsystem](changelogs-account_os_account.md)
+- [Multimedia subsystem - camera](changelogs-camera-sync.md)
+- [Common library subsystem - container](changelogs-container.md)
+- [Distributed data management subsystem](changelogs-distributeddatamgr.md)
+- [File management subsystem](changelogs-filemanagement.md)
+- [File management subsystem - MediaLibrary](changelogs-mediaLibrary.md)
+- [Multimedia subsystem](changelogs-multimedia.md)
+- [Communication subsystem - NFC](changelogs-nfc.md)
+- Location subsystem
+  - [ohos.geoLocationManager](changelogs-ohos-geoLocationManager.md)
+  - [ohos.geoLocation](changelogs-ohos-geolocation.md)
+  - [system.geolocation](changelogs-system-geolocation.md)
+- [Upload and download](changelogs-request.md)
+- [Resource scheduler subsystem](changelogs-resourceschedule.md)
+- [Security subsystem](changelogs-security.md)
+- [Telephony subsystem](changelogs-telephony.md)
+- [Common library subsystem - URL](changelogs-url.md)
+- [User IAM subsystem](changelogs-useriam.md)
+- [Window manager subsystem](changelogs-window.md)
diff --git a/en/release-notes/changelogs/v3.2-beta5/Readme.md b/en/release-notes/changelogs/v3.2-beta5/Readme.md
deleted file mode 100644
index 85236c21830d9e277187850d734b1ac2ac71a87d..0000000000000000000000000000000000000000
--- a/en/release-notes/changelogs/v3.2-beta5/Readme.md
+++ /dev/null
@@ -1,9 +0,0 @@
-# Readme
-
-- [Account](changelogs-account_os_account.md)
-- [Distributed Data Management](changelogs-distributeddatamgr.md)
-- [File Management](changelogs-filemanagement.md)
-- [Communication-NFC](changelogs-nfc.md)
-- [Security](changelogs-security.md)
-- [User IAM](changelogs-useriam.md)
-
diff --git a/en/release-notes/changelogs/v3.2-beta5/changelog-x-x.md b/en/release-notes/changelogs/v3.2-beta5/changelog-x-x.md
new file mode 100644
index 0000000000000000000000000000000000000000..dcc7cd9aabb636ed248b5a37383410d4218b346f
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta5/changelog-x-x.md
@@ -0,0 +1,28 @@
+# *Example* Subsystem Changelog
+
+Changes that affect contract compatibility of the last version should be described in the changelog. The changes include but are not limited to those related to API names, parameters, return values, required permissions, call sequence, enumerated values, configuration parameters, and paths. The last version can be an LTS, release, beta, or monthly version, or the like. Contract compatibility, also called semantic compatibility, means that the original program behavior should remain consistent over versions.
+
+## cl.subsystemname.x xxx Function Change (Example: DeviceType Attribute Change or Camera Permission Change. Use a short description.)
+
+Add the number **cl.*subsystemname*.*x*** before each change title, where **cl** is the abbreviation of changelog, *subsystemname* is the standard English name of the subsystem, and *x* indicates the change sequence number (starting from 1 in ascending order).
+Describe the changes in terms of functions. Example: *n* and *m* of the *a* function are changed. Developers need to adapt their applications based on the change description.
+If there is a requirement or design document corresponding to the change, attach the requirement number or design document number in the description.
+
+**Change Impact**
+
+Describe whether released APIs (JS or native APIs) are affected or API behavior is changed.
+Describe whether available applications are affected, that is, whether an adaptation is required for building the application code in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+List the API/component changes involved in the function change.
+
+**Adaptation Guide**
+
+Provide guidance for developers on how to adapt their application to the changes to be compatible with the new version.
+Example:
+Change parameter *n* to *m* in the *a* file.
+
+```
+sample code
+```
diff --git a/en/release-notes/changelogs/v3.2-beta5/changelogs-ability.md b/en/release-notes/changelogs/v3.2-beta5/changelogs-ability.md
new file mode 100644
index 0000000000000000000000000000000000000000..e480077668e2a0e214720dd83ad07cf567956b87
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta5/changelogs-ability.md
@@ -0,0 +1,168 @@
+# Ability Framework Changelog
+
+## cl.ability.1 API Migration
+The **requestPermissionsFromUser** API of **UIAbilityContext** is migrated from the ability subsystem to the security subsystem.
+
+Previously, the permission popup was implemented based on **UIAbility**, which used the **startAbilityForResult** API of **UIAbilityContext** to return the permission authorization result to the caller. Therefore, **requestPermissionsFromUser** was temporarily placed in **UIAbilityContext**. The permission popup is now implemented based on **ServiceExtensionAbility**, which no longer requires **startAbilityForResult** of **UIAbilityContext**. Therefore, **requestPermissionsFromUser** is migrated to the security subsystem.
+
+You need to adapt your application based on the following information.
+
+ **Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enum/Constant                                         | Change Type|
+| ------------------------- | ------------------- | ------------------------------------------------------------ | -------- |
+| application/UIAbilityContext        | UIAbilityContext        | requestPermissionsFromUser(permissions: Array<string>, requestCallback: AsyncCallback<PermissionRequestResult>): void; | Deleted    |
+| application/UIAbilityContext        | UIAbilityContext        | requestPermissionsFromUser(permissions: Array<string>): Promise<PermissionRequestResult>; | Deleted    |
+| @ohos.abilityAccessCtrl        | AtManager         | requestPermissionsFromUser(context: Context, permissions: Array<Permissions>, requestCallback: AsyncCallback<PermissionRequestResult>) : void; | Added    |
+| @ohos.abilityAccessCtrl        | AtManager         | requestPermissionsFromUser(context: Context, permissions: Array<Permissions>) : Promise<PermissionRequestResult>; | Added    |
+
+
+**Adaptation Guide**
+
+The following illustrates how **requestPermissionsFromUser** is called to show a permission popup.
+
+Stage model:
+
+```ts
+import abilityAccessCtrl from '@ohos.abilityAccessCtrl.d.ts';
+// onWindowStageCreate lifecycle of UIAbility.
+onWindowStageCreate() {
+    let AtManager = abilityAccessCtrl.createAtManager();
+    // requestPermissionsFromUser determines whether to display a popup based on the permission authorization status.
+    AtManager.requestPermissionsFromUser(this.context, ["ohos.permission.MANAGE_DISPOSED_APP_STATUS"]).then((data) => {
+        console.log("data type:" + typeof(data));
+        console.log("data:" + data);
+        console.log("data permissions:" + data.permissions);
+        console.log("data result:" + data.authResults);
+    }).catch((err) => {
+        console.error('Failed to start ability', err.code);
+    })
+}
+```
+
+
+
+## cl.ability.2 Deletion of Deprecated APIs in API Version 9
+
+In the [Ability Exception Rectification](../OpenHarmony_3.2.8.3/changelogs-ability.md) document, some APIs in API version 9 have been marked as deprecated. According to API specifications of OpenHarmony, these APIs should be deleted.
+
+**Change Impact**
+
+The application developed based on earlier versions needs to use new APIs to replace the deleted ones. Otherwise, the application compilation will be affected.
+
+**Key API/Component Changes**
+
+API files are deleted.
+
+| Deleted API                                     | New API                                         |
+| ----------------------------------------------- | ----------------------------------------------- |
+| @ohos.application.Ability.d.ts                  | @ohos.app.ability.UIAbility.d.ts                |
+| @ohos.application.AbilityConstant.d.ts          | @ohos.app.ability.AbilityConstant.d.ts          |
+| @ohos.application.AbilityLifecycleCallback.d.ts | @ohos.app.ability.AbilityLifecycleCallback.d.ts |
+| @ohos.application.AbilityStage.d.ts             | @ohos.app.ability.AbilityStage.d.ts             |
+| @ohos.application.EnvironmentCallback.d.ts      | @ohos.app.ability.EnvironmentCallback.d.ts      |
+| @ohos.application.ExtensionAbility.d.ts         | @ohos.app.ability.ExtensionAbility.d.ts         |
+| @ohos.application.FormExtension.d.ts            | @ohos.app.form.FormExtensionAbility.d.ts        |
+| @ohos.application.ServiceExtensionAbility.d.ts  | @ohos.app.ability.ServiceExtensionAbility.d.ts  |
+| @ohos.application.StartOptions.d.ts             | @ohos.app.ability.StartOptions.d.ts             |
+| @ohos.application.context.d.ts                  | @ohos.app.ability.common.d.ts                   |
+| @ohos.application.errorManager.d.ts             | @ohos.app.ability.errorManager.d.ts             |
+
+APIs or attributes are deleted:
+
+- @ohos.application.Configuration.d.ts
+  - **direction**, **screenDensity**, **displayId**, and **hasPointerDevice** of **Configuration** are deleted. Use **Configuration** of **@ohos.app.ability.Configuration.d.ts**.
+- @ohos.application.ConfigurationConstant.d.ts
+  - **Direction** and **ScreenDensity** are deleted. Use **Direction** and **ScreenDensity** of **@ohos.app.ability.ConfigurationConstant.d.ts**.
+- @ohos.application.abilityManager.d.ts
+  - **getExtensionRunningInfos** and **getTopAbility** are deleted. Use the APIs with the same name in **@ohos.app.ability.abilityManager.d.ts**.
+- @ohos.application.appManager.d.ts
+  - **ApplicationState** and **ProcessState** are deleted. Use **ApplicationState** and **ProcessState** of **@ohos.app.ability.appManager.d.ts**.
+  - **registerApplicationStateObserver** and **getProcessRunningInformation** are deleted. Use the APIs with the same name in **@ohos.app.ability.appManager.d.ts**.
+- @ohos.application.formHost.d.ts
+  - **shareForm** and **notifyFormsPrivacyProtected** are deleted. Use the APIs with the same name in **@ohos.app.form.formHost.d.ts**.
+- @ohos.application.formInfo.d.ts
+  - **eTS** of **FormType** is deleted. Use **eTS** of **FormType** in **@ohos.app.form.formInfo.d.ts**.
+  - **IDENTITY_KEY**, **BUNDLE_NAME_KEY**, **ABILITY_NAME_KEY**, and **DEVICE_ID_KEY** of **FormParam** are deleted. Use the enums with the same name in **@ohos.app.form.formInfo.d.ts**.
+  - **FormInfoFilter** is deleted. Use **FormInfoFilter** of **@ohos.app.form.formInfo.d.ts**.
+  - **FormDimension** is deleted. Use **FormDimension** of **@ohos.app.form.formInfo.d.ts**.
+  - **VisibilityType** is deleted. Use **VisibilityType** of **@ohos.app.form.formInfo.d.ts**.
+- @ohos.wantAgent.d.ts
+  - **trigger** and **getOperationType** are deleted. Use the APIs with the same name in **@ohos.app.ability.wantAgent.d.ts**.
+- application/ApplicationContext.d.ts
+  - **registerAbilityLifecycleCallback**, **unregisterAbilityLifecycleCallback**, **registerEnvironmentCallback**, and **unregisterEnvironmentCallback** are deleted. Use **on** and **off**.
+- application/ServiceExtensionContext.d.ts
+  - **connectAbility**, **connectAbilityWithAccount**, and **disconnectAbility** are deleted. Use **connectServiceExtensionAbility**, **connectServiceExtensionAbilityWithAccount**, and **disconnectServiceExtensionAbility**.
+- @ohos.application.FormExtension.d.ts
+  - **onCreate**, **onCastToNormal**, **onUpdate**, **onVisibilityChange**, **onEvent**, **onDestroy**, **onAcquireFormState**, and **onShare** are deleted. Use the following lifecycle methods of **@ohos.app.form.FormExtensionAbility.d.ts**: **onAddForm**, **onCastToNormalForm**, **onUpdateForm**, **onChangeFormVisibility**, **onFormEvent**, **onRemoveForm**, **onAcquireFormState**, and **onShareForm**.
+- @ohos.application.abilityDelegatorRegistry.d.ts
+  - **AbilityDelegator**, **AbilityDelegatorArgs**, **AbilityMonitor**, and **ShellCmdResult** are deleted. Use the classes with the same name in **@ohos.app.ability.abilityDelegatorRegistry.d.ts**.
+- @ohos.application.abilityManager.d.ts
+  - **AbilityRunningInfo** and **ExtensionRunningInfo** are deleted. Use the classes with the same name in **@ohos.app.ability.abilityManager.d.ts**.
+- @ohos.application.appManager.d.ts
+  - **AbilityStateData**, **AppStateData**, **ApplicationStateObserver**, **ProcessRunningInfo**, and **ProcessRunningInformation** are deleted. Use the classes with the same name in **@ohos.app.ability.appManager.d.ts**.
+- @ohos.application.missionManager.d.ts
+  - **MissionInfo**, **MissionListener**, and **MissionSnapshot** are deleted. Use the classes with the same name in **@ohos.app.ability.missionManager.d.ts**.
+- @ohos.wantAgent.d.ts
+  - **TriggerInfo** and **WantAgentInfo** are deleted. Use the classes with the same name in **@ohos.app.ability.wantAgent.d.ts**.
+
+**Adaptation Guide**
+
+As mentioned above, only several APIs have their names changed in terms of, for example, the registration callbacks (**registerAbilityLifecycleCallback**, **unregisterAbilityLifecycleCallback**, **registerEnvironmentCallback**, and **unregisterEnvironmentCallback**) and connection and disconnection **ServiceExtensionAbility** (**connectAbility**, **connectAbilityWithAccount**, and **disconnectAbility**). For such APIs, replace their names with those of their corresponding new APIs in the lifecycle callbacks.
+
+Most APIs are moved to the new namespace. Therefore, you can modify **import** for adaptation.
+
+For example, the original API uses **@ohos.application.Ability**:
+
+```js
+import Ability from '@ohos.application.Ability';
+```
+
+You can directly modify **import** to switch to the new namespace:
+
+```js
+import Ability from '@ohos.app.ability.UIAbility';
+```
+
+In addition, exception handling is needed. For details, see the API reference for the new APIs.
+
+## cl.ability.2 RestartFlag Attribute Names Changed and Unsupported Attribute Deleted in appRecovery
+
+In the **appRecovery** API, the enum names of **RestartFlag** are changed from **NO_RESTART** upon a specific fault to **RESTART** upon a specific fault. 
+The **CPP_CRASH_NO_RESTART** enum is deleted.
+
+**Change Impact**
+
+If your application uses the **CPP_CRASH_NO_RESTART**, **JS_CRASH_NO_RESTART**, or **APP_FREEZE_NO_RESTART** attribute in versions earlier than 3.2.10.6, its behavior will change after an upgrade to 3.2.10.6.
+
+**Key API/Component Changes**
+
+**RestartFlag** <sup>9+</sup>
+
+Before change
+
+| Name                 | Value    | Description                            |
+| --------------------- | ------ | -------------------------------- |
+| ALWAYS_RESTART        | 0      | The application is restarted in all cases.                  |
+| CPP_CRASH_NO_RESTART  | 0x0001 | The application is **not restarted** in the case of CPP_CRASH. |
+| JS_CRASH_NO_RESTART   | 0x0002 | The application is **not restarted** in the case of JS_CRASH.  |
+| APP_FREEZE_NO_RESTART | 0x0004 | The application is **not restarted** in the case of APP_FREEZE.|
+| NO_RESTART            | 0xFFFF | The application is not restarted in any case.                |
+
+After change
+
+| Name                   | Value    | Description                          |
+| ----------------------- | ------ | ------------------------------ |
+| ALWAYS_RESTART          | 0      | The application is restarted in all cases.                |
+| CPP_CRASH_NO_RESTART    | NA     | **Deleted.** The restart in this scenario is not supported.|
+| RESTART_WHEN_JS_CRASH   | 0x0001 | The application is **restarted** in the case of JS_CRASH.  |
+| RESTART_WHEN_APP_FREEZE | 0x0002 | The application is **restarted** in the case of APP_FREEZE.|
+| NO_RESTART              | 0xFFFF | The application is not restarted in any case.              |
+
+**Adaptation Guide**
+
+Perform adaptation based on the new semantics.
diff --git a/en/release-notes/changelogs/v3.2-beta5/changelogs-camera-sync.md b/en/release-notes/changelogs/v3.2-beta5/changelogs-camera-sync.md
new file mode 100644
index 0000000000000000000000000000000000000000..ef66b7500c4b5fccde024c10c95beeca5b6cbd5d
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta5/changelogs-camera-sync.md
@@ -0,0 +1,520 @@
+# Multimedia Subsystem Changelog
+
+## cl.subsystemname.1 Camera API Changed
+1. All the APIs of the camera component are changed to system APIs in the API version 9.
+2. Some functional APIs are added and some others are deprecated to:
+
+Improve the usability of camera APIs.
+Help you quickly understand camera APIs and use them for development.
+Facilitate expansion of framework functions in later versions, and reduce coupling between framework modules.
+
+You need to refer to the following change description to adapt your application.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                | Class                   | Method/Attribute/Enum/Constant                                         | Is System API| Change Type|
+| ---------------------- | ----------------------- | ------------------------------------------------------------ | --------------- | -------- |
+| ohos.multimedia.camera | camera                  | function getCameraManager(context: Context): CameraManager;  | Yes             | Added    |
+| ohos.multimedia.camera | camera                  | function getCameraManager(context: Context, callback: AsyncCallback<CameraManager>): void;<br>function getCameraManager(context: Context): Promise<CameraManager>;       | Yes             | Deprecated    |
+| ohos.multimedia.camera | CameraErrorCode         | INVALID_ARGUMENT = 7400101,<br>OPERATION_NOT_ALLOWED = 7400102,<br>SESSION_NOT_CONFIG = 7400103,<br>SESSION_NOT_RUNNING = 7400104,<br>SESSION_CONFIG_LOCKED = 7400105,<br>DEVICE_SETTING_LOCKED = 7400106,<br>CONFILICT_CAMERA = 7400107,<br>DEVICE_DISABLED = 7400108,<br>SERVICE_FATAL_ERROR = 7400201                                                      | Yes             | Added    |
+| ohos.multimedia.camera | CameraManager           | getSupportedCameras(): Array<CameraDevice>;<br>getSupportedOutputCapability(camera: CameraDevice): CameraOutputCapability;<br>createCameraInput(camera: CameraDevice): CameraInput;<br>createCameraInput(position: CameraPosition, type: CameraType): CameraInput;<br>createPreviewOutput(profile: Profile, surfaceId: string): PreviewOutput;<br>createPhotoOutput(profile: Profile, surfaceId: string): PhotoOutput;<br>createVideoOutput(profile: VideoProfile, surfaceId: string): VideoOutput;<br>createMetadataOutput(metadataObjectTypes: Array<MetadataObjectType>): MetadataOutput;<br>createCaptureSession(): CaptureSession;                                 | Yes             | Added    |
+| ohos.multimedia.camera | CameraManager           | getSupportedCameras(callback: AsyncCallback<Array<CameraDevice>>): void;<br>getSupportedCameras(): Promise<Array<CameraDevice>>;<br>getSupportedOutputCapability(camera: CameraDevice, callback: AsyncCallback<CameraOutputCapability>): void;<br>getSupportedOutputCapability(camera: CameraDevice): Promise<CameraOutputCapability>;<br>createCameraInput(camera: CameraDevice, callback: AsyncCallback<CameraInput>): void;<br>createCameraInput(camera: CameraDevice): Promise<CameraInput>;<br>createCameraInput(position: CameraPosition, type: CameraType, callback: AsyncCallback<CameraInput>): void;<br>createCameraInput(position: CameraPosition, type: CameraType): Promise<CameraInput>;<br>createPreviewOutput(profile: Profile, surfaceId: string, callback: AsyncCallback<PreviewOutput>): void;<br>createPreviewOutput(profile: Profile, surfaceId: string): Promise<PreviewOutput>;<br>createPhotoOutput(profile: Profile, surfaceId: string, callback: AsyncCallback<PhotoOutput>): void;<br>createPhotoOutput(profile: Profile, surfaceId: string): Promise<PhotoOutput>;<br>createVideoOutput(profile: VideoProfile, surfaceId: string, callback: AsyncCallback<VideoOutput>): void;<br>createVideoOutput(profile: VideoProfile, surfaceId: string): Promise<VideoOutput>;<br>createMetadataOutput(metadataObjectTypes: Array<MetadataObjectType>, callback: AsyncCallback<MetadataOutput>): void;<br>createMetadataOutput(metadataObjectTypes: Array<MetadataObjectType>): Promise<MetadataOutput>;<br>createCaptureSession(callback: AsyncCallback<CaptureSession>): void;<br>createCaptureSession(): Promise<CaptureSession>; | Yes             | Deprecated    |
+| ohos.multimedia.camera | CameraType              | CAMERA_TYPE_DEFAULT = 0                                                                           | Yes             | Added    |
+| ohos.multimedia.camera | CameraType              | CAMERA_TYPE_UNSPECIFIED = 0                                                                       | Yes             | Deprecated    |
+| ohos.multimedia.camera | CameraInput             | on(type: 'error', camera: CameraDevice, callback: ErrorCallback<BusinessError>): void;            | Yes             | Added    |
+| ohos.multimedia.camera | CameraInput             | release(callback: AsyncCallback<void>): void;<br>release(): Promise<void>;<br>on(type: 'error', camera: CameraDevice, callback: ErrorCallback<CameraInputError>): void; | Yes             | Deprecated    |
+| ohos.multimedia.camera | CameraInputErrorCode    | ERROR_UNKNOWN = -1<br>ERROR_NO_PERMISSION = 0<br>ERROR_DEVICE_PREEMPTED = 1<br>ERROR_DEVICE_DISCONNECTED = 2<br>ERROR_DEVICE_IN_USE = 3<br>ERROR_DRIVER_ERROR = 4    | Yes             | Deprecated    |
+| ohos.multimedia.camera | CameraInputError        | code: CameraInputErrorCode                                                                        | Yes             | Deprecated    |
+| ohos.multimedia.camera | CaptureSession          | beginConfig(): void;<br>addInput(cameraInput: CameraInput): void;<br>removeInput(cameraInput: CameraInput): void;<br>addOutput(cameraOutput: CameraOutput): void;<br>removeOutput(cameraOutput: CameraOutput): void;<br>hasFlash(): boolean;<br>isFlashModeSupported(flashMode: FlashMode): boolean;<br>getFlashMode(): FlashMode;<br>setFlashMode(flashMode: FlashMode): void;<br>isExposureModeSupported(aeMode: ExposureMode): boolean;<br>getExposureMode(): ExposureMode;<br>setExposureMode(aeMode: ExposureMode): void;<br>getMeteringPoint(): Point;<br>setMeteringPoint(point: Point): void;<br>getExposureBiasRange(): Array<number>;<br>setExposureBias(exposureBias: number): void;<br>getExposureValue(): number;<br>isFocusModeSupported(afMode: FocusMode): boolean;<br>getFocusMode(): FocusMode;<br>setFocusMode(afMode: FocusMode): void;<br>setFocusPoint(point: Point): void;<br>getFocusPoint(): Point;<br>getFocalLength(): number;<br>getZoomRatioRange(): Array<number>;<br>getZoomRatio(): number;<br>setZoomRatio(zoomRatio: number): void;<br>isVideoStabilizationModeSupported(vsMode: VideoStabilizationMode): boolean;<br>getActiveVideoStabilizationMode(): VideoStabilizationMode;<br>setVideoStabilizationMode(mode: VideoStabilizationMode): void;<br>on(type: 'error', callback: ErrorCallback<BusinessError>): void;                             | Yes             | Added    |
+| ohos.multimedia.camera | CaptureSession          | beginConfig(callback: AsyncCallback<void>): void;<br>beginConfig(): Promise<void>;<br>addInput(cameraInput: CameraInput, callback: AsyncCallback<void>): void;<br>addInput(cameraInput: CameraInput): Promise<void>;<br>removeInput(cameraInput: CameraInput, callback: AsyncCallback<void>): void;<br>removeInput(cameraInput: CameraInput): Promise<void>;<br>addOutput(cameraOutput: CameraOutput, callback: AsyncCallback<void>): void;<br>addOutput(cameraOutput: CameraOutput): Promise<void>;<br>removeOutput(cameraOutput: CameraOutput, callback: AsyncCallback<void>): void;<br>removeOutput(cameraOutput: CameraOutput): Promise<void>;<br>hasFlash(callback: AsyncCallback<boolean>): void;<br>hasFlash(): Promise<boolean>;<br>isFlashModeSupported(flashMode: FlashMode, callback: AsyncCallback<boolean>): void;<br>isFlashModeSupported(flashMode: FlashMode): Promise<boolean>;<br>getFlashMode(callback: AsyncCallback<FlashMode>): void;<br>getFlashMode(): Promise<FlashMode>;<br>setFlashMode(flashMode: FlashMode, callback: AsyncCallback<void>): void;<br>setFlashMode(flashMode: FlashMode): Promise<void>;<br>isExposureModeSupported(aeMode: ExposureMode, callback: AsyncCallback<boolean>): void;<br>isExposureModeSupported(aeMode: ExposureMode): Promise<boolean>;<br>getExposureMode(callback: AsyncCallback<ExposureMode>): void;<br>getExposureMode(): Promise<ExposureMode>;<br>setExposureMode(aeMode: ExposureMode, callback: AsyncCallback<void>): void;<br>setExposureMode(aeMode: ExposureMode): Promise<void>;<br>getMeteringPoint(callback: AsyncCallback<Point>): void;<br>getMeteringPoint(): Promise<Point>;<br>setMeteringPoint(point: Point, callback: AsyncCallback<void>): void;<br>setMeteringPoint(point: Point): Promise<void>;<br>getExposureBiasRange(callback: AsyncCallback<Array<number>>): void;<br>getExposureBiasRange(): Promise<Array<number>>;<br>setExposureBias(exposureBias: number, callback: AsyncCallback<void>): void;<br>setExposureBias(exposureBias: number): Promise<void>;<br>getExposureValue(callback: AsyncCallback<number>): void;<br>getExposureValue(): Promise<number>;<br>isFocusModeSupported(afMode: FocusMode, callback: AsyncCallback<boolean>): void;<br>isFocusModeSupported(afMode: FocusMode): Promise<boolean>;<br>getFocusMode(callback: AsyncCallback<FocusMode>): void;<br>getFocusMode(): Promise<FocusMode>;<br>setFocusMode(afMode: FocusMode, callback: AsyncCallback<void>): void;<br>setFocusMode(afMode: FocusMode): Promise<void>;<br>setFocusPoint(point: Point, callback: AsyncCallback<void>): void;<br>setFocusPoint(point: Point): Promise<void>;<br>getFocusPoint(callback: AsyncCallback<Point>): void;<br>getFocusPoint(): Promise<Point>;<br>getFocalLength(callback: AsyncCallback<number>): void;<br>getFocalLength(): Promise<number>;<br>getZoomRatioRange(callback: AsyncCallback<Array<number>>): void;<br>getZoomRatioRange(): Promise<Array<number>>;<br>getZoomRatio(callback: AsyncCallback<number>): void;<br>getZoomRatio(): Promise<number>;<br>setZoomRatio(zoomRatio: number, callback: AsyncCallback<void>): void;<br>setZoomRatio(zoomRatio: number): Promise<void>;<br>isVideoStabilizationModeSupported(vsMode: VideoStabilizationMode, callback: AsyncCallback<boolean>): void;<br>isVideoStabilizationModeSupported(vsMode: VideoStabilizationMode): Promise<boolean>;<br>getActiveVideoStabilizationMode(callback: AsyncCallback<VideoStabilizationMode>): void;<br>getActiveVideoStabilizationMode(): Promise<VideoStabilizationMode>;<br>setVideoStabilizationMode(mode: VideoStabilizationMode, callback: AsyncCallback<void>): void;<br>setVideoStabilizationMode(mode: VideoStabilizationMode): Promise<void>;<br>on(type: 'error', callback: ErrorCallback<CaptureSessionError>): void;                                     | Yes             | Deprecated    |
+| ohos.multimedia.camera | CaptureSessionErrorCode | ERROR_UNKNOWN = -1<br>ERROR_INSUFFICIENT_RESOURCES = 0<br>ERROR_TIMEOUT = 1  | Yes             | Deprecated    |
+| ohos.multimedia.camera | CaptureSessionError     | code: CaptureSessionErrorCode                                                  | Yes             | Deprecated    |
+| ohos.multimedia.camera | PreviewOutput           | on(type: 'error', callback: ErrorCallback<BusinessError>): void;               | Yes             | Added    |
+| ohos.multimedia.camera | PreviewOutput           | on(type: 'error', callback: ErrorCallback<PreviewOutputError>): void;          | Yes             | Deprecated    |
+| ohos.multimedia.camera | PreviewOutputErrorCode  | ERROR_UNKNOWN = -1                                                             | Yes             | Deprecated    |
+| ohos.multimedia.camera | PreviewOutputError      | code: PreviewOutputErrorCode                                                   | Yes             | Deprecated    |
+| ohos.multimedia.camera | PhotoOutput             | capture(): Promise<void>;<br>isMirrorSupported(): boolean;<br>on(type: 'error', callback: ErrorCallback<BusinessError>): void;                                              | Yes             | Added    |
+| ohos.multimedia.camera | PhotoOutput             | isMirrorSupported(callback: AsyncCallback<boolean>): void;<br>isMirrorSupported(): Promise<boolean>;<br>on(type: 'error', callback: ErrorCallback<PhotoOutputError>): void; | Yes             | Deprecated    |
+| ohos.multimedia.camera | PhotoOutputErrorCode    | ERROR_UNKNOWN = -1<br>ERROR_DRIVER_ERROR = 0<br>ERROR_INSUFFICIENT_RESOURCES = 1<br>ERROR_TIMEOUT = 2 | Yes             | Deprecated    |
+| ohos.multimedia.camera | PhotoOutputError        | code: PhotoOutputErrorCode                                                                               | Yes             | Deprecated    |
+| ohos.multimedia.camera | VideoOutput             | on(type: 'error', callback: ErrorCallback<BusinessError>): void;                                         | Yes             | Added    |
+| ohos.multimedia.camera | VideoOutput             | on(type: 'error', callback: ErrorCallback<VideoOutputError>): void;                                      | Yes             | Deprecated    |
+| ohos.multimedia.camera | VideoOutputErrorCode    | ERROR_UNKNOWN = -1<br>ERROR_DRIVER_ERROR = 0                                                            | Yes             | Deprecated    |
+| ohos.multimedia.camera | VideoOutputError        | code: VideoOutputErrorCode                                                                               | Yes             | Deprecated    |
+| ohos.multimedia.camera | MetadataObject          | readonly type: MetadataObjectType;<br>readonly timestamp: number;                                       | Yes             | Added    |
+| ohos.multimedia.camera | MetadataObject          | getType(callback: AsyncCallback<MetadataObjectType>): void;<br>getType(): Promise<MetadataObjectType>;<br>getTimestamp(callback: AsyncCallback<number>): void;<br>getTimestamp(): Promise<number>;<br>getBoundingBox(callback: AsyncCallback<Rect>): void;<br>getBoundingBox(): Promise<Rect>;                                                                                  | Yes             | Deprecated    |
+| ohos.multimedia.camera | MetadataFaceObject      | readonly boundingBox: Rect                                       | Yes             | Added    |
+| ohos.multimedia.camera | MetadataOutput          | on(type: 'error', callback: ErrorCallback<BusinessError>): void; | Yes             | Added    |
+| ohos.multimedia.camera | MetadataOutput          | on(type: 'error', callback: ErrorCallback<BusinessError>): void; | Yes             | Deprecated    |
+| ohos.multimedia.camera | MetadataOutputErrorCode | ERROR_UNKNOWN = -1<br>ERROR_INSUFFICIENT_RESOURCES = 0          | Yes             | Deprecated    |
+| ohos.multimedia.camera | MetadataOutputError     | code: MetadataOutputErrorCode                                    | Yes             | Deprecated    |
+
+**Adaptation Guide**
+
+In addition to new APIs and deprecated APIs, you need to adapt your application to changed APIs.
+
+In Beta4 and later versions, the following APIs are changed.
+
+**New APIs**
+
+1. **CameraErrorCode** enums
+
+   Enum: INVALID_ARGUMENT; value: 7400101
+
+   Enum: OPERATION_NOT_ALLOWED; value: 7400102
+   
+   Enum: SESSION_NOT_CONFIG; value: 7400103
+   
+   Enum: SESSION_NOT_RUNNING; value: 7400104
+   
+   Enum: SESSION_CONFIG_LOCKED; value: 7400105
+   
+   Enum: DEVICE_SETTING_LOCKED; value: 7400106
+   
+   Enum: CONFILICT_CAMERA; value: 7400107
+   
+   Enum: DEVICE_DISABLED; value: 7400108
+   
+   Enum: SERVICE_FATAL_ERROR; value: 7400201
+
+2. Added **capture(): Promise<void>** to the **PhotoOutput** API.
+
+3. Added the readonly type **MetadataObjectType** to the **MetadataObject** API.
+
+4. Added **readonly timestamp: number** to the **MetadataObject** API.
+
+5. Added **readonly boundingBox: Rect** to the **MetadataObject** API.
+
+**Deprecated APIs**
+
+1. Deprecated the **release(callback: AsyncCallback<void>): void** and **release(): Promise<void>** APIs in **CameraInput**.
+
+2. Deprecated the **CameraInputErrorCode** enums and all their values: **ERROR_UNKNOWN** = **-1**, **ERROR_NO_PERMISSION** = **0**, **ERROR_DEVICE_PREEMPTED** = **1**, **ERROR_DEVICE_DISCONNECTED** = **2**, **ERROR_DEVICE_IN_USE** = **3**, **ERROR_DRIVER_ERROR** = **4**
+
+3. Deprecated the **CameraInputError** API and its attribute **CameraInputErrorCode**.
+
+4. Deprecated the **CaptureSessionErrorCode** enums and all their values: **ERROR_UNKNOWN** = **-1**, **ERROR_INSUFFICIENT_RESOURCES** = **0**, **ERROR_TIMEOUT** = **1**
+
+5. Deprecated the **CaptureSessionError** API and its attribute **CaptureSessionErrorCode**.
+
+6. Deprecated the **PreviewOutputErrorCode** enum and its value: **ERROR_UNKNOWN** = **-1**
+
+7. Deprecated the **PreviewOutputError** API and its attribute **PreviewOutputErrorCode**.
+
+8. Deprecated the **PhotoOutputErrorCode** enums and all their values: **ERROR_UNKNOWN** = **-1**, **ERROR_DRIVER_ERROR** = **0**, **ERROR_INSUFFICIENT_RESOURCES** = **1**, **ERROR_TIMEOUT** = **2**
+
+9. Deprecated the **PhotoOutputError** API and its attribute **PhotoOutputErrorCode**.
+
+10. Deprecated the **VideoOutputErrorCode** enums and all their values: **ERROR_UNKNOWN** = **-1**, **ERROR_DRIVER_ERROR** = **0**
+
+11. Deprecated the **VideoOutputError** API and its attribute **VideoOutputErrorCode**.
+
+12. Deprecated **getType(callback: AsyncCallback<MetadataObjectType>): void** in the **MetadataObject** API.
+
+13. Deprecated **getType(): Promise<MetadataObjectType>** in the **MetadataObject** API.
+
+14. Deprecated **getTimestamp(callback: AsyncCallback<number>): void** in the **MetadataObject** API.
+
+15. Deprecated **getTimestamp(): Promise<number>** in the **MetadataObject** API.
+
+16. Deprecated **getBoundingBox(callback: AsyncCallback<Rect>): void** in the **MetadataObject** API.
+
+17. Deprecated **getBoundingBox(): Promise<Rect>** in the **MetadataObject** API.
+
+18. Deprecated the **MetadataOutputErrorCode** enums and all their values: **ERROR_UNKNOWN** = **-1**, **ERROR_INSUFFICIENT_RESOURCES** = **0**
+
+19. Deprecated the **MetadataOutputError** API and its attribute **MetadataOutputErrorCode**.
+
+**Changed APIs**
+
+1. Changed the return modes of the **getCameraManager** API in the camera module from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getCameraManager(context: Context, callback: AsyncCallback<CameraManager>): void** and **getCameraManager(context: Context): Promise<CameraManager>** are changed to **getCameraManager(context: Context): CameraManager**.
+
+   The code snippet is as follows:
+
+   ```
+   let cameraManager = camera.getCameraManager(context);
+   ```
+   
+2. Changed the return modes of the **getSupportedCameras** API in CameraManager from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getSupportedCameras(callback: AsyncCallback<Array<CameraDevice>>): void** and **getSupportedCameras(): Promise<Array<CameraDevice>>** are changed to **getSupportedCameras(): Array<CameraDevice>**.
+
+   The code snippet is as follows:
+
+   ```
+   let cameras = cameraManager.getSupportedCameras();
+   ```
+   
+3. Changed the return modes of the **getSupportedOutputCapability** API in CameraManager from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getSupportedOutputCapability(camera: CameraDevice, callback: AsyncCallback<CameraOutputCapability>): void** and **getSupportedOutputCapability(camera: CameraDevice): Promise<CameraOutputCapability>** are changed to **getSupportedOutputCapability(camera: CameraDevice): CameraOutputCapability**.
+
+   The code snippet is as follows:
+   
+   ```
+   let cameraDevice = cameras[0];
+   let CameraOutputCapability = cameraManager.getSupportedOutputCapability(cameraDevice);
+   ```
+   
+4. Changed the return modes of the **createCameraInput(camera: CameraDevice)** API in CameraManager from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **createCameraInput(camera: CameraDevice, callback: AsyncCallback<CameraInput>): void** and **createCameraInput(camera: CameraDevice): Promise<CameraInput>** are changed to **createCameraInput(camera: CameraDevice): CameraInput**.
+
+   The code snippet is as follows:
+   
+   ```
+   let cameraDevice = cameras[0];
+   let cameraInput = cameraManager.createCameraInput(cameraDevice);
+   ```
+   
+5. Changed the return modes of the **createCameraInput(position: CameraPosition, type: CameraType)** API in CameraManager from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **createCameraInput(position: CameraPosition, type: CameraType, callback: AsyncCallback<CameraInput>): void** and **createCameraInput(position: CameraPosition, type: CameraType): Promise<CameraInput>** are changed to **createCameraInput(position: CameraPosition, type: CameraType): CameraInput**.
+
+   The code snippet is as follows:
+   
+   ```
+   let cameraDevice = cameras[0];
+   let position = cameraDevice.cameraPosition;
+   let type = cameraDevice.cameraType;
+   let cameraInput = cameraManager.createCameraInput(position, type);
+   ```
+   
+6. Changed the return modes of the **createPreviewOutput** API in CameraManager from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **createPreviewOutput(profile: Profile, surfaceId: string, callback: AsyncCallback<PreviewOutput>): void** and **createPreviewOutput(profile: Profile, surfaceId: string): Promise<PreviewOutput>** are changed to **createPreviewOutput(profile: Profile, surfaceId: string): PreviewOutput**.
+
+   The code snippet is as follows:
+   
+   ```
+   let profile = cameraoutputcapability.previewProfiles[0];
+   let previewOutput = cameraManager.createPreviewOutput(profile, surfaceId);
+   ```
+   
+7. Changed the return modes of the **createPhotoOutput** API in CameraManager from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **createPhotoOutput(profile: Profile, surfaceId: string, callback: AsyncCallback<PhotoOutput>): void** and **createPhotoOutput(profile: Profile, surfaceId: string): Promise<PhotoOutput>** are changed to **createPhotoOutput(profile: Profile, surfaceId: string): PhotoOutput**.
+
+   The code snippet is as follows:
+   
+   ```
+   let profile = cameraoutputcapability.photoProfiles[0];
+   let photoOutput = cameraManager.createPhotoOutput(profile, surfaceId);
+   ```
+   
+8. Changed the return modes of the **createVideoOutput** API in CameraManager from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **createVideoOutput(profile: VideoProfile, surfaceId: string, callback: AsyncCallback<VideoOutput>): void** and **createVideoOutput(profile: VideoProfile, surfaceId: string): Promise<VideoOutput>** are changed to **createVideoOutput(profile: VideoProfile, surfaceId: string): VideoOutput**.
+
+   The code snippet is as follows:
+   
+   ```
+   let profile = cameraoutputcapability.videoProfiles[0];
+   let videoOutput = cameraManager.createVideoOutput(profile, surfaceId);
+   ```
+   
+9. Changed the return modes of the **createMetadataOutput** API in CameraManager from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **createMetadataOutput(metadataObjectTypes: Array<MetadataObjectType>, callback: AsyncCallback<MetadataOutput>): void** and **createMetadataOutput(metadataObjectTypes: Array<MetadataObjectType>): Promise<MetadataOutput>** are changed to **createMetadataOutput(metadataObjectTypes: Array<MetadataObjectType>): MetadataOutput**.
+
+   The code snippet is as follows:
+   
+   ```
+   let metadataObjectTypes = cameraoutputcapability.supportedMetadataObjectTypes;
+   let metadataOutput = cameraManager.createMetadataOutput(metadataObjectTypes);
+   ```
+   
+10. Changed the return modes of the **createCaptureSession** API in CameraManager from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **createCaptureSession(callback: AsyncCallback<CaptureSession>): void** and **createCaptureSession(): Promise<CaptureSession>** are changed to **createCaptureSession(): CaptureSession**.
+
+    The code snippet is as follows:
+
+       ```
+    let captureSession = cameraManager.createCaptureSession();
+       ```
+
+11. Changed the enum **CAMERA_TYPE_UNSPECIFIED** of **CameraType** to **CAMERA_TYPE_DEFAULT**.
+
+12. Changed the return value type of the **on** API in CameraInput from **CameraInputError** to **BusinessError**. Therefore, the original API **on(type: 'error', camera: CameraDevice, callback: ErrorCallback<CameraInputError>): void** is changed to **on(type: 'error', camera: CameraDevice, callback: ErrorCallback<BusinessError>): void**.
+
+    The code snippet is as follows:
+
+       ```
+    let cameraDevice = cameras[0];
+    cameraInput.on('error', cameraDevice, (BusinessError) => {
+    
+    })
+       ```
+
+13. Changed the return modes of the **beginConfig** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **beginConfig(callback: AsyncCallback<void>): void** and **beginConfig(): Promise<void>** are changed to **beginConfig(): void**.
+
+    The code snippet is as follows:
+
+       ```
+    captureSession.beginConfig();
+       ```
+
+14. Changed the return modes of the **addInput** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **addInput(cameraInput: CameraInput, callback: AsyncCallback<void>): void** and **addInput(cameraInput: CameraInput): Promise<void>** are changed to **addInput(cameraInput: CameraInput): void**.
+
+    The code snippet is as follows:
+
+       ```
+    captureSession.addInput(cameraInput);
+       ```
+
+15. Changed the return modes of the **removeInput** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **removeInput(cameraInput: CameraInput, callback: AsyncCallback<void>): void** and **removeInput(cameraInput: CameraInput): Promise<void>** are changed to **removeInput(cameraInput: CameraInput): void**.
+
+    The code snippet is as follows:
+
+       ```
+    captureSession.removeInput(cameraInput);
+       ```
+
+16. Changed the return modes of the **addOutput** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **addOutput(cameraOutput: CameraOutput, callback: AsyncCallback<void>): void** and **addOutput(cameraOutput: CameraOutput): Promise<void>** are changed to **addOutput(cameraOutput: CameraOutput): void**.
+
+    The code snippet is as follows:
+
+       ```
+    captureSession.addOutput(previewOutput);
+       ```
+
+17. Changed the return modes of the **removeOutput** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **removeOutput(cameraOutput: CameraOutput, callback: AsyncCallback<void>): void** and **removeOutput(cameraOutput: CameraOutput): Promise<void>** are changed to **removeOutput(cameraOutput: CameraOutput): void**.
+
+    The code snippet is as follows:
+
+       ```
+    captureSession.removeOutput(previewOutput);
+       ```
+
+18. Changed the return modes of the **hasFlash** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **hasFlash(callback: AsyncCallback<boolean>): void** and **hasFlash(): Promise<boolean>** are changed to **hasFlash(): boolean**.
+
+    The code snippet is as follows:
+
+       ```
+    let status = captureSession.hasFlash();
+       ```
+
+19. Changed the return modes of the **isFlashModeSupported** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **isFlashModeSupported(flashMode: FlashMode, callback: AsyncCallback<boolean>): void** and **isFlashModeSupported(flashMode: FlashMode): Promise<boolean>** are changed to **isFlashModeSupported(flashMode: FlashMode): boolean**.
+
+    The code snippet is as follows:
+
+       ```
+    let status = captureSession.isFlashModeSupported(camera.FlashMode.FLASH_MODE_AUTO);
+       ```
+
+20. Changed the return modes of the **getFlashMode** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getFlashMode(callback: AsyncCallback<FlashMode>): void** and **getFlashMode(): Promise<FlashMode>** are changed to **getFlashMode(): FlashMode**.
+
+    The code snippet is as follows:
+
+       ```
+    let flashMode = captureSession.getFlashMode();
+       ```
+
+21. Changed the return modes of the **isExposureModeSupported** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **isExposureModeSupported(aeMode: ExposureMode, callback: AsyncCallback<boolean>): void** and **isExposureModeSupported(aeMode: ExposureMode): Promise<boolean>** are changed to **isExposureModeSupported(aeMode: ExposureMode): boolean**.
+
+    The code snippet is as follows:
+
+       ```
+    let isSupported = captureSession.isExposureModeSupported(camera.ExposureMode.EXPOSURE_MODE_LOCKED);
+       ```
+
+22. Changed the return modes of the **getExposureMode** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getExposureMode(callback: AsyncCallback<ExposureMode>): void** and **getExposureMode(): Promise<ExposureMode>** are changed to **getExposureMode(): ExposureMode**.
+
+    The code snippet is as follows:
+
+       ```
+    let exposureMode = captureSession.getExposureMode();
+       ```
+
+23. Changed the return modes of the **setExposureMode** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **setExposureMode(aeMode: ExposureMode, callback: AsyncCallback<void>): void** and **setExposureMode(aeMode: ExposureMode): Promise<void>** are changed to **setExposureMode(aeMode: ExposureMode): void**.
+
+    The code snippet is as follows:
+
+       ```
+    captureSession.setExposureMode(camera.ExposureMode.EXPOSURE_MODE_LOCKED);
+       ```
+
+24. Changed the return modes of the **getMeteringPoint** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getMeteringPoint(callback: AsyncCallback<Point>): void** and **getMeteringPoint(): Promise<Point>** are changed to **getMeteringPoint(): Point**.
+
+    The code snippet is as follows:
+
+       ```
+    let exposurePoint = captureSession.getMeteringPoint();
+       ```
+
+25. Changed the return modes of the **setMeteringPoint** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **setMeteringPoint(point: Point, callback: AsyncCallback<void>): void** and **setMeteringPoint(point: Point): Promise<void>** are changed to **setMeteringPoint(point: Point): void**.
+
+    The code snippet is as follows:
+
+       ```
+    let Point2 = {x: 2, y: 2};
+    captureSession.setMeteringPoint(Point2);
+       ```
+
+26. Changed the return modes of the **getExposureBiasRange** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getExposureBiasRange(callback: AsyncCallback<Array<number>>): void** and **getExposureBiasRange(): Promise<Array<number>>** are changed to **getExposureBiasRange(): Array<number>**.
+
+    The code snippet is as follows:
+
+       ```
+    let biasRangeArray = captureSession.getExposureBiasRange();
+       ```
+
+27. Changed the return modes of the **setExposureBias** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **setExposureBias(exposureBias: number, callback: AsyncCallback<void>): void** and **setExposureBias(exposureBias: number): Promise<void>** are changed to **setExposureBias(exposureBias: number): void**.
+
+    The code snippet is as follows:
+
+       ```
+    let exposureBias = biasRangeArray[0];
+    captureSession.setExposureBias(exposureBias);
+       ```
+
+28. Changed the return modes of the **getExposureValue** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getExposureValue(callback: AsyncCallback<number>): void** and **getExposureValue(): Promise<number>** are changed to **getExposureValue(): number**.
+
+    The code snippet is as follows:
+
+       ```
+    let exposureValue = captureSession.getExposureValue();
+       ```
+
+29. Changed the return modes of the **isFocusModeSupported** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **isFocusModeSupported(afMode: FocusMode, callback: AsyncCallback<boolean>): void** and **isFocusModeSupported(afMode: FocusMode): Promise<boolean>** are changed to **isFocusModeSupported(afMode: FocusMode): boolean**.
+
+    The code snippet is as follows:
+
+       ```
+    let status = captureSession.isFocusModeSupported(camera.FocusMode.FOCUS_MODE_AUTO);
+       ```
+
+30. Changed the return modes of the **getFocusMode** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getFocusMode(callback: AsyncCallback<FocusMode>): void** and **getFocusMode(): Promise<FocusMode>** are changed to **getFocusMode(): FocusMode**.
+
+    The code snippet is as follows:
+
+       ```
+    let afMode = captureSession.getFocusMode();
+       ```
+
+31. Changed the return modes of the **setFocusMode** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **setFocusMode(afMode: FocusMode, callback: AsyncCallback<void>): void** and **setFocusMode(afMode: FocusMode): Promise<void>** are changed to **setFocusMode(afMode: FocusMode): void**.
+
+    The code snippet is as follows:
+
+       ```
+    captureSession.setFocusMode(camera.FocusMode.FOCUS_MODE_AUTO);
+       ```
+
+32. Changed the return modes of the **setFocusPoint** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **setFocusPoint(point: Point, callback: AsyncCallback<void>): void** and **setFocusPoint(point: Point): Promise<void>** are changed to **setFocusPoint(point: Point): void**.
+
+    The code snippet is as follows:
+
+       ```
+    let Point2 = {x: 2, y: 2};
+    captureSession.setFocusPoint(Point2);
+       ```
+
+33. Changed the return modes of the **getFocusPoint** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getFocusPoint(callback: AsyncCallback<Point>): void** and **getFocusPoint(): Promise<Point>** are changed to **getFocusPoint(): Point**.
+
+    The code snippet is as follows:
+
+       ```
+    let point = captureSession.getFocusPoint();
+       ```
+
+34. Changed the return modes of the **getFocalLength** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getFocalLength(callback: AsyncCallback<number>): void** and **getFocalLength(): Promise<number>** are changed to **getFocalLength(): number**.
+
+    The code snippet is as follows:
+
+       ```
+    let focalLength = captureSession.getFocalLength();
+       ```
+
+35. Changed the return modes of the **getZoomRatioRange** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getZoomRatioRange(callback: AsyncCallback<Array<number>>): void** and **getZoomRatioRange(): Promise<Array<number>>** are changed to **getZoomRatioRange(): Array<number>**.
+
+    The code snippet is as follows:
+
+       ```
+    let zoomRatioRange = captureSession.getZoomRatioRange();
+       ```
+
+36. Changed the return modes of the **getZoomRatio** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getZoomRatio(callback: AsyncCallback<number>): void** and **getZoomRatio(): Promise<number>** are changed to **getZoomRatio(): number**.
+
+    The code snippet is as follows:
+
+       ```
+    let zoomRatio = captureSession.getZoomRatio();
+       ```
+
+37. Changed the return modes of the **setZoomRatio** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **setZoomRatio(zoomRatio: number, callback: AsyncCallback<void>): void** and **setZoomRatio(zoomRatio: number): Promise<void>** are changed to **setZoomRatio(zoomRatio: number): void**.
+
+    The code snippet is as follows:
+
+       ```
+    let zoomRatio = zoomRatioRange[0];
+    captureSession.setZoomRatio(zoomRatio);
+       ```
+
+38. Changed the return modes of the **isVideoStabilizationModeSupported** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **isVideoStabilizationModeSupported(vsMode: VideoStabilizationMode, callback: AsyncCallback<boolean>): void** and **isVideoStabilizationModeSupported(vsMode: VideoStabilizationMode): Promise<boolean>** are changed to **isVideoStabilizationModeSupported(vsMode: VideoStabilizationMode): boolean**.
+
+    The code snippet is as follows:
+
+       ```
+    let isSupported = captureSession.isVideoStabilizationModeSupported(camera.VideoStabilizationMode.OFF);
+       ```
+
+39. Changed the return modes of the **getActiveVideoStabilizationMode** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **getActiveVideoStabilizationMode(callback: AsyncCallback<VideoStabilizationMode>): void** and **getActiveVideoStabilizationMode(): Promise<VideoStabilizationMode>** are changed to **getActiveVideoStabilizationMode(): VideoStabilizationMode**.
+
+    The code snippet is as follows:
+
+       ```
+    let vsMode = captureSession.getActiveVideoStabilizationMode();
+       ```
+
+40. Changed the return modes of the **setVideoStabilizationMode** API in CaptureSession from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **setVideoStabilizationMode(mode: VideoStabilizationMode, callback: AsyncCallback<void>): void** and **setVideoStabilizationMode(mode: VideoStabilizationMode): Promise<void>** are changed to **setVideoStabilizationMode(mode: VideoStabilizationMode): void**.
+
+    The code snippet is as follows:
+
+       ```
+    captureSession.setVideoStabilizationMode(camera.VideoStabilizationMode.OFF);
+       ```
+
+41. Changed the **on(type:'error') callback** type in CaptureSession from **ErrorCallback<CaptureSessionError>** to **ErrorCallback<BusinessError>**. Therefore, the original API **on(type: 'error', callback: ErrorCallback<CaptureSessionError>): void** is changed to **on(type: 'error', callback: ErrorCallback<BusinessError>): void**.
+
+    The code snippet is as follows:
+
+       ```
+    captureSession.on('error', (BusinessError) => {
+    
+    })
+       ```
+
+42. Changed the **on(type:'error') callback** type in PreviewOutput, from **ErrorCallback<PreviewOutputError>** to **ErrorCallback<BusinessError>**. Therefore, the original API **on(type: 'error', callback: ErrorCallback<PreviewOutputError>): void** is changed to **on(type: 'error', callback: ErrorCallback<BusinessError>): void**.
+
+    The code snippet is as follows:
+
+       ```
+    previewOutput.on('error', (BusinessError) => {
+    
+    })
+       ```
+
+43. Changed the return modes of the **isMirrorSupported** API in PhotoOutput from asynchronous callback and asynchronous promise to the synchronous mode. Therefore, the original APIs **isMirrorSupported(callback: AsyncCallback<boolean>): void** and **isMirrorSupported(): Promise<boolean>** are changed to **isMirrorSupported(): boolean**.
+
+    The code snippet is as follows:
+
+       ```
+    let isSupported = photoOutput.isMirrorSupported();
+       ```
+
+44. Changed the **on(type:'error') callback** type in PhotoOutput, from **ErrorCallback<PhotoOutputError>** to **ErrorCallback<BusinessError>**. Therefore, the original API **on(type: 'error', callback: ErrorCallback<PhotoOutputError>): void** is changed to **on(type: 'error', callback: ErrorCallback<BusinessError>): void**.
+
+    The code snippet is as follows:
+
+       ```
+    PhotoOutput.on('error', (BusinessError) => {
+    
+    })
+       ```
+
+45. Changed the **on(type:'error') callback** type in VideoOutput, from **ErrorCallback<VideoOutputError>** to **ErrorCallback<BusinessError>**. Therefore, the original API **on(type: 'error', callback: ErrorCallback<VideoOutputError>): void** is changed to **on(type: 'error', callback: ErrorCallback<BusinessError>): void**.
+
+    The code snippet is as follows:
+
+       ```
+    VideoOutput.on('error', (BusinessError) => {
+    
+    })
+       ```
+
+46. Changed the **on(type:'error') callback** type in MetadataOutput, from **ErrorCallback<MetadataOutputError>** to **ErrorCallback<BusinessError>**. Therefore, the original API **on(type: 'error', callback: ErrorCallback<MetadataOutputError>): void** is changed to **on(type: 'error', callback: ErrorCallback<BusinessError>): void**.
+
+    The code snippet is as follows:
+
+       ```
+    MetadataOutput.on('error', (BusinessError) => {
+    
+    })
+       ```
\ No newline at end of file
diff --git a/en/release-notes/changelogs/v3.2-beta5/changelogs-container.md b/en/release-notes/changelogs/v3.2-beta5/changelogs-container.md
new file mode 100644
index 0000000000000000000000000000000000000000..6bd06001584f34addcbec3f81a80d47d482e7ffe
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta5/changelogs-container.md
@@ -0,0 +1,21 @@
+# Common Library Subsystem Changelog
+
+## cl.commonlibrary.1 Error Code and Information Change
+The error codes and information returned by APIs of the **ArrayList**, **List**, **LinkedList**, **Stack**, **Queue**, **Deque**, **PlainArray**, **LightWeightMap**, **LightWeightSet**, **HashMap**, **HashSet**, **TreeMap**, and **TreeSet** classes are changed.
+
+For details about the changed error codes, see [Utils Error Codes](../../../application-dev/reference/errorcodes/errorcode-utils.md).
+
+No adaptation is required for applications developed using these APIs.
+
+**Key API/Component Changes**
+Error code information is redefined for APIs in these classes and marked using **'@throws'** in the *.d.ts file of the corresponding module.
+The sample code is as follows:
+**ArrayList** class before the change:
+constructor();
+**ArrayList** class after the change:
+@throws { BusinessError } 10200012 - The ArrayList's constructor cannot be directly invoked.
+constructor();
+
+**Change Impact**
+
+No impact.
diff --git a/en/release-notes/changelogs/v3.2-beta5/changelogs-mediaLibrary.md b/en/release-notes/changelogs/v3.2-beta5/changelogs-mediaLibrary.md
new file mode 100644
index 0000000000000000000000000000000000000000..459adbacf8a02fbb45ef82ee6bb6dba706633258
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta5/changelogs-mediaLibrary.md
@@ -0,0 +1,116 @@
+# File Management Subsystem Changelog
+
+## cl.file.1 mediaLibrary APIs Changed
+
+The **MediaLibrary** class of the multimedia component is replaced by the **FilePicker** class.
+
+**Change Impact**
+
+For applications developed based on earlier versions, pay attention to the changes of APIs. **FilePicker** is a system application preset in OpenHarmony. You can use it to select and save files.
+
+**Key API/Component Changes**
+
+The APIs of **MediaLibrary**, located in **@ohos.multimedia.medialibrary**, are deprecated. The **FilePicker** class, located in [@ohos.file.picker](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/@ohos.file.picker.d.ts) is used.
+
+| Module                   | Method/Attribute/Enum/Constant                                         | Change Type|
+| ------------------------- | ------------------------------------------------------------ | -------- |
+| medialibrary   |  **function** getMediaLibrary(): MediaLibrary; | Deprecated    |
+| medialibrary   |  **function** getMediaLibrary(context: Context): MediaLibrary; | Deprecated    |
+| medialibrary   |  **function** getFileAssets(options: MediaFetchOptions, callback: AsyncCallback\<FetchFileResult\>): void | Deprecated    |
+| medialibrary   |  **function** getFileAssets(options: MediaFetchOptions): Promise\<FetchFileResult\> | Deprecated    |
+| medialibrary   |  **function** on(type: 'deviceChange'\|'albumChange'\|'imageChange'\|'audioChange'\|'videoChange'\|'fileChange'\|'remoteFileChange', callback: Callback\<void\>): void | Deprecated    |
+| medialibrary   |  **function** off(type: 'deviceChange'\|'albumChange'\|'imageChange'\|'audioChange'\|'videoChange'\|'fileChange'\|'remoteFileChange', callback?: Callback\<void\>): void | Deprecated    |
+| medialibrary   |  **function** createAsset(mediaType: MediaType, displayName: string, relativePath: string, callback: AsyncCallback\<FileAsset\>): void | Deprecated    |
+| medialibrary   |  **function** createAsset(mediaType: MediaType, displayName: string, relativePath: string): Promise\<FileAsset\> | Deprecated    |
+| medialibrary   |  **function** deleteAsset(uri: string): Promise\<void\> | Deprecated    |
+| medialibrary   |  **function** deleteAsset(uri: string, callback: AsyncCallback\<void\>): void | Deprecated    |
+| medialibrary   |  **function** getPublicDirectory(type: DirectoryType, callback: AsyncCallback\<string\>): void | Deprecated    |
+| medialibrary   |  **function** getPublicDirectory(type: DirectoryType): Promise\<string\> | Deprecated    |
+| medialibrary   |  **function** getAlbums(options: MediaFetchOptions, callback: AsyncCallback\<Array\<Album\>\>): void | Deprecated    |
+| medialibrary   |  **function** getAlbums(options: MediaFetchOptions): Promise\<Array\<Album\>\> | Deprecated    |
+| medialibrary   |  **function** release(callback: AsyncCallback\<void\>): void  | Deprecated    |
+| medialibrary   |  **function** release(): Promise\<void\> | Deprecated    |
+| medialibrary   |  **function** storeMediaAsset(option: MediaAssetOption, callback: AsyncCallback\<string\>): void | Deprecated    |
+| medialibrary   |  **function** storeMediaAsset(option: MediaAssetOption): Promise\<string\> | Deprecated    |
+| medialibrary   |  **function** startImagePreview(images: Array\<string\>, index: number, callback: AsyncCallback\<void\>): void | Deprecated    |
+| medialibrary   |  **function** startImagePreview(images: Array\<string\>, callback: AsyncCallback\<void\>): void | Deprecated    |
+| medialibrary   |  **function** startImagePreview(images: Array\<string\>, index?: number): Promise\<void\> | Deprecated    |
+| medialibrary   |  **function** startMediaSelect(option: MediaSelectOption, callback: AsyncCallback\<Array\<string\>\>): void | Deprecated    |
+| medialibrary   |  **function** startMediaSelect(option: MediaSelectOption): Promise\<Array\<string\>\> | Deprecated    |
+| medialibrary   |  **function** getActivePeers(): Promise\<Array\<PeerInfo\>\>; | Deprecated    |
+| medialibrary   |  **function** getActivePeers(callback: AsyncCallback\<Array\<PeerInfo\>\>): void; | Deprecated    |
+| medialibrary   |  **function** getAllPeers(): Promise\<Array\<PeerInfo\>\>; | Deprecated    |
+| medialibrary   |  **function** FileAsset.isDirectory(callback: AsyncCallback\<boolean\>): void | Deprecated    |
+| medialibrary   |  **function** FileAsset.isDirectory():Promise\<boolean\> | Deprecated    |
+| medialibrary   |  **function** FileAsset.commitModify(callback: AsyncCallback\<void\>): void | Deprecated    |
+| medialibrary   |  **function** FileAsset.commitModify(): Promise\<void\> | Deprecated    |
+| medialibrary   |  **function** FileAsset.open(mode: string, callback: AsyncCallback\<number\>): void | Deprecated    |
+| medialibrary   |  **function** FileAsset.open(mode: string): Promise\<number\> | Deprecated    |
+| medialibrary   |  **function** FileAsset.close(fd: number, callback: AsyncCallback\<void\>): void | Deprecated    |
+| medialibrary   |  **function** FileAsset.close(fd: number): Promise\<void\> | Deprecated    |
+| medialibrary   |  **function** FileAsset.getThumbnail(callback: AsyncCallback\<image.PixelMap\>): void | Deprecated    |
+| medialibrary   |  **function** FileAsset.getThumbnail(size: Size, callback: AsyncCallback\<image.PixelMap\>): void | Deprecated    |
+| medialibrary   |  **function** FileAsset.getThumbnail(size?: Size): Promise\<image.PixelMap\> | Deprecated    |
+| medialibrary   |  **function** FileAsset.favorite(isFavorite: boolean, callback: AsyncCallback\<void\>): void | Deprecated    |
+| medialibrary   |  **function** FileAsset.favorite(isFavorite: boolean): Promise\<void\> | Deprecated    |
+| medialibrary   |  **function** FileAsset.isFavorite(callback: AsyncCallback\<boolean\>): void | Deprecated    |
+| medialibrary   |  **function** FileAsset.isFavorite():Promise\<boolean\>  | Deprecated    |
+| medialibrary   |  **function** FileAsset.trash(isTrash: boolean, callback: AsyncCallback\<void\>): void | Deprecated    |
+| medialibrary   |  **function** FileAsset.trash(isTrash: boolean): Promise\<void\> | Deprecated    |
+| medialibrary   |  **function** FileAsset.isTrash(callback: AsyncCallback\<boolean\>): void | Deprecated    |
+| medialibrary   |  **function** FileAsset.isTrash():Promise\<boolean\> | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.getCount(): number | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.isAfterLast(): boolean | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.close(): void | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.getFirstObject(callback: AsyncCallback\<FileAsset\>): void | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.getFirstObject(): Promise\<FileAsset\> | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.getNextObject(callback: AsyncCallback\<FileAsset\>): void | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.getNextObject(): Promise\<FileAsset\> | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.getLastObject(callback: AsyncCallback\<FileAsset\>): void | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.getLastObject(): Promise\<FileAsset\> | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.getPositionObject(index: number, callback: AsyncCallback\<FileAsset\>): void | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.getPositionObject(index: number): Promise\<FileAsset\> | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.getAllObject(callback: AsyncCallback\<Array\<FileAsset\>\>): void | Deprecated    |
+| medialibrary   |  **function** FetchFileResult.getAllObject(): Promise\<Array\<FileAsset\>\> | Deprecated    |
+| medialibrary   |  **function** Album.commitModify(callback: AsyncCallback\<void\>): void | Deprecated    |
+| medialibrary   |  **function** Album.commitModify(): Promise\<void\> | Deprecated    |
+| medialibrary   |  **function** Album.getFileAssets(options: MediaFetchOptions, callback: AsyncCallback\<FetchFileResult\>): void | Deprecated    |
+| medialibrary   |  **function** Album.getFileAssets(options?: MediaFetchOptions): Promise\<FetchFileResult\> | Deprecated    |
+| medialibrary   |  **enum** DeviceType | Deprecated    |
+| medialibrary   |  **enum** FileKey | Deprecated    |
+| medialibrary   |  **enum** DirectoryType | Deprecated    |
+| medialibrary   |  **enum** MediaType | Deprecated    |
+| medialibrary   |  **interface** PeerInfo | Deprecated    |
+| medialibrary   |  **interface** Size  | Deprecated    |
+| medialibrary   |  **interface** MediaFetchOptions | Deprecated    |
+| medialibrary   |  **interface** MediaAssetOption | Deprecated    |
+| medialibrary   |  **interface** MediaSelectOption | Deprecated    |
+| medialibrary   |  **interface** FileAsset | Deprecated    |
+
+**Adaptation Guide**
+
+For example, refer to the code snippet below to call an API to select an image:
+
+```js
+import picker from '@ohos.file.picker';
+
+async function example() {
+    try {  
+        let PhotoSelectOptions = new picker.PhotoSelectOptions();
+        PhotoSelectOptions.MIMEType = picker.PhotoViewMIMETypes.IMAGE_TYPE;
+        PhotoSelectOptions.maxSelectNumber = 1;
+        let photoPicker = new picker.PhotoViewPicker();
+        photoPicker.select(PhotoSelectOptions).then((PhotoSelectResult) => {
+            if (PhotoSelectResult !== undefined) {
+                console.info("PhotoViewPicker.select pass, PhotoSelectResult uri: " + JSON.stringify(PhotoSelectResult));
+            } else {
+                console.error("PhotoViewPicker.select PhotoSelectResult is undefined");
+            }
+        }).catch((err) => {
+            console.error("PhotoViewPicker.select fail, err: " + err);
+        });
+    } catch (err) {
+        console.error("PhotoViewPicker fail, err: " + err);
+    }
+}
+```
diff --git a/en/release-notes/changelogs/v3.2-beta5/changelogs-multimedia.md b/en/release-notes/changelogs/v3.2-beta5/changelogs-multimedia.md
new file mode 100644
index 0000000000000000000000000000000000000000..ffeb68c714639f07a5b53a0bacaca16be2aab81a
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta5/changelogs-multimedia.md
@@ -0,0 +1,53 @@
+## cl.multimedia.av_session.001 Change of All av_session APIs to System APIs
+
+All av_session APIs are changed to system APIs.
+
+**Change Impact**
+
+Non-system applications and applications without system API permission cannot call system APIs.
+
+**Key API/Component Changes**
+
+All APIs are changed to system APIs. The table below describes the APIs.
+
+| API/Enum/Variable| Type| Is System API|
+| -------- | -------- | ------- |
+| SessionToken | interface | Yes|
+| AVMetadata  | interface | Yes|
+| AVPlaybackState  | interface | Yes|
+| PlaybackPosition  | interface | Yes|
+| OutputDeviceInfo  | interface | Yes|
+| AVSessionDescriptor  | interface | Yes|
+| AVSessionController  | interface | Yes|
+| AVControlCommand  | interface | Yes|
+| createAVSession | function | Yes|
+| getAllSessionDescriptors | function | Yes|
+| createController | function | Yes|
+| castAudio | function | Yes|
+| on  | function | Yes|
+| off | function | Yes|
+| sendSystemAVKeyEvent | function | Yes|
+| sendSystemControlCommand | function | Yes|
+| sessionId | variable | Yes|
+| setAVMetadata | function | Yes|
+| setAVPlaybackState | function | Yes|
+| setLaunchAbility | function | Yes|
+| getController | function | Yes|
+| getOutputDevice | function | Yes|
+| activate | function | Yes|
+| deactivate | function | Yes|
+| destroy | function | Yes|
+| getAVPlaybackState | function | Yes|
+| getAVMetadata | function | Yes|
+| getOutputDevice | function | Yes|
+| sendAVKeyEvent | function | Yes|
+| getLaunchAbility | function | Yes|
+| getRealPlaybackPositionSync | function | Yes|
+| isActive | function | Yes|
+| getValidCommands | function | Yes|
+| sendControlCommand | function | Yes|
+| AVSessionType  | type | Yes|
+| AVControlCommandType  | type | Yes|
+| LoopMode  | enum | Yes|
+| PlaybackState  | enum | Yes|
+| AVSessionErrorCode  | enum | Yes|
diff --git a/en/release-notes/changelogs/v3.2-beta5/changelogs-request.md b/en/release-notes/changelogs/v3.2-beta5/changelogs-request.md
index eb14226d5b172646ccce6c1d0885fe6c8d23acb8..c6ef2f531321173269ff8ac08d86408daccda9bf 100644
--- a/en/release-notes/changelogs/v3.2-beta5/changelogs-request.md
+++ b/en/release-notes/changelogs/v3.2-beta5/changelogs-request.md
@@ -1,4 +1,4 @@
-# Upload and Download Subsystem Changelog
+# Upload and Download Changelog
 
 
 ## cl.request.2 Upload and Download API Change
diff --git a/en/release-notes/changelogs/v3.2-beta5/changelogs-resourceschedule.md b/en/release-notes/changelogs/v3.2-beta5/changelogs-resourceschedule.md
new file mode 100644
index 0000000000000000000000000000000000000000..8df3e6671bd98eb04092412fd0c6e563268fb91d
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta5/changelogs-resourceschedule.md
@@ -0,0 +1,111 @@
+# Resource Scheduler Subsystem Changelog
+
+## cl.resourceschedule.backgroundTaskManager 
+Rectified the original APIs of **backgroundTaskManager** of the resource scheduler subsystem. All APIs of API version 9 in the **@ohos.backgroundTaskManager.d.ts** file are deleted, and the APIs of API version 9 in the **@ohos.resourceschedule.backgroundTaskManager.d.ts** file are used. The new APIs in API version 9 comply with the error code specifications.
+
+**Change Impacts**
+
+If your application is developed based on the SDK versions of OpenHarmony 3.2.10.5 and later, adapt to the modules and APIs in API version 9 and the pattern for returning error codes. Otherwise, the service logic will be affected.
+
+**Key API/Component Changes**
+
+The following methods, attributes, enums, and constants are changed in API version 9 and later versions. All the APIs in the **@ohos.backgroundTaskManager.d.ts** file are migrated to the **@ohos.resourceschedule.backgroundTaskManager.d.ts** file.
+
+| Class| API Type| Declaration| Description| 
+|  -- | -- | -- | -- |
+| backgroundTaskManager | method | function resetAllEfficiencyResources(): void; | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager | method | function applyEfficiencyResources(request: EfficiencyResourcesRequest): bool; | Changed in API version 9 to **function applyEfficiencyResources(request: EfficiencyResourcesRequest): void;** and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | export enum ResourceType | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | CPU = 1 | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | COMMON_EVENT = 1 << 1 | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | TIMER = 1 << 2 | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | WORK_SCHEDULER = 1 << 3 | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | BLUETOOTH = 1 << 4 | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | GPS = 1 << 5 | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.ResourceType | enum | AUDIO = 1 << 6 | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | interface | export interface EfficiencyResourcesRequest | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | reason: string | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | isProcess?: bool | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | isPersist?: bool | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | timeOut: number | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | isApply: bool | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+| backgroundTaskManager.EfficiencyResourcesRequest | field | resourceTypes: number | Deleted in API version 9 and moved to the **ohos.resourceschedule.backgroundTaskManager.d.ts** file.| 
+
+
+**Adaptation Guide**
+
+Import the **backgroundTaskManager** module.
+```
+import bundle form '@ohos.resourceschedule.backgroundTaskManager'
+```
+Exception handling also needs to be adapted. For details, see the [backgroundTaskManager API reference](../../../application-dev/reference/apis/js-apis-resourceschedule-backgroundTaskManager.md).
+
+## c2.resourceschedule.workScheduler 
+Rectified the original APIs of **workScheduler** of the resource scheduler subsystem. All APIs of API version 9 in the **@ohos.workScheduler.d.ts** file are deleted, and the APIs of API version 9 in the **@ohos.resourceschedule.workScheduler.d.ts** file are used. The new APIs in API version 9 comply with the error code specifications.
+
+**Change Impacts**
+
+If your application is developed based on the SDK versions of OpenHarmony 3.2.10.5 and later, adapt to the modules and APIs in API version 9 and the pattern for returning error codes. Otherwise, the service logic will be affected.
+
+**Key API/Component Changes**
+
+The following methods, attributes, enums, and constants are changed in API version 9 and later versions. The **@ohos.workScheduler.d.ts** file is deleted, and all the APIs in it are moved to the **@ohos.resourceschedule.workScheduler.d.ts** file.
+
+| Class| API Type| Declaration| Change Type| 
+|  -- | -- | -- | -- |
+| workScheduler | namespace | declare namespace workScheduler | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | interface | export interface WorkInfo | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | parameters?: {[key: string]: any} | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | idleWaitTime?: number | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | isDeepIdle?: boolean | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | repeatCount?: number | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | isRepeat?: boolean | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | repeatCycleTime?: number | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | storageRequest?: StorageRequest | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | batteryStatus?: BatteryStatus | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | batteryLevel?: number | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | chargerType?: ChargingType | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | isCharging?: boolean | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | networkType?: NetworkType | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | isPersisted?: boolean | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | abilityName: string | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | bundleName: string | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.WorkInfo | field | workId: number | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function isLastWorkTimeOut(workId: number): Promise; | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function isLastWorkTimeOut(workId: number, callback: AsyncCallback<void>): boolean; | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function stopAndClearWorks(): boolean; | Changed in API version 8 to **function stopAndClearWorks(): boolean;** and moved to the **ohos.resourceschedule.workScheduler.d.ts** file| 
+| workScheduler | method | function obtainAllWorks(): Promise<Array<WorkInfo>>; | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function obtainAllWorks(callback: AsyncCallback<void>): Array<WorkInfo>; | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function getWorkStatus(workId: number): Promise<WorkInfo>; | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function getWorkStatus(workId: number, callback: AsyncCallback<WorkInfo>): void; | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function stopWork(work: WorkInfo, needCancel?: boolean): boolean; | Changed in API version 8 to **function stopWork(work: WorkInfo, needCancel?: boolean): void;** and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler | method | function startWork(work: WorkInfo): boolean; | Changed in API version 9 to **function startWork(work: WorkInfo): void;** and moved to the **ohos.resourceschedule.workScheduler.d.ts** file| 
+| workScheduler.NetworkType | enum | export enum NetworkType | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_ANY = 0 | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_MOBILE | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_WIFI | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_BLUETOOTH | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_WIFI_P2P | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.NetworkType | enum | NETWORK_TYPE_ETHERNET | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.ChargingType | enum | export enum ChargingType | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.ChargingType | enum | CHARGING_PLUGGED_ANY = 0 | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.ChargingType | enum | CHARGING_PLUGGED_AC | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.ChargingType | enum | CHARGING_PLUGGED_USB | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.ChargingType | enum | CHARGING_PLUGGED_WIRELESS | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | export enum BatteryStatus | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | BATTERY_STATUS_LOW = 0 | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | BATTERY_STATUS_OKAY | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | BATTERY_STATUS_LOW_OR_OKAY | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.StorageRequest | enum | export enum StorageRequest | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | STORAGE_LEVEL_LOW = 0 | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | STORAGE_LEVEL_OKAY | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+| workScheduler.BatteryStatus | enum | STORAGE_LEVEL_LOW_OR_OKAY | Deleted in API version 9 and moved to the **ohos.resourceschedule.workScheduler.d.ts** file.| 
+
+
+**Adaptation Guide**
+
+Import the **workScheduler** module.
+```
+import bundle form '@ohos.resourceschedule.workScheduler'
+```
+Exception handling also needs to be adapted. For details, see the [workScheduler API reference](../../../application-dev/reference/apis/js-apis-resourceschedule-workScheduler.md).
diff --git a/en/release-notes/changelogs/v3.2-beta5/changelogs-url.md b/en/release-notes/changelogs/v3.2-beta5/changelogs-url.md
new file mode 100644
index 0000000000000000000000000000000000000000..4dfc6cacb85bb40bc9f02dab6343a82d4dbf7691
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta5/changelogs-url.md
@@ -0,0 +1,68 @@
+# Common Library Subsystem Changelog
+
+## cl.commonlibrary.1 URLParams Class Changes
+The constructor function of the **URLParams** class in the URL module of the common library subsystem is changed.
+
+Specifically, **constructor(init?: string[][] | Record<string, string> | string | URLSearchParams)** is changed to **constructor(init?: string[][] | Record<string, string> | string | URLParams)**, and the parameter type is changed from **URLSearchParams** to **URLParams**.
+
+You need to adapt your application.
+
+**Change Impacts**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enum/Constant                                         | Change Type|
+| :------------------------ | ------------------- | ------------------------------------------------------------ | -------- |
+| @ohos.url        | URLParams         | constructor(string[][] \| Record&lt;string, string&gt; \| string \| URLSearchParams) | Deleted |
+| @ohos.url         | URLParams       | constructor(string[][] \| Record&lt;string, string&gt; \| string \| URLParams)| Changed |
+
+**Adaptation Guide**
+
+The following illustrates how to create a **URLParams** object in your application.
+
+Example:
+
+```ts
+import url from '@ohos.url'
+try {
+    let params1 = new Url.URLParams('?user=abc&query=xyz')
+    let params2 = new Url.URLParams(params1)
+    var result= params2.toString()
+    console.log(result) //"user=abc&query=xyz"
+} catch (err) {
+    console.error(`Fail to ceate URLParams.codeis${err.code},message is ${err.message}`);
+}
+```
+## cl.commonlibrary.2 URL Attribute Changes of URLParams Class APIs
+The URL attributes of the URL module in the common library subsystem are changed.
+
+Specifically, the **searchParams: URLSearchParams** attribute is deprecated, and the **params: URLParams** attribute is added.
+
+You need to adapt your application.
+
+ **Change Impacts**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enum/Constant                                         | Change Type|
+| :------------------------ | ------------------- | ------------------------------------------------------------ | -------- |
+| @ohos.url        | URL         |  searchParams: URLSearchParams; |Deprecated (in API version 9)<br>   |
+| @ohos.url        | URL         |  params: URLParams; | Added    |
+
+**Adaptation Guide**
+
+The following illustrates how to create a **URLParams** object in your application.
+
+Example:
+
+```ts
+import url from '@ohos.url'
+let that = new Url.URL('http://username:password@host:8080/directory/file?Hello=china#qwer=da')
+let params = that.URLParams
+var result = params.toString()
+console.log(result) //%E4%BD%A0%E5%A5%BD=china
+```
diff --git a/en/release-notes/changelogs/v3.2-beta5/changelogs-window.md b/en/release-notes/changelogs/v3.2-beta5/changelogs-window.md
new file mode 100644
index 0000000000000000000000000000000000000000..45f62272f6749f6822179648004f04623401a093
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-beta5/changelogs-window.md
@@ -0,0 +1,63 @@
+# Window Manager Subsystem Changelog
+
+## cl.window.1 Change of Window Stage Lifecycle Listener Types
+
+Changed the enumerated listener types of the window stage lifecycle in version 3.2.10.5 and later.
+
+**Change Impacts**
+
+Application lifecycle listeners developed using **FOREGROUND** and **BACKGROUND** in versions earlier than 3.2.10.5 will be invalidated in version 3.2.10.5 and later.
+
+**Key API/Component Changes**
+
+##  WindowStageEventType<sup>9+</sup>
+
+Before change
+
+| Name      | Value  | Description      |
+| ---------- | ---- | ---------- |
+| FOREGROUND | 1    | The window stage is running in the foreground.|
+| BACKGROUND | 4    | The window stage is running in the background.|
+
+After change
+| Name  | Value  | Description      |
+| ------ | ---- | ---------- |
+| SHOWN  | 1    | The window stage is running in the foreground.|
+| HIDDEN | 4    | The window stage is running in the background.|
+
+**Adaptation Guide**
+
+When registering lifecycle listeners, change the foreground and background event types to **SHOWN** and **HIDDEN**, respectively.
+
+```
+import Ability from '@ohos.application.Ability';
+
+class myAbility extends Ability {
+    onWindowStageCreate(windowStage) {
+        console.log('onWindowStageCreate');
+        try {
+            windowStage.on('windowStageEvent', (stageEventType) => {
+                switch (stageEventType) {
+                    case window.WindowStageEventType.SHOWN:
+                        console.log("windowStage shown");
+                        break;
+                    case window.WindowStageEventType.ACTIVE:
+                        console.log("windowStage active");
+                        break;
+                    case window.WindowStageEventType.INACTIVE:
+                        console.log("windowStage inActive");
+                        break;
+                    case window.WindowStageEventType.HIDDEN:
+                        console.log("windowStage hidden");
+                        break;
+                    default:
+                        break;
+                }
+        	} )
+        } catch (exception) {
+            console.error('Failed to enable the listener for window stage event changes. Cause:' +
+                JSON.stringify(exception));
+        };
+    }
+};
+```
diff --git a/en/release-notes/changelogs/v3.2-release/Readme-EN.md b/en/release-notes/changelogs/v3.2-release/Readme-EN.md
new file mode 100644
index 0000000000000000000000000000000000000000..340e3f1e7826670138645e5e658b8aa387ac270e
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-release/Readme-EN.md
@@ -0,0 +1,8 @@
+# Readme
+
+- [Ability framework](changelogs-ability.md)
+- [Bundle manager subsystem](changelogs-bundlemanager.md)
+- [Resource scheduler subsystem](changelogs-resourceschedule.md)
+- [Telephony subsystem](changelogs-telephony.md)
+- [Util subsystem](changelogs-util.md)
+
diff --git a/en/release-notes/changelogs/v3.2-release/changelogs-ability.md b/en/release-notes/changelogs/v3.2-release/changelogs-ability.md
new file mode 100644
index 0000000000000000000000000000000000000000..b9367b4ce12ae9e48d0dbef5c628e4c0b7400b36
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-release/changelogs-ability.md
@@ -0,0 +1,283 @@
+# Ability Framework Changelog
+
+## cl.ability.1 AreaMode APIs Changed
+
+Duplicate **AreaMode** APIs are deleted.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enum/Constant                                         | Change Type|
+| ------------------------- | ------------------- | ------------------------------------------------------------ | -------- |
+| @ohos.app.ability.common.d.ts | common.AreaMode |  | Deleted    |
+| application/Context.d.ts | AreaMode |  | Deleted    |
+
+
+**Adaptation Guide**
+
+Use **AreaMode** in **@ohos.app.ability.contextConstant.d.ts**.
+
+```ts
+import contextConstant from '@ohos.app.ability.contextConstant';
+let area: contextConstant.AreaMode = contextConstant.AreaMode.EL1;
+```
+
+## cl.ability.2 killProcessesBySelf Renamed
+
+The **killProcessesBySelf** API is renamed **killAllProcesses**.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                        | Class              | Method/Attribute/Enum/Constant                                  | Change Type|
+| ------------------------------ | ------------------ | ----------------------------------------------------- | -------- |
+| application/ApplicationContext | ApplicationContext | killProcessesBySelf(): Promise\<void\>;               | Deleted    |
+| application/ApplicationContext | ApplicationContext | killProcessesBySelf(callback: AsyncCallback\<void\>); | Deleted    |
+| application/ApplicationContext | ApplicationContext | killAllProcesses(): Promise\<void\>;                  | Added    |
+| application/ApplicationContext | ApplicationContext | killAllProcesses(callback: AsyncCallback\<void\>);    | Added    |
+
+
+**Adaptation Guide**
+
+The following code snippet shows how to call **killProcessesBySelf** in an application.
+
+Code before the change:
+
+```ts
+let context: common.UIAbilityContext = globalThis.abilityContext;
+let appContext = context.getApplicationContext();
+appContext.killProcessesBySelf()
+```
+
+Code after the change:
+
+```ts
+let context: common.UIAbilityContext = globalThis.abilityContext;
+let appContext = context.getApplicationContext();
+appContext.killAllProcesses()
+```
+
+## cl.ability.3 getProcessRunningInformation Renamed
+
+The **getProcessRunningInformation** API is renamed **getRunningProcessInformation**.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                             | Class              | Method/Attribute/Enum/Constant                                         | Change Type|
+| ----------------------------------- | ------------------ | ------------------------------------------------------------ | -------- |
+| @ohos.app.ability.appManager.d.ts   | appManager         | function getProcessRunningInformation(): Promise\<Array\<ProcessRunningInformation\>\>; | Deleted    |
+| @ohos.app.ability.appManager.d.ts   | appManager         | function getProcessRunningInformation(callback: AsyncCallback\<Array\<ProcessRunningInformation\>\>): void; | Deleted    |
+| @ohos.app.ability.appManager.d.ts   | appManager         | function getRunningProcessInformation(): Promise\<Array\<ProcessInformation\>\>; | Added    |
+| @ohos.app.ability.appManager.d.ts   | appManager         | function getRunningProcessInformation(callback: AsyncCallback\<Array\<ProcessInformation\>\>): void; | Added    |
+| application/ApplicationContext.d.ts | ApplicationContext | getProcessRunningInformation(): Promise\<Array\<ProcessRunningInformation\>\>; | Deleted    |
+| application/ApplicationContext.d.ts | ApplicationContext | getProcessRunningInformation(callback: AsyncCallback\<Array\<ProcessRunningInformation\>\>): void; | Deleted    |
+| application/ApplicationContext.d.ts | ApplicationContext | getRunningProcessInformation(): Promise\<Array\<ProcessInformation\>\>; | Added    |
+| application/ApplicationContext.d.ts | ApplicationContext | getRunningProcessInformation(callback: AsyncCallback\<Array\<ProcessInformation\>\>): void; | Added    |
+
+**Adaptation Guide**
+
+The following code snippet shows how to call **getProcessRunningInformation** in an application.
+
+Code before the change:
+
+```ts
+let context: common.UIAbilityContext = globalThis.abilityContext;
+let appContext = context.getApplicationContext();
+appContext.getProcessRunningInformation()
+```
+
+Code after the change:
+
+```ts
+let context: common.UIAbilityContext = globalThis.abilityContext;
+let appContext = context.getApplicationContext();
+appContext.getRunningProcessInformation()
+```
+
+## cl.ability.4 WantConstant.Flags API Changed
+
+**WantConstant.Flags** has multiple invalid flag definitions. These invalid flags are deleted.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enum/Constant                                         | Change Type|
+| ------------------------- | ------------------- | ------------------------------------------------------------ | -------- |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_ABILITY_FORWARD_RESULT | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_ABILITY_CONTINUATION | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_NOT_OHOS_COMPONENT | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_ABILITY_FORM_ENABLED | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_AUTH_PERSISTABLE_URI_PERMISSION | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_AUTH_PREFIX_URI_PERMISSION | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_ABILITYSLICE_MULTI_DEVICE | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_START_FOREGROUND_ABILITY | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_ABILITY_CONTINUATION_REVERSIBLE | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_INSTALL_WITH_BACKGROUND_MODE | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_ABILITY_CLEAR_MISSION | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_ABILITY_NEW_MISSION | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Flags  | FLAG_ABILITY_MISSION_TOP | Deleted    |
+
+## cl.ability.5 WantConstant.Action API Changed
+
+**WantConstant.Action** has multiple invalid action definitions. These invalid actions are deleted.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enum/Constant                                         | Change Type|
+| ------------------------- | ------------------- | ------------------------------------------------------------ | -------- |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Action  | ACTION_APP_ACCOUNT_AUTH | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Action  | ACTION_MARKET_DOWNLOAD | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Action  | ACTION_MARKET_CROWDTEST | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Action  | DLP_PARAMS_SANDBOX | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Action  | DLP_PARAMS_BUNDLE_NAME | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Action  | DLP_PARAMS_MODULE_NAME | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Action  | DLP_PARAMS_ABILITY_NAME | Deleted    |
+
+## cl.ability.6 Caller APIs Changed
+
+Caller APIs use the **Parcelable** and **MessageSequence** objects provided by RPC in API version 9 to replace the deprecated **Sequenceable** and **MessageParcel** object.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                   | Class               | Method/Attribute/Enum/Constant                                         | Change Type|
+| ------------------------- | ------------------- | ------------------------------------------------------------ | -------- |
+| api/@ohos.app.ability.UIAbility.d.ts | CalleeCallback | (indata: rpc.MessageParcel): rpc.Sequenceable; | Changed to **(indata: rpc.MessageSequence): rpc.Parcelable;**.    |
+| api/@ohos.app.ability.UIAbility.d.ts | Caller | call(method: string, data: rpc.Sequenceable): Promise<void>; | Changed to **call(method: string, data: rpc.Parcelable): Promise<void>;**.    |
+| api/@ohos.app.ability.UIAbility.d.ts | Caller | callWithResult(method: string, data: rpc.Sequenceable): Promise<rpc.MessageParcel>; | Changed to **callWithResult(method: string, data: rpc.Parcelable): Promise<rpc.MessageSequence>;**.    |
+
+**Adaptation Guide**
+
+The following illustrates how to call the caller APIs in your application.
+
+Code before the change:
+
+```ts
+  class MyMessageAble{
+      name:""
+      str:""
+      num: 1
+      constructor(name, str) {
+        this.name = name;
+        this.str = str;
+      }
+      marshalling(messageParcel) {
+          messageParcel.writeInt(this.num);
+          messageParcel.writeString(this.str);
+          console.log('MyMessageAble marshalling num[' + this.num + '] str[' + this.str + ']');
+          return true;
+      }
+      unmarshalling(messageParcel) {
+          this.num = messageParcel.readInt();
+          this.str = messageParcel.readString();
+          console.log('MyMessageAble unmarshalling num[' + this.num + '] str[' + this.str + ']');
+          return true;
+      }
+  };
+  let method = 'call_Function';
+  function funcCallBack(pdata) {
+      console.log('Callee funcCallBack is called ' + pdata);
+      let msg = new MyMessageAble("test", "");
+      pdata.readSequenceable(msg);
+      return new MyMessageAble("test1", "Callee test");
+  }
+  export default class MainUIAbility extends UIAbility {
+    onCreate(want, launchParam) {
+      console.log('Callee onCreate is called');
+      try {
+        this.callee.on(method, funcCallBack);
+      } catch (error) {
+        console.log('Callee.on catch error, error.code: ' + error.code +
+          ' error.message: ' + error.message);
+      }
+    }
+  }
+```
+
+Code after the change:
+
+```ts
+  class MyMessageAble{
+      name:""
+      str:""
+      num: 1
+      constructor(name, str) {
+        this.name = name;
+        this.str = str;
+      }
+      marshalling(messageSequence) {
+          messageSequence.writeInt(this.num);
+          messageSequence.writeString(this.str);
+          console.log('MyMessageAble marshalling num[' + this.num + '] str[' + this.str + ']');
+          return true;
+      }
+      unmarshalling(messageSequence) {
+          this.num = messageSequence.readInt();
+          this.str = messageSequence.readString();
+          console.log('MyMessageAble unmarshalling num[' + this.num + '] str[' + this.str + ']');
+          return true;
+      }
+  };
+  let method = 'call_Function';
+  function funcCallBack(pdata) {
+      console.log('Callee funcCallBack is called ' + pdata);
+      let msg = new MyMessageAble("test", "");
+      pdata.readParcelable(msg);
+      return new MyMessageAble("test1", "Callee test");
+  }
+  export default class MainUIAbility extends UIAbility {
+    onCreate(want, launchParam) {
+      console.log('Callee onCreate is called');
+      try {
+        this.callee.on(method, funcCallBack);
+      } catch (error) {
+        console.log('Callee.on catch error, error.code: ' + error.code +
+          ' error.message: ' + error.message);
+      }
+    }
+  }
+```
+
+## cl.ability.7 WantConstant.Flags API Changed
+
+The **wantConstant** API had two similar enums. Now the two enums are combined into one.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module                             | Class                  | Method/Attribute/Enum/Constant                | Change Type|
+| ----------------------------------- | ---------------------- | ----------------------------------- | -------- |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Parameter | ABILITY_BACK_TO_OTHER_MISSION_STACK | Deleted    |
+| @ohos.app.ability.wantConstant.d.ts | wantConstant.Params    | ABILITY_BACK_TO_OTHER_MISSION_STACK | Added    |
+
+**Adaptation Guide**
+
+Use **ABILITY_BACK_TO_OTHER_MISSION_STACK** in **@ohos.app.ability.wantConstant.d.ts**.
+
+```ts
+import wantConstant from '@ohos.app.ability.wantConstant';
+let backToOtherMissionStack: wantConstant.Params = wantParam.Params.ABILITY_BACK_TO_OTHER_MISSION_STACK;
+```
diff --git a/en/release-notes/changelogs/v3.2-release/changelogs-bundlemanager.md b/en/release-notes/changelogs/v3.2-release/changelogs-bundlemanager.md
new file mode 100644
index 0000000000000000000000000000000000000000..2aa79ad27454a6277da0bb106de84c3529593d58
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-release/changelogs-bundlemanager.md
@@ -0,0 +1,298 @@
+# Bundle Manager Subsystem Changelog
+
+## cl.bundlemanager.1 Deleted getAbilityIcon
+
+The **getAbilityIcon** API in [@ohos.bundle.bundleManager.d.ts](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/@ohos.bundle.bundleManager.d.ts) is deleted. The **getMediaContent** API in [@ohos.resourceManager.d.ts](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/@ohos.resourceManager.d.ts) can be used instead.
+
+**Change Impact**<br>
+The **getAbilityIcon** API does not take effect.
+
+**Key API/Component Changes**<br>
+The **getAbilityIcon** API is deleted from **@ohos.bundle.bundleManager.d.ts**.
+
+**Adaptation Guide**<br>
+If your application uses **getAbilityIcon** in **@ohos.bundle.bundleManager.d.ts**, replace it with **getMediaContent** in **@ohos.resourceManager.d.ts**. You need to obtain the icon ID in advance. For details, see [Usage Guide](../../../application-dev/reference/apis/js-apis-resource-manager.md#getmediacontent9).
+
+## cl.bundlemanager.2 Bottom-Layer Capability Changed So That Only the System Resource HAP Supports Custom Permissions
+
+Only the system resource HAP supports custom permissions. During HAP parsing, the bundle manager module parses the **definePermissions** field only in the configuration file of the resource HAP (bundle name: **ohos.global.systemres**), but not this field in other HAPs. This field is used to define permissions.
+If an application requires custom permissions, add the permissions under the **definePermissions** field in the [configuration file](https://gitee.com/openharmony/utils_system_resources/blob/master/systemres/main/config.json) of the system resource HAP. For details about the permission format, see [Defining Permissions](../../../application-dev/quick-start/module-structure.md#internal-structure-of-the-definepermissions-attribute).
+
+
+**Change Impact**<br>
+After an upgrade to the new version image, the custom permission of the application does not take effect, and the authorization fails.
+
+**Key API/Component Changes**<br>
+The bottom-layer capability of the bundle manager module is changed. Only the system resource HAP supports custom permissions.
+
+**Adaptation Guide**<br>
+If an application requires custom permissions, add the permissions under the **definePermissions** field in the [configuration file](https://gitee.com/openharmony/utils_system_resources/blob/master/systemres/main/config.json) of the system resource HAP. For details about the permission format, see [Defining Permissions](../../../application-dev/quick-start/module-structure.md#internal-structure-of-the-definepermissions-attribute).
+
+## cl.bundlemanager.3 Level-2 Module File Names Changed
+
+The level-2 module file names of the bundle manager module are changed to their respective API names in the file, as listed below.
+
+| Original File Name|New File Name|
+|----|----|
+| bundleManager/abilityInfo.d.ts |  bundleManager/AbilityInfo.d.ts |
+| bundleManager/applicationInfo.d.ts |  bundleManager/ApplicationInfo.d.ts |
+| bundleManager/bundleInfo.d.ts |  bundleManager/BundleInfo.d.ts |
+| bundleManager/dispatchInfo.d.ts |  bundleManager/DispatchInfo.d.ts |
+| bundleManager/elementName.d.ts |  bundleManager/ElementName.d.ts |
+| bundleManager/extensionAbilityInfo.d.ts |  bundleManager/ExtensionAbilityInfo.d.ts |
+| bundleManager/hapModuleInfo.d.ts |  bundleManager/HapModuleInfo.d.ts |
+| bundleManager/launcherAbilityInfo.d.ts |  bundleManager/LauncherAbilityInfo.d.ts |
+| bundleManager/metadata.d.ts |  bundleManager/Metadata.d.ts |
+| bundleManager/packInfo.d.ts |  bundleManager/BundlePackInfo.d.ts |
+| bundleManager/permissionDef.d.ts |  bundleManager/PermissionDef.d.ts |
+| bundleManager/remoteAbilityInfo.d.ts |  bundleManager/RemoteAbilityInfo.d.ts |
+| bundleManager/shortcutInfo.d.ts |  bundleManager/ShortcutInfo.d.ts |
+
+To sum up, except **packInfo**, which is changed to **BundlePackInfo**, the other file names are changed to start with uppercase letters.
+
+**Change Impact**<br>
+The change of the level-2 module file names does not affect the use of the level-1 module. If a level-2 module interface under **bundleManager** is directly imported to the .ts file and an error is reported during compilation on DevEco Studio, you must change the name of the imported file.
+
+**Key API/Component Changes**<br>
+The .d.ts file names in the **bundleManager** folder are changed to their respective API names in the file.
+
+**Adaptation Guide**<br>
+Generally, no adaptation is required. If a file in the **bundleManager** folder is directly imported to the application, you must change the imported file name as follows:
+
+**Before change:**
+```ts
+import {AbilityInfo} from 'bundleManger/abilityInfo';
+import {ExtensionAbilityInfo} from 'bundleManger/extensionAbilityInfo';
+import {BundlePackInfo} from 'bundleManger/packInfo';
+```
+**After change:**
+```ts
+import {AbilityInfo} from 'bundleManger/AbilityInfo';
+import {ExtensionAbilityInfo} from 'bundleManger/ExtensionAbilityInfo';
+import {BundlePackInfo} from 'bundleManger/BundlePackInfo';
+```
+
+## cl.bundlemanager.4 LaunchType Enum Type Name Changed from STANDARD to MULTITON
+
+The enum type name of [LaunchType](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/@ohos.bundle.bundleManager.d.ts) is changed from **STANDARD** to **MULTITON**. The enum value remains unchanged, indicating the multi-instance type.
+
+**Change Impact**<br>
+The **LaunchType.STANDARD** type does not take effect.
+
+**Key API/Component Changes**<br>
+The enum type name of **LaunchType** is changed from **STANDARD** to **MULTITON**.
+
+**Adaptation Guide**<br>
+Change **LaunchType.STANDARD** to **LaunchType.MULTITON** for your application.
+
+## cl.bundlemanager.5 Changed the isVisible Field in the AbilityInfo Struct to exported
+
+The **isVisible** field in the [AbilityInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/AbilityInfo.d.ts) struct is changed to **exported**. The type remains unchanged, indicating whether the ability can be exported and used by other abilities.
+
+**Change Impact**<br>
+The **isVisible** field does not take effect.
+
+**Key API/Component Changes**<br>
+The **isVisible** field in the [AbilityInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/AbilityInfo.d.ts) struct is changed to **exported**, and the type remains unchanged.
+
+**Adaptation Guide**<br>
+Change **isVisible** to **exported** for your application.
+
+## cl.bundlemanager.6 Changed the isVisible Field in the ExtensionAbilityInfo Struct to exported
+
+The **isVisible** field in the [ExtensionAbilityInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/ExtensionAbilityInfo.d.ts) struct is changed to **exported**. The type remains unchanged, indicating whether the ability can be exported and used by other abilities.
+
+**Change Impact**<br>
+The **isVisible** field does not take effect.
+
+**Key API/Component Changes**<br>
+The **isVisible** field in the [ExtensionAbilityInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/ExtensionAbilityInfo.d.ts) struct is changed to **exported**, and the type remains unchanged.
+
+**Adaptation Guide**<br>
+Change **isVisible** to **exported** for your application.
+
+## cl.bundlemanager.7 Changed the visible Field in the ModuleAbilityInfo Struct to exported
+
+The **visible** field in the [ModuleAbilityInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/BundlePackInfo.d.ts) struct is changed to **exported**. The type remains unchanged, indicating whether the ability can be exported and used by other abilities.
+
+**Change Impact**<br>
+The **visible** field does not take effect.
+
+**Key API/Component Changes**<br>
+The **visible** field in the [ModuleAbilityInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/BundlePackInfo.d.ts) struct is changed to **exported**, and the type remains unchanged.
+
+**Adaptation Guide**<br>
+Change **visible** to **exported** for your application.
+
+## cl.bundlemanager.8 Deleted the distributedNotificationEnabled Tag from the app.json Configuration File
+The [distributedNotificationEnabled](../../../application-dev/quick-start/app-configuration-file.md) tag is deleted from the **app.json** configuration file.
+
+**Change Impact**<br>
+If this tag is used, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Delete this tag from the configuration file.
+
+## cl.bundlemanager.9 Deleted the entityType Tag from the app.json Configuration File
+The [entityType](../../../application-dev/quick-start/app-configuration-file.md) tag is deleted from the **app.json** configuration file.
+
+**Change Impact**<br>
+If this tag is used, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Delete this tag from the configuration file.
+
+## cl.bundlemanager.10 Deleted the keepAlive Tag from the app.json Configuration File
+The [keepAlive](../../../application-dev/quick-start/app-configuration-file.md) tag is deleted from the **app.json** configuration file.
+
+**Change Impact**<br>
+If this tag is used, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Delete this tag from the configuration file.
+
+## cl.bundlemanager.11 Deleted the removable Tag from the app.json Configuration File
+The [removable](../../../application-dev/quick-start/app-configuration-file.md) tag is deleted from the **app.json** configuration file.
+
+**Change Impact**<br>
+If this tag is used, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Delete this tag from the configuration file.
+
+## cl.bundlemanager.12 Deleted the singleton Tag from the app.json Configuration File
+The [singleton](../../../application-dev/quick-start/app-configuration-file.md) tag is deleted from the **app.json** configuration file.
+
+**Change Impact**<br>
+If this tag is used, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Delete this tag from the configuration file.
+
+## cl.bundlemanager.13 Deleted the userDataClearable Tag from the app.json Configuration File
+The [userDataClearable](../../../application-dev/quick-start/app-configuration-file.md) tag is deleted from the **app.json** configuration file.
+
+**Change Impact**<br>
+If this tag is used, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Delete this tag from the configuration file.
+
+## cl.bundlemanager.14 No Longer Chinese Characters for the name Tag under module in the module.json Configuration File
+The value of [name](../../../application-dev/quick-start/module-configuration-file.md) under **module** in the **module.json** configuration file does not support Chinese characters.
+
+**Change Impact**<br>
+If the tag is set to Chinese, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Set this tag to English.
+
+## cl.bundlemanager.15 No Longer Chinese Characters for the name Tag under ability in the module.json Configuration File
+The value of [name](../../../application-dev/quick-start/module-configuration-file.md) under **ability** in the **module.json** configuration file does not support Chinese characters.
+
+**Change Impact**<br>
+If the tag is set to Chinese, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Set this tag to English.
+
+## cl.bundlemanager.16 Deleted the uiSyntax Tag from the module.json Configuration File
+The [uiSyntax](../../../application-dev/quick-start/module-configuration-file.md) tag is deleted from the **module.json** configuration file.
+
+**Change Impact**<br>
+If this tag is used, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Delete this tag from the configuration file.
+
+## cl.bundlemanager.17 Changed srcEntrance to srcEntry in the module.json Configuration File
+The [srcEntrance](../../../application-dev/quick-start/module-configuration-file.md) tag under **module** and **ability** in the **module.json** configuration file is changed to **srcEntry**.
+
+**Change Impact**<br>
+If the **srcEntrance** tag is used, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Replace the **srcEntrance** tag with **srcEntry** in the configuration file.
+
+## cl.bundlemanager.18 Deleted the apiVersion Tag Under distroFilter from the module.json Configuration File
+The **apiVersion** tag under [distroFilter](../../../application-dev/quick-start/module-configuration-file.md) is deleted from the **module.json** configuration file.
+
+**Change Impact**<br>
+If this tag is used, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Delete this tag from the configuration file.
+
+## cl.bundlemanager.19 Changed distroFilter to distributionFilter in the module.json Configuration File
+The [distroFilter](../../../application-dev/quick-start/module-configuration-file.md) tag in the **module.json** configuration file is changed to **distributionFilter**.
+
+**Change Impact**<br>
+If the **distroFilter** tag is used, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Replace **distroFilter** with **distributionFilter** in the configuration file.
+
+## cl.bundlemanager.20 Changed standard of launchType to multiton in the module.json Configuration File
+The **standard** mode of the [launchType](../../../application-dev/quick-start/module-configuration-file.md) tag in the **module.json** file is changed to **multiton**.
+
+**Adaptation Guide**<br>
+Replace **standard** of **launchType** to **multiton** in the configuration file.
+
+## cl.bundlemanager.21 Deleted the atomicService Tag from the app.json File
+The **atomicService** tag is deleted from the **app.json** file.
+
+**Change Impact**<br>
+If this tag is used, an error is reported during compilation on DevEco Studio.
+
+**Adaptation Guide**<br>
+Delete the **atomicService** tag from your code.
+
+## cl.bundlemanager.22 Added the bundleType Tag to the app.json File
+The **bundleType** tag is added to the **app.json** file.
+
+**Change Impact**<br>
+For an existing ability with [installationFree](../../../application-dev/quick-start/module-configuration-file.md) set to **true**, **bundleType** must be set to **atomicService** in the **app.json** file. Otherwise, the packaging fails.
+
+**Adaptation Guide**<br>
+Add the [bundleType](../../../application-dev/quick-start/app-configuration-file.md) tag. This tag can be left blank. The default value is **app**. The setting of this tag and the [installationFree](../../../application-dev/quick-start/module-configuration-file.md) field in the **module.json** file must meet the following rules:
+- If **bundleType** is **app**, **installationFree** must be set to **false**.
+- If **bundleType** is **atomicService**, **installationFree** must be set to **true**.
+
+## cl.bundlemanager.23 Deleted the split Field from the ApplicationInfo Struct
+
+The **split** field is deleted from the [ApplicationInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/ApplicationInfo.d.ts) struct.
+
+**Change Impact**<br>
+If the **split** field is used in your code, the compilation fails.
+
+**Key API/Component Changes**<br>
+The **split** field is deleted from the [ApplicationInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/ApplicationInfo.d.ts) struct.
+
+**Adaptation Guide**<br>
+Delete the **split** field from the **ApplicationInfo** struct of your code. The stage model always forcibly splits bundles.
+
+## cl.bundlemanager.24 Deleted the atomicServiceModuleType Field from the HapModuleInfo Struct
+
+The **atomicServiceModuleType** field is deleted from the [HapModuleInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/HapModuleInfo.d.ts) struct.
+
+**Change Impact**<br>
+If the **atomicServiceModuleType** field is used in your code, the compilation fails.
+
+**Key API/Component Changes**<br>
+The **atomicServiceModuleType** field is deleted from the [HapModuleInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/HapModuleInfo.d.ts) struct.
+
+**Adaptation Guide**<br>
+Record the setting of the **atomicServiceModuleType** field, delete it from the [HapModuleInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/HapModuleInfo.d.ts) struct, and set the **moduleType** field in the [HapModuleInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/HapModuleInfo.d.ts) struct to the recorded value.
+
+## cl.bundlemanager.25 Deleted the AtomicServiceModuleType Enumerated Value
+
+The **atomicServiceModuleType** field is deleted from the [HapModuleInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/HapModuleInfo.d.ts) struct.
+
+**Change Impact**<br>
+If the **atomicServiceModuleType** field is used in your code, the compilation fails.
+
+**Key API/Component Changes**<br>
+The **atomicServiceModuleType** field is deleted from the [HapModuleInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/HapModuleInfo.d.ts) struct.
+
+**Adaptation Guide**<br>
+Record the setting of the **atomicServiceModuleType** field, delete it from the [HapModuleInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/HapModuleInfo.d.ts) struct, and set the **moduleType** field in the [HapModuleInfo](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/bundleManager/HapModuleInfo.d.ts) struct to the recorded value.
diff --git a/en/release-notes/changelogs/v3.2-release/changelogs-resourceschedule.md b/en/release-notes/changelogs/v3.2-release/changelogs-resourceschedule.md
new file mode 100644
index 0000000000000000000000000000000000000000..283f2796178e294f68f755ea2570f7cc1a24a634
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-release/changelogs-resourceschedule.md
@@ -0,0 +1,21 @@
+# Resource Scheduler Subsystem Changelog
+
+## cl.resourceschedule.workScheduler 
+The data type of the **parameters** attribute value is changed. Specifically, the number, string, and boolean types are supported, but the any type is not.
+
+**Change Impact**
+
+For applications developed based on OpenHarmony3.2.10.7 and later SDK versions, the **parameters** attribute value can use the number, string, and boolean types only. If it uses the any type, a compilation error is reported.
+
+**Key API/Component Changes**
+
+The **parameters** attribute in @ohos.resourceschedule.workScheduler.d.ts is changed.
+
+| Class| API Type| Statement Before the Change| Statement After the Change| 
+|  -- | -- | -- | -- |
+| workScheduler.WorkInfo | field | parameters?: {[key: string]: any} | parameters?: {[key: string]: number | string | boolean} | 
+
+
+**Adaptation Guide**
+
+The **parameters** attribute uses the {[key: string]: number | string | boolean} data type.
diff --git a/en/release-notes/changelogs/v3.2-release/changelogs-util.md b/en/release-notes/changelogs/v3.2-release/changelogs-util.md
new file mode 100644
index 0000000000000000000000000000000000000000..52035aa2be49e1f11d72e91ec65f413112f5f13a
--- /dev/null
+++ b/en/release-notes/changelogs/v3.2-release/changelogs-util.md
@@ -0,0 +1,99 @@
+# Util Subsystem Changelog
+
+Compared with OpenHarmony 3.2 Beta4, OpenHarmony 3.2.10.7(MR) has the following API changes in the util subsystem.
+
+## cl.util.1. randomUUID Name Changed
+The **randomUUID** function name is changed to **generateRandomUUID**.
+
+Before change: function randomUUID(entropyCache?: boolean): string <br>After change: function generateRandomUUID(entropyCache?: boolean): string
+
+You need to adapt your application.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module     | Method/Attribute/Enum/Constant  | Change Type|
+| :---------- | -------------------   | -------  |
+| @ohos.util  | function randomUUID(entropyCache?: boolean): string        | Deleted |
+| @ohos.util  | function generateRandomUUID(entropyCache?: boolean): string| Added |
+
+**Adaptation Guide**
+
+Refer to the code snippet below to call **generateRandomUUID** in your application.
+
+Example:
+
+```ts
+import util from '@ohos.util'
+let uuid = util.generateRandomUUID(true);
+console.log("RFC 4122 Version 4 UUID:" + uuid);
+// Output:
+// RFC 4122 Version 4 UUID:88368f2a-d5db-47d8-a05f-534fab0a0045
+```
+
+## cl.util.2 randomBinaryUUID Name Changed
+The **randomBinaryUUID** function name is changed to **generateRandomBinaryUUID**.
+
+Before change: function randomBinaryUUID(entropyCache?: boolean): Uint8Array<br>After change: function generateRandomBinaryUUID(entropyCache?: boolean): Uint8Array
+
+You need to adapt your application.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module     | Method/Attribute/Enum/Constant  | Change Type|
+| :---------- | -------------------   | -------  |
+| @ohos.util  | function randomBinaryUUID(entropyCache?: boolean): Uint8Array;       | Deleted |
+| @ohos.util  | function generateRandomBinaryUUID(entropyCache?: boolean): Uint8Array| Added |
+
+**Adaptation Guide**
+
+Refer to the code snippet below to call **generateRandomBinaryUUID** in your application.
+
+Example:
+
+```ts
+import util from '@ohos.util'
+let uuid = util.generateRandomBinaryUUID(true);
+console.log(JSON.stringify(uuid));
+// Output:
+// 138,188,43,243,62,254,70,119,130,20,235,222,199,164,140,150
+```
+
+## cl.util.3. contains Parameter Type in the LRUCache Class Changed
+The **contains** parameter type in the LRUCache class is changed from **object** to **K**.
+
+Before change: contains(key: object): boolean <br>After change: contains(key: K): boolean
+
+You need to adapt your application.
+
+**Change Impact**
+
+JS APIs in API version 9 are affected. Your application needs to adapt these APIs so that it can properly implement features in the SDK environment of the new version.
+
+**Key API/Component Changes**
+
+| Module    | Class    | Method/Attribute/Enum/Constant             | Change Type|
+| :--------  | ---------| -------------------------------- | -------- |
+| @ohos.util | LRUCache |  contains(key: object): boolean  | Deleted    |
+| @ohos.util | LRUCache |  contains(key: K): boolean       | Added    |
+
+**Adaptation Guide**
+
+Follow the code snippet to use the **contains** function in your application.
+
+Example:
+
+```ts
+import util from '@ohos.util'
+let pro = new util.LRUCache();
+pro.put(2,10);
+let obj = {1:"key"};
+let result = pro.contains(obj);
+```
diff --git a/zh-cn/application-dev/ability-deprecated/ability-brief.md b/zh-cn/application-dev/ability-deprecated/ability-brief.md
index 73f82080c8aa0e9dfe34fa02de7665c23dda3cf1..d38d11abe2d6052569e5068af6f5a870dc4fb164 100644
--- a/zh-cn/application-dev/ability-deprecated/ability-brief.md
+++ b/zh-cn/application-dev/ability-deprecated/ability-brief.md
@@ -37,7 +37,7 @@ Stage模型的设计，主要是为了开发者更加方便地开发出分布式
 
 ### Stage 模型
 
-- [Stage模型介绍（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/StageModel)
-- [窗口扩展（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/WindowExtAbility)
-- [系统任务管理（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/MissionManager)
-- [仿桌面应用（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/Launcher)
+- [Stage模型介绍（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/ApplicationModels/StageModel)
+- [窗口扩展（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SystemFeature/WindowManagement/WindowExtAbility)
+- [系统任务管理（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SystemFeature/ApplicationModels/MissionManager)
+- [仿桌面应用（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SystemFeature/ApplicationModels/Launcher)
diff --git a/zh-cn/application-dev/ability-deprecated/fa-brief.md b/zh-cn/application-dev/ability-deprecated/fa-brief.md
index 2110b961ba95a001bd2bace6c8be53763a2d4a21..208c6f786b7beb7581375efbcde47cf070efc9aa 100644
--- a/zh-cn/application-dev/ability-deprecated/fa-brief.md
+++ b/zh-cn/application-dev/ability-deprecated/fa-brief.md
@@ -40,21 +40,3 @@ FA模型的应用包的工程目录结构，请参考[OpenHarmony工程介绍](h
 
 对FA模型的应用包结构的配置说明，请参考[应用包结构说明（FA模型）](../quick-start/application-configuration-file-overview-fa.md)。
 
-
-
-## 相关实例
-
-针对FA模型下的Ability开发，有以下相关实例可供参考：
-
-- [`FaModel`：FA模型（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/FaModel)
-- [`DistributedCalc`：分布式计算器（JS）（API8）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/common/DistributeCalc)
-- [`DistributedCalc`：分布式计算器（ArkTS）（API8）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Preset/DistributeCalc)
-- [`DistributeGraffiti`：分布式涂鸦（ArkTS）（API8）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/DistributedGraffiti)
-- [分布式调度启动远程FA（JS）（API8）](https://gitee.com/openharmony/codelabs/tree/master/Distributed/RemoteStartFA)
-- [分布式新闻客户端（JS）（API8）](https://gitee.com/openharmony/codelabs/tree/master/Distributed/NewsDemo)
-- [分布式手写板（ArkTS）（Full SDK）（API8）](https://gitee.com/openharmony/codelabs/tree/master/Distributed/DistributeDatabaseDrawEts)
-- [分布式鉴权（JS）（API8）](https://gitee.com/openharmony/codelabs/tree/master/Distributed/GameAuthOpenH)
-- [分布式游戏手柄（ArkTS）（Full SDK）（API8）](https://gitee.com/openharmony/codelabs/tree/master/Distributed/HandleGameApplication)
-- [分布式邮件（ArkTS）（Full SDK）（API8）](https://gitee.com/openharmony/codelabs/tree/master/Distributed/OHMailETS)
-- [分布式亲子早教系统（ArkTS）（Full SDK）（API8）](https://gitee.com/openharmony/codelabs/tree/master/Distributed/OpenHarmonyPictureGame)
-- [分布式遥控器（ArkTS）（Full SDK）（API8）](https://gitee.com/openharmony/codelabs/tree/master/Distributed/RemoteControllerETS)
\ No newline at end of file
diff --git a/zh-cn/application-dev/ability-deprecated/fa-dataability.md b/zh-cn/application-dev/ability-deprecated/fa-dataability.md
index 1e1582333e31f788468b2aeabc00e306043250e4..45f62948d0e168b7c5ee3185e86044d51d3a702c 100644
--- a/zh-cn/application-dev/ability-deprecated/fa-dataability.md
+++ b/zh-cn/application-dev/ability-deprecated/fa-dataability.md
@@ -308,9 +308,3 @@ URI示例：
     ]
    );
    ```
-
-## 相关实例
-
-针对DataAbility开发，有以下相关实例可供参考：
-
-- [`DataAbility`：DataAbility的创建与访问（ArkTS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/DataAbility)
diff --git a/zh-cn/application-dev/ability-deprecated/fa-formability.md b/zh-cn/application-dev/ability-deprecated/fa-formability.md
index 2f39c01d18182afe4374306687623766ce3d6d91..d99d293062cbd844474be89162371ff28cca833c 100644
--- a/zh-cn/application-dev/ability-deprecated/fa-formability.md
+++ b/zh-cn/application-dev/ability-deprecated/fa-formability.md
@@ -399,9 +399,4 @@ onUpdate(formId) {
        }
      }
    }
-   ```
-## 相关实例
-
-针对FA模型卡片提供方的开发，有以下相关实例可供参考：
-- [`FormAbility`：FA模型卡片（ArkTS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/FormAbility)
-- [`FormLauncher`：卡片使用方（ArkTS）（API8）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/FormLauncher)
\ No newline at end of file
+   ```
\ No newline at end of file
diff --git a/zh-cn/application-dev/ability-deprecated/fa-pageability.md b/zh-cn/application-dev/ability-deprecated/fa-pageability.md
index 9ad33e499938bad83ee95f027bae5138f7d4e467..c6b8de1e7f5665bbcc0adb1f47571d41503f8611 100644
--- a/zh-cn/application-dev/ability-deprecated/fa-pageability.md
+++ b/zh-cn/application-dev/ability-deprecated/fa-pageability.md
@@ -220,9 +220,4 @@ export default {
     console.info('Application onActive')
   },
 }
-```
-## 相关实例
-
-针对PageAbility开发，有以下相关实例可供参考：
-
-- [`DMS`：分布式Demo（ArkTS）（API8）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/DMS)
\ No newline at end of file
+```
\ No newline at end of file
diff --git a/zh-cn/application-dev/ability-deprecated/fa-serviceability.md b/zh-cn/application-dev/ability-deprecated/fa-serviceability.md
index b49d943102b630a3214882624285a3dd51b21a6c..efc2ac0e92685008e84cf9358a61f54776e7f19d 100644
--- a/zh-cn/application-dev/ability-deprecated/fa-serviceability.md
+++ b/zh-cn/application-dev/ability-deprecated/fa-serviceability.md
@@ -267,7 +267,6 @@ featureAbility.startAbility(
 > 说明：
 > (1) 由于DeviceManager的getTrustedDeviceList等接口仅对系统应用开放，当前仅系统应用支持连接远程Service。
 > (2) API定义可见：[deviceManager模块](..\reference\apis\js-apis-device-manager.md)
-> (3) 参考Demo可见：[分布式Demo](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/DMS)
 
 在跨设备场景下，需要向用户申请数据同步的权限，首先在config.json里配置权限：
 
@@ -320,7 +319,6 @@ async function RequestPermission() {
 
 获取deviceId需要导入`@ohos.distributedHardware.deviceManager`模块，其中提供了getTrustedDeviceList等接口用于获取远端设备的deviceId。
  - 接口使用可参考[deviceManager模块](..\reference\apis\js-apis-device-manager.md)
- - 具体实现可参考[分布式Demo](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/DMS)
 
 连接远程Service，只需要在want内定义deviceId即可，示例代码如下：
 
@@ -337,8 +335,3 @@ let connectId = featureAbility.connectAbility(want, option);
 
 其余实现均与本地连接Service相同，参考[连接本地Service](fa-serviceability.md#连接本地service)的示例代码即可。
 
-## 相关实例
-
-针对ServiceAbility开发，有以下相关实例可供参考：
-- [`ServiceAbility`：ServiceAbility的创建与使用（ArkTS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/ServiceAbility)
-- [`DMS`：分布式Demo（ArkTS）（API8）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/DMS)
diff --git a/zh-cn/application-dev/ability-deprecated/stage-brief.md b/zh-cn/application-dev/ability-deprecated/stage-brief.md
index ca50e36fdd7cf0b5bcc3d7533bf7292ebed82e37..dc953ddf61c9e30bcb09a4a74d821f694aba8955 100644
--- a/zh-cn/application-dev/ability-deprecated/stage-brief.md
+++ b/zh-cn/application-dev/ability-deprecated/stage-brief.md
@@ -116,7 +116,7 @@ Stage模型的应用包的工程目录结构，请参考[OpenHarmony工程介绍
 
 针对Stage模型下的Ability开发，有以下相关实例可供参考：
 
-- [`StageModel`：Stage模型（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/StageModel)
-- [`WindowExtAbility`：窗口扩展（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/WindowExtAbility)
-- [`MissionManager`：系统任务管理（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/MissionManager)
-- [`Launcher`：仿桌面应用（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/Launcher)
+- [`StageModel`：Stage模型（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/ApplicationModels/StageModel)
+- [`WindowExtAbility`：窗口扩展（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SystemFeature/WindowManagement/WindowExtAbility)
+- [`MissionManager`：系统任务管理（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SystemFeature/ApplicationModels/MissionManager)
+- [`Launcher`：仿桌面应用（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SystemFeature/ApplicationModels/Launcher)
diff --git a/zh-cn/application-dev/ability-deprecated/stage-formextension.md b/zh-cn/application-dev/ability-deprecated/stage-formextension.md
index 8245b6a54d252b3a29434ae6501307ef5ae3cf19..5fb2da1c519db33ee6732570147dc4381fcbba5d 100644
--- a/zh-cn/application-dev/ability-deprecated/stage-formextension.md
+++ b/zh-cn/application-dev/ability-deprecated/stage-formextension.md
@@ -241,7 +241,7 @@ FormProvider类具体的API介绍详见[接口文档](../reference/apis/js-apis-
        }
 ```
 
-具体的持久化方法可以参考[轻量级数据存储开发指导](../database/database-preference-guidelines.md)。
+具体的持久化方法可以参考[轻量级数据存储开发指导](../database/data-persistence-by-preferences.md)。
 
 需要注意的是，卡片使用方在请求卡片时传递给提供方应用的Want数据中存在临时标记字段，表示此次请求的卡片是否为临时卡片：
 
@@ -414,5 +414,4 @@ onUpdate(formId) {
 ## 相关实例
 
 针对Stage模型卡片提供方的开发，有以下相关实例可供参考：
-- [`FormExtAbility`：Stage模型卡片（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/FormExtAbility)
-- [`GalleryForm`：图库卡片（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/GalleryForm)
\ No newline at end of file
+- [`FormExtAbility`：Stage模型卡片（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/Widget/FormExtAbility)
\ No newline at end of file
diff --git a/zh-cn/application-dev/ability-deprecated/stage-serviceextension.md b/zh-cn/application-dev/ability-deprecated/stage-serviceextension.md
index 01813d7f3aef4dcf9300904c66536c77e67ecf72..cc3ac137dbd3ae70ed9c335875ca80fdba566acd 100644
--- a/zh-cn/application-dev/ability-deprecated/stage-serviceextension.md
+++ b/zh-cn/application-dev/ability-deprecated/stage-serviceextension.md
@@ -71,9 +71,4 @@ OpenHarmony当前不支持三方应用创建ServiceExtensionAbility。
             console.log('onDestroy');
         }
     }
-    ```
-## 相关实例
-
-针对ServiceExtensionAbility开发，有以下相关实例可供参考：
-
-- [`ServiceExtAbility`：StageExtAbility的创建与使用（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/ServiceExtAbility)
+    ```
\ No newline at end of file
diff --git a/zh-cn/application-dev/application-models/Readme-CN.md b/zh-cn/application-dev/application-models/Readme-CN.md
index caa6087057de32781c3b7bfd182ebfccdab5e4c5..cff971e2fde4ca9753430f717c52151118b0a126 100644
--- a/zh-cn/application-dev/application-models/Readme-CN.md
+++ b/zh-cn/application-dev/application-models/Readme-CN.md
@@ -17,11 +17,10 @@
     - ExtensionAbility组件
       - [ExtensionAbility组件概述](extensionability-overview.md)
       - [ServiceExtensionAbility](serviceextensionability.md)
-      - [DataShareExtensionAbility（仅对系统应用开放）](datashareextensionability.md)
       - [AccessibilityExtensionAbility](accessibilityextensionability.md)
       - [EnterpriseAdminExtensionAbility](enterprise-extensionAbility.md)
       - [InputMethodExtensionAbility](inputmethodextentionability.md)
-      - [WindowExtensionAbility](windowextensionability.md)
+      - [WindowExtensionAbility（仅对系统应用开放）](windowextensionability.md)
     - 服务卡片开发指导（Stage模型）
       - [服务卡片概述](service-widget-overview.md)
       - 开发基于ArkTS UI的卡片
@@ -37,10 +36,10 @@
             - [卡片使用自定义绘制能力](arkts-ui-widget-page-custom-drawing.md)
           - 开发卡片事件
             - [卡片事件能力说明](arkts-ui-widget-event-overview.md)
-            - [通过FormExtensionAbility刷新卡片内容](arkts-ui-widget-event-formextensionability.md)
-            - [使用router事件跳转到指定页面](arkts-ui-widget-event-router.md)
+            - [使用router事件跳转到指定UIAbility](arkts-ui-widget-event-router.md)
             - [使用call事件拉起指定UIAbility到后台](arkts-ui-widget-event-call.md)
-            - [通过UIAbility刷新卡片内容](arkts-ui-widget-event-uiability.md)
+            - [通过message事件刷新卡片内容](arkts-ui-widget-event-formextensionability.md)
+            - [通过router或call事件刷新卡片内容](arkts-ui-widget-event-uiability.md)
           - 卡片数据交互
             - [卡片数据交互说明](arkts-ui-widget-interaction-overview.md)
             - [定时刷新和定点刷新](arkts-ui-widget-update-by-time.md)
@@ -64,8 +63,8 @@
       - [跨端迁移（仅对系统应用开放）](hop-cross-device-migration.md)
       - [多端协同（仅对系统应用开放）](hop-multi-device-collaboration.md)
     - [订阅系统环境变量的变化](subscribe-system-environment-variable-changes.md)
-  - 进程间通信
-    - [进程模型](process-model-stage.md)
+  - 了解进程模型
+    - [进程模型概述](process-model-stage.md)
     - 公共事件
       - [公共事件简介](common-event-overview.md)
       - 公共事件订阅
@@ -74,9 +73,10 @@
         - [静态订阅公共事件（仅对系统应用开放）](common-event-static-subscription.md)
         - [取消动态订阅公共事件](common-event-unsubscription.md)
       - [公共事件发布](common-event-publish.md)
+      - [移除粘性公共事件（仅对系统应用开放）](common-event-remove-sticky.md)
     - [后台服务](background-services.md)
-  - 线程间通信
-    - [线程模型](thread-model-stage.md)
+  - 了解线程模型
+    - [线程模型概述](thread-model-stage.md)
     - [使用Emitter进行线程间通信](itc-with-emitter.md)
     - [使用Worker进行线程间通信](itc-with-worker.md)
   - 任务管理
@@ -121,12 +121,12 @@
     - [FA模型的Context](application-context-fa.md)
     - [信息传递载体Want](want-fa.md)
     - [组件启动规则（FA模型）](component-startup-rules-fa.md)
-  - 进程间通信
-    - [进程模型](process-model-fa.md)
+  - 了解进程模型
+    - [进程模型概述](process-model-fa.md)
     - [公共事件](common-event-fa.md)
     - [后台服务](rpc.md)
-  - 线程间通信
-    - [线程模型](thread-model-fa.md)
+  - 了解线程模型
+    - [线程模型概述](thread-model-fa.md)
     - [线程间通信](itc-fa-overview.md)
   - [任务管理](mission-management-fa.md)
 - FA模型与Stage模型应用组件互通指导
diff --git a/zh-cn/application-dev/application-models/application-component-configuration-stage.md b/zh-cn/application-dev/application-models/application-component-configuration-stage.md
index d8859fe551f7136464f693591d912dd83ffd862f..dcea435f3b27aa3df0e37fdca4892a81a763a72d 100644
--- a/zh-cn/application-dev/application-models/application-component-configuration-stage.md
+++ b/zh-cn/application-dev/application-models/application-component-configuration-stage.md
@@ -2,12 +2,12 @@
 
 在开发应用时，需要配置应用的一些标签，例如应用的包名、图标等标识特征的属性。本文描述了在开发应用需要配置的一些关键标签。
 
-图标和标签通常一起配置，可以分为应用图标、应用标签和入口图标、入口标签，分别对应[app.json5配置文件](../quick-start/app-configuration-file.md)和[module.json5配置文件](../quick-start/module-configuration-file.md)文件中的icon和label标签。
+图标和标签通常一起配置，可以分为应用图标、应用标签和入口图标、入口标签，分别对应[app.json5配置文件](../quick-start/app-configuration-file.md)和[module.json5配置文件](../quick-start/module-configuration-file.md)中的icon和label标签。
 
-应用图标和标签是在设置应用中使用，例如设置应用中的应用列表。入口图标是应用安装完成后在设备桌面上显示出来的，如图一所示。入口图标是以[UIAbility](uiability-overview.md)为粒度，支持同一个应用存在多个入口图标和标签，点击后进入对应的UIAbility界面。
+应用图标和标签是在设置应用中使用，例如设置应用中的应用列表。入口图标是应用安装完成后在设备桌面上显示出来的，如下图所示。入口图标是以[UIAbility](uiability-overview.md)为粒度，支持同一个应用存在多个入口图标和入口标签，点击后进入对应的UIAbility界面。
 
 **图1** 应用图标和标签    
-![application-component-configuration-stage](figures/application-component-configuration-stage.png)、
+![application-component-configuration-stage](figures/application-component-configuration-stage.png)
 
 
 - **应用包名配置**
@@ -62,6 +62,33 @@
     }
   }
   ```
+  OpenHarmony系统对无图标应用严格管控，防止一些恶意应用故意配置无入口图标，导致用户找不到软件所在的位置，无法操作卸载应用，在一定程度上保证用户的手机安全。
+
+  如果应用确需隐藏入口图标，需要配置AllowAppDesktopIconHide应用特权，具体配置方式参考[应用特权配置指南](../../device-dev/subsystems/subsys-app-privilege-config-guide.md)。详细的入口图标及入口标签的显示规则如下。
+
+  * HAP中包含UIAbility
+    * 在module.json5配置文件的abilities标签中设置了入口图标
+      * 该应用没有隐藏图标的特权
+        * 系统将使用该UIAbility配置的icon作为入口图标，并显示在桌面上。用户点击该图标，页面跳转到该UIAbility首页。
+        * 系统将使用该UIAbility配置的label作为入口标签，并显示在桌面上，如果没有配置label，系统将使用app.json5中的label作为入口标签，并显示在桌面上。
+      * 该应用具有隐藏图标的特权
+        * 桌面应用查询时不返回应用信息，不会在桌面上显示对应的入口图标和标签。
+    * 在module.json5配置文件的abilities标签中未设置入口图标
+      * 该应用没有隐藏图标的特权
+        * 系统将使用app.json5中的icon作为入口图标，并显示在桌面上。用户点击该图标，页面跳转到应用管理中对应的应用详情页面，如下图所示。
+        * 系统将使用app.json5中的label作为入口标签，并显示在桌面上。
+      * 该应用具有隐藏图标的特权
+        * 桌面应用查询时不返回应用信息，不会在桌面上显示对应的入口图标和标签。
+  * HAP中不包含UIAbility
+    * 该应用没有隐藏图标的特权
+      * 系统将使用app.json5中的icon作为入口图标，并显示在桌面上。用户点击该图标，页面跳转到应用管理中对应的应用详情页面，如下图所示。
+      * 系统将使用app.json5中的label作为入口标签，并显示在桌面上。
+    * 该应用具有隐藏图标的特权
+      * 桌面应用查询时不返回应用信息，不会在桌面上显示对应的入口图标和标签。
+
+  **图2** 应用的详情页示意图  
+  ![应用的详情页例图](figures/application_details.jpg)
+
 - **应用版本声明配置**
   
   应用版本声明需要在工程的AppScope目录下的[app.json5配置文件](../quick-start/app-configuration-file.md)中配置versionCode标签和versionName标签。versionCode用于标识应用的版本号，该标签值为32位非负整数。此数字仅用于确定某个版本是否比另一个版本更新，数值越大表示版本越高。versionName标签标识版本号的文字描述。
diff --git a/zh-cn/application-dev/application-models/arkts-ui-widget-event-call.md b/zh-cn/application-dev/application-models/arkts-ui-widget-event-call.md
index c510ff43815644db58e86a9e2a98cf5f7fb5e6bb..50e43ab959093891ccb81408864faf66ce4957fd 100644
--- a/zh-cn/application-dev/application-models/arkts-ui-widget-event-call.md
+++ b/zh-cn/application-dev/application-models/arkts-ui-widget-event-call.md
@@ -1,7 +1,7 @@
 # 使用call事件拉起指定UIAbility到后台
 
 
-许多应用希望借助卡片的能力，实现和应用在前台时相同的功能。例如音乐卡片，卡片上提供播放、暂停等按钮，点击不同按钮将触发音乐应用的不同功能，进而提高用户的体验。在卡片中使用**postCardAction**接口的call能力，能够将卡片提供方应用拉到后台。同时，call能力提供了调用应用指定方法、传递数据的功能，使应用在后台运行时可以通过卡片上的按钮执行不同的功能。
+许多应用希望借助卡片的能力，实现和应用在前台时相同的功能。例如音乐卡片，卡片上提供播放、暂停等按钮，点击不同按钮将触发音乐应用的不同功能，进而提高用户的体验。在卡片中使用**postCardAction**接口的call能力，能够将卡片提供方应用的指定的UIAbility拉到后台。同时，call能力提供了调用应用指定方法、传递数据的功能，使应用在后台运行时可以通过卡片上的按钮执行不同的功能。
 
 
 通常使用按钮控件来触发call事件，示例代码如下：
@@ -52,38 +52,38 @@
   
   ```ts
   import UIAbility from '@ohos.app.ability.UIAbility';
-  
+
   function FunACall(data) {
     // 获取call事件中传递的所有参数
-    console.info('FunACall param:' + JSON.stringify(data.readString()));
+    console.log('FunACall param:' + JSON.stringify(data.readString()));
     return null;
   }
-  
+
   function FunBCall(data) {
-    console.info('FunACall param:' + JSON.stringify(data.readString()));
+    console.log('FunACall param:' + JSON.stringify(data.readString()));
     return null;
   }
   
   export default class CameraAbility extends UIAbility {
     // 如果UIAbility第一次启动，在收到call事件后会触发onCreate生命周期回调
     onCreate(want, launchParam) {
-      try {
-        // 监听call事件所需的方法
-        this.callee.on('funA', FunACall);
-        this.callee.on('funB', FunBCall);
-      } catch (error) {
-        console.error(`Failed to register callee on. Cause: ${JSON.stringify(err)}`);
-      }
+        try {
+            // 监听call事件所需的方法
+            this.callee.on('funA', FunACall);
+            this.callee.on('funB', FunBCall);
+        } catch (error) {
+            console.log('register failed with error. Cause: ' + JSON.stringify(error));
+        }
     }
-  
+
     // 进程退出时，解除监听
     onDestroy() {
-      try {
-        this.callee.off('funA');
-        this.callee.off('funB');
-      } catch (err) {
-        console.error(`Failed to register callee off. Cause: ${JSON.stringify(err)}`);
-      }
+        try {
+            this.callee.off('funA');
+            this.callee.off('funB');
+        } catch (error) {
+            console.log('register failed with error. Cause: ' + JSON.stringify(error));
+        }
     }
   };
   ```
diff --git a/zh-cn/application-dev/application-models/arkts-ui-widget-event-formextensionability.md b/zh-cn/application-dev/application-models/arkts-ui-widget-event-formextensionability.md
index cc4533c53b8e6d767d478ee2cf1e408250dab038..5ce615a7a3d201f0179fe871654cf614f8d88a21 100644
--- a/zh-cn/application-dev/application-models/arkts-ui-widget-event-formextensionability.md
+++ b/zh-cn/application-dev/application-models/arkts-ui-widget-event-formextensionability.md
@@ -1,7 +1,7 @@
-# 通过FormExtensionAbility刷新卡片内容
+# 通过message事件刷新卡片内容
 
 
-在卡片页面中可以通过**postCardAction**接口触发message事件至FormExtensionAbility，然后由FormExtensionAbility刷新卡片内容，下面是这种刷新方式的简单示例。
+在卡片页面中可以通过**postCardAction**接口触发message事件拉起FormExtensionAbility，然后由FormExtensionAbility刷新卡片内容，下面是这种刷新方式的简单示例。
 
 
 - 在卡片页面通过注册Button的onClick点击事件回调，并在回调中调用**postCardAction**接口触发事件至FormExtensionAbility。
diff --git a/zh-cn/application-dev/application-models/arkts-ui-widget-event-overview.md b/zh-cn/application-dev/application-models/arkts-ui-widget-event-overview.md
index 06068236ace195c00aaf31409c3af6bb0ef2c74a..b2a99b1618af9db2a2ae983c36267425c8223ab3 100644
--- a/zh-cn/application-dev/application-models/arkts-ui-widget-event-overview.md
+++ b/zh-cn/application-dev/application-models/arkts-ui-widget-event-overview.md
@@ -21,7 +21,7 @@ action参数说明：
 
 | **Key** | **Value** | **样例描述** |
 | -------- | -------- | -------- |
-| "action" | string | action的类型，支持三种预定义的类型：<br/>-&nbsp;"router"：应用跳转，触发后会跳转到对应UIAbility，仅允许跳转到当前应用的UIAbility。<br/>-&nbsp;"message"：自定义消息，触发后会调用提供方FormExtensionAbility的[onFormEvent()](../reference/apis/js-apis-app-form-formExtensionAbility.md#onformevent)生命周期回调。<br/>-&nbsp;"call"：应用非前台启动，触发后会启动当前应用的UIAbility，但不会调度到前台，call的目标应用需要具备后台运行权限([ohos.permission.KEEP_BACKGROUND_RUNNING](../security/permission-list.md#ohospermissionkeep_background_running))。 |
+| "action" | string | action的类型，支持三种预定义的类型：<br/>-&nbsp;"router"：跳转到提供方应用的指定UIAbility。<br/>-&nbsp;"message"：自定义消息，触发后会调用提供方FormExtensionAbility的[onFormEvent()](../reference/apis/js-apis-app-form-formExtensionAbility.md#onformevent)生命周期回调。<br/>-&nbsp;"call"：后台启动提供方应用。触发后会拉起提供方应用的指定UIAbility，但不会调度到前台。提供方应用需要具备后台运行权限([ohos.permission.KEEP_BACKGROUND_RUNNING](../security/permission-list.md#ohospermissionkeep_background_running))。 |
 | "bundleName" | string | "router"&nbsp;/&nbsp;"call"&nbsp;类型时跳转的包名，可选。 |
 | "moduleName" | string | "router"&nbsp;/&nbsp;"call"&nbsp;类型时跳转的模块名，可选。 |
 | "abilityName" | string | "router"&nbsp;/&nbsp;"call"&nbsp;类型时跳转的UIAbility名，必填。 |
@@ -61,13 +61,4 @@ Button('拉至后台')
   })
 ```
 
-以下是卡片开发过程中可以通过卡片事件实现的典型开发场景：
-
-
-- [通过FormExtensionAbility刷新卡片内容](arkts-ui-widget-event-formextensionability.md)
-
-- [通过UIAbility刷新卡片内容](arkts-ui-widget-event-uiability.md)
-
-- [使用router事件跳转到指定页面](arkts-ui-widget-event-router.md)
-
-- [使用call事件拉起指定UIAbility到后台](arkts-ui-widget-event-call.md)
+以下介绍通过卡片事件实现的典型开发场景。
\ No newline at end of file
diff --git a/zh-cn/application-dev/application-models/arkts-ui-widget-event-router.md b/zh-cn/application-dev/application-models/arkts-ui-widget-event-router.md
index bbb3fd3e88248ad600a834075f121fa1595dd47e..19fe644cd4c7bc00b692483ff2e57b853da23eef 100644
--- a/zh-cn/application-dev/application-models/arkts-ui-widget-event-router.md
+++ b/zh-cn/application-dev/application-models/arkts-ui-widget-event-router.md
@@ -1,6 +1,7 @@
-# 使用router事件跳转到指定页面
+# 使用router事件跳转到指定UIAbility
 
-在卡片中使用**postCardAction**接口的router能力，能够快速拉起卡片提供方应用，因此页面较多的应用往往会通过卡片提供不同的跳转按钮，实现一键直达的效果。例如相机卡片，卡片上提供拍照、录像等按钮，点击不同按钮将拉起相机应用的不同页面，从而提高用户的体验。  
+
+在卡片中使用**postCardAction**接口的router能力，能够快速拉起卡片提供方应用的指定UIAbility，因此UIAbility较多的应用往往会通过卡片提供不同的跳转按钮，实现一键直达的效果。例如相机卡片，卡片上提供拍照、录像等按钮，点击不同按钮将拉起相机应用的不同UIAbility，从而提高用户的体验。
 ![WidgerCameraCard](figures/WidgerCameraCard.png)
 
 
diff --git a/zh-cn/application-dev/application-models/arkts-ui-widget-event-uiability.md b/zh-cn/application-dev/application-models/arkts-ui-widget-event-uiability.md
index 350d014866dd5b1bee9c899dc0a8f4e03abb7a22..b80050596bd791dd69743819aabeb87955b627e5 100644
--- a/zh-cn/application-dev/application-models/arkts-ui-widget-event-uiability.md
+++ b/zh-cn/application-dev/application-models/arkts-ui-widget-event-uiability.md
@@ -1,9 +1,9 @@
-# 通过UIAbility刷新卡片内容
+# 通过router或call事件刷新卡片内容
 
 
 在卡片页面中可以通过**postCardAction**接口触发router事件或者call事件拉起UIAbility，然后由UIAbility刷新卡片内容，下面是这种刷新方式的简单示例。
 
-## 通过postCardAction接口触发router事件
+## 通过router事件刷新卡片内容
 
 - 在卡片页面通过注册Button的onClick点击事件回调，并在回调中调用**postCardAction**接口触发router事件至FormExtensionAbility。
   
@@ -86,10 +86,10 @@
   }
   ```
 
-## 通过postCardAction接口触发call事件
+## 通过call事件刷新卡片内容
 
 - 在使用**postCardAction**接口的call事件时，需要在FormExtensionAbility中的onAddForm生命周期回调中更新formId。
-  
+   
    ```ts
    import formBindingData from '@ohos.app.form.formBindingData';
    import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
@@ -117,7 +117,7 @@
   struct WidgetCard {
     @LocalStorageProp('detail') detail: string = 'init';
     @LocalStorageProp('formId') formId: string = '0';
-  
+
     build() {
       Column() {
         Button('拉至后台')
@@ -150,8 +150,8 @@
   import formProvider from '@ohos.app.form.formProvider';
   import formInfo from '@ohos.app.form.formInfo';
   
-  const MSG_SEND_METHOD: string = 'funA';
-  
+  const MSG_SEND_METHOD: string = 'funA'
+
   // 在收到call事件后会触发callee监听的方法
   function FunACall(data) {
     // 获取call事件中传递的所有参数
@@ -180,7 +180,7 @@
          // 监听call事件所需的方法
         this.callee.on(MSG_SEND_METHOD, FunACall);
       } catch (error) {
-        console.info(`${MSG_SEND_METHOD} register failed with error ${JSON.stringify(error)}`)
+        console.log(`${MSG_SEND_METHOD} register failed with error ${JSON.stringify(error)}`)
       }
     }
     ...
diff --git a/zh-cn/application-dev/application-models/arkts-ui-widget-update-by-time.md b/zh-cn/application-dev/application-models/arkts-ui-widget-update-by-time.md
index 862e5f5232f73238cc3d3b663cea50e3e237b6b9..49ddb9adeb6d6b805bdd5f4732686733d21dd6cb 100644
--- a/zh-cn/application-dev/application-models/arkts-ui-widget-update-by-time.md
+++ b/zh-cn/application-dev/application-models/arkts-ui-widget-update-by-time.md
@@ -5,7 +5,7 @@
 当前卡片框架提供了如下几种按时间刷新卡片的方式：
 
 
-- 定时刷新：表示在一定时间间隔内自动刷新卡片内容。可以在form_config.json配置文件的[`updateDuration`](arkts-ui-widget-configuration.md)字段中进行设置。例如，可以将刷新时间设置为每小时一次。
+- 定时刷新：表示在一定时间间隔内调用[onUpdateForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onupdateform)的生命周期回调函数自动刷新卡片内容。可以在form_config.json配置文件的[`updateDuration`](arkts-ui-widget-configuration.md)字段中进行设置。例如，可以将刷新时间设置为每小时一次。
   
   > **说明：**
   >
diff --git a/zh-cn/application-dev/application-models/common-event-overview.md b/zh-cn/application-dev/application-models/common-event-overview.md
index 5a350a436d88c6013a675beccbc1766ba409611b..4789a84f3cb05653c0dc5778e5be10445d2098c5 100644
--- a/zh-cn/application-dev/application-models/common-event-overview.md
+++ b/zh-cn/application-dev/application-models/common-event-overview.md
@@ -7,18 +7,15 @@ OpenHarmony通过CES（Common Event Service，公共事件服务）为应用程
 公共事件从系统角度可分为：系统公共事件和自定义公共事件。
 
 
-- 系统公共事件：CES内部定义的公共事件，只有系统应用和系统服务才能发布，例如HAP安装，更新，卸载等公共事件。目前支持的系统公共事件详见[系统公共事件列表](../reference/apis/js-apis-commonEventManager.md#support)。
-
-- 自定义公共事件：应用自定义一些公共事件用来实现跨进程的事件通信能力。
+- 系统公共事件：CES内部定义的公共事件，当前仅支持系统应用和系统服务发布，例如HAP安装，更新，卸载等公共事件。目前支持的系统公共事件请参见[系统公共事件列表](../reference/apis/commonEventManager-definitions.md)。
+- 自定义公共事件：应用定义的公共事件，可用于实现跨进程的事件通信能力。
 
 
 公共事件按发送方式可分为：无序公共事件、有序公共事件和粘性公共事件。
 
 
-- 无序公共事件：CES转发公共事件时，不考虑订阅者是否接收到，且订阅者接收到的顺序与其订阅顺序无关。
-
-- 有序公共事件：CES转发公共事件时，根据订阅者设置的优先级等级，在接收到优先级较高的一个订阅者回复后，再向下一个优先级较低的订阅者转发公共事件。具有相同优先级的订阅者将按随机顺序收到公共事件。
-
+- 无序公共事件：CES在转发公共事件时，不考虑订阅者是否接收到该事件，也不保证订阅者接收到该事件的顺序与其订阅顺序一致。
+- 有序公共事件：CES在转发公共事件时，根据订阅者设置的优先级等级，优先将公共事件发送给优先级较高的订阅者，等待其成功接收该公共事件之后再将事件发送给优先级较低的订阅者。如果有多个订阅者具有相同的优先级，则他们将随机接收到公共事件。
 - 粘性公共事件：能够让订阅者收到在订阅前已经发送的公共事件就是粘性公共事件。普通的公共事件只能在订阅后发送才能收到，而粘性公共事件的特殊性就是可以先发送后订阅，同时也支持先订阅后发送。发送粘性事件必须是系统应用或系统服务，粘性事件发送后会一直存在系统中，且发送者需要申请`ohos.permission.COMMONEVENT_STICKY`权限，配置方式请参见[配置文件权限声明](../security/accesstoken-guidelines.md#配置文件权限声明)。
 
 
diff --git a/zh-cn/application-dev/application-models/common-event-static-subscription.md b/zh-cn/application-dev/application-models/common-event-static-subscription.md
index 5cbe408e03c07950ca0e337fb5f76c992765442d..3c77b9fd6e6846773bab03f4616a5592278598e0 100644
--- a/zh-cn/application-dev/application-models/common-event-static-subscription.md
+++ b/zh-cn/application-dev/application-models/common-event-static-subscription.md
@@ -2,29 +2,37 @@
 
 ## 场景介绍
 
-静态订阅者在未接收订阅的目标事件时，处于未拉起状态，当系统或应用发布了指定的公共事件后，静态订阅者将被拉起，并执行onReceiveEvent回调，开发者可通过在onReceiveEvent回调中执行业务逻辑，实现当应用接收到特定公共事件时执行业务逻辑的目的。例如，某应用希望在设备开机的时候执行一些初始化任务，那么该应用可以静态订阅开机事件，在收到开机事件后会拉起该应用，然后执行初始化任务。静态订阅是通过配置文件声明和实现继承自StaticSubscriberExtensionAbility的类实现对公共事件的订阅。**需要注意的是，静态订阅公共事件对系统功耗有一定影响，建议谨慎使用**。
+静态订阅者在未接收订阅的目标事件时，处于未拉起状态。当系统或应用发布了指定的公共事件后，静态订阅者将被拉起，并执行[`onReceiveEvent()`](../reference/apis/js-apis-application-staticSubscriberExtensionAbility.md#staticsubscriberextensionabilityonreceiveevent)回调。
+
+开发者可以通过在[`onReceiveEvent()`](../reference/apis/js-apis-application-staticSubscriberExtensionAbility.md#staticsubscriberextensionabilityonreceiveevent)回调中执行业务逻辑，实现当应用接收到特定公共事件时执行业务逻辑的目的。例如，应用希望在设备开机时执行一些初始化任务，那么该应用可以静态订阅开机事件，在收到开机事件后会拉起该应用，然后执行初始化任务。
+
+静态订阅是通过配置文件声明和实现继承自[`StaticSubscriberExtensionAbility`](../reference/apis/js-apis-application-staticSubscriberExtensionAbility.md)的类实现对公共事件的订阅。
+
+> **说明：**
+>
+> 需要注意的是，静态订阅公共事件对系统功耗有一定影响，建议谨慎使用。
 
 ## 开发步骤
 
-1. 静态订阅者声明
+1. 静态订阅者声明。
 
-   声明一个静态订阅者，首先需要在工程中新建一个ExtensionAbility，该ExtensionAbility从StaticSubscriberExtensionAbility派生，其代码实现如下：
+   声明一个静态订阅者，首先需要在工程中新建一个ExtensionAbility，该ExtensionAbility从StaticSubscriberExtensionAbility派生。
+
+   开发者可以在[`onReceiveEvent()`](../reference/apis/js-apis-application-staticSubscriberExtensionAbility.md#staticsubscriberextensionabilityonreceiveevent)回调中实现业务逻辑。
 
    ```ts
    import StaticSubscriberExtensionAbility from '@ohos.application.StaticSubscriberExtensionAbility'
    
    export default class StaticSubscriber extends StaticSubscriberExtensionAbility {
      onReceiveEvent(event) {
-       console.info('onReceiveEvent, event:' + event.event);
+       console.info('onReceiveEvent, event: ' + event.event);
      }
    }
    ```
 
-   开发者可以在onReceiveEvent中实现业务逻辑。
-
-2. 静态订阅者工程配置
+2. 静态订阅者工程配置。
 
-   在完成静态订阅者的代码实现后，需要将该订阅者配置到系统的module.json5中，配置形式如下：
+   在完成静态订阅者的代码实现后，需要在[module.json5配置文件](../quick-start/module-configuration-file.md)中进行配置订阅者信息。
 
    ```ts
    {
@@ -33,7 +41,7 @@
        "extensionAbilities": [
          {
            "name": "StaticSubscriber",
-           "srcEntry": "./ets/StaticSubscriber/StaticSubscriber.ts",
+           "srcEntry": "./ets/staticsubscriber/StaticSubscriber.ts",
            "description": "$string:StaticSubscriber_desc",
            "icon": "$media:icon",
            "label": "$string:StaticSubscriber_label",
@@ -52,19 +60,20 @@
    }
    ```
 
-   上述json文件主要关注以下字段：
+   其中部分字段解释如下：
 
-   - srcEntry : 表示ExtensionAbility的入口文件路径，即步骤2中声明的静态订阅者所在的文件路径
+   - srcEntry：表示ExtensionAbility的入口文件路径，即步骤2中声明的静态订阅者所在的文件路径。
 
-   - type: 表示ExtensionAbility的类型，对于静态订阅者需要声明为“staticSubscriber”
+   - type：表示ExtensionAbility的类型，对于静态订阅者需要声明为`staticSubscriber`。
 
-   - metadata: 表示ExtensionAbility的二级配置文件信息。由于不同的ExtensionAbility类型其配置信息不尽相同，因此需要使用不同的config文件表示其具体配置信息。
-        - name：表示ExtensionAbility的类型名称，对于静态订阅类型，name必须声明为“ohos.extension.staticSubscriber”，否则无法识别为静态订阅者；
-        - resource: 字段表示ExtensionAbility的配置信息路径，由开发者自行定义，在本例中表示路径为“resources/base/profile/subscribe.json"。
+   - metadata：表示ExtensionAbility的二级配置文件信息。由于不同的ExtensionAbility类型其配置信息不尽相同，因此需要使用不同的config文件表示其具体配置信息。
+        - name：表示ExtensionAbility的类型名称，对于静态订阅类型，name必须声明为`ohos.extension.staticSubscriber`，否则无法识别为静态订阅者。
+        - resource：字段表示ExtensionAbility的配置信息路径，由开发者自行定义，在本例中表示路径为`resources/base/profile/subscribe.json`。
 
-   metadata指向的二级配置文件的通常形式如下：
 
-   ```ts
+3. 配置metadata指向的二级配置文件。
+
+   ```json
    {
      "commonEvents": [
        {
@@ -78,28 +87,32 @@
    }
    ```
 
-   需要注意二级配置文件必须按照此形式进行声明，否则会无法正确识别。下面对字段进行介绍：
-
-   - name: 静态订阅ExtensionAbility的名称，需要和module.json5中声明的ExtensionAbility的name一致
+   需要注意二级配置文件必须按照此形式进行声明，否则会无法正确识别。部分字段解释如下：
 
-   - permission：订阅者要求的发布者需要具备的权限，对于发布了目标事件但不具备permission中声明的权限的发布者将被视为非法事件不予发布
+   - name: 静态订阅ExtensionAbility的名称，需要和module.json5中声明的ExtensionAbility的name一致。
+   - permission：订阅者要求的发布者需要具备的权限，对于发布了目标事件但不具备permission中声明的权限的发布者将被视为非法事件不予发布。
+   - events：订阅的目标事件列表。
 
-   - events: 订阅的目标事件列表
+4. 修改设备的[预置配置文件](https://gitee.com/openharmony/vendor_hihope/blob/master/rk3568/preinstall-config/install_list_permissions.json)。[预置配置文件](https://gitee.com/openharmony/vendor_hihope/blob/master/rk3568/preinstall-config/install_list_permissions.json)在设备上的路径为`/system/etc/app/install_list_permission.json`，设备开机启动时会读取该配置文件，在应用安装会对在文件中配置的`allowCommonEvent`公共事件类型进行授权。预授权配置文件字段内容包括`bundleName`、`app_signature`和`allowCommonEvent`。
 
-3. 修改设备系统配置文件
+   - `bundleName`字段配置为应用的Bundle名称。
+   - `app_signature`字段配置为应用的指纹信息。指纹信息的配置参见[应用特权配置指南](../../device-dev/subsystems/subsys-app-privilege-config-guide.md#install_list_capabilityjson中配置)。
+   - `allowCommonEvent`字段配置为允许静态广播拉起的公共事件项。
 
-    修改设备系统配置文件 **/system/etc/app/install_list_capability.json**，将静态订阅应用者的包名添加至该json文件中即可。
+   > **说明**：当前仅支持预置应用配置该文件。
 
-    ```json
-   {
-    "install_list": [
-            {
-                "bundleName": "ohos.extension.staticSubscriber",
-                "allowCommonEvent": ["usual.event.A", "usual.event.B"],
-            }
-        ]
-    }
+   ```json
+   [
+     ...
+     {
+       "bundleName": "com.example.myapplication", // Bundle名称
+       "app_signature": ["****"], // 指纹信息
+       "allowCommonEvent": ["usual.event.A", "usual.event.B"], // 允许静态广播拉起的公共事件项
+       ]
+     }
+   ]
    ```
+
 ## 相关示例
 
 针对StaticSubscriberExtensionAbility开发，可参考如下实例：
diff --git a/zh-cn/application-dev/application-models/dataability-overview.md b/zh-cn/application-dev/application-models/dataability-overview.md
index 02423a78c9b6f5ee03ccfd0a0ed414aee88980d0..40a2b556a376ace6c5f4eb9dcc77d052ae175c22 100644
--- a/zh-cn/application-dev/application-models/dataability-overview.md
+++ b/zh-cn/application-dev/application-models/dataability-overview.md
@@ -8,9 +8,3 @@ DataAbility，即"使用Data模板的Ability"，主要用于对外部提供统
 
 
 数据的存放形式多样，可以是数据库，也可以是磁盘上的文件。DataAbility对外提供对数据的增、删、改、查，以及打开文件等接口，这些接口的具体实现由开发者提供。
-
-## 相关实例
-
-基于DataAbility组件的开发，以下相关实例可供参考：
-
-- [`DataAbility`：DataAbility的创建与访问（ArkTS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/DataAbility)
\ No newline at end of file
diff --git a/zh-cn/application-dev/application-models/explicit-implicit-want-mappings.md b/zh-cn/application-dev/application-models/explicit-implicit-want-mappings.md
index 080d707d52a8912950ba051a1dc027f32b7118a2..192a25c1524ae4c68c874063b75130ad5392fcc9 100644
--- a/zh-cn/application-dev/application-models/explicit-implicit-want-mappings.md
+++ b/zh-cn/application-dev/application-models/explicit-implicit-want-mappings.md
@@ -52,6 +52,8 @@
 
 将调用方传入的want参数的action与待匹配应用组件的skills配置中的actions进行匹配。
 
+- 调用方传入的want参数的action为空，待匹配Ability的skills配置中的actions为空，则action匹配失败。
+
 - 调用方传入的want参数的action不为空，待匹配应用组件的skills配置中的actions为空，则action匹配失败。
 
 - 调用方传入的want参数的action为空，待匹配应用组件的skills配置中的actions不为空，则action匹配成功。
diff --git a/zh-cn/application-dev/application-models/fa-model-development-overview.md b/zh-cn/application-dev/application-models/fa-model-development-overview.md
index 1e664edf8f65e47bc5538eea37f6c3d3b7dcce13..ee0d68f7e84e93b54268c1d70df58890e9636b83 100644
--- a/zh-cn/application-dev/application-models/fa-model-development-overview.md
+++ b/zh-cn/application-dev/application-models/fa-model-development-overview.md
@@ -9,7 +9,7 @@
 | 任务 | 简介 | 相关指导 |
 | -------- | -------- | -------- |
 | 应用组件开发 | 本章节介绍了如何使用FA模型的PageAbility、ServiceAbility、DataAbility以及服务卡片进行应用开发。 | [应用/组件级配置](application-component-configuration-fa.md)<br/>[PageAbility开发指导](pageability-overview.md)<br/>[ServiceAbility开发指导](serviceability-overview.md)<br/>[DataAbility开发指导](dataability-overview.md)<br/>[服务卡片开发指导](widget-development-fa.md)<br/>[FA模型的Context](application-context-fa.md)<br/>[信息传递载体Want](want-fa.md) |
-| 进程间通信 | 本章节介绍了FA模型的进程模型以及几种常用的进程间通信方式。 | [公共事件](common-event-fa.md)<br/>[后台服务](rpc.md) |
-| 线程间通信 | 本章节介绍了FA模型的线程模型以及几种常用的线程间通信方式。 | [线程间通信](itc-fa-overview.md) |
+| 了解进程模型 | 本章节介绍了FA模型的进程模型以及几种常用的进程间通信方式。 | [公共事件](common-event-fa.md)<br/>[后台服务](rpc.md) |
+| 了解线程模型 | 本章节介绍了FA模型的线程模型以及几种常用的线程间通信方式。 | [线程间通信](itc-fa-overview.md) |
 | 任务管理 | 本章节介绍了FA模型中任务管理的基本概念和典型场景。 | [任务管理](mission-management-fa.md) |
 | 应用配置文件 | 本章节介绍FA模型中应用配置文件的开发要求。 | [FA模型应用配置文件](../quick-start/application-configuration-file-overview-fa.md) |
diff --git a/zh-cn/application-dev/application-models/figures/application_details.jpg b/zh-cn/application-dev/application-models/figures/application_details.jpg
new file mode 100644
index 0000000000000000000000000000000000000000..a2ba04f9143be7ca224ea77257e4ada4f76943c1
Binary files /dev/null and b/zh-cn/application-dev/application-models/figures/application_details.jpg differ
diff --git a/zh-cn/application-dev/application-models/figures/want-action.png b/zh-cn/application-dev/application-models/figures/want-action.png
index 1bc30791a3ec5d5564bf293b632d52ef5d4b7671..b6495466ec74e84d3ba887fdba5203b9dc4bf2f1 100644
Binary files a/zh-cn/application-dev/application-models/figures/want-action.png and b/zh-cn/application-dev/application-models/figures/want-action.png differ
diff --git a/zh-cn/application-dev/application-models/hop-cross-device-migration.md b/zh-cn/application-dev/application-models/hop-cross-device-migration.md
index ae9eb5bd2f164f527441958c57ddb6544e02061a..a7b82f117b886ab995e22cfb90c10d4a912f9c39 100644
--- a/zh-cn/application-dev/application-models/hop-cross-device-migration.md
+++ b/zh-cn/application-dev/application-models/hop-cross-device-migration.md
@@ -16,7 +16,7 @@
 
 跨端迁移流程如下图所示。
 
-  **图1** 跨端迁移流程图  
+**图1** 跨端迁移流程图  
 ![hop-cross-device-migration](figures/hop-cross-device-migration.png)
 
 
@@ -47,60 +47,38 @@
 
 ## 开发步骤
 
-1. 在module.json5配置数据同步权限，示例代码如下。
-   
+1. 需要申请`ohos.permission.DISTRIBUTED_DATASYNC`权限，配置方式请参见[配置文件权限声明](../security/accesstoken-guidelines.md#配置文件权限声明)。
+
+2. 同时需要在应用首次启动时弹窗向用户申请授权，使用方式请参见[向用户申请授权](../security/accesstoken-guidelines.md#向用户申请授权)。
+
+3. 在配置文件中配置跨端迁移相关标签字段。
+
+   配置应用支持迁移
+   在module.json5中配置continuable标签：true表示支持迁移，false表示不支持，默认为false。配置为false的UIAbility将被系统识别为无法迁移。
+
+
    ```json
    {
      "module": {
-       "requestPermissions":[  
-         {  
-           "name" : "ohos.permission.DISTRIBUTED_DATASYNC",
+       ...
+       "abilities": [
+         {
+           ...
+           "continuable": true,
          }
        ]
      }
    }
    ```
 
-2. 在配置文件中配置跨端迁移相关标签字段。
-   - 配置应用支持迁移
-      在module.json5中配置continuable标签：true表示支持迁移，false表示不支持，默认为false。配置为false的UIAbility将被系统识别为无法迁移。
-
-      
-      ```json
-      {
-        "module": {
-          // ...
-          "abilities": [
-            {
-              // ...
-              "continuable": true,
-            }
-          ]
-        }
-      }
-      ```
-   - 根据需要配置应用启动模式类型，配置详情请参照[UIAbility组件启动模式](uiability-launch-type.md)。
-
-3. 申请数据同步权限，弹框示例代码。
-   
-   ```ts
-   requestPermission() {   
-       let context = this.context
-       let permissions: Array<string> = ['ohos.permission.DISTRIBUTED_DATASYNC']   
-       context.requestPermissionsFromUser(permissions).then((data) => {   
-           console.info("Succeed to request permission from user with data: "+ JSON.stringify(data))
-       }).catch((error) => {       
-           console.info("Failed to request permission from user with error: "+ JSON.stringify(error))   
-       }) 
-   }
-   ```
+   根据需要配置应用启动模式类型，配置详情请参照[UIAbility组件启动模式](uiability-launch-type.md)。
 
 4. 在发起端UIAbility中实现[onContinue()](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncontinue)接口。
-     当应用触发迁移时，[onContinue()](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncontinue)接口在发起端被调用，开发者可以在该接口中保存迁移数据，实现应用兼容性检测，决定是否支持此次迁移。
+   当应用触发迁移时，[onContinue()](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncontinue)接口在发起端被调用，开发者可以在该接口中保存迁移数据，实现应用兼容性检测，决定是否支持此次迁移。
    - 保存迁移数据：开发者可以将要迁移的数据通过键值对的方式保存在wantParam中。
-   
+
    - 应用兼容性检测：开发者可以通过从wantParam中获取目标应用的版本号与本应用版本号做兼容性校验。
-   
+
    - 迁移决策：开发者可以通过onContinue接口的返回值决定是否支持此次迁移，返回值信息见[接口说明](#接口说明)。
 
      示例如下：
diff --git a/zh-cn/application-dev/application-models/inputmethodextentionability.md b/zh-cn/application-dev/application-models/inputmethodextentionability.md
index 1b09094d79e86bd1fce4145d6ba268cb387b35cd..c5be91b31631b8fae7aa731ce7c0823dc4ff5af9 100644
--- a/zh-cn/application-dev/application-models/inputmethodextentionability.md
+++ b/zh-cn/application-dev/application-models/inputmethodextentionability.md
@@ -16,6 +16,7 @@
   服务被首次创建时触发该回调，开发者可以在此进行一些初始化的操作，例如注册公共事件监听等。
 
   > **说明：**
+  >
   > 如果服务已创建，再次启动该InputMethodExtensionAbility不会触发onCreate()回调。
 
 - **onDestroy**
@@ -343,7 +344,7 @@
    ```ts
    {
      "module": {
-       // ...
+       ...
        "extensionAbilities": [
          {
            "description": "inputMethod",
@@ -359,10 +360,3 @@
    ```
 
 
-
-
-## 相关示例
-
-针对InputMethodExtensionAbility开发，有以下相关示例可供参考：
-
-- [Kika输入法](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/CompleteApps/KikaInput)
\ No newline at end of file
diff --git a/zh-cn/application-dev/application-models/itc-with-worker.md b/zh-cn/application-dev/application-models/itc-with-worker.md
index 994e3734307372051c32a2bae272bcb8b2977424..912654e0fdf29d5f472d588ca24c947b1cb58a93 100644
--- a/zh-cn/application-dev/application-models/itc-with-worker.md
+++ b/zh-cn/application-dev/application-models/itc-with-worker.md
@@ -10,13 +10,13 @@ Worker的开发步骤如下：
 1. 在工程的[模块级build-profile.json5](https://developer.harmonyos.com/cn/docs/documentation/doc-guides/ohos-building-configuration-0000001218440654#section6887184182020)文件的buildOption属性中添加配置信息。
 
    ```ts
-     "buildOption": {
-       "sourceOption": {
-         "workers": [
-           "./src/main/ets/workers/worker.ts"
-         ]
-       }
+   "buildOption": {
+     "sourceOption": {
+       "workers": [
+         "./src/main/ets/workers/worker.ts"
+       ]
      }
+   }
    ```
 
 2. 根据build-profile.json5中的配置创建对应的worker.ts文件。
@@ -28,9 +28,9 @@ Worker的开发步骤如下：
 
    // 处理来自主线程的消息
    parent.onmessage = function(message) {
-       console.info("onmessage: " + message)
-       // 发送消息到主线程
-       parent.postMessage("message from worker thread.")
+     console.info("onmessage: " + message)
+     // 发送消息到主线程
+     parent.postMessage("message from worker thread.")
    }
    ```
 
@@ -47,10 +47,10 @@ Worker的开发步骤如下：
 
       // 处理来自worker线程的消息
       wk.onmessage = function(message) {
-          console.info("message from worker: " + message)
+        console.info("message from worker: " + message)
 
-          // 根据业务按需停止worker线程
-          wk.terminate()
+        // 根据业务按需停止worker线程
+        wk.terminate();
       }
       ```
 
@@ -58,23 +58,22 @@ Worker的开发步骤如下：
 
       ```ts
       import worker from '@ohos.worker';
-
+      
       let wk = new worker.ThreadWorker("../workers/worker.ts");
-
+      
       // 发送消息到worker线程
       wk.postMessage("message from main thread.")
-
+      
       // 处理来自worker线程的消息
       wk.onmessage = function(message) {
-          console.info("message from worker: " + message)
-
-          // 根据业务按需停止worker线程
-          wk.terminate()
+        console.info("message from worker: " + message)
+      
+        // 根据业务按需停止worker线程
+        wk.terminate();
       }
       ```
 
-**说明：**
-
-- build-profile.json5中配置的worker.ts的相对路径都为`./src/main/ets/workers/worker.ts`时，在Stage模型下创建worker需要传入路径`entry/ets/workers/worker.ts`；在FA模型下创建worker需要传入路径`../workers/worker.ts`。
-
-- 主线程与Worker线程间支持的数据类型参考[序列化支持类型](../reference/apis/js-apis-worker.md#序列化支持类型)。
+> **说明：**
+>
+> - build-profile.json5中配置的worker.ts的相对路径都为`./src/main/ets/workers/worker.ts`时，在Stage模型下创建worker需要传入路径`entry/ets/workers/worker.ts`；在FA模型下创建worker需要传入路径`../workers/worker.ts`。
+> - 主线程与Worker线程间支持的数据类型参考[序列化支持类型](../reference/apis/js-apis-worker.md#序列化支持类型)。
diff --git a/zh-cn/application-dev/application-models/js-ui-widget-development.md b/zh-cn/application-dev/application-models/js-ui-widget-development.md
index 2f498681cb3e8e4e70a9f2391cabb4b53c9b7874..ce3d502f6539821846625f23cac749d9c362e456 100644
--- a/zh-cn/application-dev/application-models/js-ui-widget-development.md
+++ b/zh-cn/application-dev/application-models/js-ui-widget-development.md
@@ -81,7 +81,7 @@ Stage卡片开发，即基于[Stage模型](stage-model-development-overview.md)
 
 - [配置卡片配置文件](#配置卡片配置文件)：配置应用配置文件module.json5和profile配置文件。
 
-- [卡片数据交互](#卡片数据交互)：对卡片信息进行持久化管理。
+- [卡片信息的持久化](#卡片数据交互)：对卡片信息进行持久化管理。
 
 - [卡片数据交互](#卡片数据交互)：通过updateForm更新卡片显示的信息。
 
diff --git a/zh-cn/application-dev/application-models/module-switch.md b/zh-cn/application-dev/application-models/module-switch.md
index d0ef49e9b050111a88d7d608fdcef7daffb800fb..f6b663f1c7aea1e00f93206a977b97ce0b500d02 100644
--- a/zh-cn/application-dev/application-models/module-switch.md
+++ b/zh-cn/application-dev/application-models/module-switch.md
@@ -3,7 +3,7 @@
 
 从FA模型切换到Stage模型时，开发者需要将config.json文件module标签下的配置迁移到module.json5配置文件module标签下，具体差异见下列表格。
 
-###   **表1** FA模型module标签与Stage模型module标签差异对比
+**表1** FA模型module标签与Stage模型module标签差异对比
 
 | FA标签 | 标签说明 | 对应的Stage标签 | 差异说明 |
 | -------- | -------- | -------- | -------- |
@@ -15,8 +15,8 @@
 | distro对象中的moduleType | 标识当前HAP的类型，包括两种类型：entry和feature。另外，如果表示HAR包类型，请设置为har | type | 标签变更。 |
 | distro对象中的installationFree | 标识当前HAP是否支持免安装特性 | installationFree | 标签变更。 |
 | distro对象中的deliveryWithInstall | 标识当前HAP是否支持随应用安装 | deliveryWithInstall | 标签变更。 |
-| metaData | 标识HAP的元信息 | metadata | 具体差异如[表2](#表2-fa模型metadata和stage中metadata对比)。 |
-| abilities | 标识当前模块内的所有Ability | abilities | 具体差异如[表5](#表5-fa模型和stage中abilities差异对比)。 |
+| metaData | 标识HAP的元信息 | metadata | 具体差异见表2。 |
+| abilities | 标识当前模块内的所有Ability | abilities | 具体差异见表5。 |
 | js | 标识基于ArkUI框架开发的JS模块集合，其中的每个元素代表一个JS模块的信息 | pages | Stage模型在module标签下保留该对象中的pages，window配置与pages的下一级。 |
 | shortcuts | 标识应用的快捷方式信息 | shortcut_config.json文件 | 在开发视图的resources/base/profile下面定义配置文件shortcut_config.json。 |
 | reqPermissions | 标识应用运行时向系统申请的权限 | requestPermissions | 标签名称变更。 |
@@ -27,38 +27,38 @@
 | entryTheme | 此标签标识OpenHarmony内部主题的关键字 | / | Stage模型不支持。 |
 
 
-### 表2 FA模型metaData和Stage中metadata对比
+**表2** FA模型metaData和Stage中metadata对比
 
 | FA标签 | 标签说明 | 对应的Stage模型标签 | 差异对比 |
 | -------- | -------- | -------- | -------- |
 | parameters | 标识调用Ability时所有调用参数的元信息 | / | Stage模型不支持。 |
 | results | 标识Ability返回值的元信息 | / | Stage模型不支持。 |
-| customizeData | 该标签标识父级组件的自定义元信息，Parameters和results在application不可配 | metadata | 具体差异见[表3](#表3-fa模型metadata的customizedata和stage中metadata对比)。 |
+| customizeData | 该标签标识父级组件的自定义元信息，Parameters和results在application不可配 | metadata | 具体差异见表3。 |
 
-### 表3 FA模型metaData的customizeData和Stage中metadata对比
+**表3** FA模型metaData的customizeData和Stage中metadata对比
 
 | FA标签 | 标签说明 | 对应的Stage模型标签 | 差异对比 |
 | -------- | -------- | -------- | -------- |
 | name | 标识数据项的键名称。字符串最大长度为255字节 | name | 无。 |
 | value | 标识数据项的值。字符串最大长度为255字节。 | value | 无。 |
-| extra | 标识当前custom数据的格式，取值为表示extra的资源值。 | resource | 标签变更。具体实例见[表4](#表4-fa模型metadata和stage中metadata示例)。 |
+| extra | 标识当前custom数据的格式，取值为表示extra的资源值。 | resource | 标签变更。具体实例见表4。 |
 
 
-### 表4 FA模型metaData和Stage中metadata示例
+**表4** FA模型metaData和Stage中metadata示例
 
 | FA模型示例 | Stage模型示例 |
 | -------- | -------- |
 | “meteData”: {<br/>    "customizeDate": [{<br/>        "name": "label",<br/>        "value": "string",<br/>        "extra": "$string:label",<br/>    }]<br/>} | “meteData”: [{<br/>    "name": "label",<br/>    "value": "string",<br/>    "resource": "$string:label",<br/>}] |
 
 
-### 表5 FA模型和Stage中abilities差异对比
+**表5** FA模型和Stage中abilities差异对比
 
 | FA模型的abilities对象标签 | 描述 | Stage模型中abilities对象标签 | 差异对比 |
 | -------- | -------- | -------- | -------- |
 | process | 运行应用程序或Ability的进程名称 | / | Stage模型不支持abilities中配置，在module标签下配置process |
 | uri | 标识Ability的统一资源标识符 | / | Stage模型不支持 |
 | deviceCapability | 标识Ability运行时要求设备具有的能力，采用字符串数组的格式表示 | / | Stage模型不支持 |
-| metaData | 该标签标识ability的元信息。 | metadata | 具体差异如[表2](#表2-fa模型metadata和stage中metadata对比) |
+| metaData | 该标签标识ability的元信息。 | metadata | 具体差异见表2 |
 | type | 标识Ability的类型 | / | Stage模型不支持 |
 | grantPermission | 指定是否可以向Ability内任何数据授予权限 | / | abilities内不支持； |
 | readPermission | 标识读取Ability的数据所需的权限。该标签仅适用于data类型的Ability | / | abilities内不支持；在extensionAbilities标签中支持 |
diff --git a/zh-cn/application-dev/application-models/process-model-fa.md b/zh-cn/application-dev/application-models/process-model-fa.md
index 1e5a9c3dfded6361f27c0f68a0f332dfa38c5aba..f7a10c5094e844ad7fb14078d440da43934f2da5 100644
--- a/zh-cn/application-dev/application-models/process-model-fa.md
+++ b/zh-cn/application-dev/application-models/process-model-fa.md
@@ -1,4 +1,4 @@
-# 进程模型
+# 进程模型概述
 
 
 OpenHarmony的进程模型如下图所示：
diff --git a/zh-cn/application-dev/application-models/process-model-stage.md b/zh-cn/application-dev/application-models/process-model-stage.md
index eeb6c13e05a83c80a0c249ac71f247894a8a87eb..cf030e0ba0931f75a7ebd64757d8a355b8df36a1 100644
--- a/zh-cn/application-dev/application-models/process-model-stage.md
+++ b/zh-cn/application-dev/application-models/process-model-stage.md
@@ -1,16 +1,17 @@
-# 进程模型
+# 进程模型概述
 
 
-OpenHarmony的进程模型如下图所示：
+OpenHarmony的进程模型如下图所示。
 
 
-- 应用中（同一Bundle名称）的所有UIAbility、ServiceExtensionAbility、DataShareExtensionAbility运行在同一个独立进程中，即图中绿色部分的“Main Process”。
+- 应用中（同一Bundle名称）的所有UIAbility、ServiceExtensionAbility、DataShareExtensionAbility运行在同一个独立进程中，如下图中绿色部分的“Main Process”。
 
-- 应用中（同一Bundle名称）的同一类型ExtensionAbility（除ServiceExtensionAbility和DataShareExtensionAbility外）运行在一个独立进程中，即图中蓝色部分的“FormExtensionAbility Process”、“InputMethodExtensionAbility Process”、其他ExtensionAbility Process。
+- 应用中（同一Bundle名称）的同一类型ExtensionAbility（除ServiceExtensionAbility和DataShareExtensionAbility外）运行在一个独立进程中，如下图中蓝色部分的“FormExtensionAbility Process”、“InputMethodExtensionAbility Process”、其他ExtensionAbility Process。
 
-- WebView拥有独立的渲染进程，即图中黄色部分的“Render Process”。
+- WebView拥有独立的渲染进程，如下图中黄色部分的“Render Process”。
 
-  **图1** 进程模型示意图  
+
+**图1** 进程模型示意图  
 ![process-model](figures/process-model.png)
 
 > 说明：
@@ -20,7 +21,7 @@ OpenHarmony的进程模型如下图所示：
 
 在上述模型基础上，对于系统应用可以通过申请多进程权限（如下图所示），为指定HAP配置一个自定义进程名，该HAP中的UIAbility、DataShareExtensionAbility、ServiceExtensionAbility就会运行在自定义进程中。不同的HAP可以通过配置不同的进程名运行在不同进程中。
 
-  **图2** 多进程示意图  
+**图2** 多进程示意图  
 ![multi-process](figures/multi-process.png)
 
 
@@ -29,4 +30,4 @@ OpenHarmony的进程模型如下图所示：
 
 - [公共事件机制](common-event-overview.md)：多用于一对多的通信场景，公共事件发布者可能存在多个订阅者同时接收事件。
 
-- [后台服务机制](background-services.md)：当前主要通过[ServiceExtensionAbility](serviceextensionability.md)的能力实现。
+- [后台服务机制](background-services.md)：通过[ServiceExtensionAbility](serviceextensionability.md)的能力实现。
diff --git a/zh-cn/application-dev/application-models/stage-model-development-overview.md b/zh-cn/application-dev/application-models/stage-model-development-overview.md
index 31bc96127c72a3ec9561fc22cd92bd464bbf83db..7854471b8c8884033b7905b862fe36861e4fc643 100644
--- a/zh-cn/application-dev/application-models/stage-model-development-overview.md
+++ b/zh-cn/application-dev/application-models/stage-model-development-overview.md
@@ -17,7 +17,7 @@
   - ExtensionAbility组件是一种面向特定场景的应用组件。开发者并不直接从ExtensionAbility派生，而是需要使用ExtensionAbility的派生类。目前ExtensionAbility有用于卡片场景的FormExtensionAbility，用于输入法场景的InputMethodExtensionAbility，用于闲时任务场景的WorkSchedulerExtensionAbility等多种派生类，这些派生类都是基于特定场景提供的。例如，用户在桌面创建应用的卡片，需要应用开发者从FormExtensionAbility派生，实现其中的回调函数，并在配置文件中配置该能力。ExtensionAbility派生类实例由用户触发创建，并由系统管理生命周期。在Stage模型上，普通应用开发者不能开发自定义服务，而需要根据自身的业务场景通过ExtensionAbility的派生类来实现。
 - [WindowStage](../windowmanager/application-window-stage.md)
 
-  每个UIAbility类实例都会与一个WindowStage类实例绑定，该类提供了应用进程内窗口管理器的作用。它包含一个主窗口（Window）。也就是说UIAbility通过WindowStage持有了一个主窗口，该主窗口为ArkUI提供了绘制区域。
+  每个UIAbility类实例都会与一个WindowStage类实例绑定，该类提供了应用进程内窗口管理器的作用。它包含一个主窗口。也就是说UIAbility通过WindowStage持有了一个主窗口，该主窗口为ArkUI提供了绘制区域。
 
 - [Context](application-context-stage.md)
 
@@ -37,7 +37,7 @@
 | 任务 | 简介 | 相关指导 |
 | -------- | -------- | -------- |
 | 应用组件开发 | 本章节介绍了如何使用Stage模型的UIAbility组件和ExtensionAbility组件开发应用。 | -&nbsp;[应用/组件级配置](application-component-configuration-stage.md)<br/>-&nbsp;[UIAbility组件](uiability-overview.md)<br/>-&nbsp;[ExtensionAbility组件](extensionability-overview.md)<br/>-&nbsp;[AbilityStage组件容器](abilitystage.md)<br/>-&nbsp;[应用上下文Context](application-context-stage.md)<br/>-&nbsp;[组件启动规则](component-startup-rules.md) |
-| 进程间通信 | 本章节介绍了Stage模型的进程模型以及几种常用的进程间通信方式。 | -&nbsp;[公共事件](common-event-overview.md)<br/>-&nbsp;[后台服务](background-services.md) |
-| 线程间通信 | 本章节介绍了Stage模型的线程模型以及几种常用的线程间通信方式。 | -&nbsp;[Emitter](itc-with-emitter.md)<br/>-&nbsp;[Worker](itc-with-worker.md) |
+| 了解进程模型 | 本章节介绍了Stage模型的进程模型以及几种常用的进程间通信方式。 | -&nbsp;[公共事件](common-event-overview.md)<br/>-&nbsp;[后台服务](background-services.md) |
+| 了解线程模型 | 本章节介绍了Stage模型的线程模型以及几种常用的线程间通信方式。 | -&nbsp;[Emitter](itc-with-emitter.md)<br/>-&nbsp;[Worker](itc-with-worker.md) |
 | 任务管理 | 本章节介绍了Stage模型中任务管理的基本概念和典型场景。 | -&nbsp;[任务管理场景介绍](mission-management-overview.md)<br/>-&nbsp;[任务管理与启动模式](mission-management-launch-type.md)<br/>-&nbsp;[页面栈和任务链](page-mission-stack.md) |
 | 应用配置文件 | 本章节介绍Stage模型中应用配置文件的开发要求。 | [Stage模型应用配置文件](config-file-stage.md) |
diff --git a/zh-cn/application-dev/application-models/thread-model-stage.md b/zh-cn/application-dev/application-models/thread-model-stage.md
index 778298a3419efdbd83172af5260776a4ebfa5937..57ac44d934cee35e9b57e1a67bd8dd8047fa239a 100644
--- a/zh-cn/application-dev/application-models/thread-model-stage.md
+++ b/zh-cn/application-dev/application-models/thread-model-stage.md
@@ -1,20 +1,21 @@
-# 线程模型
+# 线程模型概述
 
 在OpenHarmony应用中，每个进程都会有一个主线程，主线程具有以下职责：
 
-1. 执行UI绘制；
-2. 管理主线程的ArkTS引擎实例，使多个UIAbility组件能够运行在其之上；
-3. 管理其他线程（例如Worker线程）的ArkTS引擎实例，例如启动和终止其他线程；
-4. 分发交互事件；
-5. 处理应用代码的回调，包括事件处理和生命周期管理；
-6. 接收Worker线程发送的消息；
+1. 执行UI绘制。
+2. 管理主线程的ArkTS引擎实例，使多个UIAbility组件能够运行在其之上。
+3. 管理其他线程（例如Worker线程）的ArkTS引擎实例，例如启动和终止其他线程。
+4. 分发交互事件。
+5. 处理应用代码的回调，包括事件处理和生命周期管理。
+6. 接收Worker线程发送的消息。
 
 除了主线程外，还有一类独立的Worker线程，用于执行耗时操作。Worker线程在主线程中创建，与主线程相互独立，但不能直接操作UI。最多可以创建7个Worker线程。  
 ![thread-model-stage](figures/thread-model-stage.png)
 
-基于OpenHarmony的线程模型，不同的业务功能运行在不同的线程上，业务功能的交互就需要线程间通信。同一个进程内，线程间通信目前主要有Emitter和Worker两种方式，其中Emitter主要适用于线程间的事件同步， Worker主要用于新开一个线程执行耗时任务。
+基于OpenHarmony的线程模型，不同的业务功能运行在不同的线程上，业务功能的交互就需要线程间通信。同一个进程内，线程间通信目前主要有Emitter和Worker两种方式，其中Emitter主要适用于线程间的事件同步，Worker主要用于新开一个线程执行耗时任务。
 
 > **说明：**
 >
-> - Stage模型只提供了主线程和Worker线程，Emitter主要用于主线程内或者主线程和Worker线程的事件同步。
-> - 执行`hdc shell`命令，进入设备的shell命令行。在shell命令行中，执行`ps -p <pid> -T`命令，可以查看指定应用进程的线程信息。其中，`<pid>`为需要指定的应用进程的进程ID。
+> - Stage模型只提供了主线程和Worker线程，Emitter主要用于主线程和Worker线程、Worker线程和Worker线程之间的事件同步。
+> - UIAbility组件与UI均在主线程中，他们之间的数据同步请参见[UIAbility组件与UI的数据同步](uiability-data-sync-with-ui.md)。
+> - 执行`hdc shell`命令，进入设备的shell命令行。在shell命令行中，执行`ps -p <pid> -T`命令，可以查看指定应用进程的线程信息。其中，`<pid>`为需要指定的应用进程的[进程ID](process-model-stage.md)。
diff --git a/zh-cn/application-dev/application-test/arkxtest-guidelines.md b/zh-cn/application-dev/application-test/arkxtest-guidelines.md
index 917bac92840f07b390dbc4eb5e59428d3d980e1d..6e2857a50c4f360d7fe2daca8980656051f959eb 100644
--- a/zh-cn/application-dev/application-test/arkxtest-guidelines.md
+++ b/zh-cn/application-dev/application-test/arkxtest-guidelines.md
@@ -58,7 +58,7 @@ DevEco Studio可参考其官网介绍进行[下载](https://developer.harmonyos.
 ## 新建测试脚本
 
 1. 在DevEco Studio中新建应用开发工程，其中ohos目录即为测试脚本所在的目录。
-2. 在工程目录下打开待测试模块下的ets文件，将光标置于代码中任意位置，单击**右键 > Show Context Actions** **> Create Ohos Test**或快捷键**Alt+enter** **> Create Ohos Test**创建测试类，更多指导请参考DevEco Studio中[指导](https://developer.harmonyos.com/cn/docs/documentation/doc-guides/ohos-openharmony-test-framework-0000001267284568)。
+2. 在工程目录下打开待测试模块下的ets文件，将光标置于代码中任意位置，单击**右键 > Show Context Actions** **> Create Ohos Test**或快捷键**Alt+enter** **> Create Ohos Test**创建测试类，更多指导请参考DevEco Studio中[指导](https://developer.harmonyos.com/cn/docs/documentation/doc-guides-V3/harmonyos_jnit_jsunit-0000001092459608-V3?catalogVersion=V3#section13366184061415)。
 
 ## 编写单元测试脚本
 
@@ -256,7 +256,7 @@ UI测试用例执行失败，查看hilog日志发现日志中有“uitest-api do
 
 1.检查用例实现，异步接口增加await语法糖调用。
 
-2.避免多进程执行UI测试用例。
+2.避免多进程执行UI的测试用例。
 
 **3、失败日志有“dose not exist on current UI! Check if the UI has changed after you got the widget object”错误信息**
 
diff --git a/zh-cn/application-dev/connectivity/ipc-rpc-development-guideline.md b/zh-cn/application-dev/connectivity/ipc-rpc-development-guideline.md
index 47366f9ed55ec3798ea2b465a74ca3e4b18050f0..d82d03c298cae4709b440e7d7a40db53836ee535 100755
--- a/zh-cn/application-dev/connectivity/ipc-rpc-development-guideline.md
+++ b/zh-cn/application-dev/connectivity/ipc-rpc-development-guideline.md
@@ -29,7 +29,7 @@ IPC/RPC的主要工作是让运行在不同进程的Proxy和Stub互相通信，
    external_deps = [
      "ipc:ipc_single",
    ]
-   
+
    #rpc场景
    external_deps = [
      "ipc:ipc_core",
@@ -50,12 +50,12 @@ IPC/RPC的主要工作是让运行在不同进程的Proxy和Stub互相通信，
 
    ```c++
    #include "iremote_broker.h"
-   
+
    //定义消息码
-   const int TRANS_ID_PING_ABILITY = 5
-   
+   const int TRANS_ID_PING_ABILITY = 5;
+
    const std::string DESCRIPTOR = "test.ITestAbility";
-   
+
    class ITestAbility : public IRemoteBroker {
    public:
        // DECLARE_INTERFACE_DESCRIPTOR是必需的，入参需使用std::u16string；
@@ -71,13 +71,13 @@ IPC/RPC的主要工作是让运行在不同进程的Proxy和Stub互相通信，
    ```c++
    #include "iability_test.h"
    #include "iremote_stub.h"
-   
+
    class TestAbilityStub : public IRemoteStub<ITestAbility> {
    public:
        virtual int OnRemoteRequest(uint32_t code, MessageParcel &data, MessageParcel &reply, MessageOption &option) override;
        int TestPingAbility(const std::u16string &dummy) override;
     };
-   
+
    int TestAbilityStub::OnRemoteRequest(uint32_t code,
        MessageParcel &data, MessageParcel &reply, MessageOption &option)
    {
@@ -98,12 +98,12 @@ IPC/RPC的主要工作是让运行在不同进程的Proxy和Stub互相通信，
 
    ```c++
    #include "iability_server_test.h"
-   
+
    class TestAbility : public TestAbilityStub {
    public:
        int TestPingAbility(const std::u16string &dummy);
    }
-   
+
    int TestAbility::TestPingAbility(const std::u16string &dummy) {
        return 0;
    }
@@ -117,7 +117,7 @@ IPC/RPC的主要工作是让运行在不同进程的Proxy和Stub互相通信，
    #include "iability_test.h"
    #include "iremote_proxy.h"
    #include "iremote_object.h"
-   
+
    class TestAbilityProxy : public IRemoteProxy<ITestAbility> {
    public:
        explicit TestAbilityProxy(const sptr<IRemoteObject> &impl);
@@ -125,12 +125,12 @@ IPC/RPC的主要工作是让运行在不同进程的Proxy和Stub互相通信，
    private:
        static inline BrokerDelegator<TestAbilityProxy> delegator_; // 方便后续使用iface_cast宏
    }
-   
+
    TestAbilityProxy::TestAbilityProxy(const sptr<IRemoteObject> &impl)
        : IRemoteProxy<ITestAbility>(impl)
    {
    }
-   
+
    int TestAbilityProxy::TestPingAbility(const std::u16string &dummy){
        MessageOption option;
        MessageParcel dataParcel, replyParcel;
@@ -149,7 +149,7 @@ IPC/RPC的主要工作是让运行在不同进程的Proxy和Stub互相通信，
    // 注册到本设备内
    auto samgr = SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();
    samgr->AddSystemAbility(saId, new TestAbility());
-   
+
    // 在组网场景下，会被同步到其他设备上
    auto samgr = SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();
    ISystemAbilityManager::SAExtraProp saExtra;
@@ -166,10 +166,10 @@ IPC/RPC的主要工作是让运行在不同进程的Proxy和Stub互相通信，
    sptr<ISystemAbilityManager> samgr = SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();
    sptr<IRemoteObject> remoteObject = samgr->GetSystemAbility(saId);
    sptr<ITestAbility> testAbility = iface_cast<ITestAbility>(remoteObject); // 使用iface_cast宏转换成具体类型
-   
+
    // 获取其他设备注册的SA的proxy
    sptr<ISystemAbilityManager> samgr = SystemAbilityManagerClient::GetInstance().GetSystemAbilityManager();
-   
+
    // networkId是组网场景下对应设备的标识符，可以通过GetLocalNodeDeviceInfo获取
    sptr<IRemoteObject> remoteObject = samgr->GetSystemAbility(saId, networkId);
    sptr<TestAbilityProxy> proxy(new TestAbilityProxy(remoteObject)); // 直接构造具体Proxy
@@ -180,59 +180,97 @@ IPC/RPC的主要工作是让运行在不同进程的Proxy和Stub互相通信，
 1. 添加依赖
 
    ```ts
-   import rpc from "@ohos.rpc"
-   import featureAbility from "@ohos.ability.featureAbility"
+   import rpc from "@ohos.rpc";
+   // 仅FA模型需要导入@ohos.ability.featureAbility
+   // import featureAbility from "@ohos.ability.featureAbility";
    ```
 
-   
+   Stage模型需要获取context
+
+   ```ts
+   import Ability from "@ohos.app.ability.UIAbility";
+
+   export default class MainAbility extends Ability {
+       onCreate(want, launchParam) {
+           console.log("[Demo] MainAbility onCreate");
+           globalThis.context = this.context;
+       }
+       onDestroy() {
+           console.log("[Demo] MainAbility onDestroy");
+       }
+       onWindowStageCreate(windowStage) {
+           // Main window is created, set main page for this ability
+           console.log("[Demo] MainAbility onWindowStageCreate");
+       }
+       onWindowStageDestroy() {
+           // Main window is destroyed, release UI related resources
+           console.log("[Demo] MainAbility onWindowStageDestroy");
+       }
+       onForeground() {
+           // Ability has brought to foreground
+           console.log("[Demo] MainAbility onForeground");
+       }
+       onBackground() {
+           // Ability has back to background
+           console.log("[Demo] MainAbility onBackground");
+       }
+   }
+   ```
 
 2. 绑定Ability
 
-   首先，构造变量want，指定要绑定的Ability所在应用的包名、组件名，如果是跨设备的场景，还需要绑定目标设备NetworkId（组网场景下对应设备的标识符，可以使用deviceManager获取目标设备的NetworkId）；然后，构造变量connect，指定绑定成功、绑定失败、断开连接时的回调函数；最后，使用featureAbility提供的接口绑定Ability。
+   首先，构造变量want，指定要绑定的Ability所在应用的包名、组件名，如果是跨设备的场景，还需要绑定目标设备NetworkId（组网场景下对应设备的标识符，可以使用deviceManager获取目标设备的NetworkId）；然后，构造变量connect，指定绑定成功、绑定失败、断开连接时的回调函数；最后，FA模型使用featureAbility提供的接口绑定Ability，Stage模型通过context获取服务后用提供的接口绑定Ability。
 
    ```ts
-   import rpc from "@ohos.rpc"
-   import featureAbility from "@ohos.ability.featureAbility"
-   
-   let proxy = null
-   let connectId = null
-   
+   import rpc from "@ohos.rpc";
+   // 仅FA模型需要导入@ohos.ability.featureAbility
+   // import featureAbility from "@ohos.ability.featureAbility";
+
+   let proxy = null;
+   let connectId = null;
+
    // 单个设备绑定Ability
    let want = {
        // 包名和组件名写实际的值
        "bundleName": "ohos.rpc.test.server",
        "abilityName": "ohos.rpc.test.server.ServiceAbility",
-   }
+   };
    let connect = {
        onConnect:function(elementName, remote) {
-           proxy = remote
+           proxy = remote;
        },
        onDisconnect:function(elementName) {
        },
        onFailed:function() {
-           proxy = null
+           proxy = null;
        }
-   }
-   connectId = featureAbility.connectAbility(want, connect)
-   
+   };
+   // FA模型使用此方法连接服务
+   // connectId = featureAbility.connectAbility(want, connect);
+
+   connectId = globalThis.context.connectServiceExtensionAbility(want,connect);
+
    // 如果是跨设备绑定，可以使用deviceManager获取目标设备NetworkId
-   import deviceManager from '@ohos.distributedHardware.deviceManager'
+   import deviceManager from '@ohos.distributedHardware.deviceManager';
    function deviceManagerCallback(deviceManager) {
-       let deviceList = deviceManager.getTrustedDeviceListSync()
-       let networkId = deviceList[0].networkId
+       let deviceList = deviceManager.getTrustedDeviceListSync();
+       let networkId = deviceList[0].networkId;
        let want = {
            "bundleName": "ohos.rpc.test.server",
            "abilityName": "ohos.rpc.test.service.ServiceAbility",
            "networkId": networkId,
            "flags": 256
-       }
-       connectId = featureAbility.connectAbility(want, connect)
+       };
+       // 建立连接后返回的Id需要保存下来，在断开连接时需要作为参数传入
+       // FA模型使用此方法连接服务
+       // connectId = featureAbility.connectAbility(want, connect);
+
+       connectId = globalThis.context.connectServiceExtensionAbility(want,connect);
    }
    // 第一个参数是本应用的包名，第二个参数是接收deviceManager的回调函数
-   deviceManager.createDeviceManager("ohos.rpc.test", deviceManagerCallback)
+   deviceManager.createDeviceManager("ohos.rpc.test", deviceManagerCallback);
    ```
 
-   
 
 3. 服务端处理客户端请求
 
@@ -240,78 +278,80 @@ IPC/RPC的主要工作是让运行在不同进程的Proxy和Stub互相通信，
 
    ```ts
    onConnect(want: Want) {
-       var robj:rpc.RemoteObject = new Stub("rpcTestAbility")
-       return robj
+       var robj:rpc.RemoteObject = new Stub("rpcTestAbility");
+       return robj;
    }
    class Stub extends rpc.RemoteObject {
        constructor(descriptor) {
-           super(descriptor)
+           super(descriptor);
        }
        onRemoteMessageRequest(code, data, reply, option) {
            // 根据code处理客户端的请求
-           return true
+           return true;
        }
    }
    ```
 
-   
-
 4. 客户端处理服务端响应
 
-   客户端在onConnect回调里接收到代理对象，调用sendRequestAsync方法发起请求，在期约（JavaScript期约：用于表示一个异步操作的最终完成或失败及其结果值）或者回调函数里接收结果。
+   客户端在onConnect回调里接收到代理对象，调用sendRequest方法发起请求，在期约（JavaScript期约：用于表示一个异步操作的最终完成或失败及其结果值）或者回调函数里接收结果。
 
    ```ts
    // 使用期约
-   let option = new rpc.MessageOption()
-   let data = rpc.MessageParcel.create()
-   let reply = rpc.MessageParcel.create()
+   let option = new rpc.MessageOption();
+   let data = rpc.MessageParcel.create();
+   let reply = rpc.MessageParcel.create();
    // 往data里写入参数
-   proxy.sendRequestAsync(1, data, reply, option)
+   proxy.sendRequest(1, data, reply, option)
        .then(function(result) {
            if (result.errCode != 0) {
-               console.error("send request failed, errCode: " + result.errCode)
-               return
+               console.error("send request failed, errCode: " + result.errCode);
+               return;
            }
            // 从result.reply里读取结果
        })
        .catch(function(e) {
-           console.error("send request got exception: " + e)
-       }
+           console.error("send request got exception: " + e);
+       })
        .finally(() => {
-           data.reclaim()
-           reply.reclaim()
+           data.reclaim();
+           reply.reclaim();
        })
-   
+
    // 使用回调函数
    function sendRequestCallback(result) {
        try {
            if (result.errCode != 0) {
-               console.error("send request failed, errCode: " + result.errCode)
-               return
+               console.error("send request failed, errCode: " + result.errCode);
+               return;
            }
            // 从result.reply里读取结果
        } finally {
-           result.data.reclaim()
-           result.reply.reclaim()
+           result.data.reclaim();
+           result.reply.reclaim();
        }
    }
-   let option = new rpc.MessageOption()
-   let data = rpc.MessageParcel.create()
-   let reply = rpc.MessageParcel.create()
+   let option = new rpc.MessageOption();
+   let data = rpc.MessageParcel.create();
+   let reply = rpc.MessageParcel.create();
    // 往data里写入参数
-   proxy.sendRequest(1, data, reply, option, sendRequestCallback)
+   proxy.sendRequest(1, data, reply, option, sendRequestCallback);
    ```
 
 5. 断开连接
 
-   IPC通信结束后，使用featureAbility的接口断开连接。
+   IPC通信结束后，FA模型使用featureAbility的接口断开连接，Stage模型在获取context后用提供的接口断开连接。
 
    ```ts
-   import rpc from "@ohos.rpc"
-   import featureAbility from "@ohos.ability.featureAbility"
+   import rpc from "@ohos.rpc";
+   // 仅FA模型需要导入@ohos.ability.featureAbility
+   // import featureAbility from "@ohos.ability.featureAbility";
    function disconnectCallback() {
-       console.info("disconnect ability done")
+       console.info("disconnect ability done");
    }
-   featureAbility.disconnectAbility(connectId, disconnectCallback)
+   // FA模型使用此方法断开连接
+   // featureAbility.disconnectAbility(connectId, disconnectCallback);
+
+   globalThis.context.disconnectServiceExtensionAbility(connectId);
    ```
 
diff --git a/zh-cn/application-dev/connectivity/ipc-rpc-overview.md b/zh-cn/application-dev/connectivity/ipc-rpc-overview.md
index 5dbf04f2d32e2ee7bca088cbd8f0a434d0e277a3..9bae7408831c2dceffce76425c579d265fd39f2a 100755
--- a/zh-cn/application-dev/connectivity/ipc-rpc-overview.md
+++ b/zh-cn/application-dev/connectivity/ipc-rpc-overview.md
@@ -3,35 +3,25 @@
 
 ## 基本概念
 
-IPC（Inter-Process Communication）与RPC（Remote Procedure Call）用于实现跨进程通信，不同的是前者使用Binder驱动，用于设备内的跨进程通信，后者使用软总线驱动，用于跨设备跨进程通信。需要跨进程通信的原因是因为每个进程都有自己独立的资源和内存空间，其他进程不能随意访问不同进程的内存和资源，IPC/RPC便是为了突破这一点。IPC和RPC通常采用客户端-服务器（Client-Server）模型，在使用时，请求服务的（Client）一端进程可获取提供服务（Server）一端所在进程的代理（Proxy），并通过此代理读写数据来实现进程间的数据通信，更具体的讲，首先请求服务的（Client）一端会建立一个服务提供端（Server）的代理对象，这个代理对象具备和服务提供端（Server）一样的功能，若想访问服务提供端（Server）中的某一个方法，只需访问代理对象中对应的方法即可，代理对象会将请求发送给服务提供端（Server）；然后服务提供端（Server）处理接受到的请求，处理完之后通过驱动返回处理结果给代理对象；最后代理对象将请求结果进一步返回给请求服务端（Client）。通常，Server会先注册系统能力（System Ability）到系统能力管理者（System Ability Manager，缩写SAMgr）中，SAMgr负责管理这些SA并向Client提供相关的接口。Client要和某个具体的SA通信，必须先从SAMgr中获取该SA的代理，然后使用代理和SA通信。下文直接使用Proxy表示服务请求方，Stub表示服务提供方。
+IPC（Inter-Process Communication）与RPC（Remote Procedure Call）用于实现跨进程通信，不同的是前者使用Binder驱动，用于设备内的跨进程通信，后者使用软总线驱动，用于跨设备跨进程通信。需要跨进程通信的原因是因为每个进程都有自己独立的资源和内存空间，其他进程不能随意访问不同进程的内存和资源，IPC/RPC便是为了突破这一点。
 
-![IPC&RPC通信机制](figures/075sd302-aeb9-481a-bb8f-e552sdb61ead.PNG)
-
-
-## 约束与限制
-
-- 单个设备上跨进程通信时，传输的数据量最大约为1MB，过大的数据量请使用[匿名共享内存](https://gitee.com/openharmony/docs/blob/master/zh-cn/application-dev/reference/apis/js-apis-rpc.md#ashmem8)
-
-- 不支持在RPC中订阅匿名Stub对象（没有向SAMgr注册Stub对象）的死亡通知。
-- 不支持把跨设备的Proxy对象传递回该Proxy对象所指向的Stub对象所在的设备，即指向远端设备Stub的Proxy对象不能在本设备内进行二次跨进程传递。
-
-## 使用建议
-
-首先，需要编写接口类，接口类中必须定义消息码，供通信双方标识操作，可以有未实现的的方法，因为通信双方均需继承该接口类且双方不能是抽象类，所以此时定义的未实现的方法必须在双方继承时给出实现，这保证了继承双方不是抽象类。然后，需要编写Stub端相关类及其接口，并且实现AsObject方法及OnRemoteRequest方法。同时，也需要编写Proxy端，实现接口类中的方法和AsObject方法，也可以封装一些额外的方法用于调用SendRequest向对端发送数据。以上三者都具备后，便可以向SAMgr注册SA了，此时的注册应该在Stub所在进程完成。最后，在需要的地方从SAMgr中获取Proxy，便可通过Proxy实现与Stub的跨进程通信了。
+> **说明：**
+> Stage模型不能直接使用本文介绍的IPC和RPC，需要通过以下能力实现相关业务场景：
+>- IPC典型使用场景为[后台服务](https://gitee.com/openharmony/docs/blob/master/zh-cn/application-dev/application-models/background-services.md)，后台服务通过IPC机制提供跨进程的服务调用能力。
+>- RPC典型使用场景为[多端协同](https://gitee.com/openharmony/docs/blob/master/zh-cn/application-dev/application-models/hop-multi-device-collaboration.md)，多端协同通过RPC机制提供远端接口调用与数据传递。
 
-相关步骤：
 
-- 实现接口类：需继承IRemoteBroker，需定义消息码，可声明不在此类实现的方法。
+## 实现原理
 
-- 实现服务提供端（Stub）：需继承IRemoteStub或者RemoteObject，需重写AsObject方法及OnRemoteRequest方法。
+IPC和RPC通常采用客户端-服务器（Client-Server）模型，在使用时，请求服务的（Client）一端进程可获取提供服务（Server）一端所在进程的代理（Proxy），并通过此代理读写数据来实现进程间的数据通信，更具体的讲，首先请求服务的（Client）一端会建立一个服务提供端（Server）的代理对象，这个代理对象具备和服务提供端（Server）一样的功能，若想访问服务提供端（Server）中的某一个方法，只需访问代理对象中对应的方法即可，代理对象会将请求发送给服务提供端（Server）；然后服务提供端（Server）处理接受到的请求，处理完之后通过驱动返回处理结果给代理对象；最后代理对象将请求结果进一步返回给请求服务端（Client）。通常，Server会先注册系统能力（System Ability）到系统能力管理者（System Ability Manager，缩写SAMgr）中，SAMgr负责管理这些SA并向Client提供相关的接口。Client要和某个具体的SA通信，必须先从SAMgr中获取该SA的代理，然后使用代理和SA通信。下文直接使用Proxy表示服务请求方，Stub表示服务提供方。
 
-- 实现服务请求端（Proxy）：需继承IRemoteProxy或RemoteProxy，需重写AsObject方法，封装所需方法调用SendRequest。
+![IPC&RPC通信机制](figures/075sd302-aeb9-481a-bb8f-e552sdb61ead.PNG)
 
-- 注册SA：申请SA的唯一ID，向SAMgr注册SA。
 
-- 获取SA：通过SA的ID和设备ID获取Proxy，使用Proxy与远端通信
+## 约束与限制
 
+- 单个设备上跨进程通信时，传输的数据量最大约为1MB，过大的数据量请使用[匿名共享内存](https://gitee.com/openharmony/docs/blob/master/zh-cn/application-dev/reference/apis/js-apis-rpc.md#ashmem8)。
 
-## 相关模块
+- 不支持在RPC中订阅匿名Stub对象（没有向SAMgr注册Stub对象）的死亡通知。
 
-[分布式任务调度子系统](https://gitee.com/openharmony/ability_dmsfwk)
+- 不支持把跨设备的Proxy对象传递回该Proxy对象所指向的Stub对象所在的设备，即指向远端设备Stub的Proxy对象不能在本设备内进行二次跨进程传递。
\ No newline at end of file
diff --git a/zh-cn/application-dev/connectivity/socket-connection.md b/zh-cn/application-dev/connectivity/socket-connection.md
index 99958e526c7847ee719d43067a69ea90a92c6003..3dc97d1cdf07ad000c8bd541f8e48a8409a4e604 100644
--- a/zh-cn/application-dev/connectivity/socket-connection.md
+++ b/zh-cn/application-dev/connectivity/socket-connection.md
@@ -315,10 +315,3 @@ tlsTwoWay.close((err) => {
 });
 ```
 
-## 相关实例
-
-针对Socket连接开发，有以下相关实例可供参考：
-
-- [`Socket`：Socket 连接（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Network/Socket)
-- [使用UDP实现与服务端通信（ArkTS）（API9）](https://gitee.com/openharmony/codelabs/tree/master/NetworkManagement/UdpDemoOH)
-- [使用TCP实现与服务端通信（ArkTS）（API9）](https://gitee.com/openharmony/codelabs/tree/master/NetworkManagement/TcpSocketDemo)
diff --git a/zh-cn/application-dev/connectivity/subscribe-remote-state.md b/zh-cn/application-dev/connectivity/subscribe-remote-state.md
index 7ce385d8e16ec68f5eaaef0bad7ca81770f2595f..be564525869803c6b6c7437c8149badaabf9685f 100755
--- a/zh-cn/application-dev/connectivity/subscribe-remote-state.md
+++ b/zh-cn/application-dev/connectivity/subscribe-remote-state.md
@@ -1,6 +1,6 @@
 # 远端状态订阅开发实例
 
-IPC/RPC提供对远端Stub对象状态的订阅机制， 在远端Stub对象消亡时，可触发消亡通知告诉本地Proxy对象。这种状态通知订阅需要调用特定接口完成，当不再需要订阅时也需要调用特定接口取消。使用这种订阅机制的用户，需要实现消亡通知接口DeathRecipient并实现onRemoteDied方法清理资源。该方法会在远端Stub对象所在进程消亡或所在设备离开组网时被回调。值得注意的是，调用这些接口有一定的顺序。首先，需要Proxy订阅Stub消亡通知，若在订阅期间Stub状态正常，则在不再需要时取消订阅；若在订阅期间Stub所在进程退出或者所在设备退出组网，则会自动触发Proxy自定义的后续操作。
+IPC/RPC提供对远端Stub对象状态的订阅机制，在远端Stub对象消亡时，可触发消亡通知告诉本地Proxy对象。这种状态通知订阅需要调用特定接口完成，当不再需要订阅时也需要调用特定接口取消。使用这种订阅机制的用户，需要实现消亡通知接口DeathRecipient并实现onRemoteDied方法清理资源。该方法会在远端Stub对象所在进程消亡或所在设备离开组网时被回调。值得注意的是，调用这些接口有一定的顺序。首先，需要Proxy订阅Stub消亡通知，若在订阅期间Stub状态正常，则在不再需要时取消订阅；若在订阅期间Stub所在进程退出或者所在设备退出组网，则会自动触发Proxy自定义的后续操作。
 
 ## 使用场景
 
@@ -21,7 +21,6 @@ IPC/RPC提供对远端Stub对象状态的订阅机制， 在远端Stub对象消
 #include "iremote_broker.h"
 #include "iremote_stub.h"
 
-
 //定义消息码
 enum {
     TRANS_ID_PING_ABILITY = 5,
@@ -61,9 +60,6 @@ int TestServiceProxy::TestPingAbility(const std::u16string &dummy){
 }
 ```
 
-
-
-
 ```c++
 #include "iremote_object.h"
 
@@ -86,16 +82,52 @@ result = object->RemoveDeathRecipient(deathRecipient); // 移除消亡通知
 
 ## JS侧接口
 
-| 接口名               | 返回值类型 | 功能描述                                                     |
-| -------------------- | ---------- | ------------------------------------------------------------ |
-| addDeathRecippient   | boolean    | 注册用于接收远程对象消亡通知的回调，增加proxy对象上的消亡通知。 |
-| removeDeathRecipient | boolean    | 注销用于接收远程对象消亡通知的回调。                         |
-| onRemoteDied         | void       | 在成功添加死亡通知订阅后，当远端对象死亡时，将自动调用本方法。 |
+| 接口名                   | 返回值类型 | 功能描述                                                          |
+| ------------------------ | ---------- | ----------------------------------------------------------------- |
+| registerDeathRecipient   | void       | 注册用于接收远程对象消亡通知的回调，增加 proxy 对象上的消亡通知。 |
+| unregisterDeathRecipient | void       | 注销用于接收远程对象消亡通知的回调。                              |
+| onRemoteDied             | void       | 在成功添加死亡通知订阅后，当远端对象死亡时，将自动调用本方法。    |
+
+### 获取context
+
+Stage模型在连接服务前需要先获取context
+
+```ts
+import Ability from "@ohos.app.ability.UIAbility";
+
+export default class MainAbility extends Ability {
+    onCreate(want, launchParam) {
+        console.log("[Demo] MainAbility onCreate");
+        globalThis.context = this.context;
+    }
+    onDestroy() {
+        console.log("[Demo] MainAbility onDestroy");
+    }
+    onWindowStageCreate(windowStage) {
+        // Main window is created, set main page for this ability
+        console.log("[Demo] MainAbility onWindowStageCreate");
+    }
+    onWindowStageDestroy() {
+        // Main window is destroyed, release UI related resources
+        console.log("[Demo] MainAbility onWindowStageDestroy");
+    }
+    onForeground() {
+        // Ability has brought to foreground
+        console.log("[Demo] MainAbility onForeground");
+    }
+    onBackground() {
+        // Ability has back to background
+        console.log("[Demo] MainAbility onBackground");
+    }
+}
+```
 
 ### 参考代码
 
 ```ts
-import FA from "@ohos.ability.featureAbility";
+// 仅FA模型需要导入@ohos.ability.featureAbility
+// import FA from "@ohos.ability.featureAbility";
+
 let proxy;
 let connect = {
     onConnect: function(elementName, remoteProxy) {
@@ -113,15 +145,19 @@ let want = {
     "bundleName": "com.ohos.server",
     "abilityName": "com.ohos.server.MainAbility",
 };
-FA.connectAbility(want, connect);
+// FA模型通过此方法连接服务
+// FA.connectAbility(want, connect);
+
+globalThis.context.connectServiceExtensionAbility(want, connect);
+
 class MyDeathRecipient {
     onRemoteDied() {
         console.log("server died");
     }
 }
 let deathRecipient = new MyDeathRecipient();
-proxy.addDeathRecippient(deathRecipient, 0);
-proxy.removeDeathRecipient(deathRecipient, 0);
+proxy.registerDeathRecippient(deathRecipient, 0);
+proxy.unregisterDeathRecipient(deathRecipient, 0);
 ```
 
 ## Stub感知Proxy消亡（匿名Stub的使用）
diff --git a/zh-cn/application-dev/connectivity/websocket-connection.md b/zh-cn/application-dev/connectivity/websocket-connection.md
index 52a0b517318cbf994002ffda3d35635bdc67b1eb..934af905e3c70b390f65877ad8a1455a69645992 100644
--- a/zh-cn/application-dev/connectivity/websocket-connection.md
+++ b/zh-cn/application-dev/connectivity/websocket-connection.md
@@ -82,9 +82,3 @@ ws.connect(defaultIpAddress, (err, value) => {
   }
 });
 ```
-
-## 相关实例
-
-针对WebSocket连接的开发，有以下相关实例可供参考：
-
-- [`WebSocket`：WebSocket（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Network/WebSocket)
\ No newline at end of file
diff --git a/zh-cn/application-dev/database/data-persistence-by-preferences.md b/zh-cn/application-dev/database/data-persistence-by-preferences.md
index 9448796f5574edd1b9537df7ecc85ed39d42a30e..ba0d562bfa4c4cf27ebfc85a1bddb610af2a438a 100644
--- a/zh-cn/application-dev/database/data-persistence-by-preferences.md
+++ b/zh-cn/application-dev/database/data-persistence-by-preferences.md
@@ -255,4 +255,4 @@
 
 - [`Preferences`：首选项（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DataManagement/Preferences)
 
-- [首选项（ArkTS）（API9）](https://gitee.com/openharmony/codelabs/tree/master/Data/Preferences)
\ No newline at end of file
+- [首选项（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DataManagement/Preferences)
\ No newline at end of file
diff --git a/zh-cn/application-dev/device-usage-statistics/device-usage-statistics-use-guide.md b/zh-cn/application-dev/device-usage-statistics/device-usage-statistics-use-guide.md
index c434acea443253d5795acea1a6110f56717402a9..779a7440c48ca614a89a0f2bafda7437058ee3ba 100644
--- a/zh-cn/application-dev/device-usage-statistics/device-usage-statistics-use-guide.md
+++ b/zh-cn/application-dev/device-usage-statistics/device-usage-statistics-use-guide.md
@@ -538,5 +538,5 @@ import usageStatistics from '@ohos.resourceschedule.usageStatistics';
 
 针对设备使用信息统计，有以下相关实例可供参考：
 
-- [`DeviceUsageStatistics`：设备使用信息统计（ArkTS）（API8）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/device/DeviceUsageStatistics)
+- [`DeviceUsageStatistics`：设备使用信息统计（ArkTS）（API8）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DeviceUsageStatistics/DeviceUsageStatistics)
 
diff --git a/zh-cn/application-dev/device/location-guidelines.md b/zh-cn/application-dev/device/location-guidelines.md
index ad146bb2c93e5f84f26d2a90fac7d74ac0cefb26..245814f72ba66d95998bea6b63de2592148f47c9 100644
--- a/zh-cn/application-dev/device/location-guidelines.md
+++ b/zh-cn/application-dev/device/location-guidelines.md
@@ -40,7 +40,7 @@
 
 针对位置服务，有以下相关实例可供参考：
 
-- [`Location`：位置服务（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/device/Location)
+- [`Location`：位置服务（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DeviceManagement/Location)
 
 
 ## 申请位置权限开发指导
diff --git a/zh-cn/application-dev/device/sensor-guidelines.md b/zh-cn/application-dev/device/sensor-guidelines.md
index 280f25668f8bdc37c44dd85b8d810f0bcf020b85..d0e94c8cca396b992045bd44200c13324d5233da 100644
--- a/zh-cn/application-dev/device/sensor-guidelines.md
+++ b/zh-cn/application-dev/device/sensor-guidelines.md
@@ -81,4 +81,4 @@
 
 针对传感器开发，有以下相关实例可供参考：
 
-- [`Sensor`：传感器（ArkTS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/device/Sensor)
\ No newline at end of file
+- [`Sensor`：传感器（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DeviceManagement/Sensor)
\ No newline at end of file
diff --git a/zh-cn/application-dev/device/usb-guidelines.md b/zh-cn/application-dev/device/usb-guidelines.md
index 8703f7a7a23ac003e97fbf671dbd3fca9b89e6e8..13773c784f3964041a3fdad220e27d9598f4dd22 100644
--- a/zh-cn/application-dev/device/usb-guidelines.md
+++ b/zh-cn/application-dev/device/usb-guidelines.md
@@ -165,4 +165,4 @@ USB设备可作为Host设备连接Device设备进行数据传输。开发示例
 
 针对USB管理开发，有以下相关实例可供参考：
 
-- [`USBManager`：USB管理（ArkTS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/device/USBManager)
\ No newline at end of file
+- [`USBManager`：USB管理（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DeviceManagement/USBManager)
\ No newline at end of file
diff --git a/zh-cn/application-dev/device/vibrator-guidelines.md b/zh-cn/application-dev/device/vibrator-guidelines.md
index 93b9c5ccd0b7cde599e995c17f9fc3baf1656256..8add16f232c284652d03ddb5dda1b5e18bd326c7 100644
--- a/zh-cn/application-dev/device/vibrator-guidelines.md
+++ b/zh-cn/application-dev/device/vibrator-guidelines.md
@@ -69,4 +69,4 @@
 
 针对振动开发，有以下相关实例可供参考：
 
-- [`Vibrator`：振动（ArkTS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/device/Vibrator)
\ No newline at end of file
+- [`Vibrator`：振动（ArkTS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DeviceManagement/Vibrator)
\ No newline at end of file
diff --git a/zh-cn/application-dev/dfx/hiappevent-guidelines.md b/zh-cn/application-dev/dfx/hiappevent-guidelines.md
index 079f72b7492731f9906bcd6cbb603f95afc07df7..8daafa41d36d3333ad3c8dc0d2090c306d0c374a 100644
--- a/zh-cn/application-dev/dfx/hiappevent-guidelines.md
+++ b/zh-cn/application-dev/dfx/hiappevent-guidelines.md
@@ -144,4 +144,4 @@ HiAppEvent是在系统层面为应用开发者提供的一种事件打点机制
 
 针对应用事件开发，有以下相关实例可供参考：
 
-- [`JsDotTest`：测试打点（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/DFX/JsDotTest)
\ No newline at end of file
+- [`DotTest`：测试打点（JS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DFX/DotTest)
\ No newline at end of file
diff --git a/zh-cn/application-dev/internationalization/intl-guidelines.md b/zh-cn/application-dev/internationalization/intl-guidelines.md
index f5382731b7bd43ad677482b555e7624444dbe26f..3094e12bcb4a73cd474b914a7b709d5badca0bae 100644
--- a/zh-cn/application-dev/internationalization/intl-guidelines.md
+++ b/zh-cn/application-dev/internationalization/intl-guidelines.md
@@ -390,6 +390,4 @@
 
 针对Intl开发，有以下相关实例可供参考：
 
--[`International`：国际化（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/International)
-
--[`International`：国际化（ArkTS）（API8）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/common/International)
+-[`International`：国际化（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SystemFeature/Internationalnation/International)
diff --git a/zh-cn/application-dev/key-features/multi-device-app-dev/adaptive-layout.md b/zh-cn/application-dev/key-features/multi-device-app-dev/adaptive-layout.md
index a2469187c0cdab7b5640c9c67e3858f6cf59c797..29b7027125fbcfa7bb930a7190c5a7b15b179a4c 100644
--- a/zh-cn/application-dev/key-features/multi-device-app-dev/adaptive-layout.md
+++ b/zh-cn/application-dev/key-features/multi-device-app-dev/adaptive-layout.md
@@ -479,7 +479,7 @@ struct ScaleCapabilitySample {
 @Component
 struct ExtensionCapabilitySample1 {
   @State rate: number = 0.60
-  const appList: number [] = [0, 1, 2, 3, 4, 5, 6, 7]
+  readonly appList: number [] = [0, 1, 2, 3, 4, 5, 6, 7]
 
   // 底部滑块，可以通过拖拽滑块改变容器尺寸
   @Builder slider() {
diff --git a/zh-cn/application-dev/key-features/multi-device-app-dev/appgallery-home-page.md b/zh-cn/application-dev/key-features/multi-device-app-dev/appgallery-home-page.md
index 9f682eab76db6d6d4e643df49ddb0835dd8aae54..deea2be861c6d0c067e5fc29f0c8631550d65d81 100644
--- a/zh-cn/application-dev/key-features/multi-device-app-dev/appgallery-home-page.md
+++ b/zh-cn/application-dev/key-features/multi-device-app-dev/appgallery-home-page.md
@@ -1,7 +1,7 @@
 # 应用市场首页
 
 
-本小节将以应用市场首页为例，介绍如何使用自适应布局能力和响应式布局能力适配不同尺寸窗口。本示例已经在[OpenHarmony应用示例](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/AppMarket)中开源，读者可以根据需要自行下载源码并运行及查看效果。
+本小节将以应用市场首页为例，介绍如何使用自适应布局能力和响应式布局能力适配不同尺寸窗口。本示例已经在[OpenHarmony应用示例](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/AppMarket)中开源，读者可以根据需要自行下载源码并运行及查看效果。
 
 
 ## 页面设计
diff --git a/zh-cn/application-dev/key-features/multi-device-app-dev/ide-using.md b/zh-cn/application-dev/key-features/multi-device-app-dev/ide-using.md
index d433f8398b05754a555b61fd92c351f875299bda..27f79ce4808d2ec1fa1ac320670b3ef8310bab38 100644
--- a/zh-cn/application-dev/key-features/multi-device-app-dev/ide-using.md
+++ b/zh-cn/application-dev/key-features/multi-device-app-dev/ide-using.md
@@ -58,7 +58,7 @@ DevEco Studio的基本使用，请参考[DevEco Studio使用指南](../../quick-
 > ![icon-note.gif](public_sys-resources/icon-note.gif) **说明：**
 > - 在一个工程中同一个设备类型只支持一个Entry类型的模块。
 > 
-> - 当前的DevEco Studio（3.0 Beta3版本）在创建工程时，设备类型仅能选择dafault和tablet，默认该模块已经选择了entry类型，那么在创建wearable这个模块，只能选择feature类型。
+> - 当前的DevEco Studio（3.0 Beta3版本）在创建工程时，设备类型仅能选择default和tablet，默认该模块已经选择了entry类型，那么在创建wearable这个模块，只能选择feature类型。
 > 
 > - 在下一个小节，我们将介绍如何修改Module的配置，包括Module的类型以及其支持的设备类型等。
 
diff --git a/zh-cn/application-dev/key-features/multi-device-app-dev/music-album-page.md b/zh-cn/application-dev/key-features/multi-device-app-dev/music-album-page.md
index a486732981a3bf5d770dc21b039494937870b6d9..b6d0f6c7ff943203b7aac1bdc8a5c1b1385adb72 100644
--- a/zh-cn/application-dev/key-features/multi-device-app-dev/music-album-page.md
+++ b/zh-cn/application-dev/key-features/multi-device-app-dev/music-album-page.md
@@ -1,7 +1,7 @@
 # 音乐专辑页
 
 
-本小节将以音乐专辑页为例，介绍如何使用自适应布局能力和响应式布局能力适配不同尺寸窗口。本示例已经在[OpenHarmony应用示例](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/MusicAlbum)中开源，读者可以根据需要自行下载源码并运行及查看效果。
+本小节将以音乐专辑页为例，介绍如何使用自适应布局能力和响应式布局能力适配不同尺寸窗口。本示例已经在[OpenHarmony应用示例](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/MusicAlbum)中开源，读者可以根据需要自行下载源码并运行及查看效果。
 
 
 ## 页面设计
diff --git a/zh-cn/application-dev/key-features/multi-device-app-dev/page-development-intro.md b/zh-cn/application-dev/key-features/multi-device-app-dev/page-development-intro.md
index eb8e73ad8ffd29ce619e29f7ea36e24e6845a8ee..85f695195c1cb3a57e11d1fb4293dc8d3f57e157 100644
--- a/zh-cn/application-dev/key-features/multi-device-app-dev/page-development-intro.md
+++ b/zh-cn/application-dev/key-features/multi-device-app-dev/page-development-intro.md
@@ -25,14 +25,14 @@
 
 ## 相关实例
 
-[OpenHarmony应用示例](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev)中提供了如下一多示例，感兴趣的开发者可以自行下载、运行及查看效果。
+[OpenHarmony应用示例](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev)中提供了如下一多示例，感兴趣的开发者可以自行下载、运行及查看效果。
 
 | 示例名称                                                     | 开发范式       | 简介                                                         |
 | ------------------------------------------------------------ | -------------- | ------------------------------------------------------------ |
-| [页面开发一多能力](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/AdaptiveCapabilities) | 声明式开发范式 | 本章配套的示例代码，包括自适应布局、响应式布局、典型布局场景以及资源文件使用等。 |
-| [页面开发一多能力](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/JsAdaptiveCapabilities) | 类Web开发范式  | 本章配套的示例代码，包括自适应布局、响应式布局及资源文件使用等。 |
-| [天气](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/Weather) | 声明式开发范式 | 一多示例应用，以天气应用为例，演示如何使用一多能力实现包含多个页面的应用。 |
-| [应用市场首页](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/AppMarket) | 声明式开发范式 | 本章配套的示例代码，以应用市场首页为例，演示如何使用一多能力适配多设备（或多窗口尺寸）。 |
-| [音乐专辑页](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/MusicAlbum) | 声明式开发范式 | 本章配套的示例代码，以音乐专辑页为例，演示如何使用一多能力适配多设备（或多窗口尺寸）。 |
+| [页面开发一多能力](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/AdaptiveCapabilities) | 声明式开发范式 | 本章配套的示例代码，包括自适应布局、响应式布局、典型布局场景以及资源文件使用等。 |
+| [页面开发一多能力](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/JsAdaptiveCapabilities) | 类Web开发范式  | 本章配套的示例代码，包括自适应布局、响应式布局及资源文件使用等。 |
+| [天气](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/Weather) | 声明式开发范式 | 一多示例应用，以天气应用为例，演示如何使用一多能力实现包含多个页面的应用。 |
+| [应用市场首页](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/AppMarket) | 声明式开发范式 | 本章配套的示例代码，以应用市场首页为例，演示如何使用一多能力适配多设备（或多窗口尺寸）。 |
+| [音乐专辑页](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/MusicAlbum) | 声明式开发范式 | 本章配套的示例代码，以音乐专辑页为例，演示如何使用一多能力适配多设备（或多窗口尺寸）。 |
 
 
diff --git a/zh-cn/application-dev/key-features/multi-device-app-dev/start-with-a-example.md b/zh-cn/application-dev/key-features/multi-device-app-dev/start-with-a-example.md
index 32eb3829070fa4509b70c17103b9930267b95ddf..88b857ab4cb7778a444a547bc5dc5a8265cd5ac6 100644
--- a/zh-cn/application-dev/key-features/multi-device-app-dev/start-with-a-example.md
+++ b/zh-cn/application-dev/key-features/multi-device-app-dev/start-with-a-example.md
@@ -78,7 +78,7 @@
 
 ## 页面开发
 
-天气应用中涉及较多的页面和弹窗，本小节以天气主页为例，简单介绍不同设备下的页面实现思路。天气应用已经在[OpenHarmony应用示例](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/Weather)中开源，感兴趣的读者可以自行下载及了解详细代码实现。
+天气应用中涉及较多的页面和弹窗，本小节以天气主页为例，简单介绍不同设备下的页面实现思路。天气应用已经在[OpenHarmony应用示例](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/Weather)中开源，感兴趣的读者可以自行下载及了解详细代码实现。
 
   观察天气主页在不同设备上的UX设计图，可以进行如下设计：
 - 将天气主页划分为9个基础区域，如：
diff --git a/zh-cn/application-dev/media/using-avsession-developer.md b/zh-cn/application-dev/media/using-avsession-developer.md
index 40643ac3e089c5cf6cbd0e980cbab7b3b744d2fd..0d7f6413c45ca32a51a4589f88dfb3dacec11231 100644
--- a/zh-cn/application-dev/media/using-avsession-developer.md
+++ b/zh-cn/application-dev/media/using-avsession-developer.md
@@ -88,7 +88,7 @@
    ```ts
    // 假设已经创建了一个session，如何创建session可以参考之前的案例
    let session: AVSessionManager.AVSession = ALLREADY_CREATE_A_SESSION;
-   let wantAgentInfo: {
+   let wantAgentInfo = {
        wants: [
            {
                bundleName: "com.example.musicdemo",
diff --git a/zh-cn/application-dev/notification/figures/zh-cn_image_0000001466462305.png b/zh-cn/application-dev/notification/figures/zh-cn_image_0000001466462305.png
index 2c580f75dc86159b4088e54d3f83e163fd352f6d..f879ad7ef01a39b5f18af8abea3f7f1842b2b446 100644
Binary files a/zh-cn/application-dev/notification/figures/zh-cn_image_0000001466462305.png and b/zh-cn/application-dev/notification/figures/zh-cn_image_0000001466462305.png differ
diff --git a/zh-cn/application-dev/notification/notification-enable.md b/zh-cn/application-dev/notification/notification-enable.md
index 84680e0a4f18b02b7ec7da8714918dcb6a840d9c..45d3345c19810f5e0c2dfce772cf1e9a378d8339 100644
--- a/zh-cn/application-dev/notification/notification-enable.md
+++ b/zh-cn/application-dev/notification/notification-enable.md
@@ -1,15 +1,15 @@
 # 使能通知开关
 
 
-应用需要开启通知开关才能发送通知。开发者可以在通知发布前调用[requestEnableNotification()](../reference/apis/js-apis-notificationManager.md#notificationrequestenablenotification)方法，弹窗让用户选择是否开启使能开关，仅弹窗一次，后续调用该接口不再弹窗。
+应用需要开启通知开关才能发送通知。开发者可以在通知发布前调用[requestEnableNotification()](../reference/apis/js-apis-notificationManager.md#notificationmanagerrequestenablenotification)方法，弹窗让用户选择是否开启使能开关，仅弹窗一次，后续调用该接口不再弹窗。
 
-  **图1** 使能通知开关示意图
+  **图1** 使能通知开关示意图  
 ![zh-cn_image_0000001416585590](figures/zh-cn_image_0000001416585590.png)
 
 
 - 点击“允许”后，则表示允许应用发送通知。
 
-- 点击“取消”后，再次调用[requestEnableNotification()](../reference/apis/js-apis-notificationManager.md#notificationrequestenablenotification)方法，则不再弹窗。此时如需要手动使能通知开关，操作步骤如下所示。
+- 点击“取消”后，再次调用[requestEnableNotification()](../reference/apis/js-apis-notificationManager.md#notificationmanagerrequestenablenotification)方法，则不再弹窗。此时如需要手动使能通知开关，操作步骤如下所示。
   
   | ①从设备左上方下拉，进入通知界面                              | ②点击右上角“设置”图标，进入通知界面，找到需要打开通知开关的应用 | ③打开“允许通知”开关                                          |
   | ------------------------------------------------------------ | ------------------------------------------------------------ | ------------------------------------------------------------ |
@@ -34,16 +34,16 @@
 1. 导入NotificationManager模块。
 
    ```ts
-   import NotificationManager from '@ohos.notificationManager';
+   import notificationManager from '@ohos.notificationManager';
    ```
 
 2. 请求发送通知的许可。
 
    ```ts
-   NotificationManager.requestEnableNotification().then(() => {
+   notificationManager.requestEnableNotification().then(() => {
        console.info(`[ANS] requestEnableNotification success`);
    }).catch((err) => {
-       console.error(`[ANS] requestEnableNotification failed, errCode[${err}]`);
+       console.error(`[ANS] requestEnableNotification failed, code is ${err.code}, message is ${err.message}`);
    });
    ```
 
diff --git a/zh-cn/application-dev/notification/notification-overview.md b/zh-cn/application-dev/notification/notification-overview.md
index dd951c314626f8ca5ff6a88e95af9ee16382c1dd..ec0a9eef7f707fd70fcf3b391203271b77e4f1f6 100644
--- a/zh-cn/application-dev/notification/notification-overview.md
+++ b/zh-cn/application-dev/notification/notification-overview.md
@@ -13,7 +13,7 @@
 
 - 显示当前正在进行的事件，如下载等。
 
-OpenHarmony通过ANS（Advanced Notification Service，通知系统服务）对通知类型的消息进行管理，支持多种通知类型，如基础类型通知、进度条类型通知、后台代理提醒。
+OpenHarmony通过ANS（Advanced Notification Service，通知系统服务）对通知类型的消息进行管理，支持多种通知类型，例如基础类型通知、进度条类型通知、后台代理提醒。
 
 
 ## 通知业务流程
@@ -24,10 +24,11 @@ OpenHarmony通过ANS（Advanced Notification Service，通知系统服务）对
 
 系统应用还支持通知相关配置，如使能开关、配置参数由系统配置发起请求，发送到通知子系统存储到内存和数据库。
 
+**图1** 通知业务流程  
 ![zh-cn_image_0000001466582017](figures/zh-cn_image_0000001466582017.png)
 
 ## 相关实例
 
 基于通知的开发，有以下相关实例可供参考：
 
-- [`Notification`：订阅、发送通知（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Notification/Notification)
\ No newline at end of file
+- [`CustomNotification`：订阅、发送通知（ArkTS）（API9）（Full SDK）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/Notification/CustomNotification)
\ No newline at end of file
diff --git a/zh-cn/application-dev/notification/notification-subscription.md b/zh-cn/application-dev/notification/notification-subscription.md
index 739ae33ed6461c3cf9a26696d6592aea81f3b95c..33db2db09dc8ca0489f79ce12d6c2fff14789138 100644
--- a/zh-cn/application-dev/notification/notification-subscription.md
+++ b/zh-cn/application-dev/notification/notification-subscription.md
@@ -20,64 +20,64 @@
 
 **表2** 通知订阅回调接口介绍
 
-| | |
-| -------- | -------- |
 | **接口名** | **描述** |
-| onConsume?:(data:&nbsp;SubscribeCallbackData)&nbsp;=&gt;&nbsp;void | 通知回调。 |
-| onCancel?:(data:&nbsp;SubscribeCallbackData)&nbsp;=&gt;&nbsp;void | 通知取消回调。 |
-| onUpdate?:(data:&nbsp;NotificationSortingMap)&nbsp;=&gt;&nbsp;void | 通知排序更新回调。 |
-| onConnect?:()&nbsp;=&gt;&nbsp;void; | 订阅成功回调。 |
-| onDisconnect?:()&nbsp;=&gt;&nbsp;void; | 取消订阅回调。 |
-| onDestroy?:()&nbsp;=&gt;&nbsp;void | 与通知子系统断开回调。 |
+| -------- | -------- |
+| onConsume?:(data:&nbsp;SubscribeCallbackData)&nbsp;=&gt;&nbsp;void | 通知回调。               |
+| onCancel?:(data:&nbsp;SubscribeCallbackData)&nbsp;=&gt;&nbsp;void | 通知取消回调。           |
+| onUpdate?:(data:&nbsp;NotificationSortingMap)&nbsp;=&gt;&nbsp;void | 通知排序更新回调。       |
+| onConnect?:()&nbsp;=&gt;&nbsp;void;                          | 订阅成功回调。           |
+| onDisconnect?:()&nbsp;=&gt;&nbsp;void;                       | 取消订阅回调。           |
+| onDestroy?:()&nbsp;=&gt;&nbsp;void                           | 与通知子系统断开回调。   |
 | onDoNotDisturbDateChange?:(mode:&nbsp;notification.DoNotDisturbDate)&nbsp;=&gt;&nbsp;void | 免打扰时间选项变更回调。 |
-| onEnabledNotificationChanged?:(callbackData:&nbsp;EnabledNotificationCallbackData)&nbsp;=&gt;&nbsp;void | 通知开关变更回调。 |
+| onEnabledNotificationChanged?:(callbackData:&nbsp;EnabledNotificationCallbackData)&nbsp;=&gt;&nbsp;void | 通知开关变更回调。       |
 
 
 ## 开发步骤
 
-1. 申请`ohos.permission.NOTIFICATION_CONTROLLER`权限，配置方式请参阅[访问控制授权申请指导](../security/accesstoken-guidelines.md)。
+1. 申请`ohos.permission.NOTIFICATION_CONTROLLER`权限，配置方式请参见[访问控制授权申请](../security/accesstoken-guidelines.md#配置文件权限声明)。
 
 2. 导入通知订阅模块。
    
    ```ts
-   import NotificationSubscribe from '@ohos.notificationSubscribe';
+   import notificationSubscribe from '@ohos.notificationSubscribe';
    ```
 
 3. 创建订阅者对象。
    
    ```ts
    let subscriber = {
-       onConsume: function (data) {
-           let req = data.request;
-           console.info('[ANS] onConsume callback req.id: ' + req.id);
-       },
-       onCancel: function (data) {
-           let req = data.request;
-           console.info('[ANS] onCancel callback req.id: : ' + req.id);
-       },
-       onUpdate: function (data) {
-           console.info('[ANS] onUpdate in test');
-       },
-       onConnect: function () {
-           console.info('[ANS] onConnect in test');
-       },
-       onDisconnect: function () {
-           console.info('[ANS] onDisConnect in test');
-       },
-       onDestroy: function () {
-           console.info('[ANS] onDestroy in test');
-       },
+     onConsume: function (data) {
+       let req = data.request;
+       console.info(`onConsume callback. req.id: ${req.id}`);
+     },
+     onCancel: function (data) {
+       let req = data.request;
+       console.info(`onCancel callback. req.id: ${req.id}`);
+     },
+     onUpdate: function (data) {
+       let req = data.request;
+       console.info(`onUpdate callback. req.id: ${req.id}`);
+     },
+     onConnect: function () {
+       console.info(`onConnect callback.}`);
+     },
+     onDisconnect: function () {
+       console.info(`onDisconnect callback.}`);
+     },
+     onDestroy: function () {
+       console.info(`onDestroy callback.}`);
+     },
    };
    ```
-
+   
 4. 发起通知订阅。
    
    ```ts
-   NotificationSubscribe.subscribe(subscriber, (err, data) => { // callback形式调用异步接口
+   notificationSubscribe.subscribe(subscriber, (err, data) => { // callback形式调用异步接口
      if (err) {
-       console.error(`[ANS] failed to subscribe, error[${err}]`);
+       console.error(`Failed to subscribe notification. Code is ${err.code}, message is ${err.message}`);
        return;
      }
-     console.info(`[ANS] subscribeTest success : + ${data}`);
+     console.info(`Succeeded in subscribing to notification. Data: ${data}`);
    });
    ```
diff --git a/zh-cn/application-dev/notification/notification-with-wantagent.md b/zh-cn/application-dev/notification/notification-with-wantagent.md
index 737e7fd14460c004501ec23bd8f080be5e1b8a0f..4b3a00ff7ceefb580ba2b6e1aff051ea95f45c93 100644
--- a/zh-cn/application-dev/notification/notification-with-wantagent.md
+++ b/zh-cn/application-dev/notification/notification-with-wantagent.md
@@ -1,18 +1,16 @@
 # 为通知添加行为意图
 
+[WantAgent](../reference/apis/js-apis-app-ability-wantAgent.md)提供了封装行为意图的能力，该行为意图是指拉起指定的应用组件及发布公共事件等能力。OpenHarmony支持以通知的形式，将[WantAgent](../reference/apis/js-apis-app-ability-wantAgent.md)从发布方传递至接收方，从而在接收方触发[WantAgent](../reference/apis/js-apis-app-ability-wantAgent.md)中指定的意图。例如在通知消息的发布者发布通知时，通常期望用户可以通过通知栏点击拉起目标应用组件。为了达成这一目标，开发者可以将[WantAgent](../reference/apis/js-apis-app-ability-wantAgent.md)封装至通知消息中，当系统接收到[WantAgent](../reference/apis/js-apis-app-ability-wantAgent.md)后，在用户点击通知栏时触发[WantAgent](../reference/apis/js-apis-app-ability-wantAgent.md)的意图，从而拉起目标应用组件。
 
-WantAgent提供了封装行为意图的能力，这里所说的行为意图主要是指拉起指定的应用组件及发布公共事件等能力。OpenHarmony支持以通知的形式，将WantAgent从发布方传递至接收方，从而在接收方触发WantAgent中指定的意图。例如，在通知消息的发布者发布通知时，通常期望用户可以通过通知栏点击拉起目标应用组件。为了达成这一目标，开发者可以将WantAgent封装至通知消息中，当系统接收到WantAgent后，在用户点击通知栏时触发WantAgent的意图，从而拉起目标应用组件。
+为通知添加行为意图的实现方式如下图所示：发布通知的应用向应用组件管理服务AMS（Ability Manager Service）申请[WantAgent](../reference/apis/js-apis-app-ability-wantAgent.md)，然后随其他通知信息一起发送给桌面，当用户在桌面通知栏上点击通知时，触发[WantAgent](../reference/apis/js-apis-app-ability-wantAgent.md)动作。
 
-
-为通知添加行为意图的实现方式如下图所示：发布通知的应用向应用组件管理服务AMS（Ability Manager Service）申请WantAgent，然后随其他通知信息一起发送给桌面，当用户在桌面通知栏上点击通知时，触发WantAgent动作。
-
-  **图1** 携带行为意图的通知运行机制  
+**图1** 携带行为意图的通知运行机制  
 ![notification-with-wantagent](figures/notification-with-wantagent.png)
 
 
 ## 接口说明
 
-具体接口描述，详见[WantAgent接口文档](../reference/apis/js-apis-wantAgent.md)。
+具体接口描述，详见[WantAgent接口文档](../reference/apis/js-apis-app-ability-wantAgent.md)。
 
 | **接口名** | **描述** |
 | -------- | -------- |
@@ -25,111 +23,99 @@ WantAgent提供了封装行为意图的能力，这里所说的行为意图主
 
 ## 开发步骤
 
-1. 导入模块。
-   
-   ```ts
-   import NotificationManager from '@ohos.notificationManager';
+1. [使能通知开关](notification-enable.md)，获得用户授权后，才能使用通知功能。
+
+2. 导入模块。
+
+   ```typescript
+   import notificationManager from '@ohos.notificationManager';
    import wantAgent from '@ohos.app.ability.wantAgent';
    ```
 
-2. 创建WantAgentInfo信息。
-     场景一：创建拉起Ability的WantAgent的[WantAgentInfo](../reference/apis/js-apis-inner-wantAgent-wantAgentInfo.md)信息。
-     
-   ```ts
+3. 创建WantAgentInfo信息。
+
+   场景一：创建拉起UIAbility的WantAgent的[WantAgentInfo](../reference/apis/js-apis-inner-wantAgent-wantAgentInfo.md)信息。
+
+   ```typescript
    let wantAgentObj = null; // 用于保存创建成功的wantAgent对象，后续使用其完成触发的动作。
    
-   // 通过WantAgentInfo的operationType设置动作类型。
+   // 通过WantAgentInfo的operationType设置动作类型
    let wantAgentInfo = {
-       wants: [
-           {
-               deviceId: '',
-               bundleName: 'com.example.test',
-               abilityName: 'com.example.test.MainAbility',
-               action: '',
-               entities: [],
-               uri: '',
-               parameters: {}
-           }
-       ],
-       operationType: wantAgent.OperationType.START_ABILITY,
-       requestCode: 0,
-       wantAgentFlags:[wantAgent.WantAgentFlags.CONSTANT_FLAG]
-   }
+     wants: [
+       {
+         deviceId: '',
+         bundleName: 'com.example.myapplication',
+         abilityName: 'EntryAbility',
+         action: '',
+         entities: [],
+         uri: '',
+         parameters: {}
+       }
+     ],
+     operationType: wantAgent.OperationType.START_ABILITY,
+     requestCode: 0,
+     wantAgentFlags:[wantAgent.WantAgentFlags.CONSTANT_FLAG]
+   };
    ```
 
-     场景二：创建发布公共事件的WantAgent的[WantAgentInfo](../reference/apis/js-apis-inner-wantAgent-wantAgentInfo.md)信息。
-   
-   ```ts
+   场景二：创建发布[公共事件](../application-models/common-event-overview.md)的WantAgent的[WantAgentInfo](../reference/apis/js-apis-inner-wantAgent-wantAgentInfo.md)信息。
+
+   ```typescript
    let wantAgentObj = null; // 用于保存创建成功的WantAgent对象，后续使用其完成触发的动作。
    
-   // wantAgentInfo
+   // 通过WantAgentInfo的operationType设置动作类型
    let wantAgentInfo = {
-       wants: [
-           {
-               action: 'event_name', // 设置事件名。
-               parameters: {},
-           }
-       ],
-       operationType: wantAgent.OperationType.SEND_COMMON_EVENT,
-       requestCode: 0,
-       wantAgentFlags: [wantAgent.WantAgentFlags.CONSTANT_FLAG],
-   }
+     wants: [
+       {
+         action: 'event_name', // 设置事件名
+         parameters: {},
+       }
+     ],
+     operationType: wantAgent.OperationType.SEND_COMMON_EVENT,
+     requestCode: 0,
+     wantAgentFlags: [wantAgent.WantAgentFlags.CONSTANT_FLAG],
+   };
    ```
 
-3. 创建WantAgent。
-   
-   ```ts
+4. 调用[getWantAgent()](../reference/apis/js-apis-app-ability-wantAgent.md#wantagentgetwantagent)方法进行创建WantAgent。
+
+   ```typescript
    // 创建WantAgent
    wantAgent.getWantAgent(wantAgentInfo, (err, data) => {
-       if (err) {
-           console.error('[WantAgent]getWantAgent err=' + JSON.stringify(err));
-       } else {
-           console.info('[WantAgent]getWantAgent success');
-           wantAgentObj = data;
-       }
+     if (err) {
+       console.error(`Failed to get want agent. Code is ${err.code}, message is ${err.message}`);
+       return;
+     }
+     console.info('Succeeded in geting want agent.');
+     wantAgentObj = data;
    });
    ```
 
-4. 构造NotificationRequest对象。
-   
-   ```ts
+5. 构造NotificationRequest对象，并发布WantAgent通知。
+
+   ```typescript
    // 构造NotificationRequest对象
-   let notificationRequest = {
-       content: {
-           contentType: NotificationManager.ContentType.NOTIFICATION_CONTENT_BASIC_TEXT,
-           normal: {
-               title: 'Test_Title',
-               text: 'Test_Text',
-               additionalText: 'Test_AdditionalText',
-           },
+   let notificationRequest: notificationManager.NotificationRequest = {
+     content: {
+       contentType: notificationManager.ContentType.NOTIFICATION_CONTENT_BASIC_TEXT,
+       normal: {
+         title: 'Test_Title',
+         text: 'Test_Text',
+         additionalText: 'Test_AdditionalText',
        },
-       id: 1,
-       label: 'TEST',
-       wantAgent: wantAgentObj,
+     },
+     id: 1,
+     label: 'TEST',
+     wantAgent: wantAgentObj,
    }
-   ```
-
-5. 发布WantAgent通知。
    
-   ```ts
-   // 通知发送
-   NotificationManager.publish(notificationRequest, (err) => {
-       if (err) {
-           console.error(`[ANS] failed to publish, error[${err}]`);
-           return;
-       }
-       console.info(`[ANS] publish success `);
+   notificationManager.publish(notificationRequest, (err) => {
+     if (err) {
+       console.error(`Failed to publish notification. Code is ${err.code}, message is ${err.message}`);
+       return;
+     }
+     console.info('Succeeded in publishing notification.');
    });
    ```
 
-6. 用户通过点击通知栏上的通知，触发WantAgent的动作。
-   
-   ```ts
-   // 触发WantAgent
-   let triggerInfo = {
-       code: 0
-   }
-   wantAgent.trigger(wantAgentObj, triggerInfo, (completeData) => {
-       console.info('[WantAgent]getWantAgent success, completeData: ',  + JSON.stringify(completeData));
-   });
-   ```
+6. 用户通过点击通知栏上的通知，系统会自动触发WantAgent的动作。
diff --git a/zh-cn/application-dev/notification/progress-bar-notification.md b/zh-cn/application-dev/notification/progress-bar-notification.md
index 6c09173b2b7a434e64146c85c87ff3728ce0df88..d5720422d429fea4edf5f0da01309ac4127ecdf2 100644
--- a/zh-cn/application-dev/notification/progress-bar-notification.md
+++ b/zh-cn/application-dev/notification/progress-bar-notification.md
@@ -5,16 +5,16 @@
 
 目前系统模板仅支持进度条模板，通知模板[NotificationTemplate](../reference/apis/js-apis-inner-notification-notificationTemplate.md)中的data参数为用户自定义数据，用于显示与模块相关的数据，效果示意如下图所示。
 
+**图1** 进度条通知效果示意图  
 ![zh-cn_image_0000001416903138](figures/zh-cn_image_0000001416903138.png)
 
 
 ## 接口说明
 
-[isSupportTemplate()](../reference/apis/js-apis-notificationManager.md#notificationissupporttemplate)是查询模板是否支持接口，目前仅支持进度条模板。
+[`isSupportTemplate()`](../reference/apis/js-apis-notificationManager.md#notificationmanagerissupporttemplate)是查询模板是否支持接口，目前仅支持进度条模板。
 
-| | |
-| -------- | -------- |
 | **接口名** | **描述** |
+| -------- | -------- |
 | isSupportTemplate(templateName:&nbsp;string,&nbsp;callback:&nbsp;AsyncCallback&lt;boolean&gt;):&nbsp;void | 查询模板是否存在。 |
 
 
@@ -25,31 +25,32 @@
 2. 导入模块。
    
    ```ts
-   import NotificationManager from '@ohos.notificationManager';
+   import notificationManager from '@ohos.notificationManager';
    ```
 
 3. 查询系统是否支持进度条模板，查询结果为支持downloadTemplate模板类通知。
    
    ```ts
-   NotificationManager.isSupportTemplate('downloadTemplate').then((data) => {
+   notificationManager.isSupportTemplate('downloadTemplate').then((data) => {
      console.info(`[ANS] isSupportTemplate success`);
+     console.info('Succeeded in supporting download template notification.');
      let isSupportTpl: boolean = data; // isSupportTpl的值为true表示支持支持downloadTemplate模板类通知，false表示不支持
      // ...
    }).catch((err) => {
-     console.error(`[ANS] isSupportTemplate failed, error[${err}]`);
+     console.error(`Failed to support download template notification. Code is ${err.code}, message is ${err.message}`);
    });
    ```
-
-   > ![icon-note.gif](public_sys-resources/icon-note.gif) **说明：**
+   
+   > **说明：**
    > 查询系统支持进度条模板后，再进行后续的步骤操作。
-
+   
 4. 构造进度条模板对象，并发布通知。
    
    ```ts
-   let notificationRequest = {
+   let notificationRequest: notificationManager.NotificationRequest = {
      id: 1,
      content: {
-       contentType: NotificationManager.ContentType.NOTIFICATION_CONTENT_BASIC_TEXT,
+       contentType: notificationManager.ContentType.NOTIFICATION_CONTENT_BASIC_TEXT,
        normal: {
          title: 'test_title',
          text: 'test_text',
@@ -64,11 +65,11 @@
    }
    
    // 发布通知
-   NotificationManager.publish(notificationRequest, (err) => {
+   notificationManager.publish(notificationRequest, (err) => {
      if (err) {
-       console.error(`[ANS] failed to publish, error[${err}]`);
+       console.error(`Failed to publish notification. Code is ${err.code}, message is ${err.message}`);
        return;
      }
-     console.info(`[ANS] publish success `);
+     console.info('Succeeded in publishing notification.');
    });
    ```
diff --git a/zh-cn/application-dev/notification/text-notification.md b/zh-cn/application-dev/notification/text-notification.md
index 3d5ab8e27f3a61eb57a4aa1e9cf3c0f670cc9a37..7685eecf65bb5030d7c2615d57f8c91e0d9713b2 100644
--- a/zh-cn/application-dev/notification/text-notification.md
+++ b/zh-cn/application-dev/notification/text-notification.md
@@ -3,8 +3,7 @@
 
 基础类型通知主要应用于发送短信息、提示信息、广告推送等，支持普通文本类型、长文本类型、多行文本类型和图片类型。
 
-
-  **表1** 基础类型通知中的内容分类
+**表1** 基础类型通知中的内容分类
 
 | 类型 | 描述 |
 | -------- | -------- |
@@ -13,16 +12,15 @@
 | NOTIFICATION_CONTENT_MULTILINE | 多行文本类型。 |
 | NOTIFICATION_CONTENT_PICTURE | 图片类型。 |
 
+目前，系统仅支持通知栏订阅通知，将通知显示在通知栏中。基本类型通知的效果示意如下图所示。
 
-目前系统仅通知栏订阅了通知，将通知显示在通知栏里。基础类型通知呈现效果示意图如下所示。
-
-
-  **图1** 基础类型通知呈现效果示意图  ![zh-cn_image_0000001466462305](figures/zh-cn_image_0000001466462305.png)
+**图1** 基础类型通知呈现效果示意图  
+![zh-cn_image_0000001466462305](figures/zh-cn_image_0000001466462305.png)
 
 
 ## 接口说明
 
-通知发布接口如下表所示，不同发布类型通知由[NotificationRequest](../reference/apis/js-apis-notification.md#notificationrequest)的字段携带不同的信息。
+通知发布接口如下表所示，不同发布类型通知由[NotificationRequest](../reference/apis/js-apis-inner-notification-notificationRequest.md#notificationrequest)的字段携带不同的信息。
 
 | **接口名** | **描述** |
 | -------- | -------- |
@@ -38,124 +36,123 @@
 2. 导入模块。
    
    ```ts
-   import NotificationManager from '@ohos.notificationManager';
+   import notificationManager from '@ohos.notificationManager';
    ```
 
 3. 构造NotificationRequest对象，并发布通知。
    - 普通文本类型通知由标题、文本内容和附加信息三个字段组成，其中标题和文本内容是必填字段，大小均需要小于200字节。
      
       ```ts
-      let notificationRequest = {
+      let notificationRequest: notificationManager.NotificationRequest = {
         id: 1,
         content: {
-      	contentType: NotificationManager.ContentType.NOTIFICATION_CONTENT_BASIC_TEXT, // 普通文本类型通知
-      	normal: {
-      	  title: 'test_title',
-      	  text: 'test_text',
-      	  additionalText: 'test_additionalText',
-      	}
+          contentType: notificationManager.ContentType.NOTIFICATION_CONTENT_BASIC_TEXT, // 普通文本类型通知
+          normal: {
+            title: 'test_title',
+            text: 'test_text',
+            additionalText: 'test_additionalText',
+          }
         }
-      }
+      };
       
-      NotificationManager.publish(notificationRequest, (err) => {
-          if (err) {
-              console.error(`[ANS] failed to publish, error[${err}]`);
-              return;
-          }
-          console.info(`[ANS] publish success`);
+      notificationManager.publish(notificationRequest, (err) => {
+        if (err) {
+          console.error(`Failed to publish notification. Code is ${err.code}, message is ${err.message}`);
+          return;
+        }
+        console.info('Succeeded in publishing notification.');
       });
       ```
 
-      运行效果如下图所示。
-     
+      运行效果如下图所示。  
      ![zh-cn_image_0000001466782033](figures/zh-cn_image_0000001466782033.png)
    - 长文本类型通知继承了普通文本类型的字段，同时新增了长文本内容、内容概要和通知展开时的标题，其中长文本内容不超过1024字节，其他字段小于200字节。通知默认显示与普通文本相同，展开后，标题显示为展开后标题内容，内容为长文本内容。
      
       ```ts
-      let notificationRequest = {
+      let notificationRequest: notificationManager.NotificationRequest = {
         id: 1,
         content: {
-      	contentType: NotificationManager.ContentType.NOTIFICATION_CONTENT_LONG_TEXT, // 长文本类型通知
-      	longText: {
-      	  title: 'test_title',
-      	  text: 'test_text',
-      	  additionalText: 'test_additionalText',
-      	  longText: 'test_longText',
-      	  briefText: 'test_briefText',
-      	  expandedTitle: 'test_expandedTitle',
-      	}
+          contentType: notificationManager.ContentType.NOTIFICATION_CONTENT_LONG_TEXT, // 长文本类型通知
+          longText: {
+            title: 'test_title',
+            text: 'test_text',
+            additionalText: 'test_additionalText',
+            longText: 'test_longText',
+            briefText: 'test_briefText',
+            expandedTitle: 'test_expandedTitle',
+          }
         }
-      }
+      };
       
       // 发布通知
-      NotificationManager.publish(notificationRequest, (err) => {
-          if (err) {
-              console.error(`[ANS] failed to publish, error[${err}]`);
-              return;
-          }
-          console.info(`[ANS] publish success`);
+      notificationManager.publish(notificationRequest, (err) => {
+        if (err) {
+          console.error(`Failed to publish notification. Code is ${err.code}, message is ${err.message}`);
+          return;
+        }
+        console.info('Succeeded in publishing notification.');
       });
       ```
    
-      运行效果如下图所示。
+      运行效果如下图所示。  
      ![zh-cn_image_0000001416745530](figures/zh-cn_image_0000001416745530.png)
    - 多行文本类型通知继承了普通文本类型的字段，同时新增了多行文本内容、内容概要和通知展开时的标题，其字段均小于200字节。通知默认显示与普通文本相同，展开后，标题显示为展开后标题内容，多行文本内容多行显示。
      
       ```ts
-      let notificationRequest = {
+      let notificationRequest: notificationManager.NotificationRequest = {
         id: 1,
         content: {
-      	contentType: NotificationManager.ContentType.NOTIFICATION_CONTENT_MULTILINE, // 多行文本类型通知
-      	multiLine: {
-      	  title: 'test_title',
-      	  text: 'test_text',
-      	  briefText: 'test_briefText',
-      	  longTitle: 'test_longTitle',
-      	  lines: ['line_01', 'line_02', 'line_03', 'line_04'],
-      	}
+          contentType: notificationManager.ContentType.NOTIFICATION_CONTENT_MULTILINE, // 多行文本类型通知
+          multiLine: {
+            title: 'test_title',
+            text: 'test_text',
+            briefText: 'test_briefText',
+            longTitle: 'test_longTitle',
+            lines: ['line_01', 'line_02', 'line_03', 'line_04'],
+          }
         }
-      }
+      };
       
       // 发布通知
-      NotificationManager.publish(notificationRequest, (err) => {
+      notificationManager.publish(notificationRequest, (err) => {
         if (err) {
-      	console.error(`[ANS] failed to publish, error[${err}]`);
-      	return;
+          console.error(`Failed to publish notification. Code is ${err.code}, message is ${err.message}`);
+          return;
         }
-        console.info(`[ANS] publish success`);
+        console.info('Succeeded in publishing notification.');
       });
       ```
    
-      运行效果如下图所示。
+      运行效果如下图所示。  
      ![zh-cn_image_0000001417062446](figures/zh-cn_image_0000001417062446.png)
-   - 图片类型通知继承了普通文本类型的字段，同时新增了图片内容、内容概要和通知展开时的标题，图片内容为PixelMap型对象，其大小不能超过2M。
+   - 图片类型通知继承了普通文本类型的字段，同时新增了图片内容、内容概要和通知展开时的标题，图片内容为[PixelMap](../reference/apis/js-apis-image.md#pixelmap7)类型对象，其大小不能超过2M。
      
       ```ts
-      let notificationPicture: PixelMap = undefined; // 需要获取图片PixelMap信息
-      let notificationRequest = {
-          id: 1,
-          content: {
-      	contentType: NotificationManager.ContentType.NOTIFICATION_CONTENT_PICTURE,
-      	picture: {
-      	  title: 'test_title',
-      	  text: 'test_text',
-      	  additionalText: 'test_additionalText',
-      	  briefText: 'test_briefText',
-      	  expandedTitle: 'test_expandedTitle',
-      	  picture: notificationPicture
-      	}
+      let imagePixelMap: PixelMap = undefined; // 需要获取图片PixelMap信息
+      let notificationRequest: notificationManager.NotificationRequest = {
+        id: 1,
+        content: {
+          contentType: notificationManager.ContentType.NOTIFICATION_CONTENT_PICTURE,
+          picture: {
+            title: 'test_title',
+            text: 'test_text',
+            additionalText: 'test_additionalText',
+            briefText: 'test_briefText',
+            expandedTitle: 'test_expandedTitle',
+            picture: imagePixelMap
           }
-      }
+        }
+      };
       
       // 发布通知
-      NotificationManager.publish(notificationRequest, (err) => {
-          if (err) {
-      	console.error(`[ANS] failed to publish, error[${err}]`);
-      	return;
-          }
-          console.info(`[ANS] publish success `);
+      notificationManager.publish(notificationRequest, (err) => {
+        if (err) {
+          console.error(`Failed to publish notification. Code is ${err.code}, message is ${err.message}`);
+          return;
+        }
+        console.info('Succeeded in publishing notification.');
       });
       ```
    
-      运行效果如下图所示。
+      运行效果如下图所示。  
      ![zh-cn_image_0000001466582045](figures/zh-cn_image_0000001466582045.png)
diff --git a/zh-cn/application-dev/quick-start/application-package-structure-stage.md b/zh-cn/application-dev/quick-start/application-package-structure-stage.md
index 9867e9c7f3b4f284f26a48e5f26c8da605c4d988..0c2344b7fd00561a2de0ede4b60cd7e65f716c24 100644
--- a/zh-cn/application-dev/quick-start/application-package-structure-stage.md
+++ b/zh-cn/application-dev/quick-start/application-package-structure-stage.md
@@ -1,10 +1,10 @@
 # Stage模型应用程序包结构
 
 
-基于[Stage模型](application-configuration-file-overview-stage.md)开发的应用，经编译打包后，其应用程序包结构如下图**应用程序包结构（Stage模型）**所示。开发者需要熟悉应用程序包结构相关的基本概念。
+基于[Stage模型](application-configuration-file-overview-stage.md)开发的应用，经编译打包后，其应用程序包结构如下图“应用程序包结构（Stage模型）”所示。开发者需要熟悉应用程序包结构相关的基本概念。
 
 
-- 在开发态，一个应用包含一个或者多个Module，可以在[DevEco Studio](https://developer.harmonyos.com/cn/develop/deveco-studio/)工程中[创建一个或者多个Module](https://developer.harmonyos.com/cn/docs/documentation/doc-guides-V3/ohos-adding-deleting-module-0000001218760594-V3)。Module是OpenHarmony应用/服务的基本功能单元，包含了源代码、资源文件、第三方库及应用/服务配置文件，每一个Module都可以独立进行编译和运行。Module分为“Ability”和“Library”两种类型，“Ability”类型的Module对应于编译后的HAP（Harmony Ability Package）；“Library”类型的Module对应于[HAR](har-package.md)（Harmony Archive），或者[HSP](shared-guide.md)（Harmony Shared Package）。
+- 在开发态，一个应用包含一个或者多个Module，可以在[DevEco Studio](https://developer.harmonyos.com/cn/develop/deveco-studio/)工程中[创建一个或者多个Module](https://developer.harmonyos.com/cn/docs/documentation/doc-guides-V3/add_new_module-0000001053223741-V3)。Module是OpenHarmony应用/服务的基本功能单元，包含了源代码、资源文件、第三方库及应用/服务配置文件，每一个Module都可以独立进行编译和运行。Module分为“Ability”和“Library”两种类型，“Ability”类型的Module对应于编译后的HAP（Harmony Ability Package）；“Library”类型的Module对应于[HAR](har-package.md)（Harmony Archive），或者[HSP](shared-guide.md)（Harmony Shared Package）。
   一个Module可以包含一个或多个[UIAbility](../application-models/uiability-overview.md)组件，如下图所示。
 
     **图1** Module与UIAbility组件关系示意图  
diff --git a/zh-cn/application-dev/quick-start/figures/application_details.jpg b/zh-cn/application-dev/quick-start/figures/application_details.jpg
index 17b7172bc5bea2f4e16af8d385834930ca4bf49f..6447a151123bcf4f1e45e72f0318430e4aac18cf 100644
Binary files a/zh-cn/application-dev/quick-start/figures/application_details.jpg and b/zh-cn/application-dev/quick-start/figures/application_details.jpg differ
diff --git a/zh-cn/application-dev/quick-start/har-package.md b/zh-cn/application-dev/quick-start/har-package.md
index 7d7512b15584c6b6996e0bfe9e32b777854c2c56..1df0179b41d18a5f68545b61f8b7f383dffc739c 100644
--- a/zh-cn/application-dev/quick-start/har-package.md
+++ b/zh-cn/application-dev/quick-start/har-package.md
@@ -2,7 +2,7 @@
 HAR（Harmony Archive）是静态共享包，可以包含代码、C++库、资源和配置文件。通过HAR可以实现多个模块或多个工程共享ArkUI组件、资源等相关代码。HAR不同于HAP，不能独立安装运行在设备上，只能作为应用模块的依赖项被引用。
 
 ## 创建HAR模块
-HAR对应DevEco Studio工程中的“Library”类型的[Module](https://developer.harmonyos.com/cn/docs/documentation/doc-guides-V3/add_new_module-0000001053223741-V3)，可以通过DevEco Studio创建一个HAR模块。HAR模块默认不开启混淆能力，开启混淆能力，需要把HAR模块的build-profile.json5文件中的artifactType字段设置为obfuscation，配置如下所示：
+通过DevEco Studio创建一个HAR模块，创建方式可[参考](https://developer.harmonyos.com/cn/docs/documentation/doc-guides-V3/creating_har_api9-0000001518082393-V3#section143510369612)。HAR模块默认不开启混淆能力，开启混淆能力，需要把HAR模块的build-profile.json5文件中的artifactType字段设置为obfuscation，配置如下所示：
 
 ```json
 {
@@ -90,7 +90,7 @@ HAR模块编译打包时会把资源打包到HAR中。在编译构建HAP时，De
 - 依赖的HAR模块，如果依赖的多个HAR之间有资源冲突，会按照依赖顺序进行覆盖（依赖顺序在前的优先级较高）。
 
 ## 引用HAR的ArkUI组件、接口、资源
-引用HAR前，需要先配置对HAR的依赖，配置方式可[参考](https://developer.harmonyos.com/cn/docs/documentation/doc-guides/ohos-development-npm-package-0000001222578434#section89674298391)。
+引用HAR前，需要先配置对HAR的依赖，配置方式可[参考](https://developer.harmonyos.com/cn/docs/documentation/doc-guides-V3/creating_har_api9-0000001518082393-V3#section611662614153)。
 
 ### 引用HAR的ArkUI组件
 
@@ -167,3 +167,7 @@ struct Index {
   }
 }
 ```
+
+## 发布HAR
+
+发布HAR可[参考](https://developer.harmonyos.com/cn/docs/documentation/doc-guides-V3/creating_har_api9-0000001518082393-V3#section1213451811512)。
diff --git a/zh-cn/application-dev/quick-start/in-app-hsp.md b/zh-cn/application-dev/quick-start/in-app-hsp.md
index 1ce3afa89b794291bf07ef70449a43f4df41645d..3a96b330ee09c972f651dbfa00686c5f076a7dad 100644
--- a/zh-cn/application-dev/quick-start/in-app-hsp.md
+++ b/zh-cn/application-dev/quick-start/in-app-hsp.md
@@ -5,7 +5,7 @@
 
 ## 开发应用内HSP
 
-`HSP`模块可以在`DevEco Studio`中由指定模板创建，我们以创建一个名为`library`的`HSP`模块为例。基本的工程目录结构大致如下：
+通过DevEco Studio创建一个HSP模块，创建方式可[参考](https://developer.harmonyos.com/cn/docs/documentation/doc-guides-V3/hsp-0000001521396322-V3#section7717162312546)，我们以创建一个名为`library`的`HSP`模块为例。基本的工程目录结构大致如下：
 ```
 library
 ├── src
@@ -88,7 +88,7 @@ export { MyTitleBar } from './components/MyTitleBar'
 ### 导出native方法
 在`HSP`中也可以包含`C++`编写的`so`。对于`so`中的`native`方法，`HSP`通过间接的方式导出，以导出`libnative.so`的乘法接口`multi`为例：
 ```ts
-// ibrary/src/main/ets/utils/nativeTest.ts
+// library/src/main/ets/utils/nativeTest.ts
 import native from "libnative.so"
 
 export function nativeMulti(a: number, b: number) {
@@ -103,15 +103,9 @@ export { nativeMulti } from './utils/nativeTest'
 ```
 
 ## 使用应用内HSP
-要使用`HSP`中的接口，首先需要在使用方的`oh-package.json5`中配置对它的依赖。如果应用内`HSP`和使用方在同一工程下，可以直接本地引用，例如：
-```json
-// entry/oh-package.json5
-"dependencies": {
-    "library": "file:../library"
-}
-```
-然后就可以像使用`HAR`一样调用`HSP`的对外接口了。
-例如，上面的`library`已经导出了下面这些接口：
+要使用HSP中的接口，首先需要在使用方的oh-package.json5中配置对它的依赖，配置方式可[参考](https://developer.harmonyos.com/cn/docs/documentation/doc-guides-V3/hsp-0000001521396322-V3#section6161154819195)。
+依赖配置成功后，就可以像使用HAR一样调用HSP的对外接口了。 例如，上面的library已经导出了下面这些接口：
+
 ```ts
 // library/src/main/ets/index.ets
 export { Log, add, minus } from './utils/test'
diff --git a/zh-cn/application-dev/quick-start/module-configuration-file.md b/zh-cn/application-dev/quick-start/module-configuration-file.md
index 627910eb37db56b73eac22436f2b918f0f62fe24..88dbf4009deca67351b9fd8f1961cb75918ef5a8 100644
--- a/zh-cn/application-dev/quick-start/module-configuration-file.md
+++ b/zh-cn/application-dev/quick-start/module-configuration-file.md
@@ -221,66 +221,6 @@ deviceTypes示例：
 
 abilities标签描述UIAbility组件的配置信息，标签值为数组类型，该标签下的配置只对当前UIAbility生效。
 
-**OpenHarmony中不允许应用隐藏入口图标**
-
-OpenHarmony系统对无图标应用严格管控。如果HAP中没有配置入口图标，那么系统将应用app.json中的icon作为入口图标，并显示在桌面上。<br>
-用户点击该图标，将跳转到设置应用管理中对应的应用详情页面（图1）中。<br>
-如果应用想要隐藏入口图标，需要配置AllowAppDesktopIconHide应用特权，具体配置方式参考[应用特权配置指南](../../device-dev/subsystems/subsys-app-privilege-config-guide.md)。
-
-**场景说明：** 该功能能防止一些恶意应用，故意配置无入口图标，导致用户找不到软件所在的位置，无法操作卸载应用，在一定程度上保证用户的手机安全
-
-**入口图标的设置:** 需要在配置文件（module.json5）中abilities配置下设置icon，label以及skills,而且skills的配置下的必须同时包含“ohos.want.action.home” 和 “entity.system.home”:
-```
-{
-  "module":{
-
-    ...
-
-    "abilities": [{
-      "icon": "$media:icon",
-      "label": "Login",
-      "skills": [{
-        "actions": ["ohos.want.action.home"],
-        "entities": ["entity.system.home"],
-        "uris": []
-      }]
-    }],
-    ...
-
-  }
-}
-```
-
-**入口图标及入口标签的显示规则**
-* HAP中包含UIAbility
-  * 配置文件（module.json5）中abilities配置中设置了入口图标
-    * 该应用没有隐藏图标的特权
-      * 显示桌面图标为该UIAbility配置的图标
-      * 显示桌面Label为该UIAbility配置的Label（如果没有配置Label，返回包名）
-      * 显示组件名为该UIAbility的组件名
-      * 用户点击该桌面图标，页面跳转到该UIAbility首页
-    * 该应用具有隐藏图标的特权
-      * 桌面查询时不返回应用信息，不会在桌面上显示对应的图标。
-  * 配置文件（module.json5）中abilities配置中未设置入口图标
-    * 该应用没有隐藏图标的特权
-      * 显示桌面图标为app配置下的图标（app.json中icon为必填项）
-      * 显示桌面Label为app配置下的label（app.json中label为必填项）
-      * 用户点击该桌面图标，页面跳转到该应用的详情页面（图1）
-    * 该应用具有隐藏图标的特权
-      * 桌面查询时不返回应用信息，不会在桌面上显示对应的图标。
-* HAP中不包含UIAbility
-  * 该应用没有隐藏图标的特权
-    * 显示桌面图标为app配置下的图标（app.json中icon为必填项）
-    * 显示桌面Label为app配置下的label（app.json中label为必填项）
-    * 用户点击该桌面图标，页面跳转到该应用的详情页面（图1）
-  * 该应用具有隐藏图标的特权
-    * 桌面查询时不返回应用信息，不会在桌面上显示对应的图标。<br><br>
-
-应用的详情页例图
-
-![应用的详情页例图](figures/application_details.jpg)
-
-
   **表6** **abilities标签说明**
 
 | 属性名称 | 含义 | 数据类型 | 是否可缺省 |
diff --git a/zh-cn/application-dev/quick-start/module-structure.md b/zh-cn/application-dev/quick-start/module-structure.md
index 0c331c169ac3b2f6d7dd784c6f931f290ebf30fd..299e07aec2ee3439b5994b34026f8c0d04756947 100644
--- a/zh-cn/application-dev/quick-start/module-structure.md
+++ b/zh-cn/application-dev/quick-start/module-structure.md
@@ -190,15 +190,45 @@ metadata对象示例：
 
 ## abilities对象的内部结构
 
-**OpenHarmony中不允许应用隐藏入口图标**
+**表8** **abilities对象的内部结构说明**
+
+| 属性名称 | 含义 | 数据类型 | 是否可缺省 |
+| -------- | -------- | -------- | -------- |
+| process | 运行应用程序或Ability的进程名称。如果在deviceConfig标记中配置了进程，则应用程序的所有能力都在此进程中运行。您还可以为特定能力设置流程属性，以便该能力可以在此流程中运行。如果此属性设置为与其他应用程序相同的进程名称，则所有这些应用程序可以在同一进程中运行，前提是他们具有相同的联合用户ID和相同的签名。该标签最大字节数为31个字节。 | 字符串 | 可缺省，缺省值为空。 |
+| name | 标识Ability名称。取值可采用反向域名方式表示，由包名和类名组成，如"com.example.myapplication.EntryAbility"；也可采用"."开头的类名方式表示，如".EntryAbility"。<br/>Ability的名称，需在一个应用的范围内保证唯一。说明：在使用DevEco&nbsp;Studio新建项目时，默认生成首个Ability的配置，即"config.json"中"EntryAbility"的配置。如使用其他IDE工具，可自定义名称。该标签最大长度为127个字节。 | 字符串 | 不可缺省 |
+| description | 标识对Ability的描述。取值可以是描述性内容，也可以是对描述性内容的资源索引，以支持多语言。该标签最大长度为255个字节。 | 字符串 | 可缺省，缺省值为空。 |
+| icon | 标识Ability图标资源文件的索引。取值示例：$media:ability_icon。如果在该Ability的skills属性中，actions的取值包含&nbsp;"action.system.home"，entities取值中包含"entity.system.home"，则该Ability的icon将同时作为应用的icon。如果存在多个符合条件的Ability，则取位置靠前的Ability的icon作为应用的icon。<br/>说明：应用的"icon"和"label"是用户可感知配置项，需要区别于当前所有已有的应用"icon"或"label"（至少有一个不同）。 | 字符串 | 可缺省，缺省值为空。 |
+| label | 标识Ability对用户显示的名称。取值是对该名称的资源索引，支持多语言，例：$string:ability_label。如果在该Ability的skills属性中，actions的取值包含&nbsp;"action.system.home"，entities取值中包含"entity.system.home"，则该Ability的label将同时作为应用的label。如果存在多个符合条件的Ability，则取位置靠前的Ability的label作为应用的label。<br/>说明：&nbsp;应用的"icon"和"label"是用户可感知配置项，需要区别于当前所有已有的应用"icon"或"label"（至少有一个不同）。该标签为资源文件中定义的字符串的引用，或以"{}"包括的字符串。该标签最大长度为255个字节。 | 字符串 | 可缺省，缺省值为空。 |
+| uri | 标识Ability的统一资源标识符。该标签最大长度为255个字节。 | 字符串 | 可缺省，对于data类型的Ability不可缺省。 |
+| launchType | 标识Ability的启动模式，支持"standard"和"singleton"两种模式：<br/>standard：表示该Ability可以有多实例。该模式适用于大多数应用场景。<br/>singleton：表示该Ability在所有任务栈中仅可以有一个实例。例如，具有全局唯一性的呼叫来电界面即采用"singleton"模式。该标签仅适用于默认设备、平板、智慧屏、车机、智能穿戴。 | 字符串 | 可缺省，缺省值为"singleton"。 |
+| visible | 标识Ability是否可以被其他应用调用。<br/>true：可以被其他应用调用。<br/>false：不能被其他应用调用。 | 布尔类型 | 可缺省，缺省值为"false"。 |
+| permissions | 标识其他应用的Ability调用此Ability时需要申请的权限集合，一个数组元素为一个权限名称。通常采用反向域名格式（最大255字节），取值为系统预定义的权限。 | 字符串数组 | 可缺省，缺省值为空。 |
+|skills | 标识Ability能够接收的want的特征。 | 对象数组 | 可缺省，缺省值为空。 |
+| deviceCapability | 标识Ability运行时要求设备具有的能力，采用字符串数组的格式表示。该标签为数组，支持最多配置512个元素，单个元素最大字节长度为64。 | 字符串数组 | 可缺省，缺省值为空。 |
+| metaData | 元数据。 | 对象 | 可缺省，缺省值为空。 |
+| type | 标识Ability的类型。取值范围如下：<br/>page：表示基于Page模板开发的FA，用于提供与用户交互的能力。<br/>service：表示基于Service模板开发的PA，用于提供后台运行任务的能力。<br/>data：表示基于Data模板开发的PA，用于对外部提供统一的数据访问对象。<br/>CA：表示支持其他应用以窗口方式调起该Ability。 | 字符串 | 不可缺省。 |
+| orientation | 标识该Ability的显示模式。该标签仅适用于page类型的Ability。取值范围如下：<br/>unspecified：由系统自动判断显示方向。<br/>landscape：横屏模式。<br/>portrait：竖屏模式。<br/>followRecent：跟随栈中最近的应用。 | 字符串 | 可缺省，缺省值为"unspecified"。 |
+| backgroundModes | 标识后台服务的类型，可以为一个服务配置多个后台服务类型。该标签仅适用于service类型的Ability。取值范围如下：<br/>dataTransfer：通过网络/对端设备进行数据下载、备份、分享、传输等业务。<br/>audioPlayback：音频输出业务。<br/>audioRecording：音频输入业务。<br/>pictureInPicture：画中画、小窗口播放视频业务。<br/>voip：音视频电话、VOIP业务。<br/>location：定位、导航业务。<br/>bluetoothInteraction：蓝牙扫描、连接、传输业务。<br/>wifiInteraction：WLAN扫描、连接、传输业务。<br/>screenFetch：录屏、截屏业务。<br/>multiDeviceConnection：多设备互联业务 | 字符串数组 | 可缺省，缺省值为空。 |
+| grantPermission | 指定是否可以向Ability内任何数据授予权限。 | 布尔值 | 可缺省，缺省值为空。 |
+| readPermission | 标识读取Ability的数据所需的权限。该标签仅适用于data类型的Ability。取值为长度不超过255字节的字符串。该标签仅适用于默认设备、平板、智慧屏、车机、智能穿戴。 | 字符串 | 可缺省，缺省为空。 |
+| writePermission | 标识向Ability写数据所需的权限。该标签仅适用于data类型的Ability。取值为长度不超过255字节的字符串。 | 字符串 | 可缺省，缺省为空。 |
+| configChanges | 标识Ability关注的系统配置集合。当已关注的配置发生变更后，Ability会收到onConfigurationUpdated回调。取值范围：<br/>mcc：表示IMSI移动设备国家/地区代码（MCC）发生变更。典型场景：检测到SIM并更新MCC。<br/>mnc：IMSI移动设备网络代码（MNC）发生变更。典型场景：检测到SIM并更新MNC。<br/>locale：表示语言区域发生变更。典型场景：用户已为设备文本的文本显示选择新的语言类型。<br/>layout：表示屏幕布局发生变更。典型场景：当前有不同的显示形态都处于活跃状态。<br/>fontSize：表示字号发生变更。典型场景：用户已设置新的全局字号。<br/>orientation：表示屏幕方向发生变更。典型场景：用户旋转设备。<br/>density：表示显示密度发生变更。典型场景：用户可能指定不同的显示比例，或当前有不同的显示形态同时处于活跃状态。<br/>size：显示窗口大小发生变更。<br/>smallestSize：显示窗口较短边的边长发生变更。<br/>colorMode：颜色模式发生变更。 | 字符串数组 | 可缺省，缺省为空。 |
+| mission | 标识Ability指定的任务栈。该标签仅适用于page类型的Ability。默认情况下应用中所有Ability同属一个任务栈。 | 字符串 | 可缺省，缺省为应用的包名。 |
+| targetAbility | 标识当前Ability重用的目标Ability。该标签仅适用于page类型的Ability。如果配置了targetAbility属性，则当前Ability（即别名Ability）的属性中仅name、icon、label、visible、permissions、skills生效，其他属性均沿用targetAbility中的属性值。目标Ability必须与别名Ability在同一应用中，且在配置文件中目标Ability必须在别名之前进行声明。 | 字符串 | 可缺省，缺省值为空。表示当前Ability不是一个别名Ability。 |
+| formsEnabled | 标识Ability是否支持卡片（forms）功能。该标签仅适用于page类型的Ability。<br/>true：支持卡片能力。<br/>false：不支持卡片能力。 | 布尔值 | 可缺省，缺省值为false。 |
+| forms | 标识服务卡片的属性。该标签仅当formsEnabled为"true"时，才能生效。 | 对象数组 | 可缺省，缺省值为空。 |
+| srcLanguage | Ability开发语言的类型，开发者创建工程时由开发者手动选择开发语言。 | 字符串 | 可缺省，缺省值为“js”。 |
+| srcPath | 该标签标识Ability对应的JS组件代码路径，该标签最大长度为127字节。 | 字符串 | 不可缺省。 |
+| uriPermission | 标识该Ability有权访问的应用程序数据。此属性由模式和路径子属性组成。此属性仅对类型提供者的能力有效。 | 对象 | 可缺省，缺省值为空。 |
+| startWindowIcon | 标识该Ability启动页面图标资源文件的索引。该标签仅适用于page类型的Ability。取值示例：$media:icon。 | 字符串 | 可缺省，缺省值为空。 |
+| startWindowBackground | 标识该Ability启动页面背景颜色资源文件的索引。该标签仅适用于page类型的Ability。取值示例：$color:red。 | 字符串 | 可缺省，缺省值为空。 |
+| removeMissionAfterTerminate | 该标签标识Ability销毁后是否从任务列表中移除任务。该标签仅适用于page类型的Ability。true表示销毁后移除任务，&nbsp;false表示销毁后不移除任务。 | 布尔值 | 可缺省，缺省值为false。 |
 
-OpenHarmony系统对无图标应用严格管控。如果HAP中没有配置入口图标，那么系统会给该应用创建一个默认的图标显示在桌面上;<br>
-用户点击该图标，将跳转到Settings的应用管理中对应的应用详情页面（图1）中。<br>
-如果应用想要隐藏入口图标，需要配置AllowAppDesktopIconHide应用特权，具体配置方式参考[应用特权配置指南](../../device-dev/subsystems/subsys-app-privilege-config-guide.md)。
+**OpenHarmony中不允许应用隐藏入口图标**
 
-**场景说明：** 该功能能防止一些恶意应用，故意配置无入口图标，导致用户找不到软件所在的位置，无法操作卸载应用，在一定程度上保证用户的手机安全
+OpenHarmony系统对无图标应用严格管控，防止一些恶意应用故意配置无入口图标，导致用户找不到软件所在的位置，无法操作卸载应用，在一定程度上保证用户的手机安全。
 
-**入口图标的设置:** 需要在配置文件（config.json）中abilities配置下设置icon，label以及skills,而且skills的配置下必须同时包含“ohos.want.action.home” 和 “entity.system.home”:
+**入口图标的设置:** 需要在配置文件（config.json）中abilities配置下设置icon，label以及skills，而且skills的配置下必须同时包含“ohos.want.action.home” 和 “entity.system.home”。
 ```
 {
   "module":{
@@ -221,72 +251,32 @@ OpenHarmony系统对无图标应用严格管控。如果HAP中没有配置入口
 }
 ```
 
-**入口图标及入口标签的显示规则**
+如果应用确需隐藏入口图标，需要配置AllowAppDesktopIconHide应用特权，具体配置方式参考[应用特权配置指南](../../device-dev/subsystems/subsys-app-privilege-config-guide.md)。详细的入口图标及入口标签的显示规则如下。
 * HAP中包含Page类型的PageAbility
   * 配置文件（config.json）中abilities配置中设置了入口图标
     * 该应用没有隐藏图标的特权
-      * 显示桌面图标为该PageAbility配置的图标
-      * 显示桌面Label为该PageAbility配置的Label（如果没有配置Label，返回包名）
-      * 显示组件名为该PageAbility的组件名
-      * 用户点击该桌面图标，页面跳转到该PageAbility首页
+      * 系统将使用该PageAbility配置的icon作为入口图标，并显示在桌面上。用户点击该图标，页面跳转到该PageAbility首页。
+      * 系统将使用该PageAbility配置的label作为入口标签，并显示在桌面上（如果没有配置label，返回包名）。
     * 该应用具有隐藏图标的特权
-      * 桌面查询时不返回应用信息，不会在桌面上显示对应的图标。
+      * 桌面查询时不返回应用信息，不会在桌面上显示对应的入口图标和标签。
   * 配置文件（config.json）中abilities配置中未设置入口图标
     * 该应用没有隐藏图标的特权
-      * 显示桌面图标为系统默认图标
-      * 显示桌面Label为该应用的包名
-      * 用户点击该桌面图标，页面跳转到该应用的详情页面（图1）
+      * 系统将使用系统默认图标作为入口图标，并显示在桌面上。用户点击该图标，页面跳转到应用管理中对应的应用详情页面（参考下图）。
+      * 系统将使用应用的包名作为入口标签，并显示在桌面上。
     * 该应用具有隐藏图标的特权
-      * 桌面查询时不返回应用信息，不会在桌面上显示对应的图标。
+      * 桌面查询时不返回应用信息，不会在桌面上显示对应的入口图标和标签。
 * HAP中不包含Page类型的PageAbility
   * 该应用没有隐藏图标的特权
-    * 显示桌面图标为系统默认图标
-    * 显示桌面Label为该应用的包名
-    * 用户点击该桌面图标，页面跳转到该应用的详情页面（图1）
+    * 系统将使用系统默认图标作为入口图标，并显示在桌面上。用户点击该图标，页面跳转到应用管理中对应的应用详情页面（参考下图）。
+    * 系统将使用应用的包名作为入口标签，并显示在桌面上。
   * 该应用具有隐藏图标的特权
-    * 桌面查询时不返回应用信息，不会在桌面上显示对应的图标。
-
-注：应用详情页面（图1）中显示的label可能与桌面上显示的不同。如果非Page类型的PageAbility配置了入口图标和label，那么详情页中显示的即为配置的。<br><br>
+    * 桌面查询时不返回应用信息，不会在桌面上显示对应的入口图标和标签。
 
-图1
+**图1** 应用的详情页示意图  
 
 ![应用的详情页例图](figures/application_details.jpg)
 
-
-**表8** **abilities对象的内部结构说明**
-
-| 属性名称 | 含义 | 数据类型 | 是否可缺省 |
-| -------- | -------- | -------- | -------- |
-| process | 运行应用程序或Ability的进程名称。如果在deviceConfig标记中配置了进程，则应用程序的所有能力都在此进程中运行。您还可以为特定能力设置流程属性，以便该能力可以在此流程中运行。如果此属性设置为与其他应用程序相同的进程名称，则所有这些应用程序可以在同一进程中运行，前提是他们具有相同的联合用户ID和相同的签名。该标签最大字节数为31个字节。 | 字符串 | 可缺省，缺省值为空。 |
-| name | 标识Ability名称。取值可采用反向域名方式表示，由包名和类名组成，如"com.example.myapplication.EntryAbility"；也可采用"."开头的类名方式表示，如".EntryAbility"。<br/>Ability的名称，需在一个应用的范围内保证唯一。说明：在使用DevEco&nbsp;Studio新建项目时，默认生成首个Ability的配置，即"config.json"中"EntryAbility"的配置。如使用其他IDE工具，可自定义名称。该标签最大长度为127个字节。 | 字符串 | 不可缺省 |
-| description | 标识对Ability的描述。取值可以是描述性内容，也可以是对描述性内容的资源索引，以支持多语言。该标签最大长度为255个字节。 | 字符串 | 可缺省，缺省值为空。 |
-| icon | 标识Ability图标资源文件的索引。取值示例：$media:ability_icon。如果在该Ability的skills属性中，actions的取值包含&nbsp;"action.system.home"，entities取值中包含"entity.system.home"，则该Ability的icon将同时作为应用的icon。如果存在多个符合条件的Ability，则取位置靠前的Ability的icon作为应用的icon。<br/>说明：应用的"icon"和"label"是用户可感知配置项，需要区别于当前所有已有的应用"icon"或"label"（至少有一个不同）。 | 字符串 | 可缺省，缺省值为空。 |
-| label | 标识Ability对用户显示的名称。取值是对该名称的资源索引，支持多语言，例：$string:ability_label。如果在该Ability的skills属性中，actions的取值包含&nbsp;"action.system.home"，entities取值中包含"entity.system.home"，则该Ability的label将同时作为应用的label。如果存在多个符合条件的Ability，则取位置靠前的Ability的label作为应用的label。<br/>说明：&nbsp;应用的"icon"和"label"是用户可感知配置项，需要区别于当前所有已有的应用"icon"或"label"（至少有一个不同）。该标签为资源文件中定义的字符串的引用，或以"{}"包括的字符串。该标签最大长度为255个字节。 | 字符串 | 可缺省，缺省值为空。 |
-| uri | 标识Ability的统一资源标识符。该标签最大长度为255个字节。 | 字符串 | 可缺省，对于data类型的Ability不可缺省。 |
-| launchType | 标识Ability的启动模式，支持"standard"和"singleton"两种模式：<br/>standard：表示该Ability可以有多实例。该模式适用于大多数应用场景。<br/>singleton：表示该Ability在所有任务栈中仅可以有一个实例。例如，具有全局唯一性的呼叫来电界面即采用"singleton"模式。该标签仅适用于默认设备、平板、智慧屏、车机、智能穿戴。 | 字符串 | 可缺省，缺省值为"singleton"。 |
-| visible | 标识Ability是否可以被其他应用调用。<br/>true：可以被其他应用调用。<br/>false：不能被其他应用调用。 | 布尔类型 | 可缺省，缺省值为"false"。 |
-| permissions | 标识其他应用的Ability调用此Ability时需要申请的权限集合，一个数组元素为一个权限名称。通常采用反向域名格式（最大255字节），取值为系统预定义的权限。 | 字符串数组 | 可缺省，缺省值为空。 |
-|skills | 标识Ability能够接收的want的特征。 | 对象数组 | 可缺省，缺省值为空。 |
-| deviceCapability | 标识Ability运行时要求设备具有的能力，采用字符串数组的格式表示。该标签为数组，支持最多配置512个元素，单个元素最大字节长度为64。 | 字符串数组 | 可缺省，缺省值为空。 |
-| metaData | 元数据。 | 对象 | 可缺省，缺省值为空。 |
-| type | 标识Ability的类型。取值范围如下：<br/>page：表示基于Page模板开发的FA，用于提供与用户交互的能力。<br/>service：表示基于Service模板开发的PA，用于提供后台运行任务的能力。<br/>data：表示基于Data模板开发的PA，用于对外部提供统一的数据访问对象。<br/>CA：表示支持其他应用以窗口方式调起该Ability。 | 字符串 | 不可缺省。 |
-| orientation | 标识该Ability的显示模式。该标签仅适用于page类型的Ability。取值范围如下：<br/>unspecified：由系统自动判断显示方向。<br/>landscape：横屏模式。<br/>portrait：竖屏模式。<br/>followRecent：跟随栈中最近的应用。 | 字符串 | 可缺省，缺省值为"unspecified"。 |
-| backgroundModes | 标识后台服务的类型，可以为一个服务配置多个后台服务类型。该标签仅适用于service类型的Ability。取值范围如下：<br/>dataTransfer：通过网络/对端设备进行数据下载、备份、分享、传输等业务。<br/>audioPlayback：音频输出业务。<br/>audioRecording：音频输入业务。<br/>pictureInPicture：画中画、小窗口播放视频业务。<br/>voip：音视频电话、VOIP业务。<br/>location：定位、导航业务。<br/>bluetoothInteraction：蓝牙扫描、连接、传输业务。<br/>wifiInteraction：WLAN扫描、连接、传输业务。<br/>screenFetch：录屏、截屏业务。<br/>multiDeviceConnection：多设备互联业务 | 字符串数组 | 可缺省，缺省值为空。 |
-| grantPermission | 指定是否可以向Ability内任何数据授予权限。 | 布尔值 | 可缺省，缺省值为空。 |
-| readPermission | 标识读取Ability的数据所需的权限。该标签仅适用于data类型的Ability。取值为长度不超过255字节的字符串。该标签仅适用于默认设备、平板、智慧屏、车机、智能穿戴。 | 字符串 | 可缺省，缺省为空。 |
-| writePermission | 标识向Ability写数据所需的权限。该标签仅适用于data类型的Ability。取值为长度不超过255字节的字符串。 | 字符串 | 可缺省，缺省为空。 |
-| configChanges | 标识Ability关注的系统配置集合。当已关注的配置发生变更后，Ability会收到onConfigurationUpdated回调。取值范围：<br/>mcc：表示IMSI移动设备国家/地区代码（MCC）发生变更。典型场景：检测到SIM并更新MCC。<br/>mnc：IMSI移动设备网络代码（MNC）发生变更。典型场景：检测到SIM并更新MNC。<br/>locale：表示语言区域发生变更。典型场景：用户已为设备文本的文本显示选择新的语言类型。<br/>layout：表示屏幕布局发生变更。典型场景：当前有不同的显示形态都处于活跃状态。<br/>fontSize：表示字号发生变更。典型场景：用户已设置新的全局字号。<br/>orientation：表示屏幕方向发生变更。典型场景：用户旋转设备。<br/>density：表示显示密度发生变更。典型场景：用户可能指定不同的显示比例，或当前有不同的显示形态同时处于活跃状态。<br/>size：显示窗口大小发生变更。<br/>smallestSize：显示窗口较短边的边长发生变更。<br/>colorMode：颜色模式发生变更。 | 字符串数组 | 可缺省，缺省为空。 |
-| mission | 标识Ability指定的任务栈。该标签仅适用于page类型的Ability。默认情况下应用中所有Ability同属一个任务栈。 | 字符串 | 可缺省，缺省为应用的包名。 |
-| targetAbility | 标识当前Ability重用的目标Ability。该标签仅适用于page类型的Ability。如果配置了targetAbility属性，则当前Ability（即别名Ability）的属性中仅name、icon、label、visible、permissions、skills生效，其他属性均沿用targetAbility中的属性值。目标Ability必须与别名Ability在同一应用中，且在配置文件中目标Ability必须在别名之前进行声明。 | 字符串 | 可缺省，缺省值为空。表示当前Ability不是一个别名Ability。 |
-| formsEnabled | 标识Ability是否支持卡片（forms）功能。该标签仅适用于page类型的Ability。<br/>true：支持卡片能力。<br/>false：不支持卡片能力。 | 布尔值 | 可缺省，缺省值为false。 |
-| forms | 标识服务卡片的属性。该标签仅当formsEnabled为"true"时，才能生效。 | 对象数组 | 可缺省，缺省值为空。 |
-| srcLanguage | Ability开发语言的类型，开发者创建工程时由开发者手动选择开发语言。 | 字符串 | 可缺省，缺省值为“js”。 |
-| srcPath | 该标签标识Ability对应的JS组件代码路径，该标签最大长度为127字节。 | 字符串 | 不可缺省。 |
-| uriPermission | 标识该Ability有权访问的应用程序数据。此属性由模式和路径子属性组成。此属性仅对类型提供者的能力有效。 | 对象 | 可缺省，缺省值为空。 |
-| startWindowIcon | 标识该Ability启动页面图标资源文件的索引。该标签仅适用于page类型的Ability。取值示例：$media:icon。 | 字符串 | 可缺省，缺省值为空。 |
-| startWindowBackground | 标识该Ability启动页面背景颜色资源文件的索引。该标签仅适用于page类型的Ability。取值示例：$color:red。 | 字符串 | 可缺省，缺省值为空。 |
-| removeMissionAfterTerminate | 该标签标识Ability销毁后是否从任务列表中移除任务。该标签仅适用于page类型的Ability。true表示销毁后移除任务，&nbsp;false表示销毁后不移除任务。 | 布尔值 | 可缺省，缺省值为false。 |
-
+注：应用详情页面中显示的label可能与桌面上显示的不同。如果非Page类型的PageAbility配置了入口图标和label，那么详情页中显示的即为配置的。
 ## uriPermission对象的内部结构
 
 **表9** **uriPermission对象的内部结构说明**
diff --git a/zh-cn/application-dev/quick-start/resource-categories-and-access.md b/zh-cn/application-dev/quick-start/resource-categories-and-access.md
index e7839cb9675e4aae49905e392bdc933695b93315..5892d7e5d1997bfcff0218950d9ee57575529ffb 100644
--- a/zh-cn/application-dev/quick-start/resource-categories-and-access.md
+++ b/zh-cn/application-dev/quick-start/resource-categories-and-access.md
@@ -246,7 +246,7 @@ plural.json文件的内容如下：
 >
 > `$r`返回值为Resource对象，可通过[getStringValue](../reference/apis/js-apis-resource-manager.md#getstringvalue9) 方法获取对应的字符串。
 
-在xxx.ets文件中，可以使用在resources目录中定义的资源。结合[资源组目录](#资源组目录)中的“资源文件示例”，资源使用示例如下：
+在xxx.ets文件中，可以使用在resources目录中定义的资源。资源分类中[资源组目录](#资源组目录)下的“资源文件示例”显示了.json文件内容，包含color.json文件、string.json文件和plural.json文件。资源的具体使用方法如下：
 
 ```ts
 Text($r('app.string.string_hello'))
@@ -257,13 +257,14 @@ Text($r('app.string.string_world'))
   .fontColor($r('app.color.color_world'))
   .fontSize($r('app.float.font_world'))
 
-// 引用string.json资源，$r的第二个参数用于替换%s，value为"We will arrive at five of the clock"。
+// 引用string.json资源。Text中$r的第一个参数指定string资源，第二个参数用于替换string.json文件中的%s。
+//如下示例代码value为"We will arrive at five of the clock"。
 Text($r('app.string.message_arrive', "five of the clock"))
   .fontColor($r('app.color.color_hello'))
   .fontSize($r('app.float.font_hello'))
 
-// 引用plural$资源，第一个指定plural资源，第二个参数指定单复数的数量quantity，此处第三个数字为对%d的替换
-// 单数下value为"5 apple"，复数下value为"5 apples"。
+// 引用plural$资源。Text中$r的第一个指定plural资源，第二个参数用于指定单复数（在中文，单复数均使用other。在英文，one：代表单数，取值为1；other：代表复数，取值为大于等于1的整数），第三个参数用于替换%d
+// 如下示例代码为复数，value为"5 apples"。
 Text($r('app.plural.eat_apple', 5, 5))
   .fontColor($r('app.color.color_world'))
   .fontSize($r('app.float.font_world'))
@@ -314,4 +315,4 @@ Image($r('sys.media.ohos_app_icon'))
 
 针对访问应用资源，有以下相关实例可供参考：
 
-- [`ResourceManager`：资源管理器（ArkTS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/common/ResourceManager)
+- [`ResourceManager`：资源管理器（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/Internationalnation/ResourceManager)
diff --git a/zh-cn/application-dev/reference/apis/Readme-CN.md b/zh-cn/application-dev/reference/apis/Readme-CN.md
index e004a817eeee7d9cea9b1fdf7ea563eef361e0fc..e8a9c68a2e0f00d36ccb578978d3ef88c3bfb931 100755
--- a/zh-cn/application-dev/reference/apis/Readme-CN.md
+++ b/zh-cn/application-dev/reference/apis/Readme-CN.md
@@ -255,7 +255,6 @@
   - [@ohos.net.connection (网络连接管理)](js-apis-net-connection.md)
   - [@ohos.net.ethernet (以太网连接管理)](js-apis-net-ethernet.md)
   - [@ohos.net.http (数据请求)](js-apis-http.md)
-  - [@ohos.net.policy (网络策略管理)](js-apis-net-policy.md)
   - [@ohos.net.sharing (网络共享管理)](js-apis-net-sharing.md)
   - [@ohos.net.socket (Socket连接)](js-apis-socket.md)
   - [@ohos.net.webSocket (WebSocket连接)](js-apis-webSocket.md)
diff --git a/zh-cn/application-dev/reference/apis/js-apis-Bundle.md b/zh-cn/application-dev/reference/apis/js-apis-Bundle.md
index 88a933f14307b125ddcd79a8a6e9921f9041ce8e..1f281d4a6dccd6212acb48871d98e5467077f5f8 100755
--- a/zh-cn/application-dev/reference/apis/js-apis-Bundle.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-Bundle.md
@@ -903,7 +903,7 @@ bundle.getAllApplicationInfo(bundleFlags, userId, (err, data) => {
 
 > 从API version 9开始不再维护，建议使用[bundleManager.getAllApplicationInfo](js-apis-bundleManager.md#bundlemanagergetallapplicationinfo)替代。
 
-getAllApplicationInfo(bundleFlags: number, callback: AsyncCallback<Array\<ApplicationInfo>>) : void;
+getAllApplicationInfo(bundleFlags: number, callback: AsyncCallback\<Array\<ApplicationInfo\>\>): void;
 
 获取调用方所在用户下已安装的应用信息，使用callback异步回调。
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-abilityAccessCtrl.md b/zh-cn/application-dev/reference/apis/js-apis-abilityAccessCtrl.md
index b638b49161042235f7bd438d32b6715bacedadba..41c1868ee8ddae1131ba0e2e7a511bfd3c3c9dfb 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-abilityAccessCtrl.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-abilityAccessCtrl.md
@@ -460,7 +460,7 @@ on(type: 'permissionStateChange', tokenIDList: Array&lt;number&gt;, permissionLi
 **示例：**
 
 ```js
-import abilityAccessCtrl, {Permissions} from '@ohos.abilityAccessCtrl';
+import {Permissions} from '@ohos.abilityAccessCtrl';
 import bundleManager from '@ohos.bundle.bundleManager';
 
 let atManager = abilityAccessCtrl.createAtManager();
@@ -511,7 +511,7 @@ off(type: 'permissionStateChange', tokenIDList: Array&lt;number&gt;, permissionL
 **示例：**
 
 ```js
-import abilityAccessCtrl, {Permissions} from '@ohos.abilityAccessCtrl';
+import {Permissions} from '@ohos.abilityAccessCtrl';
 import bundleManager from '@ohos.bundle.bundleManager';
 
 let atManager = abilityAccessCtrl.createAtManager();
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-abilityConstant.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-abilityConstant.md
index d34d7553e15a5f606ccd3c5a7debb8f59a968b71..74eb654504e8ecab27945496ab7bb1b22fb745d2 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-abilityConstant.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-abilityConstant.md
@@ -30,7 +30,7 @@ import AbilityConstant from '@ohos.app.ability.AbilityConstant';
 
 Ability初次启动原因，该类型为枚举，可配合[Ability](js-apis-app-ability-uiAbility.md)的[onCreate(want, launchParam)](js-apis-app-ability-uiAbility.md#uiabilityoncreate)方法根据launchParam.launchReason的不同类型执行相应操作。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Ability.AbilityRuntime.Core
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
 
 | 名称                          | 值   | 说明                                                         |
 | ----------------------------- | ---- | ------------------------------------------------------------ |
@@ -58,7 +58,7 @@ class MyAbility extends UIAbility {
 
 Ability上次退出原因，该类型为枚举，可配合[Ability](js-apis-app-ability-uiAbility.md)的[onCreate(want, launchParam)](js-apis-app-ability-uiAbility.md#uiabilityoncreate)方法根据launchParam.lastExitReason的不同类型执行相应操作。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Ability.AbilityRuntime.Core
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
 
 | 名称                          | 值   | 说明                                                         |
 | ----------------------------- | ---- | ------------------------------------------------------------ |
@@ -84,7 +84,7 @@ class MyAbility extends UIAbility {
 
 Ability迁移结果，该类型为枚举，可配合[Ability](js-apis-app-ability-uiAbility.md)的[onContinue(wantParam)](js-apis-app-ability-uiAbility.md#uiabilityoncontinue)方法进完成相应的返回。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Ability.AbilityRuntime.Core
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
 
 | 名称                          | 值   | 说明                                                         |
 | ----------------------------- | ---- | ------------------------------------------------------------ |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-abilityDelegatorRegistry.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-abilityDelegatorRegistry.md
index 4268caab81f591ccf21a0617f7f385f2937df6b8..e444dffba232b0f9835911b8f233feb4e2c560de 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-abilityDelegatorRegistry.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-abilityDelegatorRegistry.md
@@ -44,8 +44,6 @@ getAbilityDelegator(): AbilityDelegator
 **示例：**
 
 ```ts
-import AbilityDelegatorRegistry from '@ohos.app.ability.abilityDelegatorRegistry';
-
 let abilityDelegator = AbilityDelegatorRegistry.getAbilityDelegator();
 
 let want = {
@@ -78,8 +76,6 @@ getArguments(): AbilityDelegatorArgs
 **示例：**
 
 ```ts
-import AbilityDelegatorRegistry from '@ohos.app.ability.abilityDelegatorRegistry';
-
 let args = AbilityDelegatorRegistry.getArguments();
 console.info('getArguments bundleName:' + args.bundleName);
 console.info('getArguments parameters:' + JSON.stringify(args.parameters));
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-appManager.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-appManager.md
index 1f7bf1774933e5d8c4a80598492eeb7244d30c10..573588860bcd6e297488093d078ff5d334c11f02 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-appManager.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-appManager.md
@@ -669,7 +669,11 @@ killProcessWithAccount(bundleName: string, accountId: number): Promise\<void\>
 
 切断account进程（Promise形式）。
 
-**需要权限**：ohos.permission.CLEAN_BACKGROUND_PROCESSES，ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS，当accountId为当前用户时，不需要校验ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS权限。
+> **说明：** 
+>
+> 当accountId为当前用户时，不需要校验ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS权限。
+
+**需要权限**：ohos.permission.CLEAN_BACKGROUND_PROCESSES，ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS
 
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Core
 
@@ -715,12 +719,16 @@ killProcessWithAccount(bundleName: string, accountId: number, callback: AsyncCal
 
 切断account进程（callback形式）。
 
+> **说明：** 
+>
+> 当accountId为当前用户时，不需要校验ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS权限。
+
+**需要权限**：ohos.permission.CLEAN_BACKGROUND_PROCESSES，ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS
+
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Core
 
 **系统API**: 此接口为系统接口，三方应用不支持调用。
 
-**需要权限**：ohos.permission.CLEAN_BACKGROUND_PROCESSES，ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS，当accountId为当前用户时，不需要校验ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS权限。
-
 **参数：**
 
   | 参数名 | 类型 | 必填 | 说明 | 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-configuration.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-configuration.md
index f7db417887d5888f148e27b49fed38d0c98645e7..ec934c197c5601a01cff984fad49f0f9a0397d8a 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-configuration.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-configuration.md
@@ -6,6 +6,12 @@
 > 
 > 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
 
+## 导入模块
+
+```ts
+import Configuration from '@ohos.app.ability.Configuration';
+```
+
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Ability.AbilityBase
 
   | 名称 | 类型 | 可读 | 可写 | 说明 |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-dataUriUtils.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-dataUriUtils.md
index 74b37b9ae47045c7278ecb661aa8bc6be176ed65..15b94a4fb2dcbbe24b7be920716a994aa2a6ee45 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-dataUriUtils.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-dataUriUtils.md
@@ -1,150 +1,156 @@
-# @ohos.app.ability.dataUriUtils (DataUriUtils模块)
-
-DataUriUtils模块提供用于处理uri对象的能力，包括获取、绑定、删除和更新指定uri对象的路径末尾的ID。
-
-> **说明：**
-> 
-> 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
-
-## 导入模块
-
-```ts
-import dataUriUtils from '@ohos.app.ability.dataUriUtils';
-```
-
-## dataUriUtils.getId
-
-getId(uri: string): number
-
-获取指定uri路径末尾的ID。
-
-**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
-
-**参数：**
-
-| 名称 | 类型   | 必填 | 描述                        |
-| ---- | ------ | ---- | --------------------------- |
-| uri  | string | 是   | 表示uri对象。 |
-
-**返回值：**
-
-| 类型   | 说明                     |
-| ------ | ------------------------ |
-| number | 返回uri路径末尾的ID。 |
-
-**示例：**
-
-```ts
-try {
-    let id = dataUriUtils.getId('com.example.dataUriUtils/1221');
-    console.info('get id: ${id}');
-} catch(err) {
-    console.error('get id err ,check the uri ${err}');
-}
-```
-
-## dataUriUtils.attachId
-
-attachId(uri: string, id: number): string
-
-将ID附加到uri的路径末尾。
-
-**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
-
-**参数：**
-
-| 名称 | 类型   | 必填 | 描述                        |
-| ---- | ------ | ---- | --------------------------- |
-| uri  | string | 是   | 表示uri对象。 |
-| id   | number | 是   | 表示要附加的ID。            |
-
-**返回值：**
-
-| 类型   | 说明                  |
-| ------ | --------------------- |
-| string | 返回附加ID之后的uri对象。 |
-
-**示例：**
-
-```ts
-let id = 1122;
-try {
-    let uri = dataUriUtils.attachId(
-        'com.example.dataUriUtils',
-        id,
-    );
-    console.info('attachId the uri is: ${uri}');
-} catch (err) {
-    console.error('get id err ,check the uri ${err}');
-}
-
-```
-
-## dataUriUtils.deleteId
-
-deleteId(uri: string): string
-
-删除指定uri路径末尾的ID。
-
-**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
-
-**参数：**
-
-| 名称 | 类型   | 必填 | 描述                        |
-| ---- | ------ | ---- | --------------------------- |
-| uri  | string | 是   | 表示要从中删除ID的uri对象。 |
-
-**返回值：**
-
-| 类型   | 说明                |
-| ------ | ------------------- |
-| string | 返回删除ID之后的uri对象。 |
-
-**示例：**
-
-```ts
-try {
-    let uri = dataUriUtils.deleteId('com.example.dataUriUtils/1221');
-    console.info('delete id with the uri is: ${uri}');
-} catch(err) {
-    console.error('delete uri err, check the input uri ${err}');
-}
-
-```
-
-## dataUriUtils.updateId
-
-updateId(uri: string, id: number): string
-
-更新指定uri中的ID。
-
-**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
-
-**参数：**
-
-| 名称 | 类型   | 必填 | 描述                |
-| ---- | ------ | ---- | ------------------- |
-| uri  | string | 是   | 表示uri对象 |
-| id   | number | 是   | 表示要更新的ID            |
-
-**返回值：**
-
-| 类型   | 说明            |
-| ------ | --------------- |
-| string | 返回更新ID之后的uri对象。 |
-
-**示例：**
-
-```ts
-
-try {
-    let id = 1122;
-    let uri = dataUriUtils.updateId(
-        'com.example.dataUriUtils/1221',
-        id
-    );
-} catch (err) {
-    console.error('delete uri err, check the input uri ${err}');
-}
-```
-
+# @ohos.app.ability.dataUriUtils (DataUriUtils模块)
+
+DataUriUtils模块提供用于处理uri对象的能力，包括获取、绑定、删除和更新指定uri对象的路径末尾的ID。
+
+> **说明：**
+> 
+> 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
+
+## 导入模块
+
+```ts
+import dataUriUtils from '@ohos.app.ability.dataUriUtils';
+```
+
+## dataUriUtils.getId
+
+getId(uri: string): number
+
+获取指定uri路径末尾的ID。
+
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
+
+**参数：**
+
+| 参数名 | 类型   | 必填 | 说明                        |
+| ---- | ------ | ---- | --------------------------- |
+| uri  | string | 是   | 表示uri对象。 |
+
+**返回值：**
+
+| 类型   | 说明                     |
+| ------ | ------------------------ |
+| number | 返回uri路径末尾的ID。 |
+
+**示例：**
+
+```ts
+try {
+    let id = dataUriUtils.getId('com.example.dataUriUtils/1221');
+    console.info('get id: ${id}');
+} catch(err) {
+    console.error('get id err ,check the uri ${err}');
+}
+```
+
+
+
+## dataUriUtils.attachId
+
+attachId(uri: string, id: number): string
+
+将ID附加到uri的路径末尾。
+
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
+
+**参数：**
+
+| 参数名 | 类型   | 必填 | 说明                        |
+| ---- | ------ | ---- | --------------------------- |
+| uri  | string | 是   | 表示uri对象。 |
+| id   | number | 是   | 表示要附加的ID。            |
+
+**返回值：**
+
+| 类型   | 说明                  |
+| ------ | --------------------- |
+| string | 返回附加ID之后的uri对象。 |
+
+**示例：**
+
+```ts
+let id = 1122;
+try {
+    let uri = dataUriUtils.attachId(
+        'com.example.dataUriUtils',
+        id,
+    );
+    console.info('attachId the uri is: ${uri}');
+} catch (err) {
+    console.error('get id err ,check the uri ${err}');
+}
+
+```
+
+
+
+## dataUriUtils.deleteId
+
+deleteId(uri: string): string
+
+删除指定uri路径末尾的ID。
+
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
+
+**参数：**
+
+| 参数名 | 类型   | 必填 | 说明                        |
+| ---- | ------ | ---- | --------------------------- |
+| uri  | string | 是   | 表示要从中删除ID的uri对象。 |
+
+**返回值：**
+
+| 类型   | 说明                |
+| ------ | ------------------- |
+| string | 返回删除ID之后的uri对象。 |
+
+**示例：**
+
+```ts
+try {
+    let uri = dataUriUtils.deleteId('com.example.dataUriUtils/1221');
+    console.info('delete id with the uri is: ${uri}');
+} catch(err) {
+    console.error('delete uri err, check the input uri ${err}');
+}
+
+```
+
+
+
+## dataUriUtils.updateId
+
+updateId(uri: string, id: number): string
+
+更新指定uri中的ID。
+
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
+
+**参数：**
+
+| 参数名 | 类型   | 必填 | 说明                |
+| ---- | ------ | ---- | ------------------- |
+| uri  | string | 是   | 表示uri对象 |
+| id   | number | 是   | 表示要更新的ID            |
+
+**返回值：**
+
+| 类型   | 说明            |
+| ------ | --------------- |
+| string | 返回更新ID之后的uri对象。 |
+
+**示例：**
+
+```ts
+
+try {
+    let id = 1122;
+    let uri = dataUriUtils.updateId(
+        'com.example.dataUriUtils/1221',
+        id
+    );
+} catch (err) {
+    console.error('delete uri err, check the input uri ${err}');
+}
+```
+
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-dialogRequest.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-dialogRequest.md
index ebdcfaa9f82decdf3a8b69b402a7280e35e63531..f68d823973995e4dcd99e759b0a6a8730d1f6473 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-dialogRequest.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-dialogRequest.md
@@ -1,262 +1,419 @@
-# @ohos.app.ability.dialogRequest (dialogRequest模块)
-
-dialogRequest模块用于处理模态弹框的能力，包括获取RequestInfo（用于绑定模态弹框）、获取RequestCallback（用于设置结果）。
-模态弹框是指一个系统弹出框，其特点在于：该弹出框会拦截弹框之下的页面的鼠标、键盘、触屏等事件，销毁该弹框，才能操作下面的页面。
-
-> **说明：**
->
->  - 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
->  - 本模块接口在ServiceExtensionAbility下使用，如果ServiceExtensionAbility实现了模态弹框，则可以使用本模块的接口获取请求方的RequestInfo、RequestCallback并返回请求结果。
-
-## 导入模块
-
-```js
-import dialogRequest from '@ohos.app.ability.dialogRequest';
-```
-
-## dialogRequest.getRequestInfo
-
-getRequestInfo(want: Want): RequestInfo
-
-从Want中获取请求方的RequestInfo。
-
-**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
-
-**参数：**
-
-| 名称 | 类型   | 必填 | 描述                        |
-| ---- | ------ | ---- | --------------------------- |
-| want  | [Want](js-apis-application-want.md) | 是   | 表示发起方请求弹框时传入的want信息。 |
-
-**返回值：**
-
-| 类型   | 说明                     |
-| ------ | ------------------------ |
-| [RequestInfo](#requestinfo) | 请求方RequestInfo,用于绑定模态窗口。 |
-
-**示例：**
-
-```ts
-   import ServiceExtensionAbility from '@ohos.app.ability.ServiceExtensionAbility';
-   import rpc from '@ohos.rpc';
-   import dialogRequest from '@ohos.app.ability.dialogRequest';
-
-   export default class ServiceExtAbility extends ServiceExtensionAbility {
-     onCreate(want) {
-       console.info(TAG, `onCreate, want: ${want.abilityName}`);
-     }
-
-     onRequest(want, startId) {
-       console.info(TAG, `onRequest, want: ${want.abilityName}`);
-       try {
-            var requestInfo = dialogRequest.getRequestInfo(want);
-        } catch(err) {
-            console.error('getRequestInfo err= ${JSON.stringify(err)}');
-        }
-     }
-
-     onConnect(want) {
-       console.info(TAG, `onConnect, want: ${want.abilityName}`);
-     }
-
-     onDisconnect(want) {
-       console.info(TAG, `onDisconnect, want: ${want.abilityName}`);
-     }
-
-     onDestroy() {
-       console.info(TAG, `onDestroy`);
-     }
-   }
-   ```
-
-## dialogRequest.getRequestCallback
-
-getRequestCallback(want: Want): RequestCallback
-
-从Want中获取请求方的RequestCallback。
-
-**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
-
-**参数：**
-
-| 名称 | 类型   | 必填 | 描述                        |
-| ---- | ------ | ---- | --------------------------- |
-| want  | [Want](js-apis-application-want.md) | 是   | 表示发起方请求弹框时传入的want信息。 |
-
-**返回值：**
-
-| 类型   | 说明                     |
-| ------ | ------------------------ |
-| [RequestCallback](#requestcallback) | 请求方RequestCallback,用于设置返回结果。 |
-
-**示例：**
-
-```ts
-   import ServiceExtensionAbility from '@ohos.app.ability.ServiceExtensionAbility';
-   import rpc from '@ohos.rpc';
-   import dialogRequest from '@ohos.app.ability.dialogRequest';
-
-   export default class ServiceExtAbility extends ServiceExtensionAbility {
-     onCreate(want) {
-       console.info(TAG, `onCreate, want: ${want.abilityName}`);
-     }
-
-     onRequest(want, startId) {
-       console.info(TAG, `onRequest, want: ${want.abilityName}`);
-       try {
-            var requestCallback = dialogRequest.getRequestCallback(want);
-        } catch(err) {
-            console.error('getRequestInfo err= ${JSON.stringify(err)}');
-        }
-     }
-
-     onConnect(want) {
-       console.info(TAG, `onConnect, want: ${want.abilityName}`);
-     }
-
-     onDisconnect(want) {
-       console.info(TAG, `onDisconnect, want: ${want.abilityName}`);
-     }
-
-     onDestroy() {
-       console.info(TAG, `onDestroy`);
-     }
-   }
-   ```
-
-## RequestInfo
-
-表示发起方请求信息，作为窗口绑定模态弹框的入参。
-**系统能力**：SystemCapability.Ability.AbilityRuntime.AbilityCore
-
-**示例：**
-
-```ts
-   import ServiceExtensionAbility from '@ohos.app.ability.ServiceExtensionAbility';
-   import rpc from '@ohos.rpc';
-   import dialogRequest from '@ohos.app.ability.dialogRequest';
-   import window from '@ohos.window';
-
-   export default class ServiceExtAbility extends ServiceExtensionAbility {
-     onCreate(want) {
-       console.info(TAG, `onCreate, want: ${want.abilityName}`);
-     }
-
-     onRequest(want, startId) {
-       console.info(TAG, `onRequest, want: ${want.abilityName}`);
-       try {
-            var requestInfo = dialogRequest.getRequestInfo(want);
-            window.bindDialogTarget(requestInfo, () => {
-                console.info('Dialog Window Need Destroy.');
-            }, (err) => {
-                if (err.code) {
-                    console.error('Failed to bind dialog target. Cause: ${JSON.stringify(err)}');
-                    return;
-                }
-                console.info('Succeeded in binding dialog target.');
-            });
-        } catch(err) {
-            console.error('getRequestInfo err= ${JSON.stringify(err)}');
-        }
-     }
-
-     onConnect(want) {
-       console.info(TAG, `onConnect, want: ${want.abilityName}`);
-     }
-
-     onDisconnect(want) {
-       console.info(TAG, `onDisconnect, want: ${want.abilityName}`);
-     }
-
-     onDestroy() {
-       console.info(TAG, `onDestroy`);
-     }
-   }
-   ```
-
-## ResultCode
-
-模态弹框请求结果码。
-
-**系统能力**：SystemCapability.Ability.AbilityRuntime.AbilityCore。
-
-| 名称      | 值          | 说明     |
-| ------------ | ------------------ | ---------------------- |
-| RESULT_OK            | 0          | 表示成功。          |
-| RESULT_CANCEL        | 1          | 表示失败。          |
-
-## RequestResult
-模态弹框请求结果，当前只包含结果码，即RequestResult只当前只有ResultCode这一个成员。
-
-## 属性
-
-**系统能力**：SystemCapability.Ability.AbilityRuntime.AbilityCore
-
-| 名称 | 类型 | 可读 | 可写 | 说明 |
-| -------- | -------- | -------- | -------- | -------- |
-| result | [ResultCode](#resultcode) | 是 | 是 | 表示结果码。 |
-
-## RequestCallback
-
-用于设置模态弹框请求结果的callback接口。
-
-### RequestCallback.setRequestResult
-
-setRequestResult(result: RequestResult): void;
-
-设置请求结果
-
-**系统能力**：SystemCapability.Ability.AbilityRuntime.AbilityCore
-
-**参数：**
-
-| 参数名 | 类型 | 必填 | 说明 |
-| -------- | -------- | -------- | -------- |
-| result | [RequestResult](#requestresult) | 是 | 模态弹框请求结果信息。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息 |
-| ------- | -------------------------------- |
-| 401 | If the input parameter is not valid parameter. |
-
-以上错误码详细介绍请参考[errcode-ability](../errorcodes/errorcode-ability.md)。
-
-**示例：**
-
-```ts
-   import ServiceExtensionAbility from '@ohos.app.ability.ServiceExtensionAbility';
-   import rpc from '@ohos.rpc';
-   import dialogRequest from '@ohos.app.ability.dialogRequest';
-
-   export default class ServiceExtAbility extends ServiceExtensionAbility {
-     onCreate(want) {
-       console.info(TAG, `onCreate, want: ${want.abilityName}`);
-     }
-
-     onRequest(want, startId) {
-       console.info(TAG, `onRequest, want: ${want.abilityName}`);
-       try {
-            var requestCallback = dialogRequest.getRequestCallback(want);
-            let myResult = {
-                result : dialogRequest.ResultCode.RESULT_CANCEL,
-            };
-            requestCallback.setRequestResult(myResult);
-        } catch(err) {
-            console.error('getRequestInfo err= ${JSON.stringify(err)}');
-        }
-     }
-
-     onConnect(want) {
-       console.info(TAG, `onConnect, want: ${want.abilityName}`);
-     }
-
-     onDisconnect(want) {
-       console.info(TAG, `onDisconnect, want: ${want.abilityName}`);
-     }
-
-     onDestroy() {
-       console.info(TAG, `onDestroy`);
-     }
-   }
+# @ohos.app.ability.dialogRequest (dialogRequest模块)
+
+dialogRequest模块用于处理模态弹框的能力，包括获取RequestInfo（用于绑定模态弹框）、获取RequestCallback（用于设置结果）。
+模态弹框是指一个系统弹出框，其特点在于：该弹出框会拦截弹框之下的页面的鼠标、键盘、触屏等事件，销毁该弹框，才能操作下面的页面。
+
+> **说明：**
+>
+>  - 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
+>  - 本模块接口在ServiceExtensionAbility下使用，如果ServiceExtensionAbility实现了模态弹框，则可以使用本模块的接口获取请求方的RequestInfo、RequestCallback并返回请求结果。
+
+## 导入模块
+
+```js
+import dialogRequest from '@ohos.app.ability.dialogRequest';
+```
+
+## dialogRequest.getRequestInfo
+
+getRequestInfo(want: Want): RequestInfo
+
+从Want中获取请求方的RequestInfo。
+
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
+
+**参数：**
+
+| 参数名 | 类型   | 必填 | 说明                        |
+| ---- | ------ | ---- | --------------------------- |
+| want  | [Want](js-apis-application-want.md) | 是   | 表示发起方请求弹框时传入的want信息。 |
+
+**返回值：**
+
+| 类型   | 说明                     |
+| ------ | ------------------------ |
+| [RequestInfo](#requestinfo) | 请求方RequestInfo,用于绑定模态窗口。 |
+
+**示例：**
+
+```ts
+   import ServiceExtensionAbility from '@ohos.app.ability.ServiceExtensionAbility';
+   import rpc from '@ohos.rpc';
+   import dialogRequest from '@ohos.app.ability.dialogRequest';
+
+    const REQUEST_VALUE = 1;
+
+    class StubTest extends rpc.RemoteObject {
+      constructor(des) {
+        super(des);
+      }
+
+      onRemoteRequest(code, data, reply, option) {
+        if (code === REQUEST_VALUE) {
+          let optFir = data.readInt();
+          let optSec = data.readInt();
+          reply.writeInt(optFir + optSec);
+        }
+        return true;
+      }
+
+      queryLocallInterface(descriptor) {
+        return null;
+      }
+
+      getInterfaceDescriptor() {
+        return "";
+      }
+
+      getCallingPid() {
+        return REQUEST_VALUE;
+      }
+
+      getCallingUid() {
+        return REQUEST_VALUE;
+      }
+
+      attachLocalInterface(localInterface, descriptor) {
+      }
+    }
+
+    let TAG = "getRequestInfoTest";
+
+    export default class ServiceExtAbility extends ServiceExtensionAbility {
+      onCreate(want) {
+        console.info(TAG, `onCreate, want: ${want.abilityName}`);
+      }
+
+      onRequest(want, startId) {
+        console.info(TAG, `onRequest, want: ${want.abilityName}`);
+        try {
+          var requestInfo = dialogRequest.getRequestInfo(want);
+        } catch (err) {
+          console.error('getRequestInfo err= ${JSON.stringify(err)}');
+        }
+      }
+
+      onConnect(want) {
+        console.info(TAG, `onConnect, want: ${want.abilityName}`);
+        return new StubTest("test");
+      }
+
+      onDisconnect(want) {
+        console.info(TAG, `onDisconnect, want: ${want.abilityName}`);
+      }
+
+      onDestroy() {
+        console.info(TAG, `onDestroy`);
+      }
+    }
+   ```
+
+## dialogRequest.getRequestCallback
+
+getRequestCallback(want: Want): RequestCallback
+
+从Want中获取请求方的RequestCallback。
+
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
+
+**参数：**
+
+| 参数名 | 类型   | 必填 | 说明                        |
+| ---- | ------ | ---- | --------------------------- |
+| want  | [Want](js-apis-application-want.md) | 是   | 表示发起方请求弹框时传入的want信息。 |
+
+**返回值：**
+
+| 类型   | 说明                     |
+| ------ | ------------------------ |
+| [RequestCallback](#requestcallback) | 请求方RequestCallback,用于设置返回结果。 |
+
+**示例：**
+
+```ts
+   import ServiceExtensionAbility from '@ohos.app.ability.ServiceExtensionAbility';
+   import rpc from '@ohos.rpc';
+   import dialogRequest from '@ohos.app.ability.dialogRequest';
+   
+   let TAG = "getRequestCallbackTest";
+
+   const REQUEST_VALUE = 1;
+
+    class StubTest extends rpc.RemoteObject {
+      constructor(des) {
+        super(des);
+      }
+
+      onRemoteRequest(code, data, reply, option) {
+        if (code === REQUEST_VALUE) {
+          let optFir = data.readInt();
+          let optSec = data.readInt();
+          reply.writeInt(optFir + optSec);
+        }
+        return true;
+      }
+
+      queryLocallInterface(descriptor) {
+        return null;
+      }
+
+      getInterfaceDescriptor() {
+        return "";
+      }
+
+      getCallingPid() {
+        return REQUEST_VALUE;
+      }
+
+      getCallingUid() {
+        return REQUEST_VALUE;
+      }
+
+      attachLocalInterface(localInterface, descriptor) {
+      }
+    }
+
+   export default class ServiceExtAbility extends ServiceExtensionAbility {
+     onCreate(want) {
+       console.info(TAG, `onCreate, want: ${want.abilityName}`);
+     }
+
+     onRequest(want, startId) {
+       console.info(TAG, `onRequest, want: ${want.abilityName}`);
+       try {
+            var requestCallback = dialogRequest.getRequestCallback(want);
+        } catch(err) {
+            console.error('getRequestInfo err= ${JSON.stringify(err)}');
+        }
+     }
+
+     onConnect(want) {
+       console.info(TAG, `onConnect, want: ${want.abilityName}`);
+       return new StubTest("test");
+     }
+
+     onDisconnect(want) {
+       console.info(TAG, `onDisconnect, want: ${want.abilityName}`);
+     }
+
+     onDestroy() {
+       console.info(TAG, `onDestroy`);
+     }
+   }
+   ```
+
+## RequestInfo
+
+表示发起方请求信息，作为窗口绑定模态弹框的入参。
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
+
+**示例：**
+
+```ts
+   import ServiceExtensionAbility from '@ohos.app.ability.ServiceExtensionAbility';
+   import rpc from '@ohos.rpc';
+   import dialogRequest from '@ohos.app.ability.dialogRequest';
+   import window from '@ohos.window';
+   
+   let TAG = "RequestInfoTest";
+
+   const REQUEST_VALUE = 1;
+
+    class StubTest extends rpc.RemoteObject {
+      constructor(des) {
+        super(des);
+      }
+
+      onRemoteRequest(code, data, reply, option) {
+        if (code === REQUEST_VALUE) {
+          let optFir = data.readInt();
+          let optSec = data.readInt();
+          reply.writeInt(optFir + optSec);
+        }
+        return true;
+      }
+
+      queryLocallInterface(descriptor) {
+        return null;
+      }
+
+      getInterfaceDescriptor() {
+        return "";
+      }
+
+      getCallingPid() {
+        return REQUEST_VALUE;
+      }
+
+      getCallingUid() {
+        return REQUEST_VALUE;
+      }
+
+      attachLocalInterface(localInterface, descriptor) {
+      }
+    }
+
+   export default class ServiceExtAbility extends ServiceExtensionAbility {
+     onCreate(want) {
+       console.info(TAG, `onCreate, want: ${want.abilityName}`);
+     }
+
+     onRequest(want, startId) {
+       console.info(TAG, `onRequest, want: ${want.abilityName}`);
+       try {
+            var requestInfo = dialogRequest.getRequestInfo(want);
+            window.bindDialogTarget(requestInfo, () => {
+                console.info('Dialog Window Need Destroy.');
+            }, (err) => {
+                if (err.code) {
+                    console.error('Failed to bind dialog target. Cause: ${JSON.stringify(err)}');
+                    return;
+                }
+                console.info('Succeeded in binding dialog target.');
+            });
+        } catch(err) {
+            console.error('getRequestInfo err= ${JSON.stringify(err)}');
+        }
+     }
+
+     onConnect(want) {
+       console.info(TAG, `onConnect, want: ${want.abilityName}`);
+        return new StubTest("test");
+
+     }
+
+     onDisconnect(want) {
+       console.info(TAG, `onDisconnect, want: ${want.abilityName}`);
+     }
+
+     onDestroy() {
+       console.info(TAG, `onDestroy`);
+     }
+   }
+   ```
+
+## ResultCode
+
+模态弹框请求结果码。
+
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
+
+| 参数名      | 值          | 说明     |
+| ------------ | ------------------ | ---------------------- |
+| RESULT_OK            | 0          | 表示成功。          |
+| RESULT_CANCEL        | 1          | 表示失败。          |
+
+## RequestResult
+模态弹框请求结果，当前只包含结果码，即RequestResult只当前只有ResultCode这一个成员。
+
+## 属性
+
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
+
+| 名称 | 类型 | 可读 | 可写 | 说明 |
+| -------- | -------- | -------- | -------- | -------- |
+| result | [ResultCode](#resultcode) | 是 | 是 | 表示结果码。 |
+
+## RequestCallback
+
+用于设置模态弹框请求结果的callback接口。
+
+### RequestCallback.setRequestResult
+
+setRequestResult(result: RequestResult): void;
+
+设置请求结果
+
+**系统能力**：SystemCapability.Ability.AbilityRuntime.Core
+
+**参数：**
+
+| 参数名 | 类型 | 必填 | 说明 |
+| -------- | -------- | -------- | -------- |
+| result | [RequestResult](#requestresult) | 是 | 模态弹框请求结果信息。 |
+
+**错误码：**
+
+| 错误码ID | 错误信息 |
+| ------- | -------------------------------- |
+| 401 | If the input parameter is not valid parameter. |
+
+以上错误码详细介绍请参考[errcode-ability](../errorcodes/errorcode-ability.md)。
+
+**示例：**
+
+```ts
+   import ServiceExtensionAbility from '@ohos.app.ability.ServiceExtensionAbility';
+   import rpc from '@ohos.rpc';
+   import dialogRequest from '@ohos.app.ability.dialogRequest';
+   
+   let TAG = "setRequestResultTest";
+
+      const REQUEST_VALUE = 1;
+
+    class StubTest extends rpc.RemoteObject {
+      constructor(des) {
+        super(des);
+      }
+
+      onRemoteRequest(code, data, reply, option) {
+        if (code === REQUEST_VALUE) {
+          let optFir = data.readInt();
+          let optSec = data.readInt();
+          reply.writeInt(optFir + optSec);
+        }
+        return true;
+      }
+
+      queryLocallInterface(descriptor) {
+        return null;
+      }
+
+      getInterfaceDescriptor() {
+        return "";
+      }
+
+      getCallingPid() {
+        return REQUEST_VALUE;
+      }
+
+      getCallingUid() {
+        return REQUEST_VALUE;
+      }
+
+      attachLocalInterface(localInterface, descriptor) {
+      }
+    }
+
+   export default class ServiceExtAbility extends ServiceExtensionAbility {
+     onCreate(want) {
+       console.info(TAG, `onCreate, want: ${want.abilityName}`);
+     }
+
+     onRequest(want, startId) {
+       console.info(TAG, `onRequest, want: ${want.abilityName}`);
+       try {
+            var requestCallback = dialogRequest.getRequestCallback(want);
+            let myResult = {
+                result : dialogRequest.ResultCode.RESULT_CANCEL,
+            };
+            requestCallback.setRequestResult(myResult);
+        } catch(err) {
+            console.error('getRequestInfo err= ${JSON.stringify(err)}');
+        }
+     }
+
+     onConnect(want) {
+       console.info(TAG, `onConnect, want: ${want.abilityName}`);
+        return new StubTest("test");
+     }
+
+     onDisconnect(want) {
+       console.info(TAG, `onDisconnect, want: ${want.abilityName}`);
+     }
+
+     onDestroy() {
+       console.info(TAG, `onDestroy`);
+     }
+   }
   ```
\ No newline at end of file
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-environmentCallback.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-environmentCallback.md
index a2cdfc3ff1838c2f3478f31506f728817e05c7e8..30c22393795cdfa76bab709957183ac067ab534e 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-environmentCallback.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-environmentCallback.md
@@ -45,9 +45,8 @@ onMemoryLevel(level: AbilityConstant.MemoryLevel): void;
 
 **示例：**
     
-
-  ```ts
-import UIAbility from '@ohos.app.ability.UIAbility';
+```ts
+import UIAbility from '@ohos.app.ability.Ability';
 
 let callbackId;
 
@@ -57,8 +56,9 @@ export default class MyAbility extends UIAbility {
         globalThis.applicationContext = this.context.getApplicationContext();
         let EnvironmentCallback  =  {
             onConfigurationUpdated(config){
-                console.log('onConfigurationUpdated config:' + JSON.stringify(config));
+                console.log(`onConfigurationUpdated config: ${JSON.stringify(config)}`);
             },
+
             onMemoryLevel(level){
                 console.log('onMemoryLevel level: ${JSON.stringify(level)}');
             }
@@ -76,4 +76,4 @@ export default class MyAbility extends UIAbility {
         });
     }
 }
-  ```
\ No newline at end of file
+```
\ No newline at end of file
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-missionManager.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-missionManager.md
index f286413f94252d60efe4fa96e52907ea651fd277..15ea77ce7f550451bc76c3e92500762d137baba1 100755
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-missionManager.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-missionManager.md
@@ -3,7 +3,7 @@
 missionManager模块提供系统任务管理能力，包括对系统任务执行锁定、解锁、清理、切换到前台等操作。
 
 > **说明：**
-> 
+>
 > 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
 
 ## 导入模块
@@ -20,7 +20,7 @@ ohos.permission.MANAGE_MISSIONS
 
 on(type:'mission', listener: MissionListener): number;
 
-注册系统任务状态监听。
+注册系统任务状态监听器。
 
 **需要权限**：ohos.permission.MANAGE_MISSIONS
 
@@ -32,13 +32,13 @@ on(type:'mission', listener: MissionListener): number;
 
   | 参数名 | 类型 | 必填 | 说明 |
   | -------- | -------- | -------- | -------- |
-  | listener | [MissionListener](js-apis-inner-application-missionListener.md) | 是 | 系统任务监听方法。 |
+  | listener | [MissionListener](js-apis-inner-application-missionListener.md) | 是 | 系统任务监听器。 |
 
 **返回值：**
 
   | 类型 | 说明 |
   | -------- | -------- |
-  | number | 监听方法的index值，由系统创建，在注册系统任务状态监听时分配，和监听方法一一对应&nbsp;。 |
+  | number | 监听器的index值，由系统创建，在注册系统任务状态监听时分配，和监听器一一对应&nbsp;。 |
 
 **示例：**
 
@@ -107,7 +107,7 @@ export default class EntryAbility extends UIAbility {
 
 off(type: 'mission', listenerId: number, callback: AsyncCallback&lt;void&gt;): void;
 
-取消任务状态监听。
+解注册任务状态监听器。
 
 **需要权限**：ohos.permission.MANAGE_MISSIONS
 
@@ -119,7 +119,7 @@ off(type: 'mission', listenerId: number, callback: AsyncCallback&lt;void&gt;): v
 
   | 参数名 | 类型 | 必填 | 说明 |
   | -------- | -------- | -------- | -------- |
-  | listenerId | number | 是 | 系统任务状态监听方法的index值，和监听方法一一对应，由registerMissionListener方法返回。 |
+  | listenerId | number | 是 | 系统任务状态监器法的index值，和监听器一一对应，由on方法返回。 |
   | callback | AsyncCallback&lt;void&gt; | 是 | 执行结果回调函数。 |
 
 **错误码**：
@@ -197,7 +197,7 @@ export default class EntryAbility extends UIAbility {
 
 off(type: 'mission', listenerId: number): Promise&lt;void&gt;;
 
-取消任务状态监听，以promise方式返回执行结果。
+解注册任务状态监听，以promise方式返回执行结果。
 
 **需要权限**：ohos.permission.MANAGE_MISSIONS
 
@@ -209,14 +209,14 @@ off(type: 'mission', listenerId: number): Promise&lt;void&gt;;
 
   | 参数名 | 类型 | 必填 | 说明 |
   | -------- | -------- | -------- | -------- |
-  | listenerId | number | 是 | 系统任务状态监听方法的index值，和监听方法一一对应，由registerMissionListener方法返回。 |
+  | listenerId | number | 是 | 系统任务状态监听器的index值，和监听器一一对应，由on方法返回。 |
 
 **返回值：**
 
-  | 类型 | 说明 | 
+  | 类型 | 说明 |
   | -------- | -------- |
-  | Promise&lt;void&gt; | promise方式返回执行结果。 | 
-  
+  | Promise&lt;void&gt; | promise方式返回执行结果。 |
+
 **错误码**：
 
 | 错误码ID | 错误信息 |
@@ -311,24 +311,35 @@ getMissionInfo(deviceId: string, missionId: number, callback: AsyncCallback&lt;M
 **示例：**
 
   ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
+    import missionManager from '@ohos.app.ability.missionManager';
 
-  try {
-    let allMissions=missionManager.getMissionInfos('',10).catch(function(err){console.log(err);});
-      missionManager.getMissionInfo('', allMissions[0].missionId, (error, mission) => {
-        console.log('getMissionInfo is called, error.code = ' + error.code);
-        console.log('mission.missionId = ' + mission.missionId);
-        console.log('mission.runningState = ' + mission.runningState);
-        console.log('mission.lockedState = ' + mission.lockedState);
-        console.log('mission.timestamp = ' + mission.timestamp);
-        console.log('mission.label = ' + mission.label);
-        console.log('mission.iconPath = ' + mission.iconPath);
-      });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
+    let testMissionId = 1;
 
+    missionManager.getMissionInfos('',10)
+    .then((allMissions) => {
+        try {
+        if (allMissions && allMissions.length > 0) {
+            testMissionId = allMissions[0].missionId;
+        }
+
+        missionManager.getMissionInfo('', testMissionId, (error, mission) => {
+            if (error) {
+            console.error('getMissionInfo failed, error.code: ${error.code}, error.message: ${error.message}');
+            } else {
+            console.log('mission.missionId = ${mission.missionId}');
+            console.log('mission.runningState = ${mission.runningState}');
+            console.log('mission.lockedState = ${mission.lockedState}');
+            console.log('mission.timestamp = ${mission.timestamp}');
+            console.log('mission.label = ${mission.label}');
+            console.log('mission.iconPath = ${mission.iconPath}');
+            }
+        });
+        } catch (paramError) {
+        console.error('error.code: ${paramError.code}, error.message: ${paramError.message}');
+        }
+    })
+    .catch(function(err){console.log(err);});
+  ```
 
 ## missionManager.getMissionInfo
 
@@ -357,18 +368,20 @@ getMissionInfo(deviceId: string, missionId: number): Promise&lt;MissionInfo&gt;;
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  try {
-    let mission = missionManager.getMissionInfo('', 10).catch(function (err){
-      console.log(err);
+let testMissionId = 1;
+try {
+    missionManager.getMissionInfo('', testMissionId).then((data) => {
+        console.info('getMissionInfo successfully. Data: ${JSON.stringify(data)}');
+    }).catch(error => {
+        console.error('getMissionInfo failed. Cause: ${error.message}');
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
-
+} catch (error) {
+    console.error('getMissionInfo failed. Cause: ${error.message}');
+}
+```
 
 ## missionManager.getMissionInfos
 
@@ -397,12 +410,15 @@ getMissionInfos(deviceId: string, numMax: number, callback: AsyncCallback&lt;Arr
 
   try {
     missionManager.getMissionInfos('', 10, (error, missions) => {
-      console.log('getMissionInfos is called, error.code = ' + error.code);
-      console.log('size = ' + missions.length);
-      console.log('missions = ' + JSON.stringify(missions));
+      if (error) {
+          console.error('getMissionInfos failed, error.code: ${error.code}, error.message: ${error.message}');
+      } else {
+        console.log('size = ${missions.length}');
+        console.log('missions = ${JSON.stringify(missions)}');
+      }
     });
   } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
+    console.error('error: ${paramError.code}, ${paramError.message}');
   }
   ```
 
@@ -434,18 +450,19 @@ getMissionInfos(deviceId: string, numMax: number): Promise&lt;Array&lt;MissionIn
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  try {
-    let allMissions = missionManager.getMissionInfos('', 10).catch(function (err){
-      console.log(err);
+try {
+    missionManager.getMissionInfos('', 10).then((data) => {
+        console.info('getMissionInfos successfully. Data: ${JSON.stringify(data)}');
+    }).catch(error => {
+        console.error('getMissionInfos failed. Cause: ${error.message}');
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
-
+} catch (error) {
+    console.error('getMissionInfos failed. Cause: ${error.message}');
+}
+```
 
 ## missionManager.getMissionSnapShot
 
@@ -468,27 +485,22 @@ getMissionSnapShot(deviceId: string, missionId: number, callback: AsyncCallback&
   | callback | AsyncCallback&lt;[MissionSnapshot](js-apis-inner-application-missionSnapshot.md)&gt; | 是 | 执行结果回调函数，返回任务快照信息。 |
 
 **示例：**
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
-
-  try {
-    missionManager.getMissionInfos('', 10, (error, missions) => {
-      console.log('getMissionInfos is called, error.code = ' + error.code);
-      console.log('size = ' + missions.length);
-      console.log('missions = ' + JSON.stringify(missions));
-      let id = missions[0].missionId;
-
-      missionManager.getMissionSnapShot('', id, (error, snapshot) => {
-  	    console.log('getMissionSnapShot is called, error.code = ' + error.code);
-  	    console.log('bundleName = ' + snapshot.ability.bundleName);
-      });
+let testMissionId = 2;
+try {
+    missionManager.getMissionSnapShot('', testMissionId, (err, data) => {
+        if (err) {
+            console.error('getMissionSnapShot failed: ${err.message}');
+        } else {
+            console.info('getMissionSnapShot successfully: ${JSON.stringify(data)}');
+        }
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
-
+} catch (err) {
+    console.error('getMissionSnapShot failed: ${err.message}');
+}
+```
 
 ## missionManager.getMissionSnapShot
 
@@ -516,32 +528,26 @@ getMissionSnapShot(deviceId: string, missionId: number): Promise&lt;MissionSnaps
   | Promise&lt;[MissionSnapshot](js-apis-inner-application-missionSnapshot.md)&gt; | 任务快照信息。 |
 
 **示例：**
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
-
-  try {
-    let allMissions;
-    missionManager.getMissionInfos('',10).then(function(res){
-      allMissions=res;
-      }).catch(function(err){console.log(err);});
-      console.log('size = ' + allMissions.length);
-      console.log('missions = ' + JSON.stringify(allMissions));
-      let id = allMissions[0].missionId;
-
-      let snapshot = missionManager.getMissionSnapShot('', id).catch(function (err){
-        console.log(err);
-      });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
+let testMissionId = 2;
+try {
+    missionManager.getMissionSnapShot('', testMissionId).then((data) => {
+        console.info('getMissionSnapShot successfully. Data: ${JSON.stringify(data)}');
+    }).catch(error => {
+        console.error('getMissionSnapShot failed. Cause: ${error.message}');
+    });
+} catch (error) {
+    console.error('getMissionSnapShot failed. Cause: ${error.message}');
+}
+```
 
 ## missionManager.getLowResolutionMissionSnapShot
 
 getLowResolutionMissionSnapShot(deviceId: string, missionId: number, callback: AsyncCallback\<MissionSnapshot>): void;
 
-使用给定的任务ID获取任务低分辨率快照。
+获取任务低分辨率快照。
 
 **需要权限**：ohos.permission.MANAGE_MISSIONS
 
@@ -558,33 +564,28 @@ getLowResolutionMissionSnapShot(deviceId: string, missionId: number, callback: A
   | callback | AsyncCallback&lt;[MissionSnapshot](js-apis-inner-application-missionSnapshot.md)&gt; | 是 | 执行结果回调函数，返回任务快照信息。 |
 
 **示例：**
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
-
-  try {
-    missionManager.getMissionInfos('', 10, (error, missions) => {
-      console.log('getMissionInfos is called, error.code = ' + error.code);
-      console.log('size = ' + missions.length);
-      console.log('missions = ' + JSON.stringify(missions));
-      let id = missions[0].missionId;
-
-      missionManager.getLowResolutionMissionSnapShot('', id, (error, snapshot) => {
-  	    console.log('getLowResolutionMissionSnapShot is called, error.code = ' + error.code);
-  	    console.log('bundleName = ' + snapshot.ability.bundleName);
-      });
+let testMissionId = 2;
+try {
+    missionManager.getLowResolutionMissionSnapShot('', testMissionId, (err, data) => {
+        if (err) {
+            console.error('getLowResolutionMissionSnapShot failed: ${err.message}');
+        } else {
+            console.info('getLowResolutionMissionSnapShot successfully: ${JSON.stringify(data)}');
+        }
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
-
+} catch (err) {
+    console.error('getLowResolutionMissionSnapShot failed: ${err.message}');
+}
+```
 
 ## missionManager.getLowResolutionMissionSnapShot
 
 getLowResolutionMissionSnapShot(deviceId: string, missionId: number): Promise\<MissionSnapshot>;
 
-使用给定的任务ID获取任务低分辨率快照。
+获取任务低分辨率快照。
 
 **需要权限**：ohos.permission.MANAGE_MISSIONS
 
@@ -607,25 +608,20 @@ getLowResolutionMissionSnapShot(deviceId: string, missionId: number): Promise\<M
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  try {
-    let allMissions;
-    missionManager.getMissionInfos('',10).then(function(res){
-      allMissions=res;
-      }).catch(function(err){console.log(err);});
-      console.log('size = ' + allMissions.length);
-      console.log('missions = ' + JSON.stringify(allMissions));
-      let id = allMissions[0].missionId;
-
-      let snapshot = missionManager.getLowResolutionMissionSnapShot('', id).catch(function (err){
-        console.log(err);
-      });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
+let testMissionId = 2;
+try {
+    missionManager.getLowResolutionMissionSnapShot('', testMissionId).then((data) => {
+        console.info('getLowResolutionMissionSnapShot successfully. Data: ${JSON.stringify(data)}');
+    }).catch(error => {
+        console.error('getLowResolutionMissionSnapShot failed. Cause: ${error.message}');
+    });
+} catch (error) {
+    console.error('getLowResolutionMissionSnapShot failed. Cause: ${error.message}');
+}
+```
 
 
 ## missionManager.lockMission
@@ -657,25 +653,22 @@ lockMission(missionId: number, callback: AsyncCallback&lt;void&gt;): void;
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  try {
-    missionManager.getMissionInfos('', 10, (error, missions) => {
-      console.log('getMissionInfos is called, error.code = ' + error.code);
-      console.log('size = ' + missions.length);
-      console.log('missions = ' + JSON.stringify(missions));
-      let id = missions[0].missionId;
-
-      missionManager.lockMission(id).then(() => {
-  	    console.log('lockMission is called ');
-      });
+let testMissionId = 2;
+try {
+    missionManager.lockMission(testMissionId, (err, data) => {
+        if (err) {
+            console.error('lockMission failed: ${err.message}');
+        } else {
+            console.info('lockMission successfully: ${JSON.stringify(data)}');
+        }
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
-
+} catch (err) {
+    console.error('lockMission failed: ${err.message}');
+}
+```
 
 ## missionManager.lockMission
 
@@ -697,9 +690,9 @@ lockMission(missionId: number): Promise&lt;void&gt;;
 
 **返回值：**
 
-  | 类型 | 说明 | 
+  | 类型 | 说明 |
   | -------- | -------- |
-  | Promise&lt;void&gt; | promise方式返回执行结果。 | 
+  | Promise&lt;void&gt; | promise方式返回执行结果。 |
 
 **错误码**：
 
@@ -710,27 +703,20 @@ lockMission(missionId: number): Promise&lt;void&gt;;
 以上错误码详细介绍请参考[errcode-ability](../errorcodes/errorcode-ability.md)。
 
 **示例：**
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
-  
-  try {
-    let allMissions;
-    missionManager.getMissionInfos('',10).then(function(res){
-      allMissions=res;
-    }).catch(function(err){console.log(err);});
-    console.log('size = ' + allMissions.length);
-    console.log('missions = ' + JSON.stringify(allMissions));
-    let id = allMissions[0].missionId;
-
-    missionManager.lockMission(id).catch(function (err){
-      console.log(err);
+let testMissionId = 2;
+try {
+    missionManager.lockMission(testMissionId).then((data) => {
+        console.info('lockMission successfully. Data: ${JSON.stringify(data)}');
+    }).catch(error => {
+        console.error('lockMission failed. Cause: ${error.message}');
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
-
+} catch (error) {
+    console.error('lockMission failed. Cause: ${error.message}');
+}
+```
 
 ## missionManager.unlockMission
 
@@ -760,26 +746,22 @@ unlockMission(missionId: number, callback: AsyncCallback&lt;void&gt;): void;
 以上错误码详细介绍请参考[errcode-ability](../errorcodes/errorcode-ability.md)。
 
 **示例：**
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
-
-  try {
-    missionManager.getMissionInfos('', 10, (error, missions) => {
-      console.log('getMissionInfos is called, error.code = ' + error.code);
-      console.log('size = ' + missions.length);
-      console.log('missions = ' + JSON.stringify(missions));
-      let id = missions[0].missionId;
-
-      missionManager.unlockMission(id).then(() => {
-  	    console.log('unlockMission is called ');
-      });
+let testMissionId = 2;
+try {
+    missionManager.unlockMission(testMissionId, (err, data) => {
+        if (err) {
+            console.error('unlockMission failed: ${err.message}');
+        } else {
+            console.info('unlockMission successfully: ${JSON.stringify(data)}');
+        }
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
-
+} catch (err) {
+    console.error('unlockMission failed: ${err.message}');
+}
+```
 
 ## missionManager.unlockMission
 
@@ -801,9 +783,9 @@ unlockMission(missionId: number): Promise&lt;void&gt;;
 
 **返回值：**
 
-  | 类型 | 说明 | 
+  | 类型 | 说明 |
   | -------- | -------- |
-  | Promise&lt;void&gt; | promise方式返回执行结果。 | 
+  | Promise&lt;void&gt; | promise方式返回执行结果。 |
 
 **错误码**：
 
@@ -815,29 +797,20 @@ unlockMission(missionId: number): Promise&lt;void&gt;;
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  try {
-    let allMissions;
-    missionManager.getMissionInfos('',10).then(function(res){
-      allMissions=res;
-    }).catch(function(err){console.log(err);});
-    console.log('size = ' + allMissions.length);
-    console.log('missions = ' + JSON.stringify(allMissions));
-    let id = allMissions[0].missionId;
-
-    missionManager.lockMission(id).catch(function (err){
-      console.log(err);
-    });
-    missionManager.unlockMission(id).catch(function (err){
-      console.log(err);
+let testMissionId = 2;
+try {
+    missionManager.unlockMission(testMissionId).then((data) => {
+        console.info('unlockMission successfully. Data: ${JSON.stringify(data)}');
+    }).catch(error => {
+        console.error('unlockMission failed. Cause: ${error.message}');
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
-
+} catch (error) {
+    console.error('unlockMission failed. Cause: ${error.message}');
+}
+```
 
 ## missionManager.clearMission
 
@@ -860,24 +833,22 @@ clearMission(missionId: number, callback: AsyncCallback&lt;void&gt;): void;
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  try {
-    missionManager.getMissionInfos('', 10, (error, missions) => {
-      console.log('getMissionInfos is called, error.code = ' + error.code);
-      console.log('size = ' + missions.length);
-      console.log('missions = ' + JSON.stringify(missions));
-      let id = missions[0].missionId;
-
-      missionManager.clearMission(id).then(() => {
-  	    console.log('clearMission is called ');
-      });
+let testMissionId = 2;
+try {
+    missionManager.clearMission(testMissionId, (err, data) => {
+        if (err) {
+            console.error('clearMission failed: ${err.message}');
+        } else {
+            console.info('clearMission successfully: ${JSON.stringify(data)}');
+        }
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
+} catch (err) {
+    console.error('clearMission failed: ${err.message}');
+}
+```
 
 
 ## missionManager.clearMission
@@ -900,32 +871,26 @@ clearMission(missionId: number): Promise&lt;void&gt;;
 
 **返回值：**
 
-  | 类型 | 说明 | 
+  | 类型 | 说明 |
   | -------- | -------- |
-  | Promise&lt;void&gt; | promise方式返回执行结果。 | 
+  | Promise&lt;void&gt; | promise方式返回执行结果。 |
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  try {
-    let allMissions;
-    missionManager.getMissionInfos('',10).then(function(res){
-      allMissions=res;
-    }).catch(function(err){console.log(err);});
-    console.log('size = ' + allMissions.length);
-    console.log('missions = ' + JSON.stringify(allMissions));
-    let id = allMissions[0].missionId;
-
-    missionManager.clearMission(id).catch(function (err){
-      console.log(err);
+let testMissionId = 2;
+try {
+    missionManager.clearMission(testMissionId).then((data) => {
+        console.info('clearMission successfully. Data: ${JSON.stringify(data)}');
+    }).catch(error => {
+        console.error('clearMission failed. Cause: ${error.message}');
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
-
+} catch (error) {
+    console.error('clearMission failed. Cause: ${error.message}');
+}
+```
 
 ## missionManager.clearAllMissions
 
@@ -941,14 +906,21 @@ clearAllMissions(callback: AsyncCallback&lt;void&gt;): void;
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
-
-  missionManager.clearAllMissions().then(() => {
-    console.log('clearAllMissions is called ');
-  });
-  ```
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
+try {
+    missionManager.clearAllMissions(err => {
+        if (err) {
+            console.error('clearAllMissions failed: ${err.message}');
+        } else {
+            console.info('clearAllMissions successfully.');
+        }
+    });
+} catch (err) {
+    console.error('clearAllMissions failed: ${err.message}');
+}
+```
 
 ## missionManager.clearAllMissions
 
@@ -964,19 +936,25 @@ clearAllMissions(): Promise&lt;void&gt;;
 
 **返回值：**
 
-  | 类型 | 说明 | 
+  | 类型 | 说明 |
   | -------- | -------- |
-  | Promise&lt;void&gt; | promise方式返回执行结果。 | 
+  | Promise&lt;void&gt; | promise方式返回执行结果。 |
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
-  missionManager.clearAllMissions().catch(function (err){
-    console.log(err);
-  });
-  ```
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
+try {
+    missionManager.clearAllMissions(bundleName).then((data) => {
+        console.info('clearAllMissions successfully. Data: ${JSON.stringify(data)}');
+    }).catch(err => {
+        console.error('clearAllMissions failed: ${err.message}');
+    });
+} catch (err) {
+    console.error('clearAllMissions failed: ${err.message}');
+}
+```
 
 ## missionManager.moveMissionToFront
 
@@ -1007,25 +985,22 @@ moveMissionToFront(missionId: number, callback: AsyncCallback&lt;void&gt;): void
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  try {
-    missionManager.getMissionInfos('', 10, (error, missions) => {
-      console.log('getMissionInfos is called, error.code = ' + error.code);
-      console.log('size = ' + missions.length);
-      console.log('missions = ' + JSON.stringify(missions));
-      let id = missions[0].missionId;
-
-      missionManager.moveMissionToFront(id).then(() => {
-  	    console.log('moveMissionToFront is called ');
-      });
+let testMissionId = 2;
+try {
+    missionManager.moveMissionToFront(testMissionId, (err, data) => {
+        if (err) {
+            console.error('moveMissionToFront failed: ${err.message}');
+        } else {
+            console.info('moveMissionToFront successfully: ${JSON.stringify(data)}');
+        }
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
-
+} catch (err) {
+    console.error('moveMissionToFront failed: ${err.message}');
+}
+```
 
 ## missionManager.moveMissionToFront
 
@@ -1057,25 +1032,22 @@ moveMissionToFront(missionId: number, options: StartOptions, callback: AsyncCall
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  try {
-    missionManager.getMissionInfos('', 10, (error, missions) => {
-      console.log('getMissionInfos is called, error.code = ' + error.code);
-      console.log('size = ' + missions.length);
-      console.log('missions = ' + JSON.stringify(missions));
-      let id = missions[0].missionId;
-
-      missionManager.moveMissionToFront(id,{windowMode : 101}).then(() => {
-  	    console.log('moveMissionToFront is called ');
-      });
+let testMissionId = 2;
+try {
+    missionManager.moveMissionToFront(testMissionId, {windowMode : 101}, (err, data) => {
+        if (err) {
+            console.error('moveMissionToFront failed: ${err.message}');
+        } else {
+            console.info('moveMissionToFront successfully: ${JSON.stringify(data)}');
+        }
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
-
+} catch (err) {
+    console.error('moveMissionToFront failed: ${err.message}');
+}
+```
 
 ## missionManager.moveMissionToFront
 
@@ -1098,9 +1070,9 @@ moveMissionToFront(missionId: number, options?: StartOptions): Promise&lt;void&g
 
 **返回值：**
 
-  | 类型 | 说明 | 
+  | 类型 | 说明 |
   | -------- | -------- |
-  | Promise&lt;void&gt; | promise方式返回执行结果。 | 
+  | Promise&lt;void&gt; | promise方式返回执行结果。 |
 
 **错误码**：
 
@@ -1112,22 +1084,17 @@ moveMissionToFront(missionId: number, options?: StartOptions): Promise&lt;void&g
 
 **示例：**
 
-  ```ts
-  import missionManager from '@ohos.app.ability.missionManager';
+```ts
+import missionManager from '@ohos.app.ability.missionManager';
 
-  try {
-    let allMissions;
-    missionManager.getMissionInfos('',10).then(function(res){
-      allMissions=res;
-    }).catch(function(err){console.log(err);});
-    console.log('size = ' + allMissions.length);
-    console.log('missions = ' + JSON.stringify(allMissions));
-    let id = allMissions[0].missionId;
-
-    missionManager.moveMissionToFront(id).catch(function (err){
-      console.log(err);
+let testMissionId = 2;
+try {
+    missionManager.moveMissionToFront(testMissionId).then((data) => {
+        console.info('moveMissionToFront successfully. Data: ${JSON.stringify(data)}');
+    }).catch(error => {
+        console.error('moveMissionToFront failed. Cause: ${error.message}');
     });
-  } catch (paramError) {
-    console.log('error: ' + paramError.code + ', ' + paramError.message);
-  }
-  ```
+} catch (error) {
+    console.error('moveMissionToFront failed. Cause: ${error.message}');
+}
+```
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-quickFixManager.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-quickFixManager.md
index a5dbda2be0287469bf70272d220244dd53c51dfd..9fa29082f82282102960433b5578f7874bba724b 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-quickFixManager.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-quickFixManager.md
@@ -66,10 +66,10 @@ applyQuickFix(hapModuleQuickFixFiles: Array\<string>, callback: AsyncCallback\<v
 
 | 错误码ID | 错误信息 |
 | ------- | -------- |
-| 18500002 | Copy file failed, maybe not exist or inaccessible. |
+| 18500002 | The specified quick fix is invalid. It may not exist or inaccessible. |
 | 18500008 | Internal error. |
 
-在打补丁过程中发生的错误，其错误码及错误信息通过公共事件[COMMON_EVENT_QUICK_FIX_APPLY_RESULT](commonEvent-definitions.md#common_event_quick_fix_apply_result9)的参数返回给应用开发者。这部分错误码及错误信息如下：
+在打补丁过程中发生的错误，其错误码及错误信息通过公共事件[COMMON_EVENT_QUICK_FIX_APPLY_RESULT](commonEventManager-definitions.md#common_event_quick_fix_apply_result-9)的参数返回给应用开发者。这部分错误码及错误信息如下：
 
 | 错误码ID | 错误信息 |
 | ------- | -------- |
@@ -130,10 +130,10 @@ applyQuickFix(hapModuleQuickFixFiles: Array\<string>): Promise\<void>;
 
 | 错误码ID | 错误信息 |
 | ------- | -------- |
-| 18500002 | Copy file failed, maybe not exist or inaccessible. |
+| 18500002 | The specified quick fix is invalid. It may not exist or inaccessible. |
 | 18500008 | Internal error. |
 
-在打补丁过程中发生的错误，其错误码及错误信息通过公共事件[COMMON_EVENT_QUICK_FIX_APPLY_RESULT](commonEvent-definitions.md#common_event_quick_fix_apply_result9)的参数返回给应用开发者。这部分错误码及错误信息如下：
+在打补丁过程中发生的错误，其错误码及错误信息通过公共事件[COMMON_EVENT_QUICK_FIX_APPLY_RESULT](commonEventManager-definitions.md#common_event_quick_fix_apply_result-9)的参数返回给应用开发者。这部分错误码及错误信息如下：
 
 | 错误码ID | 错误信息 |
 | ------- | -------- |
@@ -185,7 +185,7 @@ getApplicationQuickFixInfo(bundleName: string, callback: AsyncCallback\<Applicat
 
 | 错误码ID | 错误信息 |
 | ------- | -------- |
-| 18500001 | The bundle is not exist. |
+| 18500001 | The specified bundleName is invalid. |
 | 18500008 | Internal error. |
 
 以上错误码详细介绍请参考[errcode-ability](../errorcodes/errorcode-ability.md)。
@@ -237,7 +237,7 @@ getApplicationQuickFixInfo(bundleName: string): Promise\<ApplicationQuickFixInfo
 
 | 错误码ID | 错误信息 |
 | ------- | -------- |
-| 18500001 | The bundle is not exist. |
+| 18500001 | The specified bundleName is invalid. |
 | 18500008 | Internal error. |
 
 以上错误码详细介绍请参考[errcode-ability](../errorcodes/errorcode-ability.md)。
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-startOptions.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-startOptions.md
index 8ea09e71638fb2c82e31f9329c1bceead1d2ba13..9b44db635fed0cc7dafde728b7ef9e75f9740781 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-startOptions.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-startOptions.md
@@ -15,11 +15,8 @@ import StartOptions from '@ohos.app.ability.StartOptions';
 
 ## 属性
 
-
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Ability.AbilityRuntime.Core
 
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
 | [windowMode](js-apis-app-ability-abilityConstant.md#abilityconstantwindowmode) | number | 否 | 窗口模式。 |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-uiAbility.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-uiAbility.md
index 84026b35b88ed985ba1651ac73ddaee2b257685e..7484361d91f4b74e3e28c0d10920feef11a664b4 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-uiAbility.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-uiAbility.md
@@ -333,7 +333,7 @@ call(method: string, data: rpc.Parcelable): Promise&lt;void&gt;;
 | ------- | -------------------------------- |
 | 16200001 | Caller released. The caller has been released. |
 | 16200002 | Callee invalid. The callee does not exist. |
-| 16000050 | Internal Error. |
+| 16000050 | Internal error. |
 
 以上错误码详细介绍请参考[errcode-ability](../errorcodes/errorcode-ability.md)。
 
@@ -416,7 +416,7 @@ callWithResult(method: string, data: rpc.Parcelable): Promise&lt;rpc.MessageSequ
 | ------- | -------------------------------- |
 | 16200001 | Caller released. The caller has been released. |
 | 16200002 | Callee invalid. The callee does not exist. |
-| 16000050 | Internal Error. |
+| 16000050 | Internal error. |
 
 以上错误码详细介绍请参考[errcode-ability](../errorcodes/errorcode-ability.md)。
 
@@ -569,7 +569,7 @@ release(): void;
 
 ## Caller.on
 
- on(type: 'release', callback: OnReleaseCallback): void;
+on(type: 'release', callback: OnReleaseCallback): void;
 
 注册通用组件服务端Stub（桩）断开监听通知。
 
@@ -586,6 +586,7 @@ release(): void;
 
 | 错误码ID | 错误信息 |
 | ------- | -------------------------------- |
+| 401 | If the input parameter is not valid parameter. |
 | 16200001 | Caller released. The caller has been released. |
 
 以上错误码详细介绍请参考[errcode-ability](../errorcodes/errorcode-ability.md)。
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-want.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-want.md
index ba737871aa6fb6434745828b4c551e6cf9cdae51..ed1f79a844932c02dbb5ef4cecfc355dc7400c86 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-want.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-want.md
@@ -26,7 +26,7 @@ import Want from '@ohos.app.ability.Want';
 | entities | Array\<string> | 否 | 表示目标Ability额外的类别信息（如：浏览器、视频播放器）。在隐式Want中是对action字段的补充。在隐式Want中，您可以定义该字段，来过滤匹配Ability类型。 |
 | uri | string | 否 | 表示携带的数据，一般配合type使用，指明待处理的数据类型。如果在Want中指定了uri，则Want将匹配指定的Uri信息，包括`scheme`、`schemeSpecificPart`、`authority`和`path`信息。 |
 | type | string | 否 | 表示MIME type类型描述，打开文件的类型，主要用于文管打开文件。比如：'text/xml' 、 'image/*'等，MIME定义请参见https://www.iana.org/assignments/media-types/media-types.xhtml?utm_source=ld246.com。 |
-| parameters   | {[key: string]: any} | 否   | 表示WantParams描述，由开发者自行决定传入的键值对。默认会携带以下key值：<br />- ohos.aafwk.callerPid：表示拉起方的pid。<br />- ohos.aafwk.param.callerBundleName：表示拉起方的Bundle Name。<br />- ohos.aafwk.param.callerToken：表示拉起方的token。<br />- ohos.aafwk.param.callerUid：表示[BundleInfo](js-apis-bundleManager-bundleInfo.md#bundleinfo-1)中的uid，应用包里应用程序的uid。<br />- component.startup.newRules：表示是否启用新的管控规则。<br />- moduleName：表示拉起方的模块名，该字段的值即使定义成其他字符串，在传递到另一端时会被修改为正确的值。<br />- ohos.dlp.params.sandbox：表示dlp文件才会有。 |
+| parameters   | {[key: string]: any} | 否   | 表示WantParams描述，由开发者自行决定传入的键值对。默认会携带以下key值：<br />- ohos.aafwk.callerPid：表示拉起方的pid。<br />- ohos.aafwk.param.callerBundleName：表示拉起方的Bundle Name。<br />- ohos.aafwk.param.callerToken：表示拉起方的token。<br />- ohos.aafwk.param.callerUid：表示[BundleInfo](js-apis-bundleManager-bundleInfo.md#bundleinfo-1)中的uid，应用包里应用程序的uid。<br />- component.startup.newRules：表示是否启用新的管控规则。<br />- moduleName：表示拉起方的模块名，该字段的值即使定义成其他字符串，在传递到另一端时会被修改为正确的值。<br />- ohos.dlp.params.sandbox：表示dlp文件才会有。<br />- ability.params.backToOtherMissionStack：表示是否支持跨任务链返回。 |
 | [flags](js-apis-ability-wantConstant.md#wantconstantflags) | number | 否 | 表示处理Want的方式。默认传数字。<br />例如通过wantConstant.Flags.FLAG_ABILITY_CONTINUATION表示是否以设备间迁移方式启动Ability。 |
 
 **示例：**
@@ -34,7 +34,8 @@ import Want from '@ohos.app.ability.Want';
 - 基础用法：在UIAbility对象中调用，示例中的context的获取方式请参见[获取UIAbility的上下文信息](../../application-models/uiability-usage.md#获取uiability的上下文信息)。
 
   ```ts
-  let context = ...; // UIAbilityContext
+  import common from '@ohos.app.ability.common';
+  let context = getContext(this) as common.UIAbilityContext; // UIAbilityContext
   let want = {
     'deviceId': '', // deviceId为空表示本设备
     'bundleName': 'com.example.myapplication',
@@ -52,7 +53,8 @@ import Want from '@ohos.app.ability.Want';
 
     * 字符串（String）
         ```ts
-        let context = ...; // UIAbilityContext
+        import common from '@ohos.app.ability.common';
+        let context = getContext(this) as common.UIAbilityContext; // UIAbilityContext
         let want = {
           bundleName: 'com.example.myapplication',
           abilityName: 'FuncAbility',
@@ -67,7 +69,8 @@ import Want from '@ohos.app.ability.Want';
         ```
     * 数字（Number）
         ```ts
-        let context = ...; // UIAbilityContext
+        import common from '@ohos.app.ability.common';
+        let context = getContext(this) as common.UIAbilityContext; // UIAbilityContext
         let want = {
           bundleName: 'com.example.myapplication',
           abilityName: 'FuncAbility',
@@ -83,7 +86,8 @@ import Want from '@ohos.app.ability.Want';
         ```
     * 布尔（Boolean）
         ```ts
-        let context = ...; // UIAbilityContext
+        import common from '@ohos.app.ability.common';
+        let context = getContext(this) as common.UIAbilityContext; // UIAbilityContext
         let want = {
           bundleName: 'com.example.myapplication',
           abilityName: 'FuncAbility',
@@ -98,7 +102,8 @@ import Want from '@ohos.app.ability.Want';
         ```
     * 对象（Object）
         ```ts
-        let context = ...; // UIAbilityContext
+        import common from '@ohos.app.ability.common';
+        let context = getContext(this) as common.UIAbilityContext; // UIAbilityContext
         let want = {
           bundleName: 'com.example.myapplication',
           abilityName: 'FuncAbility',
@@ -118,7 +123,8 @@ import Want from '@ohos.app.ability.Want';
         ```
     * 数组（Array）
         ```ts
-        let context = ...; // UIAbilityContext
+        import common from '@ohos.app.ability.common';
+        let context = getContext(this) as common.UIAbilityContext; // UIAbilityContext
         let want = {
           bundleName: 'com.example.myapplication',
           abilityName: 'FuncAbility',
@@ -138,7 +144,8 @@ import Want from '@ohos.app.ability.Want';
         ```ts
         import fs from '@ohos.file.fs';
         
-        let context = ...; // UIAbilityContext
+        import common from '@ohos.app.ability.common';
+        let context = getContext(this) as common.UIAbilityContext; // UIAbilityContext
         
         let fd;
         try {
@@ -160,3 +167,33 @@ import Want from '@ohos.app.ability.Want';
           console.error(`Failed to startAbility. Code: ${err.code}, message: ${err.message}`);
         });
         ```
+    - parameter参数用法：以ability.params.backToOtherMissionStack为例，ServiceExtension在拉起UIAbility的时候，可以支持跨任务链返回。
+
+    ```ts
+        // (1) UIAbility1启动一个ServiceExtension
+        let context = getContext(this) as common.UIAbilityContext; // UIAbilityContext
+        let want = {
+          bundleName: 'com.example.myapplication1',
+          abilityName: 'ServiceExtensionAbility',
+        };
+
+        context.startAbility(want, (err) => {
+          console.error(`Failed to startAbility. Code: ${err.code}, message: ${err.message}`);
+        });
+
+        // (2) 该ServiceExtension去启动另一个UIAbility2，并在启动的时候携带参数ability.params.backToOtherMissionStack为true
+        let context = ...; // ServiceExtensionContext
+        let want = {
+          bundleName: 'com.example.myapplication2',
+          abilityName: 'MainAbility',
+          parameters: {
+            "ability.params.backToOtherMissionStack": true,
+          },
+        };
+
+        context.startAbility(want, (err) => {
+          console.error(`Failed to startAbility. Code: ${err.code}, message: ${err.message}`);
+        });
+    ```
+
+    说明：上例中，如果ServiceExtension启动UIAbility2时不携带ability.params.backToOtherMissionStack参数，或者携带的ability.params.backToOtherMissionStack参数为false，则UIAbility1和UIAbility2不在同一个任务栈里面，在UIAbility2的界面点back键，不会回到UIAbility1的界面。如果携带的ability.params.backToOtherMissionStack参数为true，则表示支持跨任务链返回，此时在UIAbility2的界面点back键，会回到UIAbility1的界面。
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-wantAgent.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-wantAgent.md
index 59a9a8ba62d55c30f68c08ee137d4a9b3b329493..73551d324aa13221207c1e8148e634cf24d9791b 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-wantAgent.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-wantAgent.md
@@ -113,10 +113,8 @@ getWantAgent(info: WantAgentInfo): Promise\<WantAgent\>
 
 **示例：**
 
-```js
-import WantAgent from '@ohos.app.ability.wantAgent';
-
-
+```ts
+let wantAgent;
 //WantAgentInfo对象
 let wantAgentInfo = {
     wants: [
@@ -1126,6 +1124,27 @@ let wantAgentInfo = {
     wantAgentFlags:[WantAgent.WantAgentFlags.UPDATE_PRESENT_FLAG]
 };
 
+//getWantAgent回调
+function getWantAgentCallback(err, data) {
+    if (err === undefined) {
+        wantAgent = data;
+    } else {
+        console.error('getWantAgent failed ${JSON.stringify(wantAgent)}');
+    }
+    //getOperationTypeCallback回调
+    function getOperationTypeCallback(err, data) {
+        if(err) {
+            console.error('getOperationType failed! ${err.code} ${err.message}');
+        } else {
+            console.info('getOperationType ok! ${JSON.stringify(data)}');
+        }
+    }
+    try {
+        WantAgent.getOperationType(wantAgent, getOperationTypeCallback);
+    } catch(err) {
+        console.error('getOperationTypeCallback failed! ${err.code} ${err.message}');
+    }
+}
 try {
     WantAgent.getWantAgent(wantAgentInfo).then((data) => {
 	    console.info('==========================>getWantAgentCallback=======================>');
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-ability-wantConstant.md b/zh-cn/application-dev/reference/apis/js-apis-app-ability-wantConstant.md
index 9ca76cf932e991e28451e43ee08069e97683f29f..10db9966d492c895425c21cbe242ce029ba7cbfc 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-ability-wantConstant.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-ability-wantConstant.md
@@ -18,14 +18,14 @@ want操作的常数。
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Ability.AbilityBase
 
-| 名称      | 值          | 说明     |
-| ------------ | ------------------ | ---------------------- |
-|   DLP_PARAMS_SANDBOX    |ohos.dlp.params.sandbox  | 指示沙盒标志的参数的操作。<br>**系统API**：该接口为系统接口，三方应用不支持调用。  |
-|   DLP_PARAMS_BUNDLE_NAME    |ohos.dlp.params.bundleName  |指示DLP包名称的参数的操作。 <br>**系统API**：该接口为系统接口，三方应用不支持调用。  |
-|   DLP_PARAMS_MODULE_NAME    |ohos.dlp.params.moduleName      |指示DLP模块名称的参数的操作。 <br>**系统API**：该接口为系统接口，三方应用不支持调用。  |
-|   DLP_PARAMS_ABILITY_NAME   |ohos.dlp.params.abilityName      |指示DLP能力名称的参数的操作。 <br>**系统API**：该接口为系统接口，三方应用不支持调用。  |
-|   DLP_PARAMS_INDEX    |ohos.dlp.params.index      |指示DLP索引参数的操作。 <br>**系统API**：该接口为系统接口，三方应用不支持调用。  |
-|   ABILITY_BACK_TO_OTHER_MISSION_STACK    |ability.params.backToOtherMissionStack      |表示该Ability能返回到其它任务栈中。  |
+| 名称                    | 值                                 | 说明                                                                           |
+| ----------------------- | ---------------------------------- | ------------------------------------------------------------------------------ |
+| DLP_PARAMS_SANDBOX      | ohos.dlp.params.sandbox            | 指示沙盒标志的参数的操作。<br>**系统API**：该接口为系统接口，三方应用不支持调用。 |
+| DLP_PARAMS_BUNDLE_NAME  | ohos.dlp.params.bundleName         | 指示DLP Bundle名称的参数的操作。 <br>**系统API**：该接口为系统接口，三方应用不支持调用。 |
+| DLP_PARAMS_MODULE_NAME  | ohos.dlp.params.moduleName         | 指示DLP模块名称的参数的操作。 <br>**系统API**：该接口为系统接口，三方应用不支持调用。 |
+| DLP_PARAMS_ABILITY_NAME | ohos.dlp.params.abilityName        | 指示DLP能力名称的参数的操作。 <br>**系统API**：该接口为系统接口，三方应用不支持调用。 |
+| DLP_PARAMS_INDEX        | ohos.dlp.params.index              | 指示DLP索引参数的操作。 <br>**系统API**：该接口为系统接口，三方应用不支持调用。 |
+| ABILITY_BACK_TO_OTHER_MISSION_STACK   | ability.params.backToOtherMissionStack     | 表示是否支持跨任务链返回。 <br>**系统API**：该接口为系统接口，三方应用不支持调用。 |
 
 ## wantConstant.Flags
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-form-formHost.md b/zh-cn/application-dev/reference/apis/js-apis-app-form-formHost.md
index 512a4ccefcfceae3d8190572e3c5dcaa18adc124..4c8035b511985f000ce09c01a578503fc5ebc3bb 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-form-formHost.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-form-formHost.md
@@ -35,14 +35,15 @@ deleteForm(formId: string, callback: AsyncCallback&lt;void&gt;): void
 | 错误码ID | 错误信息 |
 | -------- | -------- |
 | 201 | Permissions denied. |
+| 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
 | 16500050 | An IPC connection error happened. |
 | 16500060 | A service connection error happened, please try again later. |
-| 202 | The application is not a system application. |
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -97,7 +98,8 @@ deleteForm(formId: string): Promise&lt;void&gt;
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **参数：**
 
@@ -143,7 +145,8 @@ releaseForm(formId: string, callback: AsyncCallback&lt;void&gt;): void
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -190,7 +193,8 @@ releaseForm(formId: string, isReleaseCache: boolean, callback: AsyncCallback&lt;
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -242,7 +246,8 @@ releaseForm(formId: string, isReleaseCache?: boolean): Promise&lt;void&gt;
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -288,7 +293,8 @@ requestForm(formId: string, callback: AsyncCallback&lt;void&gt;): void
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -339,7 +345,8 @@ requestForm(formId: string): Promise&lt;void&gt;
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -386,7 +393,8 @@ castToNormalForm(formId: string, callback: AsyncCallback&lt;void&gt;): void
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501002 | The number of forms exceeds upper bound. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -437,7 +445,8 @@ castToNormalForm(formId: string): Promise&lt;void&gt;
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501002 | The number of forms exceeds upper bound. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -481,7 +490,8 @@ notifyVisibleForms(formIds: Array&lt;string&gt;, callback: AsyncCallback&lt;void
 | 16500050 | An IPC connection error happened. |
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -530,7 +540,8 @@ notifyVisibleForms(formIds: Array&lt;string&gt;): Promise&lt;void&gt;
 | 16500050 | An IPC connection error happened. |
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -574,7 +585,8 @@ notifyInvisibleForms(formIds: Array&lt;string&gt;, callback: AsyncCallback&lt;vo
 | 16500050 | An IPC connection error happened. |
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -623,7 +635,8 @@ notifyInvisibleForms(formIds: Array&lt;string&gt;): Promise&lt;void&gt;
 | 16500050 | An IPC connection error happened. |
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -668,7 +681,8 @@ enableFormsUpdate(formIds: Array&lt;string&gt;, callback: AsyncCallback&lt;void&
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -718,7 +732,8 @@ enableFormsUpdate(formIds: Array&lt;string&gt;): Promise&lt;void&gt;
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -764,7 +779,8 @@ disableFormsUpdate(formIds: Array&lt;string&gt;, callback: AsyncCallback&lt;void
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -815,7 +831,8 @@ disableFormsUpdate(formIds: Array&lt;string&gt;): Promise&lt;void&gt;
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -852,7 +869,8 @@ isSystemReady(callback: AsyncCallback&lt;void&gt;): void
 | -------- | -------- |
 | 202 | The application is not a system application.   |
 | 401 | If the input parameter is not valid parameter. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -888,7 +906,8 @@ isSystemReady(): Promise&lt;void&gt;
 | 错误码ID | 错误信息 |
 | -------- | -------- |
 | 202 | The application is not a system application.   |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -925,7 +944,8 @@ getAllFormsInfo(callback: AsyncCallback&lt;Array&lt;formInfo.FormInfo&gt;&gt;):
 | 16500050 | An IPC connection error happened. |
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **参数：**
 
@@ -968,7 +988,8 @@ getAllFormsInfo(): Promise&lt;Array&lt;formInfo.FormInfo&gt;&gt;
 | 16500050 | An IPC connection error happened. |
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **返回值：**
 
@@ -1018,7 +1039,8 @@ getFormsInfo(bundleName: string, callback: AsyncCallback&lt;Array&lt;formInfo.Fo
 | 16500060 | A service connection error happened, please try again later. |
 | 16500100 | Failed to obtain the configuration information. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1065,7 +1087,8 @@ getFormsInfo(bundleName: string, moduleName: string, callback: AsyncCallback&lt;
 | 16500060 | A service connection error happened, please try again later. |
 | 16500100 | Failed to obtain the configuration information. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1117,7 +1140,8 @@ getFormsInfo(bundleName: string, moduleName?: string): Promise&lt;Array&lt;formI
 | 16500060 | A service connection error happened, please try again later. |
 | 16500100 | Failed to obtain the configuration information. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1160,7 +1184,8 @@ deleteInvalidForms(formIds: Array&lt;string&gt;, callback: AsyncCallback&lt;numb
 | 16500050 | An IPC connection error happened. |
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1211,7 +1236,8 @@ deleteInvalidForms(formIds: Array&lt;string&gt;): Promise&lt;number&gt;
 | 16500050 | An IPC connection error happened. |
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1256,7 +1282,8 @@ acquireFormState(want: Want, callback: AsyncCallback&lt;formInfo.FormStateInfo&g
 | 16500060 | A service connection error happened, please try again later. |
 | 16500100 | Failed to obtain the configuration information. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1317,7 +1344,8 @@ acquireFormState(want: Want): Promise&lt;formInfo.FormStateInfo&gt;
 | 16500060 | A service connection error happened, please try again later. |
 | 16500100 | Failed to obtain the configuration information. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1364,7 +1392,8 @@ on(type: 'formUninstall', callback: Callback&lt;string&gt;): void
 | -------- | -------- |
 | 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1396,7 +1425,8 @@ off(type: 'formUninstall', callback?: Callback&lt;string&gt;): void
 | -------- | -------- |
 | 202 | The application is not a system application. |
 | 401 | If the input parameter is not valid parameter. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1436,7 +1466,8 @@ notifyFormsVisible(formIds: Array&lt;string&gt;, isVisible: boolean, callback: A
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1487,7 +1518,8 @@ notifyFormsVisible(formIds: Array&lt;string&gt;, isVisible: boolean): Promise&lt
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1533,7 +1565,8 @@ notifyFormsEnableUpdate(formIds: Array&lt;string&gt;, isEnableUpdate: boolean, c
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1584,7 +1617,8 @@ notifyFormsEnableUpdate(formIds: Array&lt;string&gt;, isEnableUpdate: boolean):
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1629,7 +1663,8 @@ shareForm(formId: string, deviceId: string, callback: AsyncCallback&lt;void&gt;)
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1681,7 +1716,8 @@ shareForm(formId: string, deviceId: string): Promise&lt;void&gt;
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **参数：**
 
@@ -1725,7 +1761,8 @@ notifyFormsPrivacyProtected(formIds: Array\<string>, isProtected: boolean, callb
 | 16500050 | An IPC connection error happened. |
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
-| 以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。 |                    |
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -1746,7 +1783,7 @@ try {
 
 ## notifyFormsPrivacyProtected
 
-function notifyFormsPrivacyProtected(formIds: Array\<string\>, isProtected: boolean): Promise\<void\>;
+notifyFormsPrivacyProtected(formIds: Array\<string\>, isProtected: boolean): Promise\<void\>;
 
 通知指定卡片隐私保护状态改变。使用Promise异步回调。
 
@@ -1777,7 +1814,8 @@ function notifyFormsPrivacyProtected(formIds: Array\<string\>, isProtected: bool
 | 16500050 | An IPC connection error happened. |
 | 16500060 | A service connection error happened, please try again later. |
 | 16501000 | An internal functional error occurred. |
-| 以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。 |                    |
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 ```ts
 import formHost from '@ohos.app.form.formHost';
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-form-formInfo.md b/zh-cn/application-dev/reference/apis/js-apis-app-form-formInfo.md
index a2f7519881456edc5f171b9b7b26173a88ce5bb4..b71e342a70aed62b586e02d5b7e9ea2721645944 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-form-formInfo.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-form-formInfo.md
@@ -18,6 +18,8 @@ import formInfo from '@ohos.app.form.formInfo';
 
 **系统能力**：SystemCapability.Ability.Form
 
+**系统API**: 此接口为系统接口，三方应用不支持调用。
+
 | 名称        | 类型                 | 可读    | 可写    | 说明                                                         |
 | ----------- | -------- | -------- | -------------------- | ------------------------------------------------------------ |
 | bundleName  | string               | 是    | 否     | 卡片所属包的包名。                           |
@@ -136,5 +138,6 @@ import formInfo from '@ohos.app.form.formInfo';
 
 | 名称        |  值   | 说明         |
 | ----------- | ---- | ------------ |
+| UNKNOWN | 0   | 表示卡片为未知。 |
 | FORM_VISIBLE | 1   | 表示卡片为可见。 |
 | FORM_INVISIBLE   | 2   | 表示卡片为不可见。 |
\ No newline at end of file
diff --git a/zh-cn/application-dev/reference/apis/js-apis-app-form-formProvider.md b/zh-cn/application-dev/reference/apis/js-apis-app-form-formProvider.md
index 56ceccaa5cff96e8e3d086d7f6c8a496161cf3be..fb4d1c26673c4b1666f8bb1d3e759f851434f679 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-app-form-formProvider.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-app-form-formProvider.md
@@ -39,7 +39,8 @@ setFormNextRefreshTime(formId: string, minute: number, callback: AsyncCallback&l
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501002 | The number of forms exceeds upper bound. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -91,7 +92,8 @@ setFormNextRefreshTime(formId: string, minute: number): Promise&lt;void&gt;
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501002 | The number of forms exceeds upper bound. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -135,12 +137,14 @@ updateForm(formId: string, formBindingData: formBindingData.FormBindingData,call
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
 ```ts
-import formBindingData from '@ohos.application.formBindingData';
+import formBindingData from '@ohos.app.form.formBindingData';
+
 var formId = '12400633174999288';
 try {
   let obj = formBindingData.createFormBindingData({temperature:'22c', time:'22:00'});
@@ -188,14 +192,16 @@ updateForm(formId: string, formBindingData: formBindingData.FormBindingData): Pr
 | 16501000 | An internal functional error occurred. |
 | 16501001 | The ID of the form to be operated does not exist. |
 | 16501003 | The form can not be operated by the current application. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
 ```ts
-import formBindingData from '@ohos.application.formBindingData';
-var formId = '12400633174999288';
-let obj = formBindingData.createFormBindingData({temperature:'22c', time:'22:00'});
+import formBindingData from '@ohos.app.form.formBindingData';
+
+let formId = '12400633174999288';
+let obj = formBindingData.createFormBindingData({ temperature: '22c', time: '22:00' });
 try {
   formProvider.updateForm(formId, obj).then(() => {
       console.log('formProvider updateForm success');
@@ -228,7 +234,8 @@ getFormsInfo(callback: AsyncCallback&lt;Array&lt;formInfo.FormInfo&gt;&gt;): voi
 | 16500050 | An IPC connection error happened. |
 | 16500100 | Failed to obtain the configuration information. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 
 **示例：**
@@ -269,7 +276,8 @@ getFormsInfo(filter: formInfo.FormInfoFilter, callback: AsyncCallback&lt;Array&l
 | 16500050 | An IPC connection error happened. |
 | 16500100 | Failed to obtain the configuration information. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -321,7 +329,8 @@ getFormsInfo(filter?: formInfo.FormInfoFilter): Promise&lt;Array&lt;formInfo.For
 | 16500050 | An IPC connection error happened. |
 | 16500100 | Failed to obtain the configuration information. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -370,13 +379,15 @@ requestPublishForm(want: Want, formBindingData: formBindingData.FormBindingData,
 | 16500050 | An IPC connection error happened. |
 | 16500100 | Failed to obtain the configuration information. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
 ```ts
-import formBindingData from '@ohos.application.formBindingData';
-var want = {
+import formBindingData from '@ohos.app.form.formBindingData';
+
+let want = {
   abilityName: 'FormAbility',
   parameters: {
     'ohos.extra.param.key.form_dimension': 2,
@@ -424,12 +435,13 @@ requestPublishForm(want: Want, callback: AsyncCallback&lt;string&gt;): void
 | 16500050 | An IPC connection error happened. |
 | 16500100 | Failed to obtain the configuration information. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
 ```ts
-var want = {
+let want = {
   abilityName: 'FormAbility',
   parameters: {
     'ohos.extra.param.key.form_dimension': 2,
@@ -483,12 +495,13 @@ requestPublishForm(want: Want, formBindingData?: formBindingData.FormBindingData
 | 16500050 | An IPC connection error happened. |
 | 16500100 | Failed to obtain the configuration information. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
 ```ts
-var want = {
+let want = {
   abilityName: 'FormAbility',
   parameters: {
     'ohos.extra.param.key.form_dimension': 2,
@@ -531,7 +544,8 @@ isRequestPublishFormSupported(callback: AsyncCallback&lt;boolean&gt;): void
 | 401 | If the input parameter is not valid parameter. |
 | 16500050 | An IPC connection error happened. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
@@ -593,7 +607,8 @@ isRequestPublishFormSupported(): Promise&lt;boolean&gt;
 | 202 | The application is not a system application. |
 | 16500050 | An IPC connection error happened. |
 | 16501000 | An internal functional error occurred. |
-|以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。||
+
+以上错误码的详细介绍请参见[卡片错误码](../errorcodes/errorcode-form.md)。
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-application-appManager.md b/zh-cn/application-dev/reference/apis/js-apis-application-appManager.md
index 84ae31e59cba0c6443fc039acecaac5cd85b7217..7fb2ded431c2d6ce9b7d087025c00b9074714dba 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-application-appManager.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-application-appManager.md
@@ -389,7 +389,11 @@ killProcessWithAccount(bundleName: string, accountId: number): Promise\<void\>
 
 切断account进程（Promise形式）。
 
-**需要权限**：ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS, ohos.permission.CLEAN_BACKGROUND_PROCESSES
+> **说明：** 
+>
+> 当accountId为当前用户时，不需要校验ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS权限。
+
+**需要权限**：ohos.permission.CLEAN_BACKGROUND_PROCESSES，ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS
 
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Core
 
@@ -423,11 +427,15 @@ killProcessWithAccount(bundleName: string, accountId: number, callback: AsyncCal
 
 切断account进程（callback形式）。
 
+> **说明：** 
+>
+> 当accountId为当前用户时，不需要校验ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS权限。
+
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Core
 
 **系统API**: 此接口为系统接口，三方应用不支持调用。
 
-**需要权限**：ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS, ohos.permission.CLEAN_BACKGROUND_PROCESSES
+**需要权限**：ohos.permission.CLEAN_BACKGROUND_PROCESSES，ohos.permission.INTERACT_ACROSS_LOCAL_ACCOUNTS
 
 **参数：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-application-configuration.md b/zh-cn/application-dev/reference/apis/js-apis-application-configuration.md
index e499403a305dbf3cd82f24a7364ca0d3bcc7cc91..a65f8c5b6d52de57f8c9b66bb8d1eed88a424001 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-application-configuration.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-application-configuration.md
@@ -3,9 +3,16 @@
 定义环境变化信息。Configuration是接口定义，仅做字段声明。
 
 > **说明：**
+>
 > 本模块首批接口从API version 8开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
 > 本模块从API version 9废弃，替换模块为[@ohos.app.ability.Configuration (Configuration)](js-apis-app-ability-configuration.md)
 
+## 导入模块
+
+```ts
+import Configuration from '@ohos.app.application.Configuration';
+```
+
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Ability.AbilityBase
 
   | 名称 | 类型 | 可读 | 可写 | 说明 |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-batteryStatistics.md b/zh-cn/application-dev/reference/apis/js-apis-batteryStatistics.md
index 5de930534fc4eb5263a316ea122fa23c60820b8e..a91de5d9d68aa7659d7d85f24062f78300449ffc 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-batteryStatistics.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-batteryStatistics.md
@@ -36,7 +36,7 @@ getBatteryStats(): Promise<Array&lt;BatteryStatsInfo&gt;>
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4600101 | 连接服务失败。 |
+| 4600101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -72,7 +72,7 @@ getBatteryStats(callback: AsyncCallback<Array&lt;BatteryStatsInfo&gt;>): void
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4600101 | 连接服务失败。 |
+| 4600101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -114,7 +114,7 @@ getAppPowerValue(uid: number): number
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4600101 | 连接服务失败。 |
+| 4600101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -155,7 +155,7 @@ getAppPowerPercent(uid: number): number
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4600101 | 连接服务失败。 |
+| 4600101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -196,13 +196,13 @@ getHardwareUnitPowerValue(type: ConsumptionType): number
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4600101 | 连接服务失败。 |
+| 4600101 | If connecting to the service failed. |
 
 **示例：**
 
 ```js
 try {
-    var value = batteryStats.getHardwareUnitPowerValue(ConsumptionType.CONSUMPTION_TYPE_SCREEN);
+    var value = batteryStats.getHardwareUnitPowerValue(batteryStats.ConsumptionType.CONSUMPTION_TYPE_SCREEN);
     console.info('battery statistics value of hardware is: ' + value);
 } catch(err) {
     console.error('get battery statistics percent of hardware failed, err: ' + err);
@@ -237,13 +237,13 @@ getHardwareUnitPowerPercent(type: ConsumptionType): number
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4600101 | 连接服务失败。 |
+| 4600101 | If connecting to the service failed. |
 
 **示例：**
 
 ```js
 try {
-    var percent = batteryStats.getHardwareUnitPowerPercent(ConsumptionType.CONSUMPTION_TYPE_SCREEN);
+    var percent = batteryStats.getHardwareUnitPowerPercent(batteryStats.ConsumptionType.CONSUMPTION_TYPE_SCREEN);
     console.info('battery statistics percent of hardware is: ' + percent);
 } catch(err) {
     console.error('get battery statistics percent of hardware failed, err: ' + err);
diff --git a/zh-cn/application-dev/reference/apis/js-apis-bluetoothManager.md b/zh-cn/application-dev/reference/apis/js-apis-bluetoothManager.md
index 673a90540c0f1e82f1787f2a566d132192b480e5..fb54017d2ad0394fe5ae52160f9044d69fa4799f 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-bluetoothManager.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-bluetoothManager.md
@@ -893,7 +893,7 @@ try {
 
 on(type: "stateChange", callback: Callback&lt;BluetoothState&gt;): void
 
-订阅蓝牙连接状态改变事件。
+订阅蓝牙设备开关状态事件。
 
 **需要权限**：ohos.permission.USE_BLUETOOTH
 
@@ -932,7 +932,7 @@ try {
 
 off(type: "stateChange", callback?: Callback&lt;BluetoothState&gt;): void
 
-取消订阅蓝牙连接状态改变事件。
+取消订阅蓝牙设备开关状态事件。
 
 **需要权限**：ohos.permission.USE_BLUETOOTH
 
@@ -2075,7 +2075,7 @@ connect(device: string): void
 
 ```js
 try {
-    let hidHostProfile = bluetoothManager.getProfileInst(bluetoothManager.ProfileId.PROFILE_HID_HOST) as bluetoothManager.HidHostProfile;
+    let hidHostProfile = bluetoothManager.getProfileInstance(bluetoothManager.ProfileId.PROFILE_HID_HOST) as bluetoothManager.HidHostProfile;
     hidHostProfile.connect('XX:XX:XX:XX:XX:XX');
 } catch (err) {
     console.error("errCode:" + err.code + ",errMessage:" + err.message);
@@ -2116,7 +2116,7 @@ disconnect(device: string): void
 
 ```js
 try {
-    let hidHostProfile = bluetoothManager.getProfileInst(bluetoothManager.ProfileId.PROFILE_HID_HOST) as bluetoothManager.HidHostProfile;
+    let hidHostProfile = bluetoothManager.getProfileInstance(bluetoothManager.ProfileId.PROFILE_HID_HOST) as bluetoothManager.HidHostProfile;
     hidHostProfile.disconnect('XX:XX:XX:XX:XX:XX');
 } catch (err) {
     console.error("errCode:" + err.code + ",errMessage:" + err.message);
@@ -2145,7 +2145,7 @@ on(type: "connectionStateChange", callback: Callback&lt;[StateChangeParam](#Stat
 function onReceiveEvent(data) {
     console.info('hidHost state = '+ JSON.stringify(data));
 }
-let hidHost = bluetoothManager.getProfileInst(bluetoothManager.ProfileId.PROFILE_HID_HOST) as bluetoothManager.HidHostProfile;
+let hidHost = bluetoothManager.getProfileInstance(bluetoothManager.ProfileId.PROFILE_HID_HOST) as bluetoothManager.HidHostProfile;
 hidHost.on('connectionStateChange', onReceiveEvent);
 ```
 
@@ -2171,7 +2171,7 @@ off(type: "connectionStateChange", callback?: Callback&lt;[StateChangeParam](#St
 function onReceiveEvent(data) {
     console.info('hidHost state = '+ JSON.stringify(data));
 }
-let hidHost = bluetoothManager.getProfileInst(bluetoothManager.ProfileId.PROFILE_HID_HOST) as bluetoothManager.HidHostProfile;
+let hidHost = bluetoothManager.getProfileInstance(bluetoothManager.ProfileId.PROFILE_HID_HOST) as bluetoothManager.HidHostProfile;
 hidHost.on('connectionStateChange', onReceiveEvent);
 hidHost.off('connectionStateChange', onReceiveEvent);
 ```
@@ -2215,7 +2215,7 @@ disconnect(device: string): void
 
 ```js
 try {
-    let panProfile = bluetoothManager.getProfileInst(bluetoothManager.ProfileId.PROFILE_PAN_NETWORK) as bluetoothManager.PanProfile;
+    let panProfile = bluetoothManager.getProfileInstance(bluetoothManager.ProfileId.PROFILE_PAN_NETWORK) as bluetoothManager.PanProfile;
     panProfile.disconnect('XX:XX:XX:XX:XX:XX');
 } catch (err) {
     console.error("errCode:" + err.code + ",errMessage:" + err.message);
@@ -2244,7 +2244,7 @@ on(type: "connectionStateChange", callback: Callback&lt;[StateChangeParam](#Stat
 function onReceiveEvent(data) {
     console.info('pan state = '+ JSON.stringify(data));
 }
-let panProfile = bluetoothManager.getProfileInst(bluetoothManager.ProfileId.PROFILE_PAN_NETWORK) as bluetoothManager.PanProfile;
+let panProfile = bluetoothManager.getProfileInstance(bluetoothManager.ProfileId.PROFILE_PAN_NETWORK) as bluetoothManager.PanProfile;
 panProfile.on('connectionStateChange', onReceiveEvent);
 ```
 
@@ -2270,7 +2270,7 @@ off(type: "connectionStateChange", callback?: Callback&lt;[StateChangeParam](#St
 function onReceiveEvent(data) {
     console.info('pan state = '+ JSON.stringify(data));
 }
-let panProfile = bluetoothManager.getProfileInst(bluetoothManager.ProfileId.PROFILE_PAN_NETWORK) as bluetoothManager.PanProfile;
+let panProfile = bluetoothManager.getProfileInstance(bluetoothManager.ProfileId.PROFILE_PAN_NETWORK) as bluetoothManager.PanProfile;
 panProfile.on('connectionStateChange', onReceiveEvent);
 panProfile.off('connectionStateChange', onReceiveEvent);
 ```
@@ -2309,7 +2309,7 @@ setTethering(enable: boolean): void
 
 ```js
 try {
-    let panProfile = bluetoothManager.getProfileInst(bluetoothManager.ProfileId.PROFILE_PAN_NETWORK) as bluetoothManager.PanProfile;
+    let panProfile = bluetoothManager.getProfileInstance(bluetoothManager.ProfileId.PROFILE_PAN_NETWORK) as bluetoothManager.PanProfile;
     panProfile.setTethering(true);
 } catch (err) {
     console.error("errCode:" + err.code + ",errMessage:" + err.message);
@@ -2337,7 +2337,7 @@ isTetheringOn(): boolean
 
 ```js
 try {
-    let panProfile = bluetoothManager.getProfileInst(bluetoothManager.ProfileId.PROFILE_PAN_NETWORK) as bluetoothManager.PanProfile;
+    let panProfile = bluetoothManager.getProfileInstance(bluetoothManager.ProfileId.PROFILE_PAN_NETWORK) as bluetoothManager.PanProfile;
     let ret = panProfile.isTetheringOn();
 } catch (err) {
     console.error("errCode:" + err.code + ",errMessage:" + err.message);
diff --git a/zh-cn/application-dev/reference/apis/js-apis-brightness.md b/zh-cn/application-dev/reference/apis/js-apis-brightness.md
index 0bb0f2e7a8a0efe584d5df24483bed020c707cfc..12556adab48b360369a68406eb3c95335847598a 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-brightness.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-brightness.md
@@ -36,7 +36,7 @@ setValue(value: number): void
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4700101 | 连接服务失败。 |
+| 4700101 | If connecting to the service failed. |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-buffer.md b/zh-cn/application-dev/reference/apis/js-apis-buffer.md
index 5da74ef71ee217d044ec60848a891e7e7d9eebaa..9112f695d67576e86b4084aca9c00ec4c4a3ede7 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-buffer.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-buffer.md
@@ -872,7 +872,7 @@ let buf = buffer.from([0x63, 0x64, 0x65, 0x66, 0x67, 0x68, 0x69, 0x70,
 console.log(buf.readBigInt64BE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(8);
-let result = buf1.writeBigInt64BE(0x0102030405060708n, 0);
+let result = buf1.writeBigInt64BE(BigInt(0x0102030405060708), 0);
 ```
 
 ### readBigInt64LE
@@ -913,7 +913,7 @@ let buf = buffer.from([0x63, 0x64, 0x65, 0x66, 0x67, 0x68, 0x69, 0x70,
 console.log(buf.readBigInt64LE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(8);
-let result = buf1.writeBigInt64BE(0x0102030405060708n, 0);
+let result = buf1.writeBigInt64BE(BigInt(0x0102030405060708), 0);
 ```
 
 ### readBigUInt64BE
@@ -954,7 +954,7 @@ let buf = buffer.from([0x63, 0x64, 0x65, 0x66, 0x67, 0x68, 0x69, 0x70,
 console.log(buf.readBigUInt64BE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(8);
-let result = buf1.writeBigUInt64BE(0xdecafafecacefaden, 0);
+let result = buf1.writeBigUInt64BE(BigInt(0xdecafafecacefade), 0);
 ```
 
 ### readBigUInt64LE
@@ -995,7 +995,7 @@ let buf = buffer.from([0x63, 0x64, 0x65, 0x66, 0x67, 0x68, 0x69, 0x70,
 console.log(buf.readBigUInt64LE(0).toString());
 
 let buf1 = buffer.allocUninitializedFromPool(8);
-let result = buf1.writeBigUInt64BE(0xdecafafecacefaden, 0);
+let result = buf1.writeBigUInt64BE(BigInt(0xdecafafecacefade), 0);
 ```
 
 ### readDoubleBE
@@ -2045,7 +2045,7 @@ writeBigInt64BE(value: bigint, offset?: number): number
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-let result = buf.writeBigInt64BE(0x0102030405060708n, 0);
+let result = buf.writeBigInt64BE(BigInt(0x0102030405060708), 0);
 ```
 
 ### writeBigInt64LE
@@ -2084,7 +2084,7 @@ writeBigInt64LE(value: bigint, offset?: number): number
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-let result = buf.writeBigInt64LE(0x0102030405060708n, 0);
+let result = buf.writeBigInt64LE(BigInt(0x0102030405060708), 0);
 ```
 
 ### writeBigUInt64BE
@@ -2123,7 +2123,7 @@ writeBigUInt64BE(value: bigint, offset?: number): number
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-let result = buf.writeBigUInt64BE(0xdecafafecacefaden, 0);
+let result = buf.writeBigUInt64BE(BigInt(0xdecafafecacefade), 0);
 ```
 
 ### writeBigUInt64LE
@@ -2162,7 +2162,7 @@ writeBigUInt64LE(value: bigint, offset?: number): number
 import buffer from '@ohos.buffer';
 
 let buf = buffer.allocUninitializedFromPool(8);
-let result = buf.writeBigUInt64LE(0xdecafafecacefaden, 0);
+let result = buf.writeBigUInt64LE(BigInt(0xdecafafecacefade), 0);
 ```
 
 ### writeDoubleBE
diff --git a/zh-cn/application-dev/reference/apis/js-apis-call.md b/zh-cn/application-dev/reference/apis/js-apis-call.md
index 943762c74a0780dcbc88c5649fc5d9d1ca4d5a73..2dfc8797c5cf2f0ed6bccb3cf0c9a1d07c6d7bd2 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-call.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-call.md
@@ -117,7 +117,7 @@ dialCall\(phoneNumber: string, options?: DialCallOptions\): Promise<void\>
 | 参数名      |                 类型                | 必填 |                说明                    |
 | ----------- | ----------------------------------- | ---- | -------------------------------------- |
 | phoneNumber | string                              | 是   | 电话号码。                             |
-| options     | [DialCallOptions](#dialcalloptions9)| 否   | 通话参数，携带呼叫的其他配置信息。 |
+| options     | [DialCallOptions](#dialcalloptions9)| 否   | 通话参数，携带呼叫的其他配置信息。<br/>不填该参数则默认使用如下配置，参考[DialCallOptions](#dialcalloptions9)。<br/>- 帐户Id：卡槽1 <br/>- 音视频类型：语音通话 <br/>- 拨号场景：普通呼叫 <br/>- 拨号类型：运营商通话  |
 
 **返回值：**
 
@@ -919,7 +919,7 @@ answerCall(callId?: number\): Promise<void\>
 
 | 参数名 | 类型   | 必填 | 说明                                                         |
 | ------ | ------ | ---- | ------------------------------------------------------------ |
-| callId | number | 否   | 呼叫Id。可以通过订阅callDetailsChange事件获得。从API Version 9开始为可选参数。 |
+| callId | number | 否   | 呼叫Id。可以通过订阅callDetailsChange事件获得。从API Version 9开始为可选参数。<br/>不填该参数则接通最近一通正在响铃的来电。|
 
 **返回值：**
 
@@ -1048,7 +1048,7 @@ hangUpCall\(callId?: number\): Promise<void\>
 
 | 参数名 | 类型   | 必填 | 说明                                                         |
 | ------ | ------ | ---- | ------------------------------------------------------------ |
-| callId | number | 否   | 呼叫id。可以通过订阅callDetailsChange事件获得。从API Version 9开始为可选参数。 |
+| callId | number | 否   | 呼叫id。可以通过订阅callDetailsChange事件获得。从API Version 9开始为可选参数。</br>不填该参数则挂断最近一通正在进行/拨号/连接的通话。|
 
 **返回值：**
 
@@ -1224,8 +1224,8 @@ rejectCall(callId?: number, options?: RejectMessageOptions\): Promise<void\>
 
 | 参数名  | 类型                                           | 必填 | 说明                                                         |
 | ------- | ---------------------------------------------- | ---- | ------------------------------------------------------------ |
-| callId  | number                                         | 否   | 呼叫Id。可以通过订阅callDetailsChange事件获得。从API Version 9开始为可选参数。 |
-| options | [RejectMessageOptions](#rejectmessageoptions7) | 否   | 拒绝消息选项。                                               |
+| callId  | number                                         | 否   | 呼叫Id。可以通过订阅callDetailsChange事件获得。从API Version 9开始为可选参数。<br/>不填该参数则拒接最近一通正在响铃的来电。|
+| options | [RejectMessageOptions](#rejectmessageoptions7) | 否   | 拒绝消息选项。不填该参数则不会发送拒接短信。|
 
 **返回值：**
 
@@ -2544,7 +2544,7 @@ off\(type: 'callDetailsChange', callback?: Callback<CallAttributeOptions\>\): vo
 | 参数名   | 类型                                                     | 必填 | 说明                               |
 | -------- | -------------------------------------------------------- | ---- | ---------------------------------- |
 | type     | string                                                   | 是   | 通话结束时取消监听通话详情的变化，参数固定为'callDetailsChange'。 |
-| callback | Callback<[CallAttributeOptions](#callattributeoptions7)> | 否   | 回调函数。                         |
+| callback | Callback<[CallAttributeOptions](#callattributeoptions7)> | 否   | 回调函数。不填该参数将不会收到取消订阅的处理结果。 |
 
 **错误码：**
 
@@ -2584,7 +2584,7 @@ off\(type: 'callEventChange', callback?: Callback<CallEventOptions\>\): void
 | 参数名   | 类型                                             | 必填 | 说明                               |
 | -------- | ------------------------------------------------ | ---- | ---------------------------------- |
 | type     | string                                           | 是   | 通话结束时取消监听通话事件的变化，参数固定为'callEventChange'。 |
-| callback | Callback<[CallEventOptions](#calleventoptions8)> | 否   | 回调函数。                         |
+| callback | Callback<[CallEventOptions](#calleventoptions8)> | 否   | 回调函数。不填该参数将不会收到取消订阅的处理结果。 |
 
 **错误码：**
 
@@ -2624,7 +2624,7 @@ off\(type: 'callDisconnectedCause', callback?: Callback<DisconnectedDetails\>\):
 | 参数名   | 类型                                                       | 必填 | 说明                 |
 | -------- | ---------------------------------------------------------- | ---- | ------------------- |
 | type     | string                                                     | 是   | 调用断开连接的原因，参数固定为'callDisconnectedCause'。 |
-| callback | Callback<[DisconnectedDetails](#disconnecteddetails9)>     | 否   | 回调函数。           |
+| callback | Callback<[DisconnectedDetails](#disconnecteddetails9)>     | 否   | 回调函数。不填该参数将不会收到取消订阅的处理结果。 |
 
 **错误码：**
 
@@ -2664,7 +2664,7 @@ off\(type: 'mmiCodeResult', callback?: Callback<MmiCodeResults\>\): void
 | 参数名   | 类型                                              | 必填 | 说明        |
 | -------- | ------------------------------------------------ | ---- | ----------- |
 | type     | string                                           | 是   | MMI码结果，参数固定为'mmiCodeResult'。 |
-| callback | Callback<[MmiCodeResults](#mmicoderesults9)>     | 否   | 回调函数。  |
+| callback | Callback<[MmiCodeResults](#mmicoderesults9)>     | 否   | 回调函数。不填该参数将不会收到取消订阅的处理结果。 |
 
 **错误码：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-commonEvent.md b/zh-cn/application-dev/reference/apis/js-apis-commonEvent.md
index f00dba0881a96c34e812db65121c313b53dcc702..244557e6f78b5b5271fb74697235ff1297483f85 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-commonEvent.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-commonEvent.md
@@ -18,17 +18,20 @@ import CommonEvent from '@ohos.commonEvent';
 
 全部系统公共事件枚举定义请参见[系统公共事件定义](./commonEvent-definitions.md)。
 
-## CommonEvent.publish
+## CommonEvent.publish<sup>(deprecated)</sup>
 
 publish(event: string, callback: AsyncCallback\<void>): void
 
 发布公共事件（callback形式）。
 
-**系统能力：** SystemCapability.Notification.CommonEvent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[commonEventManager.publish](js-apis-commonEventManager.md#commoneventmanagerpublish)替代。
+
+**系统能力：** `SystemCapability.Notification.CommonEvent`
 
 **参数：**
 
-| 参数名     | 类型                 | 必填 | 说明                   |
+| 名称     | 类型                 | 必填 | 说明                   |
 | -------- | -------------------- | ---- | ---------------------- |
 | event    | string               | 是   | 表示要发送的公共事件。 |
 | callback | AsyncCallback\<void> | 是   | 表示被指定的回调方法。 |
@@ -49,23 +52,24 @@ function publishCallBack(err) {
 CommonEvent.publish("event", publishCallBack);
 ```
 
-
-
-## CommonEvent.publish
+## CommonEvent.publish<sup>(deprecated)</sup>
 
 publish(event: string, options: CommonEventPublishData, callback: AsyncCallback\<void>): void
 
 发布公共事件指定发布信息（callback形式）。
 
-**系统能力：** SystemCapability.Notification.CommonEvent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[commonEventManager.publish](js-apis-commonEventManager.md#commoneventmanagerpublish-1)替代。
+
+**系统能力：** `SystemCapability.Notification.CommonEvent`
 
 **参数：**
 
-| 参数名     | 类型                   | 必填 | 说明                   |
+| 名称     | 类型                   | 必填 | 说明                   |
 | -------- | ---------------------- | ---- | ---------------------- |
 | event    | string                 | 是   | 表示要发布的公共事件。  |
 | options  | [CommonEventPublishData](./js-apis-inner-commonEvent-commonEventPublishData.md) | 是   | 表示发布公共事件的属性。 |
-| callback | syncCallback\<void>   | 是   | 表示被指定的回调方法。  |
+| callback | AsyncCallback\<void>   | 是   | 表示被指定的回调方法。  |
 
 **示例：**
 
@@ -91,21 +95,22 @@ function publishCallBack(err) {
 CommonEvent.publish("event", options, publishCallBack);
 ```
 
-
-
-## CommonEvent.publishAsUser<sup>8+</sup>
+## CommonEvent.publishAsUser<sup>(deprecated)</sup>
 
 publishAsUser(event: string, userId: number, callback: AsyncCallback\<void>): void
 
 向指定用户发布公共事件（callback形式）。
 
-**系统能力：** SystemCapability.Notification.CommonEvent
+> **说明：**
+> 从 API version 8开始支持，从API version 9开始废弃。建议使用[commonEventManager.publishAsUser](js-apis-commonEventManager.md#commoneventmanagerpublishasuser)替代。
+
+**系统能力：** `SystemCapability.Notification.CommonEvent`
 
 **系统API**：此接口为系统接口，三方应用不支持调用。
 
 **参数：**
 
-| 参数名     | 类型                 | 必填 | 说明                               |
+| 名称     | 类型                 | 必填 | 说明                               |
 | -------- | -------------------- | ---- | ---------------------------------- |
 | event    | string               | 是   | 表示要发送的公共事件。             |
 | userId   | number               | 是   | 表示指定向该用户ID发送此公共事件。 |
@@ -130,21 +135,22 @@ let userId = 100;
 CommonEvent.publishAsUser("event", userId, publishAsUserCallBack);
 ```
 
-
-
-## CommonEvent.publishAsUser<sup>8+</sup>
+## CommonEvent.publishAsUser<sup>(deprecated)</sup>
 
 publishAsUser(event: string, userId: number, options: CommonEventPublishData, callback: AsyncCallback\<void>): void
 
 向指定用户发布公共事件并指定发布信息（callback形式）。
 
-**系统能力：** SystemCapability.Notification.CommonEvent
+> **说明：**
+> 从 API version 8开始支持，从API version 9开始废弃。建议使用[commonEventManager.publishAsUser](js-apis-commonEventManager.md#commoneventmanagerpublishasuser-1)替代。
+
+**系统能力：** `SystemCapability.Notification.CommonEvent`
 
 **系统API**：此接口为系统接口，三方应用不支持调用。
 
 **参数：**
 
-| 参数名     | 类型                   | 必填 | 说明                   |
+| 名称     | 类型                   | 必填 | 说明                   |
 | -------- | ---------------------- | ---- | ---------------------- |
 | event    | string                 | 是   | 表示要发布的公共事件。  |
 | userId   | number | 是 | 表示指定向该用户ID发送此公共事件。 |
@@ -177,19 +183,20 @@ let userId = 100;
 CommonEvent.publishAsUser("event", userId, options, publishAsUserCallBack);
 ```
 
+## CommonEvent.createSubscriber<sup>(deprecated)</sup>
 
-
-## CommonEvent.createSubscriber
-
-createSubscriber(subscribeInfo: CommonEventSubscribeInfo, callback: AsyncCallback\<CommonEventSubscriber>): void
+createSubscriber(subscribeInfo: CommonEventSubscribeInfo, callback: AsyncCallback<CommonEventSubscriber>): void
 
 创建订阅者（callback形式）。
 
-**系统能力：** SystemCapability.Notification.CommonEvent
+> **说明：** 
+>从 API version 7开始支持，从API version 9开始废弃。建议使用[commonEventManager.createSubscriber](js-apis-commonEventManager.md#commoneventmanagercreatesubscriber)替代。
+
+**系统能力：** `SystemCapability.Notification.CommonEvent`
 
 **参数：**
 
-| 参数名          | 类型                                                         | 必填 | 说明                       |
+| 名称          | 类型                                                         | 必填 | 说明                       |
 | ------------- | ------------------------------------------------------------ | ---- | -------------------------- |
 | subscribeInfo | [CommonEventSubscribeInfo](./js-apis-inner-commonEvent-commonEventSubscribeInfo.md)        | 是   | 表示订阅信息。             |
 | callback      | AsyncCallback\<[CommonEventSubscriber](./js-apis-inner-commonEvent-commonEventSubscriber.md)> | 是   | 表示创建订阅者的回调方法。 |
@@ -219,19 +226,20 @@ function createSubscriberCallBack(err, commonEventSubscriber) {
 CommonEvent.createSubscriber(subscribeInfo, createSubscriberCallBack);
 ```
 
+## CommonEvent.createSubscriber<sup>(deprecated)</sup>
 
-
-## CommonEvent.createSubscriber
-
-createSubscriber(subscribeInfo: CommonEventSubscribeInfo): Promise\<CommonEventSubscriber>
+createSubscriber(subscribeInfo: CommonEventSubscribeInfo): Promise<CommonEventSubscriber>
 
 创建订阅者（Promise形式）。
 
-**系统能力：** SystemCapability.Notification.CommonEvent
+> **说明：** 
+>从 API version 7开始支持，从API version 9开始废弃。建议使用[commonEventManager.createSubscriber](js-apis-commonEventManager.md#commoneventmanagercreatesubscriber-1)替代。
+
+**系统能力：** `SystemCapability.Notification.CommonEvent`
 
 **参数：**
 
-| 参数名          | 类型                                                  | 必填 | 说明           |
+| 名称          | 类型                                                  | 必填 | 说明           |
 | ------------- | ----------------------------------------------------- | ---- | -------------- |
 | subscribeInfo | [CommonEventSubscribeInfo](./js-apis-inner-commonEvent-commonEventSubscribeInfo.md) | 是   | 表示订阅信息。 |
 
@@ -259,19 +267,20 @@ CommonEvent.createSubscriber(subscribeInfo).then((commonEventSubscriber) => {
 });
 ```
 
+## CommonEvent.subscribe<sup>(deprecated)</sup>
 
-
-## CommonEvent.subscribe
-
-subscribe(subscriber: CommonEventSubscriber, callback: AsyncCallback\<CommonEventData>): void
+subscribe(subscriber: CommonEventSubscriber, callback: AsyncCallback<CommonEventData>): void
 
 订阅公共事件（callback形式）。
 
-**系统能力：** SystemCapability.Notification.CommonEvent
+> **说明：** 
+>从 API version 7开始支持，从API version 9开始废弃。建议使用[commonEventManager.subscribe](js-apis-commonEventManager.md#commoneventmanagersubscribe)替代。
+
+**系统能力：** `SystemCapability.Notification.CommonEvent`
 
 **参数：**
 
-| 参数名       | 类型                                                | 必填 | 说明                             |
+| 名称       | 类型                                                | 必填 | 说明                             |
 | ---------- | ---------------------------------------------------- | ---- | -------------------------------- |
 | subscriber | [CommonEventSubscriber](./js-apis-inner-commonEvent-commonEventSubscriber.md)     | 是   | 表示订阅者对象。                 |
 | callback   | AsyncCallback\<[CommonEventData](./js-apis-inner-commonEvent-commonEventData.md)> | 是   | 表示接收公共事件数据的回调函数。 |
@@ -311,19 +320,20 @@ function createSubscriberCallBack(err, commonEventSubscriber) {
 CommonEvent.createSubscriber(subscribeInfo, createSubscriberCallBack);
 ```
 
-
-
-## CommonEvent.unsubscribe
+## CommonEvent.unsubscribe<sup>(deprecated)</sup>
 
 unsubscribe(subscriber: CommonEventSubscriber, callback?: AsyncCallback\<void>): void
 
 取消订阅公共事件（callback形式）。
 
-**系统能力：** SystemCapability.Notification.CommonEvent
+> **说明：** 
+>从 API version 7开始支持，从API version 9开始废弃。建议使用[commonEventManager.subscribe](js-apis-commonEventManager.md#commoneventmanagerunsubscribe)替代。
+
+**系统能力：** `SystemCapability.Notification.CommonEvent`
 
 **参数：**
 
-| 参数名       | 类型                                             | 必填 | 说明                     |
+| 名称       | 类型                                             | 必填 | 说明                     |
 | ---------- | ----------------------------------------------- | ---- | ------------------------ |
 | subscriber | [CommonEventSubscriber](./js-apis-inner-commonEvent-commonEventSubscriber.md) | 是   | 表示订阅者对象。         |
 | callback   | AsyncCallback\<void>                            | 否   | 表示取消订阅的回调方法。 |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-commonEventManager.md b/zh-cn/application-dev/reference/apis/js-apis-commonEventManager.md
index 9e5d04a63a5b975b00a6bc146ed15cce718554a6..af38e26e67855d594d6c17d3225bf1c80c7b4f13 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-commonEventManager.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-commonEventManager.md
@@ -45,7 +45,6 @@ publish(event: string, callback: AsyncCallback\<void>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401  | The parameter check failed.             |
 | 1500004  | not System services.                |
 | 1500007  | error sending message to Common Event Service. |
 | 1500008  | Common Event Service does not complete initialization. |
@@ -98,7 +97,6 @@ publish(event: string, options: CommonEventPublishData, callback: AsyncCallback\
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401  | The parameter check failed.             |
 | 1500004  | not System services.                |
 | 1500007  | error sending message to Common Event Service. |
 | 1500008  | Common Event Service does not complete initialization. |
@@ -162,8 +160,6 @@ publishAsUser(event: string, userId: number, callback: AsyncCallback\<void>): vo
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 202  | not system app.                         |
-| 401  | The parameter check failed.             |
 | 1500004  | not System services.                |
 | 1500007  | error sending message to Common Event Service. |
 | 1500008  | Common Event Service does not complete initialization. |
@@ -223,9 +219,7 @@ publishAsUser(event: string, userId: number, options: CommonEventPublishData, ca
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 202  | not system app.                         |
-| 401  | The parameter check failed.             |
-| 1500004  | not System services.                |
+| 1500004  | not System services or System app.                |
 | 1500007  | error sending message to Common Event Service. |
 | 1500008  | Common Event Service does not complete initialization. |
 | 1500009  | error obtaining system parameters.  |
@@ -277,14 +271,6 @@ createSubscriber(subscribeInfo: CommonEventSubscribeInfo, callback: AsyncCallbac
 | subscribeInfo | [CommonEventSubscribeInfo](./js-apis-inner-commonEvent-commonEventSubscribeInfo.md)        | 是   | 表示订阅信息。             |
 | callback      | AsyncCallback\<[CommonEventSubscriber](./js-apis-inner-commonEvent-commonEventSubscriber.md)> | 是   | 表示创建订阅者的回调方法。 |
 
-**错误码：**
-
-错误码介绍请参考[@ohos.commonEventManager(事件)](../errorcodes/errorcode-CommonEventService.md)
-
-| 错误码ID | 错误信息                            |
-| -------- | ----------------------------------- |
-| 401  | The parameter check failed.             |
-
 **示例：**
 
 
@@ -335,14 +321,6 @@ createSubscriber(subscribeInfo: CommonEventSubscribeInfo): Promise\<CommonEventS
 | --------------------------------------------------------- | ---------------- |
 | Promise\<[CommonEventSubscriber](./js-apis-inner-commonEvent-commonEventSubscriber.md)> | 返回订阅者对象。 |
 
-**错误码：**
-
-错误码介绍请参考[@ohos.commonEventManager(事件)](../errorcodes/errorcode-CommonEventService.md)
-
-| 错误码ID | 错误信息                            |
-| -------- | ----------------------------------- |
-| 401  | The parameter check failed.             |
-
 **示例：**
 
 ```ts
@@ -390,7 +368,6 @@ subscribe(subscriber: CommonEventSubscriber, callback: AsyncCallback\<CommonEven
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401  | The parameter check failed.             |
 | 801  | capability not supported.               |
 | 1500007  | error sending message to Common Event Service. |
 | 1500008  | Common Event Service does not complete initialization. |
@@ -462,7 +439,6 @@ unsubscribe(subscriber: CommonEventSubscriber, callback?: AsyncCallback\<void>):
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401  | The parameter check failed.             |
 | 801  | capability not supported.               |
 | 1500007  | error sending message to Common Event Service. |
 | 1500008  | Common Event Service does not complete initialization. |
@@ -521,737 +497,6 @@ try {
 }
 ```
 
-## CommonEventSubscriber
-
-### getCode
-
-getCode(callback: AsyncCallback\<number>): void
-
-获取公共事件的结果代码（callback形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                   | 必填 | 说明               |
-| -------- | ---------------------- | ---- | ------------------ |
-| callback | AsyncCallback\<number> | 是   | 公共事件的结果代码。 |
-
-**错误码：**
-
-错误码介绍请参考[@ohos.commonEventManager(事件)](../errorcodes/errorcode-CommonEventService.md)
-
-| 错误码ID | 错误信息                            |
-| -------- | ----------------------------------- |
-| 201  | The application dose not have permission to call the interface. |
-| 202  | not system app.                         |
-| 401  | The parameter check failed.             |
-| 1500004  | not system service.                 |
-| 1500007  | The message send error.             |
-| 1500008  | The CEMS error.                     |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-//获取有序公共事件的结果代码回调
-function getCodeCallback(err, Code) {
-    if (err) {
-        console.error("getCode failed " + JSON.stringify(err));
-    } else {
-        console.info("getCode " + JSON.stringify(Code));
-    }
-}
-subscriber.getCode(getCodeCallback);
-```
-
-### getCode
-
-getCode(): Promise\<number>
-
-获取公共事件的结果代码（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**返回值：**
-
-| 类型             | 说明                 |
-| ---------------- | -------------------- |
-| Promise\<number> | 公共事件的结果代码。 |
-
-**错误码：**
-
-错误码介绍请参考[@ohos.commonEventManager(事件)](../errorcodes/errorcode-CommonEventService.md)
-
-| 错误码ID | 错误信息                            |
-| -------- | ----------------------------------- |
-| 201  | The application dose not have permission to call the interface. |
-| 202  | not system app.                         |
-| 401  | The parameter check failed.             |
-| 1500004  | not system service.                 |
-| 1500007  | The message send error.             |
-| 1500008  | The CEMS error.                     |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.getCode().then((Code) => {
-    console.info("getCode " + JSON.stringify(Code));
-}).catch((err) => {
-    console.error("getCode failed " + JSON.stringify(err));
-});
-```
-
-### setCode
-
-setCode(code: number, callback: AsyncCallback\<void>): void
-
-设置公共事件的结果代码（callback形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                 | 必填 | 说明                   |
-| -------- | -------------------- | ---- | ---------------------- |
-| code     | number               | 是   | 公共事件的结果代码。   |
-| callback | AsyncCallback\<void> | 是   | 表示被指定的回调方法。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-//设置有序公共事件的结果代码回调
-function setCodeCallback(err) {
-    if (err) {
-        console.error("setCode failed " + JSON.stringify(err));
-    } else {
-        console.info("setCode");
-    }
-}
-subscriber.setCode(1, setCodeCallback);
-```
-
-### setCode
-
-setCode(code: number): Promise\<void>
-
-设置公共事件的结果代码（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名 | 类型   | 必填 | 说明               |
-| ------ | ------ | ---- | ------------------ |
-| code   | number | 是   | 公共事件的结果代码。 |
-
-**返回值：**
-
-| 类型             | 说明                 |
-| ---------------- | -------------------- |
-| Promise\<void>   | 返回一个Promise的结果。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.setCode(1).then(() => {
-    console.info("setCode");
-}).catch((err) => {
-    console.error("setCode failed " + JSON.stringify(err));
-});
-```
-
-### getData
-
-getData(callback: AsyncCallback\<string>): void
-
-获取公共事件的结果数据（callback形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                   | 必填 | 说明                 |
-| -------- | ---------------------- | ---- | -------------------- |
-| callback | AsyncCallback\<string> | 是   | 公共事件的结果数据。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-//获取有序公共事件的结果数据回调
-function getDataCallback(err, Data) {
-    if (err) {
-        console.error("getData failed " + JSON.stringify(err));
-    } else {
-        console.info("getData " + JSON.stringify(Data));
-    }
-}
-subscriber.getData(getDataCallback);
-```
-
-### getData
-
-getData(): Promise\<string>
-
-获取公共事件的结果数据（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**返回值：**
-
-| 类型             | 说明               |
-| ---------------- | ------------------ |
-| Promise\<string> | 公共事件的结果数据。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.getData().then((Data) => {
-    console.info("getData " + JSON.stringify(Data));
-}).catch((err) => {
-    console.error("getData failed " + JSON.stringify(err));
-});
-```
-
-### setData
-
-setData(data: string, callback: AsyncCallback\<void>): void
-
-设置公共事件的结果数据（callback形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                 | 必填 | 说明                 |
-| -------- | -------------------- | ---- | -------------------- |
-| data     | string               | 是   | 公共事件的结果数据。   |
-| callback | AsyncCallback\<void> | 是   | 表示被指定的回调方法。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-//设置有序公共事件的结果数据回调
-function setDataCallback(err) {
-    if (err) {
-        console.error("setData failed " + JSON.stringify(err));
-    } else {
-        console.info("setData");
-    }
-}
-subscriber.setData("publish_data_changed", setDataCallback);
-```
-
-### setData
-
-setData(data: string): Promise\<void>
-
-设置公共事件的结果数据（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名 | 类型   | 必填 | 说明                 |
-| ------ | ------ | ---- | -------------------- |
-| data   | string | 是   | 公共事件的结果数据。 |
-
-**返回值：**
-
-| 类型             | 说明                 |
-| ---------------- | -------------------- |
-| Promise\<void>   | 返回一个Promise的结果。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.setData("publish_data_changed").then(() => {
-    console.info("setData");
-}).catch((err) => {
-    console.error("setData failed " + JSON.stringify(err));
-});
-```
-
-### setCodeAndData
-
-setCodeAndData(code: number, data: string, callback:AsyncCallback\<void>): void
-
-设置公共事件的结果代码和结果数据（callback形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                 | 必填 | 说明                   |
-| -------- | -------------------- | ---- | ---------------------- |
-| code     | number               | 是   | 公共事件的结果代码。   |
-| data     | string               | 是   | 公共事件的结果数据。   |
-| callback | AsyncCallback\<void> | 是   | 表示被指定的回调方法。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-//设置有序公共事件的结果代码和结果数据回调
-function setCodeDataCallback(err) {
-    if (err) {
-        console.error("setCodeAndData failed " + JSON.stringify(err));
-    } else {
-        console.info("setCodeDataCallback");
-    }
-}
-subscriber.setCodeAndData(1, "publish_data_changed", setCodeDataCallback);
-```
-
-### setCodeAndData
-
-setCodeAndData(code: number, data: string): Promise\<void>
-
-设置公共事件的结果代码和结果数据（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名 | 类型   | 必填 | 说明                 |
-| ------ | ------ | ---- | -------------------- |
-| code   | number | 是   | 公共事件的结果代码。 |
-| data   | string | 是   | 公共事件的结果数据。 |
-
-**返回值：**
-
-| 类型             | 说明                 |
-| ---------------- | -------------------- |
-| Promise\<void>   | 返回一个Promise的结果。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.setCodeAndData(1, "publish_data_changed").then(() => {
-    console.info("setCodeAndData");
-}).catch((err) => {
-    console.info("setCodeAndData failed " + JSON.stringify(err));
-});
-```
-
-### isOrderedCommonEvent
-
-isOrderedCommonEvent(callback: AsyncCallback\<boolean>): void
-
-查询当前公共事件的是否为有序公共事件（callback形式）。
-
-返回true代表是有序公共事件，false代表不是有序公共事件。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                    | 必填 | 说明                               |
-| -------- | ----------------------- | ---- | ---------------------------------- |
-| callback | AsyncCallback\<boolean> | 是   | 当前公共事件的是否为有序公共事件。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-//获取当前公共事件是否为有序事件的回调
-function isOrderedCallback(err, isOrdered) {
-    if (err) {
-        console.error("isOrderedCommonEvent failed " + JSON.stringify(err));
-    } else {
-        console.info("isOrdered " + JSON.stringify(isOrdered));
-    }
-}
-subscriber.isOrderedCommonEvent(isOrderedCallback);
-```
-
-### isOrderedCommonEvent
-
-isOrderedCommonEvent(): Promise\<boolean>
-
-查询当前公共事件的是否为有序公共事件（Promise形式）。
-
-返回true代表是有序公共事件，false代表不是有序公共事件。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**返回值：**
-
-| 类型              | 说明                             |
-| ----------------- | -------------------------------- |
-| Promise\<boolean> | 当前公共事件的是否为有序公共事件。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.isOrderedCommonEvent().then((isOrdered) => {
-    console.info("isOrdered " + JSON.stringify(isOrdered));
-}).catch((err) => {
-    console.error("isOrdered failed " + JSON.stringify(err));
-});
-```
-
-### isStickyCommonEvent
-
-isStickyCommonEvent(callback: AsyncCallback\<boolean>): void
-
-检查当前公共事件是否为一个粘性事件（callback形式）。
-
-返回true代表是粘性公共事件，false代表不是粘性公共事件。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                    | 必填 | 说明                               |
-| -------- | ----------------------- | ---- | ---------------------------------- |
-| callback | AsyncCallback\<boolean> | 是   | 当前公共事件的是否为粘性公共事件。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-//获取当前公共事件是否为粘性事件的回调
-function isStickyCallback(err, isSticky) {
-    if (err) {
-        console.error("isStickyCommonEvent failed " + JSON.stringify(err));
-    } else {
-        console.info("isSticky " + JSON.stringify(isSticky));
-    }
-}
-subscriber.isStickyCommonEvent(isStickyCallback);
-```
-
-### isStickyCommonEvent
-
-isStickyCommonEvent(): Promise\<boolean>
-
-检查当前公共事件是否为一个粘性事件（Promise形式）。
-
-返回true代表是粘性公共事件，false代表不是粘性公共事件。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**返回值：**
-
-| 类型              | 说明                             |
-| ----------------- | -------------------------------- |
-| Promise\<boolean> | 当前公共事件的是否为粘性公共事件。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.isStickyCommonEvent().then((isSticky) => {
-    console.info("isSticky " + JSON.stringify(isSticky));
-}).catch((err) => {
-    console.error("isSticky failed " + JSON.stringify(err));
-});
-```
-
-### abortCommonEvent
-
-abortCommonEvent(callback: AsyncCallback\<void>): void
-
-取消当前的公共事件，仅对有序公共事件有效，取消后，公共事件不再向下一个订阅者传递（callback形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                 | 必填 | 说明                 |
-| -------- | -------------------- | ---- | -------------------- |
-| callback | AsyncCallback\<void> | 是   | 取消当前的公共事件。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-//取消当前有序公共事件的回调
-function abortCallback(err) {
-    if (err) {
-        console.error("abortCommonEvent failed " + JSON.stringify(err));
-    } else {
-        console.info("abortCommonEvent");
-    }
-}
-subscriber.abortCommonEvent(abortCallback);
-```
-
-### abortCommonEvent
-
-abortCommonEvent(): Promise\<void>
-
-取消当前的公共事件，仅对有序公共事件有效，取消后，公共事件不再向下一个订阅者传递（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**返回值：**
-
-| 类型             | 说明                 |
-| ---------------- | -------------------- |
-| Promise\<void>   | 返回一个Promise的结果。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.abortCommonEvent().then(() => {
-    console.info("abortCommonEvent");
-}).catch((err) => {
-    console.error("abortCommonEvent failed " + JSON.stringify(err));
-});
-```
-
-### clearAbortCommonEvent
-
-clearAbortCommonEvent(callback: AsyncCallback\<void>): void
-
-清除当前公共事件的取消状态，仅对有序公共事件有效（callback形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                 | 必填 | 说明                 |
-| -------- | -------------------- | ---- | -------------------- |
-| callback | AsyncCallback\<void> | 是   | 表示被指定的回调方法。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-//清除当前公共事件取消状态的回调
-function clearAbortCallback(err) {
-    if (err) {
-        console.error("clearAbortCommonEvent failed " + JSON.stringify(err));
-    } else {
-        console.info("clearAbortCommonEvent");
-    }
-}
-subscriber.clearAbortCommonEvent(clearAbortCallback);
-```
-
-### clearAbortCommonEvent
-
-clearAbortCommonEvent(): Promise\<void>
-
-清除当前公共事件的取消状态，仅对有序公共事件有效（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**返回值：**
-
-| 类型             | 说明                 |
-| ---------------- | -------------------- |
-| Promise\<void>   | 返回一个Promise的结果。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.clearAbortCommonEvent().then(() => {
-    console.info("clearAbortCommonEvent");
-}).catch((err) => {
-    console.error("clearAbortCommonEvent failed " + JSON.stringify(err));
-});
-```
-
-### getAbortCommonEvent
-
-getAbortCommonEvent(callback: AsyncCallback\<boolean>): void
-
-获取当前有序公共事件是否取消的状态（callback形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                    | 必填 | 说明                               |
-| -------- | ----------------------- | ---- | ---------------------------------- |
-| callback | AsyncCallback\<boolean> | 是   | 表示当前有序公共事件是否取消的状态。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-//获取当前有序公共事件是否取消的回调
-function getAbortCallback(err, AbortCommonEvent) {
-    if (err) {
-        console.error("getAbortCommonEvent failed " + JSON.stringify(err));
-    } else {
-        console.info("AbortCommonEvent " + AbortCommonEvent)
-    }
-}
-subscriber.getAbortCommonEvent(getAbortCallback);
-```
-
-### getAbortCommonEvent
-
-getAbortCommonEvent(): Promise\<boolean>
-
-获取当前有序公共事件是否取消的状态（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**返回值：**
-
-| 类型              | 说明                               |
-| ----------------- | ---------------------------------- |
-| Promise\<boolean> | 表示当前有序公共事件是否取消的状态。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.getAbortCommonEvent().then((AbortCommonEvent) => {
-    console.info("AbortCommonEvent " + JSON.stringify(AbortCommonEvent));
-}).catch((err) => {
-    console.error("getAbortCommonEvent failed " + JSON.stringify(err));
-});
-```
-
-### getSubscribeInfo
-
-getSubscribeInfo(callback: AsyncCallback\<CommonEventSubscribeInfo>): void
-
-获取订阅者的订阅信息（callback形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                                                         | 必填 | 说明                   |
-| -------- | ------------------------------------------------------------ | ---- | ---------------------- |
-| callback | AsyncCallback\<[CommonEventSubscribeInfo](#commoneventsubscribeinfo)> | 是   | 表示订阅者的订阅信息。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-//获取订阅者信息回调
-function getSubscribeInfoCallback(err, SubscribeInfo) {
-    if (err) {
-        console.error("getSubscribeInfo failed " + JSON.stringify(err));
-    } else {
-        console.info("SubscribeInfo " + JSON.stringify(SubscribeInfo));
-    }
-}
-subscriber.getSubscribeInfo(getSubscribeInfoCallback);
-```
-
-### getSubscribeInfo
-
-getSubscribeInfo(): Promise\<CommonEventSubscribeInfo>
-
-获取订阅者的订阅信息（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**返回值：**
-
-| 类型                                                         | 说明                   |
-| ------------------------------------------------------------ | ---------------------- |
-| Promise\<[CommonEventSubscribeInfo](#commoneventsubscribeinfo)> | 表示订阅者的订阅信息。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.getSubscribeInfo().then((SubscribeInfo) => {
-    console.info("SubscribeInfo " + JSON.stringify(SubscribeInfo));
-}).catch((err) => {
-    console.error("getSubscribeInfo failed " + JSON.stringify(err));
-});
-```
-
-### finishCommonEvent<sup>9+</sup>
-
-finishCommonEvent(callback: AsyncCallback\<void\>): void
-
-结束当前有序公共事件（callback形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**参数：**
-
-| 参数名   | 类型                  | 必填 | 说明                              |
-| -------- | -------------------- | ---- | -------------------------------- |
-| callback | AsyncCallback\<void> | 是   | 表示有序公共事件结束后的回调函数。 |
-
-**示例：**
-
-```ts
-var subscriber; //创建成功的订阅者对象
-
-//结束当前有序公共事件的回调
-function finishCommonEventCallback(err) {
-  if (err) {
-    console.error("finishCommonEvent failed " + JSON.stringify(err));
-} else {
-    console.info("FinishCommonEvent");
-}
-}
-subscriber.finishCommonEvent(finishCommonEventCallback);
-```
-
-### finishCommonEvent<sup>9+</sup>
-
-finishCommonEvent(): Promise\<void\>
-
-结束当前有序公共事件（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.CommonEvent
-
-**返回值：**
-
-| 类型             | 说明                 |
-| ---------------- | -------------------- |
-| Promise\<void>   | 返回一个Promise的结果。 |
-
-**示例：**
-
-```ts
-var subscriber;	//创建成功的订阅者对象
-
-subscriber.finishCommonEvent().then(() => {
-    console.info("FinishCommonEvent");
-}).catch((err) => {
-    console.error("finishCommonEvent failed " + JSON.stringify(err));
-});
-```
-
 ## CommonEventData
 
 **系统能力：** 以下各项对应的系统能力均为SystemCapability.Notification.CommonEvent
diff --git a/zh-cn/application-dev/reference/apis/js-apis-console.md b/zh-cn/application-dev/reference/apis/js-apis-console.md
new file mode 100644
index 0000000000000000000000000000000000000000..815d920ee780ca2996689552ab523853252ba5fa
--- /dev/null
+++ b/zh-cn/application-dev/reference/apis/js-apis-console.md
@@ -0,0 +1,139 @@
+# console 控制台
+
+本模块提供了一个简单的调试控制台，类似于浏览器提供的JavaScript控制台机制。
+
+> **说明：**
+>
+> 本模块首批接口从API version 3开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
+
+## console.debug
+
+debug(message: string, ...arguments: any[]): void
+
+以格式化输出方式打印调试信息。
+
+**系统能力：** SystemCapability.ArkUI.ArkUI.Full
+
+**参数：**
+
+| 参数名     | 类型     | 必填   | 说明          |
+| ------- | ------ | ---- | ----------- |
+| message | string | 是    | 表示要打印的文本信息。 |
+| arguments | any | 否    | 表示其余要打印的信息或message的替换值。 |
+
+**示例：**
+```js
+const number = 5;
+console.debug('count: %d', number);  // 格式化输出替换message中的文本。
+// count: 5 
+console.debug('count:', number);  // 打印message以及其余信息
+// count: 5 
+console.debug('count:'); // 仅打印message
+// count: 
+```
+
+## console.log
+
+log(message: string, ...arguments: any[]): void
+
+以格式化输出方式打印日志信息。
+
+**系统能力：** SystemCapability.ArkUI.ArkUI.Full
+
+**参数：**
+
+| 参数名     | 类型     | 必填   | 说明          |
+| ------- | ------ | ---- | ----------- |
+| message | string | 是    | 表示要打印的文本信息。 |
+| arguments | any | 否    |表示其余要打印的信息或message的替换值。 |
+
+**示例：**
+```js
+const number = 5;
+console.log('count: %d', number);  // 格式化输出替换message中的文本。
+// count: 5 
+console.log('count:', number);  // 打印message以及其余信息
+// count: 5 
+console.log('count:'); // 仅打印message
+// count: 
+```
+
+## console.info
+
+info(message: string, ...arguments: any[]): void
+
+以格式化输出方式打印日志信息。(console.log()的别名）。
+
+**系统能力：** SystemCapability.ArkUI.ArkUI.Full
+
+**参数：**
+
+| 参数名     | 类型     | 必填   | 说明          |
+| ------- | ------ | ---- | ----------- |
+| message | string | 是    | 表示要打印的文本信息。 |
+| arguments | any | 否    | 表示其余要打印的信息或message的替换值。 |
+
+**示例：**
+```js
+const number = 5;
+console.info('count: %d', number);  // 格式化输出替换message中的文本。
+// count: 5 
+console.info('count:', number);  // 打印message以及其余信息
+// count: 5 
+console.info('count:'); // 仅打印message
+// count: 
+```
+
+## console.warn
+
+warn(message: string, ...arguments: any[]): void
+
+以格式化输出方式打印警告信息。
+
+**系统能力：** SystemCapability.ArkUI.ArkUI.Full
+
+**参数：**
+
+| 参数名     | 类型     | 必填   | 说明          |
+| ------- | ------ | ---- | ----------- |
+| message | string | 是    | 表示要打印的警告信息。 |
+| arguments | any | 否    | 表示其余要打印的信息或message的替换值。 |
+
+**示例：**
+```js
+const str = "name should be string";
+console.warn('warn: %d', str);  // 格式化输出替换message中的文本。
+// warn: name should be string
+console.warn('warn:', str);  // 打印message以及其余信息
+// warn: name should be string
+console.warn('warn:'); // 仅打印message
+// warn: 
+```
+
+## console.error
+
+error(message: string, ...arguments: any[]): void
+
+以格式化输出方式打印错误信息。
+
+**系统能力：** SystemCapability.ArkUI.ArkUI.Full
+
+**参数：**
+
+| 参数名     | 类型     | 必填   | 说明          |
+| ------- | ------ | ---- | ----------- |
+| message | string | 是    | 表示要打印的错误信息。 |
+| arguments | any | 否    | 表示其余要打印的信息或message的替换值。 |
+
+
+**示例：**
+```js
+const str = "value is not defined";
+console.error('error: %d', str);  // 格式化输出替换message中的文本。
+// error: value is not defined
+console.error('error:', str);  // 打印message以及其余信息
+// error: value is not defined
+console.error('error:'); // 仅打印message
+// error: 
+```
+
diff --git a/zh-cn/application-dev/reference/apis/js-apis-data-dataSharePredicates.md b/zh-cn/application-dev/reference/apis/js-apis-data-dataSharePredicates.md
index 65fa52245a53117087a637b2d2db85187a199b2f..26c91c662fff32371bd2bb9d98054dcdc59e5dcb 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-data-dataSharePredicates.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-data-dataSharePredicates.md
@@ -18,7 +18,7 @@ import dataSharePredicates from '@ohos.data.dataSharePredicates';
 ```
 
 ## DataSharePredicates
-提供用于不同实现不同查询方法的数据共享谓词。
+提供用于不同实现不同查询方法的数据共享谓词。该类型不是多线程安全的，如果应用中存在多线程同时操作该类派生出的实例，注意加锁保护。
 
 ### equalTo
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-data-distributedobject.md b/zh-cn/application-dev/reference/apis/js-apis-data-distributedobject.md
index 2adec6a401cefaa5ba69b3fb40b864973127af0d..52a0d3f55366e63c4fd40a93b34e072604e9585a 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-data-distributedobject.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-data-distributedobject.md
@@ -135,7 +135,7 @@ setSessionId(sessionId: string, callback: AsyncCallback&lt;void&gt;): void
 
   | 错误码ID | 错误信息 |
   | -------- | -------- |
-  | 15400001 | 创建内存数据库失败。|
+  | 15400001 | Create table failed.|
 
 **示例：**
 
@@ -168,7 +168,7 @@ setSessionId(callback: AsyncCallback&lt;void&gt;): void
 
   | 错误码ID | 错误信息 |
   | -------- | -------- |
-  | 15400001 | 创建内存数据库失败。|
+  | 15400001 | Create table failed.|
 
 **示例：**
 
@@ -211,7 +211,7 @@ setSessionId(sessionId?: string): Promise&lt;void&gt;
 
   | 错误码ID | 错误信息 |
   | -------- | -------- |
-  | 15400001 | 创建内存数据库失败。|
+  | 15400001 | Create table failed.|
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-data-rdb.md b/zh-cn/application-dev/reference/apis/js-apis-data-rdb.md
index 1399a1245c49a6a302c93d122b3010c7d1335d20..2c1c1a991f761243622999607866e4c3c9021cc3 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-data-rdb.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-data-rdb.md
@@ -2045,7 +2045,7 @@ on(event: 'dataChange', type: SubscribeType, observer: Callback&lt;Array&lt;stri
 | -------- | -------- | -------- | -------- |
 | event | string | 是 | 取值为'dataChange'，表示数据更改。 |
 | type | [SubscribeType](#subscribetype8) | 是 | 订阅类型。 |
-| observer | Callback&lt;Array&lt;string&gt;&gt; | 是 | 指分布式数据库中数据更改事件的观察者。 |
+| observer | Callback&lt;Array&lt;string&gt;&gt; | 是 | 指分布式数据库中数据更改事件的观察者。Array&lt;string>为数据库中的数据发生改变的对端设备ID。 |
 
 **示例：**
 
@@ -2076,7 +2076,7 @@ off(event:'dataChange', type: SubscribeType, observer: Callback&lt;Array&lt;stri
 | -------- | -------- | -------- | -------- |
 | event | string | 是 | 取值为'dataChange'，表示数据更改。 |
 | type | [SubscribeType](#subscribetype8)    | 是 | 订阅类型。 |
-| observer | Callback&lt;Array&lt;string&gt;&gt; | 是 | 指已注册的数据更改观察者。|
+| observer | Callback&lt;Array&lt;string&gt;&gt; | 是 | 指已注册的数据更改观察者。Array&lt;string>为数据库中的数据发生改变的对端设备ID。 |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-data-relationalStore.md b/zh-cn/application-dev/reference/apis/js-apis-data-relationalStore.md
index 6c1009da0adf68f52ed5ee1832df9c5ffb067ad3..7804d5aadc7bf7f85b134d3d1a257cdc5ccb2fbb 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-data-relationalStore.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-data-relationalStore.md
@@ -64,7 +64,7 @@ const STORE_CONFIG = {
 relationalStore.getRdbStore(context, STORE_CONFIG, function (err, rdbStore) {
   store = rdbStore;
   if (err) {
-    console.error(`Get RdbStore failed, err: ${err}`);
+    console.error(`Get RdbStore failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`Get RdbStore successfully.`);
@@ -87,7 +87,7 @@ class EntryAbility extends UIAbility {
     relationalStore.getRdbStore(this.context, STORE_CONFIG, function (err, rdbStore) {
       store = rdbStore;
       if (err) {
-        console.error(`Get RdbStore failed, err: ${err}`);
+        console.error(`Get RdbStore failed, code is ${err.code},message is ${err.message}`);
         return;
       }
       console.info(`Get RdbStore successfully.`);
@@ -148,7 +148,7 @@ promise.then(async (rdbStore) => {
   store = rdbStore;
   console.info(`Get RdbStore successfully.`);
 }).catch((err) => {
-  console.error(`Get RdbStore failed, err: ${err}`);
+  console.error(`Get RdbStore failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -170,7 +170,7 @@ class EntryAbility extends UIAbility {
       store = rdbStore;
       console.info(`Get RdbStore successfully.`)
     }).catch((err) => {
-      console.error(`Get RdbStore failed, err: ${err}`);
+      console.error(`Get RdbStore failed, code is ${err.code},message is ${err.message}`);
     })
   }
 }
@@ -212,7 +212,7 @@ let context = featureAbility.getContext()
 
 relationalStore.deleteRdbStore(context, "RdbTest.db", function (err) {
   if (err) {
-    console.error(`Delete RdbStore failed, err: ${err}`);
+    console.error(`Delete RdbStore failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`Delete RdbStore successfully.`);
@@ -228,7 +228,7 @@ class EntryAbility extends UIAbility {
   onWindowStageCreate(windowStage){
     relationalStore.deleteRdbStore(this.context, "RdbTest.db", function (err) {
       if (err) {
-        console.error(`Delete RdbStore failed, err: ${err}`);
+        console.error(`Delete RdbStore failed, code is ${err.code},message is ${err.message}`);
         return;
       }
       console.info(`Delete RdbStore successfully.`);
@@ -280,7 +280,7 @@ let promise = relationalStore.deleteRdbStore(context, "RdbTest.db");
 promise.then(()=>{
   console.info(`Delete RdbStore successfully.`);
 }).catch((err) => {
-  console.error(`Delete RdbStore failed, err: ${err}`);
+  console.error(`Delete RdbStore failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -295,7 +295,7 @@ class EntryAbility extends UIAbility {
     promise.then(()=>{
       console.info(`Delete RdbStore successfully.`);
     }).catch((err) => {
-      console.error(`Delete RdbStore failed, err: ${err}`);
+      console.error(`Delete RdbStore failed, code is ${err.code},message is ${err.message}`);
     })
   }
 }
@@ -311,7 +311,7 @@ class EntryAbility extends UIAbility {
 | ------------- | ------------- | ---- | --------------------------------------------------------- |
 | name          | string        | 是   | 数据库文件名。                                            |
 | securityLevel | [SecurityLevel](#securitylevel) | 是   | 设置数据库安全级别                                        |
-| encrypt       | boolean       | 否   | 指定数据库是否加密。<br/> true:加密。<br/> false:非加密。 |
+| encrypt       | boolean       | 否   | 指定数据库是否加密，默认不加密。<br/> true:加密。<br/> false:非加密。 |
 
 ## SecurityLevel
 
@@ -344,7 +344,7 @@ class EntryAbility extends UIAbility {
 
 ## ValuesBucket
 
-用于存储键值对的类型。
+用于存储键值对的类型。该类型不是多线程安全的，如果应用中存在多线程同时操作该类派生出的实例，注意加锁保护。
 
 **系统能力：** SystemCapability.DistributedDataManager.RelationalStore.Core
 
@@ -377,7 +377,7 @@ class EntryAbility extends UIAbility {
 
 ## RdbPredicates
 
-表示关系型数据库（RDB）的谓词。该类确定RDB中条件表达式的值是true还是false。
+表示关系型数据库（RDB）的谓词。该类确定RDB中条件表达式的值是true还是false。该类型不是多线程安全的，如果应用中存在多线程同时操作该类派生出的实例，注意加锁保护。
 
 ### constructor
 
@@ -1264,7 +1264,7 @@ const valueBucket = {
 };
 store.insert("EMPLOYEE", valueBucket, function (err, rowId) {
   if (err) {
-    console.error(`Insert is failed, err: ${err}`);
+    console.error(`Insert is failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`Insert is successful, rowId = ${rowId}`);
@@ -1306,7 +1306,7 @@ let promise = store.insert("EMPLOYEE", valueBucket);
 promise.then((rowId) => {
   console.info(`Insert is successful, rowId = ${rowId}`);
 }).catch((err) => {
-  console.error(`Insert is failed, err: ${err}`);
+  console.error(`Insert is failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -1352,7 +1352,7 @@ const valueBucket3 = {
 let valueBuckets = new Array(valueBucket1, valueBucket2, valueBucket3);
 store.batchInsert("EMPLOYEE", valueBuckets, function(err, insertNum) {
   if (err) {
-    console.error(`batchInsert is failed, err: ${err}`);
+    console.error(`batchInsert is failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`batchInsert is successful, the number of values that were inserted = ${insertNum}`);
@@ -1407,7 +1407,7 @@ let promise = store.batchInsert("EMPLOYEE", valueBuckets);
 promise.then((insertNum) => {
   console.info(`batchInsert is successful, the number of values that were inserted = ${insertNum}`);
 }).catch((err) => {
-  console.error(`batchInsert is failed, err: ${err}`);
+  console.error(`batchInsert is failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -1440,7 +1440,7 @@ let predicates = new relationalStore.RdbPredicates("EMPLOYEE");
 predicates.equalTo("NAME", "Lisa");
 store.update(valueBucket, predicates, function (err, rows) {
   if (err) {
-    console.error(`Updated failed, err: ${err}`);
+    console.error(`Updated failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`Updated row count: ${rows}`);
@@ -1484,7 +1484,7 @@ let promise = store.update(valueBucket, predicates);
 promise.then(async (rows) => {
   console.info(`Updated row count: ${rows}`);
 }).catch((err) => {
-  console.error(`Updated failed, err: ${err}`);
+  console.error(`Updated failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -1497,6 +1497,8 @@ update(table: string, values: ValuesBucket, predicates: dataSharePredicates.Data
 
 **系统能力：** SystemCapability.DistributedDataManager.RelationalStore.Core
 
+**模型约束：** 此接口仅可在Stage模型下使用。
+
 **系统接口：** 此接口为系统接口。
 
 **参数：**
@@ -1522,7 +1524,7 @@ let predicates = new dataSharePredicates.DataSharePredicates();
 predicates.equalTo("NAME", "Lisa");
 store.update("EMPLOYEE", valueBucket, predicates, function (err, rows) {
   if (err) {
-    console.error(`Updated failed, err: ${err}`);
+    console.error(`Updated failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`Updated row count: ${rows}`);
@@ -1537,6 +1539,8 @@ update(table: string, values: ValuesBucket, predicates: dataSharePredicates.Data
 
 **系统能力：** SystemCapability.DistributedDataManager.RelationalStore.Core
 
+**模型约束：** 此接口仅可在Stage模型下使用。
+
 **系统接口：** 此接口为系统接口。
 
 **参数：**
@@ -1569,7 +1573,7 @@ let promise = store.update("EMPLOYEE", valueBucket, predicates);
 promise.then(async (rows) => {
   console.info(`Updated row count: ${rows}`);
 }).catch((err) => {
-  console.error(`Updated failed, err: ${err}`);
+  console.error(`Updated failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -1595,7 +1599,7 @@ let predicates = new relationalStore.RdbPredicates("EMPLOYEE");
 predicates.equalTo("NAME", "Lisa");
 store.delete(predicates, function (err, rows) {
   if (err) {
-    console.error(`Delete failed, err: ${err}`);
+    console.error(`Delete failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`Delete rows: ${rows}`);
@@ -1631,7 +1635,7 @@ let promise = store.delete(predicates);
 promise.then((rows) => {
   console.info(`Delete rows: ${rows}`);
 }).catch((err) => {
-  console.error(`Delete failed, err: ${err}`);
+  console.error(`Delete failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -1643,6 +1647,8 @@ delete(table: string, predicates: dataSharePredicates.DataSharePredicates, callb
 
 **系统能力：** SystemCapability.DistributedDataManager.RelationalStore.Core
 
+**模型约束：** 此接口仅可在Stage模型下使用。
+
 **系统接口：** 此接口为系统接口。
 
 **参数：**
@@ -1661,7 +1667,7 @@ let predicates = new dataSharePredicates.DataSharePredicates();
 predicates.equalTo("NAME", "Lisa");
 store.delete("EMPLOYEE", predicates, function (err, rows) {
   if (err) {
-    console.error(`Delete failed, err: ${err}`);
+    console.error(`Delete failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`Delete rows: ${rows}`);
@@ -1676,6 +1682,8 @@ delete(table: string, predicates: dataSharePredicates.DataSharePredicates):Promi
 
 **系统能力：** SystemCapability.DistributedDataManager.RelationalStore.Core
 
+**模型约束：** 此接口仅可在Stage模型下使用。
+
 **系统接口：** 此接口为系统接口。
 
 **参数：**
@@ -1701,7 +1709,7 @@ let promise = store.delete("EMPLOYEE", predicates);
 promise.then((rows) => {
   console.info(`Delete rows: ${rows}`);
 }).catch((err) => {
-  console.error(`Delete failed, err: ${err}`);
+  console.error(`Delete failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -1728,7 +1736,7 @@ let predicates = new relationalStore.RdbPredicates("EMPLOYEE");
 predicates.equalTo("NAME", "Rose");
 store.query(predicates, ["ID", "NAME", "AGE", "SALARY", "CODES"], function (err, resultSet) {
   if (err) {
-    console.error(`Query failed, err: ${err}`);
+    console.error(`Query failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`ResultSet column names: ${resultSet.columnNames}`);
@@ -1767,7 +1775,7 @@ promise.then((resultSet) => {
   console.info(`ResultSet column names: ${resultSet.columnNames}`);
   console.info(`ResultSet column count: ${resultSet.columnCount}`);
 }).catch((err) => {
-  console.error(`Query failed, err: ${err}`);
+  console.error(`Query failed, code is ${err.code},message is ${err.message}`);
 })
   ```
 
@@ -1779,6 +1787,8 @@ query(table: string, predicates: dataSharePredicates.DataSharePredicates, column
 
 **系统能力：** SystemCapability.DistributedDataManager.RelationalStore.Core
 
+**模型约束：** 此接口仅可在Stage模型下使用。
+
 **系统接口：** 此接口为系统接口。
 
 **参数：**
@@ -1798,7 +1808,7 @@ let predicates = new dataSharePredicates.DataSharePredicates();
 predicates.equalTo("NAME", "Rose");
 store.query("EMPLOYEE", predicates, ["ID", "NAME", "AGE", "SALARY", "CODES"], function (err, resultSet) {
   if (err) {
-    console.error(`Query failed, err: ${err}`);
+    console.error(`Query failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`ResultSet column names: ${resultSet.columnNames}`);
@@ -1814,6 +1824,8 @@ query(table: string, predicates: dataSharePredicates.DataSharePredicates, column
 
 **系统能力：** SystemCapability.DistributedDataManager.RelationalStore.Core
 
+**模型约束：** 此接口仅可在Stage模型下使用。
+
 **系统接口：** 此接口为系统接口。
 
 **参数：**
@@ -1841,7 +1853,7 @@ promise.then((resultSet) => {
   console.info(`ResultSet column names: ${resultSet.columnNames}`);
   console.info(`ResultSet column count: ${resultSet.columnCount}`);
 }).catch((err) => {
-  console.error(`Query failed, err: ${err}`);
+  console.error(`Query failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -1889,7 +1901,7 @@ predicates.greaterThan("id", 0);
 store.remoteQuery(deviceId, "EMPLOYEE", predicates, ["ID", "NAME", "AGE", "SALARY", "CODES"],
   function(err, resultSet) {
     if (err) {
-      console.error(`Failed to remoteQuery, err: ${err}`);
+      console.error(`Failed to remoteQuery, code is ${err.code},message is ${err.message}`);
       return;
     }
     console.info(`ResultSet column names: ${resultSet.columnNames}`);
@@ -1949,7 +1961,7 @@ promise.then((resultSet) => {
   console.info(`ResultSet column names: ${resultSet.columnNames}`);
   console.info(`ResultSet column count: ${resultSet.columnCount}`);
 }).catch((err) => {
-  console.error(`Failed to remoteQuery, err: ${err}`);
+  console.error(`Failed to remoteQuery, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -1974,7 +1986,7 @@ querySql(sql: string, bindArgs: Array&lt;ValueType&gt;, callback: AsyncCallback&
 ```js
 store.querySql("SELECT * FROM EMPLOYEE CROSS JOIN BOOK WHERE BOOK.NAME = ?", ['sanguo'], function (err, resultSet) {
   if (err) {
-    console.error(`Query failed, err: ${err}`);
+    console.error(`Query failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`ResultSet column names: ${resultSet.columnNames}`);
@@ -2011,7 +2023,7 @@ promise.then((resultSet) => {
   console.info(`ResultSet column names: ${resultSet.columnNames}`);
   console.info(`ResultSet column count: ${resultSet.columnCount}`);
 }).catch((err) => {
-  console.error(`Query failed, err: ${err}`);
+  console.error(`Query failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -2037,7 +2049,7 @@ executeSql(sql: string, bindArgs: Array&lt;ValueType&gt;, callback: AsyncCallbac
 const SQL_DELETE_TABLE = "DELETE FROM test WHERE name = ?"
 store.executeSql(SQL_DELETE_TABLE, ['zhangsan'], function(err) {
   if (err) {
-    console.error(`ExecuteSql failed, err: ${err}`);
+    console.error(`ExecuteSql failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`Delete table done.`);
@@ -2073,7 +2085,7 @@ let promise = store.executeSql(SQL_DELETE_TABLE);
 promise.then(() => {
     console.info(`Delete table done.`);
 }).catch((err) => {
-    console.error(`ExecuteSql failed, err: ${err}`);
+    console.error(`ExecuteSql failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -2096,7 +2108,7 @@ const STORE_CONFIG = {
 };
 relationalStore.getRdbStore(context, STORE_CONFIG, async function (err, store) {
   if (err) {
-    console.error(`GetRdbStore failed, err: ${err}`);
+    console.error(`GetRdbStore failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   store.beginTransaction();
@@ -2130,7 +2142,7 @@ const STORE_CONFIG = {
 };
 relationalStore.getRdbStore(context, STORE_CONFIG, async function (err, store) {
   if (err) {
-     console.error(`GetRdbStore failed, err: ${err}`);
+     console.error(`GetRdbStore failed, code is ${err.code},message is ${err.message}`);
      return;
   }
   store.beginTransaction();
@@ -2164,7 +2176,7 @@ const STORE_CONFIG = {
 };
 relationalStore.getRdbStore(context, STORE_CONFIG, async function (err, store) {
   if (err) {
-    console.error(`GetRdbStore failed, err: ${err}`);
+    console.error(`GetRdbStore failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   try {
@@ -2179,7 +2191,7 @@ relationalStore.getRdbStore(context, STORE_CONFIG, async function (err, store) {
 	await store.insert("test", valueBucket);
     store.commit();
   } catch (err) {
-    console.error(`Transaction failed, err: ${err}`);
+    console.error(`Transaction failed, code is ${err.code},message is ${err.message}`);
     store.rollBack();
   }
 })
@@ -2205,7 +2217,7 @@ backup(destName:string, callback: AsyncCallback&lt;void&gt;):void
 ```js
 store.backup("dbBackup.db", function(err) {
   if (err) {
-    console.error(`Backup failed, err: ${err}`);
+    console.error(`Backup failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`Backup success.`);
@@ -2239,7 +2251,7 @@ let promiseBackup = store.backup("dbBackup.db");
 promiseBackup.then(()=>{
   console.info(`Backup success.`);
 }).catch((err)=>{
-  console.error(`Backup failed, err: ${err}`);
+  console.error(`Backup failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -2263,7 +2275,7 @@ restore(srcName:string, callback: AsyncCallback&lt;void&gt;):void
 ```js
 store.restore("dbBackup.db", function(err) {
   if (err) {
-    console.error(`Restore failed, err: ${err}`);
+    console.error(`Restore failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`Restore success.`);
@@ -2297,7 +2309,7 @@ let promiseRestore = store.restore("dbBackup.db");
 promiseRestore.then(()=>{
   console.info(`Restore success.`);
 }).catch((err)=>{
-  console.error(`Restore failed, err: ${err}`);
+  console.error(`Restore failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -2323,7 +2335,7 @@ setDistributedTables(tables: Array&lt;string&gt;, callback: AsyncCallback&lt;voi
 ```js
 store.setDistributedTables(["EMPLOYEE"], function (err) {
   if (err) {
-    console.error(`SetDistributedTables failed, err: ${err}`);
+    console.error(`SetDistributedTables failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`SetDistributedTables successfully.`);
@@ -2359,7 +2371,7 @@ let promise = store.setDistributedTables(["EMPLOYEE"]);
 promise.then(() => {
   console.info(`SetDistributedTables successfully.`);
 }).catch((err) => {
-  console.error(`SetDistributedTables failed, err: ${err}`);
+  console.error(`SetDistributedTables failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -2404,7 +2416,7 @@ deviceManager.createDeviceManager("com.example.appdatamgrverify", (err, manager)
 
 store.obtainDistributedTableName(deviceId, "EMPLOYEE", function (err, tableName) {
     if (err) {
-        console.error(`ObtainDistributedTableName failed, err: ${err}`);
+        console.error(`ObtainDistributedTableName failed, code is ${err.code},message is ${err.message}`);
         return;
     }
     console.info(`ObtainDistributedTableName successfully, tableName= ${tableName}`);
@@ -2459,7 +2471,7 @@ let promise = store.obtainDistributedTableName(deviceId, "EMPLOYEE");
 promise.then((tableName) => {
   console.info(`ObtainDistributedTableName successfully, tableName= ${tableName}`);
 }).catch((err) => {
-  console.error(`ObtainDistributedTableName failed, err: ${err}`);
+  console.error(`ObtainDistributedTableName failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -2504,7 +2516,7 @@ let predicates = new relationalStore.RdbPredicates('EMPLOYEE');
 predicates.inDevices(deviceIds);
 store.sync(relationalStore.SyncMode.SYNC_MODE_PUSH, predicates, function (err, result) {
   if (err) {
-    console.error(`Sync failed, err: ${err}`);
+    console.error(`Sync failed, code is ${err.code},message is ${err.message}`);
     return;
   }
   console.info(`Sync done.`);
@@ -2565,7 +2577,7 @@ promise.then((result) =>{
     console.info(`device= ${result[i][0]}, status= ${result[i][1]}`);
   }
 }).catch((err) => {
-  console.error(`Sync failed, err: ${err}`);
+  console.error(`Sync failed, code is ${err.code},message is ${err.message}`);
 })
 ```
 
@@ -2583,7 +2595,7 @@ on(event: 'dataChange', type: SubscribeType, observer: Callback&lt;Array&lt;stri
 | -------- | ----------------------------------- | ---- | ------------------------------------------- |
 | event    | string                              | 是   | 取值为'dataChange'，表示数据更改。          |
 | type     | [SubscribeType](#subscribetype)    | 是   | 订阅类型。 |
-| observer | Callback&lt;Array&lt;string&gt;&gt; | 是   | 指分布式数据库中数据更改事件的观察者。      |
+| observer | Callback&lt;Array&lt;string&gt;&gt; | 是   | 指分布式数据库中数据更改事件的观察者。Array&lt;string>为数据库中的数据发生改变的对端设备ID。 |
 
 **示例：**
 
@@ -2596,7 +2608,7 @@ function storeObserver(devices) {
 try {
   store.on('dataChange', relationalStore.SubscribeType.SUBSCRIBE_TYPE_REMOTE, storeObserver);
 } catch (err) {
-  console.error(`Register observer failed, err: ${err}`);
+  console.error(`Register observer failed, code is ${err.code},message is ${err.message}`);
 }
 ```
 
@@ -2614,7 +2626,7 @@ off(event:'dataChange', type: SubscribeType, observer: Callback&lt;Array&lt;stri
 | -------- | ---------------------------------- | ---- | ------------------------------------------ |
 | event    | string                              | 是   | 取值为'dataChange'，表示数据更改。          |
 | type     | [SubscribeType](#subscribetype)     | 是   | 订阅类型。                                 |
-| observer | Callback&lt;Array&lt;string&gt;&gt; | 是   | 指已注册的数据更改观察者。                  |
+| observer | Callback&lt;Array&lt;string&gt;&gt; | 是   | 指已注册的数据更改观察者。Array&lt;string>为数据库中的数据发生改变的对端设备ID。 |
 
 **示例：**
 
@@ -2627,7 +2639,7 @@ function storeObserver(devices) {
 try {
   store.off('dataChange', relationalStore.SubscribeType.SUBSCRIBE_TYPE_REMOTE, storeObserver);
 } catch (err) {
-  console.error(`Unregister observer failed, err: ${err}`);
+  console.error(`Unregister observer failed, code is ${err.code},message is ${err.message}`);
 }
 ```
 
@@ -2778,7 +2790,7 @@ promise.then((resultSet) => {
   resultSet.goTo(1);
   resultSet.close();
 }).catch((err) => {
-  console.error(`query failed, err: ${err}`);
+  console.error(`query failed, code is ${err.code},message is ${err.message}`);
 });
   ```
 
@@ -2819,7 +2831,7 @@ promise.then((resultSet) => {
   resultSet.goToRow(5);
   resultSet.close();
 }).catch((err) => {
-  console.error(`query failed, err: ${err}`);
+  console.error(`query failed, code is ${err.code},message is ${err.message}`);
 });
   ```
 
@@ -2855,7 +2867,7 @@ promise.then((resultSet) => {
   resultSet.goToFirstRow();
   resultSet.close();
 }).catch((err) => {
-  console.error(`query failed, err: ${err}`);
+  console.error(`query failed, code is ${err.code},message is ${err.message}`);
 });
   ```
 
@@ -2890,7 +2902,7 @@ promise.then((resultSet) => {
   resultSet.goToLastRow();
   resultSet.close();
 }).catch((err) => {
-  console.error(`query failed, err: ${err}`);
+  console.error(`query failed, code is ${err.code},message is ${err.message}`);
 });
   ```
 
@@ -2925,7 +2937,7 @@ promise.then((resultSet) => {
   resultSet.goToNextRow();
   resultSet.close();
 }).catch((err) => {
-  console.error(`query failed, err: ${err}`);
+  console.error(`query failed, code is ${err.code},message is ${err.message}`);
 });
   ```
 
@@ -2960,7 +2972,7 @@ promise.then((resultSet) => {
   resultSet.goToPreviousRow();
   resultSet.close();
 }).catch((err) => {
-  console.error(`query failed, err: ${err}`);
+  console.error(`query failed, code is ${err.code},message is ${err.message}`);
 });
   ```
 
@@ -3150,7 +3162,7 @@ let promiseClose = store.query(predicatesClose, ["ID", "NAME", "AGE", "SALARY",
 promiseClose.then((resultSet) => {
   resultSet.close();
 }).catch((err) => {
-  console.error(`resultset close failed, err: ${err}`);
+  console.error(`resultset close failed, code is ${err.code},message is ${err.message}`);
 });
   ```
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-data-valuesBucket.md b/zh-cn/application-dev/reference/apis/js-apis-data-valuesBucket.md
index e6d3accd7e92ff3bf0478a4f46dbdc1d39e8ed3a..57c35da571b4ff8700f07423b2a4dafba65d928b 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-data-valuesBucket.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-data-valuesBucket.md
@@ -30,10 +30,10 @@ import { ValuesBucket } from '@ohos.data.ValuesBucket';
 
 ## ValuesBucket
 
-用于存储键值对的类型。
+用于存储键值对的类型。该类型不是多线程安全的，如果应用中存在多线程同时操作该类派生出的实例，注意加锁保护。 
 
 **系统能力：**  SystemCapability.DistributedDataManager.DataShare.Core
 
-| 键类型          | 值类型                                      | 
-| ------------- | --------------------------------------------- | 
-|  string | [ValueType](#valuetype)\| Uint8Array \| null | 
+| 键类型          | 值类型                                      |
+| ------------- | --------------------------------------------- |
+|  string | [ValueType](#valuetype)\| Uint8Array \| null |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-distributed-data.md b/zh-cn/application-dev/reference/apis/js-apis-distributed-data.md
index d2a9c901ca3fe2b2471c0696f14bdf255d48d454..15b3fbb2bf66b253185098d2fac17db9495f3b0e 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-distributed-data.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-distributed-data.md
@@ -129,8 +129,8 @@ try {
 
 | 名称 | 类型 | 必填 | 说明 |
 | ----- | ------ |------ | ------ |
-| userId | string | 否  | 指示要设置的用户ID。 |
-| userType | [UserType](#usertype) | 否  | 指示要设置的用户类型。 |
+| userId | string | 否  | 指示要设置的用户ID，默认为'0'。 |
+| userType | [UserType](#usertype) | 否  | 指示要设置的用户类型，默认为0。 |
 
 
 ## UserType
@@ -268,7 +268,7 @@ const options = {
     backup: false,
     autoSync: true,
     kvStoreType: distributedData.KVStoreType.SINGLE_VERSION,
-    schema: '',
+    schema: undefined,
     securityLevel: distributedData.SecurityLevel.S2,
 }
 try {
@@ -318,7 +318,7 @@ const options = {
     backup: false,
     autoSync: true,
     kvStoreType: distributedData.KVStoreType.SINGLE_VERSION,
-    schema: '',
+    schema: undefined,
     securityLevel: distributedData.SecurityLevel.S2,
 }
 try {
@@ -366,7 +366,7 @@ const options = {
     backup : false,
     autoSync : true,
     kvStoreType : distributedData.KVStoreType.SINGLE_VERSION,
-    schema : '',
+    schema : undefined,
     securityLevel : distributedData.SecurityLevel.S2,
 }
 try {
@@ -415,7 +415,7 @@ const options = {
     backup : false,
     autoSync : true,
     kvStoreType : distributedData.KVStoreType.SINGLE_VERSION,
-    schema : '',
+    schema : undefined,
     securityLevel : distributedData.SecurityLevel.S2,
 }
 try {
@@ -549,7 +549,7 @@ off(event: 'distributedDataServiceDie', deathCallback?: Callback&lt;void&gt;): v
 | 参数名  | 类型 | 必填  | 说明                    |
 | -----  | ------  | ----  | ----------------------- |
 | event  | string | 是    | 取消订阅的事件名，固定为'distributedDataServiceDie'，即服务状态变更事件。 |
-| deathCallback  | Callback&lt;void&gt;  | 否    | 回调函数。 |
+| deathCallback  | Callback&lt;void&gt;  | 否    | 取消订阅的函数。如不设置callback，则取消所有已订阅的函数。 |
 
 
 **示例：**
@@ -575,13 +575,13 @@ try {
 
 | 名称  | 类型 | 必填   | 说明                    |
 | -----  | ------  | ------  | -------------------|
-| createIfMissing  | boolean | 否 | 当数据库文件不存在时是否创建数据库，默认创建。 <br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core    |
-| encrypt  | boolean | 否 |设置数据库文件是否加密，默认不加密。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core     |
-| backup  | boolean | 否 |设置数据库文件是否备份，默认备份。 <br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core    |
-| autoSync  | boolean | 否 |设置数据库文件是否自动同步。默认为false，即手动同步；设置为true时，表示自动同步。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core<br>**需要权限**： ohos.permission.DISTRIBUTED_DATASYNC     |
-| kvStoreType | [KVStoreType](#kvstoretype) | 否 |设置要创建的数据库类型，默认为多设备协同数据库。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core |
-| securityLevel | [SecurityLevel](#securitylevel) | 否 |设置数据库安全级别，默认不设置安全级别。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core  |
-| schema<sup>8+</sup> | [Schema](#schema8) | 否 | 设置定义存储在数据库中的值。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.DistributedKVStore |
+| createIfMissing  | boolean | 否 | 当数据库文件不存在时是否创建数据库，默认为true，即创建。 <br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core    |
+| encrypt  | boolean | 否 |设置数据库文件是否加密，默认为false，即不加密。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core     |
+| backup  | boolean | 否 |设置数据库文件是否备份，默认为true，即备份。 <br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core    |
+| autoSync  | boolean | 否 |设置数据库文件是否自动同步。默认为false，即手动同步；设置为true时，表示自动同步。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core<br>**需要权限**： ohos.permission.DISTRIBUTED_DATASYNC  |
+| kvStoreType | [KVStoreType](#kvstoretype) | 否 |设置要创建的数据库类型，默认为DEVICE_COLLABORATION，即多设备协同数据库。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core |
+| securityLevel | [SecurityLevel](#securitylevel) | 是 |设置数据库安全级别，设置数据库安全级别(S1-S4)。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core  |
+| schema<sup>8+</sup> | [Schema](#schema8) | 否 | 设置定义存储在数据库中的值，默认为undefined，即不设置schema。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.DistributedKVStore |
 
 
 ## KVStoreType
@@ -602,8 +602,8 @@ KVStore数据库类型枚举。
 
 | 名称  | 值 | 说明                    |
 | ---   | ----  | ----------------------- |
-| NO_LEVEL  | 0 | 表示数据库不设置安全级别。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.DistributedKVStore   |
-| S0  | 1 | 表示数据库的安全级别为公共级别。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core    |
+| NO_LEVEL  | 0 | 表示数据库不设置安全级别(已废弃)。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.DistributedKVStore   |
+| S0  | 1 | 表示数据库的安全级别为公共级别(已废弃)。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core    |
 | S1  | 2 | 表示数据库的安全级别为低级别，当数据泄露时会产生较低影响。例如，包含壁纸等系统数据的数据库。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core    |
 | S2  | 3 | 表示数据库的安全级别为中级别，当数据泄露时会产生较大影响。例如，包含录音、视频等用户生成数据或通话记录等信息的数据库。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core    |
 | S3  | 5 | 表示数据库的安全级别为高级别，当数据泄露时会产生重大影响。例如，包含用户运动、健康、位置等信息的数据库。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core    |
@@ -2292,7 +2292,7 @@ off(event:'dataChange', listener?: Callback&lt;ChangeNotification&gt;): void
 | 参数名   | 类型                                                      | 必填 | 说明                                                     |
 | -------- | --------------------------------------------------------- | ---- | -------------------------------------------------------- |
 | event    | string                                                    | 是   | 取消订阅的事件名，固定为'dataChange'，表示数据变更事件。 |
-| listener | Callback&lt;[ChangeNotification](#changenotification)&gt; | 否   | 回调函数。                                               |
+| listener | Callback&lt;[ChangeNotification](#changenotification)&gt; | 否   | 取消订阅的函数。如不设置callback，则取消所有已订阅的函数。 |
 
 
 
@@ -2330,7 +2330,7 @@ off(event: 'syncComplete', syncCallback?: Callback&lt;Array&lt;[string, number]&
 | 参数名       | 类型                                          | 必填 | 说明                                                       |
 | ------------ | --------------------------------------------- | ---- | ---------------------------------------------------------- |
 | event        | string                                        | 是   | 取消订阅的事件名，固定为'syncComplete'，表示同步完成事件。 |
-| syncCallback | Callback&lt;Array&lt;[string, number]&gt;&gt; | 否   | 回调函数。用于向调用方发送同步结果的回调。                 |
+| syncCallback | Callback&lt;Array&lt;[string, number]&gt;&gt; | 否   | 取消订阅的函数。如不设置callback，则取消所有订阅的函数。  |
 
 **示例：**
 
@@ -3769,7 +3769,7 @@ sync(deviceIds: string[], mode: SyncMode, delayMs?: number): void
 | --------- | --------------------- | ---- | ---------------------------------------------- |
 | deviceIds | string[]              | 是   | 同一组网环境下，需要同步的设备的deviceId列表。 |
 | mode      | [SyncMode](#syncmode) | 是   | 同步模式。                                     |
-| delayMs   | number                | 否   | 可选参数，允许延时时间，单位：ms（毫秒）。     |
+| delayMs   | number                | 否   | 可选参数，允许延时时间，单位：ms（毫秒），默认为0。    |
 
 **示例：**
 
@@ -3884,7 +3884,7 @@ off(event:'dataChange', listener?: Callback&lt;ChangeNotification&gt;): void
 | 参数名   | 类型                                                      | 必填 | 说明                                                     |
 | -------- | --------------------------------------------------------- | ---- | -------------------------------------------------------- |
 | event    | string                                                    | 是   | 取消订阅的事件名，固定为'dataChange'，表示数据变更事件。 |
-| listener | Callback&lt;[ChangeNotification](#changenotification)&gt; | 否   | 回调函数。                                               |
+| listener | Callback&lt;[ChangeNotification](#changenotification)&gt; | 否   | 取消订阅的函数。如不设置callback，则取消所有已订阅的函数。  |
 
 **示例：**
 
@@ -3920,7 +3920,7 @@ off(event: 'syncComplete', syncCallback?: Callback&lt;Array&lt;[string, number]&
 | 参数名       | 类型                                          | 必填 | 说明                                                       |
 | ------------ | --------------------------------------------- | ---- | ---------------------------------------------------------- |
 | event        | string                                        | 是   | 取消订阅的事件名，固定为'syncComplete'，表示同步完成事件。 |
-| syncCallback | Callback&lt;Array&lt;[string, number]&gt;&gt; | 否   | 回调函数。用于向调用方发送同步结果的回调。                 |
+| syncCallback | Callback&lt;Array&lt;[string, number]&gt;&gt; | 否   | 取消订阅的函数。如不设置callback，则取消所有订阅的函数。  |
 
 **示例：**
 
@@ -5191,7 +5191,7 @@ sync(deviceIds: string[], mode: SyncMode, delayMs?: number): void
 | -----  | ------   | ----  | ----------------------- |
 | deviceIds    |string[]               | 是    |需要同步DeviceKvStore数据库的设备ID列表。 |
 | mode            |[SyncMode](#syncmode)  | 是    |同步模式。  |
-| delayMs  |number                 | 否    |可选参数，允许延时时间，单位：ms（毫秒）。  |
+| delayMs  |number                 | 否    |可选参数，允许延时时间，单位：ms（毫秒），默认为0。  |
 
 **示例：**
 
@@ -5306,7 +5306,7 @@ off(event:'dataChange', listener?: Callback&lt;ChangeNotification&gt;): void
 | 参数名   | 类型                                                      | 必填 | 说明                                                     |
 | -------- | --------------------------------------------------------- | ---- | -------------------------------------------------------- |
 | event    | string                                                    | 是   | 取消订阅的事件名，固定为'dataChange'，表示数据变更事件。 |
-| listener | Callback&lt;[ChangeNotification](#changenotification)&gt; | 否   | 回调函数。                                               |
+| listener | Callback&lt;[ChangeNotification](#changenotification)&gt; | 否   | 取消订阅的函数。如不设置callback，则取消所有已订阅的函数。 |
 
 **示例：**
 
@@ -5342,7 +5342,7 @@ off(event: 'syncComplete', syncCallback?: Callback&lt;Array&lt;[string, number]&
 | 参数名       | 类型                                          | 必填 | 说明                                                       |
 | ------------ | --------------------------------------------- | ---- | ---------------------------------------------------------- |
 | event        | string                                        | 是   | 取消订阅的事件名，固定为'syncComplete'，表示同步完成事件。 |
-| syncCallback | Callback&lt;Array&lt;[string, number]&gt;&gt; | 否   | 回调函数。用于向调用方发送同步结果的回调。                 |
+| syncCallback | Callback&lt;Array&lt;[string, number]&gt;&gt; | 否   | 取消订阅的函数。如不设置callback，则取消所有订阅的函数。  |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-distributedKVStore.md b/zh-cn/application-dev/reference/apis/js-apis-distributedKVStore.md
index b1ad91bf1933e2558b64303796d3d4062aa9f193..11ef749fc6613fa46e80864e16e6dafee4b9a5ed 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-distributedKVStore.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-distributedKVStore.md
@@ -148,13 +148,13 @@ import distributedKVStore from '@ohos.data.distributedKVStore';
 
 | 名称          | 类型                        | 必填 | 说明                                                         |
 | --------------- | -------------- | ---- | -------------------------|
-| createIfMissing | boolean                         | 否  | 当数据库文件不存在时是否创建数据库，默认创建。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core |
-| encrypt         | boolean                         | 否   | 设置数据库文件是否加密，默认不加密。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core |
-| backup          | boolean                         | 否   | 设置数据库文件是否备份，默认备份。 <br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core |
+| createIfMissing | boolean                         | 否  | 当数据库文件不存在时是否创建数据库，默认为true，即创建。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core |
+| encrypt         | boolean                         | 否   | 设置数据库文件是否加密，默认为false，即不加密。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core |
+| backup          | boolean                         | 否   | 设置数据库文件是否备份，默认为true，即备份。 <br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core |
 | autoSync        | boolean                         | 否   | 设置数据库文件是否自动同步。默认为false，即手动同步；设置为true时，表示自动同步。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core<br>**需要权限**： ohos.permission.DISTRIBUTED_DATASYNC |
-| kvStoreType     | [KVStoreType](#kvstoretype)     | 否   | 设置要创建的数据库类型，默认为多设备协同数据库。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core |
+| kvStoreType     | [KVStoreType](#kvstoretype)     | 否   | 设置要创建的数据库类型，默认为DEVICE_COLLABORATION，即多设备协同数据库。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core |
 | securityLevel   | [SecurityLevel](#securitylevel) | 是   |设置数据库安全级别。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.Core |
-| schema          | [Schema](#schema)               | 否   | 设置定义存储在数据库中的值，默认不使用Schema。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.DistributedKVStore |
+| schema          | [Schema](#schema)               | 否   | 设置定义存储在数据库中的值，默认为undefined, 即不使用Schema。<br>**系统能力：** SystemCapability.DistributedDataManager.KVStore.DistributedKVStore |
 
 ## Schema
 
@@ -448,7 +448,7 @@ const options = {
     backup: false,
     autoSync: true,
     kvStoreType: distributedKVStore.KVStoreType.SINGLE_VERSION,
-    schema: '',
+    schema: undefined,
     securityLevel: distributedKVStore.SecurityLevel.S2,
 }
 try {
@@ -500,7 +500,7 @@ const options = {
     backup: false,
     autoSync: true,
     kvStoreType: distributedKVStore.KVStoreType.SINGLE_VERSION,
-    schema: '',
+    schema: undefined,
     securityLevel: distributedKVStore.SecurityLevel.S2,
 }
 try {
@@ -555,7 +555,7 @@ const options = {
     backup: false,
     autoSync: true,
     kvStoreType: distributedKVStore.KVStoreType.SINGLE_VERSION,
-    schema: '',
+    schema: undefined,
     securityLevel: distributedKVStore.SecurityLevel.S2,
 }
 try {
@@ -619,7 +619,7 @@ const options = {
     backup: false,
     autoSync: true,
     kvStoreType: distributedKVStore.KVStoreType.SINGLE_VERSION,
-    schema: '',
+    schema: undefined,
     securityLevel: distributedKVStore.SecurityLevel.S2,
 }
 try {
@@ -4499,7 +4499,7 @@ sync(deviceIds: string[], mode: SyncMode, delayMs?: number): void
 | --------- | --------------------- | ---- | ---------------------------------------------- |
 | deviceIds | string[]              | 是   | 同一组网环境下，需要同步的设备的deviceId列表。 |
 | mode      | [SyncMode](#syncmode) | 是   | 同步模式。                                     |
-| delayMs   | number                | 否   | 可选参数，允许延时时间，单位：ms（毫秒）。     |
+| delayMs   | number                | 否   | 可选参数，允许延时时间，单位：ms（毫秒），默认为0。     |
 
 **错误码：**
 
@@ -4570,7 +4570,7 @@ sync(deviceIds: string[], query: Query, mode: SyncMode, delayMs?: number): void
 | deviceIds | string[]              | 是   | 同一组网环境下，需要同步的设备的deviceId列表。 |
 | mode      | [SyncMode](#syncmode) | 是   | 同步模式。                                     |
 | query     | [Query](#query)        | 是   | 表示数据库的查询谓词条件                       |
-| delayMs   | number                | 否   | 可选参数，允许延时时间，单位：ms（毫秒）。     |
+| delayMs   | number                | 否   | 可选参数，允许延时时间，单位：ms（毫秒），默认为0。     |
 
 **错误码：**
 
@@ -4710,7 +4710,7 @@ off(event:'dataChange', listener?: Callback&lt;ChangeNotification&gt;): void
 | 参数名   | 类型                                                  | 必填 | 说明                                                     |
 | -------- | --------------------------------------------------------- | ---- | -------------------------------------------------------- |
 | event    | string                                                    | 是   | 取消订阅的事件名，固定为'dataChange'，表示数据变更事件。 |
-| listener | Callback&lt;[ChangeNotification](#changenotification)&gt; | 否   | 回调函数。                                               |
+| listener | Callback&lt;[ChangeNotification](#changenotification)&gt; | 否   | 取消订阅的函数。如不设置callback，则取消所有已订阅的函数。  |
 
 **错误码：**
 
@@ -4764,7 +4764,7 @@ off(event: 'syncComplete', syncCallback?: Callback&lt;Array&lt;[string, number]&
 | 参数名       | 类型                                      | 必填 | 说明                                                       |
 | ------------ | --------------------------------------------- | ---- | ---------------------------------------------------------- |
 | event        | string                                        | 是   | 取消订阅的事件名，固定为'syncComplete'，表示同步完成事件。 |
-| syncCallback | Callback&lt;Array&lt;[string, number]&gt;&gt; | 否   | 回调函数。用于向调用方发送同步结果的回调。                 |
+| syncCallback | Callback&lt;Array&lt;[string, number]&gt;&gt; | 否   | 取消订阅的函数。如不设置callback，则取消所有已订阅的函数。  |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-distributedMissionManager.md b/zh-cn/application-dev/reference/apis/js-apis-distributedMissionManager.md
index d346ef568f3ba995f77b8c2b2a7adccc65ec73bb..c5f817c83f7f8940ceca599bffde8e812c356d3c 100755
--- a/zh-cn/application-dev/reference/apis/js-apis-distributedMissionManager.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-distributedMissionManager.md
@@ -360,7 +360,7 @@ continueMission(parameter: ContinueDeviceInfo, options: ContinueCallback, callba
 
 迁移任务，以回调函数的方式返回。
 
-**需要权限**：ohos.permission.MANAGE_MISSIONS and ohos.permission.DISTRIBUTED_DATASYNC
+**需要权限**：ohos.permission.MANAGE_MISSIONS，ohos.permission.DISTRIBUTED_DATASYNC
 
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Mission
 
@@ -418,7 +418,7 @@ continueMission(parameter: ContinueDeviceInfo, options: ContinueCallback): Promi
 
 迁移任务，以promise方式返回执行结果。
 
-**需要权限**：ohos.permission.MANAGE_MISSIONS and ohos.permission.DISTRIBUTED_DATASYNC
+**需要权限**：ohos.permission.MANAGE_MISSIONS，ohos.permission.DISTRIBUTED_DATASYNC
 
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Mission
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-file-fs.md b/zh-cn/application-dev/reference/apis/js-apis-file-fs.md
index 4ea383375125b9a300ee67cf22eec96793f87f5b..c307849df40e84c09340334b44a3ff6f120e1409 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-file-fs.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-file-fs.md
@@ -2573,7 +2573,7 @@ close(callback: AsyncCallback&lt;void&gt;): void
     if (err) {
       console.info("close stream failed with error message: " + err.message + ", error code: " + err.code);
     } else {
-      console.info("close stream success"):
+      console.info("close stream success");
     }
   });
   ```
diff --git a/zh-cn/application-dev/reference/apis/js-apis-fileio.md b/zh-cn/application-dev/reference/apis/js-apis-fileio.md
index efe98724675e4d6daadc3a9ccf14e4492bd65cc4..cab660a6d71054a0ac5af34e2691bddd4a1a9119 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-fileio.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-fileio.md
@@ -20,8 +20,9 @@ import fileio from '@ohos.fileio';
 **Stage模型**
 
  ```js
-import Ability from '@ohos.application.Ability';
-class MainAbility extends Ability {
+import UIAbility from '@ohos.app.ability.UIAbility';
+
+export default class EntryAbility extends UIAbility {
     onWindowStageCreate(windowStage) {
         let context = this.context;
         let pathDir = context.filesDir;
@@ -29,19 +30,18 @@ class MainAbility extends Ability {
 }
  ```
 
- Stage模型context的具体获取方法参见[Stage模型](js-apis-inner-application-uiAbilityContext.md)。
-
 **FA模型**
 
  ```js
  import featureAbility from '@ohos.ability.featureAbility';
+ 
  let context = featureAbility.getContext();
  context.getFilesDir().then((data) => {
       let pathDir = data;
  })
  ```
- 
- FA模型context的具体获取方法参见[FA模型](js-apis-inner-app-context.md#Context模块)。
+
+FA模型context的具体获取方法参见[FA模型](js-apis-inner-app-context.md#Context模块)。
 
 ## fileio.stat
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-ability-connectOptions.md b/zh-cn/application-dev/reference/apis/js-apis-inner-ability-connectOptions.md
index ccac9612b0dfd4dea03a01aa7506a6970d9f172a..9c92bed376f3233443321ecebedff5008e3b9600 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-ability-connectOptions.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-ability-connectOptions.md
@@ -2,6 +2,10 @@
 
 在连接指定的后台服务时作为入参用于接收连接过程中的状态变化，如作为[connectServiceExtensionAbility](js-apis-inner-application-serviceExtensionContext.md#serviceextensioncontextconnectserviceextensionability)的入参连接指定的ServiceExtensionAbility。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 7开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。  
+
 ## 导入模块
 
 ```ts
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-ability-dataAbilityHelper.md b/zh-cn/application-dev/reference/apis/js-apis-inner-ability-dataAbilityHelper.md
index 3eaf81fc83ef75124d41ea14d93b75530dc309b5..6a1e8e26a4195c470e9de1defd5d5125e50f4c7b 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-ability-dataAbilityHelper.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-ability-dataAbilityHelper.md
@@ -110,7 +110,7 @@ let DAHelper: ability.DataAbilityHelper = featureAbility.acquireDataAbilityHelpe
 function onChangeNotify() {
     console.info('==========================>onChangeNotify=======================>');
 };
-helper.on(
+DAHelper.on(
     'dataChange',
     'dataability:///com.example.DataAbility',
     onChangeNotify
@@ -143,11 +143,11 @@ let DAHelper: ability.DataAbilityHelper = featureAbility.acquireDataAbilityHelpe
 function onChangeNotify() {
     console.info('==========================>onChangeNotify=======================>');
 };
-helper.off(
+DAHelper.off(
     'dataChange',
     'dataability:///com.example.DataAbility',
 );
-helper.off(
+DAHelper.off(
     'dataChange',
     'dataability:///com.example.DataAbility',
     onChangeNotify
@@ -420,7 +420,7 @@ import featureAbility from '@ohos.ability.featureAbility';
 let DAHelper: ability.DataAbilityHelper = featureAbility.acquireDataAbilityHelper(
     'dataability:///com.example.DataAbility'
 );
-helper.notifyChange('dataability:///com.example.DataAbility', (err) => {
+DAHelper.notifyChange('dataability:///com.example.DataAbility', (err) => {
     console.info('==========================>Called=======================>');
 });
 ```
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-app-context.md b/zh-cn/application-dev/reference/apis/js-apis-inner-app-context.md
index f8064bb1fa496bb2e118b66b5a7d07096cb5deb9..fb5043e46e6754bb4c98f31d32bc0a1a32dd79d4 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-app-context.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-app-context.md
@@ -106,7 +106,7 @@ import featureAbility from '@ohos.ability.featureAbility';
 import bundle from '@ohos.bundle.bundleManager';
 let context: featureAbility.Context = featureAbility.getContext();
 bundle.getBundleInfo('com.context.test', 1, (err, datainfo) =>{
-    context.verifyPermission('com.example.permission', {uid:datainfo.uid}, (err, data) =>{
+    context.verifyPermission('com.example.permission', {uid:datainfo.appInfo.uid}, (err, data) =>{
         console.info('verifyPermission err: ' + JSON.stringify(err) + 'data: ' + JSON.stringify(data));
     });
 });
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityDelegatorArgs.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityDelegatorArgs.md
index 7699b30dab5f216e6811743a9e62e816c400f115..46ca85a99a6091fe5ef6986ed571d2c43d88b6f7 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityDelegatorArgs.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityDelegatorArgs.md
@@ -32,7 +32,5 @@ import AbilityDelegatorRegistry from '@ohos.app.ability.abilityDelegatorRegistry
 **示例：**
 
 ```ts
-import AbilityDelegatorRegistry from '@ohos.application.abilityDelegatorRegistry';
-
 let args: AbilityDelegatorRegistry.AbilityDelegatorArgs = AbilityDelegatorRegistry.getArguments();
 ```
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityMonitor.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityMonitor.md
index c37e06946edc93f6445be638ec35a77be09dae80..741f1cb4df29678ce2d0a861528c972f110b760b 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityMonitor.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityMonitor.md
@@ -37,8 +37,6 @@ Ability监听器
 **示例：**
 
 ```ts
-import AbilityDelegatorRegistry from '@ohos.application.abilityDelegatorRegistry';
-
 function onAbilityCreateCallback(data) {
     console.info('onAbilityCreateCallback');
 }
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityStageMonitor.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityStageMonitor.md
index 8f750ec63bab2a46beddaff51ceafed4ad89969a..ba0cb0ff2816ccfd7997c49b613c1b7bf8bf3156 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityStageMonitor.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityStageMonitor.md
@@ -2,13 +2,16 @@
 
 提供用于匹配满足指定条件的受监视的AbilityStage对象的方法。最近匹配的AbilityStage对象将保存在AbilityStageMonitor对象中。 
 
+> **说明：**
+> 
+> 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。  
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Ability.AbilityRuntime.Core
 
 | 名称                                                         | 类型     | 可读 | 可写 | 说明                                                         |
 | ------------------------------------------------------------ | -------- | ---- | ---- | ------------------------------------------------------------ |
-| moduleName<sup>9+</sup>                                                 | string   | 是   | 是   | 要监视的abilityStage的模块名。 |
-| srcEntrance<sup>9+</sup> | string | 是   | 是   | 要监视的abilityStage的源路径。 |
+| moduleName                                                 | string   | 是   | 是   | 要监视的abilityStage的模块名。 |
+| srcEntrance | string | 是   | 是   | 要监视的abilityStage的源路径。 |
 
 **示例：**
 ```ts
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityStateData.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityStateData.md
index 846c202e4c04463ae033c5493544369a7e70b322..583121d76c9040c250dbdd70f18d06e8b592418b 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityStateData.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-abilityStateData.md
@@ -2,6 +2,10 @@
 
 定义Ability状态信息，可以通过[registerApplicationStateObserver](js-apis-application-appManager.md#appmanagerregisterapplicationstateobserver8)注册生命周期变化监听后，通过[ApplicationStateObserver](js-apis-inner-application-applicationStateObserver.md)的onAbilityStateChanged生命周期回调获取。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 8开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。  
+
 ## 导入模块
 
 ```ts
@@ -12,11 +16,30 @@ import appManager from '@ohos.application.appManager';
 
 | 名称                     | 类型     | 可读 | 可写 | 说明                       |
 | ----------------------- | ---------| ---- | ---- | ------------------------- |
-| pid<sup>8+</sup>                     | number   | 是   | 否   | 进程ID。                    |
-| bundleName<sup>8+</sup>              | string   | 是   | 否  | 应用包名。                  |
-| abilityName<sup>8+</sup>             | string   | 是   | 否   | Ability名称。               |
-| uid<sup>8+</sup>                     | number   | 是   | 否   | 用户ID。                  |
-| state<sup>8+</sup>                   | number   | 是   | 否   | Ability状态。                |
-| moduleName<sup>9+</sup> | string   | 是   | 否   | Ability所属的HAP包的名称。    |
-| abilityType<sup>8+</sup> | string   | 是   | 否   | Ability类型：页面或服务等。 |
+| pid                     | number   | 是   | 否   | 进程ID。                    |
+| bundleName              | string   | 是   | 否  | 应用Bundle名称。          |
+| abilityName            | string   | 是   | 否   | Ability名称。               |
+| uid                    | number   | 是   | 否   | 用户ID。                  |
+| state                   | number   | 是   | 否   | [Ability状态](#ability状态)。                |
+| moduleName<sup>9+</sup> | string   | 是   | 否   | Ability所属的HAP的名称。    |
+| abilityType | number | 是   | 否   | [Ability类型](#ability类型)：页面或服务等。 |
+
+#### Ability状态
+| 值   | 状态                       | 说明                   |
+| ---- | -------------------------- | ---------------------- |
+| 0    | ABILITY_STATE_CREATE       | Ability正在创建中      |
+| 1    | ABILITY_STATE_READY        | Ability已创建完成      |
+| 2    | ABILITY_STATE_FOREGROUND   | Ability处于前台        |
+| 3    | ABILITY_STATE_FOCUS        | Ability已经获焦        |
+| 4    | ABILITY_STATE_BACKGROUND   | Ability处于后台        |
+| 5    | ABILITY_STATE_TERMINATED   | Ability已经销毁        |
+| 8    | ABILITY_STATE_CONNECTED    | 后台服务已被客户端连接 |
+| 9    | ABILITY_STATE_DISCONNECTED | 后台服务客户端断开连接 |
+
+#### Ability类型
 
+| 值   | 状态    | 说明                  |
+| ---- | ------- | --------------------- |
+| 0    | UNKNOWN | 未知类型              |
+| 1    | PAGE    | UI界面类型的Ability   |
+| 2    | SERVICE | 后台服务类型的Ability |
\ No newline at end of file
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-applicationContext.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-applicationContext.md
index 7bc37cd46350e4e55be360556add0e59f8316f90..38939d982165cda11611b8d80722cc76058e89c8 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-applicationContext.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-applicationContext.md
@@ -301,7 +301,6 @@ getRunningProcessInformation(): Promise\<Array\<ProcessInformation>>;
 **示例：**
 
 ```ts
-let applicationContext = this.context.getApplicationContext();
 applicationContext.getRunningProcessInformation().then((data) => {
     console.log('The process running information is:' + JSON.stringify(data));
 }).catch((error) => {
@@ -339,7 +338,6 @@ getRunningProcessInformation(callback: AsyncCallback\<Array\<ProcessInformation>
 **示例：**
 
 ```ts
-let applicationContext = this.context.getApplicationContext();
 applicationContext.getRunningProcessInformation((err, data) => {
     if (err.code !== 0) {
         console.error('getRunningProcessInformation faile, err: ' + JSON.stringify(err));
@@ -407,10 +405,16 @@ killProcessesBySelf(callback: AsyncCallback\<void>);
 **示例：**
 
 ```ts
+<<<<<<< HEAD
 let applicationContext = this.context.getApplicationContext();
 applicationContext.killProcessesBySelf(err => {
     if (err.code !== 0) {
         console.error('killProcessesBySelf faile, err: ' + JSON.stringify(err));
+=======
+applicationContext.killAllProcesses(error => {
+    if (error) {
+        console.error('killAllProcesses fail, error: ${JSON.stringify(error)}');
+>>>>>>> 9643df3c1b (Fix document consistency issues of ability)
     }
 })
 ```
\ No newline at end of file
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-applicationStateObserver.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-applicationStateObserver.md
index 3468d620a6ac5d9a4d87275240ae55ffbf2b0a29..b60fa747916db81f0029cb8879f10ff22f185538 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-applicationStateObserver.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-applicationStateObserver.md
@@ -2,10 +2,14 @@
 
 定义应用状态监听，可以作为[registerApplicationStateObserver](js-apis-application-appManager.md#appmanagerregisterapplicationstateobserver8)的入参监听当前应用的生命周期变化。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 8开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。 
+
 ## 导入模块
 
 ```ts
-import appManager from '@ohos.application.appManager';
+import appManager from '@ohos.app.ability.appManager';
 ```
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Ability.AbilityRuntime.Core
@@ -14,16 +18,14 @@ import appManager from '@ohos.application.appManager';
 
 | 名称                     |                      | 类型     | 可读 | 可写 | 说明                       |
 | ----------------------- | ---------| ---- | ---- | ------------------------- | ------------------------- |
-| onForegroundApplicationChanged<sup>8+</sup>         | [AppStateData](js-apis-inner-application-appStateData.md) | AsyncCallback\<void>   | 是   | 否   | 应用前后台状态发生变化时执行的回调函数。                    |
-| onAbilityStateChanged<sup>8+</sup>  | [AbilityStateData](js-apis-inner-application-abilityStateData.md) | AsyncCallback\<void>   | 是   | 否  | ability状态发生变化时执行的回调函数。                  |
-| onProcessCreated<sup>8+</sup>         | [ProcessData](js-apis-inner-application-processData.md) | AsyncCallback\<void>   | 是   | 否   | 进程创建时执行的回调函数。                  |
-| onProcessDied<sup>8+</sup>         | [ProcessData](js-apis-inner-application-processData.md) | AsyncCallback\<void>   | 是   | 否   | 进程销毁时执行的回调函数。                  |
-| onProcessStateChanged<sup>8+</sup>         | [ProcessData](js-apis-inner-application-processData.md) | AsyncCallback\<void>   | 是   | 否   | 进程状态更新时执行的回调函数。                  |
+| onForegroundApplicationChanged         | [AppStateData](js-apis-inner-application-appStateData.md) | AsyncCallback\<void>   | 是   | 否   | 应用前后台状态发生变化时执行的回调函数。                    |
+| onAbilityStateChanged  | [AbilityStateData](js-apis-inner-application-abilityStateData.md) | AsyncCallback\<void>   | 是   | 否  | ability状态发生变化时执行的回调函数。                  |
+| onProcessCreated        | [ProcessData](js-apis-inner-application-processData.md) | AsyncCallback\<void>   | 是   | 否   | 进程创建时执行的回调函数。                  |
+| onProcessDied         | [ProcessData](js-apis-inner-application-processData.md) | AsyncCallback\<void>   | 是   | 否   | 进程销毁时执行的回调函数。                  |
+| onProcessStateChanged<sup>9+</sup>         | [ProcessData](js-apis-inner-application-processData.md) | AsyncCallback\<void>   | 是   | 否   | 进程状态更新时执行的回调函数。                  |
 
 **示例：**
 ```ts
-import appManager from "@ohos.application.appManager";
-
 let applicationStateObserver = {
     onForegroundApplicationChanged(appStateData) {
         console.log('onForegroundApplicationChanged appStateData: ' +  JSON.stringify(appStateData));
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-context.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-context.md
index 851287ab994b10c72d934e7ff49b71813c36582e..7392ce38bee4593061df4728a1cc173db00aad02 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-context.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-context.md
@@ -122,16 +122,12 @@ createModuleContext(bundleName: string, moduleName: string): Context;
 **示例：**
 
 ```ts
-<<<<<<< HEAD
-let moduleContext = this.context.createModuleContext('com.example.test', 'entry');
-=======
 let moduleContext: common.Context;
 try {
     moduleContext = this.context.createModuleContext('com.example.test', 'entry');
 } catch (error) {
     console.error('createModuleContext failed, error.code: ${error.code}, error.message: ${error.message}');
 }
->>>>>>> 48a75c8e72 (Modify the secondary import module of ability)
 ```
 
 ## Context.getApplicationContext
@@ -151,16 +147,12 @@ getApplicationContext(): ApplicationContext;
 **示例：**
 
 ```ts
-<<<<<<< HEAD
-let applicationContext = this.context.getApplicationContext();
-=======
 let applicationContext: common.Context;
 try {
     applicationContext = this.context.getApplicationContext();
 } catch (error) {
     console.error('getApplicationContext failed, error.code: ${error.code}, error.message: ${error.message}');
 }
->>>>>>> 48a75c8e72 (Modify the secondary import module of ability)
 ```
 
 ## AreaMode
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-continueCallback.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-continueCallback.md
index 7e12ce10bfa691c8b269e27c228ad15c6d666ff4..22124268817373e77de4add9972e275c740b14d4 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-continueCallback.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-continueCallback.md
@@ -1,6 +1,16 @@
 # ContinueCallback
 
-表示迁移完成后，返回迁移结果回调函数，可以作为[continueMission](js-apis-distributedMissionManager.md#distributedmissionmanagercontinuemission)的入参监听迁移回调。
+表示跨设备迁移Mission完成后，返回迁移结果的回调函数，迁移Mission详见：[continueMission接口](js-apis-distributedMissionManager.md#distributedmissionmanagercontinuemission)。
+
+> **说明：**
+> 
+> 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。 
+
+## ContinueCallback.onContinueDone
+
+onContinueDone(result: number): void;
+
+Mission迁移完成后调用，返回迁移结果。
 
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Mission
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-continueDeviceInfo.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-continueDeviceInfo.md
index 39761db2a1a146612252ed60368d266b2f3392e2..ea1ee33f71e676a99813838f6a71650908ee41b9 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-continueDeviceInfo.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-continueDeviceInfo.md
@@ -2,6 +2,10 @@
 
 表示发起任务迁移时所需参数的枚举，可以作为[continueMission](js-apis-distributedMissionManager.md#distributedmissionmanagercontinuemission)的入参指定迁移相关参数。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
+
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Mission
 
 | 名称       | 类型   | 可读   | 可写   | 说明      |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-errorObserver.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-errorObserver.md
index e6caa78afe4f545ca227f8ce2442ad88c224bbff..3ad1659ef10a890aa3b6bdff12cc41d99f5f6aa3 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-errorObserver.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-errorObserver.md
@@ -2,6 +2,10 @@
 
 定义异常监听，可以作为[errorManager.on](js-apis-app-ability-errorManager.md#errormanageron)的入参监听当前应用发生的异常。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。 
+
 ## 导入模块
 
 ```ts
@@ -28,9 +32,15 @@ onUnhandledException(errMsg: string): void;
 import errorManager from '@ohos.app.ability.errorManager';
 
 let observer = {
-    onUnhandledException(errorMsg) {
-        console.log('onUnhandledException, errorMsg: ' + JSON.stringify(errorMsg));
-    }
+  onUnhandledException(errorMsg) {
+    console.error('onUnhandledException, errorMsg: ', errorMsg);
+  }
 };
-errorManager.on('error',observer);
+
+try {
+    errorManager.on('error', observer);
+} catch (error) {
+    console.error('registerErrorObserver failed, error.code: ${error.code}, error.message: ${error.message}');
+}
+```
 ```
\ No newline at end of file
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionCallbacks.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionCallbacks.md
index a4885d4fdd916d0355ca438c63961d7afd1e91e4..085745b151d4cc16e43e88f01ad2a8f56bbed11d 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionCallbacks.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionCallbacks.md
@@ -2,6 +2,10 @@
 
 作为可以[registerMissionListener](js-apis-distributedMissionManager.md#distributedmissionmanagerregistermissionlistener)的入参，表示开始同步后，建立的回调函数。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。 
+
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Mission
 
 | 名称                                                 | 类型     | 可读 | 可写 | 说明                               |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionInfo.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionInfo.md
index 089302a56f68934b99a2daf4007ea8af0a0b77fa..0015992f7204545c9f23009169ad202074aaed1e 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionInfo.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionInfo.md
@@ -2,6 +2,10 @@
 
 表示Ability对应的任务信息，可以通过[getMissionInfo](js-apis-app-ability-missionManager.md#missionmanagergetmissioninfo)获取。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 8开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。 
+
 ## 导入模块
 
 ```ts
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionListener.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionListener.md
index fc7e9d754e9bdacfd0496bfdbbb3184c178dac71..4bf839e5f18c8406ec1650209cab2c54d2909ef2 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionListener.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionListener.md
@@ -2,6 +2,10 @@
 
 定义系统任务状态监听，可以通过[registerMissionListener](js-apis-application-missionManager.md#missionmanagerregistermissionlistener)注册。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 8开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。 
+
 ## 导入模块
 
 ```ts
@@ -16,9 +20,9 @@ import missionManager from '@ohos.app.ability.missionManager';
 | onMissionDestroyed   | function               | 否   | 表示当系统销毁任务时回调执行。 |
 | onMissionSnapshotChanged   | function               | 否   | 表示当系统更新任务缩略图时回调执行。 |
 | onMissionMovedToFront   | function               | 否   | 表示当系统将任务移动到前台时回调执行。 |
-| onMissionLabelUpdated   | function               | 否   | 表示当系统更新任务标签时回调执行。 |
-| onMissionIconUpdated   | function               | 否   | 表示当系统更新任务图标时回调执行。 |
-| onMissionClosed   | function               | 否   | 表示当系统关闭任务时回调执行。 |
+| onMissionLabelUpdated<sup>9+</sup>   | function               | 否   | 表示当系统更新任务标签时回调执行。 |
+| onMissionIconUpdated<sup>9+</sup>   | function               | 否   | 表示当系统更新任务图标时回调执行。 |
+| onMissionClosed<sup>9+</sup>   | function               | 否   | 表示当系统关闭任务时回调执行。 |
 
 **示例：**
 ```ts
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionParameter.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionParameter.md
index e96ca676a567a6cc8302d565959fb7a155aff663..b8fe388bb031287199e7f8250e41ad403eadaa71 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionParameter.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-missionParameter.md
@@ -2,6 +2,10 @@
 
 作为[startSyncRemoteMissions](js-apis-distributedMissionManager.md#distributedmissionmanagerstartsyncremotemissions)的入参，表示同步时所需参数的枚举。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。 
+
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Mission
 
 | 名称          | 类型    | 可读   | 可写   | 说明          |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-processData.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-processData.md
index cc7947bd6fccc05e80ad3fdaf28e589cc00edd9f..6bcaf701ab97810e91181c53b94c03d6ac29e52f 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-processData.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-processData.md
@@ -2,10 +2,14 @@
 
 定义进程数据，可以通过[registerApplicationStateObserver](js-apis-application-appManager.md#appmanagerregisterapplicationstateobserver8)注册生命周期变化监听后，通过[ApplicationStateObserver](js-apis-inner-application-applicationStateObserver.md)的onProcessCreated生命周期回调获取。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 8开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。 
+
 ## 导入模块
 
 ```ts
-import appManager from '@ohos.app.ability.appManager';
+import appManager from '@ohos.application.appManager';
 ```
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Ability.AbilityRuntime.Core
@@ -14,11 +18,12 @@ import appManager from '@ohos.app.ability.appManager';
 
 | 名称                     | 类型     | 可读 | 可写 | 说明                       |
 | ----------------------- | ---------| ---- | ---- | ------------------------- |
-| pid<sup>8+</sup>         | number   | 是   | 否   | 进程ID。                    |
-| bundleName<sup>8+</sup>  | string   | 是   | 否  | 应用包名。                  |
-| uid<sup>8+</sup>         | number   | 是   | 否   | 用户ID。                  |
-| isContinuousTask<sup>9+</sup>         | boolean   | 是   | 否   | 判断过程是否为连续任务。                  |
-| isKeepAlive<sup>9+</sup>         | boolean   | 是   | 否   | 判断该过程是否保持活跃。                  |
+| pid         | number   | 是   | 否   | 进程ID。                    |
+| bundleName  | string   | 是   | 否  | 应用包名。                  |
+| uid         | number   | 是   | 否   | 应用的uid。                  |
+| isContinuousTask<sup>9+</sup>         | boolean   | 是   | 否   | 是否为长时任务，true表示是，false表示不是                 |
+| isKeepAlive<sup>9+</sup>         | boolean   | 是   | 否   | 是否为常驻进程，true表示是，false表示不是                   |
+| state<sup>9+</sup>       | number   | 是   | 否   | 应用的状态，取值及对应的状态为：0(刚创建)，2(前台)，4(后台)，5(已终止)。     |
 
 **示例：**
 ```ts
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-shellCmdResult.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-shellCmdResult.md
index bb23f702159063e6613223c95b089c0b0a3b96dc..792c894c2fb28e0690f75a22c5270312097421c1 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-shellCmdResult.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-shellCmdResult.md
@@ -25,7 +25,6 @@ import AbilityDelegatorRegistry from '@ohos.app.ability.abilityDelegatorRegistry
 
 **示例：**
 ```ts
-import AbilityDelegatorRegistry from '@ohos.app.ability.abilityDelegatorRegistry';
 let abilityDelegator: AbilityDelegatorRegistry.AbilityDelegator;
 let cmd = 'cmd';
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-application-uiAbilityContext.md b/zh-cn/application-dev/reference/apis/js-apis-inner-application-uiAbilityContext.md
index 15f0510cc54690e9b79de8253983b311bfe86ca7..656a73101d79b00861c783f2dd62d735880b885d 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-application-uiAbilityContext.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-application-uiAbilityContext.md
@@ -366,23 +366,20 @@ startAbilityForResult(want: Want, options: StartOptions, callback: AsyncCallback
     windowMode: 0,
   };
 
-  try {
-    this.context.startAbilityForResult(want, options, (error, result) => {
-      if (error.code) {
-        // 处理业务逻辑错误
-        console.log('startAbilityForResult failed, error.code: ' + JSON.stringify(error.code) +
-          ' error.message: ' + JSON.stringify(error.message));
-        return;
-      }
-      // 执行正常业务
-      console.log('startAbilityForResult succeed, result.resultCode = ' +
-        result.resultCode)
-    });
-  } catch (paramError) {
-    // 处理入参错误异常
-    console.log('error.code: ' + JSON.stringify(paramError.code) +
-      ' error.message: ' + JSON.stringify(paramError.message));
-  }
+try {
+  this.context.startAbilityForResult(want, options, (err, result) => {
+    if (err.code) {
+      // 处理业务逻辑错误
+      console.error(`startAbilityForResult failed, code is ${err.code}, message is ${err.message}`);
+      return;
+    }
+    // 执行正常业务
+    console.info('startAbilityForResult succeed');
+  });
+} catch (err) {
+  // 处理入参错误异常
+  console.error(`startAbilityForResult failed, code is ${err.code}, message is ${err.message}`);
+}
   ```
 
 
@@ -785,22 +782,20 @@ startServiceExtensionAbility(want: Want): Promise\<void>;
     abilityName: 'MainAbility'
   };
 
-  try {
-    this.context.startServiceExtensionAbility(want)
-      .then((data) => {
-        // 执行正常业务
-        console.log('startServiceExtensionAbility succeed');
-      })
-      .catch((error) => {
-        // 处理业务逻辑错误
-        console.log('startServiceExtensionAbility failed, error.code: ' + JSON.stringify(error.code) +
-          ' error.message: ' + JSON.stringify(error.message));
-      });
-  } catch (paramError) {
-    // 处理入参错误异常
-    console.log('error.code: ' + JSON.stringify(paramError.code) +
-      ' error.message: ' + JSON.stringify(paramError.message));
-  }
+try {
+  this.context.startServiceExtensionAbility(want)
+    .then(() => {
+      // 执行正常业务
+      console.info('startServiceExtensionAbility succeed');
+    })
+    .catch((err) => {
+      // 处理业务逻辑错误
+      console.error(`startServiceExtensionAbility failed, code is ${err.code}, message is ${err.message}`);
+    });
+} catch (err) {
+  // 处理入参错误异常
+  console.error(`startServiceExtensionAbility failed, code is ${err.code}, message is ${err.message}`);
+}
   ```
 
 ## UIAbilityContext.startServiceExtensionAbilityWithAccount
@@ -1410,15 +1405,22 @@ connectServiceExtensionAbility(want: Want, options: ConnectOptions): number;
 **示例：**
 
   ```ts
-  let want = {
-    deviceId: '',
-    bundleName: 'com.extreme.test',
-    abilityName: 'MainAbility'
-  };
-  let options = {
-    onConnect(elementName, remote) { console.log('----------- onConnect -----------') },
-    onDisconnect(elementName) { console.log('----------- onDisconnect -----------') },
-    onFailed(code) { console.log('----------- onFailed -----------') }
+let want = {
+  deviceId: '',
+  bundleName: 'com.example.myapplication',
+  abilityName: 'ServiceExtensionAbility'
+};
+let commRemote;
+let options = {
+  onConnect(elementName, remote) {
+    commRemote = remote;
+    console.info('onConnect...')
+  },
+  onDisconnect(elementName) {
+    console.info('onDisconnect...')
+  },
+  onFailed(code) {
+    console.info('onFailed...')
   }
 
   let connection = null;
@@ -1472,16 +1474,23 @@ connectServiceExtensionAbilityWithAccount(want: Want, accountId: number, options
 **示例：**
 
   ```ts
-  let want = {
-    deviceId: '',
-    bundleName: 'com.extreme.test',
-    abilityName: 'MainAbility'
-  };
-  let accountId = 100;
-  let options = {
-    onConnect(elementName, remote) { console.log('----------- onConnect -----------') },
-    onDisconnect(elementName) { console.log('----------- onDisconnect -----------') },
-    onFailed(code) { console.log('----------- onFailed -----------') }
+let want = {
+  deviceId: '',
+  bundleName: 'com.example.myapplication',
+  abilityName: 'ServiceExtensionAbility'
+};
+let accountId = 100;
+let commRemote;
+let options = {
+  onConnect(elementName, remote) {
+    commRemote = remote;
+    console.info('onConnect...')
+  },
+  onDisconnect(elementName) {
+    console.info('onDisconnect...')
+  },
+  onFailed(code) {
+    console.info('onFailed...')
   }
 
   let connection = null;
@@ -1526,8 +1535,8 @@ disconnectServiceExtensionAbility(connection: number): Promise\<void>;
 **示例：**
 
   ```ts
-  // connection为connectServiceExtensionAbility中的返回值
-  let connection = 1;
+// connection为connectServiceExtensionAbility中的返回值
+let connection = 1;
 
   try {
     this.context.disconnectServiceExtensionAbility(connection)
@@ -1574,8 +1583,26 @@ disconnectServiceExtensionAbility(connection: number, callback:AsyncCallback\<vo
 **示例：**
 
   ```ts
-  // connection为connectServiceExtensionAbility中的返回值
-  let connection = 1;
+// connection为connectServiceExtensionAbility中的返回值
+let connection = 1;
+let commRemote;
+
+try {
+  this.context.disconnectServiceExtensionAbility(connection, (err) => {
+    commRemote = null;
+    if (err.code) {
+      // 处理业务逻辑错误
+      console.error(`disconnectServiceExtensionAbility failed, code is ${err.code}, message is ${err.message}`);
+      return;
+    }
+    // 执行正常业务
+    console.info('disconnectServiceExtensionAbility succeed');
+  });
+} catch (err) {
+  commRemote = null;
+  // 处理入参错误异常
+  console.error(`disconnectServiceExtensionAbility failed, code is ${err.code}, message is ${err.message}`);
+}
 
   try {
     this.context.disconnectServiceExtensionAbility(connection, (error) => {
@@ -1931,7 +1958,7 @@ requestPermissionsFromUser(permissions: Array&lt;string&gt;, requestCallback: As
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
 | permissions | Array&lt;string&gt; | 是 | 权限列表。 |
-| callback | AsyncCallback&lt;[PermissionRequestResult](js-apis-permissionRequestResult.md)&gt; | 是 | 回调函数，返回接口调用是否成功的结果。 |
+| callback | AsyncCallback&lt;[PermissionRequestResult](js-apis-permissionrequestresult.md)&gt; | 是 | 回调函数，返回接口调用是否成功的结果。 |
 
 **示例：**
 
@@ -1962,7 +1989,7 @@ requestPermissionsFromUser(permissions: Array&lt;string&gt;) : Promise&lt;Permis
 
 | 类型 | 说明 |
 | -------- | -------- |
-| Promise&lt;[PermissionRequestResult](js-apis-permissionRequestResult.md)&gt; | 返回一个Promise，包含接口的结果。 |
+| Promise&lt;[PermissionRequestResult](js-apis-permissionrequestresult.md)&gt; | 返回一个Promise，包含接口的结果。 |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventData.md b/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventData.md
index e84f3b4abffbb032a8a79c489a780ad252158737..3fc9c0588ec58f4c0d5db27eb4cfade3d0607c32 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventData.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventData.md
@@ -1,5 +1,10 @@
 # CommonEventData
 
+> **说明：**
+>
+> 本模块首批接口从API version 7开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
+
+
 **系统能力：** `SystemCapability.Notification.CommonEvent`
 
 | 名称       | 类型                 | 可读 | 可写 | 说明                                                    |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventPublishData.md b/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventPublishData.md
index 9d5fe786465e99ce4e85c49310943df600ccb8e6..70df6286eb1bf1877f40b9c37239522f9bc8d6b1 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventPublishData.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventPublishData.md
@@ -1,5 +1,9 @@
 # CommonEventPublishData
 
+> **说明：**
+>
+> 本模块首批接口从API version 7开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
+
 **系统能力：** `SystemCapability.Notification.CommonEvent`
 
 | 名称                  | 类型                 | 可读 | 可写 | 说明                         |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventSubscribeInfo.md b/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventSubscribeInfo.md
index 6938b5351b61ab96cf8d87cc78fc3333af21cfa6..1637fecf93afcdebf68884bbcd05539914258af0 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventSubscribeInfo.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventSubscribeInfo.md
@@ -1,5 +1,9 @@
 # CommonEventSubscribeInfo
 
+> **说明：**
+>
+> 本模块首批接口从API version 7开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
+
 **系统能力：** `SystemCapability.Notification.CommonEvent`
 
 | 名称                | 类型           | 可读 | 可写 | 说明                                                         |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventSubscriber.md b/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventSubscriber.md
index 411b63e250403b1f5ee916d273f5306c88cda65c..caa6b850cd30c9ac9b7c331bef6c983ba33f5a23 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventSubscriber.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-commonEvent-commonEventSubscriber.md
@@ -1,11 +1,40 @@
 # CommonEventSubscriber
 
-## getCode
+> **说明：**
+>
+> 本模块首批接口从API version 7开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
+
+## 使用说明
+
+在使用CommonEventSubscriber的功能前，需要通过CommonEvent.createSubscriber获取subscriber对象。
 
 ```ts
-getCode(callback: AsyncCallback<number>): void
+import CommonEvent from '@ohos.commonEvent';
+let subscriber; // 用于保存创建成功的订阅者对象，后续使用其完成订阅及退订的动作
+
+// 订阅者信息
+let subscribeInfo = {
+	events: ["event"]
+};
+
+// 创建订阅者回调
+function createCB(err, commonEventSubscriber) {
+    if (err.code) {
+        console.error(`createSubscriber failed, code is ${err.code}`);
+    } else {
+        console.info("createSubscriber");
+        subscriber = commonEventSubscriber;
+    }
+}
+
+// 创建订阅者
+CommonEvent.createSubscriber(subscribeInfo, createCB);
 ```
 
+## getCode
+
+getCode(callback: AsyncCallback\<number>): void
+
 以回调形式获取公共事件代码。
 
 **系统能力**：`SystemCapability.Notification.CommonEvent`
@@ -19,8 +48,6 @@ getCode(callback: AsyncCallback<number>): void
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 //获取有序公共事件代码回调
 function getCodeCB(err, code) {
     if (err.code) {
@@ -34,9 +61,7 @@ subscriber.getCode(getCodeCB);
 
 ## getCode
 
-```ts
-getCode(): Promise<number>
-```
+getCode(): Promise\<number>
 
 以Promise形式获取公共事件代码。
 
@@ -51,8 +76,6 @@ getCode(): Promise<number>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.getCode().then((code) => {
     console.info("getCode " + JSON.stringify(code));
 }).catch((err) => {
@@ -62,9 +85,7 @@ subscriber.getCode().then((code) => {
 
 ## setCode
 
-```ts
-setCode(code: number, callback: AsyncCallback<void>): void
-```
+setCode(code: number, callback: AsyncCallback\<void>): void
 
 以回调形式设置公共事件的代码。
 
@@ -80,8 +101,6 @@ setCode(code: number, callback: AsyncCallback<void>): void
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 //设置有序公共事件的代码回调
 function setCodeCB(err) {
     if (err.code) {
@@ -95,9 +114,7 @@ subscriber.setCode(1, setCodeCB);
 
 ## setCode
 
-```ts
-setCode(code: number): Promise<void>
-```
+setCode(code: number): Promise\<void>
 
 以Promise形式设置公共事件的代码。
 
@@ -118,8 +135,6 @@ setCode(code: number): Promise<void>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.setCode(1).then(() => {
     console.info("setCode");
 }).catch((err) => {
@@ -129,9 +144,7 @@ subscriber.setCode(1).then(() => {
 
 ## getData
 
-```ts
-getData(callback: AsyncCallback<string>): void
-```
+getData(callback: AsyncCallback\<string>): void
 
 以回调形式获取公共事件的数据。
 
@@ -146,8 +159,6 @@ getData(callback: AsyncCallback<string>): void
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 //获取有序公共事件代码数据回调
 function getDataCB(err, data) {
     if (err.code) {
@@ -161,9 +172,7 @@ subscriber.getData(getDataCB);
 
 ## getData
 
-```ts
-getData(): Promise<string>
-```
+getData(): Promise\<string>
 
 以Promise形式获取公共事件的数据。
 
@@ -178,8 +187,6 @@ getData(): Promise<string>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.getData().then((data) => {
     console.info("getData " + JSON.stringify(data));
 }).catch((err) => {
@@ -205,8 +212,6 @@ setData(data: string, callback: AsyncCallback\<void>): void
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 //设置有序公共事件的结果数据回调
 function setDataCB(err) {
     if (err.code) {
@@ -220,9 +225,7 @@ subscriber.setData("publish_data_changed", setDataCB);
 
 ## setData
 
-```ts
-setData(data: string): Promise<void>
-```
+setData(data: string): Promise\<void>
 
 以Promise形式设置公共事件的果数据。
 
@@ -243,8 +246,6 @@ setData(data: string): Promise<void>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.setData("publish_data_changed").then(() => {
     console.info("setData");
 }).catch((err) => {
@@ -254,9 +255,7 @@ subscriber.setData("publish_data_changed").then(() => {
 
 ## setCodeAndData
 
-```ts
-setCodeAndData(code: number, data: string, callback:AsyncCallback<void>): void
-```
+setCodeAndData(code: number, data: string, callback:AsyncCallback\<void>): void
 
 以回调形式设置公共事件代码和数据。
 
@@ -273,8 +272,6 @@ setCodeAndData(code: number, data: string, callback:AsyncCallback<void>): void
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 //设置有序公共事件的代码和数据回调
 function setCodeDataCB(err) {
     if (err.code) {
@@ -288,9 +285,7 @@ subscriber.setCodeAndData(1, "publish_data_changed", setCodeDataCB);
 
 ## setCodeAndData
 
-```ts
-setCodeAndData(code: number, data: string): Promise<void>
-```
+setCodeAndData(code: number, data: string): Promise\<void>
 
 以Promise形式设置公共事件的代码和数据。
 
@@ -312,8 +307,6 @@ setCodeAndData(code: number, data: string): Promise<void>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.setCodeAndData(1, "publish_data_changed").then(() => {
     console.info("setCodeAndData");
 }).catch((err) => {
@@ -323,9 +316,7 @@ subscriber.setCodeAndData(1, "publish_data_changed").then(() => {
 
 ## isOrderedCommonEvent
 
-```ts
-isOrderedCommonEvent(callback: AsyncCallback<boolean>): void
-```
+isOrderedCommonEvent(callback: AsyncCallback\<boolean>): void
 
 以回调形式查询当前公共事件的是否为有序公共事件。
 
@@ -342,8 +333,6 @@ isOrderedCommonEvent(callback: AsyncCallback<boolean>): void
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 //获取当前公共事件是否为有序事件的回调
 function isOrderedCB(err, isOrdered) {
     if (err.code) {
@@ -357,9 +346,7 @@ subscriber.isOrderedCommonEvent(isOrderedCB);
 
 ## isOrderedCommonEvent
 
-```ts
-isOrderedCommonEvent(): Promise<boolean>
-```
+isOrderedCommonEvent(): Promise\<boolean>
 
 以Promise形式查询当前公共事件的是否为有序公共事件。
 
@@ -376,8 +363,6 @@ isOrderedCommonEvent(): Promise<boolean>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.isOrderedCommonEvent().then((isOrdered) => {
     console.info("isOrdered " + JSON.stringify(isOrdered));
 }).catch((err) => {
@@ -387,9 +372,7 @@ subscriber.isOrderedCommonEvent().then((isOrdered) => {
 
 ## isStickyCommonEvent
 
-```ts
-isStickyCommonEvent(callback: AsyncCallback<boolean>): void
-```
+isStickyCommonEvent(callback: AsyncCallback\<boolean>): void
 
 以回调形式检查当前公共事件是否为一个粘性事件。
 
@@ -406,8 +389,6 @@ isStickyCommonEvent(callback: AsyncCallback<boolean>): void
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 //获取当前公共事件是否为粘性事件的回调
 function isStickyCB(err, isSticky) {
     if (err.code) {
@@ -421,9 +402,7 @@ subscriber.isStickyCommonEvent(isStickyCB);
 
 ## isStickyCommonEvent
 
-```ts
-isStickyCommonEvent(): Promise<boolean>
-```
+isStickyCommonEvent(): Promise\<boolean>
 
 以Promise形式检查当前公共事件是否为一个粘性事件。
 
@@ -440,8 +419,6 @@ isStickyCommonEvent(): Promise<boolean>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.isStickyCommonEvent().then((isSticky) => {
     console.info("isSticky " + JSON.stringify(isSticky));
 }).catch((err) => {
@@ -451,9 +428,7 @@ subscriber.isStickyCommonEvent().then((isSticky) => {
 
 ## abortCommonEvent
 
-```ts
-abortCommonEvent(callback: AsyncCallback<void>): void
-```
+abortCommonEvent(callback: AsyncCallback\<void>): void
 
 以回调形式取消当前的有序公共事件，取消后，有序公共事件不再向下一个订阅者传递。
 
@@ -468,8 +443,6 @@ abortCommonEvent(callback: AsyncCallback<void>): void
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 //取消当前有序公共事件的回调
 function abortCB(err) {
     if (err.code) {
@@ -483,9 +456,7 @@ subscriber.abortCommonEvent(abortCB);
 
 ## abortCommonEvent
 
-```ts
-abortCommonEvent(): Promise<void>
-```
+abortCommonEvent(): Promise\<void>
 
 以Promise形式取消当前的有序公共事件，取消后，公共事件不再向下一个订阅者传递。
 
@@ -500,8 +471,6 @@ abortCommonEvent(): Promise<void>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.abortCommonEvent().then(() => {
     console.info("abortCommonEvent");
 }).catch((err) => {
@@ -511,9 +480,7 @@ subscriber.abortCommonEvent().then(() => {
 
 ## clearAbortCommonEvent
 
-```ts
-clearAbortCommonEvent(callback: AsyncCallback<void>): void
-```
+clearAbortCommonEvent(callback: AsyncCallback\<void>): void
 
 以回调形式清除当前有序公共事件。
 
@@ -528,8 +495,6 @@ clearAbortCommonEvent(callback: AsyncCallback<void>): void
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 //清除当前公共事件取消状态的回调
 function clearAbortCB(err) {
     if (err.code) {
@@ -543,9 +508,7 @@ subscriber.clearAbortCommonEvent(clearAbortCB);
 
 ## clearAbortCommonEvent
 
-```ts
-clearAbortCommonEvent(): Promise<void>
-```
+clearAbortCommonEvent(): Promise\<void>
 
 以Promise形式清除当前有序公共事件。
 
@@ -560,8 +523,6 @@ clearAbortCommonEvent(): Promise<void>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.clearAbortCommonEvent().then(() => {
     console.info("clearAbortCommonEvent");
 }).catch((err) => {
@@ -571,9 +532,7 @@ subscriber.clearAbortCommonEvent().then(() => {
 
 ## getAbortCommonEvent
 
-```ts
-getAbortCommonEvent(callback: AsyncCallback<boolean>): void
-```
+getAbortCommonEvent(callback: AsyncCallback\<boolean>): void
 
 以回调形式获取当前有序公共事件是否取消的状态。
 
@@ -588,8 +547,6 @@ getAbortCommonEvent(callback: AsyncCallback<boolean>): void
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 //获取当前有序公共事件是否取消的回调
 function getAbortCB(err, abortEvent) {
     if (err.code) {
@@ -603,9 +560,7 @@ subscriber.getAbortCommonEvent(getAbortCB);
 
 ## getAbortCommonEvent
 
-```ts
-getAbortCommonEvent(): Promise<boolean>
-```
+getAbortCommonEvent(): Promise\<boolean>
 
 以Promise形式获取当前有序公共事件是否取消的状态。
 
@@ -620,8 +575,6 @@ getAbortCommonEvent(): Promise<boolean>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.getAbortCommonEvent().then((abortEvent) => {
     console.info("abortCommonEvent " + JSON.stringify(abortEvent));
 }).catch((err) => {
@@ -631,9 +584,7 @@ subscriber.getAbortCommonEvent().then((abortEvent) => {
 
 ## getSubscribeInfo
 
-```ts
-getSubscribeInfo(callback: AsyncCallback<CommonEventSubscribeInfo>): void
-```
+getSubscribeInfo(callback: AsyncCallback\<CommonEventSubscribeInfo>): void
 
 以回调形式获取订阅者的订阅信息。
 
@@ -648,8 +599,6 @@ getSubscribeInfo(callback: AsyncCallback<CommonEventSubscribeInfo>): void
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 //获取订阅者信息回调
 function getCB(err, subscribeInfo) {
     if (err.code) {
@@ -663,9 +612,7 @@ subscriber.getSubscribeInfo(getCB);
 
 ## getSubscribeInfo
 
-```ts
-getSubscribeInfo(): Promise<CommonEventSubscribeInfo>
-```
+getSubscribeInfo(): Promise\<CommonEventSubscribeInfo>
 
 以Promise形式获取订阅者的订阅信息。
 
@@ -680,8 +627,6 @@ getSubscribeInfo(): Promise<CommonEventSubscribeInfo>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.getSubscribeInfo().then((subscribeInfo) => {
     console.info("subscribeInfo " + JSON.stringify(subscribeInfo));
 }).catch((err) => {
@@ -691,9 +636,7 @@ subscriber.getSubscribeInfo().then((subscribeInfo) => {
 
 ## finishCommonEvent<sup>9+</sup>
 
-```ts
-finishCommonEvent(callback: AsyncCallback<void>): void
-```
+finishCommonEvent(callback: AsyncCallback\<void>): void
 
 以回调形式结束当前有序公共事件。
 
@@ -708,14 +651,13 @@ finishCommonEvent(callback: AsyncCallback<void>): void
 **示例：**
 
 ```ts
-let subscriber; //创建成功的订阅者对象
-
 //结束当前有序公共事件的回调
 function finishCB(err) {
   if (err.code) {
     console.error(`finishCommonEvent failed, code is ${err.code}, message is ${err.message}`);
-} else {
+  } else {
     console.info("FinishCommonEvent");
+  }
 }
 
 subscriber.finishCommonEvent(finishCB);
@@ -723,9 +665,7 @@ subscriber.finishCommonEvent(finishCB);
 
 ## finishCommonEvent<sup>9+</sup>
 
-```ts
-finishCommonEvent(): Promise<void\>
-```
+finishCommonEvent(): Promise\<void>
 
 以Promise形式结束当前有序公共事件。
 
@@ -740,8 +680,6 @@ finishCommonEvent(): Promise<void\>
 **示例：**
 
 ```ts
-let subscriber;	//创建成功的订阅者对象
-
 subscriber.finishCommonEvent().then(() => {
     console.info("FinishCommonEvent");
 }).catch((err) => {
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationActionButton.md b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationActionButton.md
index d822600d6939bf2c981a1ddbd611d2d6672816ca..be9c2739273588cdf154fe67e15c2934bde3253b 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationActionButton.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationActionButton.md
@@ -8,9 +8,9 @@
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
 
-| 名称      | 类型                                            | 可读 | 可写 | 说明                      |
+| 名称      | 类型                                            | 只读 | 必填 | 说明                      |
 | --------- | ----------------------------------------------- | --- | ---- | ------------------------- |
-| title     | string                                          | 是  | 是  | 按钮标题。                  |
-| wantAgent | [WantAgent](js-apis-app-ability-wantAgent.md)   | 是  | 是  | 点击按钮时触发的WantAgent。 |
-| extras    | { [key: string]: any }                          | 是  | 是  | 按钮扩展信息。              |
-| userInput<sup>8+</sup> | [NotificationUserInput](js-apis-inner-notification-notificationUserInput.md) | 是  | 是  | 用户输入对象实例。          |
+| title     | string                                          | 否  | 是  | 按钮标题。                  |
+| wantAgent | [WantAgent](js-apis-app-ability-wantAgent.md)   | 否  | 是  | 点击按钮时触发的WantAgent。 |
+| extras    | { [key: string]: any }                          | 否  | 否  | 按钮扩展信息。              |
+| userInput<sup>8+</sup> | [NotificationUserInput](js-apis-inner-notification-notificationUserInput.md) | 否  | 否  | 用户输入对象实例。          |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationCommonDef.md b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationCommonDef.md
index 5d3e7eee4755935751d1aaa1859fa16d3663197b..3752302faafe6429b6a8704783285ac3a897e896 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationCommonDef.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationCommonDef.md
@@ -10,7 +10,7 @@ BundleOption模块为指定应用的包信息。
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
 
-| 名称   | 类型   | 必填 | 说明   |
-| ------ | ------ |---- |  ------ |
-| bundle | string | 是 | 应用的包信息。 |
-| uid    | number | 否 | 用户ID。 |
+| 名称   | 类型   | 只读 | 必填 | 说明   |
+| ------ | ------ | ---- | ---- |  ------ |
+| bundle | string | 否   | 是 | 应用的包信息。 |
+| uid    | number | 否   | 否 | 用户ID。 |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationContent.md b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationContent.md
index be8496b25a4909e2c7f2796e7e98c1381b50dfe1..a8d6d31263f2ca8ea3ebc530856d3a5336b4ab80 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationContent.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationContent.md
@@ -8,13 +8,13 @@
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
 
-| 名称        | 类型                                                         | 可读 | 可写 | 说明               |
+| 名称        | 类型                                                         | 只读 | 必填 | 说明               |
 | ----------- | ------------------------------------------------------------ | ---- | --- | ------------------ |
-| contentType | [ContentType](./js-apis-notificationManager.md#contenttype)                                  | 是  | 是  | 通知内容类型。       |
-| normal      | [NotificationBasicContent](#notificationbasiccontent)        | 是  | 是  | 基本类型通知内容。   |
-| longText    | [NotificationLongTextContent](#notificationlongtextcontent)  | 是  | 是  | 长文本类型通知内容。 |
-| multiLine   | [NotificationMultiLineContent](#notificationmultilinecontent) | 是  | 是  | 多行类型通知内容。   |
-| picture     | [NotificationPictureContent](#notificationpicturecontent)    | 是  | 是  | 图片类型通知内容。   |
+| contentType | [ContentType](./js-apis-notificationManager.md#contenttype)  | 否  | 是  | 通知内容类型。       |
+| normal      | [NotificationBasicContent](#notificationbasiccontent)        | 否  | 否  | 基本类型通知内容。   |
+| longText    | [NotificationLongTextContent](#notificationlongtextcontent)  | 否  | 否  | 长文本类型通知内容。 |
+| multiLine   | [NotificationMultiLineContent](#notificationmultilinecontent) | 否  | 否  | 多行类型通知内容。   |
+| picture     | [NotificationPictureContent](#notificationpicturecontent)    | 否  | 否  | 图片类型通知内容。   |
 
 ## NotificationBasicContent
 
@@ -22,11 +22,11 @@
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
 
-| 名称           | 类型   | 可读 | 可写 | 说明                               |
+| 名称           | 类型   | 只读 | 必填 | 说明                               |
 | -------------- | ------ | ---- | ---- | ---------------------------------- |
-| title          | string | 是   | 是   | 通知标题。                         |
-| text           | string | 是   | 是   | 通知内容。                         |
-| additionalText | string | 是   | 是   | 通知附加内容，是对通知内容的补充。 |
+| title          | string | 否   | 是   | 通知标题。                         |
+| text           | string | 否   | 是   | 通知内容。                         |
+| additionalText | string | 否   | 否   | 通知附加内容，是对通知内容的补充。 |
 
 
 ## NotificationLongTextContent
@@ -35,14 +35,14 @@
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
 
-| 名称           | 类型   | 可读 | 可写 | 说明                             |
+| 名称           | 类型   | 只读 | 必填 | 说明                             |
 | -------------- | ------ | ---- | --- | -------------------------------- |
-| title          | string | 是  | 是  | 通知标题。                         |
-| text           | string | 是  | 是  | 通知内容。                         |
-| additionalText | string | 是  | 是  | 通知附加内容，是对通知内容的补充。 |
-| longText       | string | 是  | 是  | 通知的长文本。                     |
-| briefText      | string | 是  | 是  | 通知概要内容，是对通知内容的总结。 |
-| expandedTitle  | string | 是  | 是  | 通知展开时的标题。                 |
+| title          | string | 否  | 是  | 通知标题。                         |
+| text           | string | 否  | 是  | 通知内容。                         |
+| additionalText | string | 否  | 否  | 通知附加内容，是对通知内容的补充。 |
+| longText       | string | 否  | 是  | 通知的长文本。                     |
+| briefText      | string | 否  | 是  | 通知概要内容，是对通知内容的总结。   |
+| expandedTitle  | string | 否  | 是  | 通知展开时的标题。                 |
 
 
 ## NotificationMultiLineContent
@@ -53,12 +53,12 @@
 
 | 名称           | 类型            | 可读 | 可写 | 说明                             |
 | -------------- | --------------- | --- | --- | -------------------------------- |
-| title          | string          | 是  | 是  | 通知标题。                         |
-| text           | string          | 是  | 是  | 通知内容。                         |
-| additionalText | string          | 是  | 是  | 通知附加内容，是对通知内容的补充。 |
-| briefText      | string          | 是  | 是  | 通知概要内容，是对通知内容的总结。 |
-| longTitle      | string          | 是  | 是  | 通知展开时的标题。                 |
-| lines          | Array\<string\> | 是  | 是  | 通知的多行文本。                   |
+| title          | string          | 否  | 是  | 通知标题。                         |
+| text           | string          | 否  | 是  | 通知内容。                         |
+| additionalText | string          | 否  | 否  | 通知附加内容，是对通知内容的补充。 |
+| briefText      | string          | 否  | 是  | 通知概要内容，是对通知内容的总结。 |
+| longTitle      | string          | 否  | 是  | 通知展开时的标题。                 |
+| lines          | Array\<string\> | 否  | 是  | 通知的多行文本。                   |
 
 
 ## NotificationPictureContent
@@ -69,9 +69,9 @@
 
 | 名称           | 类型           | 可读 | 可写 | 说明                             |
 | -------------- | -------------- | ---- | --- | -------------------------------- |
-| title          | string         | 是  | 是  | 通知标题。                         |
-| text           | string         | 是  | 是  | 通知内容。                         |
-| additionalText | string         | 是  | 是  | 通知附加内容，是对通知内容的补充。 |
-| briefText      | string         | 是  | 是  | 通知概要内容，是对通知内容的总结。 |
-| expandedTitle  | string         | 是  | 是  | 通知展开时的标题。                 |
-| picture        | [image.PixelMap](js-apis-image.md#pixelmap7) | 是  | 是  | 通知的图片内容。                   |
+| title          | string         | 否  | 是  | 通知标题。                         |
+| text           | string         | 否  | 是  | 通知内容。                         |
+| additionalText | string         | 否  | 否  | 通知附加内容，是对通知内容的补充。 |
+| briefText      | string         | 否  | 是  | 通知概要内容，是对通知内容的总结。 |
+| expandedTitle  | string         | 否  | 是  | 通知展开时的标题。                 |
+| picture        | [image.PixelMap](js-apis-image.md#pixelmap7) | 否  | 是  | 通知的图片内容。                   |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationFlags.md b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationFlags.md
index 1dfc0990395386c786064be441c7c413d2fc744c..ba8870be4249237fda3ceb64b1ccb3f0b934c97d 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationFlags.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationFlags.md
@@ -8,7 +8,7 @@
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
 
-| 名称             | 类型                    | 可读 | 可写 | 说明                               |
+| 名称             | 类型                    | 只读 | 必填 | 说明                               |
 | ---------------- | ---------------------- | ---- | ---- | --------------------------------- |
 | soundEnabled     | [NotificationFlagStatus](#notificationflagstatus) | 是   | 否   | 是否启用声音提示。                  |
 | vibrationEnabled | [NotificationFlagStatus](#notificationflagstatus) | 是   | 否   | 是否启用振动提醒功能。               |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationRequest.md b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationRequest.md
index 9c37ecd7a7fa595eb456796051157c62cf30ae68..a4faf72799f3871cbbf2451742c8338773d2adf7 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationRequest.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationRequest.md
@@ -8,45 +8,45 @@
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
 
-| 名称                  | 类型                                          | 可读 | 可写 | 说明                       |
+| 名称                  | 类型                                          | 只读 | 必填 | 说明                       |
 | --------------------- | --------------------------------------------- | ---- | --- | -------------------------- |
-| content               | [NotificationContent](js-apis-inner-notification-notificationContent.md#notificationcontent)   | 是  | 是  | 通知内容。                   |
-| id                    | number                                        | 是  | 是  | 通知ID。                     |
-| slotType              | [SlotType](js-apis-notificationManager.md#slottype)                         | 是  | 是  | 通道类型。                   |
-| isOngoing             | boolean                                       | 是  | 是  | 是否进行时通知。             |
-| isUnremovable         | boolean                                       | 是  | 是  | 是否可移除。                 |
-| deliveryTime          | number                                        | 是  | 是  | 通知发送时间。               |
-| tapDismissed          | boolean                                       | 是  | 是  | 通知是否自动清除。           |
-| autoDeletedTime       | number                                        | 是  | 是  | 自动清除的时间。             |
-| wantAgent             | [WantAgent](js-apis-app-ability-wantAgent.md) | 是  | 是  | WantAgent封装了应用的行为意图，点击通知时触发该行为。 |
-| extraInfo             | {[key: string]: any}                          | 是  | 是  | 扩展参数。                   |
-| color                 | number                                        | 是  | 是  | 通知背景颜色。预留能力，暂未支持。 |
-| colorEnabled          | boolean                                       | 是  | 是  | 通知背景颜色是否使能。预留能力，暂未支持。 |
-| isAlertOnce           | boolean                                       | 是  | 是  | 设置是否仅有一次此通知提醒。 |
-| isStopwatch           | boolean                                       | 是  | 是  | 是否显示已用时间。           |
-| isCountDown           | boolean                                       | 是  | 是  | 是否显示倒计时时间。         |
-| isFloatingIcon        | boolean                                       | 是  | 是  | 是否显示状态栏图标。         |
-| label                 | string                                        | 是  | 是  | 通知标签。                   |
-| badgeIconStyle        | number                                        | 是  | 是  | 通知角标类型。               |
-| showDeliveryTime      | boolean                                       | 是  | 是  | 是否显示分发时间。           |
-| actionButtons         | Array\<[NotificationActionButton](js-apis-inner-notification-notificationActionButton.md)\>             | 是  | 是  | 通知按钮，最多三个按钮。  |
-| smallIcon             | [image.PixelMap](js-apis-image.md#pixelmap7) | 是  | 是  | 通知小图标。可选字段，大小不超过30KB。 |
-| largeIcon             | [image.PixelMap](js-apis-image.md#pixelmap7) | 是  | 是  | 通知大图标。可选字段，大小不超过30KB。 |
+| content               | [NotificationContent](js-apis-inner-notification-notificationContent.md#notificationcontent)   | 否  | 是  | 通知内容。                   |
+| id                    | number                                        | 否  | 否  | 通知ID。                     |
+| slotType              | [SlotType](js-apis-notificationManager.md#slottype)                         | 是  | 否  | 通道类型。                   |
+| isOngoing             | boolean                                       | 否  | 否  | 是否进行时通知。             |
+| isUnremovable         | boolean                                       | 否  | 否  | 是否可移除。                 |
+| deliveryTime          | number                                        | 否  | 否  | 通知发送时间。               |
+| tapDismissed          | boolean                                       | 否  | 否  | 通知是否自动清除。           |
+| autoDeletedTime       | number                                        | 否  | 否  | 自动清除的时间。             |
+| wantAgent             | [WantAgent](js-apis-app-ability-wantAgent.md) | 否  | 否  | WantAgent封装了应用的行为意图，点击通知时触发该行为。 |
+| extraInfo             | {[key: string]: any}                          | 否  | 否  | 扩展参数。                   |
+| color                 | number                                        | 否  | 否  | 通知背景颜色。预留能力，暂未支持。 |
+| colorEnabled          | boolean                                       | 否  | 否  | 通知背景颜色是否使能。预留能力，暂未支持。 |
+| isAlertOnce           | boolean                                       | 否  | 否  | 设置是否仅有一次此通知提醒。 |
+| isStopwatch           | boolean                                       | 否  | 否  | 是否显示已用时间。           |
+| isCountDown           | boolean                                       | 否  | 否  | 是否显示倒计时时间。         |
+| isFloatingIcon        | boolean                                       | 否  | 否  | 是否显示状态栏图标。         |
+| label                 | string                                        | 否  | 否  | 通知标签。                   |
+| badgeIconStyle        | number                                        | 否  | 否  | 通知角标类型。预留能力，暂未支持。     |
+| showDeliveryTime      | boolean                                       | 否  | 否  | 是否显示分发时间。           |
+| actionButtons         | Array\<[NotificationActionButton](js-apis-inner-notification-notificationActionButton.md)\>             | 否  | 否  | 通知按钮，最多三个按钮。  |
+| smallIcon             | [image.PixelMap](js-apis-image.md#pixelmap7) | 否  | 否  | 通知小图标。可选字段，大小不超过30KB。 |
+| largeIcon             | [image.PixelMap](js-apis-image.md#pixelmap7) | 否  | 否  | 通知大图标。可选字段，大小不超过30KB。 |
 | creatorBundleName     | string                                        | 是  | 否  | 创建通知的包名。             |
 | creatorUid<sup>8+<sup>  | number                                        | 是  | 否  | 创建通知的UID。              |
 | creatorPid            | number                                        | 是  | 否  | 创建通知的PID。              |
-| creatorUserId| number                                    | 是  | 否  | 创建通知的UserId。           |
+| creatorUserId         | number                                       | 是  | 否  | 创建通知的UserId。           |
 | hashCode              | string                                        | 是  | 否  | 通知唯一标识。               |
-| classification        | string                                        | 是  | 是  | 通知分类。<br>**系统API**: 此接口为系统接口，三方应用不支持调用。                   |
-| groupName<sup>8+<sup> | string                                        | 是  | 是  | 组通知名称。                 |
-| template<sup>8+<sup> | [NotificationTemplate](./js-apis-inner-notification-notificationTemplate.md) | 是  | 是  | 通知模板。                   |
+| classification        | string                                        | 否  | 否  | 通知分类。<br>**系统API**: 此接口为系统接口，三方应用不支持调用。                   |
+| groupName<sup>8+<sup> | string                                        | 否  | 否  | 组通知名称。                 |
+| template<sup>8+<sup> | [NotificationTemplate](./js-apis-inner-notification-notificationTemplate.md) | 否  | 否  | 通知模板。                   |
 | isRemoveAllowed<sup>8+<sup> | boolean                                | 是  | 否  | 通知是否能被移除。<br>**系统API**: 此接口为系统接口，三方应用不支持调用。                   |
 | source<sup>8+<sup> | number                                        | 是  | 否  | 通知源。<br>**系统API**: 此接口为系统接口，三方应用不支持调用。                   |
-| distributedOption<sup>8+<sup> | [DistributedOptions](#distributedoptions)                 | 是  | 是  | 分布式通知的选项。          |
+| distributedOption<sup>8+<sup> | [DistributedOptions](#distributedoptions)                 | 否  | 否  | 分布式通知的选项。          |
 | deviceId<sup>8+<sup> | string                                        | 是  | 否  | 通知源的deviceId。<br>**系统API**: 此接口为系统接口，三方应用不支持调用。          |
-| notificationFlags<sup>8+<sup> | [NotificationFlags](js-apis-inner-notification-notificationflags#notificationFlags)                    | 是  | 否  | 获取NotificationFlags。          |
-| removalWantAgent<sup>9+<sup> | [WantAgent](js-apis-app-ability-wantAgent.md) | 是  | 是  | 当移除通知时，通知将被重定向到的WantAgent实例。          |
-| badgeNumber<sup>9+<sup> | number                    | 是  | 是  | 应用程序图标上显示的通知数。          |
+| notificationFlags<sup>8+<sup> | [NotificationFlags](js-apis-inner-notification-notificationFlags.md#notificationflags)                    | 是  | 否  | 获取NotificationFlags。          |
+| removalWantAgent<sup>9+<sup> | [WantAgent](js-apis-app-ability-wantAgent.md) | 否  | 否  | 当移除通知时，通知将被重定向到的WantAgent实例。          |
+| badgeNumber<sup>9+<sup> | number                    | 否  | 否  | 应用程序图标上显示的通知数。          |
 
 
 ## DistributedOptions
@@ -55,9 +55,9 @@
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
 
-| 名称                   | 类型            | 可读 | 可写 | 说明                               |
+| 名称                   | 类型            | 只读 | 必填 | 说明                               |
 | ---------------------- | -------------- | ---- | ---- | ---------------------------------- |
-| isDistributed<sup>8+<sup>          | boolean        | 是   | 是   | 是否为分布式通知。                  |
-| supportDisplayDevices<sup>8+<sup>  | Array\<string> | 是   | 是   | 可以同步通知到的设备列表。         |
-| supportOperateDevices<sup>8+<sup>  | Array\<string> | 是   | 是   | 可以打开通知的设备列表。              |
+| isDistributed<sup>8+<sup>          | boolean        | 否   | 否   | 是否为分布式通知。                  |
+| supportDisplayDevices<sup>8+<sup>  | Array\<string> | 否   | 否   | 可以同步通知到的设备列表。         |
+| supportOperateDevices<sup>8+<sup>  | Array\<string> | 否   | 否   | 可以打开通知的设备列表。              |
 | remindType<sup>8+<sup>             | number         | 是   | 否   | 通知的提醒方式。<br>**系统API**: 此接口为系统接口，三方应用不支持调用。                    |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSlot.md b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSlot.md
index 27d5aec3672ee7caa0eefd640153f3ee70514a3a..b0ff35c59d2014fbd8b1565ea4436d58c7c6c58f 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSlot.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSlot.md
@@ -8,17 +8,17 @@
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
 
-| 名称                 | 类型                  | 可读 | 可写 | 说明                                       |
+| 名称                 | 类型                  | 只读 | 必填 | 说明                                       |
 | -------------------- | --------------------- | ---- | --- | ------------------------------------------ |
-| type                 | [SlotType](js-apis-notificationManager.md#slottype) | 是  | 是  | 通道类型。                                   |
-| level                | number                | 是  | 是  | 通知级别，不设置则根据通知渠道类型有默认值。 |
-| desc                 | string                | 是  | 是  | 通知渠道描述信息。                           |
-| badgeFlag            | boolean               | 是  | 是  | 是否显示角标。                               |
-| bypassDnd            | boolean               | 是  | 是  | 置是否在系统中绕过免打扰模式。               |
-| lockscreenVisibility | number                | 是  | 是  | 在锁定屏幕上显示通知的模式。                 |
-| vibrationEnabled     | boolean               | 是  | 是  | 是否可振动。                                 |
-| sound                | string                | 是  | 是  | 通知提示音。                                 |
-| lightEnabled         | boolean               | 是  | 是  | 是否闪灯。                                   |
-| lightColor           | number                | 是  | 是  | 通知灯颜色。                                 |
-| vibrationValues      | Array\<number\>       | 是  | 是  | 通知振动样式。                               |
+| type                 | [SlotType](js-apis-notificationManager.md#slottype) | 否  | 是  | 通道类型。                                   |
+| level                | number                | 否  | 否  | 通知级别，不设置则根据通知渠道类型有默认值。 |
+| desc                 | string                | 否  | 否  | 通知渠道描述信息。                           |
+| badgeFlag            | boolean               | 否  | 否  | 是否显示角标。                               |
+| bypassDnd            | boolean               | 否  | 否  | 置是否在系统中绕过免打扰模式。               |
+| lockscreenVisibility | number                | 否  | 否  | 在锁定屏幕上显示通知的模式。                 |
+| vibrationEnabled     | boolean               | 否  | 否  | 是否可振动。                                 |
+| sound                | string                | 否  | 否  | 通知提示音。                                 |
+| lightEnabled         | boolean               | 否  | 否  | 是否闪灯。                                   |
+| lightColor           | number                | 否  | 否  | 通知灯颜色。                                 |
+| vibrationValues      | Array\<number\>       | 否  | 否  | 通知振动样式。                               |
 | enabled<sup>9+</sup> | boolean               | 是  | 否  | 此通知插槽中的启停状态。                      |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSorting.md b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSorting.md
new file mode 100644
index 0000000000000000000000000000000000000000..70f9c43710d183ff680304f7622b0b17cd771c67
--- /dev/null
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSorting.md
@@ -0,0 +1,17 @@
+# NotificationSorting
+
+提供有关活动通知的排序信息。
+
+> **说明：**
+>
+> 本模块首批接口从API version 7开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
+
+**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
+
+**系统接口**: 以下为系统接口，三方应用不支持调用。
+
+| 名称                 | 类型                  | 只读 | 必填 | 说明                                       |
+| -------------------- | --------------------- | ---- | --- | ------------------------------------------ |
+| slot                 | [NotificationSlot](js-apis-inner-notification-notificationSlot.md) | 是  | 是  | 通道类型。                                   |
+| level                | number                | 是  | 是  | 通知级别，不设置则根据通知渠道类型有默认值。 |
+| desc                 | string                | 是  | 是  | 通知渠道描述信息。                           |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSortingMap.md b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSortingMap.md
new file mode 100644
index 0000000000000000000000000000000000000000..83a7e9c793a22fad440c7fac7568cb20c50aa5cb
--- /dev/null
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSortingMap.md
@@ -0,0 +1,16 @@
+# NotificationSortingMap
+
+提供有关已订阅的所有通知中的活动通知的排序信息。
+
+> **说明：**
+>
+> 本模块首批接口从API version 7开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
+
+**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
+
+**系统接口**: 以下为系统接口，三方应用不支持调用。
+
+| 名称                 | 类型                  | 只读 | 必填 | 说明                                       |
+| -------------------- | --------------------- | ---- | --- | ------------------------------------------ |
+| sortings              | { [key: string]: [NotificationSorting](js-apis-inner-notification-notificationSorting.md) } | 是  | 是  | 通知排序信息。                                   |
+| sortedHashCode                | Array<string>                | 是  | 是  | 通知排序的HashCode。 |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSubscribeInfo.md b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSubscribeInfo.md
new file mode 100644
index 0000000000000000000000000000000000000000..58977595bb7fa9e3713dd56d4783fa951716cc2d
--- /dev/null
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationSubscribeInfo.md
@@ -0,0 +1,16 @@
+# NotificationSubscribeInfo
+
+通知发布者的信息。
+
+> **说明：**
+>
+> 本模块首批接口从API version 7开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
+
+**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
+
+**系统接口**: 以下为系统接口，三方应用不支持调用。
+
+| 名称                 | 类型                  | 只读 | 必填 | 说明                                       |
+| -------------------- | --------------------- | ---- | --- | ------------------------------------------ |
+| bundleNames          | Array<string>         | 否  | 否  | 应用Bundle名称。                              |
+| userId               | number                | 否  | 否  | 用户ID。                                      |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationTemplate.md b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationTemplate.md
index 58e9d4442712e965f56d6837de8d9cbfef010544..bd1c262c5417cd745f0ea0d711a09bc93141f2c5 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationTemplate.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationTemplate.md
@@ -8,7 +8,7 @@
 
 **系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.Notification
 
-| 名称 | 类型                    | 可读 | 可写 | 说明       |
+| 名称 | 类型                    | 只读 | 必填 | 说明       |
 | ---- | ---------------------- | ---- | ---- | ---------- |
-| name | string                 | 是   | 是   | 模板名称。 |
-| data | {[key:string]: Object} | 是   | 是   | 模板数据。 |
+| name | string                 | 否   | 是   | 模板名称。 |
+| data | {[key:string]: Object} | 否   | 是   | 模板数据。 |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationUserInput.md b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationUserInput.md
index bc60f868ba6d787cbacf2b79e50102b7f06cb103..6623fad27f64660cfadff9e79813f152e3f01f72 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationUserInput.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-notification-notificationUserInput.md
@@ -8,6 +8,6 @@
 
 **系统能力**：SystemCapability.Notification.Notification
 
-| 名称     | 类型   | 可读 | 可写 | 说明                          |
+| 名称     | 类型   | 只读 | 必填 | 说明                          |
 | -------- | ------ | --- | ---- | ----------------------------- |
-| inputKey | string | 是  | 是  | 用户输入时用于标识此输入的key。 |
+| inputKey | string | 否  | 是  | 用户输入时用于标识此输入的key。 |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-wantAgent-triggerInfo.md b/zh-cn/application-dev/reference/apis/js-apis-inner-wantAgent-triggerInfo.md
index 8a32144ecffecf3ca612a5ab42d22f6f17960be3..e641ed3d1c0d8b6f1b1f8c0969c6e749c5d6c1e9 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-wantAgent-triggerInfo.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-wantAgent-triggerInfo.md
@@ -2,6 +2,10 @@
 
 作为[trigger](js-apis-app-ability-wantAgent.md#wantagenttrigger)的入参定义触发WantAgent所需要的信息。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 7开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。 
+
 ## 导入模块
 
 ```ts
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inner-wantAgent-wantAgentInfo.md b/zh-cn/application-dev/reference/apis/js-apis-inner-wantAgent-wantAgentInfo.md
index df7c43d3ccd64a120641927a5e2efe1de20f2f02..6adfe0d53e74a2b569efa6ecf6c42fa82a575bd2 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inner-wantAgent-wantAgentInfo.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inner-wantAgent-wantAgentInfo.md
@@ -2,6 +2,10 @@
 
 定义触发WantAgent所需要的信息，可以作为[getWantAgent](js-apis-app-ability-wantAgent.md#wantagentgetwantagent)的入参创建指定的WantAgent对象。
 
+> **说明：**
+> 
+> 本模块首批接口从API version 7开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。 
+
 ## 导入模块
 
 ```ts
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inputdevice.md b/zh-cn/application-dev/reference/apis/js-apis-inputdevice.md
index edd8ebd01dedc9e6dad5873910a62aab479e548c..e9c181f466f4dbfe8f26268ce74f9482ba7514bd 100755
--- a/zh-cn/application-dev/reference/apis/js-apis-inputdevice.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inputdevice.md
@@ -427,7 +427,7 @@ try {
 
 getKeyboardType(deviceId: number): Promise&lt;KeyboardType&gt;
 
-获取输入设备的键盘类型，使用AsyncCallback异步方式返回结果。
+获取输入设备的键盘类型，使用Promise异步方式返回结果。
 
 **系统能力**：SystemCapability.MultimodalInput.Input.InputDevice
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inputmethod.md b/zh-cn/application-dev/reference/apis/js-apis-inputmethod.md
index b93e06d8a644e537eaa540e08948ed56718f2c12..7c8fbe93065e3b9b61b2c201855c1cc8d657e6bb 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inputmethod.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inputmethod.md
@@ -60,7 +60,7 @@ getController(): InputMethodController
 
 | 错误码ID | 错误信息                     |
 | -------- | ------------------------------ |
-| 12800006 | Input method controller error. |
+| 12800006 | input method controller error. |
 
 **示例：**
 
@@ -88,7 +88,7 @@ getSetting(): InputMethodSetting
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800007 | Input method settings extension error. |
+| 12800007 | input method settings extension error. |
 
 **示例：**
 
@@ -119,8 +119,8 @@ switchInputMethod(target: InputMethodProperty, callback: AsyncCallback&lt;boolea
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800005 | Configuration persisting error.        |
-| 12800008 | Input method manager service error. |
+| 12800005 | configuration persisting error.        |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -176,8 +176,8 @@ switchInputMethod(target: InputMethodProperty): Promise&lt;boolean&gt;
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800005 | Configuration persisting error.        |
-| 12800008 | Input method manager service error. |
+| 12800005 | configuration persisting error.        |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -248,8 +248,8 @@ switchCurrentInputMethodSubtype(target: InputMethodSubtype, callback: AsyncCallb
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800005 | Configuration persisting error.        |
-| 12800008 | Input method manager service error. |
+| 12800005 | configuration persisting error.        |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -309,8 +309,8 @@ switchCurrentInputMethodSubtype(target: InputMethodSubtype): Promise&lt;boolean&
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800005 | Configuration persisting error.        |
-| 12800008 | Input method manager service error. |
+| 12800005 | configuration persisting error.        |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -384,8 +384,8 @@ switchCurrentInputMethodAndSubtype(inputMethodProperty: InputMethodProperty, inp
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800005 | Configuration persisting error.        |
-| 12800008 | Input method manager service error. |
+| 12800005 | configuration persisting error.        |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -438,8 +438,8 @@ switchCurrentInputMethodAndSubtype(inputMethodProperty: InputMethodProperty, inp
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800005 | Configuration persisting error.        |
-| 12800008 | Input method manager service error. |
+| 12800005 | configuration persisting error.        |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -447,7 +447,7 @@ switchCurrentInputMethodAndSubtype(inputMethodProperty: InputMethodProperty, inp
 let im = inputMethod.getCurrentInputMethod();
 let imSubType = inputMethod.getCurrentInputMethodSubtype();
 try {
-    inputMethod.switchCurrentInputMethodAndSubtype(inputMethodProperty, imSubType).then((result) => {
+    inputMethod.switchCurrentInputMethodAndSubtype(im, imSubType).then((result) => {
         if (result) {
             console.info('Succeeded in switching currentInputMethodAndSubtype.');
         } else {
@@ -533,8 +533,8 @@ stopInputSession(callback: AsyncCallback&lt;boolean&gt;): void
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800003 | Input method client error.             |
-| 12800008 | Input method manager service error. |
+| 12800003 | input method client error.             |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -576,8 +576,8 @@ stopInputSession(): Promise&lt;boolean&gt;
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800003 | Input method client error.             |
-| 12800008 | Input method manager service error. |
+| 12800003 | input method client error.             |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -619,8 +619,8 @@ showSoftKeyboard(callback: AsyncCallback&lt;void&gt;): void
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800003 | Input method client error.             |
-| 12800008 | Input method manager service error. |
+| 12800003 | input method client error.             |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -656,8 +656,8 @@ showSoftKeyboard(): Promise&lt;void&gt;
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800003 | Input method client error.             |
-| 12800008 | Input method manager service error. |
+| 12800003 | input method client error.             |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -691,8 +691,8 @@ hideSoftKeyboard(callback: AsyncCallback&lt;void&gt;): void
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800003 | Input method client error.             |
-| 12800008 | Input method manager service error. |
+| 12800003 | input method client error.             |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -728,8 +728,8 @@ hideSoftKeyboard(): Promise&lt;void&gt;
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800003 | Input method client error.             |
-| 12800008 | Input method manager service error. |
+| 12800003 | input method client error.             |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -876,8 +876,8 @@ listInputMethodSubtype(inputMethodProperty: InputMethodProperty, callback: Async
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800001 | Package manager error.                 |
-| 12800008 | Input method manager service error. |
+| 12800001 | package manager error.                 |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -928,8 +928,8 @@ listInputMethodSubtype(inputMethodProperty: InputMethodProperty): Promise&lt;Arr
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800001 | Package manager error.                 |
-| 12800008 | Input method manager service error. |
+| 12800001 | package manager error.                 |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -972,8 +972,8 @@ listCurrentInputMethodSubtype(callback: AsyncCallback&lt;Array&lt;InputMethodSub
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800001 | Package manager error.                 |
-| 12800008 | Input method manager service error. |
+| 12800001 | package manager error.                 |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -1011,8 +1011,8 @@ listCurrentInputMethodSubtype(): Promise&lt;Array&lt;InputMethodSubtype&gt;&gt;
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800001 | Package manager error.                 |
-| 12800008 | Input method manager service error. |
+| 12800001 | package manager error.                 |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -1049,8 +1049,8 @@ getInputMethods(enable: boolean, callback: AsyncCallback&lt;Array&lt;InputMethod
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800001 | Package manager error.                 |
-| 12800008 | Input method manager service error. |
+| 12800001 | package manager error.                 |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -1088,8 +1088,8 @@ getInputMethods(enable: boolean): Promise&lt;Array&lt;InputMethodProperty&gt;&gt
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800001 | Package manager error.                 |
-| 12800008 | Input method manager service error. |
+| 12800001 | package manager error.                 |
+| 12800008 | input method manager service error. |
 
 **返回值：**
 
@@ -1131,7 +1131,7 @@ showOptionalInputMethods(callback: AsyncCallback&lt;boolean&gt;): void
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800008 | Input method manager service error. |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
@@ -1169,7 +1169,7 @@ showOptionalInputMethods(): Promise&lt;boolean&gt;
 
 | 错误码ID | 错误信息                             |
 | -------- | -------------------------------------- |
-| 12800008 | Input method manager service error. |
+| 12800008 | input method manager service error. |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-inputmethodengine.md b/zh-cn/application-dev/reference/apis/js-apis-inputmethodengine.md
index 54980a9d681fc68d57d66de49504b1a7113aa0dc..70c2be3e1b82f61351e9093c880012ba4c4ed44d 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-inputmethodengine.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-inputmethodengine.md
@@ -975,7 +975,7 @@ getForward(length:number): Promise&lt;string&gt;
 | 错误码ID | 错误信息                     |
 | -------- | ------------------------------ |
 | 12800003 | input method client error.     |
-| 12800006 | Input method controller error. |
+| 12800006 | input method controller error. |
 
 **示例：**
 
@@ -1014,7 +1014,7 @@ getBackward(length:number, callback: AsyncCallback&lt;string&gt;): void
 | 错误码ID | 错误信息                     |
 | -------- | ------------------------------ |
 | 12800003 | input method client error.     |
-| 12800006 | Input method controller error. |
+| 12800006 | input method controller error. |
 
 **示例：**
 
@@ -1060,7 +1060,7 @@ getBackward(length:number): Promise&lt;string&gt;
 | 错误码ID | 错误信息                     |
 | -------- | ------------------------------ |
 | 12800003 | input method client error.     |
-| 12800006 | Input method controller error. |
+| 12800006 | input method controller error. |
 
 **示例：**
 
@@ -1098,7 +1098,7 @@ deleteForward(length:number, callback: AsyncCallback&lt;boolean&gt;): void
 
 | 错误码ID | 错误信息                 |
 | -------- | -------------------------- |
-| 12800002 | Input method engine error. |
+| 12800002 | input method engine error. |
 | 12800003 | input method client error. |
 
 **示例：**
@@ -1148,7 +1148,7 @@ deleteForward(length:number): Promise&lt;boolean&gt;
 
 | 错误码ID | 错误信息                 |
 | -------- | -------------------------- |
-| 12800002 | Input method engine error. |
+| 12800002 | input method engine error. |
 | 12800003 | input method client error. |
 
 **示例：**
@@ -1191,7 +1191,7 @@ deleteBackward(length:number, callback: AsyncCallback&lt;boolean&gt;): void
 
 | 错误码ID | 错误信息                 |
 | -------- | -------------------------- |
-| 12800002 | Input method engine error. |
+| 12800002 | input method engine error. |
 | 12800003 | input method client error. |
 
 **示例：**
@@ -1241,7 +1241,7 @@ deleteBackward(length:number): Promise&lt;boolean&gt;
 
 | 错误码ID | 错误信息                 |
 | -------- | -------------------------- |
-| 12800002 | Input method engine error. |
+| 12800002 | input method engine error. |
 | 12800003 | input method client error. |
 
 **示例：**
@@ -1280,7 +1280,7 @@ insertText(text:string, callback: AsyncCallback&lt;boolean&gt;): void
 
 | 错误码ID | 错误信息                 |
 | -------- | -------------------------- |
-| 12800002 | Input method engine error. |
+| 12800002 | input method engine error. |
 | 12800003 | input method client error. |
 
 **示例：**
@@ -1325,7 +1325,7 @@ insertText(text:string): Promise&lt;boolean&gt;
 
 | 错误码ID | 错误信息                 |
 | -------- | -------------------------- |
-| 12800002 | Input method engine error. |
+| 12800002 | input method engine error. |
 | 12800003 | input method client error. |
 
 **示例：**
diff --git a/zh-cn/application-dev/reference/apis/js-apis-logs.md b/zh-cn/application-dev/reference/apis/js-apis-logs.md
deleted file mode 100644
index 40213556ac95c072d5b85679700734315d2e9470..0000000000000000000000000000000000000000
--- a/zh-cn/application-dev/reference/apis/js-apis-logs.md
+++ /dev/null
@@ -1,101 +0,0 @@
-# console (日志打印)
-
-本模块提供基础的日志打印能力，支持按照日志级别打印日志信息。
-
-如果需要使用更高级的日志打印服务，比如按照指定标识筛选日志内容，推荐使用[`@ohos.hilog`](js-apis-hilog.md)。
-
-> **说明：**
->
-> 本模块首批接口从API version 3开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
-
-## console.debug
-
-debug(message: string): void
-
-打印debug级别的日志信息。
-
-**系统能力：** SystemCapability.ArkUI.ArkUI.Full
-
-**参数：**
-
-| 参数名     | 类型     | 必填   | 说明          |
-| ------- | ------ | ---- | ----------- |
-| message | string | 是    | 表示要打印的文本信息。 |
-
-
-## console.log
-
-log(message: string): void
-
-打印debug级别的日志信息。
-
-**系统能力：** SystemCapability.ArkUI.ArkUI.Full
-
-**参数：**
-
-| 参数名     | 类型     | 必填   | 说明          |
-| ------- | ------ | ---- | ----------- |
-| message | string | 是    | 表示要打印的文本信息。 |
-
-
-## console.info
-
-info(message: string): void
-
-打印info级别的日志信息。
-
-**系统能力：** SystemCapability.ArkUI.ArkUI.Full
-
-**参数：**
-
-| 参数名     | 类型     | 必填   | 说明          |
-| ------- | ------ | ---- | ----------- |
-| message | string | 是    | 表示要打印的文本信息。 |
-
-
-## console.warn
-
-warn(message: string): void
-
-打印warn级别的日志信息。
-
-**系统能力：** SystemCapability.ArkUI.ArkUI.Full
-
-**参数：**
-
-| 参数名     | 类型     | 必填   | 说明          |
-| ------- | ------ | ---- | ----------- |
-| message | string | 是    | 表示要打印的文本信息。 |
-
-
-## console.error
-
-error(message: string): void
-
-打印error级别的日志信息。
-
-**系统能力：** SystemCapability.ArkUI.ArkUI.Full
-
-**参数：**
-
-| 参数名     | 类型     | 必填   | 说明          |
-| ------- | ------ | ---- | ----------- |
-| message | string | 是    | 表示要打印的文本信息。 |
-
-
-## 示例
-
-```
-export default {    
-  clickConsole(){        
-    var versionCode = 1;        
-    console.info('Hello World. The current version code is ' + versionCode);        
-    console.log(`versionCode: ${versionCode}`);        
-    // 以下写法从API Version 6开始支持console.log('versionCode:%d.', versionCode);    
-  }
-}
-```
-
-在DevEco Studio的底部，切换到“HiLog”窗口。选择当前的设备及进程，日志级别选择Info，搜索内容设置为“Hello World”。此时窗口仅显示符合条件的日志，效果如图所示：
-
-![zh-cn_image_0000001200913929](figures/zh-cn_image_0000001200913929.png)
diff --git a/zh-cn/application-dev/reference/apis/js-apis-media.md b/zh-cn/application-dev/reference/apis/js-apis-media.md
index bb377864a18274fd47c1ed8a52e6cb89861f2db2..8c816b559d8c79eefba7b10b68fef070c0a57c5d 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-media.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-media.md
@@ -45,15 +45,15 @@ createAVPlayer(callback: AsyncCallback\<AVPlayer>): void
 **示例：**
 
 ```js
-let avPlayer
+let avPlayer;
 
 media.createAVPlayer((error, video) => {
-   if (video != null) {
-       avPlayer = video;
-       console.info('createAVPlayer success');
-   } else {
-       console.info(`createAVPlayer fail, error:${error}`);
-   }
+  if (video != null) {
+    avPlayer = video;
+    console.info('createAVPlayer success');
+  } else {
+    console.error(`createAVPlayer fail, error message:${error.message}`);
+  }
 });
 ```
 
@@ -82,17 +82,17 @@ createAVPlayer(): Promise\<AVPlayer>
 **示例：**
 
 ```js
-let avPlayer
+let avPlayer;
 
 media.createAVPlayer().then((video) => {
-    if (video != null) {
-       avPlayer = video;
-       console.info('createAVPlayer success');
-   } else {
-       console.info('createAVPlayer fail');
-   }
+  if (video != null) {
+    avPlayer = video;
+    console.info('createAVPlayer success');
+  } else {
+    console.error('createAVPlayer fail');
+  }
 }).catch((error) => {
-   console.info(`AVPlayer catchCallback, error:${error}`);
+  console.error(`AVPlayer catchCallback, error message:${error.message}`);
 });
 ```
 
@@ -124,15 +124,15 @@ createAVRecorder(callback: AsyncCallback\<AVRecorder>): void
 **示例：**
 
 ```js
-let avRecorder
+let avRecorder;
 
 media.createAVRecorder((error, recorder) => {
-   if (recorder != null) {
-       avRecorder = recorder;
-       console.info('createAVRecorder success');
-   } else {
-       console.info(`createAVRecorder fail, error:${error}`);
-   }
+  if (recorder != null) {
+    avRecorder = recorder;
+    console.info('createAVRecorder success');
+  } else {
+    console.error(`createAVRecorder fail, error message:${error.message}`);
+  }
 });
 ```
 
@@ -164,17 +164,17 @@ createAVRecorder(): Promise\<AVRecorder>
 **示例：**
 
 ```js
-let avRecorder
+let avRecorder;
 
 media.createAVRecorder().then((recorder) => {
-    if (recorder != null) {
-       avRecorder = recorder;
-       console.info('createAVRecorder success');
-   } else {
-       console.info('createAVRecorder fail');
-   }
+  if (recorder != null) {
+    avRecorder = recorder;
+    console.info('createAVRecorder success');
+  } else {
+    console.error('createAVRecorder fail');
+  }
 }).catch((error) => {
-   console.info(`createAVRecorder catchCallback, error:${error}`);
+  console.error(`createAVRecorder catchCallback, error message:${error.message}`);
 });
 ```
 
@@ -206,15 +206,15 @@ createVideoRecorder(callback: AsyncCallback\<VideoRecorder>): void
 **示例：**
 
 ```js
-let videoRecorder
+let videoRecorder;
 
 media.createVideoRecorder((error, video) => {
-   if (video != null) {
-       videoRecorder = video;
-       console.info('video createVideoRecorder success');
-   } else {
-       console.info(`video createVideoRecorder fail, error:${error}`);
-   }
+  if (video != null) {
+    videoRecorder = video;
+    console.info('video createVideoRecorder success');
+  } else {
+    console.error(`video createVideoRecorder fail, error message:${error.message}`);
+  }
 });
 ```
 
@@ -246,17 +246,17 @@ createVideoRecorder(): Promise\<VideoRecorder>
 **示例：**
 
 ```js
-let videoRecorder
+let videoRecorder;
 
 media.createVideoRecorder().then((video) => {
-    if (video != null) {
-       videoRecorder = video;
-       console.info('video createVideoRecorder success');
-   } else {
-       console.info('video createVideoRecorder fail');
-   }
+  if (video != null) {
+    videoRecorder = video;
+    console.info('video createVideoRecorder success');
+  } else {
+    console.error('video createVideoRecorder fail');
+  }
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error message:${error.message}`);
 });
 ```
 
@@ -397,38 +397,38 @@ on(type: 'stateChange', callback: (state: AVPlayerState, reason: StateChangeReas
 
 ```js
 avPlayer.on('stateChange', async (state, reason) => {
-    switch (state) {
-        case 'idle':
-            console.info('state idle called')
-            break;
-        case 'initialized':
-            console.info('initialized prepared called')
-            break;
-        case 'prepared':
-            console.info('state prepared called')
-            break;
-        case 'playing':
-            console.info('state playing called')
-            break;
-        case 'paused':
-            console.info('state paused called')
-            break;
-        case 'completed':
-            console.info('state completed called')
-            break;
-        case 'stopped':
-            console.info('state stopped called')
-            break;
-        case 'released':
-            console.info('state released called')
-            break;
-        case 'error':
-            console.info('state error called')
-            break;
-        default:
-            console.info('unkown state :' + state)
-            break;
-    }
+  switch (state) {
+    case 'idle':
+      console.info('state idle called')
+      break;
+    case 'initialized':
+      console.info('initialized prepared called')
+      break;
+    case 'prepared':
+      console.info('state prepared called')
+      break;
+    case 'playing':
+      console.info('state playing called')
+      break;
+    case 'paused':
+      console.info('state paused called')
+      break;
+    case 'completed':
+      console.info('state completed called')
+      break;
+    case 'stopped':
+      console.info('state stopped called')
+      break;
+    case 'released':
+      console.info('state released called')
+      break;
+    case 'error':
+      console.info('state error called')
+      break;
+    default:
+      console.info('unkown state :' + state)
+      break;
+  }
 })
 ```
 
@@ -485,8 +485,8 @@ AVPlayer回调的**错误分类**<a name = error_info></a>可以分为以下几
 
 ```js
 avPlayer.on('error', (error) => {
-    console.info('error happened,and error message is :' + error.message)
-    console.info('error happened,and error code is :' + error.code)
+  console.error('error happened,and error message is :' + error.message)
+  console.error('error happened,and error code is :' + error.code)
 })
 ```
 
@@ -537,11 +537,11 @@ prepare(callback: AsyncCallback\<void>): void
 
 ```js
 avPlayer.prepare((err) => {
-    if (err == null) {
-        console.info('prepare success');
-    } else {
-        console.error('prepare filed,error message is :' + err.message)
-    }
+  if (err == null) {
+    console.info('prepare success');
+  } else {
+    console.error('prepare filed,error message is :' + err.message)
+  }
 })
 ```
 
@@ -572,9 +572,9 @@ prepare(): Promise\<void>
 
 ```js
 avPlayer.prepare().then(() => {
-    console.info('prepare success');
+  console.info('prepare success');
 }, (err) => {
-    console.error('prepare filed,error message is :' + err.message)
+  console.error('prepare filed,error message is :' + err.message)
 })
 ```
 
@@ -604,11 +604,11 @@ play(callback: AsyncCallback\<void>): void
 
 ```js
 avPlayer.play((err) => {
-    if (err == null) {
-        console.info('play success');
-    } else {
-        console.error('play filed,error message is :' + err.message)
-    }
+  if (err == null) {
+    console.info('play success');
+  } else {
+    console.error('play filed,error message is :' + err.message)
+  }
 })
 ```
 
@@ -638,9 +638,9 @@ play(): Promise\<void>
 
 ```js
 avPlayer.play().then(() => {
-    console.info('play success');
+  console.info('play success');
 }, (err) => {
-    console.error('play filed,error message is :' + err.message)
+  console.error('play filed,error message is :' + err.message)
 })
 ```
 
@@ -670,11 +670,11 @@ pause(callback: AsyncCallback\<void>): void
 
 ```js
 avPlayer.pause((err) => {
-    if (err == null) {
-        console.info('pause success');
-    } else {
-        console.error('pause filed,error message is :' + err.message)
-    }
+  if (err == null) {
+    console.info('pause success');
+  } else {
+    console.error('pause filed,error message is :' + err.message)
+  }
 })
 ```
 
@@ -704,9 +704,9 @@ pause(): Promise\<void>
 
 ```js
 avPlayer.pause().then(() => {
-    console.info('pause success');
+  console.info('pause success');
 }, (err) => {
-    console.error('pause filed,error message is :' + err.message)
+  console.error('pause filed,error message is :' + err.message)
 })
 ```
 
@@ -736,11 +736,11 @@ stop(callback: AsyncCallback\<void>): void
 
 ```js
 avPlayer.stop((err) => {
-    if (err == null) {
-        console.info('stop success');
-    } else {
-        console.error('stop filed,error message is :' + err.message)
-    }
+  if (err == null) {
+    console.info('stop success');
+  } else {
+    console.error('stop filed,error message is :' + err.message)
+  }
 })
 ```
 
@@ -770,9 +770,9 @@ stop(): Promise\<void>
 
 ```js
 avPlayer.stop().then(() => {
-    console.info('stop success');
+  console.info('stop success');
 }, (err) => {
-    console.error('stop filed,error message is :' + err.message)
+  console.error('stop filed,error message is :' + err.message)
 })
 ```
 
@@ -802,11 +802,11 @@ reset(callback: AsyncCallback\<void>): void
 
 ```js
 avPlayer.reset((err) => {
-    if (err == null) {
-        console.info('reset success');
-    } else {
-        console.error('reset filed,error message is :' + err.message)
-    }
+  if (err == null) {
+    console.info('reset success');
+  } else {
+    console.error('reset filed,error message is :' + err.message)
+  }
 })
 ```
 
@@ -836,9 +836,9 @@ reset(): Promise\<void>
 
 ```js
 avPlayer.reset().then(() => {
-    console.info('reset success');
+  console.info('reset success');
 }, (err) => {
-    console.error('reset filed,error message is :' + err.message)
+  console.error('reset filed,error message is :' + err.message)
 })
 ```
 
@@ -868,11 +868,11 @@ release(callback: AsyncCallback\<void>): void
 
 ```js
 avPlayer.release((err) => {
-    if (err == null) {
-        console.info('reset success');
-    } else {
-        console.error('release filed,error message is :' + err.message)
-    }
+  if (err == null) {
+    console.info('reset success');
+  } else {
+    console.error('release filed,error message is :' + err.message)
+  }
 })
 ```
 
@@ -902,9 +902,9 @@ release(): Promise\<void>
 
 ```js
 avPlayer.release().then(() => {
-    console.info('release success');
+  console.info('release success');
 }, (err) => {
-    console.error('release filed,error message is :' + err.message)
+  console.error('release filed,error message is :' + err.message)
 })
 ```
 
@@ -933,22 +933,22 @@ getTrackDescription(callback: AsyncCallback\<Array\<MediaDescription>>): void
 **示例：**
 
 ```js
-printfDescription(obj) {
-    for (let item in obj) {
-        let property = obj[item];
-        console.info('audio key is ' + item);
-        console.info('audio value is ' + property);
-    }
+function printfDescription(obj) {
+  for (let item in obj) {
+    let property = obj[item];
+    console.info('audio key is ' + item);
+    console.info('audio value is ' + property);
+  }
 }
 
 avPlayer.getTrackDescription((error, arrList) => {
-    if ((arrList) != null) {
-        for (let i = 0; i < arrList.length; i++) {
-            printfDescription(arrList[i]);
-        }
-    } else {
-        console.log(`video getTrackDescription fail, error:${error}`);
+  if ((arrList) != null) {
+    for (let i = 0; i < arrList.length; i++) {
+      printfDescription(arrList[i]);
     }
+  } else {
+    console.log(`video getTrackDescription fail, error:${error}`);
+  }
 });
 ```
 
@@ -979,24 +979,24 @@ getTrackDescription(): Promise\<Array\<MediaDescription>>
 ```js
 let arrayDescription;
 
-printfDescription(obj) {
-    for (let item in obj) {
-        let property = obj[item];
-        console.info('audio key is ' + item);
-        console.info('audio value is ' + property);
-    }
+function printfDescription(obj) {
+  for (let item in obj) {
+    let property = obj[item];
+    console.info('audio key is ' + item);
+    console.info('audio value is ' + property);
+  }
 }
 avPlayer.getTrackDescription().then((arrList) => {
-    if (arrList != null) {
-        arrayDescription = arrList;
-    } else {
-        console.log('video getTrackDescription fail');
-    }
+  if (arrList != null) {
+    arrayDescription = arrList;
+  } else {
+    console.log('video getTrackDescription fail');
+  }
 }).catch((error) => {
-    console.info(`video catchCallback, error:${error}`);
+  console.info(`video catchCallback, error:${error}`);
 });
 for (let i = 0; i < arrayDescription.length; i++) {
-    printfDescription(arrayDescription[i]);
+  printfDescription(arrayDescription[i]);
 }
 ```
 
@@ -1041,7 +1041,7 @@ on(type: 'seekDone', callback: Callback\<number>): void
 
 ```js
 avPlayer.on('seekDone', (seekDoneTime:number) => {
-    console.info('seekDone success,and seek time is:' + seekDoneTime)
+  console.info('seekDone success,and seek time is:' + seekDoneTime)
 })
 ```
 
@@ -1104,7 +1104,7 @@ on(type: 'speedDone', callback: Callback\<number>): void
 
 ```js
 avPlayer.on('speedDone', (speed:number) => {
-    console.info('speedDone success,and speed value is:' + speed)
+  console.info('speedDone success,and speed value is:' + speed)
 })
 ```
 
@@ -1140,7 +1140,7 @@ setBitrate(bitrate: number): void
 
 | 参数名  | 类型   | 必填 | 说明                                                         |
 | ------- | ------ | ---- | ------------------------------------------------------------ |
-| bitrate | number | 是   | 指定比特率，可以通过[availableBitrates](#availableBitrates_on)事件获得当前HLS协议流可用的比特率，如果用户指定的比特率不在此列表中，则播放器将从可用比特率列表中选择最小和最接近的比特率。如果通过availableBitrates时间获得的比特率列表长度为0，则不支持指定比特率，也不会产生bitrateDone回调。 |
+| bitrate | number | 是   | 指定比特率，可以通过[availableBitrates](#availableBitrates_on)事件获得当前HLS协议流可用的比特率，如果用户指定的比特率不在此列表中，则播放器将从可用比特率列表中选择最小和最接近的比特率。如果通过availableBitrates事件获得的比特率列表长度为0，则不支持指定比特率，也不会产生bitrateDone回调。 |
 
 **示例：**
 
@@ -1168,7 +1168,7 @@ on(type: 'bitrateDone', callback: Callback\<number>): void
 
 ```js
 avPlayer.on('bitrateDone', (bitrate:number) => {
-    console.info('bitrateDone success,and bitrate value is:' + bitrate)
+  console.info('bitrateDone success,and bitrate value is:' + bitrate)
 })
 ```
 
@@ -1211,7 +1211,7 @@ on(type: 'availableBitrates', callback: (bitrates: Array\<number>) => void): voi
 
 ```js
 avPlayer.on('availableBitrates', (bitrates: Array<number>) => {
-    console.info('availableBitrates success,and availableBitrates length is:' + bitrates.length)
+  console.info('availableBitrates success,and availableBitrates length is:' + bitrates.length)
 })
 ```
 
@@ -1275,7 +1275,7 @@ on(type: 'volumeChange', callback: Callback\<number>): void
 
 ```js
 avPlayer.on('volumeChange', (vol:number) => {
-    console.info('volumeChange success,and new volume is :' + vol)
+  console.info('volumeChange success,and new volume is :' + vol)
 })
 ```
 
@@ -1291,7 +1291,7 @@ off(type: 'volumeChange'): void
 
 | 参数名 | 类型   | 必填 | 说明                                                         |
 | ------ | ------ | ---- | ------------------------------------------------------------ |
-| type   | string | 是   | setVolume生效的事件回调类型，取消注册的事件：'availableBitrates'。 |
+| type   | string | 是   | setVolume生效的事件回调类型，取消注册的事件：'volumeChange'。 |
 
 **示例：**
 
@@ -1318,7 +1318,7 @@ on(type: 'endOfStream', callback: Callback\<void>): void
 
 ```js
 avPlayer.on('endOfStream', () => {
-    console.info('endOfStream success')
+  console.info('endOfStream success')
 })
 ```
 
@@ -1361,7 +1361,7 @@ on(type: 'timeUpdate', callback: Callback\<number>): void
 
 ```js
 avPlayer.on('timeUpdate', (time:number) => {
-    console.info('timeUpdate success,and new time is :' + time)
+  console.info('timeUpdate success,and new time is :' + time)
 })
 ```
 
@@ -1404,7 +1404,7 @@ on(type: 'durationUpdate', callback: Callback\<number>): void
 
 ```js
 avPlayer.on('durationUpdate', (duration) => {
-    console.info('durationUpdate success,new duration is :' + duration)
+  console.info('durationUpdate success,new duration is :' + duration)
 })
 ```
 
@@ -1447,7 +1447,7 @@ on(type: 'bufferingUpdate', callback: (infoType: BufferingInfoType, value: numbe
 
 ```js
 avPlayer.on('bufferingUpdate', (infoType: media.BufferingInfoType, value: number) => {
-    console.info('bufferingUpdate success,and infoType value is:' + infoType + ', value is :' + value)
+  console.info('bufferingUpdate success,and infoType value is:' + infoType + ', value is :' + value)
 })
 ```
 
@@ -1490,7 +1490,7 @@ on(type: 'startRenderFrame', callback: Callback\<void>): void
 
 ```js
 avPlayer.on('startRenderFrame', () => {
-    console.info('startRenderFrame success')
+  console.info('startRenderFrame success')
 })
 ```
 
@@ -1533,7 +1533,7 @@ on(type: 'videoSizeChange', callback: (width: number, height: number) => void):
 
 ```js
 avPlayer.on('videoSizeChange', (width: number, height: number) => {
-    console.info('videoSizeChange success,and width is:' + width + ', height is :' + height)
+  console.info('videoSizeChange success,and width is:' + width + ', height is :' + height)
 })
 ```
 
@@ -1578,7 +1578,7 @@ on(type: 'audioInterrupt', callback: (info: audio.InterruptEvent) => void): void
 import audio from '@ohos.multimedia.audio';
 
 avPlayer.on('audioInterrupt', (info: audio.InterruptEvent) => {
-    console.info('audioInterrupt success,and InterruptEvent info is:' + info)
+  console.info('audioInterrupt success,and InterruptEvent info is:' + info)
 })
 ```
 
@@ -1679,19 +1679,19 @@ avPlayer.off('audioInterrupt')
 ```js
 import media from '@ohos.multimedia.media'
 function printfItemDescription(obj, key) {
-    let property = obj[key];
-    console.info('audio key is ' + key); // 通过key值获取对应的value。key值具体可见[MediaDescriptionKey]
-    console.info('audio value is ' + property); //对应key值得value。其类型可为任意类型，具体key对应value的类型可参考[MediaDescriptionKey]
+  let property = obj[key];
+  console.info('audio key is ' + key); // 通过key值获取对应的value。key值具体可见[MediaDescriptionKey]
+  console.info('audio value is ' + property); //对应key值得value。其类型可为任意类型，具体key对应value的类型可参考[MediaDescriptionKey]
 }
 let audioPlayer = media.createAudioPlayer();
 audioPlayer.getTrackDescription((error, arrList) => {
-    if (arrList != null) {
-        for (let i = 0; i < arrList.length; i++) {
-            printfItemDescription(arrList[i], media.MediaDescriptionKey.MD_KEY_TRACK_TYPE);  //打印出每条轨道MD_KEY_TRACK_TYPE的值
-        }
-    } else {
-        console.log(`audio getTrackDescription fail, error:${error}`);
+  if (arrList != null) {
+    for (let i = 0; i < arrList.length; i++) {
+      printfItemDescription(arrList[i], media.MediaDescriptionKey.MD_KEY_TRACK_TYPE);  //打印出每条轨道MD_KEY_TRACK_TYPE的值
     }
+  } else {
+    console.log(`audio getTrackDescription fail, error:${error}`);
+  }
 });
 ```
 
@@ -1748,32 +1748,32 @@ prepare(config: AVRecorderConfig, callback: AsyncCallback\<void>): void
 ```js
 // 配置参数以实际硬件设备支持的范围为准
 let AVRecorderProfile = {
-    audioBitrate : 48000,
-    audioChannels : 2,
-    audioCodec : media.CodecMimeType.AUDIO_AAC,
-    audioSampleRate : 48000,
-    fileFormat : media.ContainerFormatType.CFT_MPEG_4,
-    videoBitrate : 2000000,
-    videoCodec : media.CodecMimeType.VIDEO_AVC,
-    videoFrameWidth : 640,
-    videoFrameHeight : 480,
-    videoFrameRate : 30
+  audioBitrate : 48000,
+  audioChannels : 2,
+  audioCodec : media.CodecMimeType.AUDIO_AAC,
+  audioSampleRate : 48000,
+  fileFormat : media.ContainerFormatType.CFT_MPEG_4,
+  videoBitrate : 2000000,
+  videoCodec : media.CodecMimeType.VIDEO_AVC,
+  videoFrameWidth : 640,
+  videoFrameHeight : 480,
+  videoFrameRate : 30
 }
 let AVRecorderConfig = {
-    audioSourceType : media.AudioSourceType.AUDIO_SOURCE_TYPE_MIC,
-    videoSourceType : media.VideoSourceType.VIDEO_SOURCE_TYPE_SURFACE_YUV,
-    profile : AVRecorderProfile,
-    url : 'fd://', // 文件需先由调用者创建，赋予读写权限，将文件fd传给此参数，eg.fd://45
-    rotation : 0, // 合理值0、90、180、270，非合理值prepare接口将报错
-    location : { latitude : 30, longitude : 130 }
+  audioSourceType : media.AudioSourceType.AUDIO_SOURCE_TYPE_MIC,
+  videoSourceType : media.VideoSourceType.VIDEO_SOURCE_TYPE_SURFACE_YUV,
+  profile : AVRecorderProfile,
+  url : 'fd://', // 文件需先由调用者创建，赋予读写权限，将文件fd传给此参数，eg.fd://45
+  rotation : 0, // 合理值0、90、180、270，非合理值prepare接口将报错
+  location : { latitude : 30, longitude : 130 }
 }
 
 avRecorder.prepare(AVRecorderConfig, (err) => {
-    if (err == null) {
-        console.info('prepare success');
-    } else {
-        console.info('prepare failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('prepare success');
+  } else {
+    console.error('prepare failed and error is ' + err.message);
+  }
 })
 ```
 
@@ -1817,30 +1817,30 @@ prepare(config: AVRecorderConfig): Promise\<void>
 ```js
 // 配置参数以实际硬件设备支持的范围为准
 let AVRecorderProfile = {
-    audioBitrate : 48000,
-    audioChannels : 2,
-    audioCodec : media.CodecMimeType.AUDIO_AAC,
-    audioSampleRate : 48000,
-    fileFormat : media.ContainerFormatType.CFT_MPEG_4,
-    videoBitrate : 2000000,
-    videoCodec : media.CodecMimeType.VIDEO_AVC,
-    videoFrameWidth : 640,
-    videoFrameHeight : 480,
-    videoFrameRate : 30
+  audioBitrate : 48000,
+  audioChannels : 2,
+  audioCodec : media.CodecMimeType.AUDIO_AAC,
+  audioSampleRate : 48000,
+  fileFormat : media.ContainerFormatType.CFT_MPEG_4,
+  videoBitrate : 2000000,
+  videoCodec : media.CodecMimeType.VIDEO_AVC,
+  videoFrameWidth : 640,
+  videoFrameHeight : 480,
+  videoFrameRate : 30
 }
 let AVRecorderConfig = {
-    audioSourceType : media.AudioSourceType.AUDIO_SOURCE_TYPE_MIC,
-    videoSourceType : media.VideoSourceType.VIDEO_SOURCE_TYPE_SURFACE_YUV,
-    profile : AVRecorderProfile,
-    url : 'fd://',  // 文件需先由调用者创建，赋予读写权限，将文件fd传给此参数，eg.fd://45
-    rotation : 0, // 合理值0、90、180、270，非合理值prepare接口报错
-    location : { latitude : 30, longitude : 130 }
+  audioSourceType : media.AudioSourceType.AUDIO_SOURCE_TYPE_MIC,
+  videoSourceType : media.VideoSourceType.VIDEO_SOURCE_TYPE_SURFACE_YUV,
+  profile : AVRecorderProfile,
+  url : 'fd://',  // 文件需先由调用者创建，赋予读写权限，将文件fd传给此参数，eg.fd://45
+  rotation : 0, // 合理值0、90、180、270，非合理值prepare接口报错
+  location : { latitude : 30, longitude : 130 }
 }
 
 avRecorder.prepare(AVRecorderConfig).then(() => {
-    console.info('prepare success');
+  console.info('prepare success');
 }).catch((err) => {
-    console.info('prepare failed and catch error is ' + err.message);
+  console.error('prepare failed and catch error is ' + err.message);
 });
 
 ```
@@ -1879,12 +1879,12 @@ getInputSurface(callback: AsyncCallback\<string>): void
 let surfaceID = null; // 该surfaceID用于传递给相机接口创造videoOutput
 
 avRecorder.getInputSurface((err, surfaceId) => {
-    if (err == null) {
-        console.info('getInputSurface success');
-        surfaceID = surfaceId;
-    } else {
-        console.info('getInputSurface failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('getInputSurface success');
+    surfaceID = surfaceId;
+  } else {
+    console.error('getInputSurface failed and error is ' + err.message);
+  }
 });
 
 ```
@@ -1923,10 +1923,10 @@ getInputSurface(): Promise\<string>
 let surfaceID = null; // 该surfaceID用于传递给相机接口创造videoOutput
 
 avRecorder.getInputSurface().then((surfaceId) => {
-    console.info('getInputSurface success');
-    surfaceID = surfaceId;
+  console.info('getInputSurface success');
+  surfaceID = surfaceId;
 }).catch((err) => {
-    console.info('getInputSurface failed and catch error is ' + err.message);
+  console.error('getInputSurface failed and catch error is ' + err.message);
 });
 ```
 
@@ -1960,11 +1960,11 @@ start(callback: AsyncCallback\<void>): void
 
 ```js
 avRecorder.start((err) => {
-    if (err == null) {
-        console.info('start AVRecorder success');
-    } else {
-        console.info('start AVRecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('start AVRecorder success');
+  } else {
+    console.error('start AVRecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -1998,9 +1998,9 @@ start(): Promise\<void>
 
 ```js
 avRecorder.start().then(() => {
-    console.info('start AVRecorder success');
+  console.info('start AVRecorder success');
 }).catch((err) => {
-    console.info('start AVRecorder failed and catch error is ' + err.message);
+  console.error('start AVRecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -2034,11 +2034,11 @@ pause(callback: AsyncCallback\<void>): void
 
 ```js
 avRecorder.pause((err) => {
-    if (err == null) {
-        console.info('pause AVRecorder success');
-    } else {
-        console.info('pause AVRecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('pause AVRecorder success');
+  } else {
+    console.error('pause AVRecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -2072,9 +2072,9 @@ pause(): Promise\<void>
 
 ```js
 avRecorder.pause().then(() => {
-    console.info('pause AVRecorder success');
+  console.info('pause AVRecorder success');
 }).catch((err) => {
-    console.info('pause AVRecorder failed and catch error is ' + err.message);
+  console.error('pause AVRecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -2108,11 +2108,11 @@ resume(callback: AsyncCallback\<void>): void
 
 ```js
 avRecorder.resume((err) => {
-    if (err == null) {
-        console.info('resume AVRecorder success');
-    } else {
-        console.info('resume AVRecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('resume AVRecorder success');
+  } else {
+    console.error('resume AVRecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -2146,9 +2146,9 @@ resume(): Promise\<void>
 
 ```js
 avRecorder.resume().then(() => {
-    console.info('resume AVRecorder success');
+  console.info('resume AVRecorder success');
 }).catch((err) => {
-    console.info('resume AVRecorder failed and catch error is ' + err.message);
+  console.error('resume AVRecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -2184,11 +2184,11 @@ stop(callback: AsyncCallback\<void>): void
 
 ```js
 avRecorder.stop((err) => {
-    if (err == null) {
-        console.info('stop AVRecorder success');
-    } else {
-        console.info('stop AVRecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('stop AVRecorder success');
+  } else {
+    console.error('stop AVRecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -2224,9 +2224,9 @@ stop(): Promise\<void>
 
 ```js
 avRecorder.stop().then(() => {
-    console.info('stop AVRecorder success');
+  console.info('stop AVRecorder success');
 }).catch((err) => {
-    console.info('stop AVRecorder failed and catch error is ' + err.message);
+  console.error('stop AVRecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -2259,11 +2259,11 @@ reset(callback: AsyncCallback\<void>): void
 
 ```js
 avRecorder.reset((err) => {
-    if (err == null) {
-        console.info('reset AVRecorder success');
-    } else {
-        console.info('reset AVRecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('reset AVRecorder success');
+  } else {
+    console.error('reset AVRecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -2296,9 +2296,9 @@ reset(): Promise\<void>
 
 ```js
 avRecorder.reset().then(() => {
-    console.info('reset AVRecorder success');
+  console.info('reset AVRecorder success');
 }).catch((err) => {
-    console.info('reset AVRecorder failed and catch error is ' + err.message);
+  console.error('reset AVRecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -2330,11 +2330,11 @@ release(callback: AsyncCallback\<void>): void
 
 ```js
 avRecorder.release((err) => {
-    if (err == null) {
-        console.info('release AVRecorder success');
-    } else {
-        console.info('release AVRecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('release AVRecorder success');
+  } else {
+    console.error('release AVRecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -2366,9 +2366,9 @@ release(): Promise\<void>
 
 ```js
 avRecorder.release().then(() => {
-    console.info('release AVRecorder success');
+  console.info('release AVRecorder success');
 }).catch((err) => {
-    console.info('release AVRecorder failed and catch error is ' + err.message);
+  console.error('release AVRecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -2391,7 +2391,7 @@ on(type: 'stateChange', callback: (state: AVRecorderState, reason: StateChangeRe
 
 ```js
 avRecorder.on('stateChange', async (state, reason) => {
-    console.info('case state has changed, new state is :' + state + ',and new reason is : ' + reason);
+  console.info('case state has changed, new state is :' + state + ',and new reason is : ' + reason);
 });
 ```
 
@@ -2445,7 +2445,7 @@ on(type: 'error', callback: ErrorCallback): void
 
 ```js
 avRecorder.on('error', (err) => {
-    console.info('case avRecorder.on(error) called, errMessage is ' + err.message);
+  console.error('case avRecorder.on(error) called, errMessage is ' + err.message);
 });
 ```
 
@@ -2626,34 +2626,34 @@ prepare(config: VideoRecorderConfig, callback: AsyncCallback\<void>): void;
 ```js
 // 配置参数以实际硬件设备支持的范围为准
 let videoProfile = {
-    audioBitrate : 48000,
-    audioChannels : 2,
-    audioCodec : 'audio/mp4a-latm',
-    audioSampleRate : 48000,
-    fileFormat : 'mp4',
-    videoBitrate : 2000000,
-    videoCodec : 'video/avc',
-    videoFrameWidth : 640,
-    videoFrameHeight : 480,
-    videoFrameRate : 30
+  audioBitrate : 48000,
+  audioChannels : 2,
+  audioCodec : 'audio/mp4a-latm',
+  audioSampleRate : 48000,
+  fileFormat : 'mp4',
+  videoBitrate : 2000000,
+  videoCodec : 'video/avc',
+  videoFrameWidth : 640,
+  videoFrameHeight : 480,
+  videoFrameRate : 30
 }
 
 let videoConfig = {
-    audioSourceType : 1,
-    videoSourceType : 0,
-    profile : videoProfile,
-    url : 'fd://xx',   // 文件需先由调用者创建，并给予适当的权限
-    orientationHint : 0,
-    location : { latitude : 30, longitude : 130 },
+  audioSourceType : 1,
+  videoSourceType : 0,
+  profile : videoProfile,
+  url : 'fd://xx',   // 文件需先由调用者创建，并给予适当的权限
+  orientationHint : 0,
+  location : { latitude : 30, longitude : 130 },
 }
 
 // asyncallback
 videoRecorder.prepare(videoConfig, (err) => {
-    if (err == null) {
-        console.info('prepare success');
-    } else {
-        console.info('prepare failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('prepare success');
+  } else {
+    console.error('prepare failed and error is ' + err.message);
+  }
 })
 ```
 
@@ -2697,32 +2697,32 @@ prepare(config: VideoRecorderConfig): Promise\<void>;
 ```js
 // 配置参数以实际硬件设备支持的范围为准
 let videoProfile = {
-    audioBitrate : 48000,
-    audioChannels : 2,
-    audioCodec : 'audio/mp4a-latm',
-    audioSampleRate : 48000,
-    fileFormat : 'mp4',
-    videoBitrate : 2000000,
-    videoCodec : 'video/avc',
-    videoFrameWidth : 640,
-    videoFrameHeight : 480,
-    videoFrameRate : 30
+  audioBitrate : 48000,
+  audioChannels : 2,
+  audioCodec : 'audio/mp4a-latm',
+  audioSampleRate : 48000,
+  fileFormat : 'mp4',
+  videoBitrate : 2000000,
+  videoCodec : 'video/avc',
+  videoFrameWidth : 640,
+  videoFrameHeight : 480,
+  videoFrameRate : 30
 }
 
 let videoConfig = {
-    audioSourceType : 1,
-    videoSourceType : 0,
-    profile : videoProfile,
-    url : 'fd://xx',   // 文件需先由调用者创建，并给予适当的权限
-    orientationHint : 0,
-    location : { latitude : 30, longitude : 130 },
+  audioSourceType : 1,
+  videoSourceType : 0,
+  profile : videoProfile,
+  url : 'fd://xx',   // 文件需先由调用者创建，并给予适当的权限
+  orientationHint : 0,
+  location : { latitude : 30, longitude : 130 },
 }
 
 // promise
 videoRecorder.prepare(videoConfig).then(() => {
-    console.info('prepare success');
+  console.info('prepare success');
 }).catch((err) => {
-    console.info('prepare failed and catch error is ' + err.message);
+  console.error('prepare failed and catch error is ' + err.message);
 });
 ```
 
@@ -2762,12 +2762,12 @@ getInputSurface(callback: AsyncCallback\<string>): void;
 // asyncallback
 let surfaceID = null;                                               // 传递给外界的surfaceID
 videoRecorder.getInputSurface((err, surfaceId) => {
-    if (err == null) {
-        console.info('getInputSurface success');
-        surfaceID = surfaceId;
-    } else {
-        console.info('getInputSurface failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('getInputSurface success');
+    surfaceID = surfaceId;
+  } else {
+    console.error('getInputSurface failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -2807,10 +2807,10 @@ getInputSurface(): Promise\<string>;
 // promise
 let surfaceID = null;                                               // 传递给外界的surfaceID
 videoRecorder.getInputSurface().then((surfaceId) => {
-    console.info('getInputSurface success');
-    surfaceID = surfaceId;
+  console.info('getInputSurface success');
+  surfaceID = surfaceId;
 }).catch((err) => {
-    console.info('getInputSurface failed and catch error is ' + err.message);
+  console.error('getInputSurface failed and catch error is ' + err.message);
 });
 ```
 
@@ -2847,11 +2847,11 @@ start(callback: AsyncCallback\<void>): void;
 ```js
 // asyncallback
 videoRecorder.start((err) => {
-    if (err == null) {
-        console.info('start videorecorder success');
-    } else {
-        console.info('start videorecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('start videorecorder success');
+  } else {
+    console.error('start videorecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -2888,9 +2888,9 @@ start(): Promise\<void>;
 ```js
 // promise
 videoRecorder.start().then(() => {
-    console.info('start videorecorder success');
+  console.info('start videorecorder success');
 }).catch((err) => {
-    console.info('start videorecorder failed and catch error is ' + err.message);
+  console.error('start videorecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -2927,11 +2927,11 @@ pause(callback: AsyncCallback\<void>): void;
 ```js
 // asyncallback
 videoRecorder.pause((err) => {
-    if (err == null) {
-        console.info('pause videorecorder success');
-    } else {
-        console.info('pause videorecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('pause videorecorder success');
+  } else {
+    console.error('pause videorecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -2968,9 +2968,9 @@ pause(): Promise\<void>;
 ```js
 // promise
 videoRecorder.pause().then(() => {
-    console.info('pause videorecorder success');
+  console.info('pause videorecorder success');
 }).catch((err) => {
-    console.info('pause videorecorder failed and catch error is ' + err.message);
+  console.error('pause videorecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -3005,11 +3005,11 @@ resume(callback: AsyncCallback\<void>): void;
 ```js
 // asyncallback
 videoRecorder.resume((err) => {
-    if (err == null) {
-        console.info('resume videorecorder success');
-    } else {
-        console.info('resume videorecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('resume videorecorder success');
+  } else {
+    console.error('resume videorecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -3044,9 +3044,9 @@ resume(): Promise\<void>;
 ```js
 // promise
 videoRecorder.resume().then(() => {
-    console.info('resume videorecorder success');
+  console.info('resume videorecorder success');
 }).catch((err) => {
-    console.info('resume videorecorder failed and catch error is ' + err.message);
+  console.error('resume videorecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -3083,11 +3083,11 @@ stop(callback: AsyncCallback\<void>): void;
 ```js
 // asyncallback
 videoRecorder.stop((err) => {
-    if (err == null) {
-        console.info('stop videorecorder success');
-    } else {
-        console.info('stop videorecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('stop videorecorder success');
+  } else {
+    console.error('stop videorecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -3124,9 +3124,9 @@ stop(): Promise\<void>;
 ```js
 // promise
 videoRecorder.stop().then(() => {
-    console.info('stop videorecorder success');
+  console.info('stop videorecorder success');
 }).catch((err) => {
-    console.info('stop videorecorder failed and catch error is ' + err.message);
+  console.error('stop videorecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -3159,11 +3159,11 @@ release(callback: AsyncCallback\<void>): void;
 ```js
 // asyncallback
 videoRecorder.release((err) => {
-    if (err == null) {
-        console.info('release videorecorder success');
-    } else {
-        console.info('release videorecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('release videorecorder success');
+  } else {
+    console.error('release videorecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -3196,9 +3196,9 @@ release(): Promise\<void>;
 ```js
 // promise
 videoRecorder.release().then(() => {
-    console.info('release videorecorder success');
+  console.info('release videorecorder success');
 }).catch((err) => {
-    console.info('release videorecorder failed and catch error is ' + err.message);
+  console.error('release videorecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -3234,11 +3234,11 @@ reset(callback: AsyncCallback\<void>): void;
 ```js
 // asyncallback
 videoRecorder.reset((err) => {
-    if (err == null) {
-        console.info('reset videorecorder success');
-    } else {
-        console.info('reset videorecorder failed and error is ' + err.message);
-    }
+  if (err == null) {
+    console.info('reset videorecorder success');
+  } else {
+    console.error('reset videorecorder failed and error is ' + err.message);
+  }
 });
 ```
 
@@ -3274,9 +3274,9 @@ reset(): Promise\<void>;
 ```js
 // promise
 videoRecorder.reset().then(() => {
-    console.info('reset videorecorder success');
+  console.info('reset videorecorder success');
 }).catch((err) => {
-    console.info('reset videorecorder failed and catch error is ' + err.message);
+  console.error('reset videorecorder failed and catch error is ' + err.message);
 });
 ```
 
@@ -3309,7 +3309,7 @@ on(type: 'error', callback: ErrorCallback): void
 ```js
 // 当获取videoRecordState接口出错时通过此订阅事件上报
 videoRecorder.on('error', (error) => {                                  // 设置'error'事件回调
-    console.info(`audio error called, error: ${error}`); 
+  console.error(`audio error called, error: ${error}`); 
 })
 ```
 
@@ -3411,15 +3411,15 @@ createVideoPlayer(callback: AsyncCallback\<VideoPlayer>): void
 **示例：**
 
 ```js
-let videoPlayer
+let videoPlayer;
 
 media.createVideoPlayer((error, video) => {
-   if (video != null) {
-       videoPlayer = video;
-       console.info('video createVideoPlayer success');
-   } else {
-       console.info(`video createVideoPlayer fail, error:${error}`);
-   }
+  if (video != null) {
+    videoPlayer = video;
+    console.info('video createVideoPlayer success');
+  } else {
+    console.error(`video createVideoPlayer fail, error:${error}`);
+  }
 });
 ```
 
@@ -3443,17 +3443,17 @@ createVideoPlayer(): Promise\<VideoPlayer>
 **示例：**
 
 ```js
-let videoPlayer
+let videoPlayer;
 
 media.createVideoPlayer().then((video) => {
-   if (video != null) {
-       videoPlayer = video;
-       console.info('video createVideoPlayer success');
-   } else {
-       console.info('video createVideoPlayer fail');
-   }
+  if (video != null) {
+    videoPlayer = video;
+    console.info('video createVideoPlayer success');
+  } else {
+    console.error('video createVideoPlayer fail');
+  }
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 ```
 
@@ -3536,7 +3536,7 @@ play(): void
 
 ```js
 audioPlayer.on('play', () => {    //设置'play'事件回调
-    console.log('audio play success');
+  console.log('audio play success');
 });
 audioPlayer.play();
 ```
@@ -3553,7 +3553,7 @@ pause(): void
 
 ```js
 audioPlayer.on('pause', () => {    //设置'pause'事件回调
-    console.log('audio pause success');
+  console.log('audio pause success');
 });
 audioPlayer.pause();
 ```
@@ -3570,7 +3570,7 @@ stop(): void
 
 ```js
 audioPlayer.on('stop', () => {    //设置'stop'事件回调
-    console.log('audio stop success');
+  console.log('audio stop success');
 });
 audioPlayer.stop();
 ```
@@ -3587,7 +3587,7 @@ reset(): void
 
 ```js
 audioPlayer.on('reset', () => {    //设置'reset'事件回调
-    console.log('audio reset success');
+  console.log('audio reset success');
 });
 audioPlayer.reset();
 ```
@@ -3610,11 +3610,11 @@ seek(timeMs: number): void
 
 ```js
 audioPlayer.on('timeUpdate', (seekDoneTime) => {    //设置'timeUpdate'事件回调
-    if (seekDoneTime == null) {
-        console.info('audio seek fail');
-        return;
-    }
-    console.log('audio seek success. seekDoneTime: ' + seekDoneTime);
+  if (seekDoneTime == null) {
+    console.info('audio seek fail');
+    return;
+  }
+  console.log('audio seek success. seekDoneTime: ' + seekDoneTime);
 });
 audioPlayer.seek(30000);    //seek到30000ms的位置
 ```
@@ -3637,7 +3637,7 @@ setVolume(vol: number): void
 
 ```js
 audioPlayer.on('volumeChange', () => {    //设置'volumeChange'事件回调
-    console.log('audio volumeChange success');
+  console.log('audio volumeChange success');
 });
 audioPlayer.setVolume(1);    //设置音量到100%
 ```
@@ -3675,21 +3675,21 @@ getTrackDescription(callback: AsyncCallback\<Array\<MediaDescription>>): void
 
 ```js
 function printfDescription(obj) {
-    for (let item in obj) {
-        let property = obj[item];
-        console.info('audio key is ' + item);
-        console.info('audio value is ' + property);
-    }
+  for (let item in obj) {
+    let property = obj[item];
+    console.info('audio key is ' + item);
+    console.info('audio value is ' + property);
+  }
 }
 
 audioPlayer.getTrackDescription((error, arrList) => {
-    if (arrList != null) {
-        for (let i = 0; i < arrList.length; i++) {
-            printfDescription(arrList[i]);
-        }
-    } else {
-        console.log(`audio getTrackDescription fail, error:${error}`);
+  if (arrList != null) {
+    for (let i = 0; i < arrList.length; i++) {
+      printfDescription(arrList[i]);
     }
+  } else {
+    console.log(`audio getTrackDescription fail, error:${error}`);
+  }
 });
 ```
 
@@ -3711,25 +3711,25 @@ getTrackDescription(): Promise\<Array\<MediaDescription>>
 
 ```js
 function printfDescription(obj) {
-    for (let item in obj) {
-        let property = obj[item];
-        console.info('audio key is ' + item);
-        console.info('audio value is ' + property);
-    }
+  for (let item in obj) {
+    let property = obj[item];
+    console.info('audio key is ' + item);
+    console.info('audio value is ' + property);
+  }
 }
 let arrayDescription = null
 audioPlayer.getTrackDescription().then((arrList) => {
-    if (arrList != null) {
-        arrayDescription = arrList;
-    } else {
-        console.log('audio getTrackDescription fail');
-    }
+  if (arrList != null) {
+    arrayDescription = arrList;
+  } else {
+    console.log('audio getTrackDescription fail');
+  }
 }).catch((error) => {
-   console.info(`audio catchCallback, error:${error}`);
+  console.info(`audio catchCallback, error:${error}`);
 });
 
 for (let i = 0; i < arrayDescription.length; i++) {
-    printfDescription(arrayDescription[i]);
+  printfDescription(arrayDescription[i]);
 }
 ```
 
@@ -3752,8 +3752,8 @@ on(type: 'bufferingUpdate', callback: (infoType: BufferingInfoType, value: numbe
 
 ```js
 audioPlayer.on('bufferingUpdate', (infoType, value) => {
-    console.log('audio bufferingInfo type: ' + infoType);
-    console.log('audio bufferingInfo value: ' + value);
+  console.log('audio bufferingInfo type: ' + infoType);
+  console.log('audio bufferingInfo value: ' + value);
 });
 ```
 
@@ -3779,40 +3779,40 @@ import fs from '@ohos.file.fs';
 
 let audioPlayer = media.createAudioPlayer();  //创建一个音频播放实例
 audioPlayer.on('dataLoad', () => {            //设置'dataLoad'事件回调，src属性设置成功后，触发此回调
-    console.info('audio set source success');
-    audioPlayer.play();                       //开始播放，并触发'play'事件回调
+  console.info('audio set source success');
+  audioPlayer.play();                       //开始播放，并触发'play'事件回调
 });
 audioPlayer.on('play', () => {                //设置'play'事件回调
-    console.info('audio play success');
-    audioPlayer.seek(30000);                  //调用seek方法，并触发'timeUpdate'事件回调
+  console.info('audio play success');
+  audioPlayer.seek(30000);                  //调用seek方法，并触发'timeUpdate'事件回调
 });
 audioPlayer.on('pause', () => {               //设置'pause'事件回调
-    console.info('audio pause success');
-    audioPlayer.stop();                       //停止播放，并触发'stop'事件回调
+  console.info('audio pause success');
+  audioPlayer.stop();                       //停止播放，并触发'stop'事件回调
 });
 audioPlayer.on('reset', () => {               //设置'reset'事件回调
-    console.info('audio reset success');
-    audioPlayer.release();                    //释放播放实例资源
-    audioPlayer = undefined;
+  console.info('audio reset success');
+  audioPlayer.release();                    //释放播放实例资源
+  audioPlayer = undefined;
 });
 audioPlayer.on('timeUpdate', (seekDoneTime) => {  //设置'timeUpdate'事件回调
-    if (seekDoneTime == null) {
-        console.info('audio seek fail');
-        return;
-    }
-    console.info('audio seek success, and seek time is ' + seekDoneTime);
-    audioPlayer.setVolume(0.5);                //设置音量为50%，并触发'volumeChange'事件回调
+  if (seekDoneTime == null) {
+    console.info('audio seek fail');
+    return;
+  }
+  console.info('audio seek success, and seek time is ' + seekDoneTime);
+  audioPlayer.setVolume(0.5);                //设置音量为50%，并触发'volumeChange'事件回调
 });
 audioPlayer.on('volumeChange', () => {         //设置'volumeChange'事件回调
-    console.info('audio volumeChange success');
-    audioPlayer.pause();                       //暂停播放，并触发'pause'事件回调
+  console.info('audio volumeChange success');
+  audioPlayer.pause();                       //暂停播放，并触发'pause'事件回调
 });
 audioPlayer.on('finish', () => {               //设置'finish'事件回调
-    console.info('audio play finish');
-    audioPlayer.stop();                        //停止播放，并触发'stop'事件回调
+  console.info('audio play finish');
+  audioPlayer.stop();                        //停止播放，并触发'stop'事件回调
 });
 audioPlayer.on('error', (error) => {           //设置'error'事件回调
-    console.info(`audio error called, error: ${error}`);
+  console.error(`audio error called, error: ${error}`);
 });
 
 // 用户选择音频设置fd(本地播放)
@@ -3820,13 +3820,13 @@ let fdPath = 'fd://';
 // path路径的码流可通过"hdc file send D:\xxx\01.mp3 /data/accounts/account_0/appdata" 命令，将其推送到设备上
 let path = '/data/accounts/account_0/appdata/ohos.xxx.xxx.xxx/01.mp3';
 fs.open(path).then((file) => {
-   fdPath = fdPath + '' + file.fd;
-   console.info('open fd success fd is' + fdPath);
-   audioPlayer.src = fdPath;  //设置src属性，并触发'dataLoad'事件回调
+  fdPath = fdPath + '' + file.fd;
+  console.info('open fd success fd is' + fdPath);
+  audioPlayer.src = fdPath;  //设置src属性，并触发'dataLoad'事件回调
 }, (err) => {
-   console.info('open fd failed err is' + err);
+  console.info('open fd failed err is' + err);
 }).catch((err) => {
-   console.info('open fd failed err is' + err);
+  console.info('open fd failed err is' + err);
 });
 ```
 
@@ -3849,11 +3849,11 @@ on(type: 'timeUpdate', callback: Callback\<number>): void
 
 ```js
 audioPlayer.on('timeUpdate', (newTime) => {    //设置'timeUpdate'事件回调
-    if (newTime == null) {
-        console.info('audio timeUpadate fail');
-        return;
-    }
-    console.log('audio timeUpadate success. seekDoneTime: ' + newTime);
+  if (newTime == null) {
+    console.info('audio timeUpadate fail');
+    return;
+  }
+  console.log('audio timeUpadate success. seekDoneTime: ' + newTime);
 });
 audioPlayer.play();    //开始播放后，自动触发时间戳更新事件
 ```
@@ -3877,7 +3877,7 @@ on(type: 'error', callback: ErrorCallback): void
 
 ```js
 audioPlayer.on('error', (error) => {      //设置'error'事件回调
-    console.info(`audio error called, error: ${error}`); 
+  console.error(`audio error called, error: ${error}`); 
 });
 audioPlayer.setVolume(3);  //设置volume为无效值，触发'error'事件
 ```
@@ -3945,11 +3945,11 @@ setDisplaySurface(surfaceId: string, callback: AsyncCallback\<void>): void
 ```js
 let surfaceId = null;
 videoPlayer.setDisplaySurface(surfaceId, (err) => {
-    if (err == null) {
-        console.info('setDisplaySurface success!');
-    } else {
-        console.info('setDisplaySurface fail!');
-    }
+  if (err == null) {
+    console.info('setDisplaySurface success!');
+  } else {
+    console.error('setDisplaySurface fail!');
+  }
 });
 ```
 
@@ -3980,9 +3980,9 @@ setDisplaySurface(surfaceId: string): Promise\<void>
 ```js
 let surfaceId = null;
 videoPlayer.setDisplaySurface(surfaceId).then(() => {
-    console.info('setDisplaySurface success');
+  console.info('setDisplaySurface success');
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 ```
 
@@ -4004,11 +4004,11 @@ prepare(callback: AsyncCallback\<void>): void
 
 ```js
 videoPlayer.prepare((err) => {
-    if (err == null) {
-        console.info('prepare success!');
-    } else {
-        console.info('prepare fail!');
-    }
+  if (err == null) {
+    console.info('prepare success!');
+  } else {
+    console.error('prepare fail!');
+  }
 });
 ```
 
@@ -4030,9 +4030,9 @@ prepare(): Promise\<void>
 
 ```js
 videoPlayer.prepare().then(() => {
-    console.info('prepare success');
+  console.info('prepare success');
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 ```
 
@@ -4054,11 +4054,11 @@ play(callback: AsyncCallback\<void>): void;
 
 ```js
 videoPlayer.play((err) => {
-    if (err == null) {
-        console.info('play success!');
-    } else {
-        console.info('play fail!');
-    }
+  if (err == null) {
+    console.info('play success!');
+  } else {
+    console.error('play fail!');
+  }
 });
 ```
 
@@ -4080,9 +4080,9 @@ play(): Promise\<void>;
 
 ```js
 videoPlayer.play().then(() => {
-    console.info('play success');
+  console.info('play success');
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 ```
 
@@ -4104,11 +4104,11 @@ pause(callback: AsyncCallback\<void>): void
 
 ```js
 videoPlayer.pause((err) => {
-    if (err == null) {
-        console.info('pause success!');
-    } else {
-        console.info('pause fail!');
-    }
+  if (err == null) {
+    console.info('pause success!');
+  } else {
+    console.info('pause fail!');
+  }
 });
 ```
 
@@ -4130,9 +4130,9 @@ pause(): Promise\<void>
 
 ```js
 videoPlayer.pause().then(() => {
-    console.info('pause success');
+  console.info('pause success');
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 ```
 
@@ -4154,11 +4154,11 @@ stop(callback: AsyncCallback\<void>): void
 
 ```js
 videoPlayer.stop((err) => {
-    if (err == null) {
-        console.info('stop success!');
-    } else {
-        console.info('stop fail!');
-    }
+  if (err == null) {
+    console.info('stop success!');
+  } else {
+    console.error('stop fail!');
+  }
 });
 ```
 
@@ -4180,9 +4180,9 @@ stop(): Promise\<void>
 
 ```js
 videoPlayer.stop().then(() => {
-    console.info('stop success');
+  console.info('stop success');
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 ```
 
@@ -4204,11 +4204,11 @@ reset(callback: AsyncCallback\<void>): void
 
 ```js
 videoPlayer.reset((err) => {
-    if (err == null) {
-        console.info('reset success!');
-    } else {
-        console.info('reset fail!');
-    }
+  if (err == null) {
+    console.info('reset success!');
+  } else {
+    console.error('reset fail!');
+  }
 });
 ```
 
@@ -4230,9 +4230,9 @@ reset(): Promise\<void>
 
 ```js
 videoPlayer.reset().then(() => {
-    console.info('reset success');
+  console.info('reset success');
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 ```
 
@@ -4256,11 +4256,11 @@ seek(timeMs: number, callback: AsyncCallback\<number>): void
 ```js
 let seekTime = 5000;
 videoPlayer.seek(seekTime, (err, result) => {
-    if (err == null) {
-        console.info('seek success!');
-    } else {
-        console.info('seek fail!');
-    }
+  if (err == null) {
+    console.info('seek success!');
+  } else {
+    console.error('seek fail!');
+  }
 });
 ```
 
@@ -4286,11 +4286,11 @@ seek(timeMs: number, mode:SeekMode, callback: AsyncCallback\<number>): void
 import media from '@ohos.multimedia.media'
 let seekTime = 5000;
 videoPlayer.seek(seekTime, media.SeekMode.SEEK_NEXT_SYNC, (err, result) => {
-    if (err == null) {
-        console.info('seek success!');
-    } else {
-        console.info('seek fail!');
-    }
+  if (err == null) {
+    console.info('seek success!');
+  } else {
+    console.error('seek fail!');
+  }
 });
 ```
 
@@ -4321,15 +4321,15 @@ seek(timeMs: number, mode?:SeekMode): Promise\<number>
 import media from '@ohos.multimedia.media'
 let seekTime = 5000;
 videoPlayer.seek(seekTime).then((seekDoneTime) => { // seekDoneTime表示seek完成后的时间点
-    console.info('seek success');
+  console.info('seek success');
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 
 videoPlayer.seek(seekTime, media.SeekMode.SEEK_NEXT_SYNC).then((seekDoneTime) => {
-    console.info('seek success');
+  console.info('seek success');
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 ```
 
@@ -4353,11 +4353,11 @@ setVolume(vol: number, callback: AsyncCallback\<void>): void
 ```js
 let vol = 0.5;
 videoPlayer.setVolume(vol, (err, result) => {
-    if (err == null) {
-        console.info('setVolume success!');
-    } else {
-        console.info('setVolume fail!');
-    }
+  if (err == null) {
+    console.info('setVolume success!');
+  } else {
+    console.error('setVolume fail!');
+  }
 });
 ```
 
@@ -4386,9 +4386,9 @@ setVolume(vol: number): Promise\<void>
 ```js
 let vol = 0.5;
 videoPlayer.setVolume(vol).then(() => {
-    console.info('setVolume success');
+  console.info('setVolume success');
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 ```
 
@@ -4410,11 +4410,11 @@ release(callback: AsyncCallback\<void>): void
 
 ```js
 videoPlayer.release((err) => {
-    if (err == null) {
-        console.info('release success!');
-    } else {
-        console.info('release fail!');
-    }
+  if (err == null) {
+    console.info('release success!');
+  } else {
+    console.error('release fail!');
+  }
 });
 ```
 
@@ -4436,9 +4436,9 @@ release(): Promise\<void>
 
 ```js
 videoPlayer.release().then(() => {
-    console.info('release success');
+  console.info('release success');
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 ```
 
@@ -4460,21 +4460,21 @@ getTrackDescription(callback: AsyncCallback\<Array\<MediaDescription>>): void
 
 ```js
 function printfDescription(obj) {
-    for (let item in obj) {
-        let property = obj[item];
-        console.info('video key is ' + item);
-        console.info('video value is ' + property);
-    }
+  for (let item in obj) {
+    let property = obj[item];
+    console.info('video key is ' + item);
+    console.info('video value is ' + property);
+  }
 }
 
 videoPlayer.getTrackDescription((error, arrList) => {
-    if ((arrList) != null) {
-        for (let i = 0; i < arrList.length; i++) {
-            printfDescription(arrList[i]);
-        }
-    } else {
-        console.log(`video getTrackDescription fail, error:${error}`);
+  if ((arrList) != null) {
+    for (let i = 0; i < arrList.length; i++) {
+      printfDescription(arrList[i]);
     }
+  } else {
+    console.log(`video getTrackDescription fail, error:${error}`);
+  }
 });
 ```
 
@@ -4496,25 +4496,25 @@ getTrackDescription(): Promise\<Array\<MediaDescription>>
 
 ```js
 function printfDescription(obj) {
-    for (let item in obj) {
-        let property = obj[item];
-        console.info('video key is ' + item);
-        console.info('video value is ' + property);
-    }
+  for (let item in obj) {
+    let property = obj[item];
+    console.info('video key is ' + item);
+    console.info('video value is ' + property);
+  }
 }
 
 let arrayDescription;
 videoPlayer.getTrackDescription().then((arrList) => {
-    if (arrList != null) {
-        arrayDescription = arrList;
-    } else {
-        console.log('video getTrackDescription fail');
-    }
+  if (arrList != null) {
+    arrayDescription = arrList;
+  } else {
+    console.log('video getTrackDescription fail');
+  }
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.info(`video catchCallback, error:${error}`);
 });
 for (let i = 0; i < arrayDescription.length; i++) {
-    printfDescription(arrayDescription[i]);
+  printfDescription(arrayDescription[i]);
 }
 ```
 
@@ -4540,11 +4540,11 @@ import media from '@ohos.multimedia.media'
 let speed = media.PlaybackSpeed.SPEED_FORWARD_2_00_X;
 
 videoPlayer.setSpeed(speed, (err, result) => {
-    if (err == null) {
-        console.info('setSpeed success!');
-    } else {
-        console.info('setSpeed fail!');
-    }
+  if (err == null) {
+    console.info('setSpeed success!');
+  } else {
+    console.error('setSpeed fail!');
+  }
 });
 ```
 
@@ -4575,9 +4575,9 @@ import media from '@ohos.multimedia.media'
 let speed = media.PlaybackSpeed.SPEED_FORWARD_2_00_X;
 
 videoPlayer.setSpeed(speed).then(() => {
-    console.info('setSpeed success');
+  console.info('setSpeed success');
 }).catch((error) => {
-   console.info(`video catchCallback, error:${error}`);
+  console.error(`video catchCallback, error:${error}`);
 });
 ```
 
@@ -4600,7 +4600,7 @@ on(type: 'playbackCompleted', callback: Callback\<void>): void
 
 ```js
 videoPlayer.on('playbackCompleted', () => {
-    console.info('playbackCompleted success!');
+  console.info('playbackCompleted success!');
 });
 ```
 
@@ -4623,8 +4623,8 @@ on(type: 'bufferingUpdate', callback: (infoType: BufferingInfoType, value: numbe
 
 ```js
 videoPlayer.on('bufferingUpdate', (infoType, value) => {
-    console.log('video bufferingInfo type: ' + infoType);
-    console.log('video bufferingInfo value: ' + value);
+  console.log('video bufferingInfo type: ' + infoType);
+  console.log('video bufferingInfo value: ' + value);
 });
 ```
 
@@ -4647,7 +4647,7 @@ on(type: 'startRenderFrame', callback: Callback\<void>): void
 
 ```js
 videoPlayer.on('startRenderFrame', () => {
-    console.info('startRenderFrame success!');
+  console.info('startRenderFrame success!');
 });
 ```
 
@@ -4670,8 +4670,8 @@ on(type: 'videoSizeChanged', callback: (width: number, height: number) => void):
 
 ```js
 videoPlayer.on('videoSizeChanged', (width, height) => {
-    console.log('video width is: ' + width);
-    console.log('video height is: ' + height);
+  console.log('video width is: ' + width);
+  console.log('video height is: ' + height);
 });
 ```
 
@@ -4694,7 +4694,7 @@ on(type: 'error', callback: ErrorCallback): void
 
 ```js
 videoPlayer.on('error', (error) => {      // 设置'error'事件回调
-    console.info(`video error called, error: ${error}`);
+  console.error(`video error called, error: ${error}`);
 });
 videoPlayer.url = 'fd://error';  //设置错误的播放地址，触发'error'事件
 ```
@@ -4744,16 +4744,16 @@ prepare(config: AudioRecorderConfig): void
 
 ```js
 let audioRecorderConfig = {
-    audioEncoder : media.AudioEncoder.AAC_LC,
-    audioEncodeBitRate : 22050,
-    audioSampleRate : 22050,
-    numberOfChannels : 2,
-    format : media.AudioOutputFormat.AAC_ADTS,
-    uri : 'fd://1',       // 文件需先由调用者创建，并给予适当的权限
-    location : { latitude : 30, longitude : 130},
+  audioEncoder : media.AudioEncoder.AAC_LC,
+  audioEncodeBitRate : 22050,
+  audioSampleRate : 22050,
+  numberOfChannels : 2,
+  format : media.AudioOutputFormat.AAC_ADTS,
+  uri : 'fd://1',       // 文件需先由调用者创建，并给予适当的权限
+  location : { latitude : 30, longitude : 130},
 }
 audioRecorder.on('prepare', () => {    //设置'prepare'事件回调
-    console.log('prepare success');
+  console.log('prepare success');
 });
 audioRecorder.prepare(audioRecorderConfig);
 ```
@@ -4771,7 +4771,7 @@ start(): void
 
 ```js
 audioRecorder.on('start', () => {    //设置'start'事件回调
-    console.log('audio recorder start success');
+  console.log('audio recorder start success');
 });
 audioRecorder.start();
 ```
@@ -4788,7 +4788,7 @@ pause():void
 
 ```js
 audioRecorder.on('pause', () => {    //设置'pause'事件回调
-    console.log('audio recorder pause success');
+  console.log('audio recorder pause success');
 });
 audioRecorder.pause();
 ```
@@ -4805,7 +4805,7 @@ resume():void
 
 ```js
 audioRecorder.on('resume', () => {    //设置'resume'事件回调
-    console.log('audio recorder resume success');
+  console.log('audio recorder resume success');
 });
 audioRecorder.resume();
 ```
@@ -4822,7 +4822,7 @@ stop(): void
 
 ```js
 audioRecorder.on('stop', () => {    //设置'stop'事件回调
-    console.log('audio recorder stop success');
+  console.log('audio recorder stop success');
 });
 audioRecorder.stop();
 ```
@@ -4839,7 +4839,7 @@ release(): void
 
 ```js
 audioRecorder.on('release', () => {    //设置'release'事件回调
-    console.log('audio recorder release success');
+  console.log('audio recorder release success');
 });
 audioRecorder.release();
 audioRecorder = undefined;
@@ -4859,7 +4859,7 @@ reset(): void
 
 ```js
 audioRecorder.on('reset', () => {    //设置'reset'事件回调
-    console.log('audio recorder reset success');
+  console.log('audio recorder reset success');
 });
 audioRecorder.reset();
 ```
@@ -4884,38 +4884,38 @@ on(type: 'prepare' | 'start' | 'pause' | 'resume' | 'stop' | 'release' | 'reset'
 ```js
 let audioRecorder = media.createAudioRecorder();                                  // 创建一个音频录制实例
 let audioRecorderConfig = {
-    audioEncoder : media.AudioEncoder.AAC_LC,
-    audioEncodeBitRate : 22050,
-    audioSampleRate : 22050,
-    numberOfChannels : 2,
-    format : media.AudioOutputFormat.AAC_ADTS,
-    uri : 'fd://xx',                                                            // 文件需先由调用者创建，并给予适当的权限
-    location : { latitude : 30, longitude : 130},
+  audioEncoder : media.AudioEncoder.AAC_LC,
+  audioEncodeBitRate : 22050,
+  audioSampleRate : 22050,
+  numberOfChannels : 2,
+  format : media.AudioOutputFormat.AAC_ADTS,
+  uri : 'fd://xx',                                                            // 文件需先由调用者创建，并给予适当的权限
+  location : { latitude : 30, longitude : 130},
 }
 audioRecorder.on('error', (error) => {                                             // 设置'error'事件回调
-    console.info(`audio error called, error: ${error}`);
+  console.info(`audio error called, error: ${error}`);
 });
 audioRecorder.on('prepare', () => {                                              // 设置'prepare'事件回调
-    console.log('prepare success');
-    audioRecorder.start();                                                       // 开始录制，并触发'start'事件回调
+  console.log('prepare success');
+  audioRecorder.start();                                                       // 开始录制，并触发'start'事件回调
 });
 audioRecorder.on('start', () => {                                                 // 设置'start'事件回调
-    console.log('audio recorder start success');
+  console.log('audio recorder start success');
 });
 audioRecorder.on('pause', () => {                                                 // 设置'pause'事件回调
-    console.log('audio recorder pause success');
+  console.log('audio recorder pause success');
 });
 audioRecorder.on('resume', () => {                                                 // 设置'resume'事件回调
-    console.log('audio recorder resume success');
+  console.log('audio recorder resume success');
 });
 audioRecorder.on('stop', () => {                                                 // 设置'stop'事件回调
-    console.log('audio recorder stop success');
+  console.log('audio recorder stop success');
 });
 audioRecorder.on('release', () => {                                                 // 设置'release'事件回调
-    console.log('audio recorder release success');
+  console.log('audio recorder release success');
 });
 audioRecorder.on('reset', () => {                                                 // 设置'reset'事件回调
-    console.log('audio recorder reset success');
+  console.log('audio recorder reset success');
 });
 audioRecorder.prepare(audioRecorderConfig)                                       // 设置录制参数 ，并触发'prepare'事件回调
 ```
@@ -4939,16 +4939,16 @@ on(type: 'error', callback: ErrorCallback): void
 
 ```js
 let audioRecorderConfig = {
-    audioEncoder : media.AudioEncoder.AAC_LC,
-    audioEncodeBitRate : 22050,
-    audioSampleRate : 22050,
-    numberOfChannels : 2,
-    format : media.AudioOutputFormat.AAC_ADTS,
-    uri : 'fd://xx',                                                     // 文件需先由调用者创建，并给予适当的权限
-    location : { latitude : 30, longitude : 130},
+  audioEncoder : media.AudioEncoder.AAC_LC,
+  audioEncodeBitRate : 22050,
+  audioSampleRate : 22050,
+  numberOfChannels : 2,
+  format : media.AudioOutputFormat.AAC_ADTS,
+  uri : 'fd://xx',                                                     // 文件需先由调用者创建，并给予适当的权限
+  location : { latitude : 30, longitude : 130},
 }
 audioRecorder.on('error', (error) => {                                  // 设置'error'事件回调
-    console.info(`audio error called, error: ${error}`); 
+  console.error(`audio error called, error: ${error}`);
 });
 audioRecorder.prepare(audioRecorderConfig);                            // prepare不设置参数，触发'error'事件
 ```
diff --git a/zh-cn/application-dev/reference/apis/js-apis-net-policy.md b/zh-cn/application-dev/reference/apis/js-apis-net-policy.md
deleted file mode 100644
index 4a5565d19248bc64274f854ee724dfebd9d77d33..0000000000000000000000000000000000000000
--- a/zh-cn/application-dev/reference/apis/js-apis-net-policy.md
+++ /dev/null
@@ -1,1568 +0,0 @@
-# @ohos.net.policy (网络策略管理)
-
-网络策略管理通过对用户使用数据流量进行控制管理，采用防火墙技术实现网络策略的管理。
-
-> **说明：**
->
-> 本模块首批接口从API version 9开始支持。后续版本的新增接口，采用上角标单独标记接口的起始版本。
-
-## 导入模块
-
-```js
-import policy from '@ohos.net.policy'
-```
-
-## policy.setBackgroundAllowed
-
-setBackgroundAllowed(isAllowed: boolean, callback: AsyncCallback\<void>): void
-
-设置后台网络策略，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| isAllowed | boolean | 是   | 是否允许应用后台使用数据 |
-| callback | AsyncCallback\<void> | 是   | 回调函数，成功返回设置后台网络策略的结果，失败返回错误码错误信息。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.setBackgroundAllowed(Boolean(Number.parseInt(this.isBoolean)), (error) => {
-  this.callBack(error);
-  console.log(JSON.stringify(error))
-})
-;
-```
-
-## policy.setBackgroundAllowed
-
-setBackgroundAllowed(isAllowed: boolean): Promise\<void>
-
-设置后台网络策略，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| isAllowed | boolean | 是   | 是否允许应用后台使用数据 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<void> | 以Promise形式返回设定结果，失败返回错误码错误信息。 |
-
-**示例：**
-
-```js
-policy.setBackgroundAllowed(Boolean(Number.parseInt(this.isBoolean))).then(function (error) {
-  console.log(JSON.stringify(error))
-})
-```
-
-## policy.isBackgroundAllowed
-
-isBackgroundAllowed(callback: AsyncCallback\<boolean>): void
-
-获取后台网络策略，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| callback | AsyncCallback\<boolean> | 是   | 回调函数，返回true代表后台策略为允许。失败返回错误码错误信息。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.isBackgroundAllowed((error, data) => {
-  this.callBack(error, data);
-  console.log(JSON.stringify(error))
-  console.log(JSON.stringify(data))
-});
-```
-
-## policy.isBackgroundAllowed
-
-isBackgroundAllowed(): Promise\<boolean>;
-
-获取后台网络策略，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<boolean> | 以Promise形式返回设定结果。 返回true代表后台策略为允许。失败返回错误码错误信息。|
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.isBackgroundAllowed().then(function (error, data) {
-  console.log(JSON.stringify(error))
-  console.log(JSON.stringify(data))
-})
-
-```
-
-## policy.setPolicyByUid
-
-setPolicyByUid(uid: number, policy: NetUidPolicy, callback: AsyncCallback\<void>): void
-
-设置对应uid应用的访问计量网络的策略，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是   | 应用的唯一标识符 |
-| policy | [NetUidPolicy](#netuidpolicy) | 是 | 应用对应的策略 |
-| callback | AsyncCallback\<void> | 是   | 回调函数，成功返回设定结果。失败返回错误码错误信息。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  uid: Number.parseInt(this.firstParam), policy: Number.parseInt(this.currentNetUidPolicy)
-}
-policy.setPolicyByUid(Number.parseInt(this.firstParam), Number.parseInt(this.currentNetUidPolicy), (error) => {
-  console.log(JSON.stringify(error))
-});
-```
-
-## policy.setPolicyByUid
-
-setPolicyByUid(uid: number, policy: NetUidPolicy): Promise\<void>;
-
-设置对应uid应用的访问计量网络的策略，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是   | 应用的唯一标识符 |
-| policy | [NetUidPolicy](#netuidpolicy) | 是 | 应用对应的策略 |
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<void> | 以Promise形式返回设定结果。失败返回错误码错误信息。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  uid: Number.parseInt(this.firstParam), policy: Number.parseInt(this.currentNetUidPolicy)
-}
-policy.setPolicyByUid(Number.parseInt(this.firstParam), Number.parseInt(this.currentNetUidPolicy)).then(function (error) {
-  console.log(JSON.stringify(error))
-})
-
-```
-
-## policy.getPolicyByUid
-
-getPolicyByUid(uid: number, callback: AsyncCallback\<NetUidPolicy>): void
-
-通过应用uid获取策略，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-| callback | AsyncCallback\<[NetUidPolicy](#netuidpolicy)> | 是   | 回调函数，成功返回获取策略结果，失败返回错误码错误信息。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.getPolicyByUid(Number.parseInt(this.firstParam), (error, data) => {
-  this.callBack(error, data);
-});
-```
-
-## policy.getPolicyByUid
-
-getPolicyByUid(uid: number): Promise\<NetUidPolicy>;
-
-通过应用uid获取策略，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<[NetUidPolicy](#netuidpolicy)> | 以Promise形式返回获取策略结果。失败返回错误码错误信息。|
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.getPolicyByUid(Number.parseInt(this.firstParam)).then(function (error, data) {
-  console.log(JSON.stringify(error))
-  console.log(JSON.stringify(data))
-})
-
-```
-
-## policy.getUidsByPolicy
-
-getUidsByPolicy(policy: NetUidPolicy, callback: AsyncCallback\<Array\<number>>): void
-
-通过策略获取设置这一策略的应用uid数组，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| policy | [NetUidPolicy](#netuidpolicy) | 是 | 应用对应的计量网络下的策略 |
-| callback | AsyncCallback\<Array\<number>> | 是   | 回调函数，成功返回应用的uid数组，失败返回错误码错误信息。|
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.getUidsByPolicy(Number.parseInt(this.currentNetUidPolicy), (error, data) => {
-  this.callBack(error, data);
-});
-```
-
-## policy.getUidsByPolicy
-
-function getUidsByPolicy(policy: NetUidPolicy): Promise\<Array\<number>>;
-
-通过策略获取设置这一策略的应用uid数组，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| policy | [NetUidPolicy](#netuidpolicy) | 是 | app对应的计量网络下的策略 |
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<Array\<number>> | 以Promise形式返回应用的uid数组，失败返回错误码错误信息。|
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.getUidsByPolicy(Number.parseInt(this.firstParam)).then(function (error, data) {
-  console.log(JSON.stringify(error))
-  console.log(JSON.stringify(data))
-})
-
-```
-
-## policy.getNetQuotaPolicies
-
-getNetQuotaPolicies(callback: AsyncCallback\<Array\<NetQuotaPolicy>>): void
-
-获取计量网络策略，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| callback | AsyncCallback\<Array\<[NetQuotaPolicy](#netquotapolicy)>> | 是   | 回调函数，返回获取结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.getNetQuotaPolicies((error, data) => {
-  this.callBack(error, data);
-});
-```
-
-## policy.getNetQuotaPolicies
-
-getNetQuotaPolicies(): Promise\<Array\<NetQuotaPolicy>>;
-
-获取计量网络策略，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<Array\<[NetQuotaPolicy](#netquotapolicy)>> | 以Promise形式返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.getNetQuotaPolicies().then(function (error, data) {
-  console.log(JSON.stringify(error))
-  console.log(JSON.stringify(data))
-})
-
-```
-
-## policy.setNetQuotaPolicies
-
-setNetQuotaPolicies(quotaPolicies: Array\<NetQuotaPolicy>, callback: AsyncCallback\<void>): void
-
-设置计量网络策略，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| quotaPolicies | Array\<[NetQuotaPolicy](#netquotapolicy)> | 是 | 计量网络策略 |
-| callback | AsyncCallback\<void> | 是   | 回调函数，返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  netType: Number.parseInt(this.netType),
-  iccid: this.iccid,
-  ident: this.ident,
-  periodDuration: this.periodDuration,
-  warningBytes: Number.parseInt(this.warningBytes),
-  limitBytes: Number.parseInt(this.limitBytes),
-  lastWarningRemind: this.lastWarningRemind,
-  lastLimitRemind: this.lastLimitRemind,
-  metered: Boolean(Number.parseInt(this.metered)),
-  limitAction: this.limitAction
-};
-this.netQuotaPolicyList.push(param);
-
-policy.setNetQuotaPolicies(this.netQuotaPolicyList, (error) => {
-  console.log(JSON.stringify(error))
-});
-```
-
-## policy.setNetQuotaPolicies
-
-setNetQuotaPolicies(quotaPolicies: Array\<NetQuotaPolicy>): Promise\<void>;
-
-设置计量网络策略，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| quotaPolicies | Array\<[NetQuotaPolicy](#netquotapolicy)> | 是 | 计量网络策略 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<void> | 以Promise形式返回设定结果。 |
-
-**示例：**
-
-```js
-let param = {
-  netType: Number.parseInt(this.netType),
-  iccid: this.iccid,
-  ident: this.ident,
-  periodDuration: this.periodDuration,
-  warningBytes: Number.parseInt(this.warningBytes),
-  limitBytes: Number.parseInt(this.limitBytes),
-  lastWarningRemind: this.lastWarningRemind,
-  lastLimitRemind: this.lastLimitRemind,
-  metered: Boolean(Number.parseInt(this.metered)),
-  limitAction: this.limitAction
-};
-this.netQuotaPolicyList.push(param);
-
-policy.setNetQuotaPolicies(this.netQuotaPolicyList).then(function (error) {
-  console.log(JSON.stringify(error))
-})
-```
-
-## policy.restoreAllPolicies
-
-restoreAllPolicies(iccid: string, callback: AsyncCallback\<void>): void
-
-重置对应sim卡id的蜂窝网络、后台网络策略、防火墙策略、应用对应的策略，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| iccid | string | 是 | SIM卡ID|
-| callback | AsyncCallback\<void> | 是   | 回调函数，返回重置结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-this.firstParam = iccid;
-policy.restoreAllPolicies(this.firstParam, (error) => {
-  console.log(JSON.stringify(error))
-});
-```
-
-## policy.restoreAllPolicies
-
-restoreAllPolicies(iccid: string): Promise\<void>;
-
-重置对应sim卡id的蜂窝网络、后台网络策略、防火墙策略、应用对应的策略，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| iccid | string | 是 | SIM卡ID|
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<void> | 以Promise形式返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-this.firstParam = iccid;
-policy.restoreAllPolicies(this.firstParam).then(function (error) {
-  console.log(JSON.stringify(error))
-})
-
-```
-
-## policy.isUidNetAllowed
-
-isUidNetAllowed(uid: number, isMetered: boolean, callback: AsyncCallback\<boolean>): void
-
-获取对应uid能否访问计量或非计量网络，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-| isMetered | boolean | 是 | 是否为计量网络 |
-| callback | AsyncCallback\<boolean> | 是   | 回调函数，返回true表示这个uid可以访问对应的计量网络。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-
-let param = {
-  uid: Number.parseInt(this.firstParam), isMetered: Boolean(Number.parseInt(this.isBoolean))
-}
-policy.isUidNetAllowed(Number.parseInt(this.firstParam), Boolean(Number.parseInt(this.isBoolean)), (error, data) => {
-  this.callBack(error, data);
-});
-```
-
-## policy.isUidNetAllowed
-
-isUidNetAllowed(uid: number, isMetered: boolean): Promise\<boolean>;
-
-获取对应uid能否访问计量或非计量网络，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-| isMetered | boolean | 是 | 是否为计量网络 |
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<boolean> | 以Promise形式返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  uid: Number.parseInt(this.firstParam), isMetered: Boolean(Number.parseInt(this.isBoolean))
-}
-policy.isUidNetAllowed(Number.parseInt(this.firstParam), Boolean(Number.parseInt(this.isBoolean))).then(function (error, data) {
-  console.log(JSON.stringify(error))
-  console.log(JSON.stringify(data))
-})
-
-```
-
-## policy.isUidNetAllowed
-
-isUidNetAllowed(uid: number, iface: string, callback: AsyncCallback\<boolean>): void
-
-获取对应uid能否访问指定的iface的网络，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-| iface | string | 是 | 网络对应的名称 |
-| callback | AsyncCallback\<boolean> | 是   | 回调函数，返回true表示这个uid可以访问对应iface的网络。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  uid: Number.parseInt(this.firstParam), iface: this.secondParam
-}
-policy.isUidNetAllowed(Number.parseInt(this.firstParam), this.secondParam, (error, data) => {
-  this.callBack(error, data);
-});
-```
-
-## policy.isUidNetAllowed
-
-isUidNetAllowed(uid: number, iface: string): Promise\<boolean>;
-
-获取对应uid能否访问指定的iface的网络，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-| iface | string | 是 | 网络对应的名称 |
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<boolean> | 以Promise形式返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  uid: Number.parseInt(this.firstParam), iface: this.secondParam
-}
-policy.isUidNetAllowed(Number.parseInt(this.firstParam), this.secondParam).then(function (error, data) {
-  console.log(JSON.stringify(error))
-  console.log(JSON.stringify(data))
-})
-```
-
-## policy.setDeviceIdleAllowList
-
-setDeviceIdleAllowList(uid: number, isAllowed: boolean, callback: AsyncCallback\<void>): void
-
-设置指定uid应用是否在休眠防火墙的白名单，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-| isAllowed | boolean | 是 | 是否加入白名单 |
-| callback | callback: AsyncCallback\<void> | 是   | 回调函数，返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  uid: Number.parseInt(this.firstParam), isAllowed: Boolean(Number.parseInt(this.isBoolean))
-}
-policy.setDeviceIdleAllowList(Number.parseInt(this.firstParam), Boolean(Number.parseInt(this.isBoolean)), (error) => {
-  console.log(JSON.stringify(error))
-});
-```
-
-## policy.setDeviceIdleAllowList
-
-setDeviceIdleAllowList(uid: number, isAllowed: boolean): Promise\<void>;
-
-设置指定uid应用是否在休眠防火墙的白名单，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-| isAllowed | boolean | 是 | 是否加入白名单 |
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<void> | 以Promise形式返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  uid: Number.parseInt(this.firstParam), isAllowed: Boolean(Number.parseInt(this.isBoolean))
-}
-policy.setDeviceIdleAllowList(Number.parseInt(this.firstParam), Boolean(Number.parseInt(this.isBoolean))).then(function (error) {
-  console.log(JSON.stringify(error))
-})
-
-```
-
-## policy.getDeviceIdleAllowList
-
-getDeviceIdleAllowList(callback: AsyncCallback\<Array\<number>>): void
-
-获取休眠模式白名单所包含的uid数组，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| callback | AsyncCallback\<Array\<number>> | 是   | 回调函数，返回获取结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.getDeviceIdleAllowList((error, data) => {
-  this.callBack(error, data);
-});
-```
-
-## policy.getDeviceIdleAllowList
-
-getDeviceIdleAllowList(): Promise\<Array\<number>>;
-
-获取休眠模式白名单所包含的uid数组，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<Array\<number>> | 以Promise形式返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.getDeviceIdleAllowList().then(function (error, data) {
-  console.log(JSON.stringify(error))
-  console.log(JSON.stringify(data))
-})
-```
-
-## policy.getBackgroundPolicyByUid
-
-getBackgroundPolicyByUid(uid: number, callback: AsyncCallback\<NetBackgroundPolicy>): void
-
-获取指定uid能否访问后台网络，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-| callback | AsyncCallback\<[NetBackgroundPolicy](#netbackgroundpolicy)> | 是   | 回调函数，返回获取结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-this.firstParam = uid
-policy.getBackgroundPolicyByUid(Number.parseInt(this.firstParam), (error, data) => {
-  this.callBack(error, data);
-});
-```
-
-## policy.getBackgroundPolicyByUid
-
-getBackgroundPolicyByUid(uid: number): Promise\<NetBackgroundPolicy>;
-
-获取指定uid能否访问后台网络，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<[NetBackgroundPolicy](#netbackgroundpolicy)> | 以Promise形式返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-this.firstParam = uid
-policy.getBackgroundPolicyByUid(Number.parseInt(this.firstParam)).then(function (error, data) {
-  console.log(JSON.stringify(error))
-  console.log(JSON.stringify(data))
-})
-```
-
-## policy.resetPolicies
-
-resetPolicies(iccid: string, callback: AsyncCallback\<void>): void
-
-重置对应sim卡id的蜂窝网络、后台网络策略、防火墙策略、应用对应的策略，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| iccid | string | 是 | SIM卡ID|
-| callback | AsyncCallback\<void> | 是   | 回调函数，返回重置结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-this.firstParam = iccid
-policy.resetPolicies(this.firstParam, (error) => {
-  console.log(JSON.stringify(error))
-});
-```
-
-## policy.resetPolicies
-
-resetPolicies(iccid: string): Promise\<void>;
-
-重置对应sim卡id的蜂窝网络、后台网络策略、防火墙策略、应用对应的策略，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| iccid | string | 是 | SIM卡ID|
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<void> | 以Promise形式返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.getUidsByPolicy(Number.parseInt(this.firstParam)).then(function (error, data) {
-
-})
-this.firstParam = iccid
-policy.resetPolicies(this.firstParam).then(function (error) {
-  console.log(JSON.stringify(error))
-})
-
-```
-
-## policy.updateRemindPolicy
-
-updateRemindPolicy(netType: NetBearType, iccid: string, remindType: RemindType, callback: AsyncCallback\<void>): void
-
-更新提醒策略，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| netType | [NetBearType](js-apis-net-connection.md#netbeartype) | 是 | 网络类型 |
-| iccid | string | 是 | SIM卡ID|
-| remindType | [RemindType](#remindtype) | 是 | 提醒类型 |
-| callback | AsyncCallback\<void> | 是   | 回调函数，返回更新结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  netType: Number.parseInt(this.netType), iccid: this.firstParam, remindType: this.currentRemindType
-}
-policy.updateRemindPolicy(Number.parseInt(this.netType), this.firstParam, Number.parseInt(this.currentRemindType), (error, data) => {
-  this.callBack(error, data);
-});
-```
-
-## policy.updateRemindPolicy
-
-updateRemindPolicy(netType: NetBearType, iccid: string, remindType: RemindType): Promise\<void>;
-
-更新提醒策略，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| netType | [NetBearType](js-apis-net-connection.md#netbeartype) | 是 | 网络类型 |
-| iccid | string | 是 | SIM卡ID|
-| remindType | [RemindType](#remindtype) | 是 | 提醒类型 |
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<void> | 以Promise形式返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  netType: Number.parseInt(this.netType), iccid: this.firstParam, remindType: this.currentRemindType
-}
-policy.updateRemindPolicy(Number.parseInt(this.netType), this.firstParam, Number.parseInt(this.currentRemindType)).then(function (error, data) {
-  console.log(JSON.stringify(error))
-  console.log(JSON.stringify(data))
-})
-
-```
-
-## policy.setPowerSaveAllowList
-
-setPowerSaveAllowList(uid: number, isAllowed: boolean, callback: AsyncCallback\<void>): void
-
-设置指定uid应用是否在省电防火墙的白名单，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-| isAllowed | boolean | 是 | 是否加入白名单 |
-| callback | callback: AsyncCallback\<void> | 是   | 回调函数，返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  uid: Number.parseInt(this.firstParam), isAllowed: Boolean(Number.parseInt(this.isBoolean))
-}
-policy.setPowerSaveAllowList(Number.parseInt(this.firstParam), Boolean(Number.parseInt(this.isBoolean)), (error) => {
-  console.log(JSON.stringify(error))
-});
-```
-
-## policy.setPowerSaveAllowList
-
-setPowerSaveAllowList(uid: number, isAllowed: boolean): Promise\<void>;
-
-设置指定uid应用是否在省电防火墙的白名单，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| uid | number | 是 | app唯一标识符 |
-| isAllowed | boolean | 是 | 是否加入白名单 |
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<void> | 以Promise形式返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 401     | Parameter error.                             |
-| 2100001 | Invalid parameter value.                |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-let param = {
-  uid: Number.parseInt(this.firstParam), isAllowed: Boolean(Number.parseInt(this.isBoolean))
-}
-policy.setPowerSaveAllowList(Number.parseInt(this.firstParam), Boolean(Number.parseInt(this.isBoolean))).then(function (error) {
-  console.log(JSON.stringify(error))
-})
-
-```
-
-## policy.getPowerSaveAllowList
-
-getPowerSaveAllowList(callback: AsyncCallback\<Array\<number>>): void
-
-获取省电模式白名单所包含的uid数组，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                                    | 必填 | 说明       |
-| -------- | --------------------------------------- | ---- | ---------- |
-| callback | AsyncCallback\<Array\<number>> | 是   | 回调函数，返回获取结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.getPowerSaveAllowList((error, data) => {
-  this.callBack(error, data);
-});
-```
-
-## policy.getPowerSaveAllowList
-
-getPowerSaveAllowList(): Promise\<Array\<number>>;
-
-获取休眠模式白名单所包含的uid数组，使用Promise方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**返回值：**
-
-| 类型                              | 说明                                  |
-| --------------------------------- | ------------------------------------- |
-| Promise\<Array\<number>> | 以Promise形式返回设定结果。 |
-
-**错误码：**
-
-| 错误码ID | 错误信息                                      |
-| ------- | -------------------------------------------- |
-| 201     | Permission denied.                           |
-| 2100002 | Operation failed. Cannot connect to service.|
-| 2100003 | System internal error.                  |
-
-**示例：**
-
-```js
-policy.getPowerSaveAllowList().then(function (error, data) {
-  console.log(JSON.stringify(error))
-  console.log(JSON.stringify(data))
-})
-```
-
-## policy.on
-
-网络策略的句柄。
-
-### on('netUidPolicyChange')
-
-on(type: "netUidPolicyChange", callback: Callback\<{ uid: number, policy: NetUidPolicy }>): void
-
-注册policy发生改变时的回调，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                               | 必填 | 说明                                                         |
-| -------- | ---------------------------------- | ---- | ------------------------------------------------------------ |
-| type | netUidPolicyChange | 是 | policy发生改变的类型 |
-| callback | Callback\<{ uid: number, policy: [NetUidPolicy](#netuidpolicy) }> | 是   | 回调函数。注册policy发生改变时调用。 |
-
-**示例：**
-
-```js
-policy.on('netUidPolicyChange', (data) => {
-  this.log('on netUidPolicyChange: ' + JSON.stringify(data));
-})
-```
-
-### on('netUidRuleChange')
-
-on(type: "netUidRuleChange", callback: Callback\<{ uid: number, rule: NetUidRule }>): void
-
-注册rule发生改变时的回调，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                               | 必填 | 说明                                                         |
-| -------- | ---------------------------------- | ---- | ------------------------------------------------------------ |
-| type | netUidRuleChange | 是 | rule发生改变的类型 |
-| callback | Callback\<{ uid: number, rule: [NetUidRule](#netuidrule) }> | 是   | 回调函数。注册rule发生改变时的调用。 |
-
-**示例：**
-
-```js
-policy.on('netUidRuleChange', (data) => {
-  this.log('on netUidRuleChange: ' + JSON.stringify(data));
-})
-```
-
-### on('netMeteredIfacesChange')
-
-on(type: "netMeteredIfacesChange", callback: Callback\<Array\<string>>): void
-
-注册计量iface发生改变时的回调，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                               | 必填 | 说明                                                         |
-| -------- | ---------------------------------- | ---- | ------------------------------------------------------------ |
-| type | netMeteredIfacesChange | 是 | 计量iface发生改变的类型 |
-| callback | Callback\<Array\<string>> | 是   | 回调函数。注册计量iface发生改变时调用。 |
-
-**示例：**
-
-```js
-policy.on('netMeteredIfacesChange', (data) => {
-  this.log('on netMeteredIfacesChange: ' + JSON.stringify(data));
-})
-```
-
-### on('netQuotaPolicyChange')
-
-on(type: "netQuotaPolicyChange", callback: Callback\<Array\<NetQuotaPolicy>>): void
-
-注册计量网络策略发生改变时的回调，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                               | 必填 | 说明                                                         |
-| -------- | ---------------------------------- | ---- | ------------------------------------------------------------ |
-| type | netQuotaPolicyChange | 是 | 计量网络策略发生改变的类型 |
-| callback | Callback\<Array\<[NetQuotaPolicy](#netquotapolicy)>> | 是   | 回调函数。注册计量网络策略发生改变时调用。 |
-
-**示例：**
-
-```js
-policy.on('netQuotaPolicyChange', (data) => {
-  this.log('on netQuotaPolicyChange: ' + JSON.stringify(data));
-})
-```
-
-### on('netBackgroundPolicyChange')
-
-on(type: "netBackgroundPolicyChange", callback: Callback\<boolean>): void
-
-注册后台网络策略发生改变时的回调，使用callback方式作为异步方法。
-
-**需要权限**：ohos.permission.CONNECTIVITY_INTERNAL
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-**参数：**
-
-| 参数名   | 类型                               | 必填 | 说明                                                         |
-| -------- | ---------------------------------- | ---- | ------------------------------------------------------------ |
-| type | netBackgroundPolicyChange | 是 | 后台网络策略发生改变的类型 |
-| callback | Callback\<boolean> | 是   | 回调函数。注册后台网络策略发生改变时调用。 |
-
-**示例：**
-
-```js
-policy.on('netBackgroundPolicyChange', (data) => {
-  this.log('on netBackgroundPolicyChange: ' + JSON.stringify(data));
-})
-```
-
-## NetBackgroundPolicy
-
-后台网络策略。
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-| 参数名                  | 值   | 说明                   |
-| ------------------------ | ---- | ---------------------- |
-| NET_BACKGROUND_POLICY_NONE       | 0 | 默认值。 |
-| NET_BACKGROUND_POLICY_ENABLE     | 1 | 应用在后台可以使用计量网路。 |
-| NET_BACKGROUND_POLICY_DISABLE    | 2 | 应用在后台不可以使用计量网路。 |
-| NET_BACKGROUND_POLICY_ALLOW_LIST | 3 | 只有应用指定的列表在后台可以使用计量网络。 |
-
-## NetQuotaPolicy
-
-计量网络策略。
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-| 参数名                  | 类型                                | 说明                                                         |
-| ----------------------- | ----------------------------------- | ------------------------------------------------------------ |
-| netType           | [NetBearType](js-apis-net-connection.md#netbeartype) | 网络类型。 |
-| iccid             | string                      | 计量蜂窝网络的SIM卡的标识值。以太网，wifi网络不会用到 |
-| ident             | string                      | 计量蜂窝网络中配合iccid联合使用。以太网，wifi网络单独使用。用于标记类型。 |
-| periodDuration    | string                      | 计量开始时间。 |
-| warningBytes      | number                      | 发出警告的流量阈值。 |
-| limitBytes        | number                      | 流量设置的配额。 |
-| lastWarningRemind | string                      | 最新一次发出警告的时间。 |
-| lastLimitRemind   | string                      | 最新一次配额耗尽的时间。 |
-| metered           | string                      | 是否为计量网络。 |
-| limitAction       | [LimitAction](#limitaction) | 到达流量限制后的动作。 |
-
-## LimitAction
-
-限制动作。
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-| 参数名                  | 值 | 说明   |
-| ---------------------- | ----- | ------------ |
-| LIMIT_ACTION_NONE     | -1 | 默认值。 |
-| LIMIT_ACTION_DISABLE  | 0  | 当配额策略达到限制时，访问被禁用。 |
-| LIMIT_ACTION_AUTO_BILL| 1  | 当配额策略达到限制时，用户将自动计费。 |
-
-## NetUidRule
-
-计量网络规则。
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-| 参数名                  | 值 | 说明   |
-| ---------------------- | ----- | ------------ |
-| NET_RULE_NONE                     | 0 | 默认规则 |
-| NET_RULE_ALLOW_METERED_FOREGROUND | 1 | 允许前台访问计量网络 |
-| NET_RULE_ALLOW_METERED            | 2 | 允许访问计量网络 |
-| NET_RULE_REJECT_METERED           | 4 | 拒绝访问计量网络 |
-| NET_RULE_ALLOW_ALL                | 32 | 允许访问所有网络 |
-| NET_RULE_REJECT_ALL               | 64 | 拒绝访问所有网络 |
-
-## RemindType
-
-提醒类型。
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-| 参数名                  | 值 | 说明   |
-| ---------------------- | - | ------- |
-| REMIND_TYPE_WARNING    | 1 | 警告提醒 |
-| REMIND_TYPE_LIMIT      | 2 | 限制提醒 |
-
-## NetUidPolicy
-
-应用对应的网络策略。
-
-**系统能力**：SystemCapability.Communication.NetManager.Core
-
-| 参数名                  | 值 | 说明   |
-| ---------------------- | ----- | ------------ |
-| NET_POLICY_NONE                       | 0 | 默认网络策略 |
-| NET_POLICY_ALLOW_METERED_BACKGROUND   | 1 | 允许应用在后台访问计量网络 |
-| NET_POLICY_REJECT_METERED_BACKGROUND  | 2 | 拒绝应用在后台访问计量网络 |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-notification.md b/zh-cn/application-dev/reference/apis/js-apis-notification.md
index 57caa47b96bafb866f96a4a00a5571fd713d0c50..35676d2514c38ff2d673e9f555a7fdb94c613c17 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-notification.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-notification.md
@@ -588,7 +588,7 @@ Notification.getSlot(slotType).then((data) => {
 
 ## Notification.getSlots
 
-getSlots(callback: AsyncCallback<Array\<NotificationSlot\>>): void
+getSlots(callback: AsyncCallback\<Array\<NotificationSlot>>): void
 
 获取此应用程序的所有通知通道（callback形式）。
 
@@ -598,7 +598,7 @@ getSlots(callback: AsyncCallback<Array\<NotificationSlot\>>): void
 
 | 参数名     | 类型                              | 必填 | 说明                 |
 | -------- | --------------------------------- | ---- | -------------------- |
-| callback | AsyncCallback\<Array\<[NotificationSlot](#notificationslot)\>\> | 是   | 以callback形式返回获取此应用程序的所有通知通道的结果。 |
+| callback | AsyncCallback\<Array\<[NotificationSlot](#notificationslot)>> | 是   | 以callback形式返回获取此应用程序的所有通知通道的结果。 |
 
 **示例：**
 
@@ -1372,7 +1372,7 @@ Notification.setSlotByBundle(bundle, notificationSlot).then(() => {
 
 ## Notification.getSlotsByBundle
 
-getSlotsByBundle(bundle: BundleOption, callback: AsyncCallback<Array\<NotificationSlot\>>): void
+getSlotsByBundle(bundle: BundleOption, callback: AsyncCallback\<Array\<NotificationSlot>>): void
 
 获取指定应用的所有通知通道（Callback形式）。
 
@@ -1387,7 +1387,7 @@ getSlotsByBundle(bundle: BundleOption, callback: AsyncCallback<Array\<Notificati
 | 参数名     | 类型                                     | 必填 | 说明                 |
 | -------- | ---------------------------------------- | ---- | -------------------- |
 | bundle   | [BundleOption](#bundleoption)                             | 是   | 指定应用的包信息。           |
-| callback | AsyncCallback<Array\<[NotificationSlot](#notificationslot)\>> | 是   | 获取通知通道回调函数。 |
+| callback | AsyncCallback\<Array\<[NotificationSlot](#notificationslot)>> | 是   | 获取通知通道回调函数。 |
 
 **示例：**
 
@@ -1409,7 +1409,7 @@ Notification.getSlotsByBundle(bundle, getSlotsByBundleCallback);
 
 ## Notification.getSlotsByBundle
 
-getSlotsByBundle(bundle: BundleOption): Promise<Array\<NotificationSlot\>>
+getSlotsByBundle(bundle: BundleOption): Promise\<Array\<NotificationSlot>>
 
 获取指定应用的所有通知通道（Promise形式）。
 
@@ -1429,7 +1429,7 @@ getSlotsByBundle(bundle: BundleOption): Promise<Array\<NotificationSlot\>>
 
 | 类型                                                        | 说明                                                         |
 | ----------------------------------------------------------- | ------------------------------------------------------------ |
-| Promise<Array\<[NotificationSlot](#notificationslot)\>> | 以Promise形式返回获取指定应用的通知通道。 |
+| Promise\<Array\<[NotificationSlot](#notificationslot)>> | 以Promise形式返回获取指定应用的通知通道。 |
 
 **示例：**
 
@@ -1831,7 +1831,7 @@ Notification.removeAll(userId).then(() => {
 
 ## Notification.getAllActiveNotifications
 
-getAllActiveNotifications(callback: AsyncCallback<Array\<NotificationRequest\>>): void
+getAllActiveNotifications(callback: AsyncCallback\<Array\<NotificationRequest>>): void
 
 获取当前未删除的所有通知（Callback形式）。
 
@@ -1845,7 +1845,7 @@ getAllActiveNotifications(callback: AsyncCallback<Array\<NotificationRequest\>>)
 
 | 参数名     | 类型                                                         | 必填 | 说明                 |
 | -------- | ------------------------------------------------------------ | ---- | -------------------- |
-| callback | AsyncCallback<Array\<[NotificationRequest](#notificationrequest)\>> | 是   | 获取活动通知回调函数。 |
+| callback | AsyncCallback\<Array\<[NotificationRequest](#notificationrequest)>> | 是   | 获取活动通知回调函数。 |
 
 **示例：**
 
@@ -1865,7 +1865,7 @@ Notification.getAllActiveNotifications(getAllActiveNotificationsCallback);
 
 ## Notification.getAllActiveNotifications
 
-getAllActiveNotifications(): Promise\<Array\<[NotificationRequest](#notificationrequest)\>\>
+getAllActiveNotifications(): Promise\<Array\<[NotificationRequest](#notificationrequest)>>
 
 获取当前未删除的所有通知（Promise形式）。
 
@@ -1879,7 +1879,7 @@ getAllActiveNotifications(): Promise\<Array\<[NotificationRequest](#notification
 
 | 类型                                                        | 说明                                                         |
 | ----------------------------------------------------------- | ------------------------------------------------------------ |
-| Promise\<Array\<[NotificationRequest](#notificationrequest)\>\> | 以Promise形式返回获取活动通知。 |
+| Promise\<Array\<[NotificationRequest](#notificationrequest)>> | 以Promise形式返回获取活动通知。 |
 
 **示例：**
 
@@ -2913,476 +2913,6 @@ Notification.getDeviceRemindType().then((data) => {
 });
 ```
 
-
-## Notification.publishAsBundle<sup>9+</sup>
-
-publishAsBundle(request: NotificationRequest, representativeBundle: string, userId: number, callback: AsyncCallback\<void\>): void
-
-发布代理通知（callback形式）。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**需要权限**: ohos.permission.NOTIFICATION_CONTROLLER，ohos.permission.NOTIFICATION_AGENT_CONTROLLER
-
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
-**参数：**
-
-| 参数名               | 类型                                        | 必填 | 说明                                     |
-| -------------------- | ------------------------------------------- | ---- | ---------------------------------------- |
-| request              | [NotificationRequest](#notificationrequest) | 是   | 用于设置要发布通知的内容和相关配置信息。 |
-| representativeBundle | string                                      | 是   | 被代理应用的包名。                       |
-| userId               | number                                      | 是   | 用户ID。                                 |
-| callback             | AsyncCallback                               | 是   | 发布代理通知的回调方法。                 |
-
-**示例：**
-
-```js
-// publishAsBundle回调
-function callback(err) {
-    if (err.code) {
-        console.info("publishAsBundle failed " + JSON.stringify(err));
-    } else {
-        console.info("publishAsBundle success");
-    }
-}
-// 被代理应用的包名
-let representativeBundle = "com.example.demo";
-// 用户ID
-let userId = 100;
-// NotificationRequest对象
-let request = {
-    id: 1,
-    content: {
-        contentType: Notification.ContentType.NOTIFICATION_CONTENT_BASIC_TEXT,
-        normal: {
-            title: "test_title",
-            text: "test_text",
-            additionalText: "test_additionalText"
-        }
-    }
-};
-
-Notification.publishAsBundle(request, representativeBundle, userId, callback);
-```
-
-## Notification.publishAsBundle<sup>9+</sup>
-
-publishAsBundle(request: NotificationRequest, representativeBundle: string, userId: number): Promise\<void\>
-
-发布代理通知（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**需要权限**: ohos.permission.NOTIFICATION_CONTROLLER，ohos.permission.NOTIFICATION_AGENT_CONTROLLER
-
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
-**参数：**
-
-
-| 参数名               | 类型                                        | 必填 | 说明                                          |
-| -------------------- | ------------------------------------------- | ---- | --------------------------------------------- |
-| request              | [NotificationRequest](#notificationrequest) | 是   | 用于设置要发布通知的内容和相关配置信息。 |
-| representativeBundle | string                                      | 是   | 被代理应用的包名。                            |
-| userId               | number                                      | 是   | 用户ID。                            |
-
-**示例：**
-
-```js
-// 被代理应用的包名
-let representativeBundle = "com.example.demo";
-// 用户ID
-let userId = 100;
-// NotificationRequest对象
-let request = {
-    id: 1,
-    content: {
-        contentType: Notification.ContentType.NOTIFICATION_CONTENT_BASIC_TEXT,
-        normal: {
-            title: "test_title",
-            text: "test_text",
-            additionalText: "test_additionalText"
-        }
-    }
-};
-
-Notification.publishAsBundle(request, representativeBundle, userId).then(() => {
-	console.info("publishAsBundle success");
-});
-```
-
-## Notification.cancelAsBundle<sup>9+</sup>
-
-cancelAsBundle(id: number, representativeBundle: string, userId: number, callback: AsyncCallback\<void\>): void
-
-取消代理通知（callback形式）。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**：此接口为系统接口，三方应用不支持调用。
-
-**需要权限**: ohos.permission.NOTIFICATION_CONTROLLER，ohos.permission.NOTIFICATION_AGENT_CONTROLLER
-
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
-**参数：**
-
-| 参数名               | 类型          | 必填 | 说明                     |
-| -------------------- | ------------- | ---- | ------------------------ |
-| id                   | number        | 是   | 通知ID。                 |
-| representativeBundle | string        | 是   | 被代理应用的包名。       |
-| userId               | number        | 是   | 用户ID。       |
-| callback             | AsyncCallback | 是   | 取消代理通知的回调方法。 |
-
-**示例：**
-
-```js
-// cancelAsBundle
-function cancelAsBundleCallback(err) {
-    if (err.code) {
-        console.info("cancelAsBundle failed " + JSON.stringify(err));
-    } else {
-        console.info("cancelAsBundle success");
-    }
-}
-// 被代理应用的包名
-let representativeBundle = "com.example.demo";
-// 用户ID
-let userId = 100;
-
-Notification.cancelAsBundle(0, representativeBundle, userId, cancelAsBundleCallback);
-```
-
-## Notification.cancelAsBundle<sup>9+</sup>
-
-cancelAsBundle(id: number, representativeBundle: string, userId: number): Promise\<void\>
-
-取消代理通知（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**：此接口为系统接口，三方应用不支持调用。
-
-**需要权限**: ohos.permission.NOTIFICATION_CONTROLLER，ohos.permission.NOTIFICATION_AGENT_CONTROLLER
-
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
-**参数：**
-
-| 参数名               | 类型   | 必填 | 说明               |
-| -------------------- | ------ | ---- | ------------------ |
-| id                   | number | 是   | 通知ID。           |
-| representativeBundle | string | 是   | 被代理应用的包名。 |
-| userId               | number | 是   | 用户ID。 |
-
-**示例：**
-
-```js
-// 被代理应用的包名
-let representativeBundle = "com.example.demo";
-// 用户ID
-let userId = 100;
-
-Notification.cancelAsBundle(0, representativeBundle, userId).then(() => {
-	console.info("cancelAsBundle success");
-});
-```
-
-## Notification.enableNotificationSlot <sup>9+</sup>
-
-enableNotificationSlot(bundle: BundleOption, type: SlotType, enable: boolean, callback: AsyncCallback\<void>): void
-
-设置指定应用的指定渠道类型的使能状态（Callback形式）。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**：此接口为系统接口，三方应用不支持调用。
-
-**需要权限**：ohos.permission.NOTIFICATION_CONTROLLER
-
-**参数：**
-
-| 参数名   | 类型                          | 必填 | 说明                   |
-| -------- | ----------------------------- | ---- | ---------------------- |
-| bundle   | [BundleOption](#bundleoption) | 是   | 应用的包信息。           |
-| type     | [SlotType](#slottype)         | 是   | 指定渠道类型。         |
-| enable   | boolean                       | 是   | 使能状态。             |
-| callback | AsyncCallback\<void\>         | 是   | 设置渠道使能回调函数。 |
-
-**示例：**
-
-```js
-// enableNotificationSlot
-function enableSlotCallback(err) {
-    if (err.code) {
-        console.info("enableNotificationSlot failed " + JSON.stringify(err));
-    } else {
-        console.info("enableNotificationSlot success");
-    }
-};
-
-Notification.enableNotificationSlot(
-    { bundle: "ohos.samples.notification", },
-    Notification.SlotType.SOCIAL_COMMUNICATION,
-    true,
-    enableSlotCallback);
-```
-
-## Notification.enableNotificationSlot <sup>9+</sup>
-
-enableNotificationSlot(bundle: BundleOption, type: SlotType, enable: boolean): Promise\<void> 
-
-设置指定应用的指定渠道类型的使能状态（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**：此接口为系统接口，三方应用不支持调用。
-
-**需要权限**：ohos.permission.NOTIFICATION_CONTROLLER
-
-**参数：**
-
-| 参数名 | 类型                          | 必填 | 说明           |
-| ------ | ----------------------------- | ---- | -------------- |
-| bundle | [BundleOption](#bundleoption) | 是   | 应用的包信息。   |
-| type   | [SlotType](#slottype)         | 是   | 渠道类型。 |
-| enable | boolean                       | 是   | 使能状态。     |
-
-**示例：**
-
-```js
-// enableNotificationSlot
-Notification.enableNotificationSlot({ bundle: "ohos.samples.notification", },
-    Notification.SlotType.SOCIAL_COMMUNICATION,true).then(() => {
-    console.info("enableNotificationSlot success");
-});
-```
-
-## Notification.isNotificationSlotEnabled <sup>9+</sup>
-
-isNotificationSlotEnabled(bundle: BundleOption, type: SlotType, callback: AsyncCallback\<boolean\>): void
-
-获取指定应用的指定渠道类型的使能状态（Callback形式）。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**：此接口为系统接口，三方应用不支持调用。
-
-**需要权限**：ohos.permission.NOTIFICATION_CONTROLLER
-
-**参数：**
-
-| 参数名   | 类型                          | 必填 | 说明                   |
-| -------- | ----------------------------- | ---- | ---------------------- |
-| bundle   | [BundleOption](#bundleoption) | 是   | 应用的包信息。           |
-| type     | [SlotType](#slottype)         | 是   | 渠道类型。         |
-| callback | AsyncCallback\<boolean\>         | 是   | 获取渠道使能状态回调函数。 |
-
-**示例：**
-
-```js
-// isNotificationSlotEnabled
-function getEnableSlotCallback(err, data) {
-    if (err.code) {
-        console.info("isNotificationSlotEnabled failed " + JSON.stringify(err));
-    } else {
-        console.info("isNotificationSlotEnabled success");
-    }
-};
-
-Notification.isNotificationSlotEnabled(
-    { bundle: "ohos.samples.notification", },
-    Notification.SlotType.SOCIAL_COMMUNICATION,
-    getEnableSlotCallback);
-```
-
-## Notification.isNotificationSlotEnabled <sup>9+</sup>
-
-isNotificationSlotEnabled(bundle: BundleOption, type: SlotType): Promise\<boolean\>  
-
-获取指定应用的指定渠道类型的使能状态（Promise形式）。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**：此接口为系统接口，三方应用不支持调用。
-
-**需要权限**：ohos.permission.NOTIFICATION_CONTROLLER
-
-**参数：**
-
-| 参数名 | 类型                          | 必填 | 说明           |
-| ------ | ----------------------------- | ---- | -------------- |
-| bundle | [BundleOption](#bundleoption) | 是   | 应用的包信息。   |
-| type   | [SlotType](#slottype)         | 是   | 渠道类型。 |
-
-**返回值：**
-
-| 类型               | 说明                            |
-| ------------------ | ------------------------------- |
-| Promise\<boolean\> | 以Promise形式返回渠道使能状态。 |
-
-**示例：**
-
-```js
-// isNotificationSlotEnabled
-Notification.isNotificationSlotEnabled({ bundle: "ohos.samples.notification", },
-    Notification.SlotType.SOCIAL_COMMUNICATION).then((data) => {
-    console.info("isNotificationSlotEnabled success, data: " + JSON.stringify(data));
-});
-```
-
-
-## Notification.setSyncNotificationEnabledWithoutApp<sup>9+</sup>
-
-setSyncNotificationEnabledWithoutApp(userId: number, enable: boolean, callback: AsyncCallback\<void\>): void
-
-设置是否将通知同步到未安装应用程序的设备(callback形式)。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**：此接口为系统接口，三方应用不支持调用。
-
-**需要权限**：ohos.permission.NOTIFICATION_CONTROLLER
-
-**参数：** 
-
-| 参数名 | 类型                          | 必填 | 说明           |
-| ------ | ----------------------------- | ---- | -------------- |
-| userId | number | 是   | 用户ID。   |
-| enable | boolean | 是   | 是否启用。   |
-| callback | AsyncCallback\<void\>    | 是   | 设置是否将通知同步到未安装应用程序的设备的回调函数。 |
-
-**示例：**
-
-```js
-let userId = 100;
-let enable = true;
-
-function callback(err) {
-    if (err.code) {
-        console.info("setSyncNotificationEnabledWithoutApp failed " + JSON.stringify(err));
-    } else {
-        console.info("setSyncNotificationEnabledWithoutApp success");
-    }
-}
-
-Notification.setSyncNotificationEnabledWithoutApp(userId, enable, callback);
-```
-
-
-## Notification.setSyncNotificationEnabledWithoutApp<sup>9+</sup>
-
-setSyncNotificationEnabledWithoutApp(userId: number, enable: boolean): Promise\<void>
-
-设置是否将通知同步到未安装应用程序的设备(Promise形式)。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**：此接口为系统接口，三方应用不支持调用。
-
-**需要权限**：ohos.permission.NOTIFICATION_CONTROLLER
-
-**参数：**
-
-| 参数名 | 类型                          | 必填 | 说明           |
-| ------ | ----------------------------- | ---- | -------------- |
-| userId | number | 是   | 用户ID。   |
-| enable | boolean | 是   | 是否启用。   |
-
-**返回值：**
-
-| 类型                                                        | 说明                                                         |
-| ----------------------------------------------------------- | ------------------------------------------------------------ |
-| Promise\<void\> | 以Promise形式返回设置是否将通知同步到未安装应用程序的设备的结果。 |
-
-**示例：**
-
-```js
-let userId = 100;
-let enable = true;
-
-Notification.setSyncNotificationEnabledWithoutApp(userId, enable).then(() => {
-    console.info('setSyncNotificationEnabledWithoutApp success');
-}).catch((err) => {
-    console.info('setSyncNotificationEnabledWithoutApp, err:' + JSON.stringify(err));
-});
-```
-
-
-## Notification.getSyncNotificationEnabledWithoutApp<sup>9+</sup>
-
-getSyncNotificationEnabledWithoutApp(userId: number, callback: AsyncCallback\<boolean>): void
-
-获取同步通知到未安装应用程序设备的开关是否开启(callback形式)。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**：此接口为系统接口，三方应用不支持调用。
-
-**需要权限**：ohos.permission.NOTIFICATION_CONTROLLER
-
-**参数：**
-
-| 参数名 | 类型                          | 必填 | 说明           |
-| ------ | ----------------------------- | ---- | -------------- |
-| userId | number | 是   | 用户ID。   |
-| callback | AsyncCallback\<boolean\>         | 是   | 获取同步通知到未安装应用程序设备的开关是否开启的回调函数。 |
-
-**示例：**
-
-```js
-let userId = 100;
-
-function getSyncNotificationEnabledWithoutAppCallback(err, data) {
-    if (err) {
-        console.info('getSyncNotificationEnabledWithoutAppCallback, err:' + err);
-    } else {
-        console.info('getSyncNotificationEnabledWithoutAppCallback, data:' + data);
-    }
-}
-
-Notification.getSyncNotificationEnabledWithoutApp(userId, getSyncNotificationEnabledWithoutAppCallback);
-```
-
-
-## Notification.getSyncNotificationEnabledWithoutApp<sup>9+</sup>
-
-getSyncNotificationEnabledWithoutApp(userId: number): Promise\<boolean>
-
-获取同步通知到未安装应用程序设备的开关是否开启(Promise形式)。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**：此接口为系统接口，三方应用不支持调用。
-
-**需要权限**：ohos.permission.NOTIFICATION_CONTROLLER
-
-**参数：**
-
-| 参数名 | 类型                          | 必填 | 说明           |
-| ------ | ----------------------------- | ---- | -------------- |
-| userId | number | 是   | 用户ID。   |
-
-**返回值：**
-
-| 类型               | 说明                                                         |
-| ------------------ | ------------------------------------------------------------ |
-| Promise\<boolean\> | 以Promise形式返回获取同步通知到未安装应用程序设备的开关是否开启的结果。 |
-
-**示例：**
-
-```js
-let userId = 100;
-Notification.getSyncNotificationEnabledWithoutApp(userId).then((data) => {
-    console.info('getSyncNotificationEnabledWithoutApp, data:' + data);
-}).catch((err) => {
-    console.info('getSyncNotificationEnabledWithoutApp, err:' + err);
-});
-```
-
-
-
 ## NotificationSubscriber
 
 作为订阅通知接口[subscribe](#notificationsubscribe)的入参，提供订阅者接收到新通知、取消通知等的回调方法。
@@ -4121,5 +3651,5 @@ Notification.enableNotification(bundle, false).then(() => {
 
 | 名称                 | 值  | 说明                  |
 | -------------------- | --- | -------------------- |
-| CLICK_REASON_REMOVE  | 1   | 点击通知后删除通知。    |
-| CANCEL_REASON_REMOVE | 2   | 用户删除通知。         |
\ No newline at end of file
+| CLICK_REASON_REMOVE<sup>9+</sup>  | 1   | 点击通知后删除通知。    |
+| CANCEL_REASON_REMOVE<sup>9+</sup> | 2   | 用户删除通知。         |
\ No newline at end of file
diff --git a/zh-cn/application-dev/reference/apis/js-apis-notificationManager.md b/zh-cn/application-dev/reference/apis/js-apis-notificationManager.md
index b1f981dbbae7a5bc14c68844af517e88375ef05d..0c9c3fd3449b3ffdc2d3a26f534e73a4f689a606 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-notificationManager.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-notificationManager.md
@@ -33,7 +33,6 @@ publish(request: NotificationRequest, callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                                  |
 | -------- | ----------------------------------------- |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -89,8 +88,6 @@ publish(request: NotificationRequest): Promise\<void\>
 
 | 错误码ID | 错误信息                                  |
 | -------- | ----------------------------------------- |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -145,8 +142,6 @@ publish(request: NotificationRequest, userId: number, callback: AsyncCallback\<v
 
 | 错误码ID | 错误信息                                  |
 | -------- | ----------------------------------------- |
-| 202      | Not system application to call the interface.   |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -208,8 +203,6 @@ publish(request: NotificationRequest, userId: number): Promise\<void\>
 
 | 错误码ID | 错误信息                                  |
 | -------- | ----------------------------------------- |
-| 201      | Permission denied.                        |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -263,7 +256,6 @@ cancel(id: number, label: string, callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -306,7 +298,6 @@ cancel(id: number, label?: string): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -343,7 +334,6 @@ cancel(id: number, callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -379,7 +369,6 @@ cancelAll(callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -420,7 +409,6 @@ cancelAll(): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -460,9 +448,6 @@ addSlot(slot: NotificationSlot, callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -511,9 +496,6 @@ addSlot(slot: NotificationSlot): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -553,7 +535,6 @@ addSlot(type: SlotType, callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -594,7 +575,6 @@ addSlot(type: SlotType): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -634,9 +614,6 @@ addSlots(slots: Array\<NotificationSlot\>, callback: AsyncCallback\<void\>): voi
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -689,9 +666,6 @@ addSlots(slots: Array\<NotificationSlot\>): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -735,7 +709,6 @@ getSlot(slotType: SlotType, callback: AsyncCallback\<NotificationSlot\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -783,7 +756,6 @@ getSlot(slotType: SlotType): Promise\<NotificationSlot\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -801,7 +773,7 @@ Notification.getSlot(slotType).then((data) => {
 
 ## Notification.getSlots
 
-getSlots(callback: AsyncCallback<Array\<NotificationSlot\>>): void
+getSlots(callback: AsyncCallback\<Array\<NotificationSlot>>): void
 
 获取此应用程序的所有通知通道（callback形式）。
 
@@ -819,7 +791,6 @@ getSlots(callback: AsyncCallback<Array\<NotificationSlot\>>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -842,7 +813,7 @@ Notification.getSlots(getSlotsCallback);
 
 ## Notification.getSlots
 
-getSlots(): Promise\<Array\<NotificationSlot\>>
+getSlots(): Promise\<Array\<NotificationSlot>>
 
 获取此应用程序的所有通知通道（Promise形式）。
 
@@ -860,7 +831,6 @@ getSlots(): Promise\<Array\<NotificationSlot\>>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -896,7 +866,6 @@ removeSlot(slotType: SlotType, callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -938,7 +907,6 @@ removeSlot(slotType: SlotType): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -974,7 +942,6 @@ removeAllSlots(callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1008,7 +975,6 @@ removeAllSlots(): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1049,9 +1015,6 @@ setNotificationEnable(bundle: BundleOption, enable: boolean, callback: AsyncCall
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1100,9 +1063,6 @@ setNotificationEnable(bundle: BundleOption, enable: boolean): Promise\<void\>
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1146,9 +1106,6 @@ isNotificationEnabled(bundle: BundleOption, callback: AsyncCallback\<boolean\>):
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1202,9 +1159,6 @@ isNotificationEnabled(bundle: BundleOption): Promise\<boolean\>
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1247,9 +1201,6 @@ isNotificationEnabled(callback: AsyncCallback\<boolean\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1282,11 +1233,93 @@ isNotificationEnabled(): Promise\<boolean\>
 
 **系统API**: 此接口为系统接口，三方应用不支持调用。
 
+**返回值：**
+
+| 类型                                                        | 说明                                                         |
+| ----------------------------------------------------------- | ------------------------------------------------------------ |
+| Promise\<boolean\> | 以Promise形式返回获取通知使能状态的结果。 |
+
+**错误码：**
+
+错误码详细介绍请参考[errcode-notification](../errorcodes/errorcode-notification.md)。
+
+| 错误码ID | 错误信息                                 |
+| -------- | ---------------------------------------- |
+| 1600001  | Internal error.                          |
+| 1600002  | Marshalling or unmarshalling error.      |
+| 1600003  | Failed to connect service.               |
+
+**示例：**
+
+```ts
+notificationManager.isNotificationEnabled().then((data) => {
+	console.info("isNotificationEnabled success, data: " + JSON.stringify(data));
+});
+```
+
+## notificationManager.isNotificationEnabled
+
+isNotificationEnabled(userId: number, callback: AsyncCallback\<boolean\>): void
+
+获取制定用户ID下的通知使能状态（Callback形式）。
+
+**系统能力**：SystemCapability.Notification.Notification
+
+**需要权限**: ohos.permission.NOTIFICATION_CONTROLLER
+
+**系统API**: 此接口为系统接口，三方应用不支持调用。
+
+**参数：**
+
+| 参数名     | 类型                  | 必填 | 说明                     |
+| -------- | --------------------- | ---- | ------------------------ |
+| userId   | number                | 是   | 指定的用户ID。 |
+| callback | AsyncCallback\<void\> | 是   | 获取通知使能状态回调函数。 |
+
+**错误码：**
+
+错误码详细介绍请参考[errcode-notification](../errorcodes/errorcode-notification.md)。
+
+| 错误码ID | 错误信息                            |
+| -------- | ----------------------------------- |
+| 1600001  | Internal error.                     |
+| 1600002  | Marshalling or unmarshalling error. |
+| 1600003  | Failed to connect service.          |
+| 1600008  | The user is not exist.              |
+
+**示例：**
+
+```ts
+function isNotificationEnabledCallback(err, data) {
+    if (err) {
+        console.error(`isNotificationEnabled failed, code is ${err.code}, message is ${err.message}`);
+    } else {
+        console.info("isNotificationEnabled success");
+    }
+}
+
+let userId = 1;
+
+notificationManager.isNotificationEnabled(userId, isNotificationEnabledCallback);
+```
+
+## notificationManager.isNotificationEnabled
+
+isNotificationEnabled(userId: number): Promise\<boolean\>
+
+获取制定用户下的通知使能状态（Promise形式）。
+
+**系统能力**：SystemCapability.Notification.Notification
+
+**需要权限**: ohos.permission.NOTIFICATION_CONTROLLER
+
+**系统API**: 此接口为系统接口，三方应用不支持调用。
+
 **参数：**
 
 | 参数名   | 类型         | 必填 | 说明       |
 | ------ | ------------ | ---- | ---------- |
-| bundle | [BundleOption](./js-apis-inner-notification-notificationCommonDef.md#bundleoption) | 是   | 指定应用的包信息。 |
+| userId | number       | 是   | 指定的用户ID。 |
 
 **返回值：**
 
@@ -1300,18 +1333,17 @@ isNotificationEnabled(): Promise\<boolean\>
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
-| 17700001 | The specified bundle name was not found. |
+| 1600008  | The user is not exist..                  |
 
 **示例：**
 
-```js
-Notification.isNotificationEnabled().then((data) => {
+```ts
+let userId = 1;
+
+notificationManager.isNotificationEnabled(userId).then((data) => {
 	console.info("isNotificationEnabled success, data: " + JSON.stringify(data));
 });
 ```
@@ -1344,9 +1376,6 @@ displayBadge(bundle: BundleOption, enable: boolean, callback: AsyncCallback\<voi
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1395,9 +1424,6 @@ displayBadge(bundle: BundleOption, enable: boolean): Promise\<void\>
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1441,9 +1467,6 @@ isBadgeDisplayed(bundle: BundleOption, callback: AsyncCallback\<boolean\>): void
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1497,9 +1520,6 @@ isBadgeDisplayed(bundle: BundleOption): Promise\<boolean\>
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1542,9 +1562,6 @@ setSlotByBundle(bundle: BundleOption, slot: NotificationSlot, callback: AsyncCal
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1598,9 +1615,6 @@ setSlotByBundle(bundle: BundleOption, slot: NotificationSlot): Promise\<void\>
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1624,7 +1638,7 @@ Notification.setSlotByBundle(bundle, notificationSlot).then(() => {
 
 ## Notification.getSlotsByBundle
 
-getSlotsByBundle(bundle: BundleOption, callback: AsyncCallback<Array\<NotificationSlot\>>): void
+getSlotsByBundle(bundle: BundleOption, callback: AsyncCallback\<Array\<NotificationSlot>>): void
 
 获取指定应用的所有通知通道（Callback形式）。
 
@@ -1639,7 +1653,7 @@ getSlotsByBundle(bundle: BundleOption, callback: AsyncCallback<Array\<Notificati
 | 参数名     | 类型                                     | 必填 | 说明                 |
 | -------- | ---------------------------------------- | ---- | -------------------- |
 | bundle   | [BundleOption](./js-apis-inner-notification-notificationCommonDef.md#bundleoption)                             | 是   | 指定应用的包信息。           |
-| callback | AsyncCallback<Array\<[NotificationSlot](js-apis-inner-notification-notificationSlot.md)\>> | 是   | 获取通知通道回调函数。 |
+| callback | AsyncCallback\<Array\<[NotificationSlot](js-apis-inner-notification-notificationSlot.md)>> | 是   | 获取通知通道回调函数。 |
 
 **错误码：**
 
@@ -1647,9 +1661,6 @@ getSlotsByBundle(bundle: BundleOption, callback: AsyncCallback<Array\<Notificati
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1675,7 +1686,7 @@ Notification.getSlotsByBundle(bundle, getSlotsByBundleCallback);
 
 ## Notification.getSlotsByBundle
 
-getSlotsByBundle(bundle: BundleOption): Promise<Array\<NotificationSlot\>>
+getSlotsByBundle(bundle: BundleOption): Promise\<Array\<NotificationSlot>>
 
 获取指定应用的所有通知通道（Promise形式）。
 
@@ -1695,7 +1706,7 @@ getSlotsByBundle(bundle: BundleOption): Promise<Array\<NotificationSlot\>>
 
 | 类型                                                        | 说明                                                         |
 | ----------------------------------------------------------- | ------------------------------------------------------------ |
-| Promise<Array\<[NotificationSlot](js-apis-inner-notification-notificationSlot.md)\>> | 以Promise形式返回获取指定应用的通知通道。 |
+| Promise\<Array\<[NotificationSlot](js-apis-inner-notification-notificationSlot.md)>> | 以Promise形式返回获取指定应用的通知通道。 |
 
 **错误码：**
 
@@ -1703,9 +1714,6 @@ getSlotsByBundle(bundle: BundleOption): Promise<Array\<NotificationSlot\>>
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1749,9 +1757,6 @@ getSlotNumByBundle(bundle: BundleOption, callback: AsyncCallback\<number\>): voi
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1805,9 +1810,6 @@ getSlotNumByBundle(bundle: BundleOption): Promise\<number\>
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -1829,7 +1831,7 @@ Notification.getSlotNumByBundle(bundle).then((data) => {
 
 ## Notification.getAllActiveNotifications
 
-getAllActiveNotifications(callback: AsyncCallback<Array\<NotificationRequest\>>): void
+getAllActiveNotifications(callback: AsyncCallback\<Array\<NotificationRequest>>): void
 
 获取当前未删除的所有通知（Callback形式）。
 
@@ -1843,7 +1845,7 @@ getAllActiveNotifications(callback: AsyncCallback<Array\<NotificationRequest\>>)
 
 | 参数名     | 类型                                                         | 必填 | 说明                 |
 | -------- | ------------------------------------------------------------ | ---- | -------------------- |
-| callback | AsyncCallback<Array\<[NotificationRequest](js-apis-inner-notification-notificationRequest.md#notificationrequest)\>> | 是   | 获取活动通知回调函数。 |
+| callback | AsyncCallback\<Array\<[NotificationRequest](js-apis-inner-notification-notificationRequest.md#notificationrequest)>> | 是   | 获取活动通知回调函数。 |
 
 **错误码：**
 
@@ -1851,9 +1853,6 @@ getAllActiveNotifications(callback: AsyncCallback<Array\<NotificationRequest\>>)
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1898,9 +1897,6 @@ getAllActiveNotifications(): Promise\<Array\<[NotificationRequest](js-apis-inner
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1935,7 +1931,6 @@ getActiveNotificationCount(callback: AsyncCallback\<number\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1976,7 +1971,6 @@ getActiveNotificationCount(): Promise\<number\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -1993,7 +1987,7 @@ Notification.getActiveNotificationCount().then((data) => {
 
 ## Notification.getActiveNotifications
 
-getActiveNotifications(callback: AsyncCallback<Array\<NotificationRequest\>>): void
+getActiveNotifications(callback: AsyncCallback\<Array\<NotificationRequest>>): void
 
 获取当前应用未删除的通知列表（Callback形式）。
 
@@ -2003,7 +1997,7 @@ getActiveNotifications(callback: AsyncCallback<Array\<NotificationRequest\>>): v
 
 | 参数名     | 类型                                                         | 必填 | 说明                           |
 | -------- | ------------------------------------------------------------ | ---- | ------------------------------ |
-| callback | AsyncCallback<Array\<[NotificationRequest](js-apis-inner-notification-notificationRequest.md#notificationrequest)\>> | 是   | 获取当前应用通知列表回调函数。 |
+| callback | AsyncCallback\<Array\<[NotificationRequest](js-apis-inner-notification-notificationRequest.md#notificationrequest)>> | 是   | 获取当前应用通知列表回调函数。 |
 
 **错误码：**
 
@@ -2011,7 +2005,6 @@ getActiveNotifications(callback: AsyncCallback<Array\<NotificationRequest\>>): v
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2052,7 +2045,6 @@ getActiveNotifications(): Promise\<Array\<[NotificationRequest](js-apis-inner-no
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2088,7 +2080,6 @@ cancelGroup(groupName: string, callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2131,7 +2122,6 @@ cancelGroup(groupName: string): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2173,9 +2163,6 @@ removeGroupByBundle(bundle: BundleOption, groupName: string, callback: AsyncCall
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -2225,9 +2212,6 @@ removeGroupByBundle(bundle: BundleOption, groupName: string): Promise\<void\>
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -2270,9 +2254,6 @@ setDoNotDisturbDate(date: DoNotDisturbDate, callback: AsyncCallback\<void\>): vo
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2323,9 +2304,6 @@ setDoNotDisturbDate(date: DoNotDisturbDate): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2370,9 +2348,6 @@ setDoNotDisturbDate(date: DoNotDisturbDate, userId: number, callback: AsyncCallb
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2427,9 +2402,6 @@ setDoNotDisturbDate(date: DoNotDisturbDate, userId: number): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2476,9 +2448,6 @@ getDoNotDisturbDate(callback: AsyncCallback\<DoNotDisturbDate\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2523,9 +2492,6 @@ getDoNotDisturbDate(): Promise\<DoNotDisturbDate\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2564,9 +2530,6 @@ getDoNotDisturbDate(userId: number, callback: AsyncCallback\<DoNotDisturbDate\>)
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2620,9 +2583,6 @@ getDoNotDisturbDate(userId: number): Promise\<DoNotDisturbDate\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2663,9 +2623,6 @@ isSupportDoNotDisturbMode(callback: AsyncCallback\<boolean\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2710,9 +2667,6 @@ isSupportDoNotDisturbMode(): Promise\<boolean\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2748,11 +2702,9 @@ isSupportTemplate(templateName: string, callback: AsyncCallback\<boolean\>): voi
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
-| 1600011  | Read template config failed.        |
 
 **示例：**
 
@@ -2797,11 +2749,9 @@ isSupportTemplate(templateName: string): Promise\<boolean\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
-| 1600011  | Read template config failed.        |
 
 **示例：**
 
@@ -2835,7 +2785,6 @@ requestEnableNotification(callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2870,7 +2819,6 @@ requestEnableNotification(): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2910,9 +2858,6 @@ setDistributedEnable(enable: boolean, callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2960,9 +2905,6 @@ setDistributedEnable(enable: boolean): Promise\<void>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -2999,7 +2941,6 @@ isDistributedEnabled(callback: AsyncCallback\<boolean>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3041,7 +2982,6 @@ isDistributedEnabled(): Promise\<boolean>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 401      | The parameter check failed.         |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3083,9 +3023,6 @@ setDistributedEnableByBundle(bundle: BundleOption, enable: boolean, callback: As
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3139,9 +3076,6 @@ setDistributedEnableByBundle(bundle: BundleOption, enable: boolean): Promise\<vo
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3187,9 +3121,6 @@ isDistributedEnabledByBundle(bundle: BundleOption, callback: AsyncCallback\<bool
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3246,9 +3177,6 @@ isDistributedEnabledByBundle(bundle: BundleOption): Promise\<boolean>
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3292,9 +3220,6 @@ getDeviceRemindType(callback: AsyncCallback\<DeviceRemindType\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3339,9 +3264,6 @@ getDeviceRemindType(): Promise\<DeviceRemindType\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3382,9 +3304,6 @@ publishAsBundle(request: NotificationRequest, representativeBundle: string, user
 
 | 错误码ID | 错误信息                                  |
 | -------- | ----------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -3451,9 +3370,6 @@ publishAsBundle(request: NotificationRequest, representativeBundle: string, user
 
 | 错误码ID | 错误信息                                  |
 | -------- | ----------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                           |
 | 1600002  | Marshalling or unmarshalling error.       |
 | 1600003  | Failed to connect service.                |
@@ -3516,9 +3432,6 @@ cancelAsBundle(id: number, representativeBundle: string, userId: number, callbac
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3572,9 +3485,6 @@ cancelAsBundle(id: number, representativeBundle: string, userId: number): Promis
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3621,9 +3531,6 @@ setNotificationEnableSlot(bundle: BundleOption, type: SlotType, enable: boolean,
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3674,9 +3581,6 @@ setNotificationEnableSlot(bundle: BundleOption, type: SlotType, enable: boolean)
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3720,9 +3624,6 @@ isNotificationSlotEnabled(bundle: BundleOption, type: SlotType, callback: AsyncC
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3777,9 +3678,6 @@ isNotificationSlotEnabled(bundle: BundleOption, type: SlotType): Promise\<boolea
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -3822,9 +3720,6 @@ setSyncNotificationEnabledWithoutApp(userId: number, enable: boolean, callback:
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3879,9 +3774,6 @@ setSyncNotificationEnabledWithoutApp(userId: number, enable: boolean): Promise\<
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3926,9 +3818,6 @@ getSyncNotificationEnabledWithoutApp(userId: number, callback: AsyncCallback\<bo
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -3981,9 +3870,6 @@ getSyncNotificationEnabledWithoutApp(userId: number): Promise\<boolean>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201      | Permission denied.                        |
-| 202      | Not system application to call the interface. |
-| 401      | The parameter check failed.               |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-notificationSubscribe.md b/zh-cn/application-dev/reference/apis/js-apis-notificationSubscribe.md
index e7e683660aea1d465b724e484ae188c7d261faf3..b4f509d3457a12e3855b1b40ead3749c167eb2fd 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-notificationSubscribe.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-notificationSubscribe.md
@@ -40,9 +40,6 @@ subscribe(subscriber: NotificationSubscriber, info: NotificationSubscribeInfo, c
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201  | Permission denied.                      |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.             |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -95,9 +92,6 @@ subscribe(subscriber: NotificationSubscriber, callback: AsyncCallback\<void\>):
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201  | Permission denied.                      |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.             |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -148,9 +142,6 @@ subscribe(subscriber: NotificationSubscriber, info?: NotificationSubscribeInfo):
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201  | Permission denied.                      |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.             |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -196,9 +187,6 @@ unsubscribe(subscriber: NotificationSubscriber, callback: AsyncCallback\<void\>)
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201  | Permission denied.                      |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.             |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -246,9 +234,6 @@ unsubscribe(subscriber: NotificationSubscriber): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201  | Permission denied.                      |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.             |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -294,9 +279,6 @@ remove(bundle: BundleOption, notificationKey: NotificationKey, reason: RemoveRea
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201  | Permission denied.                           |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -352,9 +334,6 @@ remove(bundle: BundleOption, notificationKey: NotificationKey, reason: RemoveRea
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201  | Permission denied.                           |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -371,7 +350,7 @@ let notificationKey = {
     id: 0,
     label: "label",
 };
-let reason = NotificationSubscribe.RemoveReason.CLICK_REASON_REMOVE;
+let reason = notificationSubscribe.RemoveReason.CLICK_REASON_REMOVE;
 notificationSubscribe.remove(bundle, notificationKey, reason).then(() => {
 	console.info("remove success");
 });
@@ -393,7 +372,7 @@ remove(hashCode: string, reason: RemoveReason, callback: AsyncCallback\<void\>):
 
 | 参数名     | 类型                  | 必填 | 说明                 |
 | -------- | --------------------- | ---- | -------------------- |
-| hashCode | string                | 是   | 通知唯一ID。可以通过[onConsume](#onconsume)回调的入参[SubscribeCallbackData](js-apis-notification.md#subscribecallbackdata)获取其内部[NotificationRequest](js-apis-inner-notification-notificationRequest.md#notificationrequest)对象中的hashCode。 |
+| hashCode | string                | 是   | 通知唯一ID。可以通过[onConsume](js-apis-notification.md#onconsume)回调的入参[SubscribeCallbackData](js-apis-notification.md#subscribecallbackdata)获取其内部[NotificationRequest](js-apis-inner-notification-notificationRequest.md#notificationrequest)对象中的hashCode。 |
 | reason   | [RemoveReason](#removereason) | 是   | 通知删除原因。         |
 | callback | AsyncCallback\<void\> | 是   | 删除指定通知回调函数。 |
 
@@ -403,9 +382,6 @@ remove(hashCode: string, reason: RemoveReason, callback: AsyncCallback\<void\>):
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201  | Permission denied.                           |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -423,7 +399,7 @@ function removeCallback(err) {
         console.info("remove success");
     }
 }
-let reason = NotificationSubscribe.RemoveReason.CANCEL_REASON_REMOVE;
+let reason = notificationSubscribe.RemoveReason.CANCEL_REASON_REMOVE;
 notificationSubscribe.remove(hashCode, reason, removeCallback);
 ```
 
@@ -452,9 +428,6 @@ remove(hashCode: string, reason: RemoveReason): Promise\<void\>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201  | Permission denied.                           |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -495,9 +468,6 @@ removeAll(bundle: BundleOption, callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201  | Permission denied.                           |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -516,7 +486,7 @@ function removeAllCallback(err) {
 let bundle = {
     bundle: "bundleName1",
 };
-NotificationSubscribe.removeAll(bundle, removeAllCallback);
+notificationSubscribe.removeAll(bundle, removeAllCallback);
 ```
 
 ## NotificationSubscribe.removeAll
@@ -543,9 +513,6 @@ removeAll(callback: AsyncCallback\<void\>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201  | Permission denied.                           |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -588,9 +555,6 @@ removeAll(bundle?: BundleOption): Promise\<void\>
 
 | 错误码ID | 错误信息                                 |
 | -------- | ---------------------------------------- |
-| 201  | Permission denied.                           |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                          |
 | 1600002  | Marshalling or unmarshalling error.      |
 | 1600003  | Failed to connect service.               |
@@ -630,9 +594,6 @@ removeAll(userId: number, callback: AsyncCallback\<void>): void
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201  | Permission denied.                           |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -678,9 +639,6 @@ removeAll(userId: number): Promise\<void>
 
 | 错误码ID | 错误信息                            |
 | -------- | ----------------------------------- |
-| 201  | Permission denied.                           |
-| 202  | Not system application to call the interface. |
-| 401  | The parameter check failed.                  |
 | 1600001  | Internal error.                     |
 | 1600002  | Marshalling or unmarshalling error. |
 | 1600003  | Failed to connect service.          |
@@ -702,319 +660,6 @@ let userId = 1;
 notificationSubscribe.removeAll(userId, removeAllCallback);
 ```
 
-## NotificationSubscriber
-
-作为订阅通知接口[subscribe](#notificationsubscribe)的入参，提供订阅者接收到新通知、取消通知等的回调方法。
-
-**系统API**：此接口为系统接口，三方应用不支持调用。
-
-### onConsume
-
-onConsume?: (data: [SubscribeCallbackData](js-apis-notification.md#subscribecallbackdata)) => void
-
-接收到新通知的回调函数。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统接口**: 此接口为系统接口，三方应用不支持调用。
-
-**参数：**
-
-| 参数名 | 类型 | 必填 | 说明 |
-| ------------ | ------------------------ | ---- | -------------------------- |
-| data | [SubscribeCallbackData](js-apis-notification.md#subscribecallbackdata) | 是 | 新接收到的通知信息。 |
-
-**示例：**
-
-```javascript
-function subscribeCallback(err) {
-    if (err) {
-        console.error(`subscribe failed, code is ${err.code}, message is ${err.message}`);
-    } else {
-        console.info("subscribeCallback");
-    }
-};
-
-function onConsumeCallback(data) {
-    console.info('===> onConsume in test');
-    let req = data.request;
-    console.info('===> onConsume callback req.id:' + req.id);
-};
-
-let subscriber = {
-    onConsume: onConsumeCallback
-};
-
-notificationSubscribe.subscribe(subscriber, subscribeCallback);
-```
-
-### onCancel
-
-onCancel?:(data: [SubscribeCallbackData](js-apis-notification.md#subscribecallbackdata)) => void
-
-取消通知的回调函数。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
-**参数：**
-
-| 参数名 | 类型 | 必填 | 说明 |
-| ------------ | ------------------------ | ---- | -------------------------- |
-| data | [SubscribeCallbackData](js-apis-notification.md#subscribecallbackdata) | 是 | 需要取消的通知信息。 |
-
-**示例：**
-
-```javascript
-function subscribeCallback(err) {
-    if (err) {
-        console.error(`subscribe failed, code is ${err.code}, message is ${err.message}`);
-    } else {
-        console.info("subscribeCallback");
-    }
-};
-
-function onCancelCallback(data) {
-    console.info('===> onCancel in test');
-    let req = data.request;
-    console.info('===> onCancel callback req.id:' + req.id);
-}
-
-let subscriber = {
-    onCancel: onCancelCallback
-};
-
-notificationSubscribe.subscribe(subscriber, subscribeCallback);
-```
-
-### onUpdate
-
-onUpdate?:(data: [NotificationSortingMap](js-apis-notification.md#notificationsortingmap)) => void
-
-更新通知排序的回调函数。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
-**参数：**
-
-| 参数名 | 类型 | 必填 | 说明 |
-| ------------ | ------------------------ | ---- | -------------------------- |
-| data | [NotificationSortingMap](js-apis-notification.md#notificationsortingmap)) | 是 | 最新的通知排序列表。 |
-
-**示例：**
-
-```javascript
-function subscribeCallback(err) {
-    if (err) {
-        console.error(`subscribe failed, code is ${err.code}, message is ${err.message}`);
-    } else {
-        console.info("subscribeCallback");
-    }
-};
-
-function onUpdateCallback(map) {
-    console.info('===> onUpdateCallback map:' + JSON.stringify(map));
-}
-
-let subscriber = {
-    onUpdate: onUpdateCallback
-};
-
-notificationSubscribe.subscribe(subscriber, subscribeCallback);
-```
-
-### onConnect
-
-onConnect?:() => void
-
-订阅完成的回调函数。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
-**示例：**
-
-```javascript
-function subscribeCallback(err) {
-    if (err) {
-        console.error(`subscribe failed, code is ${err.code}, message is ${err.message}`);
-    } else {
-        console.info("subscribeCallback");
-    }
-};
-
-function onConnectCallback() {
-    console.info('===> onConnect in test');
-}
-
-let subscriber = {
-    onConnect: onConnectCallback
-};
-
-notificationSubscribe.subscribe(subscriber, subscribeCallback);
-```
-
-### onDisconnect
-
-onDisconnect?:() => void
-
-取消订阅的回调函数。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
-**示例：**
-
-```javascript
-function subscribeCallback(err) {
-    if (err) {
-        console.error(`subscribe failed, code is ${err.code}, message is ${err.message}`);
-    } else {
-        console.info("subscribeCallback");
-    }
-};
-function unsubscribeCallback(err) {
-    if (err.code) {
-        console.error(`unsubscribe failed, code is ${err.code}, message is ${err.message}`);
-    } else {
-        console.info("unsubscribeCallback");
-    }
-};
-
-function onConnectCallback() {
-    console.info('===> onConnect in test');
-}
-function onDisconnectCallback() {
-    console.info('===> onDisconnect in test');
-}
-
-let subscriber = {
-    onConnect: onConnectCallback,
-    onDisconnect: onDisconnectCallback
-};
-
-// 订阅通知后会收到onConnect回调
-notificationSubscribe.subscribe(subscriber, subscribeCallback);
-// 取消订阅后会收到onDisconnect回调
-notificationSubscribe.unsubscribe(subscriber, unsubscribeCallback);
-```
-
-### onDestroy
-
-onDestroy?:() => void
-
-服务失联回调函数。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
-**示例：**
-
-```javascript
-function subscribeCallback(err) {
-    if (err) {
-        console.error(`subscribe failed, code is ${err.code}, message is ${err.message}`);
-    } else {
-        console.info("subscribeCallback");
-    }
-};
-
-function onDestroyCallback() {
-    console.info('===> onDestroy in test');
-}
-
-let subscriber = {
-    onDestroy: onDestroyCallback
-};
-
-notificationSubscribe.subscribe(subscriber, subscribeCallback);
-```
-
-### onDoNotDisturbDateChange
-
-onDoNotDisturbDateChange?:(mode: notification.[DoNotDisturbDate](js-apis-notificationManager.md#donotdisturbdate)) => void
-
-免打扰时间选项发生变更时的回调函数。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
-**参数：**
-
-| 参数名 | 类型 | 必填 | 说明 |
-| ------------ | ------------------------ | ---- | -------------------------- |
-| mode | notification.[DoNotDisturbDate](js-apis-notificationManager.md#DoNotDisturbDate) | 是 | 回调返回免打扰时间选项变更。 |
-
-**示例：**
-
-```javascript
-function subscribeCallback(err) {
-    if (err) {
-        console.error(`subscribe failed, code is ${err.code}, message is ${err.message}`);
-    } else {
-        console.info("subscribeCallback");
-    }
-};
-
-function onDoNotDisturbDateChangeCallback(mode) {
-    console.info('===> onDoNotDisturbDateChange:' + mode);
-}
-
-let subscriber = {
-    onDoNotDisturbDateChange: onDoNotDisturbDateChangeCallback
-};
-
-notificationSubscribe.subscribe(subscriber, subscribeCallback);
-```
-
-
-### onEnabledNotificationChanged
-
-onEnabledNotificationChanged?:(callbackData: [EnabledNotificationCallbackData](js-apis-notification.md#enablednotificationcallbackdata)) => void
-
-监听应用通知使能变化。
-
-**系统能力**：SystemCapability.Notification.Notification
-
-**系统API**: 此接口为系统接口，三方应用不支持调用。
-
-**参数：**
-
-| 参数名 | 类型 | 必填 | 说明 |
-| ------------ | ------------------------ | ---- | -------------------------- |
-| callback | AsyncCallback\<[EnabledNotificationCallbackData](js-apis-notification.md#enablednotificationcallbackdata)\> | 是 | 回调返回监听到的应用信息。 |
-
-**示例：**
-
-```javascript
-function subscribeCallback(err) {
-    if (err) {
-        console.error(`subscribe failed, code is ${err.code}, message is ${err.message}`);
-    } else {
-        console.info("subscribeCallback");
-    }
-};
-
-function onEnabledNotificationChangedCallback(callbackData) {
-    console.info("bundle: ", callbackData.bundle);
-    console.info("uid: ", callbackData.uid);
-    console.info("enable: ", callbackData.enable);
-};
-
-let subscriber = {
-    onEnabledNotificationChanged: onEnabledNotificationChangedCallback
-};
-
-notificationSubscribe.subscribe(subscriber, subscribeCallback);
-```
-
 ## RemoveReason
 
 **系统能力**：SystemCapability.Notification.Notification
diff --git a/zh-cn/application-dev/reference/apis/js-apis-pasteboard.md b/zh-cn/application-dev/reference/apis/js-apis-pasteboard.md
index b976f8d54ae4826a17f1fcd3aa0d32673f8a312f..c9d05622207981548b15f36bfd3865576d306972 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-pasteboard.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-pasteboard.md
@@ -483,9 +483,9 @@ record.convertToText().then((data) => {
 
 ## PasteData
 
-剪贴板内容对象。
+剪贴板内容对象。剪贴板内容包含一个或者多个内容条目（[PasteDataRecord](#pastedatarecord7)）以及属性描述对象（[PasteDataProperty](#pastedataproperty7)）。
 
-在调用PasteData的接口前，需要先获取一个PasteData对象。
+在调用PasteData的接口前，需要先通过[createData()](#pasteboardcreatedata9)或[getData()](#getdata9)获取一个PasteData对象。
 
 **系统能力：** SystemCapability.MiscServices.Pasteboard
 
@@ -666,8 +666,8 @@ addRecord(mimeType: string, value: ValueType): void
 
   ```js
   let pasteData = pasteboard.createData(pasteboard.MIMETYPE_TEXT_URI, 'dataability:///com.example.myapplication1/user.txt');
-let dataXml = new ArrayBuffer(256);
-pasteData.addRecord('app/xml', dataXml);
+  let dataXml = new ArrayBuffer(256);
+  pasteData.addRecord('app/xml', dataXml);
   ```
 
 ### getMimeTypes<sup>7+</sup>
@@ -1192,10 +1192,10 @@ off(type:  'update', callback?: () =&gt;void ): void
 
 **参数：**
 
-| 参数名 | 类型 | 必填 | 说明                                                        |
-| -------- | -------- | -------- |-----------------------------------------------------------|
-| type | string | 是 | 取值为'update'，表示系统剪贴板内容变化事件。                                |
-| callback | function | 否 | 剪贴板中内容变化时触发的用户程序的回调。 如果此参数未填，表明清除本应用的所有监听回调，否则表示清除指定监听回调。 |
+| 参数名 | 类型 | 必填 | 说明                                                      |
+| -------- | -------- | -------- |---------------------------------------------------------|
+| type | string | 是 | 取值为'update'，表示系统剪贴板内容变化事件。                              |
+| callback | function | 否 | 剪贴板中内容变化时触发的用户程序的回调。如果此参数未填，表明清除本应用的所有监听回调，否则表示清除指定监听回调。|
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-plugincomponent.md b/zh-cn/application-dev/reference/apis/js-apis-plugincomponent.md
index dad78c6fad1f8a8114ab5d487f298f6add5ad09d..ada7897303b8676a5c80336a3d4a761674240deb 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-plugincomponent.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-plugincomponent.md
@@ -155,11 +155,11 @@ OnPushEventCallback = (source: Want, template: PluginComponentTemplate, data: KV
 
 ```js
 function onPushListener(source, template, data, extraData) {
-    console.log("onPushListener template.source=" + template.source)
-    console.log("onPushListener source=" + JSON.stringify(source))
-    console.log("onPushListener template=" + JSON.stringify(template))
-    console.log("onPushListener data=" + JSON.stringify(data))
-    console.log("onPushListener extraData=" + JSON.stringify(extraData))
+  console.log("onPushListener template.source=" + template.source)
+  console.log("onPushListener source=" + JSON.stringify(source))
+  console.log("onPushListener template=" + JSON.stringify(template))
+  console.log("onPushListener data=" + JSON.stringify(data))
+  console.log("onPushListener extraData=" + JSON.stringify(extraData))
 }
 ```
 
@@ -181,14 +181,13 @@ OnRequestEventCallback = (source: Want, name: string, data: KVObject) => Request
 **示例：**
 
 ```js
-function onRequestListener(source, name, data)
-{
-    console.error("onRequestListener");
-    console.log("onRequestListener source=" + JSON.stringify(source));
-    console.log("onRequestListener name=" + name);
-    console.log("onRequestListener data=" + JSON.stringify(data));
+function onRequestListener(source, name, data) {
+  console.error("onRequestListener");
+  console.log("onRequestListener source=" + JSON.stringify(source));
+  console.log("onRequestListener name=" + name);
+  console.log("onRequestListener data=" + JSON.stringify(data));
 
-    return {template:"ets/pages/plugin.js", data:data};
+  return { template: "ets/pages/plugin.js", data: data };
 }
 ```
 
@@ -210,24 +209,24 @@ push(param: PushParameters , callback: AsyncCallback&lt;void&gt;): void
 
 ```js
 pluginComponentManager.push(
-{
+  {
     want: {
-        bundleName: "com.example.provider",
-        abilityName: "com.example.provider.MainAbility",
+      bundleName: "com.example.provider",
+      abilityName: "com.example.provider.MainAbility",
     },
     name: "plugintemplate",
     data: {
-        "key_1": "plugin component test",
-        "key_2": 34234
+      "key_1": "plugin component test",
+      "key_2": 34234
     },
     extraData: {
-        "extra_str": "this is push event"
+      "extra_str": "this is push event"
     },
     jsonPath: "",
-    },
-    (err, data) => {
-        console.log("push_callback: push ok!");
-    }
+  },
+  (err, data) => {
+    console.log("push_callback: push ok!");
+  }
 )
 ```
 
@@ -251,30 +250,30 @@ push(param: PushParameterForStage, callback: AsyncCallback&lt;void&gt;): void
 
 ```js
 pluginComponentManager.push(
-    {
-        owner:{
-            bundleName:"com.example.provider",
-            abilityName:"com.example.provider.MainAbility"
-        },
-        target: {
-            bundleName: "com.example.provider",
-            abilityName: "com.example.provider.MainAbility",
-        },
-        name: "ets/pages/plugin2.js",
-        data: {
-            "js": "ets/pages/plugin.js",
-            "key_1": 1111, ,
-        },
-        extraData: {
-            "extra_str": "this is push event"
-        },
-        jsonPath: "",
+  {
+    owner: {
+      bundleName: "com.example.provider",
+      abilityName: "com.example.provider.MainAbility"
+    },
+    target: {
+      bundleName: "com.example.provider",
+      abilityName: "com.example.provider.MainAbility",
+    },
+    name: "ets/pages/plugin2.js",
+    data: {
+      "js": "ets/pages/plugin.js",
+      "key_1": 1111, ,
+    },
+    extraData: {
+      "extra_str": "this is push event"
     },
-    (err, data) => {
-        console.log("push_callback:err: " ,JSON.stringify(err));
-        console.log("push_callback:data: " , JSON.stringify(data));
-        console.log("push_callback: push ok!");
-    }
+    jsonPath: "",
+  },
+  (err, data) => {
+    console.log("push_callback:err: ", JSON.stringify(err));
+    console.log("push_callback:data: ", JSON.stringify(data));
+    console.log("push_callback: push ok!");
+  }
 )
 ```
 
@@ -299,24 +298,24 @@ request(param: RequestParameters, callback: AsyncCallback&lt;RequestCallbackPara
 
 ```js
 pluginComponentManager.request(
-    {
-        want: {
-            bundleName: "com.example.provider",
-            abilityName: "com.example.provider.MainAbility",
-        },
-        name: "plugintemplate",
-        data: {
-            "key_1": "plugin component test",
-            "key_2": 1111111
-        },
-        jsonPath: "",
+  {
+    want: {
+      bundleName: "com.example.provider",
+      abilityName: "com.example.provider.MainAbility",
     },
-    (err, data) => {
-        console.log("request_callback: componentTemplate.ability=" + data.componentTemplate.ability)
-        console.log("request_callback: componentTemplate.source=" + data.componentTemplate.source)
-        console.log("request_callback: data=" + JSON.stringify(data.data))
-        console.log("request_callback: extraData=" + JSON.stringify(data.extraData))
-    }
+    name: "plugintemplate",
+    data: {
+      "key_1": "plugin component test",
+      "key_2": 1111111
+    },
+    jsonPath: "",
+  },
+  (err, data) => {
+    console.log("request_callback: componentTemplate.ability=" + data.componentTemplate.ability)
+    console.log("request_callback: componentTemplate.source=" + data.componentTemplate.source)
+    console.log("request_callback: data=" + JSON.stringify(data.data))
+    console.log("request_callback: extraData=" + JSON.stringify(data.extraData))
+  }
 )
 ```
 
@@ -342,25 +341,25 @@ request(param: RequestParameterForStage, callback: AsyncCallback&lt;RequestCallb
 
 ```js
 pluginComponentManager.request(
-    {
-        owner:{
-            bundleName:"com.example.provider",
-            abilityName:"com.example.provider.MainAbility"
-            },
-        target: {
-            bundleName: "com.example.provider",
-            abilityName: "ets/pages/plugin2.js",
-            },
-        name: "plugintemplate",
-        data: {
-                "key_1": " myapplication plugin component test",
-                },
-        jsonPath: "",
+  {
+    owner: {
+      bundleName: "com.example.provider",
+      abilityName: "com.example.provider.MainAbility"
+    },
+    target: {
+      bundleName: "com.example.provider",
+      abilityName: "ets/pages/plugin2.js",
     },
-    (err, data) => {
-        console.log("request_callback: componentTemplate.ability=" + data.componentTemplate.ability)
-        console.log("request_callback: componentTemplate.source=" + data.componentTemplate.source)
-    }
+    name: "plugintemplate",
+    data: {
+      "key_1": " myapplication plugin component test",
+    },
+    jsonPath: "",
+  },
+  (err, data) => {
+    console.log("request_callback: componentTemplate.ability=" + data.componentTemplate.ability)
+    console.log("request_callback: componentTemplate.source=" + data.componentTemplate.source)
+  }
 )
 ```
 
@@ -381,8 +380,8 @@ on(eventType: string, callback: OnPushEventCallback | OnRequestEventCallback ):
 **示例：**
 
 ```js
-    pluginComponentManager.on("push", onPushListener)
-    pluginComponentManager.on("request", onRequestListener)
+pluginComponentManager.on("push", onPushListener)
+pluginComponentManager.on("request", onRequestListener)
 ```
 
 ## external.json文件说明
@@ -396,3 +395,5 @@ external.json文件由开发者创建。external.json中以键值对形式存放
   "PluginProviderExample": "ets/pages/PluginProviderExample.js",
   "plugintemplate2": "ets/pages/plugintemplate2.js"
 }
+
+```
\ No newline at end of file
diff --git a/zh-cn/application-dev/reference/apis/js-apis-power.md b/zh-cn/application-dev/reference/apis/js-apis-power.md
index a03ed05ddda5cd846edccc8f7f699f7d62f67a5e..e87ff4b9b17acb804a18795c1a7c98582b9daaf9 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-power.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-power.md
@@ -36,7 +36,7 @@ shutdown(reason: string): void
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4900101 | 连接服务失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -72,7 +72,7 @@ reboot(reason: string): void
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4900101 | 连接服务失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -98,7 +98,7 @@ isActive(): boolean
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4900101 | 连接服务失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -133,7 +133,7 @@ wakeup(detail: string): void
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4900101 | 连接服务失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -161,7 +161,7 @@ suspend(): void
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4900101 | 连接服务失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -193,7 +193,7 @@ getPowerMode(): DevicePowerMode
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4900101 | 连接服务失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -231,7 +231,7 @@ setPowerMode(mode: DevicePowerMode, callback: AsyncCallback&lt;void&gt;): void
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4900101 | 连接服务失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -275,7 +275,7 @@ setPowerMode(mode: DevicePowerMode): Promise&lt;void&gt;
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4900101 | 链接服务失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-radio.md b/zh-cn/application-dev/reference/apis/js-apis-radio.md
index 92cac4d69345aa5a635e5b202b0e9936a6865b1d..3b4caad54c9a73c59126ebc86dfbc685e299995b 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-radio.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-radio.md
@@ -2516,7 +2516,7 @@ off(type: 'imsRegStateChange', slotId: number, imsType: ImsServiceType, callback
 | type     | string                               | 是   | 取消监听IMS注册状态的变化。     |
 | slotId   | number                               | 是   | 卡槽ID。<br/>- 0：卡槽1<br/>- 1：卡槽2 |
 | imsType  | [ImsServiceType](#imsservicetype9)   | 是   | IMS服务类型。                          |
-| callback | Callback<[ImsRegInfo](#imsreginfo9)> | 否   | 回调函数。                             |
+| callback | Callback<[ImsRegInfo](#imsreginfo9)> | 否   | 回调函数。不填该参数不影响取消订阅。 |
 
 **错误码：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-reminderAgent.md b/zh-cn/application-dev/reference/apis/js-apis-reminderAgent.md
index 659a4c964d96ff94d0d57085d6571d2b84282ebd..632a854051913bb16c1d3973a044ff193adcbe4a 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-reminderAgent.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-reminderAgent.md
@@ -18,13 +18,16 @@ import reminderAgent from'@ohos.reminderAgent';
 ```
 
 
-## reminderAgent.publishReminder
+## reminderAgent.publishReminder<sup>(deprecated)</sup>
 
 publishReminder(reminderReq: ReminderRequest, callback: AsyncCallback&lt;number&gt;): void
 
 发布一个后台代理提醒，使用callback方式实现异步调用，该方法需要申请通知弹窗[Notification.requestEnableNotification](js-apis-notification.md#notificationrequestenablenotification8)后才能调用。
 
-**需要权限**： ohos.permission.PUBLISH_AGENT_REMINDER
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.publishReminder](js-apis-reminderAgentManager.md#reminderagentmanagerpublishreminder)替代。
+
+**需要权限**： `ohos.permission.PUBLISH_AGENT_REMINDER`
 
 **系统能力**： SystemCapability.Notification.ReminderAgent
 
@@ -47,13 +50,16 @@ publishReminder(reminderReq: ReminderRequest, callback: AsyncCallback&lt;number&
 ```
 
 
-## reminderAgent.publishReminder
+## reminderAgent.publishReminder<sup>(deprecated)</sup>
 
 publishReminder(reminderReq: ReminderRequest): Promise&lt;number&gt;
 
 发布一个后台代理提醒，使用Promise方式实现异步调用，该方法需要申请通知弹窗[Notification.requestEnableNotification](js-apis-notification.md#notificationrequestenablenotification8)后才能调用。
 
-**需要权限**： ohos.permission.PUBLISH_AGENT_REMINDER
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.publishReminder](js-apis-reminderAgentManager.md#reminderagentmanagerpublishreminder-1)替代。
+
+**需要权限**： `ohos.permission.PUBLISH_AGENT_REMINDER`
 
 **系统能力**： SystemCapability.Notification.ReminderAgent
 
@@ -79,13 +85,16 @@ publishReminder(reminderReq: ReminderRequest): Promise&lt;number&gt;
 ```
 
 
-## reminderAgent.cancelReminder
+## reminderAgent.cancelReminder<sup>(deprecated)</sup>
 
 cancelReminder(reminderId: number, callback: AsyncCallback&lt;void&gt;): void
 
 取消指定id的提醒，使用callback方式实现异步调用。
 
-**系统能力**： SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.cancelReminder](js-apis-reminderAgentManager.md#reminderagentmanagercancelreminder)替代。
+
+**系统能力**： `SystemCapability.Notification.ReminderAgent`
 
 **参数**：
 
@@ -103,13 +112,16 @@ reminderAgent.cancelReminder(1, (err, data) => {
 ```
 
 
-## reminderAgent.cancelReminder
+## reminderAgent.cancelReminder<sup>(deprecated)</sup>
 
-cancelReminder(reminderId: number): Promise&lt;void&gt;
+cancelReminder(reminderId: number): Promise\<void>
 
 取消指定id的提醒，使用Promise方式实现异步调用。
 
-**系统能力**： SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.cancelReminder](js-apis-reminderAgentManager.md#reminderagentmanagercancelreminder-1)替代。
+
+**系统能力**： `SystemCapability.Notification.ReminderAgent`
 
 **参数**：
 
@@ -131,14 +143,16 @@ reminderAgent.cancelReminder(1).then(() => {
 });
 ```
 
+## reminderAgent.getValidReminders<sup>(deprecated)</sup>
 
-## reminderAgent.getValidReminders
-
-getValidReminders(callback: AsyncCallback&lt;Array&lt;ReminderRequest&gt;&gt;): void
+getValidReminders(callback: AsyncCallback\<Array\<ReminderRequest>>): void
 
 获取当前应用已设置的所有有效（未过期）的提醒，使用callback方式实现异步调用。
 
-**系统能力**： SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.getValidReminders](js-apis-reminderAgentManager.md#reminderagentmanagergetvalidreminders)替代。
+
+**系统能力**： `SystemCapability.Notification.ReminderAgent`
 
 **参数**：
 
@@ -176,13 +190,16 @@ reminderAgent.getValidReminders((err, reminders) => {
 ```
 
 
-## reminderAgent.getValidReminders
+## reminderAgent.getValidReminders<sup>(deprecated)</sup>
 
-getValidReminders(): Promise&lt;Array&lt;ReminderRequest&gt;&gt;
+getValidReminders(): Promise\<Array\<ReminderRequest>>
 
 获取当前应用已设置的所有有效（未过期）的提醒，使用Promise方式实现异步调用。
 
-**系统能力**： SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.getValidReminders](js-apis-reminderAgentManager.md#reminderagentmanagergetvalidreminders-1)替代。
+
+**系统能力**： `SystemCapability.Notification.ReminderAgent`
 
 **返回值**：
 
@@ -220,13 +237,16 @@ reminderAgent.getValidReminders().then((reminders) => {
 ```
 
 
-## reminderAgent.cancelAllReminders
+## reminderAgent.cancelAllReminders<sup>(deprecated)</sup>
 
 cancelAllReminders(callback: AsyncCallback&lt;void&gt;): void
 
 取消当前应用所有的提醒，使用callback方式实现异步调用。
 
-**系统能力**： SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.cancelAllReminders](js-apis-reminderAgentManager.md#reminderagentmanagercancelallreminders)替代。
+
+**系统能力**： `SystemCapability.Notification.ReminderAgent`
 
 **参数**：
 
@@ -243,13 +263,16 @@ reminderAgent.cancelAllReminders((err, data) =>{
 ```
 
 
-## reminderAgent.cancelAllReminders
+## reminderAgent.cancelAllReminders<sup>(deprecated)</sup>
 
-cancelAllReminders(): Promise&lt;void&gt;
+cancelAllReminders(): Promise\<void>
 
 取消当前应用所有的提醒，使用Promise方式实现异步调用。
 
-**系统能力**： SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.cancelAllReminders](js-apis-reminderAgentManager.md#reminderagentmanagercancelallreminders-1)替代。
+
+**系统能力**： `SystemCapability.Notification.ReminderAgent`
 
 **返回值**：
 
@@ -272,7 +295,10 @@ addNotificationSlot(slot: NotificationSlot, callback: AsyncCallback&lt;void&gt;)
 
 添加一个NotificationSlot，使用callback方式实现异步调用。
 
-**系统能力**： SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.addNotificationSlot](js-apis-reminderAgentManager.md#reminderagentmanageraddnotificationslot)替代。
+
+**系统能力**： `SystemCapability.Notification.ReminderAgent`
 
 **参数**：
 
@@ -295,13 +321,16 @@ reminderAgent.addNotificationSlot(mySlot, (err, data) => {
 ```
 
 
-## reminderAgent.addNotificationSlot
+## reminderAgent.addNotificationSlot<sup>(deprecated)</sup>
 
-addNotificationSlot(slot: NotificationSlot): Promise&lt;void&gt;
+addNotificationSlot(slot: NotificationSlot): Promise\<void>
 
 添加一个NotificationSlot，使用Promise方式实现异步调用。
 
-**系统能力**： SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.addNotificationSlot](js-apis-reminderAgentManager.md#reminderagentmanageraddnotificationslot-1)替代。
+
+**系统能力**： `SystemCapability.Notification.ReminderAgent`
 
 **参数**：
 
@@ -329,13 +358,16 @@ reminderAgent.addNotificationSlot(mySlot).then(() => {
 ```
 
 
-## reminderAgent.removeNotificationSlot
+## reminderAgent.removeNotificationSlot<sup>(deprecated)</sup>
 
 removeNotificationSlot(slotType: notification.SlotType, callback: AsyncCallback&lt;void&gt;): void
 
 删除目标NotificationSlot，使用callback方式实现异步调用。
 
-**系统能力**： SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.removeNotificationSlot](js-apis-reminderAgentManager.md#reminderagentmanagerremovenotificationslot)替代。
+
+**系统能力**： `SystemCapability.Notification.ReminderAgent`
 
 **参数**：
 
@@ -355,13 +387,16 @@ reminderAgent.removeNotificationSlot(notification.SlotType.CONTENT_INFORMATION,
 ```
 
 
-## reminderAgent.removeNotificationSlot
+## reminderAgent.removeNotificationSlot<sup>(deprecated)</sup>
 
 removeNotificationSlot(slotType: notification.SlotType): Promise&lt;void&gt;
 
 删除目标NotificationSlot，使用Promise方式实现异步调用。
 
-**系统能力**： SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.removeNotificationSlot](js-apis-reminderAgentManager.md#reminderagentmanagerremovenotificationslot-1)替代。
+
+**系统能力**： `SystemCapability.Notification.ReminderAgent`
 
 **参数**：
 
@@ -386,11 +421,14 @@ reminderAgent.removeNotificationSlot(notification.SlotType.CONTENT_INFORMATION).
 ```
 
 
-## ActionButtonType
+## ActionButtonType<sup>(deprecated)</sup>
 
 按钮的类型。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.ActionButtonType](js-apis-reminderAgentManager.md#ActionButtonType)替代。
+
+**系统能力**：`SystemCapability.Notification.ReminderAgent`
 
 | 名称 | 值 | 说明 |
 | -------- | -------- | -------- |
@@ -398,11 +436,14 @@ reminderAgent.removeNotificationSlot(notification.SlotType.CONTENT_INFORMATION).
 | ACTION_BUTTON_TYPE_SNOOZE | 1 | 表示延迟提醒的按钮。 |
 
 
-## ReminderType
+## ReminderType<sup>(deprecated)</sup>
 
 提醒的类型。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.ReminderType](js-apis-reminderAgentManager.md#ReminderType)替代。
+
+**系统能力**：`SystemCapability.Notification.ReminderAgent`
 
 | 名称 | 值 | 说明 |
 | -------- | -------- | -------- |
@@ -411,11 +452,14 @@ reminderAgent.removeNotificationSlot(notification.SlotType.CONTENT_INFORMATION).
 | REMINDER_TYPE_ALARM | 2 | 表示提醒类型：闹钟。 |
 
 
-## ActionButton
+## ActionButton<sup>(deprecated)</sup>
 
 用于设置弹出的提醒通知信息上显示的按钮类型和标题。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.ActionButton](js-apis-reminderAgentManager.md#ActionButton)替代。
+
+**系统能力**：`SystemCapability.Notification.ReminderAgent`
 
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
@@ -423,11 +467,14 @@ reminderAgent.removeNotificationSlot(notification.SlotType.CONTENT_INFORMATION).
 | type | [ActionButtonType](#actionbuttontype) | 是 | 按钮的类型。 |
 
 
-## WantAgent
+## WantAgent<sup>(deprecated)</sup>
 
 点击提醒通知后跳转的目标ability信息。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.WantAgent](js-apis-reminderAgentManager.md#WantAgent)替代。
+
+**系统能力**：`SystemCapability.Notification.ReminderAgent`
 
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
@@ -435,11 +482,14 @@ reminderAgent.removeNotificationSlot(notification.SlotType.CONTENT_INFORMATION).
 | abilityName | string | 是 | 指明点击提醒通知栏后跳转的目标ability名称。 |
 
 
-## MaxScreenWantAgent
+## MaxScreenWantAgent<sup>(deprecated)</sup>
 
 全屏显示提醒到达时自动拉起的目标ability信息，该接口预留。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.MaxScreenWantAgent](js-apis-reminderAgentManager.md#MaxScreenWantAgent)替代。
+
+**系统能力**：`SystemCapability.Notification.ReminderAgent`
 
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
@@ -447,11 +497,14 @@ reminderAgent.removeNotificationSlot(notification.SlotType.CONTENT_INFORMATION).
 | abilityName | string | 是 | 指明提醒到达时自动拉起的目标ability名（如果设备在使用中，则只弹出通知横幅框）。 |
 
 
-## ReminderRequest
+## ReminderRequest<sup>(deprecated)</sup>
 
 提醒实例对象，用于设置提醒类型、响铃时长等具体信息。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.ReminderRequest](js-apis-reminderAgentManager.md#ReminderRequest)替代。
+
+**系统能力**：`SystemCapability.Notification.ReminderAgent`
 
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
@@ -470,13 +523,16 @@ reminderAgent.removeNotificationSlot(notification.SlotType.CONTENT_INFORMATION).
 | slotType | [notification.SlotType](js-apis-notification.md#slottype) | 否 | 指明提醒的slot类型。 |
 
 
-## ReminderRequestCalendar
+## ReminderRequestCalendar<sup>(deprecated)</sup>
 
 ReminderRequestCalendar extends ReminderRequest
 
 日历实例对象，用于设置提醒的时间。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.ReminderRequestCalendar](js-apis-reminderAgentManager.md#ReminderRequestCalendar)替代。
+
+**系统能力**：`SystemCapability.Notification.ReminderAgent`
 
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
@@ -485,13 +541,16 @@ ReminderRequestCalendar extends ReminderRequest
 | repeatDays | Array&lt;number&gt; | 否 | 指明重复提醒的日期。 |
 
 
-## ReminderRequestAlarm
+## ReminderRequestAlarm<sup>(deprecated)</sup>
 
 ReminderRequestAlarm extends ReminderRequest
 
 闹钟实例对象，用于设置提醒的时间。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.ReminderRequestAlarm](js-apis-reminderAgentManager.md#ReminderRequestAlarm)替代。
+
+**系统能力**：`SystemCapability.Notification.ReminderAgent`
 
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
@@ -500,24 +559,30 @@ ReminderRequestAlarm extends ReminderRequest
 | daysOfWeek | Array&lt;number&gt; | 否 | 指明每周哪几天需要重复提醒。范围为周一到周末，对应数字为1到7。 |
 
 
-## ReminderRequestTimer
+## ReminderRequestTimer<sup>(deprecated)</sup>
 
 ReminderRequestTimer extends ReminderRequest
 
 倒计时实例对象，用于设置提醒的时间。
 
-**系统能力**：SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.ReminderRequestTimer](js-apis-reminderAgentManager.md#ReminderRequestTimer)替代。
+
+**系统能力**：`SystemCapability.Notification.ReminderAgent`
 
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
 | triggerTimeInSeconds | number | 是 | 指明倒计时的秒数。 |
 
 
-## LocalDateTime
+## LocalDateTime<sup>(deprecated)</sup>
 
 用于日历类提醒设置时指定时间信息。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.ReminderAgent
+> **说明：**
+> 从 API version 7开始支持，从API version 9开始废弃。建议使用[reminderAgentManager.LocalDateTime](js-apis-reminderAgentManager.md#LocalDateTime)替代。
+
+**系统能力**：`SystemCapability.Notification.ReminderAgent`
 
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-reminderAgentManager.md b/zh-cn/application-dev/reference/apis/js-apis-reminderAgentManager.md
index cfb15104b76488f84b66eec239d6c2470434d6c3..449d85a4ba26aa1c22dc9281be0c067d4807f6b2 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-reminderAgentManager.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-reminderAgentManager.md
@@ -564,7 +564,7 @@ try {
 
 用于设置弹出的提醒通知信息上显示的按钮类型和标题。
 
-**系统能力**：以下各项对应的系统能力均为SystemCapability.Notification.ReminderAgent
+**系统能力**：`SystemCapability.Notification.ReminderAgent`
 
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
@@ -580,8 +580,9 @@ try {
 
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| pkgName | string | 是 | 指明点击提醒通知栏后跳转的目标hap包名。 |
-| abilityName | string | 是 | 指明点击提醒通知栏后跳转的目标ability名称。 |
+| pkgName | string | 是 | 指明跳转的目标包名。 |
+| abilityName | string | 是 | 指明跳转的目标ability名称。 |
+| uri | string | 否 | 指明跳转目标的uri信息。（系统接口） |
 
 
 ## MaxScreenWantAgent
diff --git a/zh-cn/application-dev/reference/apis/js-apis-request.md b/zh-cn/application-dev/reference/apis/js-apis-request.md
index 0d254844110c21eaead7ed08a4572cfb9dde5922..721177662ec7309958e3d1eb0a966fec98c138ba 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-request.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-request.md
@@ -97,7 +97,7 @@ uploadFile(context: BaseContext, config: UploadConfig): Promise&lt;UploadTask&gt
 
   | 错误码ID | 错误信息 |
   | -------- | -------- |
-  | 13400002 | Bad file path. |
+  | 13400002 | bad file path. |
 
 **示例：**
 
@@ -145,7 +145,7 @@ uploadFile(context: BaseContext, config: UploadConfig, callback: AsyncCallback&l
 
   | 错误码ID | 错误信息 |
   | -------- | -------- |
-  | 13400002 | Bad file path. |
+  | 13400002 | bad file path. |
 
 **示例：**
 
@@ -360,7 +360,7 @@ on(type: 'headerReceive', callback:  (header: object) =&gt; void): void
         console.info("upOnComplete taskState:" + JSON.stringify(taskStates[i]));
     }
   };
-  uploadTask.on('complete', upComplete);
+  uploadTask.on('complete', upCompleteCallback);
 
   let upFailCallback = (taskStates) => {
     for (let i = 0; i < taskStates.length; i++ ) {
@@ -391,6 +391,9 @@ off(type:  'progress',  callback?: (uploadedSize: number, totalSize: number) =&g
 **示例：**
 
   ```js
+  let upProgressCallback = (uploadedSize, totalSize) => {
+      console.info('Upload delete progress notification.' + 'totalSize:' + totalSize + 'uploadedSize:' + uploadedSize);
+  };
   uploadTask.off('progress', upProgressCallback);
   ```
 
@@ -415,6 +418,9 @@ off(type: 'headerReceive', callback?: (header: object) =&gt; void): void
 **示例：**
 
   ```js
+  let headerCallback = (header) => {
+      console.info(`Upload delete headerReceive notification. header: ${JSON.stringify(header)}`);
+  };
   uploadTask.off('headerReceive', headerCallback);
   ```
 
@@ -438,8 +444,20 @@ off(type: 'headerReceive', callback?: (header: object) =&gt; void): void
 **示例：**
 
   ```js
+  let upCompleteCallback = (taskStates) => {
+    console.info('Upload delete complete notification.');
+    for (let i = 0; i < taskStates.length; i++ ) {
+        console.info('taskState:' + JSON.stringify(taskStates[i]));
+    }
+  };
   uploadTask.off('complete', upCompleteCallback);
 
+  let upFailCallback = (taskStates) => {
+    console.info('Upload delete fail notification.');
+    for (let i = 0; i < taskStates.length; i++ ) {
+      console.info('taskState:' + JSON.stringify(taskStates[i]));
+    }
+  };
   uploadTask.off('fail', upFailCallback);
   ```
 
@@ -657,9 +675,9 @@ downloadFile(context: BaseContext, config: DownloadConfig): Promise&lt;DownloadT
 
   | 错误码ID | 错误信息 |
   | -------- | -------- |
-  | 13400001 | File operation error. |
-  | 13400002 | Bad file path. |
-  | 13400003 | Task manager service error. |
+  | 13400001 | file operation error. |
+  | 13400002 | bad file path. |
+  | 13400003 | task manager service error. |
 
 **示例：**
 
@@ -700,9 +718,9 @@ downloadFile(context: BaseContext, config: DownloadConfig, callback: AsyncCallba
 
   | 错误码ID | 错误信息 |
   | -------- | -------- |
-  | 13400001 | File operation error. |
-  | 13400002 | Bad file path. |
-  | 13400003 | Task manager service error. |
+  | 13400001 | file operation error. |
+  | 13400002 | bad file path. |
+  | 13400003 | task manager service error. |
 
 **示例：**
 
@@ -827,10 +845,10 @@ on(type: 'progress', callback:(receivedSize: number, totalSize: number) =&gt; vo
 **示例：**
 
   ```js
-  let progresCallbanck = (receivedSize, totalSize) => {
+  let progresCallback = (receivedSize, totalSize) => {
       console.info("download receivedSize:" + receivedSize + " totalSize:" + totalSize);
   };
-  downloadTask.on('progress', progresCallbanck);
+  downloadTask.on('progress', progresCallback);
   ```
 
 
@@ -854,7 +872,10 @@ off(type: 'progress', callback?: (receivedSize: number, totalSize: number) =&gt;
 **示例：**
 
   ```js
-  downloadTask .off('progress',progresCallbanck);
+  let progresCallback = (receivedSize, totalSize) => {
+      console.info('Download delete progress notification.' + 'receivedSize:' + receivedSize + 'totalSize:' + totalSize);
+  };
+  downloadTask.off('progress', progresCallback);
   ```
 
 
@@ -882,6 +903,16 @@ on(type: 'complete'|'pause'|'remove', callback:() =&gt; void): void
       console.info('Download task completed.');
   };
   downloadTask.on('complete', completeCallback);
+
+  let pauseCallback = () => {
+      console.info('Download task pause.');
+  };
+  downloadTask.on('pause', pauseCallback);
+
+  let removeCallback = () => {
+      console.info('Download task remove.');
+  };
+  downloadTask.on('remove', removeCallback);
   ```
 
 
@@ -905,7 +936,20 @@ off(type: 'complete'|'pause'|'remove', callback?:() =&gt; void): void
 **示例：**
 
   ```js
+  let completeCallback = () => {
+      console.info('Download delete complete notification.');
+  };
   downloadTask.off('complete', completeCallback);
+
+  let pauseCallback = () => {
+      console.info('Download delete pause notification.');
+  };
+  downloadTask.off('pause', pauseCallback);
+
+  let removeCallback = () => {
+      console.info('Download delete remove notification.');
+  };
+  downloadTask.off('remove', removeCallback);
   ```
 
 
@@ -962,6 +1006,9 @@ off(type: 'fail', callback?: (err: number) =&gt; void): void
 **示例：**
 
   ```js
+  let failCallback = (err) => {
+      console.info(`Download delete fail notification. err: ${err.message}`);
+  };
   downloadTask.off('fail', failCallback);
   ```
 
@@ -1607,7 +1654,7 @@ resume(callback: AsyncCallback&lt;void&gt;): void
 | -------- | -------- | -------- | -------- |
 | url | string | 是 | 资源地址。 |
 | header | Object | 否 | 添加要包含在下载请求中的HTTPS标志头。<br/>开发者可以通过header的X-TLS-Version参数指定需要使用的TLS版本(如果不指定，则默认使用CURL_SSLVERSION_TLSv1_2版本，指定则使用指定版本。)<br/>CURL_SSLVERSION_TLSv1_0<br/>CURL_SSLVERSION_TLSv1_1<br/>CURL_SSLVERSION_TLSv1_2<br/>CURL_SSLVERSION_TLSv1_3<br/>通过header的X-Cipher-List参数指定需要使用的密码套件(如果不指定，则默认使用安全密码套件，指定则使用指定密码套件。)<br/>-1.2允许使用的密码套件白名单：<br/>TLS_DHE_RSA_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_AES_256_GCM_SHA384,<br/>TLS_DHE_DSS_WITH_AES_128_GCM_SHA256,TLS_DSS_RSA_WITH_AES_256_GCM_SHA384,<br/>TLS_PSK_WITH_AES_256_GCM_SHA384,TLS_DHE_PSK_WITH_AES_128_GCM_SHA256,<br/>TLS_DHE_PSK_WITH_AES_256_GCM_SHA384,TLS_DHE_PSK_WITH_CHACHA20_POLY1305_SHA256,<br/>TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,<br/>TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,<br/>TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_PSK_WITH_CHACHA20_POLY1305_SHA256,<br/>TLS_ECDHE_PSK_WITH_AES_128_GCM_SHA256,TLS_ECDHE_PSK_WITH_AES_256_GCM_SHA384,<br/>TLS_ECDHE_PSK_WITH_AES_128_GCM_SHA256,TLS_DHE_RSA_WITH_AES_128_CCM,<br/>TLS_DHE_RSA_WITH_AES_256_CCM,TLS_DHE_RSA_WITH_CHACHA20_POLY1305_SHA256,<br/>TLS_PSK_WITH_AES_256_CCM,TLS_DHE_PSK_WITH_AES_128_CCM,<br/>TLS_DHE_PSK_WITH_AES_256_CCM,TLS_ECDHE_ECDSA_WITH_AES_128_CCM,<br/>TLS_ECDHE_ECDSA_WITH_AES_256_CCM,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256<br/>-1.3允许使用的密码套件白名单：<br/>TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_AES_128_CCM_SHA256<br/>-1.3新增国密算法套：<br/>TLS_SM4_GCM_SM3,TLS_SM4_CCM_SM3 |
-| enableMetered | boolean | 否 | 设置是否允许在按流量计费的连接下下载(默认使用false)。<br/>-&nbsp;true：是<br/>-&nbsp;false：否 |
+| enableMetered | boolean | 否 | 设置是否允许在按流量计费的连接下下载(默认使用false)。Wi-Fi为非计费网络，数据流量为计费网络。<br/>-&nbsp;true：是<br/>-&nbsp;false：否 |
 | enableRoaming | boolean | 否 | 设置是否允许在漫游网络中下载(默认使用false)。 <br/>-&nbsp;true：是<br/>-&nbsp;false：否|
 | description | string | 否 | 设置下载会话的描述。 |
 | filePath<sup>7+</sup> | string | 否 | 设置下载路径。<br/>-&nbsp;FA模型下使用[context](js-apis-inner-app-context.md#contextgetcachedir) 获取应用存储路径，比如：\'${featureAbility.getContext().getFilesDir()}/test.txt\'，并将文件存储在此路径下。<br/>-&nbsp;Stage模型下使用[AbilityContext](js-apis-inner-application-context.md) 类获取文件路径，比如：\'${globalThis.abilityContext.tempDir}/test.txt\'并将文件存储在此路径下。 |
@@ -1623,17 +1670,17 @@ resume(callback: AsyncCallback&lt;void&gt;): void
 
 **系统能力**: SystemCapability.MiscServices.Download
 
-| 名称 | 类型 | 说明 |
-| -------- | ------ |---------------- |
-| downloadId | number | 下载任务ID。 |
-| failedReason | number | 下载失败原因，可以是任何[下载任务的错误码](#下载任务的错误码)常量。 |
-| fileName | string | 下载的文件名。 |
-| filePath | string | 存储文件的URI。 |
-| pausedReason | number | 会话暂停的原因，可以是任何[下载任务暂停原因](#下载任务暂停原因)常量。 |
-| status | number | 下载状态码，可以是任何[下载任务状态码](#下载任务状态码)常量。 |
-| targetURI | string | 下载文件的URI。 |
-| downloadTitle | string | 下载任务名称。 |
-| downloadTotalBytes | number | 下载的文件的总大小（int&nbsp;bytes）。 |
-| description | string | 待下载任务的描述信息。 |
-| downloadedBytes | number | 实时下载大小（int&nbsp;&nbsp;bytes）。 |
+| 名称 | 类型 | 必填 | 说明 |
+| -------- | ------ | ------ |---------------- |
+| downloadId | number | 是 |下载任务ID。 |
+| failedReason | number | 是 |下载失败原因，可以是任何[下载任务的错误码](#下载任务的错误码)常量。 |
+| fileName | string | 是 |下载的文件名。 |
+| filePath | string | 是 |存储文件的URI。 |
+| pausedReason | number |是 | 会话暂停的原因，可以是任何[下载任务暂停原因](#下载任务暂停原因)常量。 |
+| status | number | 是 |下载状态码，可以是任何[下载任务状态码](#下载任务状态码)常量。 |
+| targetURI | string | 是 |下载文件的URI。 |
+| downloadTitle | string | 是 |下载任务名称。 |
+| downloadTotalBytes | number |是 | 下载的文件的总大小（int&nbsp;bytes）。 |
+| description | string |是 | 待下载任务的描述信息。 |
+| downloadedBytes | number | 是 |实时下载大小（int&nbsp;&nbsp;bytes）。 |
 <!--no_check-->
\ No newline at end of file
diff --git a/zh-cn/application-dev/reference/apis/js-apis-resourceschedule-deviceUsageStatistics.md b/zh-cn/application-dev/reference/apis/js-apis-resourceschedule-deviceUsageStatistics.md
index 62c12ed4e43a62ab8638a71e2e91f9adf10bec58..92d9b57320216d7a033ecd5c7211da9f68a18a80 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-resourceschedule-deviceUsageStatistics.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-resourceschedule-deviceUsageStatistics.md
@@ -1587,7 +1587,7 @@ FA卡片的使用信息的属性集合。
 
 | 参数名                            | 类型                                       | 必填   | 说明             |
 | ------------------------------ | ---------------------------------------- | ---- | -------------- |
-| [key: string]: BundleStatsInfo | [key: string]: [BundleStatsInfo](#bundlestatsinfo) | 是    | 不同应用的使用时长统计信息。 |
+| [key: string] | [BundleStatsInfo](#bundlestatsinfo) | 是    | 不同应用的使用时长统计信息。 |
 
 ## DeviceEventStats
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-resourceschedule-workScheduler.md b/zh-cn/application-dev/reference/apis/js-apis-resourceschedule-workScheduler.md
index 482c103218009534aeb1f4a453dd478211957c16..91bba9e6a2de73da665c2e16f894cf62520c352f 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-resourceschedule-workScheduler.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-resourceschedule-workScheduler.md
@@ -118,7 +118,7 @@ stopWork(work: WorkInfo, needCancel?: boolean): void
   }
 ```
 
-## workScheduler.getWorkStatus:callback
+## workScheduler.getWorkStatus
 getWorkStatus(workId: number, callback : AsyncCallback\<WorkInfo>): void
 
 获取工作的最新状态，使用Callback形式返回。
@@ -161,7 +161,7 @@ getWorkStatus(workId: number, callback : AsyncCallback\<WorkInfo>): void
   }
 ```
 
-## workScheduler.getWorkStatus:promise
+## workScheduler.getWorkStatus
 getWorkStatus(workId: number): Promise\<WorkInfo>
 
 获取工作的最新状态，使用Promise形式返回。
@@ -207,7 +207,7 @@ getWorkStatus(workId: number): Promise\<WorkInfo>
   }
 ```
 
-## workScheduler.obtainAllWorks:callback
+## workScheduler.obtainAllWorks
 obtainAllWorks(callback : AsyncCallback\<void>): Array\<WorkInfo>
 
 获取与当前应用程序关联的所有工作，使用Callback形式返回。
@@ -252,8 +252,8 @@ obtainAllWorks(callback : AsyncCallback\<void>): Array\<WorkInfo>
   }
 ```
 
-## workScheduler.obtainAllWorks:promise
-obtainAllWorks(): Promise<Array\<WorkInfo>>
+## workScheduler.obtainAllWorks
+obtainAllWorks(): Promise\<Array\<WorkInfo>>
 
 获取与当前应用程序关联的所有工作，使用Promise形式返回。
 
@@ -317,7 +317,7 @@ stopAndClearWorks(): void
   }
 ```
 
-## workScheduler.isLastWorkTimeOut:callback
+## workScheduler.isLastWorkTimeOut
 isLastWorkTimeOut(workId: number, callback : AsyncCallback\<void>): boolean
 
 检查指定工作的最后一次执行是否为超时操作，使用Callback形式返回。
@@ -364,7 +364,7 @@ isLastWorkTimeOut(workId: number, callback : AsyncCallback\<void>): boolean
   }
 ```
 
-## workScheduler.isLastWorkTimeOut:promise
+## workScheduler.isLastWorkTimeOut
 isLastWorkTimeOut(workId: number): Promise\<boolean>
 
 检查指定工作的最后一次执行是否为超时操作，使用Promise形式返回。
@@ -432,7 +432,7 @@ isLastWorkTimeOut(workId: number): Promise\<boolean>
 | isPersisted     | boolean                           | 否    | 是否持久化保存工作        |
 | isDeepIdle      | boolean                           | 否    | 是否要求设备进入空闲状态     |
 | idleWaitTime    | number                            | 否    | 空闲等待时间           |
-| parameters      | {[key: string]: number | string | boolean}              | 否    | 携带参数信息           |
+| parameters      | {[key: string]: number \| string \| boolean}              | 否    | 携带参数信息           |
 
 ## NetworkType
 触发工作的网络类型。
diff --git a/zh-cn/application-dev/reference/apis/js-apis-router.md b/zh-cn/application-dev/reference/apis/js-apis-router.md
index 97d0974a039625a53fa30c3a6d88f8f7ab8dc6f3..52a5633cba72956a34cc350a34ada590ca0aee8f 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-router.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-router.md
@@ -320,7 +320,7 @@ replaceUrl(options: RouterOptions, mode: RouterMode): Promise&lt;void&gt;
 
 | 错误码ID   | 错误信息 |
 | --------- | ------- |
-| 100001    | if UI execution context not found, only throw in standard system. |
+| 100001    | if can not get the delegate, only throw in standard system. |
 | 200002    | if the uri is not exist. |
 
 **示例：**
@@ -362,7 +362,7 @@ replaceUrl(options: RouterOptions, mode: RouterMode, callback: AsyncCallback&lt;
 
 | 错误码ID   | 错误信息 |
 | --------- | ------- |
-| 100001    | if can not get the delegate, only throw in standard system. |
+| 100001    | if UI execution context not found, only throw in standard system. |
 | 200002    | if the uri is not exist. |
 
 **示例：**
@@ -659,8 +659,8 @@ struct Second {
   private content: string = "这是第二页"
   @State text: string = router.getParams()['text']
   @State data: object = router.getParams()['data']
-  @State secondData : string = ''
-  
+  @State secondData: string = ''
+
   build() {
     Flex({ direction: FlexDirection.Column, alignItems: ItemAlign.Center, justifyContent: FlexAlign.Center }) {
       Text(`${this.content}`)
@@ -668,14 +668,14 @@ struct Second {
         .fontWeight(FontWeight.Bold)
       Text(this.text)
         .fontSize(30)
-        .onClick(()=>{
+        .onClick(() => {
           this.secondData = (this.data.['array'][1]).toString()
         })
-      .margin({top:20})
+        .margin({ top: 20 })
       Text(`第一页传来的数值:${this.secondData}`)
         .fontSize(20)
-        .margin({top:20})
-        .backgroundColor('red')      
+        .margin({ top: 20 })
+        .backgroundColor('red')
     }
     .width('100%')
     .height('100%')
diff --git a/zh-cn/application-dev/reference/apis/js-apis-rpc.md b/zh-cn/application-dev/reference/apis/js-apis-rpc.md
index 8eab9108278155967de12031d86900d53f46a140..a771ad00f3b52cdf37d618e20c2df40db12b8cdd 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-rpc.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-rpc.md
@@ -2396,7 +2396,7 @@ readException(): void
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -2414,10 +2414,10 @@ readException(): void
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -4856,9 +4856,9 @@ readException(): void
   Stage模型的应用在获取服务前需要先获取context，具体方法可参考[获取context](#获取context)
 
   ```ts
-  // 仅FA模型需要导入@ohos.ability.;featureAbility
+  // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -4876,10 +4876,10 @@ readException(): void
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -5450,6 +5450,7 @@ marshalling(dataOut: MessageSequence): boolean
   | 类型    | 说明                             |
   | ------- | -------------------------------- |
   | boolean | true：封送成功，false：封送失败。|
+
 **示例：**
 
   ```ts
@@ -5555,6 +5556,7 @@ marshalling(dataOut: MessageParcel): boolean
   | 类型    | 说明                              |
   | ------- | --------------------------------  |
   | boolean | true：封送成功，false：封送失败。 |
+
 **示例：**
 
   ```ts
@@ -5671,7 +5673,7 @@ asObject(): IRemoteObject
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -5689,10 +5691,10 @@ asObject(): IRemoteObject
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6115,7 +6117,7 @@ sendRequest(code: number, data: MessageParcel, reply: MessageParcel, options: Me
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6133,10 +6135,10 @@ sendRequest(code: number, data: MessageParcel, reply: MessageParcel, options: Me
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6191,7 +6193,7 @@ sendMessageRequest(code: number, data: MessageSequence, reply: MessageSequence,
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6209,10 +6211,10 @@ sendMessageRequest(code: number, data: MessageSequence, reply: MessageSequence,
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6275,7 +6277,7 @@ sendRequest(code: number, data: MessageParcel, reply: MessageParcel, options: Me
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6293,10 +6295,10 @@ sendRequest(code: number, data: MessageParcel, reply: MessageParcel, options: Me
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6352,7 +6354,7 @@ sendMessageRequest(code: number, data: MessageSequence, reply: MessageSequence,
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6383,10 +6385,10 @@ sendMessageRequest(code: number, data: MessageSequence, reply: MessageSequence,
       result.data.reclaim();
       result.reply.reclaim();
   }
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6433,7 +6435,7 @@ sendRequest(code: number, data: MessageParcel, reply: MessageParcel, options: Me
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6464,10 +6466,10 @@ sendRequest(code: number, data: MessageParcel, reply: MessageParcel, options: Me
       result.data.reclaim();
       result.reply.reclaim();
   }
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6517,7 +6519,7 @@ getLocalInterface(interface: string): IRemoteBroker
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6535,10 +6537,10 @@ getLocalInterface(interface: string): IRemoteBroker
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6583,7 +6585,7 @@ queryLocalInterface(interface: string): IRemoteBroker
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6601,10 +6603,10 @@ queryLocalInterface(interface: string): IRemoteBroker
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6645,7 +6647,7 @@ registerDeathRecipient(recipient: DeathRecipient, flags: number): void
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6663,10 +6665,10 @@ registerDeathRecipient(recipient: DeathRecipient, flags: number): void
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6717,7 +6719,7 @@ addDeathRecipient(recipient: DeathRecipient, flags: number): boolean
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6735,10 +6737,10 @@ addDeathRecipient(recipient: DeathRecipient, flags: number): boolean
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6784,7 +6786,7 @@ unregisterDeathRecipient(recipient: DeathRecipient, flags: number): void
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6802,10 +6804,10 @@ unregisterDeathRecipient(recipient: DeathRecipient, flags: number): void
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6857,7 +6859,7 @@ removeDeathRecipient(recipient: DeathRecipient, flags: number): boolean
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6875,10 +6877,10 @@ removeDeathRecipient(recipient: DeathRecipient, flags: number): boolean
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -6925,7 +6927,7 @@ getDescriptor(): string
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -6943,10 +6945,10 @@ getDescriptor(): string
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
   上述onConnect回调函数中的proxy对象需要等ability异步连接成功后才会被赋值，然后才可调用proxy对象的getDescriptor接口方法获取对象的接口描述符
@@ -6984,7 +6986,7 @@ getInterfaceDescriptor(): string
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -7002,10 +7004,10 @@ getInterfaceDescriptor(): string
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -7037,7 +7039,7 @@ isObjectDead(): boolean
   ```ts
   // 仅FA模型需要导入@ohos.ability.featureAbility
   // import FA from "@ohos.ability.featureAbility";
-  
+
   let proxy;
   let connect = {
       onConnect: function(elementName, remoteProxy) {
@@ -7055,10 +7057,10 @@ isObjectDead(): boolean
       "bundleName": "com.ohos.server",
       "abilityName": "com.ohos.server.EntryAbility",
   };
-  
+
   // FA模型使用此方法连接服务
   // FA.connectAbility(want,connect);
-  
+
   globalThis.context.connectServiceExtensionAbility(want, connect);
   ```
 
@@ -7093,9 +7095,9 @@ MessageOption构造函数。
 
 **参数：**
 
-  | 参数名    | 类型   | 必填 | 说明                                   |
-  | --------- | ------ | ---- | -------------------------------------- |
-  | syncFlags | number | 否   | 同步调用或异步调用标志。默认同步调用。 |
+| 参数名 | 类型    | 必填 | 说明                                   |
+| ------ | ------- | ---- | -------------------------------------- |
+| async  | boolean | 否   | 同步调用或异步调用标志。默认同步调用。 |
 
 
 **示例：**
@@ -7823,7 +7825,7 @@ sendMessageRequest(code: number, data: MessageSequence, reply: MessageSequence,
 
   | 类型                         | 说明                                          |
   | ---------------------------- | --------------------------------------------- |
-  | Promise&lt;RequestResult&gt; | 返回一个期约，兑现值是sendRequestResult实例。 |
+  | Promise&lt;RequestResult&gt; | 返回一个期约，兑现值是RequestResult实例。     |
 
 **示例：**
 
@@ -9099,30 +9101,31 @@ readFromAshmem(size: number, offset: number): number[]
 
  ```ts
   import Ability from '@ohos.app.ability.UIAbility';
+
   export default class MainAbility extends Ability {
-    onCreate(want, launchParam) {
-        console.log("[Demo] MainAbility onCreate");
-        globalThis.context = this.context;
-    }
-    onDestroy() {
-        console.log("[Demo] MainAbility onDestroy");
-    }
-    onWindowStageCreate(windowStage) {
-        // Main window is created, set main page for this ability
-        console.log("[Demo] MainAbility onWindowStageCreate");
-    }
-    onWindowStageDestroy() {
-        // Main window is destroyed, release UI related resources
-        console.log("[Demo] MainAbility onWindowStageDestroy");
-    }
-    onForeground() {
-        // Ability has brought to foreground
-        console.log("[Demo] MainAbility onForeground");
-    }
-    onBackground() {
-        // Ability has back to background
-        console.log("[Demo] MainAbility onBackground");
-    }
+      onCreate(want, launchParam) {
+          console.log("[Demo] MainAbility onCreate");
+          globalThis.context = this.context;
+      }
+      onDestroy() {
+          console.log("[Demo] MainAbility onDestroy");
+      }
+      onWindowStageCreate(windowStage) {
+          // Main window is created, set main page for this ability
+          console.log("[Demo] MainAbility onWindowStageCreate");
+      }
+      onWindowStageDestroy() {
+          // Main window is destroyed, release UI related resources
+          console.log("[Demo] MainAbility onWindowStageDestroy");
+      }
+      onForeground() {
+          // Ability has brought to foreground
+          console.log("[Demo] MainAbility onForeground");
+      }
+      onBackground() {
+          // Ability has back to background
+          console.log("[Demo] MainAbility onBackground");
+      }  
   };
  ```
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-runninglock.md b/zh-cn/application-dev/reference/apis/js-apis-runninglock.md
index c98c19d58950f4320a1559d1fdf5bc937a26b4c0..ee5e434d5468d3c57a6234b60b4e8b5088ca1061 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-runninglock.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-runninglock.md
@@ -38,7 +38,7 @@ isSupported(type: RunningLockType): boolean;
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4900101 | 连接服务失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -75,7 +75,7 @@ create(name: string, type: RunningLockType, callback: AsyncCallback&lt;RunningLo
 
 | 错误码ID   | 错误信息     |
 |---------|----------|
-| 4900101 | 连接服务器失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -118,7 +118,7 @@ create(name: string, type: RunningLockType): Promise&lt;RunningLock&gt;
 
 | 错误码ID   | 错误信息     |
 |---------|----------|
-| 4900101 | 连接服务器失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -290,7 +290,7 @@ hold(timeout: number): void
 
 | 错误码ID   | 错误信息     |
 |---------|----------|
-| 4900101 | 连接服务器失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -326,7 +326,7 @@ unhold(): void
 
 | 错误码ID   | 错误信息     |
 |---------|----------|
-| 4900101 | 连接服务器失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -366,7 +366,7 @@ isHolding(): boolean
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4900101 | 连接服务失败。 |
+| 4900101 | If connecting to the service failed. |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-stationary.md b/zh-cn/application-dev/reference/apis/js-apis-stationary.md
index 2ea3413e0ce3ca6d00a0f86aa13e895dd9d48b68..14c971750b9df9889c9687e5098411e58b39f489 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-stationary.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-stationary.md
@@ -123,7 +123,7 @@ off(activity: ActivityType, event: ActivityEvent, callback?: Callback&lt;Activit
 | -------------------- | -------------------------------------------------- | ---- | ---------------------------- |
 | activity  | [ActivityType](#activitytype)  | 是   | 设备状态能力类型。              |
 | event  | [ActivityEvent](#activityevent)  | 是   | 事件类型。              |
-| callback             | Callback<[ActivityResponse](#activityresponse)\>  | 否   | 回调函数，接收上报状态变化事件。    |
+| callback             | Callback<[ActivityResponse](#activityresponse)\>  | 否   | 回调函数，接收上报状态变化事件，如果没有传递callback参数，会移除该进程下订阅该类型得所有callback。    |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-system-battery.md b/zh-cn/application-dev/reference/apis/js-apis-system-battery.md
index d917ea5ff7e1bc5e234295b4072083fd6184572e..0c102a55bb2e4b90ed8caeed8866f44fc86a5f6f 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-system-battery.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-system-battery.md
@@ -27,7 +27,7 @@ getStatus(options?: GetStatusOptions): void;
 
 | 名称 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| options | [GetStatusOptions](#getstatusoptions) | 否 | 包含接口调用结果的对象。 |
+| options | [GetStatusOptions](#getstatusoptions) | 否 | 包含接口调用结果的对象。可选，默认为空。 |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-system-brightness.md b/zh-cn/application-dev/reference/apis/js-apis-system-brightness.md
index 0d44e435efd777c9f7a0c557ecbb69ca552c3d62..9097f8f38dd76cf4f29fa1edcad22c58462a1830 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-system-brightness.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-system-brightness.md
@@ -28,7 +28,7 @@ getValue(options?: GetBrightnessOptions): void
 
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| options | [GetBrightnessOptions](#getbrightnessoptions) | 否   | 获取屏幕亮度的参数对象。 |
+| options | [GetBrightnessOptions](#getbrightnessoptions) | 否   | 获取屏幕亮度的参数对象。可选，默认为空。 |
 
 **示例：**
 
@@ -56,7 +56,7 @@ setValue(options?: SetBrightnessOptions): void
 
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| options | [SetBrightnessOptions](#setbrightnessoptions) | 否   | 设置屏幕亮度的参数对象。 |
+| options | [SetBrightnessOptions](#setbrightnessoptions) | 否   | 设置屏幕亮度的参数对象。可选，默认为空。 |
 
 **示例：**
 
@@ -85,7 +85,7 @@ getMode(options?: GetBrightnessModeOptions): void
 
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| options | [GetBrightnessModeOptions](#getbrightnessmodeoptions) | 否 | 获取屏幕亮度模式的参数对象。 |
+| options | [GetBrightnessModeOptions](#getbrightnessmodeoptions) | 否 | 获取屏幕亮度模式的参数对象。可选，默认为空。 |
 
 **示例：**
 
@@ -112,7 +112,7 @@ setMode(options?: SetBrightnessModeOptions): void
 **参数：**
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| options | [SetBrightnessModeOptions](#setbrightnessmodeoptions) | 否   | 设置屏幕亮度模式的参数对象。 |
+| options | [SetBrightnessModeOptions](#setbrightnessmodeoptions) | 否   | 设置屏幕亮度模式的参数对象。可选，默认为空。 |
 
 **示例：**
 
@@ -143,7 +143,7 @@ setKeepScreenOn(options?: SetKeepScreenOnOptions): void
 
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| options | [SetKeepScreenOnOptions](#setkeepscreenonoptions) | 否 | 设置屏幕常亮的参数对象。 |
+| options | [SetKeepScreenOnOptions](#setkeepscreenonoptions) | 否 | 设置屏幕常亮的参数对象。可选，默认为空。 |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-system-router.md b/zh-cn/application-dev/reference/apis/js-apis-system-router.md
index 96a9e913ce4faf33d435fb8080d8746ad1e26c54..4d22c6d63cb4a3e66c13a22cf2a2fa93fa1220c6 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-system-router.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-system-router.md
@@ -341,8 +341,8 @@ export default {
 
 | 名称   | 类型 | 必填 | 说明                                                         |
 | ------ | -------- | ---- | ------------------------------------------------------------ |
-| uri    | string   | 是   | 目标页面的uri，可以是以下的两种格式：<br/>1. 页面的绝对路径，由config.json文件中的页面列表提供。例如：<br/>- pages/index/index<br/> -pages/detail/detail<br/>2. 特定路径。如果URI为斜杠（/），则显示主页。 |
-| params | object   | 否   | 表示路由跳转时要同时传递到目标页面的数据。跳转到目标页面后，使用router.getParams()获取传递的参数，此外，在类web范式中，参数也可以在页面中直接使用，如this.keyValue(keyValue为跳转时params参数中的key值)，如果目标页面中已有该字段，则其值会被传入的字段值覆盖。 |
+| uri<sup>7+</sup> | string   | 是   | 目标页面的uri，可以是以下的两种格式：<br/>1. 页面的绝对路径，由config.json文件中的页面列表提供。例如：<br/>- pages/index/index<br/> -pages/detail/detail<br/>2. 特定路径。如果URI为斜杠（/），则显示主页。 |
+| params<sup>7+</sup> | object   | 否   | 表示路由跳转时要同时传递到目标页面的数据。跳转到目标页面后，使用router.getParams()获取传递的参数，此外，在类web范式中，参数也可以在页面中直接使用，如this.keyValue(keyValue为跳转时params参数中的key值)，如果目标页面中已有该字段，则其值会被传入的字段值覆盖。 |
 
 
 ## BackRouterOptions
@@ -353,8 +353,8 @@ export default {
 
 | 名称   | 类型 | 必填 | 说明                                                         |
 | ------ | -------- | ---- | ------------------------------------------------------------ |
-| uri    | string   | 否   | 返回到指定uri的界面，如果页面栈上没有uri页面，则不响应该情况。如果uri未设置，则返回上一页。 <br>**系统能力：** SystemCapability.ArkUI.ArkUI.Full |
-| params | object   | 否   | 跳转时要同时传递到目标页面的数据。 <br>**系统能力：** SystemCapability.ArkUI.ArkUI.Lite |
+| uri<sup>7+</sup> | string   | 否   | 返回到指定uri的界面，如果页面栈上没有uri页面，则不响应该情况。如果uri未设置，则返回上一页。 <br>**系统能力：** SystemCapability.ArkUI.ArkUI.Full |
+| params<sup>7+</sup> | object   | 否   | 跳转时要同时传递到目标页面的数据。 <br>**系统能力：** SystemCapability.ArkUI.ArkUI.Lite |
 
 ## RouterState
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-system-sensor.md b/zh-cn/application-dev/reference/apis/js-apis-system-sensor.md
index 2f3d54255a9a81a80a337a8877df9e76c032fecc..f23a26cfc42e199fb9560c4c304f108ba7224630 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-system-sensor.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-system-sensor.md
@@ -89,7 +89,7 @@ sensor.unsubscribeAccelerometer();
 ```js
 sensor.subscribeCompass({
   success: function(ret) {
-    console.log('get data direction:' + ret.direction);
+    console.log('Get data direction:' + ret.direction);
   },
   fail: function(data, code) {
     console.error('Subscription failed. Code: ' + code + '; Data: ' + data);
@@ -133,7 +133,7 @@ sensor.unsubscribeCompass();
 ```js
 sensor.subscribeProximity({
   success: function(ret) {
-    console.log('get data distance:' + ret.distance);
+    console.log('Get data distance:' + ret.distance);
   },
   fail: function(data, code) {
     console.error('Subscription failed. Code: ' + code + '; Data: ' + data);
@@ -177,7 +177,7 @@ sensor.unsubscribeProximity();
 ```js
 sensor.subscribeLight({
   success: function(ret) {
-    console.log('get data intensity:' + ret.intensity);
+    console.log('Get data intensity:' + ret.intensity);
   },
   fail: function(data, code) {
     console.error('Subscription failed. Code: ' + code + '; Data: ' + data);
@@ -223,7 +223,7 @@ sensor.unsubscribeLight();
 ```js
 sensor.subscribeStepCounter({
   success: function(ret) {
-    console.log('get step value:' + ret.steps);
+    console.log('Get step value:' + ret.steps);
   },
   fail: function(data, code) {
     console.log('Subscription failed. Code: ' + code + '; Data: ' + data);
@@ -255,7 +255,7 @@ sensor.unsubscribeStepCounter();
 
 subscribeBarometer(options: SubscribeBarometerOptions): void
 
-订阅气压传感器数据变化。针对同一个应用，多次点击调用时，会覆盖前面的调用效果，即仅最后一次调用生效。
+订阅气压计传感器数据变化。针对同一个应用，多次点击调用时，会覆盖前面的调用效果，即仅最后一次调用生效。
 
 **系统能力**：SystemCapability.Sensors.Sensor
 
@@ -270,7 +270,7 @@ subscribeBarometer(options: SubscribeBarometerOptions): void
 ```js
 sensor.subscribeBarometer({
   success: function(ret) {
-    console.log('get data value:' + ret.pressure);
+    console.log('Get data value:' + ret.pressure);
   },
   fail: function(data, code) {
     console.log('Subscription failed. Code: ' + code + '; Data: ' + data);
@@ -286,7 +286,7 @@ sensor.subscribeBarometer({
 
 unsubscribeBarometer(): void
 
-取消订阅气压传感器。
+取消订阅气压计传感器。
 
 **系统能力**：SystemCapability.Sensors.Sensor
 
@@ -318,7 +318,7 @@ sensor.unsubscribeBarometer();
 ```js
 sensor.subscribeHeartRate({
   success: function(ret) {
-    console.log('get heartrate value:' + ret.heartRate);
+    console.log('Get heartrate value:' + ret.heartRate);
   },
   fail: function(data, code) {
     console.log('Subscription failed. Code: ' + code + '; Data: ' + data);
@@ -334,7 +334,7 @@ sensor.subscribeHeartRate({
 
 unsubscribeHeartRate(): void
 
-取消订阅心率。
+取消订阅心率传感器。
 
 **系统能力**：SystemCapability.Sensors.Sensor
 
@@ -365,7 +365,7 @@ sensor.unsubscribeHeartRate();
 ```js
 sensor.subscribeOnBodyState({
   success: function(ret) {
-    console.log('get on-body state value:' + ret.value);
+    console.log('Get on-body state value:' + ret.value);
   },
   fail: function(data, code) {
     console.log('Subscription failed. Code: ' + code + '; Data: ' + data);
@@ -409,7 +409,7 @@ sensor.unsubscribeOnBodyState();
 ```js
 sensor.getOnBodyState({
   success: function(ret) {
-    console.log('on body state: ' + ret.value);
+    console.log('On body state: ' + ret.value);
   },
   fail: function(data, code) {
     console.log('Subscription failed. Code: ' + code + '; Data: ' + data);
@@ -470,7 +470,7 @@ sensor.unsubscribeDeviceOrientation();
 
  subscribeGyroscope(options: SubscribeGyroscopeOptions): void
 
-观察陀螺仪数据变化。
+观察陀螺仪传感器数据变化。
 
 针对同一个应用，多次点击调用时，会覆盖前面的调用效果，即仅最后一次调用生效；针对同一个方法内，不支持多次调用。
 
@@ -507,7 +507,7 @@ sensor.subscribeGyroscope({
 
 unsubscribeGyroscope(): void
 
-取消订阅陀螺仪数据。
+取消订阅陀螺仪传感器数据。
 
 **系统能力**：SystemCapability.Sensors.Sensor
 
@@ -643,12 +643,12 @@ sensor.unsubscribeGyroscope();
 
 | 名称    | 类型                                    | 必填 | 说明                             |
 | ------- | --------------------------------------- | ---- | -------------------------------- |
-| success | [BarometerResponse](#barometerresponse) | 是   | 气压传感器数据改变后的回调函数。 |
+| success | [BarometerResponse](#barometerresponse) | 是   | 气压计传感器数据改变后的回调函数。 |
 | fail    | Function                                | 否   | 接口调用失败的回调函数。         |
 
 ## BarometerResponse 
 
-气压传感器数据改变后的回调函数。
+气压计传感器数据改变后的回调函数。
 
 **系统能力**：SystemCapability.Sensors.Sensor
 
@@ -710,7 +710,7 @@ sensor.unsubscribeGyroscope();
 
 | 名称     | 类型                                        | 必填 | 说明                     |
 | -------- | ------------------------------------------- | ---- | ------------------------ |
-| success  | [OnBodyStateResponse](#onbodystateresponse) | 否   | 接口调用成功的回调函数。 |
+| success  | [OnBodyStateResponse](#onbodystateresponse) | 是   | 接口调用成功的回调函数。 |
 | fail     | Function                                    | 否   | 接口调用失败的回调函数。 |
 | complete | Function                                    | 否   | 接口调用结束的回调函数。 |
 
@@ -754,7 +754,7 @@ sensor.unsubscribeGyroscope();
 
 ## GyroscopeResponse<sup>6+</sup> 
 
-感应到陀螺仪数据变化后的回调函数。
+感应到陀螺仪传感器数据变化后的回调函数。
 
 **需要权限**：ohos.permission.GYROSCOPE
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-thermal.md b/zh-cn/application-dev/reference/apis/js-apis-thermal.md
index 2e2e42c50360a00b3ebb3ece5f708d8250a2c99b..f3e304c00c4b3e37c31303516de651fae43090d1 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-thermal.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-thermal.md
@@ -32,7 +32,7 @@ registerThermalLevelCallback(callback: Callback&lt;ThermalLevel&gt;): void
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4800101 | 连接服务失败。 |
+| 4800101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -67,7 +67,7 @@ unregisterThermalLevelCallback(callback?: Callback\<void>): void
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4800101 | 连接服务失败。 |
+| 4800101 | If connecting to the service failed. |
 
 **示例：**
 
@@ -102,7 +102,7 @@ getLevel(): ThermalLevel
 
 | 错误码ID   | 错误信息    |
 |---------|---------|
-| 4800101 | 连接服务失败。 |
+| 4800101 | If connecting to the service failed. |
 
 **示例：**
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-timer.md b/zh-cn/application-dev/reference/apis/js-apis-timer.md
index ae0957a9b4978d69674f4a63fa0b861fc1a3a48b..669a26623435c1d03bf87456c31506d0df8699e4 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-timer.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-timer.md
@@ -18,7 +18,7 @@ setTimeout(handler: Function | string, delay?: number, ...arguments: any[]): num
 
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| handler | Function \| string | 是 | 定时器到期后执行函数。 |
+| handler | Function \| string | 是 | 定时器到期后执行函数。类型为string则打印Error信息，不进行其他处理。 |
 | delay | number | 否 | 延迟的毫秒数，函数的调用会在该延迟之后发生。如果省略该参数，delay取默认值0，意味着“马上”执行，或尽快执行。 |
 | ...arguments | Array&lt;any&gt; | 否 | 附加参数，一旦定时器到期，它们会作为参数传递给handler。 |
 
@@ -26,24 +26,20 @@ setTimeout(handler: Function | string, delay?: number, ...arguments: any[]): num
 
 | 类型 | 说明 |
 | -------- | -------- |
-| number | timeout定时器的ID。 |
+| number | 该定时器的ID。 |
 
 **示例：**
 
   ```js
-  export default {    
-    setTimeOut() {        
-      var timeoutID = setTimeout(function() {            
-        console.log('delay 1s');
-      }, 1000);    
-    }
-  }
+  setTimeout(function() {            
+    console.log('delay 1s');
+  }, 1000);
   ```
 
 
 ## clearTimeout
 
-clearTimeout(timeoutID: number): void
+clearTimeout(timeoutID?: number): void
 
 取消了先前通过调用setTimeout()建立的定时器。
 
@@ -53,19 +49,15 @@ clearTimeout(timeoutID: number): void
 
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| timeoutID | number | 是 | 要取消定时器的ID，&nbsp;是由setTimeout()返回的。 |
+| timeoutID | number | 否 | 要取消定时器的ID，&nbsp;是由setTimeout()返回的。如果省略该参数，则不取消任何定时任务，无任何处理。|
 
 **示例：**
 
-  ```js
-  export default {    
-    clearTimeOut() {        
-      var timeoutID = setTimeout(function() {            
-        console.log('do after 1s delay.');        
-      }, 1000);        
-      clearTimeout(timeoutID);    
-    }
-  }
+  ```js    
+  let timeoutID = setTimeout(function() {            
+    console.log('do after 1s delay.');        
+  }, 1000);        
+  clearTimeout(timeoutID);
   ```
 
 
@@ -81,32 +73,28 @@ setInterval(handler: Function | string, delay: number, ...arguments: any[]): num
 
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| handler | Function \| string | 是 | 要重复调用的函数。 |
-| delay | number | 是 | 延迟的毫秒数（一秒等于1000毫秒），函数的调用会在该延迟之后发生。 |
+| handler | Function \| string | 是 | 要重复调用的函数。类型为string则打印Error信息，不进行其他处理。|
+| delay | number | 是 | 延迟的毫秒数，函数的调用会在该延迟之后发生。 |
 | ...arguments | Array&lt;any&gt; | 否 | 附加参数，一旦定时器到期，他们会作为参数传递给handler。 |
 
 **返回值：**
 
 | 类型 | 说明 |
 | -------- | -------- |
-| number | intervalID重复定时器的ID。 |
+| number | 该定时器的ID。 |
 
 **示例：**
 
   ```js
-  export default {    
-    setInterval() {        
-      var intervalID = setInterval(function() {            
-        console.log('do very 1s.');        
-      }, 1000);    
-    }
-  }
+  setInterval(function() {            
+    console.log('do every 1s.');        
+  }, 1000);
   ```
 
 
 ## clearInterval
 
-clearInterval(intervalID: number): void
+clearInterval(intervalID?: number): void
 
 可取消先前通过setInterval()设置的重复定时任务。
 
@@ -116,17 +104,13 @@ clearInterval(intervalID: number): void
 
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| intervalID | number | 是 | 要取消的重复定时器的ID，是由&nbsp;setInterval()&nbsp;返回的。 |
+| intervalID | number | 否 | 要取消的重复定时器的ID，是由&nbsp;setInterval()&nbsp;返回的。如果省略该参数，则不取消任何定时任务，无任何处理。|
 
 **示例：**
 
-  ```js
-  export default {    
-    clearInterval() {        
-      var intervalID = setInterval(function() {
-        console.log('do very 1s.');
-      }, 1000);
-      clearInterval(intervalID);
-    }
-  }
+  ```js      
+  let intervalID = setInterval(function() {
+    console.log('do every 1s.');
+  }, 1000);
+  clearInterval(intervalID);
   ```
diff --git a/zh-cn/application-dev/reference/apis/js-apis-uitest.md b/zh-cn/application-dev/reference/apis/js-apis-uitest.md
index 97ec1fc917f2e6851962f4955bc98a69ccac89a6..f532dfc53caa5900ebc8fd7a61991e2895d38228 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-uitest.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-uitest.md
@@ -2093,7 +2093,7 @@ fling(from: Point, to: Point, stepLen: number, speed: number): Promise\<void>
 ```js
 async function demo() {
     let driver = Driver.create();
-    await driver.fling({x: 500, Y: 480},{x: 450, Y: 480},5,600);
+    await driver.fling({x: 500, y: 480},{x: 450, y: 480},5,600);
 }
 ```
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-url.md b/zh-cn/application-dev/reference/apis/js-apis-url.md
index 9545f710b3bb38e7c78ce52010f2b5e4c92ff25e..77fe1371423c81cc9f493010766834a5ae18b783 100755
--- a/zh-cn/application-dev/reference/apis/js-apis-url.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-url.md
@@ -23,7 +23,7 @@ URLParams的构造函数。
 
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| init | string[][] \| Record&lt;string, string&gt; \| string \| URLSearchParams | 否 | 入参对象。<br/>- string[][]：字符串二维数组<br/>- Record&lt;string, string&gt;：对象列表<br/>- string：字符串<br/>- URLSearchParams：对象 |
+| init | string[][] \| Record&lt;string, string&gt; \| string \| URLSearchParams | 否 | 入参对象。<br/>- string[][]：字符串二维数组<br/>- Record&lt;string, string&gt;：对象列表<br/>- string：字符串<br/>- URLSearchParams：对象<br/>- 默认值：null。 |
 
 **示例：**
 
@@ -150,7 +150,7 @@ forEach(callbackFn: (value: string, key: string, searchParams: this) => void, th
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
 | callbackFn | function | 是 | 回调函数。 |
-| thisArg | Object | 否 | callbackFn被调用时用作this值 |
+| thisArg | Object | 否 | callbackFn被调用时用作this值，默认值是本对象。 |
 
 **表1** callbackFn的参数说明
 
@@ -404,7 +404,7 @@ URL的构造函数。
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
 | url | string | 是 | 入参对象。 |
-| base | string \| URL | 否 | 入参字符串或者对象。<br/>- string：字符串<br/>- URL：字符串或对象 |
+| base | string \| URL | 否 | 入参字符串或者对象。<br/>- string：字符串<br/>- URL：字符串或对象<br/>- 默认值是空字符串或空对象。 |
 
 **示例：**
 
@@ -444,7 +444,7 @@ URL静态成员函数。
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
 | url | string | 是 | 入参对象。 |
-| base | string \| URL | 否 | 入参字符串或者对象。<br/>- string：字符串<br/>- URL：字符串或对象 |
+| base | string \| URL | 否 | 入参字符串或者对象。<br/>- string：字符串<br/>- URL：字符串或对象<br/>- 默认值是空字符串或空对象。 |
 
 **错误码：**
 
@@ -522,7 +522,7 @@ URLSearchParams的构造函数。
 
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| init | string[][] \| Record&lt;string, string&gt; \| string \| URLSearchParams | 否 | 入参对象。<br/>- string[][]：字符串二维数组<br/>- Record&lt;string, string&gt;：对象列表<br/>- string：字符串<br/>- URLSearchParams：对象 |
+| init | string[][] \| Record&lt;string, string&gt; \| string \| URLSearchParams | 否 | 入参对象。<br/>- string[][]：字符串二维数组<br/>- Record&lt;string, string&gt;：对象列表<br/>- string：字符串<br/>- URLSearchParams：对象<br/>- 默认值：null。 |
 
 **示例：**
 
@@ -665,7 +665,7 @@ forEach(callbackFn: (value: string, key: string, searchParams: this) => void, th
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
 | callbackFn | function | 是 | 回调函数。 |
-| thisArg | Object | 否 | callbackFn被调用时用作this值 |
+| thisArg | Object | 否 | callbackFn被调用时用作this值，默认值是本对象。 |
 
 **表1** callbackFn的参数说明
 
diff --git a/zh-cn/application-dev/reference/apis/js-apis-usbManager.md b/zh-cn/application-dev/reference/apis/js-apis-usbManager.md
index c9dbcbbfe22ef45fa59569695297f02d5df07da5..4d4b694f7ded0314d274209755474931d66fa8a8 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-usbManager.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-usbManager.md
@@ -30,7 +30,7 @@ getDevices(): Array&lt;Readonly&lt;USBDevice&gt;&gt;
 
 ```js
 let devicesList = usb.getDevices();
-cconsole.log(`devicesList = ${devicesList}`);
+console.log(`devicesList = ${devicesList}`);
 //devicesList  返回的数据结构
 //此处提供一个简单的示例，如下
 [
@@ -209,8 +209,8 @@ removeRight(deviceName: string): boolean
 **示例：**
 
 ```js
-let devicesName="1-1";
-if usb.removeRight(devicesName) {
+let devicesName= "1-1";
+if (usb.removeRight(devicesName)) {
   console.log(`Succeed in removing right`);
 }
 ```
@@ -245,7 +245,7 @@ addRight(bundleName: string, deviceName: string): boolean
 ```js
 let devicesName = "1-1";
 let bundleName = "com.example.hello";
-if usb.addRight(bundleName, devicesName) {
+if (usb.addRight(bundleName, devicesName)) {
   console.log(`Succeed in adding right`);
 }
 ```
@@ -454,7 +454,14 @@ controlTransfer(pipe: USBDevicePipe, controlparam: USBControlParams, timeout ?:
 **示例：**
 
 ```js
-let param = new usb.USBControlParams();
+let param = {
+  request: 0,
+  reqType: 0,
+  target:0,
+  value: 0,
+  index: 0,
+  data: null
+};
 usb.controlTransfer(devicepipe, param).then((ret) => {
  console.log(`controlTransfer = ${ret}`);
 })
@@ -579,7 +586,7 @@ usbFunctionsToString(funcs: FunctionType): string
 **示例：**
 
 ```js
-let funcs = usb.ACM | usb.ECM;
+let funcs = usb.FunctionType.ACM | usb.FunctionType.ECM;
 let ret = usb.usbFunctionsToString(funcs);
 ```
 
@@ -608,7 +615,7 @@ setCurrentFunctions(funcs: FunctionType): Promise\<void\>
 **示例：**
 
 ```js
-let funcs = usb.HDC;
+let funcs = usb.FunctionType.HDC;
 usb.setCurrentFunctions(funcs).then(() => {
     console.info('usb setCurrentFunctions successfully.');
 }).catch(err => {
diff --git a/zh-cn/application-dev/reference/apis/js-apis-util.md b/zh-cn/application-dev/reference/apis/js-apis-util.md
index a556dac2502d4c7de69cedd050a590491b15707e..b6d01f5737ab9e79960a9153f99edc33758ca4ee 100755
--- a/zh-cn/application-dev/reference/apis/js-apis-util.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-util.md
@@ -547,7 +547,7 @@ TextEncoder的构造函数。
 
 | 参数名 | 类型 | 必填 | 说明 |
 | ----- | ---- | ---- | ---- |
-| encoding | string | 否 | 编码格式 |
+| encoding | string | 否 | 编码格式，默认值为'utf-8'。 |
 
 **示例：**
 
@@ -567,7 +567,7 @@ encodeInto(input?: string): Uint8Array
 
 | 参数名 | 类型   | 必填 | 说明               |
 | ------ | ------ | ---- | ------------------ |
-| input  | string | 否   | 需要编码的字符串。 |
+| input  | string | 否   | 需要编码的字符串，默认值是空字符串。 |
 
 **返回值：**
 
@@ -665,7 +665,7 @@ encode(input?: string): Uint8Array
 
 | 参数名 | 类型 | 必填 | 说明 |
 | -------- | -------- | -------- | -------- |
-| input | string | 否 | 需要编码的字符串。 |
+| input | string | 否 | 需要编码的字符串，默认值是空字符串。 |
 
 **返回值：**
 
@@ -1646,18 +1646,18 @@ compareTo(other: ScopeComparable): boolean;
 
 ```js
 class Temperature{
-    constructor(value){
-       // 当使用ts语言开发时，需要补充以下代码：
-       // private readonly _temp: Temperature;
+    // 当使用ArkTS语言开发时，需要补充以下代码：
+    // private readonly _temp: Temperature;
+    constructor(value) {
        this._temp = value;
     }
-    compareTo(value){
+    compareTo(value) {
        return this._temp >= value.getTemp();
     }
-    getTemp(){
+    getTemp() {
        return this._temp;
     }
-    toString(){
+    toString() {
        return this._temp.toString();
     }
 }
diff --git a/zh-cn/application-dev/reference/apis/js-apis-wantAgent.md b/zh-cn/application-dev/reference/apis/js-apis-wantAgent.md
index 26b5437c7380644a97c46487d9c3d4ab96892acf..5f33db0ad4a1acb5c53d88b8b14aabfe557477ef 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-wantAgent.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-wantAgent.md
@@ -20,6 +20,8 @@ getWant(agent: WantAgent, callback: AsyncCallback\<Want\>): void
 
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Core
 
+**系统API**：该接口为系统接口，三方应用不支持调用。
+
 **参数：**
 
 | 参数名     | 类型                       | 必填 | 说明                    |
@@ -91,6 +93,8 @@ getWant(agent: WantAgent): Promise\<Want\>
 
 **系统能力**：SystemCapability.Ability.AbilityRuntime.Core
 
+**系统API**：该接口为系统接口，三方应用不支持调用。
+
 **参数：**
 
 | 参数名 | 类型          | 必填 | 说明          |
diff --git a/zh-cn/application-dev/reference/apis/js-apis-window.md b/zh-cn/application-dev/reference/apis/js-apis-window.md
index c747b38a638ef39226e778586858f36cd7360233..7f34cf090aa4d018e43b82edf927cbbd48916b68 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-window.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-window.md
@@ -232,7 +232,7 @@ import window from '@ohos.window';
 | isLayoutFullScreen<sup>7+</sup>       | boolean                   | 是   | 是   | 窗口是否为沉浸式，默认为false。true表示沉浸式；false表示非沉浸式。 |
 | focusable<sup>7+</sup>                | boolean                   | 是   | 否   | 窗口是否可聚焦，默认为true。true表示可聚焦；false表示不可聚焦。 |
 | touchable<sup>7+</sup>                | boolean                   | 是   | 否   | 窗口是否可触摸，默认为true。true表示可触摸；false表示不可触摸。 |
-| brightness                            | number                    | 是   | 是   | 屏幕亮度， 取值范围为0~1，1表示最大亮度值。                  |
+| brightness                            | number                    | 是   | 是   | 屏幕亮度， 可设置的亮度范围为0~1，其中1表示最大亮度值。如果窗口没有设置亮度值，表示亮度跟随系统，此时获取到的亮度值为-1。 |
 | dimBehindValue<sup>(deprecated)</sup> | number                    | 是   | 是   | 靠后窗口的暗度值，取值范围为0~1，1表示最暗。<br>- **说明：** 从API version 9开始废弃。<br>- 从 API version 7开始支持。 |
 | isKeepScreenOn                        | boolean                   | 是   | 是   | 屏幕是否常亮，默认为false。true表示常亮；false表示不常亮。 |
 | isPrivacyMode<sup>7+</sup>            | boolean                   | 是   | 是   | 隐私模式，默认为false。true表示模式开启；false表示模式关闭。 |
@@ -3091,6 +3091,8 @@ setWindowBrightness(brightness: number, callback: AsyncCallback&lt;void&gt;): vo
 
 设置屏幕亮度值，使用callback异步回调。
 
+当前屏幕亮度规格：窗口设置屏幕亮度生效时，控制中心不可以调整系统屏幕亮度，窗口恢复默认系统亮度之后，控制中心可以调整系统屏幕亮度。
+
 **系统能力：** SystemCapability.WindowManager.WindowManager.Core
 
 **参数：**
@@ -3132,6 +3134,8 @@ setWindowBrightness(brightness: number): Promise&lt;void&gt;
 
 设置屏幕亮度值，使用Promise异步回调。
 
+当前屏幕亮度规格：窗口设置屏幕亮度生效时，控制中心不可以调整系统屏幕亮度，窗口恢复默认系统亮度之后，控制中心可以调整系统屏幕亮度。
+
 **系统能力：** SystemCapability.WindowManager.WindowManager.Core
 
 **参数：**
@@ -5336,6 +5340,8 @@ setBrightness(brightness: number, callback: AsyncCallback&lt;void&gt;): void
 
 设置屏幕亮度值，使用callback异步回调。
 
+当前屏幕亮度规格：窗口设置屏幕亮度生效时，控制中心不可以调整系统屏幕亮度，窗口恢复默认系统亮度之后，控制中心可以调整系统屏幕亮度。
+
 > **说明：**
 > 
 > 从 API version 6开始支持，从API version 9开始废弃，推荐使用[setWindowBrightness()](#setwindowbrightness9)。
@@ -5368,6 +5374,8 @@ setBrightness(brightness: number): Promise&lt;void&gt;
 
 设置屏幕亮度值，使用Promise异步回调。
 
+当前屏幕亮度规格：窗口设置屏幕亮度生效时，控制中心不可以调整系统屏幕亮度，窗口恢复默认系统亮度之后，控制中心可以调整系统屏幕亮度。
+
 > **说明：**
 > 
 > 从 API version 6开始支持，从API version 9开始废弃，推荐使用[setWindowBrightness()](#setwindowbrightness9-1)。
diff --git a/zh-cn/application-dev/reference/apis/js-apis-xml.md b/zh-cn/application-dev/reference/apis/js-apis-xml.md
index 2eb5d5ffc8fdcf7cee88c66fad0afef595c4d109..fc17e6e4a9963a728104080f7d51108c064646cc 100644
--- a/zh-cn/application-dev/reference/apis/js-apis-xml.md
+++ b/zh-cn/application-dev/reference/apis/js-apis-xml.md
@@ -32,7 +32,7 @@ XmlSerializer的构造函数。
 
 ```js
 let arrayBuffer = new ArrayBuffer(2048);
-let thatSer = new xml.XmlSerializer(arrayBuffer,"utf-8");
+let thatSer = new xml.XmlSerializer(arrayBuffer, "utf-8");
 thatSer.setDeclaration();
 let result = '<?xml version="1.0" encoding="utf-8"?>';
 let view = new Uint8Array(arrayBuffer);
@@ -400,13 +400,9 @@ let strXml =
     '        </h:tr>' +
     '    </h:table>' +
     '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let i = 0; i < strLen; ++i) {
-    bufView[i] = strXml.charCodeAt(i);
-}
-let that = new xml.XmlPullParser(arrayBuffer, 'UTF-8');
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer, 'UTF-8');
 let str1 = '';
 function func1(name, value){
     str1 += name+':'+value;
@@ -442,13 +438,9 @@ let strXml =
             '    <todo>Work</todo>' +
             '    <todo>Play</todo>' +
             '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let tmp = 0; tmp < strLen; ++tmp) {
-    bufView[tmp] = strXml.charCodeAt(tmp);
-}
-let that = new xml.XmlPullParser(arrayBuffer);
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer);
 let arrTag = {};
 let str = "";
 let i = 0;
@@ -513,13 +505,9 @@ let strXml =
             '    <todo>Work</todo>' +
             '    <todo>Play</todo>' +
             '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let tmp = 0; tmp < strLen; ++tmp) {
-    bufView[tmp] = strXml.charCodeAt(tmp);
-}
-let that = new xml.XmlPullParser(arrayBuffer);
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer);
 let arrTag = {};
 let str = "";
 let i = 0;
@@ -560,13 +548,9 @@ let strXml =
             '    <todo>Work</todo>' +
             '    <todo>Play</todo>' +
             '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let tmp = 0; tmp < strLen; ++tmp) {
-    bufView[tmp] = strXml.charCodeAt(tmp);
-}
-let that = new xml.XmlPullParser(arrayBuffer);
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer);
 let arrTag = {};
 let str = "";
 let i = 0;
@@ -610,13 +594,9 @@ let strXml =
             '    <todo>Work</todo>' +
             '    <todo>Play</todo>' +
             '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let tmp = 0; tmp < strLen; ++tmp) {
-    bufView[tmp] = strXml.charCodeAt(tmp);
-}
-let that = new xml.XmlPullParser(arrayBuffer);
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer);
 let arrTag = {};
 let str = "";
 let i = 0;
@@ -657,13 +637,9 @@ let strXml =
             '    <todo>Work</todo>' +
             '    <todo>Play</todo>' +
             '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let tmp = 0; tmp < strLen; ++tmp) {
-    bufView[tmp] = strXml.charCodeAt(tmp);
-}
-let that = new xml.XmlPullParser(arrayBuffer);
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer);
 let arrTag = {};
 let str = "";
 let i = 0;
@@ -703,13 +679,9 @@ let strXml =
             '    <todo>Work</todo>' +
             '    <todo>Play</todo>' +
             '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let tmp = 0; tmp < strLen; ++tmp) {
-    bufView[tmp] = strXml.charCodeAt(tmp);
-}
-let that = new xml.XmlPullParser(arrayBuffer);
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer);
 let arrTag = {};
 let str = "";
 let i = 0;
@@ -749,13 +721,9 @@ let strXml =
             '    <todo>Work</todo>' +
             '    <todo>Play</todo>' +
             '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let tmp = 0; tmp < strLen; ++tmp) {
-    bufView[tmp] = strXml.charCodeAt(tmp);
-}
-let that = new xml.XmlPullParser(arrayBuffer);
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer);
 let arrTag = {};
 let str = "";
 let i = 0;
@@ -796,13 +764,9 @@ let strXml =
             '    <todo>Work</todo>' +
             '    <todo>Play</todo>' +
             '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let tmp = 0; tmp < strLen; ++tmp) {
-    bufView[tmp] = strXml.charCodeAt(tmp);
-}
-let that = new xml.XmlPullParser(arrayBuffer);
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer);
 let arrTag = {};
 let str = "";
 let i = 0;
@@ -842,13 +806,9 @@ let strXml =
             '    <todo>Work</todo>' +
             '    <todo>Play</todo>' +
             '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let tmp = 0; tmp < strLen; ++tmp) {
-    bufView[tmp] = strXml.charCodeAt(tmp);
-}
-let that = new xml.XmlPullParser(arrayBuffer);
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer);
 let arrTag = {};
 let str = "";
 let i = 0;
@@ -888,13 +848,9 @@ let strXml =
             '    <todo>Work</todo>' +
             '    <todo>Play</todo>' +
             '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let tmp = 0; tmp < strLen; ++tmp) {
-    bufView[tmp] = strXml.charCodeAt(tmp);
-}
-let that = new xml.XmlPullParser(arrayBuffer);
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer);
 let arrTag = {};
 let str = "";
 let i = 0;
@@ -933,13 +889,9 @@ let strXml =
             '    <todo>Work</todo>' +
             '    <todo>Play</todo>' +
             '</note>';
-let arrayBuffer = new ArrayBuffer(strXml.length);
-let bufView = new Uint8Array(arrayBuffer);
-let strLen = strXml.length;
-for (let tmp = 0; tmp < strLen; ++tmp) {
-    bufView[tmp] = strXml.charCodeAt(tmp);
-}
-let that = new xml.XmlPullParser(arrayBuffer);
+let textEncoder = new util.TextEncoder();
+let arrbuffer = textEncoder.encodeInto(strXml);
+let that = new xml.XmlPullParser(arrbuffer.buffer);
 let arrTag = {};
 let str = "";
 let i = 0;
diff --git a/zh-cn/application-dev/reference/arkui-ts/Readme-CN.md b/zh-cn/application-dev/reference/arkui-ts/Readme-CN.md
index 2020b9ebb6c771f623f4ab865cd916b3e62289f6..fa859bbe062c8dbb67f15fee3a880fac8b8664b6 100644
--- a/zh-cn/application-dev/reference/arkui-ts/Readme-CN.md
+++ b/zh-cn/application-dev/reference/arkui-ts/Readme-CN.md
@@ -124,6 +124,7 @@
   - [Swiper](ts-container-swiper.md)
   - [Tabs](ts-container-tabs.md)
   - [TabContent](ts-container-tabcontent.md)
+  - [WaterFlow](ts-container-waterflow.md)
 - 媒体组件
   - [Video](ts-media-components-video.md)
 - 绘制组件
diff --git a/zh-cn/application-dev/reference/arkui-ts/figures/LoadingProgress.gif b/zh-cn/application-dev/reference/arkui-ts/figures/LoadingProgress.gif
index 90d9c7bba27ef616fb6bfdea407358df25ac6f91..60d551dd3f1de3a5443bc594c5080b5692704fd0 100644
Binary files a/zh-cn/application-dev/reference/arkui-ts/figures/LoadingProgress.gif and b/zh-cn/application-dev/reference/arkui-ts/figures/LoadingProgress.gif differ
diff --git a/zh-cn/application-dev/reference/arkui-ts/figures/zh-cn_image_0000001169582302.png b/zh-cn/application-dev/reference/arkui-ts/figures/zh-cn_image_0000001169582302.png
index 4248727e91ebbd2ad2dd35211936745a8800f94c..db2eaa5d6fa3c8184bf5fe94ece002960b0d19fc 100644
Binary files a/zh-cn/application-dev/reference/arkui-ts/figures/zh-cn_image_0000001169582302.png and b/zh-cn/application-dev/reference/arkui-ts/figures/zh-cn_image_0000001169582302.png differ
diff --git a/zh-cn/application-dev/reference/arkui-ts/figures/zh-cn_image_canvas_height.png b/zh-cn/application-dev/reference/arkui-ts/figures/zh-cn_image_canvas_height.png
new file mode 100644
index 0000000000000000000000000000000000000000..589059ee8bf53b736cdadfc79ee44bbfd9d3db02
Binary files /dev/null and b/zh-cn/application-dev/reference/arkui-ts/figures/zh-cn_image_canvas_height.png differ
diff --git a/zh-cn/application-dev/reference/arkui-ts/figures/zh-cn_image_canvas_width.png b/zh-cn/application-dev/reference/arkui-ts/figures/zh-cn_image_canvas_width.png
new file mode 100644
index 0000000000000000000000000000000000000000..c9d63dc6b6ff97b2b0ff3ae4599b787db8dd096f
Binary files /dev/null and b/zh-cn/application-dev/reference/arkui-ts/figures/zh-cn_image_canvas_width.png differ
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-blank.md b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-blank.md
index 891e3964deb2a69acc23c0b6811da9bb2c3dbe16..5d32393929fa65468adbc9ffd0f656b570ea9261 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-blank.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-blank.md
@@ -1,6 +1,6 @@
 # Blank
 
-空白填充组件，在容器主轴方向上，空白填充组件具有自动填充容器空余部分的能力。仅当父组件为Row/Column时生效。
+空白填充组件，在容器主轴方向上，空白填充组件具有自动填充容器空余部分的能力。仅当父组件为Row/Column/Flex时生效。
 
 >  **说明：**
 >
@@ -50,7 +50,7 @@ struct BlankExample {
       Row() {
         Text('Bluetooth').fontSize(18)
         Blank()
-        Toggle({ type: ToggleType.Switch })
+        Toggle({ type: ToggleType.Switch }).margin({ top: 14, bottom: 14, left: 6, right: 6 })
       }.width('100%').backgroundColor(0xFFFFFF).borderRadius(15).padding({ left: 12 })
     }.backgroundColor(0xEFEFEF).padding(20)
   }
@@ -80,16 +80,16 @@ struct BlankExample {
       Row() {
         Text('Bluetooth').fontSize(18)
         Blank().color(Color.Yellow)
-        Toggle({ type: ToggleType.Switch })
+        Toggle({ type: ToggleType.Switch }).margin({ top: 14, bottom: 14, left: 6, right: 6 })
       }.backgroundColor(0xFFFFFF).borderRadius(15).padding({ left: 12 })
 
       Row() {
         Text('Bluetooth').fontSize(18)
         // 设置最小宽度为160
         Blank('160').color(Color.Yellow)
-        Toggle({ type: ToggleType.Switch })
+        Toggle({ type: ToggleType.Switch }).margin({ top: 14, bottom: 14, left: 6, right: 6 })
       }.backgroundColor(0xFFFFFF).borderRadius(15).padding({ left: 12 })
-      
+
     }.backgroundColor(0xEFEFEF).padding(20).width('100%')
   }
 }
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-image.md b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-image.md
index b0edfeca7a67fe9bf2e7091d24b3ea9ca87dc988..09680577598c2cb8ed6cd5498f2162d8af8c7e03 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-image.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-image.md
@@ -54,7 +54,7 @@ Image(src: string | PixelMap | Resource)
 >  **说明：**
 >
 >  使用快捷组合键对Image组件复制的前提是，该组件必须处于获焦状态。将Image组件的属性focusable设置为true，即可使用TAB键将焦点切换到Image组件上，再将Image组件的focusOnTouch属性设置为true，即可实现点击获焦。
->  图片设置svg图源时，支持的标签范围有限，目前支持的svg标签包括svg、rect、circle、ellipse、path、line、polyline、polygon、animate。
+>  图片设置svg图源时，支持的标签范围有限，目前支持的svg标签包括svg、rect、circle、ellipse、path、line、polyline、polygon。
 
 ### ImageInterpolation
 
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-plugincomponent.md b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-plugincomponent.md
index baf8013ab88547a5222bc1a5a1b64af25a356c67..23932ceb53958abb68389045136f508c8f263ab4 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-plugincomponent.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-plugincomponent.md
@@ -37,9 +37,9 @@ PluginComponent(value: { template: PluginComponentTemplate, data: KVObject})
 
   模板支持两种提供方式：
 * 1.使用绝对路径进行资源提供：source字段填写模板绝对路径，bundleName不需要填写。仅适用于不需要加载资源的单独模板页面，不建议使用。
-* 2.通过应用包进行资源提供：bundleName字段需要填写应用包名；source字段填写相对hap包的模板相对路径，对于多hap场景，通过相对路径&hap名称的方式进行hap包的确认。
+* 2.通过应用包进行资源提供：bundleName字段需要填写应用包名；source字段填写相对hap包的模板相对路径。
 
-  例如：{source：'ets/pages/plugin.js&plugin', bundleName:'com.example.provider'}
+  例如：{source：'ets/pages/plugin.js', bundleName:'com.example.provider'}
 
   仅对FA模型支持source字段填写AbilityName进行模板提供。
 
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-qrcode.md b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-qrcode.md
index e6e48f77ebd3b8d73f5a1a72997021cdcc2dd850..7e2ae518b46f862eeeadba35fdca9d5827d42ea6 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-qrcode.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-qrcode.md
@@ -22,7 +22,7 @@ QRCode(value: string)
 
 | 参数名 | 参数类型 | 必填 | 参数描述 |
 | -------- | -------- | -------- | -------- |
-| value | string | 是 | 二维码内容字符串。 |
+| value | string | 是 | 二维码内容字符串。最大支持256个字符，若超出，则截取前256个字符。<br/>**说明：** <br/>该字符串内容确保有效，不支持null、undefined以及空内容。 |
 
 ## 属性
 
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-slider.md b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-slider.md
index bb0dbba1047de69dd17b57e3e1244652f3617af5..081f513dc6585832ee0a22b6cbdeac93e7850db8 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-slider.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-slider.md
@@ -22,7 +22,7 @@ Slider(options?: {value?: number, min?: number, max?: number, step?: number, sty
 
 | 参数名 | 参数类型 | 必填 | 参数描述 |
 | -------- | -------- | -------- | -------- |
-| value | number | 否 | 当前进度值。<br/>默认值：0 |
+| value | number | 否 | 当前进度值。<br/>默认值：min |
 | min | number | 否 | 设置最小值。<br/>默认值：0 |
 | max | number | 否 | 设置最大值。<br/>默认值：100<br/>**说明：** <br/>min >= max异常情况，min取默认值0，max取默认值100。<br/>value不在[min, max]范围之内，取min/max，靠近min取min，靠近max取max。 |
 | step | number | 否 | 设置Slider滑动步长。<br/>默认值：1<br/>取值范围：[0.01, max]<br/>**说明：** <br/>设置小于0或百分比的值时，按默认值显示。 |
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-stepperitem.md b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-stepperitem.md
index 16eca00028f791c505086f8f54d8d305cc3e8f74..2dcd381ba8e505f7525ec7a4c7ba38838046aae6 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-stepperitem.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-stepperitem.md
@@ -28,12 +28,12 @@ StepperItem()
 
 ## ItemState枚举说明
 
-|   名称    |   值    | 描述 |
-| -------- | -------- |-------- |
-| Normal |  0  |正常状态，右侧文本按钮正常显示，可点击进入下一个StepperItem。 |
-| Disabled |  1  |不可用状态，右侧文本按钮灰度显示，不可点击进入下一个StepperItem。 |
-| Waiting |  2  | 等待状态，右侧文本按钮不显示，显示等待进度条，不可点击进入下一个StepperItem。 |
-| Skip |  3  |跳过状态，右侧文本按钮默认显示“跳过”，此时可在Stepper的onSkip回调中自定义相关逻辑。 |
+|   名称    | 描述 |
+| -------- |-------- |
+| Normal |正常状态，右侧文本按钮正常显示，可点击进入下一个StepperItem。 |
+| Disabled |不可用状态，右侧文本按钮灰度显示，不可点击进入下一个StepperItem。 |
+| Waiting | 等待状态，右侧文本按钮不显示，显示等待进度条，不可点击进入下一个StepperItem。 |
+| Skip |跳过状态，右侧文本按钮默认显示“跳过”，此时可在Stepper的onSkip回调中自定义相关逻辑。 |
 
 
 ## 示例
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-text.md b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-text.md
index c33b1c703e5b6c510b478fd509b44c3ce4543c5b..787893fd3bdce2ae341be72e2d6448eb9e3e8985 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-text.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-text.md
@@ -109,7 +109,7 @@ struct TextExample1 {
       Text('TextOverflow+maxLines').fontSize(9).fontColor(0xCCCCCC)
       // 超出maxLines截断内容展示
       Text('This is the setting of textOverflow to Clip text content This is the setting of textOverflow to None text content. This is the setting of textOverflow to Clip text content This is the setting of textOverflow to None text content.')
-        .textOverflow({ overflow: TextOverflow.None })
+        .textOverflow({ overflow: TextOverflow.Clip })
         .maxLines(1)
         .fontSize(12)
         .border({ width: 1 })
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-textpicker.md b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-textpicker.md
index ae3c675fe37090aaaea79918ea0e1240a3314b4d..af6a568d7e75d7a21e3695d89d0920c37963321b 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-textpicker.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-textpicker.md
@@ -40,7 +40,9 @@ TextPicker(options?: {range: string[]|Resource, selected?: number, value?: strin
 
 | 名称 | 描述 |
 | -------- | -------- |
-| onChange(callback:&nbsp;(value:&nbsp;string,&nbsp;index:&nbsp;number)&nbsp;=&gt;&nbsp;void) | 滑动选中TextPicker文本内容后，触发该回调。<br/>-&nbsp;value:&nbsp;当前选中项的文本。<br/>-&nbsp;index:&nbsp;当前选中项的索引值。 |
+| onAccept(callback: (value: string, index: number) => void) | 点击弹窗中的“确定”按钮时触发该回调。<br/><br/>-&nbsp;value:&nbsp;当前选中项的文本。<br/>-&nbsp;index:&nbsp;当前选中项的索引值。<br/>**说明：** <br/>该事件仅在[文本滑动选择器弹窗](ts-methods-textpicker-dialog.md)中生效。 |
+| onCancel(callback: () => void) | 点击弹窗中的“取消”按钮时触发该回调。<br/>**说明：** <br/>该事件仅在[文本滑动选择器弹窗](ts-methods-textpicker-dialog.md)中生效。 |
+| onChange(callback:&nbsp;(value:&nbsp;string,&nbsp;index:&nbsp;number)&nbsp;=&gt;&nbsp;void) | 滑动选中TextPicker文本内容后，触发该回调。<br/>-&nbsp;value:&nbsp;当前选中项的文本。<br/>**说明**：当显示文本或图片加文本列表时，value值为选中项中的文本值，当显示图片列表时，value值为空。<br/>-&nbsp;index:&nbsp;当前选中项的索引值。 |
 
 
 ## 示例
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-toggle.md b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-toggle.md
index bb1e7686a6c2f51ca662c864fca63bd5ea469a71..67e868100a5d7c1eca1c88da7db7795a3dcc19d6 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-toggle.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-basic-components-toggle.md
@@ -31,9 +31,9 @@ Toggle(options: { type: ToggleType, isOn?: boolean })
 
 | 名称       | 描述                 |
 | -------- | ---------------- |
-| Checkbox | 提供单选框样式。<br>**说明：**<br/>[通用属性margin](ts-universal-attributes-size.md)的默认值为：<br>{<br>&nbsp;top: 12 vp,<br>&nbsp;right: 12 vp,<br>&nbsp;bottom: 12 vp,<br>&nbsp;left: 12 vp<br> } |
+| Checkbox | 提供单选框样式。<br>**说明：**<br/>[通用属性margin](ts-universal-attributes-size.md)的默认值为：<br>{<br>&nbsp;top: 12 px,<br>&nbsp;right: 12 px,<br>&nbsp;bottom: 12 px,<br>&nbsp;left: 12 px<br> } |
 | Button   | 提供状态按钮样式，如果子组件有文本设置，则相应的文本内容会显示在按钮内部。       |
-| Switch   | 提供开关样式。<br>**说明：**<br/>[通用属性margin](ts-universal-attributes-size.md)默认值为：<br>{<br/>&nbsp;top: 14 vp,<br/>&nbsp;right:6 vp,<br/>&nbsp;bottom: 6 vp,<br/>&nbsp;left: 14 vp<br/> } |
+| Switch   | 提供开关样式。<br>**说明：**<br/>[通用属性margin](ts-universal-attributes-size.md)默认值为：<br>{<br/>&nbsp;top: 14 px,<br/>&nbsp;right:6 px,<br/>&nbsp;bottom: 6 px,<br/>&nbsp;left: 14 px<br/> } |
 
 ## 属性
 
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-canvasrenderingcontext2d.md b/zh-cn/application-dev/reference/arkui-ts/ts-canvasrenderingcontext2d.md
index 62073483bec9e914dfd59535d99b132519727ef7..c0b297e0fd526f06e43498f03b71ac6d6db91409 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-canvasrenderingcontext2d.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-canvasrenderingcontext2d.md
@@ -57,6 +57,8 @@ RenderingContextSettings(antialias?: boolean)
 | [shadowOffsetX](#shadowoffsetx)                       | number                                                       | 设置绘制阴影时和原有对象的水平偏移值。<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。 |
 | [shadowOffsetY](#shadowoffsety)                       | number                                                       | 设置绘制阴影时和原有对象的垂直偏移值。<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。 |
 | [imageSmoothingEnabled](#imagesmoothingenabled)       | boolean                                                      | 用于设置绘制图片时是否进行图像平滑度调整，true为启用，false为不启用。 <br/>默认值：true<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。 |
+| [height](#height)                                     | number                                                       | 组件高度。 <br/>单位：vp<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。 |
+| [width](#width)                                       | number                                                       | 组件宽度。 <br/>单位：vp<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。 |
 
 > **说明：**
 >
@@ -652,6 +654,68 @@ struct ImageSmoothingEnabled {
 ![zh-cn_image_0000001238712415](figures/zh-cn_image_0000001238712415.png)
 
 
+### height
+
+```ts
+// xxx.ets
+@Entry
+@Component
+struct HeightExample {
+  private settings: RenderingContextSettings = new RenderingContextSettings(true)
+  private context: CanvasRenderingContext2D = new CanvasRenderingContext2D(this.settings)
+
+  build() {
+    Flex({ direction: FlexDirection.Column, alignItems: ItemAlign.Center, justifyContent: FlexAlign.Center }) {
+      Canvas(this.context)
+        .width(300)
+        .height(300)
+        .backgroundColor('#ffff00')
+        .onReady(() => {
+          let h = this.context.height
+          let w = this.context.width
+          this.context.fillRect(0, 0, 300, h/2)
+        })
+    }
+    .width('100%')
+    .height('100%')
+  }
+}
+```
+
+![zh-cn_image_canvas_height](figures/zh-cn_image_canvas_height.png)
+
+
+### width
+
+```ts
+// xxx.ets
+@Entry
+@Component
+struct WidthExample {
+  private settings: RenderingContextSettings = new RenderingContextSettings(true)
+  private context: CanvasRenderingContext2D = new CanvasRenderingContext2D(this.settings)
+
+  build() {
+    Flex({ direction: FlexDirection.Column, alignItems: ItemAlign.Center, justifyContent: FlexAlign.Center }) {
+      Canvas(this.context)
+        .width(300)
+        .height(300)
+        .backgroundColor('#ffff00')
+        .onReady(() => {
+          let h = this.context.height
+          let w = this.context.width
+          this.context.fillRect(0, 0, w/2, 300)
+        })
+    }
+    .width('100%')
+    .height('100%')
+  }
+}
+```
+
+![zh-cn_image_canvas_width](figures/zh-cn_image_canvas_width.png)
+
+
 ## 方法
 
 
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-components-canvas-canvasgradient.md b/zh-cn/application-dev/reference/arkui-ts/ts-components-canvas-canvasgradient.md
index bb1ab8f3b2721ea789e51b23ecdb0aa4b3611c80..a817a3386b28041f6637570e58cbc34493f8ffe3 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-components-canvas-canvasgradient.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-components-canvas-canvasgradient.md
@@ -22,7 +22,7 @@ addColorStop(offset: number, color: string): void
 | 参数     | 类型     | 必填   | 默认值       | 描述                           |
 | ------ | ------ | ---- | --------- | ---------------------------- |
 | offset | number | 是    | 0         | 设置渐变点距离起点的位置占总体长度的比例，范围为0到1。 |
-| color  | string | 是    | '#ffffff' | 设置渐变的颜色。                     |
+| color  | string | 是    | '#ffffff' | 设置渐变的颜色。颜色格式参考[ResourceColor](ts-types.md#resourcecolor)中string类型说明                     |
 
 
 **示例：**
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-components-summary.md b/zh-cn/application-dev/reference/arkui-ts/ts-components-summary.md
index 1becf8095e670afa88849f400616a5183be6afb8..6504c28f9530a96cc49e936c6f884e7859e12187 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-components-summary.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-components-summary.md
@@ -69,6 +69,12 @@
 - [Swiper](ts-container-swiper.md)
 
     滑块视图容器组件，提供子组件滑动轮播显示的能力。
+- [WaterFlow](ts-container-waterflow.md)
+
+    瀑布流容器组件，由“行”和“列”分割的单元格所组成，通过容器自身的排列规则，将不同大小的“项目”自上而下，如瀑布般紧密布局。
+- [FlowItem](ts-container-flowitem.md)
+
+    瀑布流组件WaterFlow的子组件，用来展示瀑布流具体item。
 
 
 ## 导航
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-container-flowitem.md b/zh-cn/application-dev/reference/arkui-ts/ts-container-flowitem.md
new file mode 100644
index 0000000000000000000000000000000000000000..4628ea7bb51de907d3b1ace994e25c80d1e100b3
--- /dev/null
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-container-flowitem.md
@@ -0,0 +1,31 @@
+# FlowItem
+
+
+[瀑布流组件](ts-container-waterflow.md)的子组件，用来展示瀑布流具体item。
+
+
+> **说明：**
+>
+> 该组件从API Version 9开始支持。后续版本如有新增内容，则采用上角标单独标记该内容的起始版本。
+
+
+## 子组件
+
+
+支持单个子组件。
+
+
+## 接口
+
+FlowItem()
+
+使用该接口来创建瀑布流子组件。
+
+
+## 属性
+
+无
+
+## 示例
+
+详见[瀑布流组件示例](ts-container-waterflow.md#示例)。
\ No newline at end of file
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-container-scroll.md b/zh-cn/application-dev/reference/arkui-ts/ts-container-scroll.md
index 1262713d8412a0447a225794d33fae1da65c683d..1f86949d0ec12e39742e9fa6ed74fefed8191fcd 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-container-scroll.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-container-scroll.md
@@ -61,7 +61,7 @@ Scroll(scroller?: Scroller)
 
 ## Scroller
 
-可滚动容器组件的控制器，可以将此组件绑定至容器组件，然后通过它控制容器组件的滚动，同一个控制器不可以控制多个容器组件，目前支持绑定到List、Scroll、ScrollBar、Grid上。
+可滚动容器组件的控制器，可以将此组件绑定至容器组件，然后通过它控制容器组件的滚动，同一个控制器不可以控制多个容器组件，目前支持绑定到List、Scroll、ScrollBar、Grid、WaterFlow上。
 
 
 ### 导入对象
@@ -139,7 +139,7 @@ scrollToIndex(value: number): void
 
 >  **说明：**
 >
->  仅支持Grid、List组件。
+>  仅支持Grid、List、WaterFlow组件。
 
 **参数：**
 
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-container-swiper.md b/zh-cn/application-dev/reference/arkui-ts/ts-container-swiper.md
index 28e18abef3a2dd1404de99c5ca5ba65ee90f2ee4..38863585ac5ba858585b233413aeb51c665f8642 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-container-swiper.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-container-swiper.md
@@ -42,7 +42,7 @@ Swiper(controller?: SwiperController)
 | vertical                    | boolean                                  | 是否为纵向滑动。<br/>默认值：false                                 |
 | itemSpace                   | number&nbsp;\|&nbsp;string          | 设置子组件与子组件之间间隙。<br/>默认值：0<br/>**说明：** <br/>不支持设置百分比。 |
 | displayMode                 | SwiperDisplayMode                        | 主轴方向上元素排列的模式，优先以displayCount设置的个数显示，displayCount未设置时本属性生效。<br/>默认值：SwiperDisplayMode.Stretch |
-| cachedCount<sup>8+</sup>    | number                                   | 设置预加载子组件个数。<br/>默认值：1                              |
+| cachedCount<sup>8+</sup>    | number                                   | 设置预加载子组件个数。<br/>默认值：1<br/>**说明：** <br/>cachedCount已经做了预加载的优化，不建议与[LazyForEach](../../quick-start/arkts-rendering-control-lazyforeach.md)一起使用。 |
 | disableSwipe<sup>8+</sup>   | boolean                                  | 禁用组件滑动切换功能。<br/>默认值：false                              |
 | curve<sup>8+</sup>          | [Curve](ts-appendix-enums.md#curve)  \| string | 设置Swiper的动画曲线，默认为淡入淡出曲线，常用曲线参考[Curve枚举说明](ts-appendix-enums.md#curve)，也可以通过[插值计算](../apis/js-apis-curve.md)模块提供的接口创建自定义的插值曲线对象。<br/>默认值：Curve.Ease |
 | indicatorStyle<sup>8+</sup> | {<br/>left?:&nbsp;[Length](ts-types.md#length),<br/>top?:&nbsp;[Length](ts-types.md#length),<br/>right?:&nbsp;[Length](ts-types.md#length),<br/>bottom?:&nbsp;[Length](ts-types.md#length),<br/>size?:&nbsp;[Length](ts-types.md#length),<br/>mask?:&nbsp;boolean,<br/>color?:&nbsp;[ResourceColor](ts-types.md),<br/>selectedColor?:&nbsp;[ResourceColor](ts-types.md)<br/>} | 设置导航点样式：<br/>\- left: 设置导航点距离Swiper组件左边的距离。<br/>\- top: 设置导航点距离Swiper组件顶部的距离。<br/>\- right: 设置导航点距离Swiper组件右边的距离。<br/>\- bottom: 设置导航点距离Swiper组件底部的距离。<br/>\- size: 设置导航点的直径。<br/>\- mask: 设置是否显示导航点蒙层样式。<br/>\- color: 设置导航点的颜色。<br/>\- selectedColor: 设置选中的导航点的颜色。 |
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-container-waterflow.md b/zh-cn/application-dev/reference/arkui-ts/ts-container-waterflow.md
new file mode 100644
index 0000000000000000000000000000000000000000..fed88989ee0322121956030cfb2f1523cd52d3bd
--- /dev/null
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-container-waterflow.md
@@ -0,0 +1,296 @@
+# WaterFlow
+
+
+瀑布流容器，由“行”和“列”分割的单元格所组成，通过容器自身的排列规则，将不同大小的“项目”自上而下，如瀑布般紧密布局。
+
+
+> **说明：**
+>
+> 该组件从API Version 9 开始支持。后续版本如有新增内容，则采用上角标单独标记该内容的起始版本。
+
+
+## 子组件
+
+
+包含[FlowItem](ts-container-flowitem.md)子组件。
+
+>  **说明：**
+>
+>  WaterFlow子组件的visibility属性设置为None时不显示，但依然会占用子组件对应的网格。
+
+## 接口
+
+
+WaterFlow(options?: {footer?: CustomBuilder, scroller?: Scroller})
+
+**参数：**
+
+| 参数名     | 参数类型                                        | 必填 | 参数描述                                     |
+| ---------- | ----------------------------------------------- | ------ | -------------------------------------------- |
+| footer |  [CustomBuilder](ts-types.md#custombuilder8) | 否   | 设置WaterFlow尾部组件。  |
+| scroller | [Scroller](ts-container-scroll.md#scroller) | 否   | 可滚动组件的控制器，与可滚动组件绑定。<br/>目前瀑布流仅支持Scroller组件的scrollToIndex接口。 |
+
+
+## 属性
+
+
+除支持[通用属性](ts-universal-attributes-size.md)外，还支持以下属性：
+
+| 名称 | 参数类型 | 描述 |
+| -------- | -------- | -------- |
+| columnsTemplate | string | 设置当前瀑布流组件布局列的数量，不设置时默认1列。<br/>例如, '1fr 1fr 2fr' 是将父组件分3列，将父组件允许的宽分为4等份，第一列占1份，第二列占1份，第三列占2份。并支持[auto-fill](#auto-fill说明)。<br>默认值：'1fr' |
+| rowsTemplate | string | 设置当前瀑布流组件布局行的数量，不设置时默认1行。<br/>例如, '1fr 1fr 2fr'是将父组件分三行，将父组件允许的高分为4等份，第一行占1份，第二行占一份，第三行占2份。并支持[auto-fill](#auto-fill说明)。<br/>默认值：'1fr' |
+| itemConstraintSize | [ConstraintSizeOptions](ts-types.md#constraintsizeoptions) | 设置约束尺寸，子组件布局时，进行尺寸范围限制。               |
+| columnsGap | Length |设置列与列的间距。 <br>默认值：0|
+| rowsGap | Length |设置行与行的间距。<br> 默认值：0|
+| layoutDirection | [FlexDirection](ts-appendix-enums.md#flexdirection) |设置布局的主轴方向。<br/>默认值：FlexDirection.Column|
+
+layoutDirection优先级高于rowsTemplate和columnsTemplate。根据layoutDirection设置情况，分为以下三种设置模式:
+
+- layoutDirection设置纵向布局（FlexDirection.Column 或 FlexDirection.ColumnReverse）
+
+	此时columnsTemplate有效（如果未设置，取默认值）。例如columnsTemplate设置为"1fr 1fr"、rowsTemplate设置为"1fr 1fr 1fr"时，瀑布流组件纵向布局，辅轴均分成横向2列。
+
+- layoutDirection设置横向布局（FlexDirection.Row 或 FlexDirection.RowReverse）
+
+	此时rowsTemplate有效（如果未设置，取默认值）。例如columnsTemplate设置为"1fr 1fr"、rowsTemplate设置为"1fr 1fr 1fr"时，瀑布流组件横向布局，辅轴均分成纵向3列。
+
+- layoutDirection未设置布局方向
+
+	布局方向为layoutDirection的默认值：FlexDirection.Column，此时columnsTemplate有效。例如columnsTemplate设置为"1fr 1fr"、rowsTemplate设置为"1fr 1fr 1fr"时，瀑布流组件纵向布局，辅轴均分成横向2列。
+
+## 事件
+
+
+除支持[通用事件](ts-universal-events-click.md)外，还支持以下事件：
+
+
+| 名称 | 功能描述 |
+| -------- | -------- |
+| onReachStart(event: () => void) | 瀑布流组件到达起始位置时触发。 |
+| onReachEnd(event: () => void)   | 瀑布流组件到底末尾位置时触发。 |
+
+
+## auto-fill说明
+
+WaterFlow的columnsTemplate、rowsTemplate属性的auto-fill仅支持以下格式：
+
+```css
+repeat(auto-fill, track-size)
+```
+
+其中repeat、auto-fill为关键字。track-size为行高或者列宽，支持的单位包括px、vp、%或有效数字，track-size至少包括一个有效行高或者列宽。
+
+
+## 示例
+
+
+```ts
+// WaterFlowDataSource.ets
+
+// 实现IDataSource接口的对象，用于瀑布流组件加载数据
+export class WaterFlowDataSource implements IDataSource {
+
+  private dataArray: number[] = []
+  private listeners: DataChangeListener[] = []
+
+  constructor() {
+      for (let i = 0; i < 100; i++) {
+          this.dataArray.push(i)
+      }
+  }
+
+  // 获取索引对应的数据
+  public getData(index: number): any {
+      return this.dataArray[index]
+  }
+
+  // 通知控制器数据重新加载
+  notifyDataReload(): void {
+      this.listeners.forEach(listener => {
+          listener.onDataReloaded()
+      })
+  }
+
+  // 通知控制器数据增加
+  notifyDataAdd(index: number): void {
+      this.listeners.forEach(listener => {
+          listener.onDataAdded(index)
+      })
+  }
+
+  // 通知控制器数据变化
+  notifyDataChange(index: number): void {
+      this.listeners.forEach(listener => {
+          listener.onDataChanged(index)
+      })
+  }
+
+  // 通知控制器数据删除
+  notifyDataDelete(index: number): void {
+      this.listeners.forEach(listener => {
+          listener.onDataDeleted(index)
+      })
+  }
+
+  // 通知控制器数据位置变化
+  notifyDataMove(from: number, to: number): void {
+      this.listeners.forEach(listener => {
+          listener.onDataMoved(from, to)
+      })
+  }
+
+  // 获取数据总数
+  public totalCount(): number {
+      return this.dataArray.length
+  }
+
+  // 注册改变数据的控制器
+  registerDataChangeListener(listener: DataChangeListener): void {
+      if (this.listeners.indexOf(listener) < 0) {
+          this.listeners.push(listener)
+      }
+  }
+
+  // 注销改变数据的控制器
+  unregisterDataChangeListener(listener: DataChangeListener): void {
+      const pos = this.listeners.indexOf(listener)
+      if (pos >= 0) {
+          this.listeners.splice(pos, 1)
+      }
+  }
+
+  // 增加数据
+  public Add1stItem(): void {
+      this.dataArray.splice(0, 0, this.dataArray.length)
+      this.notifyDataAdd(0)
+  }
+
+  // 在数据尾部增加一个元素
+  public AddLastItem(): void {
+      this.dataArray.splice(this.dataArray.length, 0, this.dataArray.length)
+      this.notifyDataAdd(this.dataArray.length-1)
+  }
+
+  // 在指定索引位置增加一个元素
+  public AddItem(index: number): void {
+      this.dataArray.splice(index, 0, this.dataArray.length)
+      this.notifyDataAdd(index)
+  }
+
+  // 删除第一个元素
+  public Delete1stItem(): void {
+      this.dataArray.splice(0, 1)
+      this.notifyDataDelete(0)
+  }
+
+  // 删除第二个元素
+  public Delete2ndItem(): void {
+      this.dataArray.splice(1, 1)
+      this.notifyDataDelete(1)
+  }
+
+  // 删除最后一个元素
+  public DeleteLastItem(): void {
+      this.dataArray.splice(-1, 1)
+      this.notifyDataDelete(this.dataArray.length)
+  }
+
+  // 重新加载数据
+  public Reload(): void {
+      this.dataArray.splice(1, 1)
+      this.dataArray.splice(3, 2)
+      this.notifyDataReload()
+  }
+}
+```
+
+```ts
+// WaterflowDemo.ets
+import { WaterFlowDataSource } from './WaterFlowDataSource'
+
+@Entry
+@Component
+struct WaterflowDemo {
+  @State minSize: number = 50
+  @State maxSize: number = 100
+  @State fontSize: number = 24
+  @State colors: number[] = [0xFFC0CB, 0xDA70D6, 0x6B8E23, 0x6A5ACD, 0x00FFFF, 0x00FF7F]
+  scroller: Scroller = new Scroller()
+  datasource: WaterFlowDataSource = new WaterFlowDataSource()
+  private itemWidthArray: number[] = []
+  private itemHeightArray: number[] = []
+
+  // 计算flow item宽/高  
+  getSize() {
+    let ret = Math.floor(Math.random() * this.maxSize)
+    return (ret > this.minSize ? ret : this.minSize)
+  }
+
+  // 保存flow item宽/高   
+  getItemSizeArray() {
+    for (let i = 0; i < 100; i++) {
+      this.itemWidthArray.push(this.getSize())
+      this.itemHeightArray.push(this.getSize())
+    }
+  }
+    
+  aboutToAppear() {
+    this.getItemSizeArray()
+  }
+    
+  @Builder itemFoot() {
+    Column() {
+      Text(`Footer`)
+        .fontSize(10)
+        .backgroundColor(Color.Red)
+        .width(50)
+        .height(50)
+        .align(Alignment.Center)
+        .margin({ top: 2 })
+    }
+  }
+
+  build() {
+    Column({ space: 2 }) {
+      WaterFlow({ footer: this.itemFoot.bind(this), scroller: this.scroller }) {
+        LazyForEach(this.datasource, (item: number) => {
+          FlowItem() {
+            Column() {
+              Text("N" + item).fontSize(12).height('16')
+              Image('res/waterFlowTest(' + item % 5 + ').jpg')
+                .objectFit(ImageFit.Fill)
+                .width('100%')
+                .layoutWeight(1)
+            }
+          }
+          .width(this.itemWidthArray[item])
+          .height(this.itemHeightArray[item])
+          .backgroundColor(this.colors[item % 5])
+        }, item => item)
+      }
+      .columnsTemplate("1fr 1fr 1fr 1fr")
+      .itemConstraintSize({
+        minWidth: 0,
+        maxWidth: '100%',
+        minHeight: 0,
+        maxHeight: '100%'
+      })
+      .columnsGap(10)
+      .rowsGap(5)
+      .onReachStart(() => {
+        console.info("onReachStart")
+      })
+      .onReachEnd(() => {
+        console.info("onReachEnd")
+      })
+      .backgroundColor(0xFAEEE0)
+      .width('100%')
+      .height('80%')
+      .layoutDirection(FlexDirection.Column)
+    }
+  }
+}
+```
+
+![zh-cn_image_WaterFlow.gif](figures/waterflow.gif)
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-media-components-video.md b/zh-cn/application-dev/reference/arkui-ts/ts-media-components-video.md
index 722d551917a357b060084c9acecb33df0d3c03b5..393510966ab51178698288fa67f7498f97f340ca 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-media-components-video.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-media-components-video.md
@@ -24,9 +24,9 @@ Video(value: {src?: string | Resource, currentProgressRate?: number | string | P
 
 | 参数名              | 参数类型                                                     | 必填 | 参数描述                                                     |
 | ------------------- | ------------------------------------------------------------ | ---- | ------------------------------------------------------------ |
-| src                 | string \| [Resource](ts-types.md)                            | 否   | 视频播放源的路径，支持本地视频路径和网络路径。<br>支持在resources下面的video或rawfile文件夹里放置媒体资源。<br>支持dataability://的路径前缀，用于访问通过Data Ability提供的视频路径，具体路径信息详见 [DataAbility说明](../../application-models/dataability-overview.md)。<br/>**说明：**<br/>视频支持的格式是：mp4、mkv、webm、TS。 |
+| src                 | string \| [Resource](ts-types.md)                            | 否   | 视频播放源的路径，支持本地视频路径和网络路径。<br>支持在resources下面的video或rawfile文件夹里放置媒体资源。<br>支持dataability://的路径前缀，用于访问通过Data Ability提供的视频路径，具体路径信息详见 [DataAbility说明](../../application-models/dataability-overview.md)。<br/>- 支持file:///data/storage路径前缀的字符串，用于读取应用沙箱路径内的资源。需要保证目录包路径下的文件有可读权限。<br/>**说明：**<br/>视频支持的格式是：mp4、mkv、webm、TS。 |
 | currentProgressRate | number&nbsp;\|&nbsp;string&nbsp;\|&nbsp;PlaybackSpeed<sup>8+</sup> | 否   | 视频播放倍速。<br/>**说明：**<br/>number取值仅支持：0.75，1.0，1.25，1.75，2.0。<br/>默认值：1.0 \| PlaybackSpeed.Speed_Forward_1_00_X |
-| previewUri          | string&nbsp;\|PixelMap&nbsp;\|&nbsp;[Resource](ts-types.md)  | 否   | 视频未播放时的预览图片路径。（暂不支持PixelMap类型）         |
+| previewUri          | string&nbsp;\|PixelMap&nbsp;\|&nbsp;[Resource](ts-types.md)  | 否   | 视频未播放时的预览图片路径。                                 |
 | controller          | [VideoController](#videocontroller)                          | 否   | 设置视频控制器。                                             |
 
 ## PlaybackSpeed<sup>8+</sup>枚举说明
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-pixel-units.md b/zh-cn/application-dev/reference/arkui-ts/ts-pixel-units.md
index d2de0f74094efb91025691580bef33c1e9e954b8..0e1e2016c6be59f061970aecd5203858aab30718 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-pixel-units.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-pixel-units.md
@@ -3,11 +3,11 @@
 为开发者提供4种像素单位，框架采用vp为基准数据单位。
 
 
-| 名称   | 描述                                       |
-| ---- | ---------------------------------------- |
-| px   | 屏幕物理像素单位。                                |
-| vp   | 屏幕密度相关像素，根据屏幕像素密度转换为屏幕物理像素，当数值不带单位时，默认单位vp。 |
-| fp   | 字体像素，与vp类似适用屏幕密度变化，随系统字体大小设置变化。          |
+| 名称 | 描述                                                         |
+| ---- | ------------------------------------------------------------ |
+| px   | 屏幕物理像素单位。                                           |
+| vp   | 屏幕密度相关像素，根据屏幕像素密度转换为屏幕物理像素，当数值不带单位时，默认单位vp。在实际宽度为1440物理像素的屏幕上，1vp约等于3px。 |
+| fp   | 字体像素，与vp类似适用屏幕密度变化，随系统字体大小设置变化。 |
 | lpx  | 视窗逻辑像素单位，lpx单位为实际屏幕宽度与逻辑宽度（通过designWidth配置）的比值，designWidth默认值为720。当designWidth为720时，在实际宽度为1440物理像素的屏幕上，1lpx为2px大小。 |
 
 
@@ -37,33 +37,71 @@ struct Example {
       Flex({ wrap: FlexWrap.Wrap }) {
         Column() {
           Text("width(220)")
-            .width(220).height(40).backgroundColor(0xF9CF93)
-            .textAlign(TextAlign.Center).fontColor(Color.White).fontSize('12vp')
+            .width(220)
+            .height(40)
+            .backgroundColor(0xF9CF93)
+            .textAlign(TextAlign.Center)
+            .fontColor(Color.White)
+            .fontSize('12vp')
         }.margin(5)
+
         Column() {
           Text("width('220px')")
-            .width('220px').height(40).backgroundColor(0xF9CF93)
-            .textAlign(TextAlign.Center).fontColor(Color.White)
+            .width('220px')
+            .height(40)
+            .backgroundColor(0xF9CF93)
+            .textAlign(TextAlign.Center)
+            .fontColor(Color.White)
         }.margin(5)
+
         Column() {
           Text("width('220vp')")
-            .width('220vp').height(40).backgroundColor(0xF9CF93)
-            .textAlign(TextAlign.Center).fontColor(Color.White).fontSize('12vp')
+            .width('220vp')
+            .height(40)
+            .backgroundColor(0xF9CF93)
+            .textAlign(TextAlign.Center)
+            .fontColor(Color.White)
+            .fontSize('12vp')
         }.margin(5)
+
         Column() {
           Text("width('220lpx') designWidth:720")
-            .width('220lpx').height(40).backgroundColor(0xF9CF93)
-            .textAlign(TextAlign.Center).fontColor(Color.White).fontSize('12vp')
+            .width('220lpx')
+            .height(40)
+            .backgroundColor(0xF9CF93)
+            .textAlign(TextAlign.Center)
+            .fontColor(Color.White)
+            .fontSize('12vp')
         }.margin(5)
+
         Column() {
           Text("width(vp2px(220) + 'px')")
-            .width(vp2px(220) + 'px').height(40).backgroundColor(0xF9CF93)
-            .textAlign(TextAlign.Center).fontColor(Color.White).fontSize('12vp')
+            .width(vp2px(220) + 'px')
+            .height(40)
+            .backgroundColor(0xF9CF93)
+            .textAlign(TextAlign.Center)
+            .fontColor(Color.White)
+            .fontSize('12vp')
         }.margin(5)
+
         Column() {
           Text("fontSize('12fp')")
-            .width(220).height(40).backgroundColor(0xF9CF93)
-            .textAlign(TextAlign.Center).fontColor(Color.White).fontSize('12fp')
+            .width(220)
+            .height(40)
+            .backgroundColor(0xF9CF93)
+            .textAlign(TextAlign.Center)
+            .fontColor(Color.White)
+            .fontSize('12fp')
+        }.margin(5)
+
+        Column() {
+          Text("width(px2vp(220))")
+            .width(px2vp(220))
+            .height(40)
+            .backgroundColor(0xF9CF93)
+            .textAlign(TextAlign.Center)
+            .fontColor(Color.White)
+            .fontSize('12fp')
         }.margin(5)
       }.width('100%')
     }
diff --git a/zh-cn/application-dev/reference/arkui-ts/ts-transition-animation-component.md b/zh-cn/application-dev/reference/arkui-ts/ts-transition-animation-component.md
index 27e49abebea9cec1e379b5ff2168fb034e819dff..7952f69866714bb7337b17f6543250491db42991 100644
--- a/zh-cn/application-dev/reference/arkui-ts/ts-transition-animation-component.md
+++ b/zh-cn/application-dev/reference/arkui-ts/ts-transition-animation-component.md
@@ -19,10 +19,10 @@
 | 参数名称 | 参数类型 | 必填 | 参数描述 |
 | -------- | -------- | -------- | -------- |
 | type | [TransitionType](ts-appendix-enums.md#transitiontype)  | 否 | 默认包括组件新增和删除。<br/>默认值：TransitionType.All<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。<br/>**说明：**<br/>不指定Type时说明插入删除使用同一种效果。 |
-| opacity | number | 否 | 设置组件转场时的透明度效果，为插入时起点和删除时终点的值。<br/>默认值：1<br/>取值范围： [0, 1]<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。<br/>**说明：** <br/>设置小于0的值时，按值为0处理；设置大于1的值时，按值为1处理。 |
+| opacity | number | 否 | 设置组件转场时的透明度效果，为插入时起点和删除时终点的值。<br/>默认值：1<br/>取值范围： [0, 1]<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。<br/>**说明：** <br/>设置小于0或大于1的非法值时，按1处理。 |
 | translate | {<br/>x?&nbsp;:&nbsp;number&nbsp;\|&nbsp;string,<br/>y?&nbsp;:&nbsp;number&nbsp;\|&nbsp;string,<br/>z?&nbsp;:&nbsp;number&nbsp;\|&nbsp;string<br/>} | 否 | 设置组件转场时的平移效果，为插入时起点和删除时终点的值。<br/>-x：横向的平移距离。<br/>-y：纵向的平移距离。<br/>-z：竖向的平移距离。<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。 |
 | scale | {<br/>x?&nbsp;:&nbsp;number,<br/>y?&nbsp;:&nbsp;number,<br/>z?&nbsp;:&nbsp;number,<br/>centerX?&nbsp;:&nbsp;number&nbsp;\|&nbsp;string,<br/>centerY?&nbsp;:&nbsp;number&nbsp;\|&nbsp;string<br/>} | 否 | 设置组件转场时的缩放效果，为插入时起点和删除时终点的值。<br/>-x：横向放大倍数（或缩小比例）。<br/>-y：纵向放大倍数（或缩小比例）。<br/>-z：竖向放大倍数（或缩小比例）。<br/>-&nbsp;centerX、centerY指缩放中心点，centerX和centerY默认值是"50%"。<br/>-&nbsp;中心点为0时，默认的是组件的左上角。<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。 |
-| rotate | {<br/>x?:&nbsp;number,<br/>y?:&nbsp;number,<br/>z?:&nbsp;number,<br/>angle?:&nbsp;number&nbsp;\|&nbsp;string,<br/>centerX?:&nbsp;number&nbsp;\|&nbsp;string,<br/>centerY?:&nbsp;number&nbsp;\|&nbsp;string<br/>} | 否 | 设置组件转场时的旋转效果，为插入时起点和删除时终点的值。<br/>-x：横向的旋转向量。<br/>-y：纵向的旋转向量。<br/>-z：竖向的旋转向量。<br/>-&nbsp;centerX,centerY指旋转中心点，centerX和centerY默认值是"50%"。<br/>-&nbsp;中心点为（0，0）时，默认的是组件的左上角。<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。 |
+| rotate | {<br/>x?:&nbsp;number,<br/>y?:&nbsp;number,<br/>z?:&nbsp;number,<br/>angle:&nbsp;number&nbsp;\|&nbsp;string,<br/>centerX?:&nbsp;number&nbsp;\|&nbsp;string,<br/>centerY?:&nbsp;number&nbsp;\|&nbsp;string<br/>} | 否 | 设置组件转场时的旋转效果，为插入时起点和删除时终点的值。<br/>-x：横向的旋转向量。<br/>-y：纵向的旋转向量。<br/>-z：竖向的旋转向量。<br/>-&nbsp;centerX,centerY指旋转中心点，centerX和centerY默认值是"50%"。<br/>-&nbsp;中心点为（0，0）时，默认的是组件的左上角。<br/>从API version 9开始，该接口支持在ArkTS卡片中使用。 |
 
 
 ## 示例
diff --git a/zh-cn/application-dev/reference/errorcodes/Readme-CN.md b/zh-cn/application-dev/reference/errorcodes/Readme-CN.md
index df23a3f911158d52c7bd40f583c8df8e242c3d47..7564ae451eb572f2be20b109ab4f643223fa4ca9 100644
--- a/zh-cn/application-dev/reference/errorcodes/Readme-CN.md
+++ b/zh-cn/application-dev/reference/errorcodes/Readme-CN.md
@@ -55,7 +55,6 @@
   - [网络连接管理错误码](errorcode-net-connection.md)
   - [以太网连接错误码](errorcode-net-ethernet.md)
   - [网络共享错误码](errorcode-net-sharing.md)
-  - [策略管理错误码](errorcode-net-policy.md)
 - 通信与连接
   - [NFC错误码](errorcode-nfc.md)
   - [RPC错误码](errorcode-rpc.md)
diff --git a/zh-cn/application-dev/reference/errorcodes/errorcode-net-policy.md b/zh-cn/application-dev/reference/errorcodes/errorcode-net-policy.md
deleted file mode 100644
index 0c54931590be55a6ded4df980f07293938c14dfe..0000000000000000000000000000000000000000
--- a/zh-cn/application-dev/reference/errorcodes/errorcode-net-policy.md
+++ /dev/null
@@ -1,63 +0,0 @@
-# 策略管理错误码
-
-> **说明：**
->
-> 以下仅介绍本模块特有错误码，通用错误码请参考[通用错误码说明文档](errorcode-universal.md)。
-
-## 2100001 非法参数值
-
-**错误信息**
-
-Invalid parameter value.
-
-**错误描述**
-
-非法参数值
-
-**可能原因**
-
-输入参数取值范围错误。
-
-**处理步骤**
-
-检查输入参数的取值范围是否正确。
-
-## 2100002 连接服务失败
-
-**错误信息**
-
-Operation failed. Cannot connect to service.
-
-**错误描述**
-
-操作失败，连接系统服务发生异常。
-
-**可能原因**
-
-服务发生异常。
-
-**处理步骤**
-
-检查系统服务运行状态是否正常。
-
-## 2100003 系统内部错误
-
-**错误信息**
-
-System internal error.
-
-**错误描述**
-
-系统内部错误。
-
-**可能原因**
-
-1.内存异常。
-
-2.空指针。
-
-**处理步骤**
-
-1.检查内存空间是否充足，清理内存后重试。
-
-2.系统异常，请稍后重试或重启设备。
diff --git a/zh-cn/application-dev/reference/native-lib/third_party_napi/napi.md b/zh-cn/application-dev/reference/native-lib/third_party_napi/napi.md
index 98a19c118a66b4b556ae269e216f33ebdb0a0828..27933ad0d7f79d43bf3535906aba3bf1f4c33520 100644
--- a/zh-cn/application-dev/reference/native-lib/third_party_napi/napi.md
+++ b/zh-cn/application-dev/reference/native-lib/third_party_napi/napi.md
@@ -9,117 +9,127 @@ Node-API是用于封装JavaScript能力为Native插件的API，独立于底层Ja
 
 Node-API可以去除底层的JavaScript引擎的差异，提供一套稳定的接口。
 
-OpenHarmony的Native API组件对Node-API的接口进行了重新实现，底层对接了ArkJS等引擎。当前支持[Node-API](https://nodejs.org/docs/v14.9.0/api/n-api.html)标准库中的部分接口。
+OpenHarmony的N-API组件对Node-API的接口进行了重新实现，底层对接了ArkJS等引擎。当前支持[Node-API](https://nodejs.org/docs/v14.9.0/api/n-api.html)标准库中的部分接口。
 
-## Native API组件扩展的符号列表
-
-|符号类型|符号名|备注|
-| --- | --- | --- |
-|FUNC|napi_run_script_path|运行JavaScript文件|
+## N-API组件扩展的符号列表
 
 **标准库中导出的符号列表**
 
-|符号类型|符号名|备注|
+|符号类型|符号名|说明|
 | --- | --- | --- |
-|FUNC|napi_module_register||
-|FUNC|napi_get_last_error_info||
-|FUNC|napi_throw||
-|FUNC|napi_throw_error||
-|FUNC|napi_throw_type_error||
-|FUNC|napi_throw_range_error||
-|FUNC|napi_is_error||
-|FUNC|napi_create_error||
-|FUNC|napi_create_type_error||
-|FUNC|napi_create_range_error||
-|FUNC|napi_get_and_clear_last_exception||
-|FUNC|napi_is_exception_pending||
-|FUNC|napi_fatal_error||
-|FUNC|napi_open_handle_scope||
-|FUNC|napi_close_handle_scope||
-|FUNC|napi_open_escapable_handle_scope||
-|FUNC|napi_close_escapable_handle_scope||
-|FUNC|napi_escape_handle||
-|FUNC|napi_create_reference||
-|FUNC|napi_delete_reference||
-|FUNC|napi_reference_ref||
-|FUNC|napi_reference_unref||
-|FUNC|napi_get_reference_value||
-|FUNC|napi_create_array||
-|FUNC|napi_create_array_with_length||
-|FUNC|napi_create_arraybuffer||
-|FUNC|napi_create_external||
-|FUNC|napi_create_external_arraybuffer||
-|FUNC|napi_create_object||
-|FUNC|napi_create_symbol||
-|FUNC|napi_create_typedarray||
-|FUNC|napi_create_dataview||
-|FUNC|napi_create_int32||
-|FUNC|napi_create_uint32||
-|FUNC|napi_create_int64||
-|FUNC|napi_create_double||
-|FUNC|napi_create_string_latin1||
-|FUNC|napi_create_string_utf8||
-|FUNC|napi_get_array_length||
-|FUNC|napi_get_arraybuffer_info||
-|FUNC|napi_get_prototype||
-|FUNC|napi_get_typedarray_info||
-|FUNC|napi_get_dataview_info||
-|FUNC|napi_get_value_bool||
-|FUNC|napi_get_value_double||
-|FUNC|napi_get_value_external||
-|FUNC|napi_get_value_int32||
-|FUNC|napi_get_value_int64||
-|FUNC|napi_get_value_string_latin1||
-|FUNC|napi_get_value_string_utf8||
-|FUNC|napi_get_value_uint32||
-|FUNC|napi_get_boolean||
-|FUNC|napi_get_global||
-|FUNC|napi_get_null||
-|FUNC|napi_get_undefined||
-|FUNC|napi_coerce_to_bool||
-|FUNC|napi_coerce_to_number||
-|FUNC|napi_coerce_to_object||
-|FUNC|napi_coerce_to_string||
-|FUNC|napi_typeof||
-|FUNC|napi_instanceof||
-|FUNC|napi_is_array||
-|FUNC|napi_is_arraybuffer||
-|FUNC|napi_is_typedarray||
-|FUNC|napi_is_dataview||
-|FUNC|napi_is_date||
-|FUNC|napi_strict_equals||
-|FUNC|napi_get_property_names||
-|FUNC|napi_set_property||
-|FUNC|napi_get_property||
-|FUNC|napi_has_property||
-|FUNC|napi_delete_property||
-|FUNC|napi_has_own_property||
-|FUNC|napi_set_named_property||
-|FUNC|napi_get_named_property||
-|FUNC|napi_has_named_property||
-|FUNC|napi_set_element||
-|FUNC|napi_get_element||
-|FUNC|napi_has_element||
-|FUNC|napi_delete_element||
-|FUNC|napi_define_properties||
-|FUNC|napi_call_function||
-|FUNC|napi_create_function||
-|FUNC|napi_get_cb_info||
-|FUNC|napi_get_new_target||
-|FUNC|napi_new_instance||
-|FUNC|napi_define_class||
-|FUNC|napi_wrap||
-|FUNC|napi_unwrap||
-|FUNC|napi_remove_wrap||
-|FUNC|napi_create_async_work||
-|FUNC|napi_delete_async_work||
-|FUNC|napi_queue_async_work||
-|FUNC|napi_cancel_async_work||
-|FUNC|napi_get_node_version||
-|FUNC|napi_get_version||
-|FUNC|napi_create_promise||
-|FUNC|napi_resolve_deferred||
-|FUNC|napi_reject_deferred||
-|FUNC|napi_is_promise||
-|FUNC|napi_run_script||
-|FUNC|napi_get_uv_event_loop||
\ No newline at end of file
+|FUNC|napi_module_register|napi native模块注册接口。|
+|FUNC|napi_get_last_error_info|获取`napi_extended_error_info`结构体，其中包含最近一次出现的error信息。|
+|FUNC|napi_throw|抛出一个js value。|
+|FUNC|napi_throw_error|抛出一个带文本信息的js `Error`。|
+|FUNC|napi_throw_type_error|抛出一个带文本信息的js `TypeError`。|
+|FUNC|napi_throw_range_error|抛出一个带文本信息的js `RangeError`。|
+|FUNC|napi_is_error|判断`napi_value`是否表示为一个error对象。|
+|FUNC|napi_create_error|创建并获取一个带文本信息的js `Error`。|
+|FUNC|napi_create_type_error|创建并获取一个带文本信息的js `TypeError`。|
+|FUNC|napi_create_range_error|创建并获取一个带文本信息的js `RangeError`。|
+|FUNC|napi_get_and_clear_last_exception|获取并清除最近一次出现的异常。|
+|FUNC|napi_is_exception_pending|判断是否出现了异常。|
+|FUNC|napi_fatal_error|引发致命错误以立即终止进程。|
+|FUNC|napi_open_handle_scope|创建一个上下文环境使用。|
+|FUNC|napi_close_handle_scope|关闭传入的上下文环境，关闭后，全部在其中声明的引用都将被关闭。|
+|FUNC|napi_open_escapable_handle_scope|创建出一个可逃逸的handel scope，可将范围内声明的值返回到父作用域。|
+|FUNC|napi_close_escapable_handle_scope|关闭传入的可逃逸的handel scope。|
+|FUNC|napi_escape_handle|提升传入的js object的生命周期到其父作用域。|
+|FUNC|napi_create_reference|为`Object`创建一个reference，以延长其生命周期。调用者需要自己管理reference生命周期。|
+|FUNC|napi_delete_reference|删除传入的reference。|
+|FUNC|napi_reference_ref|增加传入的reference的引用计数，并获取该计数。|
+|FUNC|napi_reference_unref|减少传入的reference的引用计数，并获取该计数。|
+|FUNC|napi_get_reference_value|获取与reference相关联的js `Object`。|
+|FUNC|napi_create_array|创建并获取一个js `Array`。|
+|FUNC|napi_create_array_with_length|创建并获取一个指定长度的js `Array`。|
+|FUNC|napi_create_arraybuffer|创建并获取一个指定大小的js `ArrayBuffer`。|
+|FUNC|napi_create_external|分配一个附加有外部数据的js value。|
+|FUNC|napi_create_external_arraybuffer|分配一个附加有外部数据的js `ArrayBuffer`。|
+|FUNC|napi_create_object|创建一个默认的js `Object`。|
+|FUNC|napi_create_symbol|创建一个js `Symbol`。|
+|FUNC|napi_create_typedarray|通过现有的`ArrayBuffer`创建一个js `TypeArray`。|
+|FUNC|napi_create_dataview|通过现有的`ArrayBuffer`创建一个js `DataView`。|
+|FUNC|napi_create_int32|通过一个C的`int32_t`数据创建js `Number`。|
+|FUNC|napi_create_uint32|通过一个C的`uint32_t`数据创建js `Number`。|
+|FUNC|napi_create_int64|通过一个C的`int64_t`数据创建js `Number`。|
+|FUNC|napi_create_double|通过一个C的`double`数据创建js `Number`。|
+|FUNC|napi_create_string_latin1|通过ISO-8859-1编码的C字符串数据创建js `String`。|
+|FUNC|napi_create_string_utf8|通过UTF8编码的C字符串数据创建js `String`。|
+|FUNC|napi_get_array_length|获取array的length。|
+|FUNC|napi_get_arraybuffer_info|获取`ArrayBuffer`的底层data buffer及其长度。|
+|FUNC|napi_get_prototype|获取给定js `Object`的`prototype`。|
+|FUNC|napi_get_typedarray_info|获取给定`TypedArray`的各种属性。|
+|FUNC|napi_get_dataview_info|获取给定`DataView`的各种属性。|
+|FUNC|napi_get_value_bool|获取给定js `Boolean`对应的C bool值。|
+|FUNC|napi_get_value_double|获取给定js `Number`对应的C double值。|
+|FUNC|napi_get_value_external|获取先前通过napi_create_external()传递的外部数据指针。|
+|FUNC|napi_get_value_int32|获取给定js `Number`对应的C int32值。|
+|FUNC|napi_get_value_int64|获取给定js `Number`对应的C int64值。|
+|FUNC|napi_get_value_string_latin1|获取给定js vaule对应的ISO-8859-1编码的字符串。|
+|FUNC|napi_get_value_string_utf8|获取给定js vaule对应的UTF8编码的字符串。|
+|FUNC|napi_get_value_uint32|获取给定js `Number`对应的C uint32值。|
+|FUNC|napi_get_boolean|根据给定的C boolean值，获取js bool对象。|
+|FUNC|napi_get_global|获取`global`对象。|
+|FUNC|napi_get_null|获取`null`对象。|
+|FUNC|napi_get_undefined|获取`undefined`对象。|
+|FUNC|napi_coerce_to_bool|将给定的js value强转成js `Boolean`。|
+|FUNC|napi_coerce_to_number|将给定的js value强转成js `Number`。|
+|FUNC|napi_coerce_to_object|将给定的js value强转成js `Object`。|
+|FUNC|napi_coerce_to_string|将给定的js value强转成js `String`。|
+|FUNC|napi_typeof|获取给定js value的js type。|
+|FUNC|napi_instanceof|判断给定object是否为给定constructor的实例。|
+|FUNC|napi_is_array|判断给定js value是否为array。|
+|FUNC|napi_is_arraybuffer|判断给定js value是否为`ArrayBuffer`。|
+|FUNC|napi_is_typedarray|判断给定js value是否表示一个`TypedArray`。|
+|FUNC|napi_is_dataview|判断给定js value是否表示一个`DataView`。|
+|FUNC|napi_is_date|判断给定js value是否为js `Date`对象。|
+|FUNC|napi_strict_equals|判断给定的两个js value是否严格相等。|
+|FUNC|napi_get_property_names|以字符串数组的形式获取对象的可枚举属性的名称。|
+|FUNC|napi_set_property|对给定`Object`设置属性。|
+|FUNC|napi_get_property|获取给定`Object`的给定属性。|
+|FUNC|napi_has_property|判断给定对象中是否存在给定属性。|
+|FUNC|napi_delete_property|尝试从给定`Object`中删除给定`key`属性。|
+|FUNC|napi_has_own_property|判断给定`Object`中是否有名为`key`的own property。|
+|FUNC|napi_set_named_property|对给定`Object`设置一个给定名称的属性。|
+|FUNC|napi_get_named_property|获取给定`Object`中指定名称的属性。|
+|FUNC|napi_has_named_property|判断给定`Object`中是否有给定名称的属性。|
+|FUNC|napi_set_element|在给定`Object`的指定索引处，设置元素。|
+|FUNC|napi_get_element|获取给定`Object`指定索引处的元素。|
+|FUNC|napi_has_element|若给定`Object`的指定索引处拥有属性，获取该元素。|
+|FUNC|napi_delete_element|尝试删除给定`Object`的指定索引处的元素。|
+|FUNC|napi_define_properties|批量的向给定`Object`中定义属性。|
+|FUNC|napi_call_function|在Native方法中调用js function，即native call js。|
+|FUNC|napi_create_function|创建native方法给js使用，以便于js call native。|
+|FUNC|napi_get_cb_info|从给定的callback info中获取有关调用的详细信息，如参数和this指针。|
+|FUNC|napi_get_new_target|获取构造函数调用的`new.target`。|
+|FUNC|napi_new_instance|通过给定的构造函数，构建一个实例。|
+|FUNC|napi_define_class|定义与C++类相对应的JavaScript类。|
+|FUNC|napi_wrap|在js object上绑定一个native对象实例。|
+|FUNC|napi_unwrap|从js object上获取先前绑定的native对象实例。|
+|FUNC|napi_remove_wrap|从js object上获取先前绑定的native对象实例，并解除绑定。|
+|FUNC|napi_create_async_work|创建一个异步工作对象。|
+|FUNC|napi_delete_async_work|释放先前创建的异步工作对象。|
+|FUNC|napi_queue_async_work|将异步工作对象加到队列，由底层去调度执行。|
+|FUNC|napi_cancel_async_work|取消入队的异步任务。|
+|FUNC|napi_get_node_version|获取node的版本信息。|
+|FUNC|napi_get_version|获取Node运行时支持的最高 N-API 版本。|
+|FUNC|napi_create_promise|创建一个延迟对象和js promise。|
+|FUNC|napi_resolve_deferred|resolve与js promise对象关联的延迟函数。|
+|FUNC|napi_reject_deferred|reject与js promise对象关联的延迟函数。|
+|FUNC|napi_is_promise|判断给定js value是否为promise对象。|
+|FUNC|napi_get_uv_event_loop|获取当前libuv loop实例。|
+|FUNC|napi_create_threadsafe_function|创建线程安全函数。|
+|FUNC|napi_get_threadsafe_function_context|获取线程安全函数中的context。|
+|FUNC|napi_call_threadsafe_function|调用线程安全函数。|
+|FUNC|napi_acquire_threadsafe_function|指示线程安全函数可以开始使用。|
+|FUNC|napi_release_threadsafe_function|指示线程安全函数将停止使用。|
+|FUNC|napi_ref_threadsafe_function|指示在主线程上运行的事件循环在线程安全函数被销毁之前不应退出。|
+|FUNC|napi_unref_threadsafe_function|指示在主线程上运行的事件循环可能会在线程安全函数被销毁之前退出。|
+|FUNC|napi_create_date|通过一个C的`double`数据创建js `Date`。|
+|FUNC|napi_get_date_value|获取给定js `Date`对应的C double值。|
+|FUNC|napi_create_bigint_int64|通过一个C的`int64`数据创建js `BigInt`。|
+|FUNC|napi_create_bigint_uint64|通过一个C的`uint64`数据创建js `BigInt`。|
+|FUNC|napi_create_bigint_words|通过一个C的`uint64`数组创建单个js `BigInt`。|
+|FUNC|napi_get_value_bigint_int64|获取给定js `BigInt`对应的C int64值。|
+|FUNC|napi_get_value_bigint_uint64|获取给定js `BigInt`对应的C uint64值。|
+|FUNC|napi_get_value_bigint_words|获取给定js `BigInt`对应的信息，包括符号位、64位小端序数组和数组中的元素个数。|
diff --git a/zh-cn/application-dev/reference/syscap-list.md b/zh-cn/application-dev/reference/syscap-list.md
index 937ebfdbd333267cb5e78e4e02b43201247dff19..9fc6840d6c407e815cbf0b8e09d14d161b891811 100644
--- a/zh-cn/application-dev/reference/syscap-list.md
+++ b/zh-cn/application-dev/reference/syscap-list.md
@@ -1347,7 +1347,7 @@ webview组件
 
 | Default | 运动表 | 智能表 | 平板 | 车机 | 智慧屏 | Smart-Vision | Router |
 | ------- | ------ | ------ | ---- | ---- | ------ | ------------ | ------ |
-| 是      | 否     | 是     | 是   | 是   | 是     | 否           | 否     |
+| 是      | 否     | 否     | 是   | 是   | 否     | 否           | 否     |
 
 ## SystemCapability.Cloud.AAID
 
diff --git a/zh-cn/application-dev/task-management/continuous-task-dev-guide.md b/zh-cn/application-dev/task-management/continuous-task-dev-guide.md
index 7ff252080910a020896f80d828c95069400752f5..120d259b4bf450b1c26178e397f00c366692c7d9 100644
--- a/zh-cn/application-dev/task-management/continuous-task-dev-guide.md
+++ b/zh-cn/application-dev/task-management/continuous-task-dev-guide.md
@@ -421,9 +421,3 @@ export default class BgTaskAbility extends Ability {
     }
 };
 ```
-
-## 相关实例
-
-基于后台任务管理，有以下相关实例可供参考：
-
-- [`BackgroundTaskManager`：后台任务管理（ArkTS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ResourcesSchedule/BackgroundTaskManager)
\ No newline at end of file
diff --git a/zh-cn/application-dev/task-management/work-scheduler-dev-guide.md b/zh-cn/application-dev/task-management/work-scheduler-dev-guide.md
index 02d18fe0925d11b9712eb373c023efe82d1d4abb..51a5643951532aace0fbeb179b030dbc01050ee6 100644
--- a/zh-cn/application-dev/task-management/work-scheduler-dev-guide.md
+++ b/zh-cn/application-dev/task-management/work-scheduler-dev-guide.md
@@ -199,4 +199,4 @@ try{
 
 基于延迟任务调度，有以下相关实例可供参考：
 
-- [`WorkScheduler`：延迟任务调度（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ResourcesSchedule/WorkScheduler)
\ No newline at end of file
+- [`WorkScheduler`：延迟任务调度（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/TaskManagement/WorkScheduler)
\ No newline at end of file
diff --git a/zh-cn/application-dev/task-management/workscheduler-extensionability.md b/zh-cn/application-dev/task-management/workscheduler-extensionability.md
index 17af45de59bdff449e63279f1fe454ea85b1601c..fc4de09866f847e2eccf999a427c40943b923282 100644
--- a/zh-cn/application-dev/task-management/workscheduler-extensionability.md
+++ b/zh-cn/application-dev/task-management/workscheduler-extensionability.md
@@ -199,5 +199,5 @@ WorkSchedulerExtensionAbility类拥有如下API接口，具体的API介绍详见
 
 针对WorkSchedulerExtensionAbility开发，有以下相关实例可供参考：
 
-- [WorkScheduler的创建与使用（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ResourcesSchedule/WorkScheduler)
+- [WorkScheduler的创建与使用（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/TaskManagement/WorkScheduler)
 
diff --git a/zh-cn/application-dev/telephony/cellular-network-signal-info.md b/zh-cn/application-dev/telephony/cellular-network-signal-info.md
index 7848977b41138194f83ecb774a796f03ccc9f2b1..f5bc1ca4cfd32cc537f9c842ce5fc539948a1fcd 100644
--- a/zh-cn/application-dev/telephony/cellular-network-signal-info.md
+++ b/zh-cn/application-dev/telephony/cellular-network-signal-info.md
@@ -53,4 +53,4 @@ radio模块提供了获取当前网络信号信息的方法。observer模块为
 ## 相关实例
 
 针对蜂窝网络数据开发，有以下相关实例可供参考：
-- [`MobileNetwork`：蜂窝数据（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Telephony/MobileNetwork)
\ No newline at end of file
+- [`MobileNetwork`：蜂窝数据（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/Telephony/MobileNetwork)
\ No newline at end of file
diff --git a/zh-cn/application-dev/ui/arkts-common-components-video-player.md b/zh-cn/application-dev/ui/arkts-common-components-video-player.md
index efc9efde21295e8bc414e546df5e4ffc2bd43eee..084b5fa36a58dc6a37e6c0354ef580dabda4b699 100644
--- a/zh-cn/application-dev/ui/arkts-common-components-video-player.md
+++ b/zh-cn/application-dev/ui/arkts-common-components-video-player.md
@@ -70,6 +70,27 @@ Video组件支持加载本地视频和网络视频。
   }
   ```
 
+### 加载沙箱路径视频
+
+支持file:///data/storage路径前缀的字符串，用于读取应用沙箱路径内的资源。需要保证应用沙箱目录路径下的文件存在并且有可读权限。
+
+```ts
+@Component
+export struct VideoPlayer {
+  private controller: VideoController;
+  private videosrc: string = 'file:///data/storage/el2/base/haps/entry/files/show.mp4'
+
+  build() {
+    Column() {
+      Video({
+        src: this.videosrc,
+        controller: this.controller
+      })
+    }
+  }
+}
+```
+
 
 ### 加载网络视频
 
diff --git a/zh-cn/application-dev/ui/arkts-common-events-touch-screen-event.md b/zh-cn/application-dev/ui/arkts-common-events-touch-screen-event.md
index 9ce68b0a8860a5738f6a9d76d8dbf258fa3f5f3a..f9a92ac2cdeeac70bd861618b912581cdb5fd940 100644
--- a/zh-cn/application-dev/ui/arkts-common-events-touch-screen-event.md
+++ b/zh-cn/application-dev/ui/arkts-common-events-touch-screen-event.md
@@ -83,11 +83,7 @@ import image from '@ohos.multimedia.image';
 @Entry
 @Component
 struct Index {
-  @State text: string = ''
-  @State bool1: boolean = false
-  @State bool2: boolean = false
   @State visible: Visibility = Visibility.Visible
-  @State pixelMap: PixelMap = undefined
   private pixelMapReader = undefined
 
   aboutToAppear() {
@@ -111,7 +107,6 @@ struct Index {
     const promise = image.createPixelMap(color, opts);
     promise.then((data) => {
       console.info('create pixmap has info message: ' + JSON.stringify(data))
-      this.pixelMap = data;
       this.pixelMapReader = data;
     })
   }
@@ -147,8 +142,6 @@ struct Index {
         .visibility(this.visible)
         .onDragStart(() => {                    //启动跨窗口拖拽
           console.info('Text onDrag start')
-          this.bool1 = true
-          this.text = 'TextDrag'
           return { pixelMap: this.pixelMapReader, extraInfo: 'custom extra info.' }
         })
         .onDrop((event: DragEvent, extraParams: string) => {
diff --git a/zh-cn/application-dev/ui/arkts-performance-improvement-recommendation.md b/zh-cn/application-dev/ui/arkts-performance-improvement-recommendation.md
index 3ca296f127341ecfad6547c6346b33e31b4c4172..82590267d36c3cbb313689b936e5326db68dfa39 100644
--- a/zh-cn/application-dev/ui/arkts-performance-improvement-recommendation.md
+++ b/zh-cn/application-dev/ui/arkts-performance-improvement-recommendation.md
@@ -2,7 +2,7 @@
 
 开发者若使用低性能的代码实现功能场景可能不会影响应用的正常运行，但却会对应用的性能造成负面影响。本章节列举出了一些可提升性能的场景供开发者参考，以避免应用实现上带来的性能劣化。
 
-## 推荐使用数据懒加载
+## 使用数据懒加载
 
 开发者在使用长列表时，如果直接采用循环渲染方式，如下所示，会一次性加载所有的列表元素，一方面会导致页面启动时间过长，影响用户体验，另一方面也会增加服务器的压力和流量，加重系统负担。
 
@@ -131,6 +131,226 @@ struct MyComponent {
 
 上述代码在页面加载时仅初始化加载三个列表元素，之后每点击一次列表元素，将增加一个列表元素。
 
+## 设置List组件的宽高
+
+在使用Scroll容器组件嵌套List组件加载长列表时，若不指定List的宽高尺寸，则默认全部加载。
+
+>  **说明：**
+>
+>  Scroll嵌套List时：
+>
+>  - List没有设置宽高，会布局List的所有子组件。
+>  
+>  - List设置宽高，会布局List显示区域内的子组件。
+>  
+>  - List使用[ForEach](../quick-start/arkts-rendering-control-foreach.md)加载子组件时，无论是否设置List的宽高，都会加载所有子组件。
+>  
+>  - List使用[LazyForEach](../quick-start/arkts-rendering-control-lazyforeach.md)加载子组件时，没有设置List的宽高，会加载所有子组件，设置了List的宽高，会加载List显示区域内的子组件。
+
+```ts
+class BasicDataSource implements IDataSource {
+  private listeners: DataChangeListener[] = []
+
+  public totalCount(): number {
+    return 0
+  }
+
+  public getData(index: number): any {
+    return undefined
+  }
+
+  registerDataChangeListener(listener: DataChangeListener): void {
+    if (this.listeners.indexOf(listener) < 0) {
+      console.info('add listener')
+      this.listeners.push(listener)
+    }
+  }
+
+  unregisterDataChangeListener(listener: DataChangeListener): void {
+    const pos = this.listeners.indexOf(listener);
+    if (pos >= 0) {
+      console.info('remove listener')
+      this.listeners.splice(pos, 1)
+    }
+  }
+
+  notifyDataReload(): void {
+    this.listeners.forEach(listener => {
+      listener.onDataReloaded()
+    })
+  }
+
+  notifyDataAdd(index: number): void {
+    this.listeners.forEach(listener => {
+      listener.onDataAdd(index)
+    })
+  }
+
+  notifyDataChange(index: number): void {
+    this.listeners.forEach(listener => {
+      listener.onDataChange(index)
+    })
+  }
+
+  notifyDataDelete(index: number): void {
+    this.listeners.forEach(listener => {
+      listener.onDataDelete(index)
+    })
+  }
+
+  notifyDataMove(from: number, to: number): void {
+    this.listeners.forEach(listener => {
+      listener.onDataMove(from, to)
+    })
+  }
+}
+
+class MyDataSource extends BasicDataSource {
+  private dataArray: Array<string> = new Array(100).fill('test')
+
+  public totalCount(): number {
+    return this.dataArray.length
+  }
+
+  public getData(index: number): any {
+    return this.dataArray[index]
+  }
+
+  public addData(index: number, data: string): void {
+    this.dataArray.splice(index, 0, data)
+    this.notifyDataAdd(index)
+  }
+
+  public pushData(data: string): void {
+    this.dataArray.push(data)
+    this.notifyDataAdd(this.dataArray.length - 1)
+  }
+}
+
+@Entry
+@Component
+struct MyComponent {
+  private data: MyDataSource = new MyDataSource()
+
+  build() {
+    Scroll() {
+      List() {
+        LazyForEach(this.data, (item: string, index: number) => {
+          ListItem() {
+            Row() {
+              Text('item value: ' + item + (index + 1)).fontSize(20).margin(10)
+            }
+          }
+        })
+      }
+    }
+  }
+}
+```
+
+因此，此场景下建议设置List子组件的宽高。
+
+```ts
+class BasicDataSource implements IDataSource {
+  private listeners: DataChangeListener[] = []
+
+  public totalCount(): number {
+    return 0
+  }
+
+  public getData(index: number): any {
+    return undefined
+  }
+
+  registerDataChangeListener(listener: DataChangeListener): void {
+    if (this.listeners.indexOf(listener) < 0) {
+      console.info('add listener')
+      this.listeners.push(listener)
+    }
+  }
+
+  unregisterDataChangeListener(listener: DataChangeListener): void {
+    const pos = this.listeners.indexOf(listener);
+    if (pos >= 0) {
+      console.info('remove listener')
+      this.listeners.splice(pos, 1)
+    }
+  }
+
+  notifyDataReload(): void {
+    this.listeners.forEach(listener => {
+      listener.onDataReloaded()
+    })
+  }
+
+  notifyDataAdd(index: number): void {
+    this.listeners.forEach(listener => {
+      listener.onDataAdd(index)
+    })
+  }
+
+  notifyDataChange(index: number): void {
+    this.listeners.forEach(listener => {
+      listener.onDataChange(index)
+    })
+  }
+
+  notifyDataDelete(index: number): void {
+    this.listeners.forEach(listener => {
+      listener.onDataDelete(index)
+    })
+  }
+
+  notifyDataMove(from: number, to: number): void {
+    this.listeners.forEach(listener => {
+      listener.onDataMove(from, to)
+    })
+  }
+}
+
+class MyDataSource extends BasicDataSource {
+  private dataArray: Array<string> = new Array(100).fill('test')
+
+  public totalCount(): number {
+    return this.dataArray.length
+  }
+
+  public getData(index: number): any {
+    return this.dataArray[index]
+  }
+
+  public addData(index: number, data: string): void {
+    this.dataArray.splice(index, 0, data)
+    this.notifyDataAdd(index)
+  }
+
+  public pushData(data: string): void {
+    this.dataArray.push(data)
+    this.notifyDataAdd(this.dataArray.length - 1)
+  }
+}
+
+@Entry
+@Component
+struct MyComponent {
+  private data: MyDataSource = new MyDataSource()
+
+  build() {
+    Scroll() {
+      List() {
+        LazyForEach(this.data, (item: string, index: number) => {
+          ListItem() {
+            Text('item value: ' + item + (index + 1)).fontSize(20).margin(10)
+          }.width('100%')
+        })
+      }.width('100%').height(500)
+    }.backgroundColor(Color.Pink)
+  }
+}
+```
+
+![list1](figures/list1.gif)
+
 ## 使用条件渲染替代显隐控制
 
 如下所示，开发者在使用visibility通用属性控制组件的显隐状态时，仍存在组件的重新创建过程，造成性能上的损耗。
diff --git a/zh-cn/application-dev/ui/figures/list1.gif b/zh-cn/application-dev/ui/figures/list1.gif
new file mode 100644
index 0000000000000000000000000000000000000000..167da600d4884c8877aa4b0ba76e3233a61b1bf7
Binary files /dev/null and b/zh-cn/application-dev/ui/figures/list1.gif differ
diff --git a/zh-cn/application-dev/ui/ui-js-animate-background-position-style.md b/zh-cn/application-dev/ui/ui-js-animate-background-position-style.md
index d11f4f917d029cfe87607a528178b997a30e255c..c90eeaff77c795377f2fdf07d673916b41a7d2fe 100644
--- a/zh-cn/application-dev/ui/ui-js-animate-background-position-style.md
+++ b/zh-cn/application-dev/ui/ui-js-animate-background-position-style.md
@@ -91,4 +91,4 @@
 
 针对background-position样式动画开发，有以下相关实例可供参考：
 
-- [`JsImage`：基本动画（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsImage)
\ No newline at end of file
+- [`JsComponentCollection`：JS组件集合（JS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/UI/JsComponentClollection/JsComponentCollection)
\ No newline at end of file
diff --git a/zh-cn/application-dev/ui/ui-js-animate-dynamic-effects.md b/zh-cn/application-dev/ui/ui-js-animate-dynamic-effects.md
index e9d60c5cf47743b28b909dcdfd84d06e837284f2..44abac846ce2424573af6a897890faa63f488fa7 100644
--- a/zh-cn/application-dev/ui/ui-js-animate-dynamic-effects.md
+++ b/zh-cn/application-dev/ui/ui-js-animate-dynamic-effects.md
@@ -153,7 +153,7 @@ button{
 ```js
 // xxx.js
 import animator from '@ohos.animator';
-import prompt from '@system.prompt';
+import promptAction from '@ohos.promptAction';
 export default {
   data: {
     scaleVal:1,
@@ -175,7 +175,7 @@ export default {
     var _this= this;
     //添加动画重放事件
     this.animation.onrepeat = function() {
-      prompt.showToast({
+      promptAction.showToast({
         message: 'repeat'
       });
       var repeatoptions = {
@@ -217,7 +217,7 @@ export default {
     var _this= this;
    //添加动画完成事件
     this.animation.onfinish = function() {
-      prompt.showToast({
+      promptAction.showToast({
         message: 'finish'
       })
     };
diff --git a/zh-cn/application-dev/ui/ui-js-animate-transform.md b/zh-cn/application-dev/ui/ui-js-animate-transform.md
index 7532337bb4c5e6d1ab1e6b71aaff848c9d4e9fd2..8a73dea54dae0e2be2184619c5aef83b26cebbe2 100644
--- a/zh-cn/application-dev/ui/ui-js-animate-transform.md
+++ b/zh-cn/application-dev/ui/ui-js-animate-transform.md
@@ -584,10 +584,5 @@ transform可以设置多个值并且多个值可同时设置，下面案例中
 
 针对transform样式动画开发，有以下相关实例可供参考：
 
-- [`JsAnimation`：动效示例应用（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsAnimation)
+- [`JsComponentCollection`：JS组件集合（JS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/UI/JsComponentClollection/JsComponentCollection)
 
-- [`JsAnimationStyle`：动画与自定义字体（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsAnimationStyle)
-
-- [`Clock`：时钟（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/common/Clock)
-
-- [`JsAnimator`：动画（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsAnimation)
diff --git a/zh-cn/application-dev/ui/ui-js-building-ui-component.md b/zh-cn/application-dev/ui/ui-js-building-ui-component.md
index ea6ca34941580fb821eeb872fd61f3bc49bf5939..d37da0e4da35fdb9f89e38120a4f561d78934970 100755
--- a/zh-cn/application-dev/ui/ui-js-building-ui-component.md
+++ b/zh-cn/application-dev/ui/ui-js-building-ui-component.md
@@ -25,20 +25,4 @@
 
 针对组件开发，有以下相关实例可供参考：
 
-- [`JsPanel`：内容展示面板（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsPanel)
-
-- [`Popup`：气泡（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/Popup)
-
-- [`RefreshContainer`：下拉刷新容器（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/RefreshContainer)
-
-- [`JSComponments`：Js组件（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JSComponments)
-
-- [`JsUserRegistration`：用户注册（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsUserRegistration)
-
-- [`Badge`：事件标记控件（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/Badge)
-
-- [`JsVideo`：视频播放（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/media/JsVideo)
-
-- [rating（JS）（API8）](https://gitee.com/openharmony/codelabs/tree/master/JSUI/RatingApplication)
-
-- [简易视频播放器（JS）（API8）](https://gitee.com/openharmony/codelabs/tree/master/Media/VideoOpenHarmony)
+- [`JsComponentCollection`：Js组件（JS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/UI/JsComponentClollection/JsComponentCollection)
diff --git a/zh-cn/application-dev/ui/ui-js-building-ui-routes.md b/zh-cn/application-dev/ui/ui-js-building-ui-routes.md
index b11883934b7f3c26d3593a277101403ad6b243ba..80b214701c5376d5013cb2f3f271acb81af41972 100644
--- a/zh-cn/application-dev/ui/ui-js-building-ui-routes.md
+++ b/zh-cn/application-dev/ui/ui-js-building-ui-routes.md
@@ -91,4 +91,4 @@ export default {
 
 针对页面路由开发，有以下相关实例可供参考：
 
-- [`JsRouter`：页面路由（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsRouter)
+- [`JsComponentCollection`：JS组件集合（JS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/UI/JsComponentClollection/JsComponentCollection)
diff --git a/zh-cn/application-dev/ui/ui-js-component-tabs.md b/zh-cn/application-dev/ui/ui-js-component-tabs.md
index d84e6ee6f74f36606a62d0db7927288ba992a76c..f183ee5dfaa6010f9b13e4239246e7b096dfc919 100644
--- a/zh-cn/application-dev/ui/ui-js-component-tabs.md
+++ b/zh-cn/application-dev/ui/ui-js-component-tabs.md
@@ -270,4 +270,4 @@ export default {
 
 针对tabs开发，有以下相关实例可供参考：
 
-- [`Tabs`：页签容器（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/Tabs)
\ No newline at end of file
+- [`JsComponentCollection`：JS组件集合（JS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/UI/JsComponentClollection/JsComponentCollection)
\ No newline at end of file
diff --git a/zh-cn/application-dev/ui/ui-js-components-canvas.md b/zh-cn/application-dev/ui/ui-js-components-canvas.md
index cceb5d4829c68b1dffb7a3a80b01c87bd59e0c34..cdfcac4c6dd4cf02e27035ff9cf67eafe2f0867a 100644
--- a/zh-cn/application-dev/ui/ui-js-components-canvas.md
+++ b/zh-cn/application-dev/ui/ui-js-components-canvas.md
@@ -146,4 +146,4 @@ export default {
 
 针对Canvas开发，有以下相关实例可供参考：
 
-- [`JsCanvas`：画布组件（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsCanvas)
+- [`JsComponentCollection`：JS组件集合（JS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/UI/JsComponentClollection/JsComponentCollection)
diff --git a/zh-cn/application-dev/ui/ui-js-components-chart.md b/zh-cn/application-dev/ui/ui-js-components-chart.md
index c83cd1fd2c8d8ecf24999bdca19c09a8b389d32a..e95ef50818c3fe33b2450ab2fe7c8127c94dabfc 100644
--- a/zh-cn/application-dev/ui/ui-js-components-chart.md
+++ b/zh-cn/application-dev/ui/ui-js-components-chart.md
@@ -619,11 +619,3 @@ export default {
 ![zh-cn_image_0000001179018876](figures/zh-cn_image_0000001179018876.gif)
 
 
-
-## 相关实例
-
-针对chart开发，有以下相关实例可供参考：
-
-- [`chart`：图表组件（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/chart)
-
-- [chart（JS）（API8）](https://gitee.com/openharmony/codelabs/tree/master/JSUI/SwitchApplication)
diff --git a/zh-cn/application-dev/ui/ui-js-components-dialog.md b/zh-cn/application-dev/ui/ui-js-components-dialog.md
index 7c46e55bb4647081df08083d1a9f5dd3c872c598..91defb304a19deabd099cfdc2da6e9c4820f2dfa 100644
--- a/zh-cn/application-dev/ui/ui-js-components-dialog.md
+++ b/zh-cn/application-dev/ui/ui-js-components-dialog.md
@@ -267,7 +267,6 @@ export default {
 // xxx.js
 var info = null;
 import promptAction from '@ohos.promptAction';
-
 export default {
   data: {
     curYear:'',
@@ -325,6 +324,4 @@ export default {
 
 针对dialog开发，有以下相关实例可供参考：
 
-- [`JsDialog`：页面弹窗（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsDialog)
-
-- [Dialog（JS）（API8）](https://gitee.com/openharmony/codelabs/tree/master/JSUI/DialogDemo)
+- [`JsComponentCollection`：JS组件集合（JS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/UI/JsComponentClollection/JsComponentCollection)
diff --git a/zh-cn/application-dev/ui/ui-js-components-grid.md b/zh-cn/application-dev/ui/ui-js-components-grid.md
index e7481dde306e2c48c7da747a694434778631f85a..252819211fdc274575910279e0859f140d705b1f 100644
--- a/zh-cn/application-dev/ui/ui-js-components-grid.md
+++ b/zh-cn/application-dev/ui/ui-js-components-grid.md
@@ -215,7 +215,7 @@ text{
 
 ```js
 // index.js
-import prompt from '@system.prompt';
+import promptAction from '@ohos.promptAction';
 export default {
   data:{
     list:[
@@ -226,7 +226,7 @@ export default {
     fresh:false
   },
   refresh(e) {
-    prompt.showToast({
+    promptAction.showToast({
       message: 'refreshing'
     })
     var that = this;
@@ -234,7 +234,7 @@ export default {
     setTimeout(function () {
       that.fresh = false;
       that.list.unshift({src: 'common/images/4.png',id:'4'});
-      prompt.showToast({
+      promptAction.showToast({
         message: 'succeed'
       })
     }, 2000)
@@ -244,9 +244,3 @@ export default {
 
 
 ![zh-cn_image_0000001263160403](figures/zh-cn_image_0000001263160403.gif)
-
-## 相关实例
-
-针对Grid开发，有以下相关实例可供参考：
-
-- [`JsGrid`：栅格组件（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsGrid)
\ No newline at end of file
diff --git a/zh-cn/application-dev/ui/ui-js-components-image-animator.md b/zh-cn/application-dev/ui/ui-js-components-image-animator.md
index cd6376954a2e8291995c24210af83b4e0fa7bed5..d707239ec2242bd8b5a9c5097bbf48549513101f 100644
--- a/zh-cn/application-dev/ui/ui-js-components-image-animator.md
+++ b/zh-cn/application-dev/ui/ui-js-components-image-animator.md
@@ -285,7 +285,7 @@ button{
 
 ```js
 // index.js
-import prompt from '@system.prompt';
+import promptAction from '@ohos.promptAction';
 export default {
   data: {
     rev:false,
@@ -317,7 +317,7 @@ export default {
     this.$element('img').resume()
   },
   getimgstate(e) {
-    prompt.showToast({
+    promptAction.showToast({
       message: '当前状态：' + this.$element('img').getState()
     })
   },
diff --git a/zh-cn/application-dev/ui/ui-js-components-list.md b/zh-cn/application-dev/ui/ui-js-components-list.md
index e45917edf220c7dab870ddf85c646668dc9d137e..570ca2ea795927f40d9fae00c61c344cee39e815 100644
--- a/zh-cn/application-dev/ui/ui-js-components-list.md
+++ b/zh-cn/application-dev/ui/ui-js-components-list.md
@@ -309,9 +309,3 @@ export default {
 
 ![zh-cn_image_0000001234287779](figures/zh-cn_image_0000001234287779.gif)
 
-
-## 相关实例
-
-针对list开发，有以下相关实例可供参考：
-
-- [`JsList`：商品列表（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsList)
\ No newline at end of file
diff --git a/zh-cn/application-dev/ui/ui-js-components-menu.md b/zh-cn/application-dev/ui/ui-js-components-menu.md
index 31a094cad3a30d50610a353513d13c8a1b32535f..65055af509bb09e93c9795c9f0a76d2a790beb0e 100644
--- a/zh-cn/application-dev/ui/ui-js-components-menu.md
+++ b/zh-cn/application-dev/ui/ui-js-components-menu.md
@@ -278,8 +278,3 @@ export default {
 
 ![zh-cn_image_0000001226815403](figures/zh-cn_image_0000001226815403.gif)
 
-## 相关实例
-
-针对menu开发，有以下相关实例可供参考：
-
-- [`JSMenu`：菜单（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JSMenu)
diff --git a/zh-cn/application-dev/ui/ui-js-components-picker.md b/zh-cn/application-dev/ui/ui-js-components-picker.md
index 4f929795113d9be2799b053749b38711e92c8c9f..3dff7f45262be57a3a65ad13a30a52dca4c96662 100644
--- a/zh-cn/application-dev/ui/ui-js-components-picker.md
+++ b/zh-cn/application-dev/ui/ui-js-components-picker.md
@@ -301,4 +301,4 @@ export default {
 
 针对picker开发，有以下相关实例可供参考：
 
-- [`Picker`：滑动选择器（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/Picker)
+- [`JsComponentCollection`：JS组件集合（JS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/UI/JsComponentClollection/JsComponentCollection)
\ No newline at end of file
diff --git a/zh-cn/application-dev/ui/ui-js-components-rating.md b/zh-cn/application-dev/ui/ui-js-components-rating.md
index b77e395d932bc4b05969844fc182b95d4ff5fded..379359f379612cb991438eff61b102077e24983a 100644
--- a/zh-cn/application-dev/ui/ui-js-components-rating.md
+++ b/zh-cn/application-dev/ui/ui-js-components-rating.md
@@ -154,10 +154,10 @@ rating {
 
 ```js
 // xxx.js
-import prompt from '@system.prompt';
+import promptAction from '@ohos.promptAction';
 export default {
   showrating(e) {
-    prompt.showToast({
+    promptAction.showToast({
       message: '当前评分' + e.rating
     })
   }
diff --git a/zh-cn/application-dev/ui/ui-js-components-slider.md b/zh-cn/application-dev/ui/ui-js-components-slider.md
index 5c11d3754620f3d3481c929e6add1304519db785..32416ac9a3e399defd43c5a9330b419c38eb8fbb 100644
--- a/zh-cn/application-dev/ui/ui-js-components-slider.md
+++ b/zh-cn/application-dev/ui/ui-js-components-slider.md
@@ -217,6 +217,4 @@ export default{
 
 针对slider开发，有以下相关实例可供参考：
 
-- [`Slider`：滑动条（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/Slider)
-
-- [slider（JS）（API8）](https://gitee.com/openharmony/codelabs/tree/master/JSUI/SliderApplication)
\ No newline at end of file
+- [`JsComponentCollection`：JS组件集合（JS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/UI/JsComponentClollection/JsComponentCollection)
\ No newline at end of file
diff --git a/zh-cn/application-dev/ui/ui-js-components-stepper.md b/zh-cn/application-dev/ui/ui-js-components-stepper.md
index 5fcba699583fe260cde6729b236e783a5269843a..3a8ca9f666909ed27de856c9ebb3598f1bfdd05f 100644
--- a/zh-cn/application-dev/ui/ui-js-components-stepper.md
+++ b/zh-cn/application-dev/ui/ui-js-components-stepper.md
@@ -403,9 +403,3 @@ export default {
 
 ![zh-cn_image_0000001189249862](figures/zh-cn_image_0000001189249862.gif)
 
-
-## 相关实例
-
-针对stepper开发，有以下相关实例可供参考：
-
-- [`StepNavigator`：步骤导航器（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/StepNavigator)
diff --git a/zh-cn/application-dev/ui/ui-js-components-svg-overview.md b/zh-cn/application-dev/ui/ui-js-components-svg-overview.md
index 270c23db9f57de0fcd13ca0e37947e5ea5e7523e..eff78f13a5265d080d7847882d06050a1f8047d6 100644
--- a/zh-cn/application-dev/ui/ui-js-components-svg-overview.md
+++ b/zh-cn/application-dev/ui/ui-js-components-svg-overview.md
@@ -82,9 +82,3 @@ svg{
 >
 > - viewBox的宽高和svg的宽高不一致，会以中心对齐进行缩放。
 
-
-## 相关实例
-
-针对Svg开发，有以下相关实例可供参考：
-
-- [`JsSvg`：可缩放矢量图形（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsSvg)
diff --git a/zh-cn/application-dev/ui/ui-js-components-text.md b/zh-cn/application-dev/ui/ui-js-components-text.md
index b877e039b02217b7f29c6c866711c3e725fc9268..99dbfc2d5b32b9995744283a65f19e2c7c368f32 100644
--- a/zh-cn/application-dev/ui/ui-js-components-text.md
+++ b/zh-cn/application-dev/ui/ui-js-components-text.md
@@ -276,4 +276,4 @@ export default {
 
 针对text开发，有以下相关实例可供参考：
 
-- [`JstextComponents`：基础组件（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsBasicComponents)
+- [`JsComponentCollection`：JS组件集合（JS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/UI/JsComponentClollection/JsComponentCollection)
diff --git a/zh-cn/application-dev/ui/ui-js-components-toolbar.md b/zh-cn/application-dev/ui/ui-js-components-toolbar.md
index 9b79f6a0cb7f4133800b406516b958a05229aaa7..6203d6a62a988e33e97b4238a990728f5792c428 100644
--- a/zh-cn/application-dev/ui/ui-js-components-toolbar.md
+++ b/zh-cn/application-dev/ui/ui-js-components-toolbar.md
@@ -225,8 +225,3 @@ export default {
 ![zh-cn_image_0000001263279105](figures/zh-cn_image_0000001263279105.gif)
 
 
-## 相关实例
-
-针对toolbar开发，有以下相关实例可供参考：
-
-- [`Toolbar`：工具栏（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/Toolbar)
diff --git a/zh-cn/application-dev/ui/ui-js-custom-components.md b/zh-cn/application-dev/ui/ui-js-custom-components.md
index a9bb9a2253cfb84d484fe36bb84f7469226a1341..48ee973e103124c05f30e1ed73ba63fe23c0f1fa 100755
--- a/zh-cn/application-dev/ui/ui-js-custom-components.md
+++ b/zh-cn/application-dev/ui/ui-js-custom-components.md
@@ -99,10 +99,3 @@
 ![zh-cn_image_0000001070693737](figures/zh-cn_image_0000001070693737.png)
 
 
-## 相关实例
-
-针对自定义组件开发，有以下相关实例可供参考：
-
-- [`JSUICustomComponent`：自定义组件（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JSUICustomComponent)
-
-- [自定义组件（JS）（API8）](https://gitee.com/openharmony/codelabs/tree/master/JSUI/JSCanvasComponet)
diff --git a/zh-cn/application-dev/ui/ui-js-overview.md b/zh-cn/application-dev/ui/ui-js-overview.md
index 097ad76023f0b7e7e7f70bb621ddda63f79e0193..1db9439fd49413c71a66472d3cd51ea451f00f39 100755
--- a/zh-cn/application-dev/ui/ui-js-overview.md
+++ b/zh-cn/application-dev/ui/ui-js-overview.md
@@ -34,20 +34,4 @@
 
 兼容JS的类Web开发范式的方舟开发框架，有以下相关实例可供参考：
 
-- [`AtomicLayout`：原子布局（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/AtomicLayout)
-
-- [`JsFA`：FA示例应用（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsFA)
-
-- [`JsShopping`：购物示例应用（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsShopping)
-
-- [`Stack`：堆叠容器（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/Stack)
-
-- [`JsAdaptivePortalList`：多设备自适应的效率型首页（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsAdaptivePortalList)
-
-- [`JsAdaptivePortalPage`：多设备自适应的FA页面（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsAdaptivePortalPage)
-
-- [`JsGallery`：图库示例应用（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/JsGallery)
-
-- [`Badge`：事件标记控件（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/UI/Badge)
-
-- [购物应用（JS）（API8）](https://gitee.com/openharmony/codelabs/tree/master/JSUI/ShoppingOpenHarmony)
+- [`JsAdaptivePortalPage`：多设备自适应的FA页面（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/JsAdaptivePortalPage)
diff --git a/zh-cn/application-dev/webgl/webgl-guidelines.md b/zh-cn/application-dev/webgl/webgl-guidelines.md
index 604822bc12d93e51f01e200de64d822c0d5d6bf3..493e9100788dd733bb3da489d29048e9353b14c0 100644
--- a/zh-cn/application-dev/webgl/webgl-guidelines.md
+++ b/zh-cn/application-dev/webgl/webgl-guidelines.md
@@ -703,9 +703,3 @@ WebGL主要帮助开发者在前端开发中完成图形图像的相关处理，
 **图2** 点击按钮绘制彩色三角形的效果图
 
 ![zh-cn_image_0000001192429306](figures/zh-cn_image_0000001192429306.gif)
-
-## 相关实例
-
-针对WebGL开发，有以下相关实例可供参考：
-
-- [`JsWbgGL`：WebGL（JS）（API8）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Graphics/JsWebGL)
\ No newline at end of file
diff --git a/zh-cn/application-dev/website.md b/zh-cn/application-dev/website.md
index e98b6762a1ac22d79dfc158e4f477569df41d37e..ccdac5e2d9cfb21929c1384ac05566b56d0bebfa 100644
--- a/zh-cn/application-dev/website.md
+++ b/zh-cn/application-dev/website.md
@@ -26,8 +26,6 @@
         - [HAR](quick-start/har-package.md)
         - HSP
           - [应用内HSP开发指导](quick-start/in-app-hsp.md)
-      - 原子化服务
-        - [原子化服务开发指导](quick-start/atomicService.md)
       - 应用程序包快速修复
         - [快速修复概述](quick-start/quickfix-principles.md)
         - [快速修复调试指导](quick-start/quickfix-debug.md)
@@ -141,8 +139,8 @@
           - [流转概述](application-models/inter-device-interaction-hop-overview.md)
           - [跨端迁移（仅对系统应用开放）](application-models/hop-cross-device-migration.md)
           - [多端协同（仅对系统应用开放）](application-models/hop-multi-device-collaboration.md)
-      - 进程间通信
-        - [进程模型](application-models/process-model-stage.md)
+      - 了解进程模型
+        - [进程模型概述](application-models/process-model-stage.md)
         - 公共事件
           - [公共事件简介](application-models/common-event-overview.md)
           - 公共事件订阅
@@ -152,8 +150,8 @@
             - [取消动态订阅公共事件](application-models/common-event-unsubscription.md)
           - [公共事件发布](application-models/common-event-publish.md)
         - [后台服务](application-models/background-services.md)
-      - 线程间通信
-        - [线程模型](application-models/thread-model-stage.md)
+      - 了解线程模型
+        - [线程模型概述](application-models/thread-model-stage.md)
         - [使用Emitter进行线程间通信](application-models/itc-with-emitter.md)
         - [使用Worker进行线程间通信](application-models/itc-with-worker.md)
       - 任务管理
@@ -196,12 +194,12 @@
         - [FA模型的Context](application-models/application-context-fa.md)
         - [信息传递载体Want](application-models/want-fa.md)
         - [组件启动规则（FA模型）](application-models/component-startup-rules-fa.md)
-      - 进程间通信
-        - [进程模型](application-models/process-model-fa.md)
+      - 了解进程模型
+        - [进程模型概述](application-models/process-model-fa.md)
         - [公共事件](application-models/common-event-fa.md)
         - [后台服务](application-models/rpc.md)
-      - 线程间通信
-        - [线程模型](application-models/thread-model-fa.md)
+      - 了解线程模型
+        - [线程模型概述](application-models/thread-model-fa.md)
         - [线程间通信](application-models/itc-fa-overview.md)
       - [任务管理](application-models/mission-management-fa.md)
     - FA模型与Stage模型应用组件互通指导
@@ -659,6 +657,7 @@
     - [cem工具](tools/cem-tool.md)
     - [anm工具](tools/anm-tool.md)
 - 示例教程
+  - [开发案例](https://gitee.com/openharmony/docs/blob/master/zh-cn/third-party-cases/Readme-CN.md)
   - [示例代码](https://gitee.com/openharmony/applications_app_samples/blob/OpenHarmony-3.2-Release/README_zh.md)
   - [Codelabs](https://gitee.com/openharmony/codelabs/blob/master/README.md)
 - API参考
@@ -789,6 +788,7 @@
       - [Swiper](reference/arkui-ts/ts-container-swiper.md)
       - [Tabs](reference/arkui-ts/ts-container-tabs.md)
       - [TabContent](reference/arkui-ts/ts-container-tabcontent.md)
+      - [WaterFlow](reference/arkui-ts/ts-container-waterflow.md)
     - 媒体组件
       - [Video](reference/arkui-ts/ts-media-components-video.md)
     - 绘制组件
diff --git a/zh-cn/application-dev/windowmanager/application-window-stage.md b/zh-cn/application-dev/windowmanager/application-window-stage.md
index 89af5fde83d067a017f13c352bd579305117d893..dd68ca50595bec0158f4f38f6aafd290f1d30ad8 100644
--- a/zh-cn/application-dev/windowmanager/application-window-stage.md
+++ b/zh-cn/application-dev/windowmanager/application-window-stage.md
@@ -285,7 +285,7 @@ export default class EntryAbility extends UIAbility {
 
    > **说明：**
    >
-   > 虽然悬浮窗具备始终在前台显示的能力，但如果创建悬浮窗的应用任务被系统回收，仍然会导致悬浮窗从界面移除。如果想要保持悬浮窗口始终在前台显示，请申请[长时任务](../task-management/background-task-overview.md)。
+   > 虽然悬浮窗具备始终在前台显示的能力，但如果创建悬浮窗的应用任务被系统回收，仍然会导致悬浮窗从界面移除。如果想要保持悬浮窗口始终在前台显示，请申请[长时任务](../task-management/continuous-task-dev-guide.md)。
    
    ```json
    {
@@ -381,4 +381,4 @@ export default class EntryAbility extends UIAbility {
 
 针对window开发（Stage模型），有以下相关实例可供参考：
 
-- [`Window`：窗口（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Graphics/Window)
+- [`WindowManage`：窗口（ArkTS）（API9）](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/WindowManagement/WindowManage)
diff --git a/zh-cn/device-dev/reference/hdi-apis/_stream_info.md b/zh-cn/device-dev/reference/hdi-apis/_stream_info.md
index ee81d8c68b65077efd2955c34d50b3d27ce0100b..2d4f5c39bf016824e2f3fa98e49673f90f9f5bb1 100644
--- a/zh-cn/device-dev/reference/hdi-apis/_stream_info.md
+++ b/zh-cn/device-dev/reference/hdi-apis/_stream_info.md
@@ -17,16 +17,16 @@
 
   | 名称 | 描述 | 
 | -------- | -------- |
-| [streamId_](#streamid) | 流的ID，用于在设备内唯一标识一条流。 | 
-| [width_](#width) | 图像宽度。 | 
-| [height_](#height) | 图像高度。 | 
-| [format_](#format) | 图像格式。 | 
-| [dataspace_](#dataspace) | 图像颜色空间。 | 
-| [intent_](#intent) | 流类型。 | 
-| [tunneledMode_](#tunneledmode) | 隧道模式，值为true时开启，false关闭。 | 
-| [bufferQueue_](#bufferqueue) | 图形提供的生产者句柄。 | 
-| [minFrameDuration_](#minframeduration) | 最小帧间隔。 | 
-| [encodeType_](#encodetype) | 编码类型。 | 
+| [streamId_](#streamid_) | 流的ID，用于在设备内唯一标识一条流。 | 
+| [width_](#width_) | 图像宽度。 | 
+| [height_](#height_) | 图像高度。 | 
+| [format_](#format_) | 图像格式。 | 
+| [dataspace_](#dataspace_) | 图像颜色空间。 | 
+| [intent_](#intent_) | 流类型。 | 
+| [tunneledMode_](#tunneledmode_) | 隧道模式，值为true时开启，false关闭。 | 
+| [bufferQueue_](#bufferqueue_) | 图形提供的生产者句柄。 | 
+| [minFrameDuration_](#minframeduration_) | 最小帧间隔。 | 
+| [encodeType_](#encodetype_) | 编码类型。 | 
 
 
 ## **类成员变量说明**
diff --git a/zh-cn/device-dev/subsystems/subsys-app-privilege-config-guide.md b/zh-cn/device-dev/subsystems/subsys-app-privilege-config-guide.md
index 327e5e5f64896afa2144fd06a150420503c7b711..9f3fe79468ca7bb7116e0f54f365c0e732e5bcc0 100755
--- a/zh-cn/device-dev/subsystems/subsys-app-privilege-config-guide.md
+++ b/zh-cn/device-dev/subsystems/subsys-app-privilege-config-guide.md
@@ -4,7 +4,9 @@
 
 OpenHarmony提供通用的应用特权和可由设备厂商针对不同设备单独配置的应用特权。
 
-注：应当注意不要滥用应用特权，避免造成用户反感甚至对用户造成侵权。
+> **说明：**
+> - 应当注意不要滥用应用特权，避免造成用户反感甚至对用户造成侵权。
+> - 直接修改应用Profile文件的方式，仅用于应用/服务调试阶段使用，不可用于发布上架应用市场。如果需要开发商用版本的应用，请在对应的应用市场进行发布证书和Profile文件的申请。
 
 ## 通用应用特权
 
diff --git a/zh-cn/device-dev/subsystems/subsys-dfx-hidumper.md b/zh-cn/device-dev/subsystems/subsys-dfx-hidumper.md
index 7112238681fcb2a2ac40c4e8892f5f824621eb22..f92fc9704ba497a67aa4a92fe848665ad07e89c4 100644
--- a/zh-cn/device-dev/subsystems/subsys-dfx-hidumper.md
+++ b/zh-cn/device-dev/subsystems/subsys-dfx-hidumper.md
@@ -163,6 +163,22 @@ HiDumper可以为开发者导出系统当前基本信息，通过这些基本信
     ```
     hidumper --mem [pid]
     ```
+    当携带pid参数时输出结果中第一列标题的详细说明如下：
+    | 名称             | 描述 |
+    |----------------|----|
+    | GL             | GPU内存   |
+    | Graph          | 图形内存  |
+    | ark ts heap    | ArkTS堆的内存占用  |
+    | guard          | 保护段所占内存   |
+    | native heap    | 堆内存   |
+    | AnonPage other | 其它没有被映射到文件的页所占内存  |
+    | stack          | 栈内存   |
+    | .hap           | 应用程序所占内存   |
+    | .db            | 进程加载的.db数据文件所占内存   |
+    | .so            | 进程加载的.so动态库所占内存   |
+    | .ttf           | 进程加载的.ttf字体文件所占内存   |
+    | dev            | 进程加载的以/dev开头的文件所占内存   |
+    | FilePage other | 其它有被映射到文件的页所占内存   |
 
 17. 运行 hidumper --zip 命令压缩信息数据到/data/dumper目录下。
      
@@ -174,4 +190,4 @@ HiDumper可以为开发者导出系统当前基本信息，通过这些基本信
      
     ```
     hidumper -t [timeout]
-    ```
\ No newline at end of file
+    ```
diff --git a/zh-cn/release-notes/OpenHarmony-v3.2-beta1.md b/zh-cn/release-notes/OpenHarmony-v3.2-beta1.md
index 6ad780d60a8ff9c75fb740054cd5b8348f658c28..023448d0cba8c86905ba4eef89465c86a0db92ab 100644
--- a/zh-cn/release-notes/OpenHarmony-v3.2-beta1.md
+++ b/zh-cn/release-notes/OpenHarmony-v3.2-beta1.md
@@ -186,26 +186,19 @@ _[API差异报告](api-change/v3.2-beta1/Readme-CN.md)_
 
 | 子系统 | 名称 | 简介 | 开发语言 |
 | -------- | -------- | -------- | -------- |
-| ArkUI | [MouseEvent](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ETSUI/MouseEvent) | 本示例模拟了简单的扫雷游戏调用了鼠标事件的相关接口 | ArkTS |
-| ArkUI | [Vibrator](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/device/Vibrator) | 本示例模拟倒计时场景，展示振动接口的使用方法。 | ArkTS |
-| DFX | [FaultLogger](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/DFX/FaultLogger) | 本示例展示了在ArkTS中如何获取应用故障相关信息。 | ArkTS |
-| ArkUI | [Gallery](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ETSUI/Gallery) | 本Demo通过不同示例向用户介绍通用事件、通用属性、手势处理等不同组件的功能。 | ArkTS |
-| 图形 | [JsWebGL](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Graphics/JsWebGL) | 本示例调用GPU资源绘制了五角星和矩形，展示WebGL相关接口的使用方法。 | JS |
-| ArkUI | [Clock](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Preset/Clock) | 本示例使用ArkTS&nbsp;UI能力实现一个简单的时钟应用。 | ArkTS |
-| 网络管理 | [Http](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Network/Http) | 本示例仿postman输入API接口地址，获取相应数据，介绍数据请求接口的用法。 | ArkTS |
-| 网络管理 | [Socket](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Network/Socket) | 本示例主要演示了Socket在网络通信方面的应用，展示了Socket在两端设备的连接验证、聊天通信方面的应用。 | ArkTS |
-| 分布式数据管理 | [DistributedRdb](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/data/DistributedRdb) | 本示例展示了在ArkTS中分布式关系型数据库的使用，在增、删、改、查的基本操作外，还包括分布式数据库的数据同步能力。 | ArkTS |
-| 元能力 | [BackgroundTaskManager](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ResourcesSchedule/BackgroundTaskManager) | 本示例模拟下载功能，将下载任务通过后台任务管理进行处理，实现退出应用后任务仍能够执行，直至任务结束。 | ArkTS |
-| 元能力 | [BringApp](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ETSUI/BringApp) | 本示例使用FeatureAbility接口，通过应用的包名与Ability名，拉起系统应用。 | ArkTS |
-| 媒体 | [VideoPlayer](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/media/VideoPlayer) | 本示例展示了在ArkTS中VideoPlayer如何播放视频，同时提供一个可供其他应用调用播放视频的Ability。 | ArkTS |
-| 元能力 | [DistributeCalc](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Preset/DistributeCalc) | 本示例使用JS分布式能力实现了一个简单的计算器应用，可以进行简单的数值计算，支持远程拉起另一个计算器FA，两个FA进行协同计算。 | ArkTS |
-| Web | [Browser](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/device/Browser) | 本示例运用OpenHarmony系统提供的Stage模型与相关接口展示了一个简易的浏览器。 | ArkTS |
-| 元能力 | [DeviceUsageStatistics](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/device/DeviceUsageStatistics) | 本示例主要展示了设备使用信息情况。 | ArkTS |
-| ArkUI | [AdaptiveCapabilities](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/AdaptiveCapabilities) | 本示例展示在ArkTS中的多设备自适应能力，包括资源限定词、原子布局和响应式布局。 | ArkTS |
-| ArkUI | [Game2048](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ETSUI/Game2048) | 2048是一款比较流行的数字游戏，此游戏demo是grid组件基础上进行开发完成的。 | ArkTS |
-| 窗口 | [Window](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Graphics/Window) | 本示例展示了创建新窗口，将应用悬浮在其他界面，及应用分屏等功能 | ArkTS |
-| 分布式数据管理 | [Preference](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/data/Preferences) | 本示例主要展示了首选项在主题切换方面的功能。 | ArkTS |
-| 全球化 | [International](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/common/International) | 本示例展示了i18n，intl，resourceManager在ArkTS中的使用，使用相关api实现系统语言和地区设置、时间和时区设置，展示了区域格式化示例。 | ArkTS |
+| ArkUI | [Vibrator](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DeviceManagement/Vibrator) | 本示例模拟倒计时场景，展示振动接口的使用方法。 | ArkTS |
+| DFX | [FaultLogger](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DFX/FaultLogger) | 本示例展示了在ArkTS中如何获取应用故障相关信息。 | ArkTS |
+| ArkUI | [ArkTSClock](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/Solutions/Tools/ArkTSClock) | 本示例使用ArkTS&nbsp;UI能力实现一个简单的时钟应用。 | ArkTS |
+| 网络管理 | [Http](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/Connectivity/Http) | 本示例仿postman输入API接口地址，获取相应数据，介绍数据请求接口的用法。 | ArkTS |
+| 分布式数据管理 | [DistributedRdb](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/DistributedAppDev/DistributedRdb) | 本示例展示了在ArkTS中分布式关系型数据库的使用，在增、删、改、查的基本操作外，还包括分布式数据库的数据同步能力。 | ArkTS |
+| 元能力 | [ArkTSDistributedCalc](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/DistributedAppDev/ArkTSDistributedCalc) | 本示例使用JS分布式能力实现了一个简单的计算器应用，可以进行简单的数值计算，支持远程拉起另一个计算器FA，两个FA进行协同计算。 | ArkTS |
+| Web | [Browser](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/Web/Browser) | 本示例运用OpenHarmony系统提供的Stage模型与相关接口展示了一个简易的浏览器。 | ArkTS |
+| 元能力 | [DeviceUsageStatistics](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DeviceUsageStatistics/DeviceUsageStatistics) | 本示例主要展示了设备使用信息情况。 | ArkTS |
+| ArkUI | [AdaptiveCapabilities](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/AdaptiveCapabilities) | 本示例展示在ArkTS中的多设备自适应能力，包括资源限定词、原子布局和响应式布局。 | ArkTS |
+| ArkUI | [Game2048](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/Solutions/Game/Game2048) | 2048是一款比较流行的数字游戏，此游戏demo是grid组件基础上进行开发完成的。 | ArkTS |
+| 窗口 | [WindowManage](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/WindowManagement/WindowManage) | 本示例展示了创建新窗口，将应用悬浮在其他界面，及应用分屏等功能 | ArkTS |
+| 分布式数据管理 | [Preference](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/DataManagement/Preferences) | 本示例主要展示了首选项在主题切换方面的功能。 | ArkTS |
+| 全球化 | [International](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SystemFeature/Internationalnation/International) | 本示例展示了i18n，intl，resourceManager在ArkTS中的使用，使用相关api实现系统语言和地区设置、时间和时区设置，展示了区域格式化示例。 | ArkTS |
 
 请访问[Samples](https://gitee.com/openharmony/applications_app_samples)仓了解更多信息。
 
diff --git a/zh-cn/release-notes/OpenHarmony-v3.2-beta3.md b/zh-cn/release-notes/OpenHarmony-v3.2-beta3.md
index 60dffa649cbd428bc17d2478945e0ab49e357d9a..7a2745b24078d1ce595a56ba1901fe74f8532609 100644
--- a/zh-cn/release-notes/OpenHarmony-v3.2-beta3.md
+++ b/zh-cn/release-notes/OpenHarmony-v3.2-beta3.md
@@ -190,13 +190,12 @@ API变更请参考：
 
 | 子系统 | 名称 | 简介 | 开发语言 |
 | -------- | -------- | -------- | -------- |
-| ArkUI | [HealthyDiet：健康饮食](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ETSUI/HealthyDiet) | 这是一个记录饮食和查看食物信息的应用，主要用于管理饮食健康。可以添加饮食信息，包括食物的种类、重量以及用餐时间，如早餐、&nbsp;午餐、晚餐和夜宵，并能统计得到相应用餐时间的总热量值、总蛋白质、总脂肪和总碳水值，并且用柱状图的形式展示出来。 | ArkTS |
-| ArkUI | [MusicAlbum：一多音乐专辑主页](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/MusicAlbum) | 本示例展示了音乐专辑主页，使用一次开发多端部署中介绍的自适应布局能力和响应式布局能力进行多设备（或多窗口尺寸）适配，保证应用在不同设备或不同窗口尺寸下可以正常显示。 | ArkTS |
-| 元能力、文件管理 | [Share：分享](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Share/Share) | 分享的主要工作是实现：发送方将文本，链接，图片文件三种类型分享给三方应用,同时能够在三方应用中分别呈现出来。 | ArkTS |
-| 元能力 | [GalleryForm：图库卡片](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/ability/GalleryForm) | 本示例是模拟图库卡片，实现对图库中的照片在卡片中显示，定时刷新卡片内容等功能。 | ArkTS |
-| ArkUI | [AppMarket：一多应用市场首页](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/AppMarket) | 本示例展示了应用市场首页，页面中包括Tab栏、运营横幅、精品应用、精品游戏等。 | ArkTS |
-| ArkUI | [Weather：一多天气](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/MultiDeviceAppDev/Weather) | 本示例展示一个天气应用界面，包括首页、城市管理、添加城市、更新时间弹窗，体现一次开发，多端部署的能力。 | ArkTS |
-| 媒体 | [MediaCollections：媒体管理合集](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/media/MediaCollections) | 本示例展示了网络流播放能力、音视频播控能力、音量调节能力等。 | ArkTS |
+| ArkUI | [HealthyDiet：健康饮食](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/HealthyDiet) | 这是一个记录饮食和查看食物信息的应用，主要用于管理饮食健康。可以添加饮食信息，包括食物的种类、重量以及用餐时间，如早餐、&nbsp;午餐、晚餐和夜宵，并能统计得到相应用餐时间的总热量值、总蛋白质、总脂肪和总碳水值，并且用柱状图的形式展示出来。 | ArkTS |
+| ArkUI | [MusicAlbum：一多音乐专辑主页](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/MusicAlbum) | 本示例展示了音乐专辑主页，使用一次开发多端部署中介绍的自适应布局能力和响应式布局能力进行多设备（或多窗口尺寸）适配，保证应用在不同设备或不同窗口尺寸下可以正常显示。 | ArkTS |
+| 元能力、文件管理 | [CustomShare：自定义分享](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/ApplicationModels/CustomShare) | 分享的主要工作是实现：发送方将文本，链接，图片文件三种类型分享给三方应用,同时能够在三方应用中分别呈现出来。 | ArkTS |
+| ArkUI | [AppMarket：一多应用市场首页](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/AppMarket) | 本示例展示了应用市场首页，页面中包括Tab栏、运营横幅、精品应用、精品游戏等。 | ArkTS |
+| ArkUI | [Weather：一多天气](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/SuperFeature/MultiDeviceAppDev/Weather) | 本示例展示一个天气应用界面，包括首页、城市管理、添加城市、更新时间弹窗，体现一次开发，多端部署的能力。 | ArkTS |
+| 媒体 | [MediaCollections：媒体管理合集](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/FileManagement/MediaCollections) | 本示例展示了网络流播放能力、音视频播控能力、音量调节能力等。 | ArkTS |
 
 请访问[Samples](https://gitee.com/openharmony/applications_app_samples)仓了解更多信息。
 
diff --git a/zh-cn/release-notes/OpenHarmony-v3.2-beta4.md b/zh-cn/release-notes/OpenHarmony-v3.2-beta4.md
index d65b97521495cc4ed9cbdb1f45060827010a0e56..fea0753db5a58ab72d66973b3de8d30e86d665c2 100644
--- a/zh-cn/release-notes/OpenHarmony-v3.2-beta4.md
+++ b/zh-cn/release-notes/OpenHarmony-v3.2-beta4.md
@@ -196,9 +196,8 @@ ArkTS API新增支持错误码的上报，帮助开发者快速捕捉异常，
 
 | 子系统<div style="width:100px"></div> | 名称 | 简介 |
 | -------- | -------- | -------- |
-| 事件通知 | [Emitter: 处理进程内事件](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Notification/Emitter) | 本示例主要展示进程内事件通知，用户通过选择对应商品并提交订单后在订单列表显示所选商品。 |
-| 资源调度 | [AlarmClock: 后台代理提醒](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Notification/AlarmClock) | 本示例通过使用后台代理提醒的能力，创建闹钟的定时提醒，保证应用被冻结或退出时，计时和弹出提醒的功能可以被后台系统服务代理。 |
-| 窗口 | [Window: 窗口](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/Graphics/Window) | 本本示例展示了创建新窗口，将应用悬浮在其他界面，及应用分屏等功能。 |
+| 事件通知 | [CustomEmitter: 处理进程内事件](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/Notification/CustomEmitter) | 本示例主要展示进程内事件通知，用户通过选择对应商品并提交订单后在订单列表显示所选商品。 |
+| 窗口 | [WindowManage: 窗口](https://gitee.com/openharmony/applications_app_samples/tree/OpenHarmony-3.2-Release/code/BasicFeature/WindowManagement/WindowManage) | 本本示例展示了创建新窗口，将应用悬浮在其他界面，及应用分屏等功能。 |
 
 请访问[Samples](https://gitee.com/openharmony/applications_app_samples)仓了解更多信息。
 
diff --git a/zh-cn/release-notes/changelogs/v3.2-beta5/changelogs-mediaLibrary.md b/zh-cn/release-notes/changelogs/v3.2-beta5/changelogs-mediaLibrary.md
index 8b4a3fb8bec467cf18acf76cfbdd8deadb1d9d10..73ef9158bc274f11f4de68f19cfc9561ca85ddad 100644
--- a/zh-cn/release-notes/changelogs/v3.2-beta5/changelogs-mediaLibrary.md
+++ b/zh-cn/release-notes/changelogs/v3.2-beta5/changelogs-mediaLibrary.md
@@ -2,63 +2,32 @@
 
 ## cl.file.1 mediaLibrary相关接口变更
 
-multimedia 部件 medialibrary 接口废弃原有相关接口，使用 FilePicker 替代。
+multimedia 部件 mediaLibrary所有接口废弃。
 
 **变更影响**
 
-基于此前版本开发的应用，需注意废弃接口的迭代更新。替代的 FilePicker 应用是OpenHarmony中预置的系统应用，为用户提供文件选择及保存功能。
+[mediaLibrary](../../../application-dev/reference/apis/js-apis-medialibrary.md)所有接口废弃。系统只对三方应用开放公共目录下文件资源选择和保存功能，由[FilePicker](../../../application-dev/reference/apis/js-apis-file-picker.md)提供能力。
+基于此前版本开发的应用，需注意废弃接口的迭代更新。
 
 **关键接口/组件变更**
 
-medialibrary 相关接口废弃，原接口位于 @ohos.multimedia.medialibrary；替代应用为 FilePicker，位于[@ohos.file.picker](https://gitee.com/openharmony/interface_sdk-js/blob/master/api/@ohos.file.picker.d.ts)
+以下为可以使用FilePicker替代的接口。
 
 | 模块名                    | 方法/属性/枚举/常量                                          | 变更类型 |
 | ------------------------- | ------------------------------------------------------------ | -------- |
-| medialibrary   |  **function** getMediaLibrary(): MediaLibrary; | 废弃     |
 | medialibrary   |  **function** getMediaLibrary(context: Context): MediaLibrary; | 废弃     |
 | medialibrary   |  **function** getFileAssets(options: MediaFetchOptions, callback: AsyncCallback\<FetchFileResult\>): void | 废弃     |
 | medialibrary   |  **function** getFileAssets(options: MediaFetchOptions): Promise\<FetchFileResult\> | 废弃     |
-| medialibrary   |  **function** on(type: 'deviceChange'\|'albumChange'\|'imageChange'\|'audioChange'\|'videoChange'\|'fileChange'\|'remoteFileChange', callback: Callback\<void\>): void | 废弃     |
-| medialibrary   |  **function** off(type: 'deviceChange'\|'albumChange'\|'imageChange'\|'audioChange'\|'videoChange'\|'fileChange'\|'remoteFileChange', callback?: Callback\<void\>): void | 废弃     |
 | medialibrary   |  **function** createAsset(mediaType: MediaType, displayName: string, relativePath: string, callback: AsyncCallback\<FileAsset\>): void | 废弃     |
 | medialibrary   |  **function** createAsset(mediaType: MediaType, displayName: string, relativePath: string): Promise\<FileAsset\> | 废弃     |
-| medialibrary   |  **function** deleteAsset(uri: string): Promise\<void\> | 废弃     |
-| medialibrary   |  **function** deleteAsset(uri: string, callback: AsyncCallback\<void\>): void | 废弃     |
 | medialibrary   |  **function** getPublicDirectory(type: DirectoryType, callback: AsyncCallback\<string\>): void | 废弃     |
 | medialibrary   |  **function** getPublicDirectory(type: DirectoryType): Promise\<string\> | 废弃     |
-| medialibrary   |  **function** getAlbums(options: MediaFetchOptions, callback: AsyncCallback\<Array\<Album\>\>): void | 废弃     |
-| medialibrary   |  **function** getAlbums(options: MediaFetchOptions): Promise\<Array\<Album\>\> | 废弃     |
 | medialibrary   |  **function** release(callback: AsyncCallback\<void\>): void  | 废弃     | 
 | medialibrary   |  **function** release(): Promise\<void\> | 废弃     |
-| medialibrary   |  **function** storeMediaAsset(option: MediaAssetOption, callback: AsyncCallback\<string\>): void | 废弃     |
-| medialibrary   |  **function** storeMediaAsset(option: MediaAssetOption): Promise\<string\> | 废弃     |
-| medialibrary   |  **function** startImagePreview(images: Array\<string\>, index: number, callback: AsyncCallback\<void\>): void | 废弃     |
-| medialibrary   |  **function** startImagePreview(images: Array\<string\>, callback: AsyncCallback\<void\>): void | 废弃     |
-| medialibrary   |  **function** startImagePreview(images: Array\<string\>, index?: number): Promise\<void\> | 废弃     |
-| medialibrary   |  **function** startMediaSelect(option: MediaSelectOption, callback: AsyncCallback\<Array\<string\>\>): void | 废弃     |
-| medialibrary   |  **function** startMediaSelect(option: MediaSelectOption): Promise\<Array\<string\>\> | 废弃     |
-| medialibrary   |  **function** getActivePeers(): Promise\<Array\<PeerInfo\>\>; | 废弃     |
-| medialibrary   |  **function** getActivePeers(callback: AsyncCallback\<Array\<PeerInfo\>\>): void; | 废弃     |
-| medialibrary   |  **function** getAllPeers(): Promise\<Array\<PeerInfo\>\>; | 废弃     |
-| medialibrary   |  **function** FileAsset.isDirectory(callback: AsyncCallback\<boolean\>): void | 废弃     |
-| medialibrary   |  **function** FileAsset.isDirectory():Promise\<boolean\> | 废弃     |
-| medialibrary   |  **function** FileAsset.commitModify(callback: AsyncCallback\<void\>): void | 废弃     |
-| medialibrary   |  **function** FileAsset.commitModify(): Promise\<void\> | 废弃     |
 | medialibrary   |  **function** FileAsset.open(mode: string, callback: AsyncCallback\<number\>): void | 废弃     |
 | medialibrary   |  **function** FileAsset.open(mode: string): Promise\<number\> | 废弃     |
 | medialibrary   |  **function** FileAsset.close(fd: number, callback: AsyncCallback\<void\>): void | 废弃     |
 | medialibrary   |  **function** FileAsset.close(fd: number): Promise\<void\> | 废弃     |
-| medialibrary   |  **function** FileAsset.getThumbnail(callback: AsyncCallback\<image.PixelMap\>): void | 废弃     |
-| medialibrary   |  **function** FileAsset.getThumbnail(size: Size, callback: AsyncCallback\<image.PixelMap\>): void | 废弃     |
-| medialibrary   |  **function** FileAsset.getThumbnail(size?: Size): Promise\<image.PixelMap\> | 废弃     |
-| medialibrary   |  **function** FileAsset.favorite(isFavorite: boolean, callback: AsyncCallback\<void\>): void | 废弃     |
-| medialibrary   |  **function** FileAsset.favorite(isFavorite: boolean): Promise\<void\> | 废弃     |
-| medialibrary   |  **function** FileAsset.isFavorite(callback: AsyncCallback\<boolean\>): void | 废弃     |
-| medialibrary   |  **function** FileAsset.isFavorite():Promise\<boolean\>  | 废弃     |
-| medialibrary   |  **function** FileAsset.trash(isTrash: boolean, callback: AsyncCallback\<void\>): void | 废弃     |
-| medialibrary   |  **function** FileAsset.trash(isTrash: boolean): Promise\<void\> | 废弃     |
-| medialibrary   |  **function** FileAsset.isTrash(callback: AsyncCallback\<boolean\>): void | 废弃     |
-| medialibrary   |  **function** FileAsset.isTrash():Promise\<boolean\> | 废弃     |
 | medialibrary   |  **function** FetchFileResult.getCount(): number | 废弃     |
 | medialibrary   |  **function** FetchFileResult.isAfterLast(): boolean | 废弃     |
 | medialibrary   |  **function** FetchFileResult.close(): void | 废弃     |
@@ -72,45 +41,232 @@ medialibrary 相关接口废弃，原接口位于 @ohos.multimedia.medialibrary
 | medialibrary   |  **function** FetchFileResult.getPositionObject(index: number): Promise\<FileAsset\> | 废弃     |
 | medialibrary   |  **function** FetchFileResult.getAllObject(callback: AsyncCallback\<Array\<FileAsset\>\>): void | 废弃     |
 | medialibrary   |  **function** FetchFileResult.getAllObject(): Promise\<Array\<FileAsset\>\> | 废弃     |
-| medialibrary   |  **function** Album.commitModify(callback: AsyncCallback\<void\>): void | 废弃     |
-| medialibrary   |  **function** Album.commitModify(): Promise\<void\> | 废弃     |
 | medialibrary   |  **function** Album.getFileAssets(options: MediaFetchOptions, callback: AsyncCallback\<FetchFileResult\>): void | 废弃     |
 | medialibrary   |  **function** Album.getFileAssets(options?: MediaFetchOptions): Promise\<FetchFileResult\> | 废弃     |
-| medialibrary   |  **enum** DeviceType | 废弃     |
 | medialibrary   |  **enum** FileKey | 废弃     |
 | medialibrary   |  **enum** DirectoryType | 废弃     |
 | medialibrary   |  **enum** MediaType | 废弃     |
-| medialibrary   |  **interface** PeerInfo | 废弃     |
-| medialibrary   |  **interface** Size  | 废弃     |
 | medialibrary   |  **interface** MediaFetchOptions | 废弃     |
-| medialibrary   |  **interface** MediaAssetOption | 废弃     |
-| medialibrary   |  **interface** MediaSelectOption | 废弃     |
 | medialibrary   |  **interface** FileAsset | 废弃     |
 
 **适配指导**
 
-以选取一张图片为例，在替代应用中如下方式进行调用：
+**使用mediaLibrary接口编辑公共目录下的文件示例：**
+
+1. 使用getMediaLibrary接口获取媒体库实例。
+2. 创建MediaFetchOptions检索条件使用mediaLibrary实例调用getFileAssets接口获取公共目录下的文件。
+3. 使用FetchFileResult相应接口获取目的文件的fileAsset。
+4. 使用fileAsset.open接口打开这个文件得到fd。
+5. 通过fd使用[fs.writeSync](../../../application-dev/reference/apis/js-apis-file-fs.md#writesync)接口对这个文件进行编辑修改。
+6. 修改完成后使用fileAsset.close接口关闭这个文件的fd。
+7. 使用fetchFileResult.close接口释放getFileAssets时占用的资源。
+8. 使用release接口释放媒体库实例。
+
+**示例：**
 
 ```js
+import mediaLibrary from '@ohos.multimedia.mediaLibrary';
+import fs from '@ohos.file.fs';
+
+async function example() {
+  try {
+    let context = getContext(this);
+    let media = mediaLibrary.getMediaLibrary(context);
+    let fileKeyObj = mediaLibrary.FileKey;
+    let imageType = mediaLibrary.MediaType.IMAGE;
+    let getImageOp = {
+      selections: fileKeyObj.MEDIA_TYPE + '= ?',
+      selectionArgs: [imageType.toString()],
+      order: fileKeyObj.DATE_ADDED + ' DESC',
+    };
+    const fetchFileResult = await media.getFileAssets(getImageOp);
+    const fileAsset = await fetchFileResult.getFirstObject();
+    console.info('mediaLibrary fileAsset displayName: ' + fileAsset.displayName);
+    let fd = await fileAsset.open('rw');
+    console.info('mediaLibrary fileAsset open fd: ' + fd);
+    let writeLen = fs.writeSync(fd, 'hello, world');
+    console.info('write data to file succeed and size is: ' + writeLen);
+    fileAsset.close(fd);
+    fetchFileResult.close();
+    media.release();
+  } catch (err) {
+    console.error('mediaLibrary fail, err: ' + err);
+  }
+}
+```
+
+**使用FilePicker编辑公共目录下的文件示例：**
+
+1. 获取DocumentViewPicker文件选择器对象。
+2. 拉起DocumentViewPicker.select接口选择目的文件。
+3. 用户选择完后返回目的文件的uri。
+4. 待界面从DocumentViewPicker返回后在其他函数中使用[fs.openSync](../../../application-dev/reference/apis/js-apis-file-fs.md#fsopensync)接口通过uri打开这个文件得到fd。
+5. 通过fd使用[fs.writeSync](../../../application-dev/reference/apis/js-apis-file-fs.md#writesync)接口对这个文件进行编辑修改。
+6. 编辑修改完毕后使用[fs.closeSync](../../../application-dev/reference/apis/js-apis-file-fs.md#closesync)接口关闭这个fd。
+
+**示例：**
+
+```js
+import mediaLibrary from '@ohos.multimedia.mediaLibrary';
 import picker from '@ohos.file.picker';
+import fs from '@ohos.file.fs';
+
+let uri;
 
 async function example() {
-    try {  
-        let PhotoSelectOptions = new picker.PhotoSelectOptions();
-        PhotoSelectOptions.MIMEType = picker.PhotoViewMIMETypes.IMAGE_TYPE;
-        PhotoSelectOptions.maxSelectNumber = 1;
-        let photoPicker = new picker.PhotoViewPicker();
-        photoPicker.select(PhotoSelectOptions).then((PhotoSelectResult) => {
-            if (PhotoSelectResult !== undefined) {
-                console.info("PhotoViewPicker.select pass, PhotoSelectResult uri: " + JSON.stringify(PhotoSelectResult));
-            } else {
-                console.error("PhotoViewPicker.select PhotoSelectResult is undefined");
-            }
-        }).catch((err) => {
-            console.error("PhotoViewPicker.select fail, err: " + err);
-        });
-    } catch (err) {
-        console.error("PhotoViewPicker fail, err: " + err);
-    }
+  try {
+    let DocumentSelectOptions = new picker.DocumentSelectOptions();
+    let documentPicker = new picker.DocumentViewPicker();
+    documentPicker.select(DocumentSelectOptions).then((DocumentSelectResult) => {
+      console.info('DocumentViewPicker.select successfully, DocumentSelectResult uri: ' + JSON.stringify(DocumentSelectResult));
+      uri = DocumentSelectResult[0];
+    }).catch((err) => {
+      console.error('DocumentViewPicker.select failed with err: ' + err);
+    });
+  } catch (err) {
+    console.error('DocumentViewPicker failed with err: ' + err);
+  }
+}
+
+async function writeFile() {
+  try {
+    let file = fs.openSync(uri, fs.OpenMode.READ_WRITE);
+    console.info('DocumentViewPicker file fd: ' + file.fd);
+    let writeLen = fs.writeSync(file.fd, 'hello, world');
+    console.info('write data to file succeed and size is: ' + writeLen);
+    fs.closeSync(file);
+  } catch (err) {
+    console.error('DocumentViewPicker fail, err: ' + err);
+  }
 }
-```
\ No newline at end of file
+```
+
+**使用mediaLibrary接口在公共目录下创建文件示例：**
+
+1. 使用getMediaLibrary接口获取媒体库实例。
+2. 使用getPublicDirectory接口获取公共目录路径。
+3. 使用createAsset接口创建文件得到这个文件的fileAsset。
+4. 使用fileAsset.open接口打开这个文件得到fd。
+5. 通过fd使用fs.write接口对这个文件进行编辑修改。
+6. 修改完成后使用fileAsset.close接口关闭这个文件的fd。
+7. 使用release接口释放媒体库实例。
+
+**示例：**
+
+```js
+import mediaLibrary from '@ohos.multimedia.mediaLibrary';
+import fs from '@ohos.file.fs';
+
+async function example() {
+  try {
+    let context = getContext(this);
+    let media = mediaLibrary.getMediaLibrary(context);
+    let mediaType = mediaLibrary.MediaType.FILE;
+    let DIR_DOWNLOAD = mediaLibrary.DirectoryType.DIR_DOWNLOAD;
+    const path = await media.getPublicDirectory(DIR_DOWNLOAD);
+    const fileAsset = await media.createAsset(mediaType, 'test.txt', path);
+    console.info('mediaLibrary fileAsset displayName: ' + fileAsset.displayName);
+    let fd = await fileAsset.open('rw');
+    console.info('mediaLibrary fileAsset open fd: ' + fd);
+    let writeLen = fs.writeSync(fd, 'hello, world');
+    console.info('write data to file succeed and size is: ' + writeLen);
+    fileAsset.close(fd);
+    media.release();
+  } catch (err) {
+    console.error('mediaLibrary fail, err: ' + err);
+  }
+}
+```
+
+**使用FilePicker在公共目录下创建文件示例：**
+
+1. 获取DocumentViewPicker文件选择器对象。
+2. 拉起DocumentViewPicker.save接口创建保存一个空的文件。
+3. 用户保存完后返回目的文件的uri。
+4. 待界面从DocumentViewPicker返回后在其他函数中使用[fs.openSync](../../../application-dev/reference/apis/js-apis-file-fs.md#fsopensync)接口通过uri打开这个文件得到fd。
+5. 通过fd使用[fs.writeSync](../../../application-dev/reference/apis/js-apis-file-fs.md#writesync)接口对这个文件进行编辑修改。
+6. 编辑修改完毕后使用[fs.closeSync](../../../application-dev/reference/apis/js-apis-file-fs.md#closesync)接口关闭这个fd。
+
+**示例：**
+
+```js
+import mediaLibrary from '@ohos.multimedia.mediaLibrary';
+import picker from '@ohos.file.picker';
+import fs from '@ohos.file.fs';
+
+let uri;
+
+async function example() {
+  try {
+    let DocumentSaveOptions = new picker.DocumentSaveOptions();
+    DocumentSaveOptions.newFileNames = ['DocumentViewPicker01.txt'];
+    let documentPicker = new picker.DocumentViewPicker();
+    documentPicker.save(DocumentSaveOptions).then((DocumentSaveResult) => {
+      console.info('DocumentViewPicker.save successfully, DocumentSaveResult uri: ' + JSON.stringify(DocumentSaveResult));
+      uri = DocumentSaveResult[0];
+    }).catch((err) => {
+      console.error('DocumentViewPicker.save failed with err: ' + err);
+    });
+  } catch (err) {
+    console.error('DocumentViewPicker failed with err: ' + err);
+  }
+}
+
+async function writeFile() {
+  try {
+    let file = fs.openSync(uri, fs.OpenMode.READ_WRITE);
+    console.info('DocumentViewPicker file fd: ' + file.fd);
+    let writeLen = fs.writeSync(file.fd, 'hello, world');
+    console.info('write data to file succeed and size is: ' + writeLen);
+    fs.closeSync(file);
+  } catch (err) {
+    console.error('DocumentViewPicker fail, err: ' + err);
+  }
+}
+```
+
+**关键接口/组件变更**
+
+medialibrary以下废弃接口由于功能管控，不对三方应用开放，无替代接口。
+
+| 模块名                    | 方法/属性/枚举/常量                                          | 变更类型 |
+| ------------------------- | ------------------------------------------------------------ | -------- |
+| medialibrary   |  **function** getMediaLibrary(): MediaLibrary; | 废弃     |
+| medialibrary   |  **function** on(type: 'deviceChange'\|'albumChange'\|'imageChange'\|'audioChange'\|'videoChange'\|'fileChange'\|'remoteFileChange', callback: Callback\<void\>): void | 废弃     |
+| medialibrary   |  **function** off(type: 'deviceChange'\|'albumChange'\|'imageChange'\|'audioChange'\|'videoChange'\|'fileChange'\|'remoteFileChange', callback?: Callback\<void\>): void | 废弃     |
+| medialibrary   |  **function** deleteAsset(uri: string): Promise\<void\> | 废弃     |
+| medialibrary   |  **function** deleteAsset(uri: string, callback: AsyncCallback\<void\>): void | 废弃     |
+| medialibrary   |  **function** storeMediaAsset(option: MediaAssetOption, callback: AsyncCallback\<string\>): void | 废弃     |
+| medialibrary   |  **function** storeMediaAsset(option: MediaAssetOption): Promise\<string\> | 废弃     |
+| medialibrary   |  **function** startImagePreview(images: Array\<string\>, index: number, callback: AsyncCallback\<void\>): void | 废弃     |
+| medialibrary   |  **function** startImagePreview(images: Array\<string\>, callback: AsyncCallback\<void\>): void | 废弃     |
+| medialibrary   |  **function** startImagePreview(images: Array\<string\>, index?: number): Promise\<void\> | 废弃     |
+| medialibrary   |  **function** startMediaSelect(option: MediaSelectOption, callback: AsyncCallback\<Array\<string\>\>): void | 废弃     |
+| medialibrary   |  **function** startMediaSelect(option: MediaSelectOption): Promise\<Array\<string\>\> | 废弃     |
+| medialibrary   |  **function** getActivePeers(): Promise\<Array\<PeerInfo\>\>; | 废弃     |
+| medialibrary   |  **function** getActivePeers(callback: AsyncCallback\<Array\<PeerInfo\>\>): void; | 废弃     |
+| medialibrary   |  **function** getAllPeers(): Promise\<Array\<PeerInfo\>\>; | 废弃     |
+| medialibrary   |  **function** FileAsset.isDirectory(callback: AsyncCallback\<boolean\>): void | 废弃     |
+| medialibrary   |  **function** FileAsset.isDirectory():Promise\<boolean\> | 废弃     |
+| medialibrary   |  **function** FileAsset.commitModify(callback: AsyncCallback\<void\>): void | 废弃     |
+| medialibrary   |  **function** FileAsset.commitModify(): Promise\<void\> | 废弃     |
+| medialibrary   |  **function** FileAsset.getThumbnail(callback: AsyncCallback\<image.PixelMap\>): void | 废弃     |
+| medialibrary   |  **function** FileAsset.getThumbnail(size: Size, callback: AsyncCallback\<image.PixelMap\>): void | 废弃     |
+| medialibrary   |  **function** FileAsset.getThumbnail(size?: Size): Promise\<image.PixelMap\> | 废弃     |
+| medialibrary   |  **function** FileAsset.favorite(isFavorite: boolean, callback: AsyncCallback\<void\>): void | 废弃     |
+| medialibrary   |  **function** FileAsset.favorite(isFavorite: boolean): Promise\<void\> | 废弃     |
+| medialibrary   |  **function** FileAsset.isFavorite(callback: AsyncCallback\<boolean\>): void | 废弃     |
+| medialibrary   |  **function** FileAsset.isFavorite():Promise\<boolean\>  | 废弃     |
+| medialibrary   |  **function** FileAsset.trash(isTrash: boolean, callback: AsyncCallback\<void\>): void | 废弃     |
+| medialibrary   |  **function** FileAsset.trash(isTrash: boolean): Promise\<void\> | 废弃     |
+| medialibrary   |  **function** FileAsset.isTrash(callback: AsyncCallback\<boolean\>): void | 废弃     |
+| medialibrary   |  **function** FileAsset.isTrash():Promise\<boolean\> | 废弃     |
+| medialibrary   |  **function** getAlbums(options: MediaFetchOptions, callback: AsyncCallback\<Array\<Album\>\>): void | 废弃     |
+| medialibrary   |  **function** getAlbums(options: MediaFetchOptions): Promise\<Array\<Album\>\> | 废弃     |
+| medialibrary   |  **function** Album.commitModify(callback: AsyncCallback\<void\>): void | 废弃     |
+| medialibrary   |  **function** Album.commitModify(): Promise\<void\> | 废弃     |
+| medialibrary   |  **enum** DeviceType | 废弃     |
+| medialibrary   |  **interface** PeerInfo | 废弃     |
+| medialibrary   |  **interface** Size  | 废弃     |
+| medialibrary   |  **interface** MediaAssetOption | 废弃     |
+| medialibrary   |  **interface** MediaSelectOption | 废弃     |
\ No newline at end of file