Merge branch 'master' of gitee.com:openharmony/docs

.gitattributes

@@ -13,3 +13,6 @@
 *.so filter=lfs diff=lfs merge=lfs -text
 *.bin filter=lfs diff=lfs merge=lfs -text
 *.dll filter=lfs diff=lfs merge=lfs -text
+OpenHarmony_Icons.zip filter=lfs diff=lfs merge=lfs -text
+zip filter=lfs diff=lfs merge=lfs -text
+figures/OpenHarmony_Icons.zip filter=lfs diff=lfs merge=lfs -text

en/application-dev/IDL/idl-guidelines.md

-# OpenHarmony IDL Specifications and User Guide
+# IDL Specifications and User Guide
 
 ## IDL Overview
 To ensure successful communications between the client and server, interfaces recognized by both parties must be defined. The OpenHarmony Interface Definition Language (IDL) is a tool for defining such interfaces. OpenHarmony IDL decomposes objects to be transferred into primitives that can be understood by the operating system and encapsulates cross-boundary objects based on developers' requirements.
@@ -162,7 +162,7 @@ Go to the local installation path, choose **toolchains > 3.x.x.x** (the folder n
 
 If the executable file does not exist, download the SDK package from the mirror as instructed in the [Release Notes](../../release-notes). The following uses [3.2 Beta3](../../release-notes/OpenHarmony-v3.2-beta3.md) as an example.
 
-For details about how to replace the SDK package, see [Full SDK Compilation Guide](../quick-start/full-sdk-compile-guide.md).
+For details about how to replace the SDK package, see [Full SDK Compilation Guide](../faqs/full-sdk-compile-guide.md).
 
 After obtaining the executable file, perform subsequent development steps based on your scenario.
 

en/application-dev/Readme-EN.md

@@ -4,18 +4,16 @@
 - About OpenHarmony
   - [OpenHarmony Project](../OpenHarmony-Overview.md)
   - [Glossary](../glossary.md)
-  - [OpenHarmony Release Notes](../release-notes/Readme.md)
+  - [Release Notes](../release-notes/Readme.md)
 - Quick Start
   - Getting Started
     - [Before You Start](quick-start/start-overview.md)
     - [Getting Started with ArkTS in Stage Model](quick-start/start-with-ets-stage.md)
-    - [Getting Started with ArkTS in FA Model](quick-start/start-with-ets-fa.md)
-    - [Getting Started with JavaScript in FA Model](quick-start/start-with-js-fa.md)
   - Development Fundamentals
     - Application Package Fundamentals
       - [Application Package Overview](quick-start/application-package-overview.md)
       - Application Package Structure
-        - [Application Package Structure in Stage Model)](quick-start/application-package-structure-stage.md)
+        - [Application Package Structure in Stage Model](quick-start/application-package-structure-stage.md)
         - [Application Package Structure in FA Model](quick-start/application-package-structure-fa.md)
       - Multi-HAP Mechanism
         - [Multi-HAP Design Objectives](quick-start/multi-hap-objective.md)
@@ -37,9 +35,9 @@
     - Application Configuration Files in FA Model
       - [Application Configuration File Overview (FA Model)](quick-start/application-configuration-file-overview-fa.md)
       - [Internal Structure of the app Tag](quick-start/app-structure.md)
-      - [Internal structure of deviceConfig Tag](quick-start/deviceconfig-structure.md)
+      - [Internal Structure of the deviceConfig Tag](quick-start/deviceconfig-structure.md)
       - [Internal Structure of the module Tag](quick-start/module-structure.md)
-    - [Resource Categories and Access](quick-start/resource-categories-and-access.md)
+  - [Resource Categories and Access](quick-start/resource-categories-and-access.md)
   - Learning ArkTS
     - [Getting Started with ArkTS](quick-start/arkts-get-started.md)
     - Basic Syntax
@@ -49,7 +47,7 @@
         - [Creating a Custom Component](quick-start/arkts-create-custom-components.md)
         - [Page and Custom Component Lifecycle](quick-start/arkts-page-custom-components-lifecycle.md)
       - [\@Builder: Custom Builder Function](quick-start/arkts-builder.md)
-      - [\@BuilderParam: @Builder Function Reference](quick-start/arkts-builderparam.md)
+      - [\@BuilderParam: \@Builder Function Reference](quick-start/arkts-builderparam.md)
       - [\@Styles: Definition of Resusable Styles](quick-start/arkts-style.md)
       - [\@Extend: Extension of Built-in Components](quick-start/arkts-extend.md)
       - [stateStyles: Polymorphic Style](quick-start/arkts-statestyles.md)
@@ -72,7 +70,7 @@
         - [\@Watch: Getting Notified of State Variable Changes](quick-start/arkts-watch.md)
         - [$$ Syntax: Two-Way Synchronization of Built-in Components](quick-start/arkts-two-way-sync.md)
     - Rendering Control
-      - [Rendering Control Overview](quick-start/arkts-rendering-control-overview.md)
+      - [Overview of Rendering Control](quick-start/arkts-rendering-control-overview.md)
       - [if/else: Conditional Rendering](quick-start/arkts-rendering-control-ifelse.md)
       - [ForEach: Rendering of Repeated Content](quick-start/arkts-rendering-control-foreach.md)
       - [LazyForEach: Lazy Data Loading](quick-start/arkts-rendering-control-lazyforeach.md)
@@ -95,14 +93,14 @@
   - [DFX](dfx/Readme-EN.md)
   - [Internationalization](internationalization/Readme-EN.md)
   - [Application Test](application-test/Readme-EN.md)
-  - [OpenHarmony IDL Specifications and User Guide](IDL/idl-guidelines.md)
+  - [IDL Specifications and User Guide](IDL/idl-guidelines.md)
   - [Native APIs](napi/Readme-EN.md)
 - Tools
   - [DevEco Studio (OpenHarmony) User Guide](quick-start/deveco-studio-user-guide-for-openharmony.md)
   - [Debugging Tools](tools/Readme-EN.md)
 - Hands-On Tutorials
   - [Samples](https://gitee.com/openharmony/applications_app_samples/blob/master/README.md)
-  - [Codelabs](https://gitee.com/openharmony/codelabs)
+  - [Codelabs](https://gitee.com/openharmony/codelabs/tree/master)
 - API References
   - [SystemCapability](reference/syscap.md)
   - [SystemCapability List](reference/syscap-list.md)
@@ -113,10 +111,9 @@
     - [ArkTS and JS APIs](reference/apis/Readme-EN.md)
     - [Error Codes](reference/errorcodes/Readme-EN.md)
     - Native APIs
-      - [Native APIs](reference/native-apis/Readme-EN.md)
+      - [Native API Reference](reference/native-apis/Readme-EN.md)
       - [Standard Libraries](reference/native-lib/third_party_libc/musl.md)
       - [Node_API](reference/native-lib/third_party_napi/napi.md)
 - [FAQs](faqs/Readme-EN.md)
 - Contribution
   - [How to Contribute](../contribute/documentation-contribution.md)
-<!--no_check-->
\ No newline at end of file

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

@@ -5,23 +5,22 @@
   - [Interpretation of the Application Model](application-model-description.md)
 - Stage Model Development
   - [Stage Model Development Overview](stage-model-development-overview.md)
-  - Stage Mode Application Components
+  - Stage Model Application Components
     - [Application- or Component-Level Configuration](application-component-configuration-stage.md)
     - UIAbility Component
-      - [UIAbility Component Overview](uiability-overview.md)
-      - [UIAbility Component Lifecycle](uiability-lifecycle.md)
-      - [UIAbility Component Launch Type](uiability-launch-type.md)
-      - [UIAbility Component Usage](uiability-usage.md)
-      - [Data Synchronization Between UIAbility and UI](uiability-data-sync-with-ui.md)
+      - [UIAbility Overview](uiability-overview.md)
+      - [UIAbility Lifecycle](uiability-lifecycle.md)
+      - [UIAbility Launch Type](uiability-launch-type.md)
+      - [UIAbility Usage](uiability-usage.md)
+      - [Data Synchronization Between UIAbility and UI Page](uiability-data-sync-with-ui.md)
       - [Interaction Between Intra-Device UIAbility Components](uiability-intra-device-interaction.md)
     - ExtensionAbility Component
-      - [ExtensionAbility Component Overview](extensionability-overview.md)
+      - [ExtensionAbility Overview](extensionability-overview.md)
       - [ServiceExtensionAbility](serviceextensionability.md)
-      - [DataShareExtensionAbility (for System Applications Only)](datashareextensionability.md)
       - [AccessibilityExtensionAbility](accessibilityextensionability.md)
       - [EnterpriseAdminExtensionAbility](enterprise-extensionAbility.md)
       - [InputMethodExtensionAbility](inputmethodextentionability.md)
-      - [WindowExtensionAbility](windowextensionability.md)
+      - [WindowExtensionAbility (for System Applications Only)](windowextensionability.md)
     - Service Widget Development in Stage Model
       - [Service Widget Overview](service-widget-overview.md)
       - Developing an ArkTS Widget
@@ -37,9 +36,10 @@
             - [Applying Custom Drawing in the Widget](arkts-ui-widget-page-custom-drawing.md)
           - Widget Event Development
             - [Widget Event Capability Overview](arkts-ui-widget-event-overview.md)
-            - [Updating Widget Content Through FormExtensionAbility](arkts-ui-widget-event-formextensionability.md)
-            - [Updating Widget Content Through UIAbility](arkts-ui-widget-event-uiability.md)
-            - [Redirecting to a Specified Page Through the Router Event](arkts-ui-widget-event-router.md)
+            - [Redirecting to a UIAbility Through the router Event](arkts-ui-widget-event-router.md)
+            - [Launching a UIAbility in the Background Through the call Event](arkts-ui-widget-event-call.md)
+            - [Updating Widget Content Through the message Event](arkts-ui-widget-event-formextensionability.md)
+            - [Updating Widget Content Through the router or call Event](arkts-ui-widget-event-uiability.md)
           - Widget Data Interaction
             - [Widget Data Interaction Overview](arkts-ui-widget-interaction-overview.md)
             - [Configuring a Widget to Update Periodically](arkts-ui-widget-update-by-time.md)
@@ -53,17 +53,18 @@
       - [Want Overview](want-overview.md)
       - [Matching Rules of Explicit Want and Implicit Want](explicit-implicit-want-mappings.md)
       - [Common action and entities Values](actions-entities.md)
-      - [Using Explicit Want to Start an Ability](ability-startup-with-explicit-want.md)
+      - [Using Explicit Want to Start an Application Component](ability-startup-with-explicit-want.md)
       - [Using Implicit Want to Open a Website](ability-startup-with-implicit-want.md)
       - [Using Want to Share Data Between Applications](data-share-via-want.md)
-    - [Component Startup Rules](component-startup-rules.md)
-    - Inter-Device Application Component Interaction (Continuation) 
+    - [Component Startup Rules (Stage Model)](component-startup-rules.md)
+    - Inter-Device Application Component Interaction (Continuation)
       - [Continuation Overview](inter-device-interaction-hop-overview.md)
       - [Cross-Device Migration (for System Applications Only)](hop-cross-device-migration.md)
       - [Multi-device Collaboration (for System Applications Only)](hop-multi-device-collaboration.md)
     - [Subscribing to System Environment Variable Changes](subscribe-system-environment-variable-changes.md)
-  - IPC
-    - [Process Model](process-model-stage.md)
+    - [Setting Atomic Services to Support Sharing](atomic-services-support-sharing.md)
+  - Process Model
+    - [Process Model Overview](process-model-stage.md)
     - Common Events
       - [Introduction to Common Events](common-event-overview.md)
       - Common Event Subscription
@@ -72,25 +73,25 @@
         - [Subscribing to Common Events in Static Mode (for System Applications Only)](common-event-static-subscription.md)
         - [Unsubscribing from Common Events](common-event-unsubscription.md)
       - [Publishing Common Events](common-event-publish.md)
-      - [Removing Sticky Common Events](common-event-remove-sticky.md)
+      - [Removing Sticky Common Events (for System Applications Only)](common-event-remove-sticky.md)
     - [Background Services](background-services.md)
-  - Inter-Thread Communication
-    - [Thread Model](thread-model-stage.md)
+  - Thread Model
+    - [Thread Model Overview](thread-model-stage.md)
     - [Using Emitter for Inter-Thread Communication](itc-with-emitter.md)
     - [Using Worker for Inter-Thread Communication](itc-with-worker.md)
   - Mission Management
     - [Mission Management Scenarios](mission-management-overview.md)
-    - [Mission Management and Launch Type](mission-management-launch-type.md)
-    - [Page Stack and MissionList](page-mission-stack.md)
+    - [Mission and Launch Type](mission-management-launch-type.md)
+    - [Page Stack and Mission List](page-mission-stack.md)
     - [Setting the Icon and Name of a Mission Snapshot](mission-set-icon-name-for-task-snapshot.md)
   - [Application Configuration File](config-file-stage.md)
 - FA Model Development
   - [FA Model Development Overview](fa-model-development-overview.md)
-  - FA Mode Application Components
+  - FA Model Application Components
     - [Application- or Component-Level Configuration](application-component-configuration-fa.md)
     - PageAbility Component Development
-      - [PageAbility Component Overview](pageability-overview.md)
-      - [PageAbility Component Configuration](pageability-configuration.md)
+      - [PageAbility Overview](pageability-overview.md)
+      - [PageAbility Configuration](pageability-configuration.md)
       - [PageAbility Lifecycle](pageability-lifecycle.md)
       - [PageAbility Launch Type](pageability-launch-type.md)
       - [Creating a PageAbility](create-pageability.md)
@@ -102,15 +103,15 @@
       - [Requesting Permissions](request-permissions.md)
       - [Redirection Rules](redirection-rules.md)
     - ServiceAbility Component Development
-      - [ServiceAbility Component Overview](serviceability-overview.md)
-      - [ServiceAbility Component Configuration](serviceability-configuration.md)
+      - [ServiceAbility Overview](serviceability-overview.md)
+      - [ServiceAbility Configuration](serviceability-configuration.md)
       - [ServiceAbility Lifecycle](serviceability-lifecycle.md)
       - [Creating a ServiceAbility](create-serviceability.md)
       - [Starting a ServiceAbility](start-serviceability.md)
       - [Connecting to a ServiceAbility](connect-serviceability.md)
     - DataAbility Component Development
-      - [DataAbility Component Overview](dataability-overview.md)
-      - [DataAbility Component Configuration](dataability-configuration.md)
+      - [DataAbility Overview](dataability-overview.md)
+      - [DataAbility Configuration](dataability-configuration.md)
       - [DataAbility Lifecycle](dataability-lifecycle.md)
       - [Creating a DataAbility](create-dataability.md)
       - [Starting a DataAbility](start-dataability.md)
@@ -119,13 +120,13 @@
     - [Widget Development](widget-development-fa.md)
     - [Context](application-context-fa.md)
     - [Want](want-fa.md)
-    - [Component Startup Rules](component-startup-rules-fa.md)
-  - IPC
-    - [Process Model](process-model-fa.md)
+    - [Component Startup Rules (FA Model)](component-startup-rules-fa.md)
+  - Process Model
+    - [Process Model Overview](process-model-fa.md)
     - [Common Events](common-event-fa.md)
     - [Background Services](rpc.md)
-  - Inter-Thread Communication
-    - [Thread Model](thread-model-fa.md)
+  - Thread Model
+    - [Thread Model Overview](thread-model-fa.md)
     - [Inter-Thread Communication](itc-fa-overview.md)
   - [Mission Management](mission-management-fa.md)
   - [Application Configuration File](config-file-fa.md)

en/application-dev/application-models/ability-startup-with-explicit-want.md

-# Using Explicit Want to Start an Ability
+# Using Explicit Want to Start an Application Component
 
 When a user touches a button in an application, the application often needs to start a UIAbility component to complete a specific task. If the **abilityName** and **bundleName** parameters are specified when starting a UIAbility, then the explicit Want is used. 
 

en/application-dev/application-models/ability-startup-with-implicit-want.md

@@ -5,21 +5,21 @@ This section uses the operation of using a browser to open a website as an examp
 ```json
 {
   "module": {
-    // ...
+    ...
     "abilities": [
       {
-        // ...
+        ...
         "skills": [
           {
             "entities": [
               "entity.system.home",
               "entity.system.browsable"
-              // ...
+              ...
             ],
             "actions": [
               "action.system.home",
               "ohos.want.action.viewData"
-              // ...
+              ...
             ],
             "uris": [
               {
@@ -31,9 +31,9 @@ This section uses the operation of using a browser to open a website as an examp
               },
               {
                 "scheme": "http",
-                // ...
+                ...
               }
-              // ...
+              ...
             ]
           }
         ]
@@ -59,19 +59,18 @@ function implicitStartAbility() {
     'uri': 'https://www.test.com:8080/query/student'
   }
   context.startAbility(wantInfo).then(() => {
-    // ...
+    ...
   }).catch((err) => {
-    // ...
+    ...
   })
 }
 ```
 
 The matching process is as follows:
 
-1. If **action** in the passed **want** parameter is specified and is included in **actions** under **skills** of the ability to match, the matching is successful.
-2. If **entities** in the passed **want** parameter is specified and is included in **entities** under **skills** of the ability to match, the matching is successful.
-3. If **uri** in the passed **want** parameter is included in **uris** under **skills** of the ability to match, which is concatenated into https://www.test.com:8080/query* (where * is a wildcard), the matching is successful.
-4. If **type** in the passed **want** parameter is specified and is included in **type** under **skills** of the ability to match, the matching is successful.
+1. If **action** in the passed **want** parameter is specified and is included in **actions** under **skills** of the application component to match, the matching is successful.
+2. If **entities** in the passed **want** parameter is specified and is included in **entities** under **skills** of the application component to match, the matching is successful.
+3. If **uri** in the passed **want** parameter is included in **uris** under **skills** of the application component to match, which is concatenated into https://www.test.com:8080/query* (where * is a wildcard), the matching is successful.
 
 If there are multiple matching applications, the system displays a dialog box for you to select one of them. The following figure shows an example. 
 

en/application-dev/application-models/abilitystage.md

@@ -24,7 +24,7 @@ AbilityStage is not automatically generated in the default project of DevEco Stu
        // 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.
+       // Triggered only for the UIAbility with the specified launch type.
        return "MyAbilityStage";
      }
    }
@@ -37,7 +37,7 @@ AbilityStage is not automatically generated in the default project of DevEco Stu
        "name": "entry",
        "type": "entry",
        "srcEntry": "./ets/myabilitystage/MyAbilityStage.ts",
-       // ...
+       ...
      }
    }
    ```

en/application-dev/application-models/access-dataability.md

@@ -11,7 +11,7 @@ The basic dependency packages include:
 
 - @ohos.data.dataAbility
 
-- @ohos.data.rdb
+- @ohos.data.relationalStore
 
 
 The sample code for accessing a DataAbility is as follows:
@@ -23,7 +23,7 @@ The sample code for accessing a DataAbility is as follows:
    // Different from the URI defined in the config.json file, the URI passed in the parameter has an extra slash (/), three slashes in total.
    import featureAbility from '@ohos.ability.featureAbility'
    import ohos_data_ability from '@ohos.data.dataAbility'
-   import ohos_data_rdb from '@ohos.data.rdb'
+   import relationalStore from '@ohos.data.relationalStore'
    
    let urivar = "dataability:///com.ix.DataAbility"
    let DAHelper = featureAbility.acquireDataAbilityHelper(urivar);

en/application-dev/application-models/access-datashareextensionability-from-fa.md

@@ -27,12 +27,14 @@ Instead of manual modification, OpenHarmony adopts the following processing:
 
 ## Constraints
 
-1. When you switch a DataAbility to a DataShareExtensionAbility, only the URI prefix can be modified.![FAvsStage-uri](figures/FAvsStage-uri.png)
+1. When you switch a DataAbility to a DataShareExtensionAbility, only the URI prefix can be modified.
 
-2. The **DataShareHelper** class implements only certain APIs of **DataAbilityHelper**. For details about the APIs, see the table below.
+   ![FAvsStage-uri](figures/FAvsStage-uri.png)
+
+3. The **DataShareHelper** class implements only certain APIs of **DataAbilityHelper**. For details about the APIs, see the table below.
+
+   **Table 1** API compatibility when the FA model accesses a DataShareExtensionAbility of the stage model
 
-     **Table 1** APIs invoked when the FA model accesses a DataShareExtensionAbility of the stage model
-   
    | API| Provided by DataAbilityHelper| Provided by DataShareHelper| Compatible|
    | -------- | -------- | -------- | -------- |
    | on | Yes| Yes| Yes|

en/application-dev/application-models/accessibilityextensionability.md

-# AccessibilityExtensionAbility Development
+# AccessibilityExtensionAbility
 
 The **AccessibilityExtensionAbility** module provides accessibility extension capabilities based on the **ExtensionAbility** framework. You can develop your accessibility applications by applying the **AccessibilityExtensionAbility** template to enhance usability.
 
@@ -10,19 +10,25 @@ The **AccessibilityExtensionAbility** module provides accessibility extension ca
 >
 > Model: stage
 
-This document is organized as follows:
+## AccessibilityExtensionAbility Overview
 
-- [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)
+Accessibility is about giving equal access to everyone so that they can access and use information equally and conveniently under any circumstances. It helps narrow the digital divide between people of different classes, regions, ages, and health status in terms of information understanding, information exchange, and information utilization, so that they can participate in social life more conveniently and enjoy the benefits of technological advances.
+
+AccessibilityExtensionAbility is an accessibility extension service framework. It allows you to develop your own extension services and provides a standard mechanism for exchanging information between applications and extension services. You can make use of the provided capabilities and APIs to develop accessibility features for users with disabilities or physical limitations. For example, you can develop a screen reader for users with vision impairments.
+
+Below shows the AccessibilityExtensionAbility framework.
+
+![AccessibilityFramework](figures/AccessibilityFramework.png)
+
+1. Accessibility application: extension service application developed based on the AccessibilityExtensionAbility framework, for example, a screen reader application.
+2. Target application: application assisted by the accessibility application.
+3. AccessibilityAbilityManagerService (AAMS): main service of the AccessibilityExtensionAbility framework, which is used to manage the lifecycle of accessibility applications and provide a bridge for information exchange between accessibility applications and target applications.
+4. AccessibilityAbility (AAkit): ability that is used by the accessibility application to build an extension service ability operating environment and that provides interfaces for the accessibility application to query and operate the target application, including performing click/long press operations.
+5. AccessibilitySystemAbilityClient (ASACkit): used by the target application to send accessibility events, such as content change events, to AAMS, and respond to the instructions (such as performing click/long press operations) sent by the accessibility application through AAMS.
 
 ## Creating an Accessibility Extension Service
 
-You can create an accessibility extension service by creating a project from scratch or adding the service to an existing project.
+You can create an accessibility extension service by creating a project from scratch or adding the service to an existing project. Only one accessibility extension service can be created for a project.
 
 ### Creating a Project
 
@@ -40,15 +46,15 @@ import AccessibilityExtensionAbility from '@ohos.application.AccessibilityExtens
 
 class AccessibilityExtAbility extends AccessibilityExtensionAbility {
     onConnect() {
-        console.log('AccessibilityExtAbility onConnect');
+        console.info('AccessibilityExtAbility onConnect');
     }
 
     onDisconnect() {
-        console.log('AccessibilityExtAbility onDisconnect');
+        console.info('AccessibilityExtAbility onDisconnect');
     }
 
     onAccessibilityEvent(accessibilityEvent) {
-        console.log('AccessibilityExtAbility onAccessibilityEvent: ' + JSON.stringify(accessibilityEvent));
+        console.info('AccessibilityExtAbility onAccessibilityEvent: ' + JSON.stringify(accessibilityEvent));
     }
 }
 
@@ -69,9 +75,9 @@ You can process the service logic for accessibility events in the **onAccessibil
 
 ```typescript
 onAccessibilityEvent(accessibilityEvent) {
-    console.log('AccessibilityExtAbility onAccessibilityEvent: ' + JSON.stringify(accessibilityEvent));
+    console.info('AccessibilityExtAbility onAccessibilityEvent: ' + JSON.stringify(accessibilityEvent));
     if (accessibilityEvent.eventType === 'pageStateUpdate') {
-        console.log('AccessibilityExtAbility onAccessibilityEvent: pageStateUpdate');
+        console.info('AccessibilityExtAbility onAccessibilityEvent: pageStateUpdate');
         // TODO: Develop custom logic.
     }
 }
@@ -110,12 +116,13 @@ After developing the custom logic for an accessibility extension service, you mu
   ]
 }
 ```
-## Enabling a Custom Accessibility Extension Service
+## Enabling or Disabling a Custom Accessibility Extension Service
 
 To enable or disable an accessibility extension service, run the following command:
 - To enable the service: **accessibility enable -a AccessibilityExtAbility -b com.example.demo -c rg**
 - To disable the service: **accessibility disable -a AccessibilityExtAbility -b com.example.demo**
 
-In the preceding commands, **AccessibilityExtAbility** indicates the name of the accessibility extension service, **com.example.demo** indicates the bundle name, and **rg** indicates the capabilities (**r** is short for retrieve).
+In the preceding commands, **AccessibilityExtAbility** indicates the name of the accessibility extension service, **com.example.demo** indicates the bundle name, and **rg** indicates the capabilities (**r** is short for retrieve and **g** gesture).
 
 If the service is enabled or disabled successfully, the message "enable ability successfully" or "disable ability successfully" is displayed.
+

en/application-dev/application-models/actions-entities.md

 # Common action and entities Values
 
-**action**: Action to take, such as viewing, sharing, and application details, by the caller. In implicit Want, you can define this field and use it together with **uri** or **parameters** to specify the operation to be performed on the data, for example, viewing URI data. For example, if the URI is a website and the action is **ohos.want.action.viewData**, the ability that supports website viewing is matched. Declaring the **action** field in Want indicates that the invoked application should support the declared operation. The **actions** field under **skills** in the configuration file indicates the operations supported by the application.
+The **action** field specifies the common operation (such as viewing, sharing, and application details) to be performed by the caller. In implicit [Want](../reference/apis/js-apis-app-ability-want.md), you can define this field and use it together with **uri** or **parameters** to specify the operation to be performed on the data, for example, viewing URI data. For example, if the URI is a website and the action is **ohos.want.action.viewData**, the application component that supports website viewing is matched. Declaring the **action** field in [Want](../reference/apis/js-apis-app-ability-want.md) indicates that the invoked application is expected to support the declared operation. The **actions** field under **skills** in the configuration file indicates the operations supported by the application.
 
-
-**Common action Values**
+The following **action** values are available:
 
 
 - **ACTION_HOME**: action of starting the application entry component. It must be used together with **ENTITY_HOME**. The application icon on the home screen is an explicit entry component. Users can touch the icon to start the entry component. Multiple entry components can be configured for an application.
@@ -14,14 +13,13 @@
 
 - **ACTION_VIEW_MULTIPLE_DATA**: action of launching the UI for sending multiple data records.
 
-**entities**: Category information (such as browser and video player) of the target ability. It is a supplement to **action** in implicit Want. You can define this field to filter application categories, for example, browser. Declaring the **entities** field in Want indicates that the invoked application should belong to the declared category. The **entities** field under **skills** in the configuration file indicates the categories supported by the application.
-
+The **entities** field specify the category information (such as browser and video player) of the target application component. It is a supplement to **action** in implicit Want. You can define this field to filter application categories, for example, browser. Declaring the **entities** field in Want indicates that the invoked application should belong to the declared category. The **entities** field under **skills** in the configuration file indicates the categories supported by the application.
 
-**Common entities Values**
+The following **entities** values are available:
 
 
 - **ENTITY_DEFAULT**: default category, which is meaningless.
 
-- **ENTITY_HOME**: abilities with an icon displayed on the home screen.
+- **ENTITY_HOME**: application components with an icon displayed on the home screen.
 
 - **ENTITY_BROWSABLE**: browser type.

en/application-dev/application-models/api-switch-overview.md

 # API Switching Overview
 
 
-Due to the differences in the thread model and process model, certain APIs (marked with **FAModelOnly** in the SDK) can be used only in the FA model. When switching an application from the FA model to the stage model, replace the APIs marked with **FAModelOnly** in the application with the APIs supported in the stage model. This topic uses the switching of **startAbility()** as an example.
+Due to the differences in the thread model and process model, certain APIs can be used only in the FA model. They are marked with **FAModelOnly** in the SDK. When switching an application from the FA model to the stage model, replace the APIs marked with **FAModelOnly** in the application with the APIs supported in the stage model. This topic uses the switching of **startAbility()** as an example.
 
 ![api-switch-overview](figures/api-switch-overview.png)
 
@@ -27,7 +27,7 @@ Due to the differences in the thread model and process model, certain APIs (mark
 - Sample code of **startAbility()** in the stage model:
 
   ```ts
-  // context is a member of the ability object and is required for invoking inside a non-ability object.
+  // Context is a member of the ability object and is required for invoking inside a non-ability object.
   // Pass in the Context object.
   let wantInfo = {
     bundleName: "com.example.myapplication",

en/application-dev/application-models/app-deviceconfig-switch.md

@@ -22,7 +22,7 @@ OpenHarmony has reconstructed the [deviceConfig](../quick-start/deviceconfig-str
 | deviceConfig in the FA Model| Description| Stage Model| Difference|
 | -------- | -------- | -------- | -------- |
 | deviceConfig| Device information.| / | This tag is no longer available in the stage model. In the stage model, device information is configured under the **app** tag.|
-| process | Name of the process running the application or ability. If the **process** attribute is configured in the **deviceConfig** tag, all abilities of the application run in this process. You can set the **process** attribute for a specific ability in the **abilities** attribute, so that the ability can run in the particular process.| / | The stage model does not support the configuration of process names.|
+| process | Name of the process running the application or UIAbility. If the **process** attribute is configured in the **deviceConfig** tag, all UIAbilities of the application run in this process. You can set the **process** attribute for a specific UIAbility in the **abilities** attribute, so that the UIAbility can run in the particular process.| / | The stage model does not support the configuration of process names.|
 | keepAlive | Whether the application is always running. This attribute applies only to system applications and does not take effect for third-party applications.| / | The stage model does not support changing of the model control mode for system applications.|
 | supportBackup | Whether the application supports data backup and restore.| / | This configuration is not supported in the stage model.|
 | compressNativeLibs | Whether the **libs** libraries are packaged in the HAP file after being compressed.| / | This configuration is not supported in the stage model.|

en/application-dev/application-models/application-component-configuration-fa.md

@@ -22,7 +22,7 @@ When developing an application, you may need to configure certain tags to identi
           "actions": ["action.system.home"]
         }
       ]
-      // ...
+      ...
     }
   ```
 

en/application-dev/application-models/application-component-configuration-stage.md

 # Application- or Component-Level Configuration (Stage Model)
 
+When developing an application, you may need to configure certain tags to identify the application, such as the bundle name and application icon. This topic describes key tags that need to be configured during application development.
 
-When developing an application, you may need to configure certain tags to identify the application, such as the bundle name and application icon. This topic describes key tags that need to be configured during application development. Icons and labels are usually configured together. There is the application icon, application label, entry icon, and entry label, which correspond to the **icon** and **label** fields in the [app.json5 file](../quick-start/app-configuration-file.md) and [module.json5 file](../quick-start/module-configuration-file.md). The application icon and label are used in **Settings**. For example, they are displayed in the application list in **Settings**. The entry icon is displayed on the device's home screen after the application is installed. The entry icon maps to a [UIAbility](uiability-overview.md) component. Therefore, an application can have multiple entry icons and labels. When you touch one of them, the corresponding UIAbility page is displayed.
+Icons and labels are usually configured together. There is the application icon, application label, entry icon, and entry label, which correspond to the **icon** and **label** fields in the [app.json5 file](../quick-start/app-configuration-file.md) and [module.json5 file](../quick-start/module-configuration-file.md).
 
+The application icon and label are used in **Settings**. For example, they are displayed in the application list in **Settings**. The entry icon is displayed on the device's home screen after the application is installed. The entry icon maps to a [UIAbility](uiability-overview.md) component. Therefore, an application can have multiple entry icons and entry labels. When you touch one of them, the corresponding UIAbility page is displayed.
 
-  **Figure 1** Icons and labels 
+**Figure 1** Icons and labels
 
 ![application-component-configuration-stage](figures/application-component-configuration-stage.png)
 
 
 - **Configuring the bundle name**
   
-  The bundle name is specified by the **bundleName** field in the [app.json5 file](../quick-start/app-configuration-file.md) in the **AppScope** directory of the project. This field uniquely identifies an application. You are advised to use the reverse domain name notion, for example, *com.example.demo*, where the first part is the domain suffix **com**, the second part is the vendor/individual name, and the third part is the application name, which can be of multiple levels.
+  The bundle name is specified by the **bundleName** field in the [app.json5 file](../quick-start/app-configuration-file.md) in the **AppScope** directory of the project. This field uniquely identifies an application. You are advised to use the reverse domain name notation, for example, *com.example.demo*, where the first part is the domain suffix **com**, the second part is the vendor/individual name, and the third part is the application name, which can be of multiple levels.
   
 - **Configuring the application icon and label**
 
@@ -19,28 +21,28 @@ When developing an application, you may need to configure certain tags to identi
 
   The application icon is specified by the **icon** field in the [app.json5 file](../quick-start/app-configuration-file.md) in the **AppScope** directory of the project. The **icon** field must be set to the index of an image so that the image is displayed as the application icon.
 
-  The application label is specified by the **label** field in the [app.json5 file](../quick-start/app-configuration-file.md) in the **AppScope** module of the project. The **label** field specifies the application name displayed to users. It must be set to the index of a string resource.
+  The application label is specified by the **label** field in the [app.json5 file](../quick-start/app-configuration-file.md) in the **AppScope** directory of the project. The **label** field specifies the application name displayed to users. It must be set to the index of a string resource.
 
   ```json
-    {
-      "app": {
-        "icon": "$media:app_icon",
-        "label": "$string:app_name"
-        // ...
-      }
+  {
+    "app": {
+      "icon": "$media:app_icon",
+      "label": "$string:app_name"
+      ...
     }
+  }
   ```
 
 - **Configuring the entry icon and label**
   
     On the stage model, you can configure an entry icon and label for each application component. The entry icon and label are displayed on the home screen.
 
-    The entry icon is configured by specifying **icon** under **abilities** in the [module.json5 file](../quick-start/module-configuration-file.md). For example, if you want to display the icon of the UIAbility component on the home screen, add **entity.system.home** to **entities** and **ohos.want.action.home** to **actions** under **skills**. If this field is configured for multiple UIAbility components of an application, multiple icons are displayed on the home screen, corresponding to their respective UIAbility component.
+    The entry icon is configured by specifying **icon** under **abilities** in the [module.json5 file](../quick-start/module-configuration-file.md). For example, if you want to display the icon of the UIAbility component on the home screen, add **entity.system.home** to **entities** and **ohos.want.action.home** to **actions** under **skills**. If this field is configured for multiple UIAbility components of an application, multiple icons are displayed on the home screen, corresponding to their respective UIAbility components.
   
   ```json
   {
     "module": {
-      // ...
+      ...
       "abilities": [
         {
           // The information starting with $ is the resource value.
@@ -61,6 +63,35 @@ When developing an application, you may need to configure certain tags to identi
     }
   }
   ```
+  OpenHarmony strictly controls applications without icons to prevent malicious applications from deliberately configuring no icon to block uninstall attempts.
+
+  To hide an application icon on the home screen, you must configure the **AllowAppDesktopIconHide** privilege. For details, see [Application Privilege Configuration Guide](../../device-dev/subsystems/subsys-app-privilege-config-guide.md). The rules for displaying the entry icon and entry label are as follows:
+
+  1. The HAP file contains UIAbility configuration.
+    * An entry icon is set in the **abilities** field of the **module.json5** file.
+      * The application does not have the privilege to hide its icon on the home screen.
+        * The system uses the icon configured for the UIAbility as the entry icon and displays it on the home screen. Touching this icon will direct the user to the home page of the UIAbility.
+        * The system uses the label configured for the UIAbility as the entry label and displays it on the home screen. If no label is configured, the system uses the label specified in the **app.json5** file as the entry label and displays it on the home screen.
+      * The application has the privilege to hide its icon on the home screen.
+        * The application information is not returned when the home screen queries the information, and the entry icon and label of the application are not displayed on the home screen.
+    * No entry icon is set in the **abilities** field of the **module.json5** file.
+      * The application does not have the privilege to hide its icon on the home screen.
+        * The system uses the icon specified in the **app.json5** file as the entry icon and displays it on the home screen. Touching this icon will direct the user to the application details page, as shown below.
+        * The system uses the label specified in the **app.json5** file as the entry label and displays it on the home screen.
+      * The application has the privilege to hide its icon on the home screen.
+        * The application information is not returned when the home screen queries the information, and the entry icon and label of the application are not displayed on the home screen.
+
+  2. The HAP file does not contain UIAbility configuration.
+    * The application does not have the privilege to hide its icon on the home screen.
+      * The system uses the icon specified in the **app.json5** file as the entry icon and displays it on the home screen. Touching this icon will direct the user to the application details page, as shown below.
+      * The system uses the label specified in the **app.json5** file as the entry label and displays it on the home screen.
+    * The application has the privilege to hide its icon on the home screen.
+      * The application information is not returned when the home screen queries the information, and the entry icon and label of the application are not displayed on the home screen.
+
+  **Figure 2** Application details page
+  
+![Application details page](figures/application_details.jpg)
+  
 - **Configuring application version declaration**
   
   To declare the application version, configure the **versionCode** and **versionName** fields in the [app.json5 file](../quick-start/app-configuration-file.md) in the **AppScope** directory of the project. **versionCode** specifies the version number of the application. The value is a 32-bit non-negative integer. It is used only to determine whether a version is later than another version. A larger value indicates a later version. **versionName** provides the text description of the version number.

en/application-dev/application-models/application-context-fa.md

@@ -44,17 +44,17 @@ For details about the APIs, see [API Reference](../reference/apis/js-apis-inner-
    }
    ```
 
-2. Set the display orientation of the host featureAbility.
+2. Set the display orientation of the **featureAbility**.
    
    ```ts
    import featureAbility from '@ohos.ability.featureAbility'
-   import bundle from '@ohos.bundle';
+   import bundleManager from '@ohos.bundle.bundleManager';
    
    export default {
      onCreate() {
        // Obtain the context and call related APIs.
        let context = featureAbility.getContext();
-       context.setDisplayOrientation(bundle.DisplayOrientation.LANDSCAPE).then(() => {
+       context.setDisplayOrientation(bundleManager.DisplayOrientation.LANDSCAPE).then(() => {
            console.info("Set display orientation.")
        })
        console.info('Application onCreate')

en/application-dev/application-models/application-model-description.md

@@ -12,10 +12,9 @@ Along its evolution, OpenHarmony has provided two application models:
 The stage model is designed based on the following considerations, which make it become the recommended model:
 
 1. **Designed for complex applications**
-   
    - In the stage model, multiple application components share an ArkTS engine (VM running the programming language ArkTS) instance, making it easy for application components to share objects and status while requiring less memory.
    - The object-oriented development mode makes the code of complex applications easy to read, maintain, and scale.
-  
+
 2. **Native support for [cross-device migration](hop-cross-device-migration.md) and [multi-device collaboration](hop-multi-device-collaboration.md) at the application component level**
 
    The stage model decouples application components from User Interfaces (UIs).
@@ -38,7 +37,7 @@ The stage model is designed based on the following considerations, which make it
 
    The stage model redefines the boundary of application capabilities to well balance application capabilities and system management costs.
 
-   - Diverse application components (such as widgets and input methods) for specific scenarios.
+   - Diverse application components (such as service widgets and input methods) for specific scenarios.
    - Standardized background process management. To deliver a better user experience, the stage model manages background application processes in a more orderly manner. Applications cannot reside in the background randomly, and their background behavior is strictly managed to minimize malicious behavior.
 
 
@@ -52,8 +51,8 @@ The table below describes their differences in detail.
 
 | Item| FA model| Stage model|
 | -------- | -------- | -------- |
-| **Application component**| 1. Component classification<br>![fa-model-component](figures/fa-model-component.png)<br/>- PageAbility: has the UI and supports user interaction For details, see [PageAbility Component Overview](pageability-overview.md).<br>- ServiceAbility: provides background services and has no UI. For details, see [ServiceAbility Component Overview](serviceability-overview.md).<br>- DataAbility: provides the data sharing capability and has no UI. For details, see [DataAbility Component Overview](dataability-overview.md).<br>2. Development mode<br>Application components are specified by exporting anonymous objects and fixed entry files. You cannot perform derivation. It is inconvenient for capability expansion. | 1. Component classification<br>![stage-model-component](figures/stage-model-component.png)<br/> - UIAbility: has the UI and supports user interaction. For details, see [UIAbility Component Overview](uiability-overview.md).<br>- ExtensionAbility: provides extension capabilities (such as widget and input methods) for specific scenarios. For details, see [ExtensionAbility Component Overview](extensionability-overview.md).<br>2. Development mode<br>The object-oriented mode is used to provide open application components as classes. You can derive application components for capability expansion. |
-| **Process model**| There are two types of processes:<br>1. Main process<br>2. Rendering process<br>For details, see [Process Model (FA Model)](process-model-fa.md).| There are three types of processes:<br>1. Main process<br>2. ExtensionAbility process<br>3. Rendering process<br>For details, see [Process Model (Stage Model)](process-model-stage.md).|
-| **Thread model**| 1. ArkTS engine instance creation<br>A process can run multiple application component instances, and each application component instance runs in an independent ArkTS engine instance.<br>2. Thread model<br>Each ArkTS engine instance is created on an independent thread (non-main thread). The main thread does not have an ArkTS engine instance.<br>3. Intra-process object sharing: not supported.<br>For details, see [Thread Model (FA Model)](thread-model-fa.md).| 1. ArkTS engine instance creation<br>A process can run multiple application component instances, and all application component instances share one ArkTS engine instance.<br>2. Thread model<br>The ArkTS engine instance is created on the main thread.<br>3. Intra-process object sharing: supported.<br>For details, see [Thread Model (Stage Model)](thread-model-stage.md).|
+| **Application component**| 1. Component classification<br>![fa-model-component](figures/fa-model-component.png)<br>- PageAbility: has the UI and supports user interaction For details, see [PageAbility Component Overview](pageability-overview.md).<br>- ServiceAbility: provides background services and has no UI. For details, see [ServiceAbility Component Overview](serviceability-overview.md).<br>- DataAbility: provides the data sharing capability and has no UI. For details, see [DataAbility Component Overview](dataability-overview.md).<br>2. Development mode<br>Application components are specified by exporting anonymous objects and fixed entry files. You cannot perform derivation. It is inconvenient for capability expansion.| 1. Component classification<br>![stage-model-component](figures/stage-model-component.png)<br>- UIAbility: has the UI and supports user interaction. For details, see [UIAbility Component Overview](uiability-overview.md).<br>- ExtensionAbility: provides extension capabilities (such as widget and input methods) for specific scenarios. For details, see [ExtensionAbility Component Overview](extensionability-overview.md).<br>2. Development mode<br>The object-oriented mode is used to provide open application components as classes. You can derive application components for capability expansion.|
+| **Process model**| There are two types of processes:<br>1. Main process<br>2. Rendering process<br>For details, see [Process Model Overview (FA Model)](process-model-fa.md). | There are three types of processes:<br>1. Main process<br>2. ExtensionAbility process<br>3. Rendering process<br>For details, see [Process Model Overview (Stage Model)](process-model-stage.md). |
+| **Thread model**| 1. ArkTS engine instance creation<br>A process can run multiple application component instances, and each application component instance runs in an independent ArkTS engine instance.<br>2. Thread model<br>Each ArkTS engine instance is created on an independent thread (non-main thread). The main thread does not have an ArkTS engine instance.<br>3. Intra-process object sharing: not supported.<br>For details, see [Thread Model Overview (FA Model)](thread-model-fa.md). | 1. ArkTS engine instance creation<br>A process can run multiple application component instances, and all application component instances share one ArkTS engine instance.<br>2. Thread model<br>The ArkTS engine instance is created on the main thread.<br>3. Intra-process object sharing: supported.<br>For details, see [Thread Model Overview (Stage Model)](thread-model-stage.md). |
 | **Mission management model**| - A mission is created for each PageAbility component instance.<br>- Missions are stored persistently until the number of missions exceeds the maximum (customized based on the product configuration) or users delete missions.<br>- PageAbility components do not form a stack structure.<br>For details, see [Mission Management Scenarios](mission-management-overview.md).| - A mission is created for each UIAbility component instance.<br>- Missions are stored persistently until the number of missions exceeds the maximum (customized based on the product configuration) or users delete missions.<br>- UIAbility components do not form a stack structure.<br>For details, see [Mission Management Scenarios](mission-management-overview.md).|
 | **Application configuration file**| The **config.json** file is used to describe the application, HAP, and application component information.<br>For details, see [Application Configuration File Overview (FA Model)](../quick-start/application-configuration-file-overview-fa.md).| The **app.json5** file is used to describe the application information, and the **module.json5** file is used to describe the HAP and application component information.<br>For details, see [Application Configuration File Overview (Stage Model)](../quick-start/application-configuration-file-overview-stage.md).|

en/application-dev/application-models/arkts-ui-widget-configuration.md

@@ -32,7 +32,7 @@ Widget-related configuration includes **FormExtensionAbility** configuration and
    }
    ```
 
-2. Configure the widget configuration information. In the **metadata** configuration item of FormExtensionAbility, you can specify the resource index of specific configuration information of the widget. For example, if resource is set to **$profile:form_config**, **form_config.json** in the **resources/base/profile/** directory of the development view is used as the profile configuration file of the widget. The following table describes the internal field structure.
+2. Configure the widget configuration information. In the **metadata** configuration item of FormExtensionAbility, you can specify the resource index of specific configuration information of the widget. For example, if **resource** is set to **$profile:form_config**, **form_config.json** in the **resources/base/profile/** directory of the development view is used as the profile configuration file of the widget. The following table describes the internal structure of the profile configuration file.
 
    **Table 1** form_config.json file
 
@@ -47,8 +47,8 @@ Widget-related configuration includes **FormExtensionAbility** configuration and
    | colorMode | Color mode of the widget.<br>- **auto**: auto-adaptive color mode<br>- **dark**: dark color mode<br>- **light**: light color mode| String| Yes (initial value: **auto**)|
    | supportDimensions | Grid styles supported by the widget.<br>- **1 * 2**: indicates a grid with one row and two columns.<br>- **2 * 2**: indicates a grid with two rows and two columns.<br>- **2 * 4**: indicates a grid with two rows and four columns.<br>- **4 * 4**: indicates a grid with four rows and four columns.| String array| No|
    | defaultDimension | Default grid style of the widget. The value must be available in the **supportDimensions** array of the widget.| String| No|
-   | updateEnabled | Whether the widget can be updated periodically.<br>- **true**: The widget can be updated at a specified interval (**updateDuration**) or at the scheduled time (**scheduledUpdateTime**). **updateDuration** takes precedence over **scheduledUpdateTime**.<br>- **false**: The widget cannot be updated periodically.| Boolean| No|
-   | scheduledUpdateTime | Scheduled time to update the widget. The value is in 24-hour format and accurate to minute.<br>**NOTE**<br>**updateDuration** takes precedence over **scheduledUpdateTime**. If both are specified, the value specified by **updateDuration** is used.| String| Yes (initial value: The widget cannot be updated periodically.）|
+   | updateEnabled | Whether the widget can be updated periodically.<br>- **true**: The widget can be updated at a specified interval (**updateDuration**) or at the scheduled time (**scheduledUpdateTime**). **updateDuration** takes precedence over **scheduledUpdateTime**. If both are specified, the value specified by **updateDuration** is used.<br>- **false**: The widget cannot be updated periodically.| Boolean| No|
+   | scheduledUpdateTime | Scheduled time to update the widget. The value is in 24-hour format and accurate to minute.<br>**NOTE**<br>**updateDuration** takes precedence over **scheduledUpdateTime**. If both are specified, the value specified by **updateDuration** is used.| String| Yes (initial value: The widget is not updated at the scheduled time.)|
    | updateDuration | Interval to update the widget. The value is a natural number, in the unit of 30 minutes.<br>If the value is **0**, this field does not take effect.<br>If the value is a positive integer *N*, the interval is calculated by multiplying *N* and 30 minutes.<br>**NOTE**<br>**updateDuration** takes precedence over **scheduledUpdateTime**. If both are specified, the value specified by **updateDuration** is used.| Number| Yes (initial value: **0**)|
    | formConfigAbility | Link to a specific page of the application. The value is a URI.| String| Yes (initial value: left empty)|
    | formVisibleNotify | Whether the widget is allowed to use the widget visibility notification.| String| Yes (initial value: left empty)|

en/application-dev/application-models/arkts-ui-widget-creation.md

@@ -3,9 +3,9 @@
 To create an ArkTS widget in an existing application project, perform the following steps:
 
 1. Create a widget.
-
+   
    ![WidgetProjectCreate1](figures/WidgetProjectCreate1.png)
-
+   
 2. Select a widget template based on the actual service scenario.
 
    ![WidgetProjectCreate2](figures/WidgetProjectCreate2.png)
@@ -14,6 +14,6 @@ To create an ArkTS widget in an existing application project, perform the follow
 
    ![WidgetProjectCreate3](figures/WidgetProjectCreate3.png)
 
-After an ArkTS widget is created, the following widget-related files are added to the project directory: **EntryFormAbility.ts** (widget lifecycle management file), **WidgetCard.ets** (widget page file), and **form_config.json** (widget configuration file).
+After an ArkTS widget is created, the following widget-related files are automatically added to the project directory: **EntryFormAbility.ts** (widget lifecycle management file), **WidgetCard.ets** (widget page file), and **form_config.json** (widget configuration file).
 
-![WidgetProjectView](figures/WidgetProjectView.png)
+![WidgetProjectView](figures/WidgetProjectView.png)
\ No newline at end of file

en/application-dev/application-models/arkts-ui-widget-event-call.md

+# Launching a UIAbility in the Background Through the call Event
+
+
+There may be cases you want to provide in a widget access to features available in your application running in the foreground, for example, the play, pause, and stop buttons in a music application widget. This is where the **call** capability of the **postCardAction** API comes in handy. This capability, when used in a widget, can start the specified UIAbility of the widget provider in the background. It also allows the widget to call the specified method of the application and transfer data so that the application, while in the background, can behave accordingly in response to touching of the buttons on the widget.
+
+
+Typically, the call event is triggered for touching of buttons. Below is an example.
+
+
+- In this example, two buttons are laid out on the widget page. When one button is clicked, the **postCardAction** API is called to send a call event to the target UIAbility. Note that the **method** parameter in the API indicates the method to call in the target UIAbility. It is mandatory and of the string type.
+  
+  ```ts
+  @Entry
+  @Component
+  struct WidgetCard {
+    build() {
+      Column() {
+        Button ('Feature A')
+          .margin('20%')
+          .onClick(() => {
+            console.info('call EntryAbility funA');
+            postCardAction(this, {
+              'action': 'call',
+              'abilityName': 'EntryAbility', // Only the UIAbility of the current application is allowed.
+              'params': {
+                'method': 'funA' // Set the name of the method to call in the EntryAbility.
+              }
+            });
+          })
+  
+        Button ('Feature B')
+          .margin('20%')
+          .onClick(() => {
+            console.info('call EntryAbility funB');
+            postCardAction(this, {
+              'action': 'call',
+              'abilityName': 'EntryAbility', // Only the UIAbility of the current application is allowed.
+              'params': {
+                'method': 'funB', // Set the name of the method to call in the EntryAbility.
+                'num': 1 // Set other parameters to be passed in.
+              }
+            });
+          })
+      }
+      .width('100%')
+      .height('100%')
+    }
+  }
+  ```
+
+- The UIAbility receives the call event and obtains the transferred parameters. It then executes the target method specified by the **method** parameter. Other data can be obtained in readString mode. Listen for the method required by the call event in the **onCreate** callback of the UIAbility.
+  
+  ```ts
+  import UIAbility from '@ohos.app.ability.UIAbility';
+  
+  function FunACall(data) {
+    // Obtain all parameters passed in the call event.
+    console.info('FunACall param:' + JSON.stringify(data.readString()));
+    return null;
+  }
+  
+  function FunBCall(data) {
+    console.info('FunBCall param:' + JSON.stringify(data.readString()));
+    return null;
+  }
+  
+  export default class CameraAbility extends UIAbility {
+    // If the UIAbility is started for the first time, onCreate is triggered afte the call event is received.
+    onCreate(want, launchParam) {
+      try {
+        // Listen for the method required by the call event.
+        this.callee.on('funA', FunACall);
+        this.callee.on('funB', FunBCall);
+      } catch (err) {
+        console.error(`Failed to register callee on. Cause: ${JSON.stringify(err)}`);
+      }
+    }
+  
+    ...
+  
+    // Deregister the listener when the process exits.
+    onDestroy() {
+      try {
+        this.callee.off('funA');
+        this.callee.off('funB');
+      } catch (err) {
+        console.error(`Failed to register callee off. Cause: ${JSON.stringify(err)}`);
+      }
+    }
+  };
+  ```

en/application-dev/application-models/arkts-ui-widget-event-formextensionability.md

-# Updating Widget Content Through FormExtensionAbility
+# Updating Widget Content Through the message Event
 
 
-On the widget page, the **postCardAction** API can be used to trigger a message event to the FormExtensionAbility, which then updates the widget content. The following is an example of this widget update mode.
+On the widget page, the **postCardAction** API can be used to trigger a message event to start a FormExtensionAbility, which then updates the widget content. The following is an example of this widget update mode.
 
 
 - On the widget page, register the **onClick** event callback of the button and call the **postCardAction** API in the callback to trigger the event to the FormExtensionAbility.
@@ -57,10 +57,10 @@ On the widget page, the **postCardAction** API can be used to trigger a message
       })
     }
   
-    // ...
+    ...
   }
   ```
 
   The figure below shows the effect.
-
+  
   ![WidgetUpdatePage](figures/WidgetUpdatePage.png)

en/application-dev/application-models/arkts-ui-widget-event-overview.md

 # Widget Event Capability Overview
 
-
 The ArkTS widget provides the **postCardAction()** API for interaction between the widget internal and the provider application. Currently, this API supports the router, message, and call events and can be called only in the widget.
 
-
 ![WidgetPostCardAction](figures/WidgetPostCardAction.png)
 
+**Definition**: postCardAction(component: Object, action: Object): void
 
-Definition: postCardAction(component: Object, action: Object): void
-
-
-Parameters:
-
+**Parameters**
 
 | Name| Type| Mandatory| Description|
 | -------- | -------- | -------- | -------- |
 | component | Object | Yes| Instance of the current custom component. Generally, **this** is transferred.|
 | action | Object | Yes| Action description. For details, see the following table.|
 
+**Description of the action parameter**
 
-Description of the action parameter
-
-
-| **Key** | **Value** | Description|
+| Key | Value | Description|
 | -------- | -------- | -------- |
-| "action" | string | Action type.<br>- **"router"**: application redirection. If this type of action is triggered, the corresponding UIAbility is displayed. Only the UIAbility of the current application can be displayed.<br>- **"message"**: custom message. If this type of action is triggered, the [onFormEvent()](../reference/apis/js-apis-app-form-formExtensionAbility.md#onformevent) lifecycle callback of the provider FormExtensionAbility is called.<br>- **"call"**: application startup in the background. If this type of action is triggered, the corresponding UIAbility is started but does not run in the foreground. The target application must have the permission to run in the background ([ohos.permission.KEEP_BACKGROUND_RUNNING](../security/permission-list.md#ohospermissionkeep_background_running)).|
+| "action" | string | Action type.<br>- **"router"**: redirection to the specified UIAbility of the widget provider.<br>- **"message"**: custom message. If this type of action is triggered, the [onFormEvent()](../reference/apis/js-apis-app-form-formExtensionAbility.md#onformevent) lifecycle callback of the provider FormExtensionAbility is called.<br>- **"call"**: launch of the widget provider in the background. If this type of action is triggered, the specified UIAbility of the widget provider is started in the background, but not displayed in the foreground. This action type requires that the widget provider should have the [ohos.permission.KEEP_BACKGROUND_RUNNING](../security/permission-list.md#ohospermissionkeep_background_running) permission.|
 | "bundleName" | string | Name of the target bundle when **action** is **"router"** or **"call"**. This parameter is optional.|
 | "moduleName" | string | Name of the target module when **action** is **"router"** or **"call"**. This parameter is optional.|
 | "abilityName" | string | Name of the target UIAbility when **action** is **"router"** or **"call"**. This parameter is mandatory.|
-| "params" | Object | Additional parameters carried in the current action. The value is a key-value pair in JSON format.|
+| "params" | Object | Additional parameters carried in the current action. The value is a key-value pair in JSON format. For the **"call"** action type, the **method** parameter must be set and its value type must be string. This parameter is mandatory.|
 
 
 Sample code of the **postCardAction()** API:
 
-
-
 ```typescript
 Button ('Jump')
   .width('40%')
@@ -45,18 +36,26 @@ Button ('Jump')
       'bundleName': 'com.example.myapplication',
       'abilityName': 'EntryAbility',
       'params': {
-        'message': 'testForRouter' // Customize the message to be sent.
+        'message': 'testForRouter' // Customize the message to send.
       }
     });
   })
-```
-
-
-The following are typical widget development scenarios that can be implemented through widget events:
 
+Button ('Start in Background')
+  .width('40%')
+  .height('20%')
+  .onClick(() => {
+    postCardAction(this, {
+      'action': 'call',
+      'bundleName': 'com.example.myapplication',
+      'abilityName': 'EntryAbility',
+      'params': {
+        'method': 'fun', // Set the name of the method to call. It is mandatory.
+        'message': 'testForcall' // Customize the message to send.
+      }
+    });
+  })
+```
 
-- [Updating Widget Content Through FormExtensionAbility](arkts-ui-widget-event-formextensionability.md)
-
-- [Updating Widget Content Through UIAbility](arkts-ui-widget-event-uiability.md)
 
-- [Redirecting to a Specified Page Through the Router Event](arkts-ui-widget-event-router.md)
+Read on to learn the typical widget development scenarios that can be implemented through widget events.

en/application-dev/application-models/arkts-ui-widget-event-router.md

-# Redirecting to a Specified Page Through the Router Event
-
-
-The **router** capability of the **postCardAction** API can be used in a widget to quickly start the widget provider application. An application can provide different buttons through the widget so that users can jump to different pages at the touch of a button. For example, a camera widget provides the buttons that direct the user to respective pages, such as the page for taking a photo and the page for recording a video.
+# Redirecting to a UIAbility Through the router Event
 
+The **router** capability of the **postCardAction** API can be used in a widget to quickly start a specific UIAbility of the widget provider. By leveraging this capability, an application can provide in the widget multiple buttons, each of which targets a different target UIAbility. For example, a camera widget can provide the buttons that redirect the user to the UIAbility for taking a photo and the UIAbility for recording a video.
 
 ![WidgerCameraCard](figures/WidgerCameraCard.png)
 

en/application-dev/application-models/arkts-ui-widget-event-uiability.md

-# Updating Widget Content Through UIAbility
+# Updating Widget Content Through the router or call Event
 
 
-On the widget page, the **postCardAction** API can be used to trigger a router or call event to start the UIAbility, which then updates the widget content. The following is an example of this widget update mode.
+On the widget page, the **postCardAction** API can be used to trigger a router or call event to start a UIAbility, which then updates the widget content. The following is an example of this widget update mode.
 
+## Updating Widget Content Through the router Event
 
-- On the widget page, register the **onClick** event callback of the button and call the **postCardAction** API in the callback to trigger the event to the FormExtensionAbility.
+- On the widget page, register the **onClick** event callback of the button and call the **postCardAction** API in the callback to trigger the router event to the FormExtensionAbility.
   
   ```ts
   let storage = new LocalStorage();
@@ -44,7 +45,7 @@ On the widget page, the **postCardAction** API can be used to trigger a router o
   import formInfo from '@ohos.app.form.formInfo';
   
   export default class EntryAbility extends UIAbility {
-    // If the UIAbility is started for the first time, the onCreate lifecycle callback is triggered after the router event is received.
+    // If the UIAbility is started for the first time, onCreate is triggered after the router event is received.
     onCreate(want, launchParam) {
       console.info('Want:' + JSON.stringify(want));
       if (want.parameters[formInfo.FormParam.IDENTITY_KEY] !== undefined) {
@@ -62,7 +63,7 @@ On the widget page, the **postCardAction** API can be used to trigger a router o
         })
       }
     }
-    // If the UIAbility is running in the background, the onNewWant lifecycle callback is triggered after the router event is received.
+    // If the UIAbility is running in the background, onNewWant is triggered after the router event is received.
     onNewWant(want, launchParam) {
       console.info('onNewWant Want:' + JSON.stringify(want));
       if (want.parameters[formInfo.FormParam.IDENTITY_KEY] !== undefined) {
@@ -84,3 +85,103 @@ On the widget page, the **postCardAction** API can be used to trigger a router o
     ...
   }
   ```
+
+## Updating Widget Content Through the call Event
+
+- When using the call event of the **postCardAction** API, the value of **formId** must be updated in the **onAddForm** callback of the FormExtensionAbility.
+  
+   ```ts
+   import formBindingData from '@ohos.app.form.formBindingData';
+   import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
+   
+   export default class EntryFormAbility extends FormExtensionAbility {
+     onAddForm(want) {
+      let formId = want.parameters["ohos.extra.param.key.form_identity"];
+      let dataObj1 = {
+        "formId": formId
+      };
+      let obj1 = formBindingData.createFormBindingData(dataObj1);
+      return obj1;
+    }
+    
+     ...
+   };
+   ```
+
+- On the widget page, register the **onClick** event callback of the button and call the **postCardAction** API in the callback to trigger the event to the UIAbility.
+  
+  ```ts
+  let storage = new LocalStorage();
+  @Entry(storage)
+  @Component
+  struct WidgetCard {
+    @LocalStorageProp('detail') detail: string = 'init';
+    @LocalStorageProp('formId') formId: string = '0';
+  
+    build() {
+      Column() {
+        Button ('Start in Background')
+          .margin('20%')
+          .onClick(() => {
+            console.info('postCardAction to EntryAbility');
+            postCardAction(this, {
+              'action': 'call',
+              'abilityName': 'EntryAbility', // Only the UIAbility of the current application is allowed.
+              'params': {
+                'method': 'funA',
+                'formId': this.formId,
+                'detail': 'CallFromCard'
+              }
+            });
+          })
+        Text(`${this.detail}`).margin('20%')
+      }
+      .width('100%')
+      .height('100%')
+    }
+  }
+  ```
+  
+- Listen for the method required by the call event in the **onCreate** callback of the UIAbility, and then call the [updateForm](../reference/apis/js-apis-app-form-formProvider.md#updateform) API in the corresponding method to update the widget.
+  
+  ```ts
+  import UIAbility from '@ohos.app.ability.UIAbility';
+  import formBindingData from '@ohos.app.form.formBindingData';
+  import formProvider from '@ohos.app.form.formProvider';
+  
+  const MSG_SEND_METHOD: string = 'funA';
+  
+  // After the call event is received, the method listened for by the callee is triggered.
+  function FunACall(data) {
+    // Obtain all parameters transferred in the call event.
+    let params = JSON.parse(data.readString())
+    if (params.formId !== undefined) {
+      let curFormId = params.formId;
+      let message = params.detail;
+      console.info(`UpdateForm formId: ${curFormId}, message: ${message}`);
+      let formData = {
+        "detail": message
+      };
+      let formMsg = formBindingData.createFormBindingData(formData)
+      formProvider.updateForm(curFormId, formMsg).then((data) => {
+        console.info('updateForm success.' + JSON.stringify(data));
+      }).catch((error) => {
+        console.error('updateForm failed:' + JSON.stringify(error));
+      })
+    }
+    return null;
+  }
+  export default class EntryAbility extends UIAbility {
+    // If the UIAbility is started for the first time, onCreate is triggered after the call event is received.
+    onCreate(want, launchParam) {
+      console.info('Want:' + JSON.stringify(want));
+      try {
+         // Listen for the method required by the call event.
+        this.callee.on(MSG_SEND_METHOD, FunACall);
+      } catch (error) {
+        console.info(`${MSG_SEND_METHOD} register failed with error ${JSON.stringify(error)}`)
+      }
+    }
+    ...
+  }
+  ```

en/application-dev/application-models/arkts-ui-widget-image-update.md

 # Updating Local and Online Images in the Widget
 
 
-Generally, local images or online images downloaded from the network need to be displayed on a widget. To obtain local and online images, use the FormExtensionAbility. The following exemplifies how to show local and online images on a widget.
+Typically, a widget includes local images or online images downloaded from the network. To obtain local and online images, use the FormExtensionAbility. The following exemplifies how to show local and online images on a widget.
 
 
-1. Internet access is required for downloading online images. Therefore, you need to apply for the **ohos.permission.INTERNET** permission. For details, see[Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md).
+1. For the widget to download online images, declare the **ohos.permission.INTERNET** permission for the widget. For details, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md).
 
 2. Update local files in the **onAddForm** lifecycle callback of the EntryFormAbility.
    
@@ -44,7 +44,7 @@ Generally, local images or online images downloaded from the network need to be
    }
    ```
 
-3. Update online files in the onFormEvent lifecycle callback of the EntryFormAbility.
+3. Update online images in the **onFormEvent** lifecycle callback of the EntryFormAbility.
    
    ```ts
    import formBindingData from '@ohos.app.form.formBindingData';
@@ -60,8 +60,8 @@ Generally, local images or online images downloaded from the network need to be
          'text': 'Updating...'
        })
        formProvider.updateForm(formId, formInfo)
-       // Note: The FormExtensionAbility is started when the lifecycle callback is triggered. It can run  in the background for only 5 seconds.
-       // When possible, limit the size of the image to download. If an image cannot be downloaded within 5 seconds, it cannot be updated to the widget page.
+       // Note: After being started with the triggering of the lifecycle callback, the FormExtensionAbility can run in the background for only 5 seconds.
+       // When possible, limit the size of the image to download. If an image cannot be downloaded within 5 seconds, it will not be updated to the widget page.
        let netFile = 'https://xxxx/xxxx.png'; // Specify the URL of the image to download.
        let tempDir = this.context.getApplicationContext().tempDir;
        let fileName = 'file' + Date.now();
@@ -161,6 +161,6 @@ Generally, local images or online images downloaded from the network need to be
    ```
 
 > **NOTE**
-> - The **\<Image>** component displays images in the remote memory based on the **memory://** identifier in the input parameter (**memory://fileName**). The **fileName** value must be consistent with the key in the object (**'formImages': {key: fd}**) passed by the EntryFormAbility.
+> - The **\<Image>** component displays images in the remote memory based on the **memory://** identifier in the input parameter (**memory://fileName**). The value of **fileName** must be consistent with the key in the object (**'formImages': {key: fd}**) passed by the EntryFormAbility.
 > 
-> - The **\<Image>** component determines whether to update the image based on whether the input parameter is changed. Therefore, the value of **imgName** passed by the EntryFormAbility each time must be different. If the two values of **imgName** passed consecutively are identical, the image is not updated.
+> - The **\<Image>** component determines whether to update the image by comparing the values of **imgName** consecutively passed by the EntryFormAbility. It updates the image only when the values are different.

en/application-dev/application-models/arkts-ui-widget-interaction-overview.md

 # Widget Data Interaction
 
-
 The ArkTS widget framework provides the **updateForm()** and **requestForm()** APIs to proactively trigger widget updates.
 
-
 ![WidgetLocalStorageProp](figures/WidgetLocalStorageProp.png)
 
 
 | API| System Capability| Constraints|
 | -------- | -------- | -------- |
-| updateForm | No| 1. Invoked by the provider.<br>2. Allows only the widget provider to update its own widgets. It cannot be used to update widgets by other providers.|
-| requestForm | Yes| 1. Invoked by the host.<br>2. Allows only the widget host to update the widgets added to it. It cannot be used to update widgets added to other hosts.|
+| updateForm | No| 1. Invoked by the widget provider.<br>2. Allows only the widget provider to update its own widgets.|
+| requestForm | Yes| 1. Invoked by the widget host.<br>2. Allows only the widget host to update the widgets added to it.|
 
-The following describes the typical use cases of widget updates:
+The following are the typical use cases of widget updates:
 
 - [Configuring a Widget to Update Periodically](arkts-ui-widget-update-by-time.md)
+- [Updating Widget Content Through a Proxy](arkts-ui-widget-update-by-proxy.md)
 - [Updating Local and Online Images](arkts-ui-widget-image-update.md)
 - [Updating Widget Content by State](arkts-ui-widget-update-by-status.md)
 - [Updating Widget Content by Widget Host (for System Applications Only)](arkts-ui-widget-content-update.md)

en/application-dev/application-models/arkts-ui-widget-lifecycle.md

@@ -92,4 +92,5 @@ When creating an ArkTS widget, you need to implement the [FormExtensionAbility](
 
 
 > **NOTE**
-> The FormExtensionAbility cannot reside in the background. Therefore, continuous tasks cannot be processed in the widget lifecycle callbacks. The FormExtensionAbility persists for 5 seconds after the lifecycle callback is completed and will exit if no new lifecycle callback is invoked during this time frame. For the service logic that may take more than 5 seconds to complete, it is recommended that you [start the application](arkts-ui-widget-event-uiability.md). After the processing is complete, use the [updateForm](../reference/apis/js-apis-app-form-formProvider.md#updateform) to notify the widget of the update.
+>
+> The FormExtensionAbility cannot reside in the background. It persists for 5 seconds after the lifecycle callback is completed and exist if no new lifecycle callback is invoked during this time frame. This means that continuous tasks cannot be processed in the widget lifecycle callbacks. For the service logic that may take more than 5 seconds to complete, it is recommended that you [start the application](arkts-ui-widget-event-uiability.md) for processing. After the processing is complete, use [updateForm()](../reference/apis/js-apis-app-form-formProvider.md#updateform) to notify the widget of the update.

en/application-dev/application-models/arkts-ui-widget-modules.md

 # ArkTS Widget Related Modules
 
+**Figure 1** ArkTS widget related modules
 
-  **Figure 1** ArkTS widget related modules 
 ![WidgetModules](figures/WidgetModules.png)
 
 
@@ -15,10 +15,10 @@
 
 - [formBindingData](../reference/apis/js-apis-app-form-formBindingData.md): provides APIs for widget data binding. You can use the APIs to create a **FormBindingData** object and obtain related information.
 
-- [Page Layout (Card.ets)](arkts-ui-widget-page-overview.md): provides APIs for a declarative paradigm UI.
-  - [ArkTS widget capabilities](arkts-ui-widget-event-overview.md): include the **postCardAction** API used for interaction between the widget internal and the provider application and can be called only in the widget.
-  - [ArkTS widget capability list](arkts-ui-widget-page-overview.md#page-capabilities-supported-by-arkts-widgets): lists the APIs, components, events, attributes, and lifecycle callbacks that can be used in ArkTS widgets.
+- [Page layout (Card.ets)](arkts-ui-widget-page-overview.md): provides APIs for a declarative paradigm UI.
+  - [Capabilities exclusive to ArkTS widgets](arkts-ui-widget-event-overview.md): include the **postCardAction** API used for interaction between the widget internal and the provider application and can be called only in the widget.
+  - [ArkTS widget capability list](arkts-ui-widget-page-overview.md#page-capabilities-supported-by-arkts-widgets): contain the APIs, components, events, attributes, and lifecycle callbacks that can be used in ArkTS widgets.
 
 - [Widget configuration](arkts-ui-widget-configuration.md): includes FormExtensionAbility configuration and widget configuration.
-  - Configure FormExtensionAbility information under **extensionAbilities** in the [module.json5 file](../quick-start/module-configuration-file.md).
+  - Configure the FormExtensionAbility information under **extensionAbilities** in the [module.json5 file](../quick-start/module-configuration-file.md).
   - Configure the widget configuration information (**WidgetCard.ets**) in the [form_config.json](arkts-ui-widget-configuration.md) file in **resources/base/profile**.

en/application-dev/application-models/arkts-ui-widget-page-animation.md

 # Using Animations in the Widget
 
 
-To make your ArkTS widget more engaging, you can apply animations to it, including [explicit animation](../reference/arkui-ts/ts-explicit-animation.md), [attribute animation](../reference/arkui-ts/ts-animatorproperty.md), and [component transition](../reference/arkui-ts/ts-transition-animation-component.md). Note the following restrictions when using the animations in ArkTS widgets.
+To make your ArkTS widget more engaging, you can apply animations to it, including [explicit animation](../reference/arkui-ts/ts-explicit-animation.md), [attribute animation](../reference/arkui-ts/ts-animatorproperty.md), and [component transition](../reference/arkui-ts/ts-transition-animation-component.md). Just note the following restrictions when using the animations in ArkTS widgets.
 
 
-  **Table 1** Restrictions on animation parameters
+**Table 1** Restrictions on animation parameters
 
 | Name| Description| Description|
 | -------- | -------- | -------- |
@@ -13,14 +13,10 @@ To make your ArkTS widget more engaging, you can apply animations to it, includi
 | delay | Animation delay duration.| Do not set this parameter in the widget. Use the default value 0.|
 | iterations | Number of times that the animation is played.| Do not set this parameter in the widget. Use the default value 1.|
 
-
 The following sample code implements the animation effect of button rotation:
 
-
 ![WidgetAnimation](figures/WidgetAnimation.gif)
 
-
-
 ```ts
 @Entry
 @Component

en/application-dev/application-models/arkts-ui-widget-page-custom-drawing.md

 # Applying Custom Drawing in the Widget
 
 
-  You can apply custom drawing in your ArkTS widget to create a more vibrant experience. Use the [Canvas](../reference/arkui-ts/ts-components-canvas-canvas.md) component to create a canvas on the widget, and then use the [CanvasRenderingContext2D](../reference/arkui-ts/ts-canvasrenderingcontext2d.md) object to draw custom graphics on the canvas. The following code shows how to draw a smiling face in the center of the canvas.
+You can apply custom drawing in your ArkTS widget to create a more vibrant experience. Use the [Canvas](../reference/arkui-ts/ts-components-canvas-canvas.md) component to create a canvas on the widget, and then use the [CanvasRenderingContext2D](../reference/arkui-ts/ts-canvasrenderingcontext2d.md) object to draw custom graphics on the canvas. The following code snippet draws a smiling face in the center of a canvas.
 
-```typescript
+```ts
 @Entry
 @Component
 struct Card {
@@ -30,41 +30,41 @@ struct Card {
             this.context.fillRect(0, 0, this.canvasWidth, this.canvasHeight);
             // Draw a red circle in the center of the canvas.
             this.context.beginPath();
-            let radius = this.context.width / 3
-            let circleX = this.context.width / 2
-            let circleY = this.context.height / 2
+            let radius = this.context.width / 3;
+            let circleX = this.context.width / 2;
+            let circleY = this.context.height / 2;
             this.context.moveTo(circleX - radius, circleY);
             this.context.arc(circleX, circleY, radius, 2 * Math.PI, 0, true);
             this.context.closePath();
             this.context.fillStyle = 'red';
             this.context.fill();
             // Draw the left eye of the smiling face.
-            let leftR = radius / 4
-            let leftX = circleX - (radius / 2)
-            let leftY = circleY - (radius / 3.5)
+            let leftR = radius / 4;
+            let leftX = circleX - (radius / 2);
+            let leftY = circleY - (radius / 3.5);
             this.context.beginPath();
             this.context.arc(leftX, leftY, leftR, 0, Math.PI, true);
-            this.context.strokeStyle = '#ffff00'
-            this.context.lineWidth = 10
-            this.context.stroke()
+            this.context.strokeStyle = '#ffff00';
+            this.context.lineWidth = 10;
+            this.context.stroke();
             // Draw the right eye of the smiling face.
-            let rightR = radius / 4
-            let rightX = circleX + (radius / 2)
-            let rightY = circleY - (radius / 3.5)
+            let rightR = radius / 4;
+            let rightX = circleX + (radius / 2);
+            let rightY = circleY - (radius / 3.5);
             this.context.beginPath();
             this.context.arc(rightX, rightY, rightR, 0, Math.PI, true);
-            this.context.strokeStyle = '#ffff00'
-            this.context.lineWidth = 10
-            this.context.stroke()
+            this.context.strokeStyle = '#ffff00';
+            this.context.lineWidth = 10;
+            this.context.stroke();
             // Draw the mouth of the smiling face.
-            let mouthR = radius / 2.5
-            let mouthX = circleX
-            let mouthY = circleY + (radius / 3)
+            let mouthR = radius / 2.5;
+            let mouthX = circleX;
+            let mouthY = circleY + (radius / 3);
             this.context.beginPath();
             this.context.arc(mouthX, mouthY, mouthR, Math.PI, 0, true);
-            this.context.strokeStyle = '#ffff00'
-            this.context.lineWidth = 10
-            this.context.stroke()
+            this.context.strokeStyle = '#ffff00';
+            this.context.lineWidth = 10;
+            this.context.stroke();
           })
       }
     }.height('100%').width('100%')
@@ -72,8 +72,6 @@ struct Card {
 }
 ```
 
-
 The figure below shows the effect.
 
-
-![WidgetCanvasDemo](figures/WidgetCanvasDemo.jpeg)
+![WidgetCanvasDemo](figures/WidgetCanvasDemo.png)
\ No newline at end of file

en/application-dev/application-models/arkts-ui-widget-page-overview.md

 # Widget Page Capability Overview
 
-
 You can leverage the ArkUI declarative paradigm to develop ArkTS widget pages. The following widget pages are automatically generated by a DevEco Studio template. You can adjust the pages based on the real-world service scenarios.
 
-
 ![WidgetPreviewPage](figures/WidgetPreviewPage.png)
 
 
-ArkTS widgets have full capabilities of JS widgets, with added animation and custom drawing capabilities plus partial support for components, events, animations, data management, and state management capabilities of the [declarative paradigm](../reference/arkui-ts/ts-components-summary.md). For details, see [Page Capabilities Supported by ArkTS Widgets](#page-capabilities-supported-by-arkts-widgets).
-
-
-## Page Capabilities Supported by ArkTS Widgets
+ArkTS widgets have full capabilities of JS widgets, with added animation and custom drawing capabilities plus partial support for components, events, animations, data management, and state management capabilities of the [declarative paradigm](../reference/arkui-ts/ts-components-summary.md).
 
-For details about the page capabilities supported by ArkTS widgets, see [Learning ArkTS](../quick-start/arkts-create-custom-components.md) and [ArkTS-based Declarative Development Paradigm](../reference/arkui-ts/ts-components-summary.md).
+For details about the capabilities supported by ArkTS widgets, see [Learning ArkTS](../quick-start/arkts-create-custom-components.md) and [ArkTS-based Declarative Development Paradigm](../reference/arkui-ts/ts-components-summary.md).
 
-Only the APIs marked with "supported in ArkTS widgets" can be used for ArkTS widgets. Pay special attention to the capability differences with applications.
+Only the APIs marked with "supported in ArkTS widgets" can be used for ArkTS widgets. Pay special attention to the differences from applications.
 
 For example, the following description indicates that the @Component decorator can be used in ArkTS widgets.
 
-![WidgetSupportApi](figures/WidgetSupportApi.png)
+![WidgetSupportApi](figures/WidgetSupportApi.png)
\ No newline at end of file

en/application-dev/application-models/arkts-ui-widget-update-by-proxy.md

+# Updating Widget Content Through a Proxy
+
+A widget can be updated through a proxy – a system application that has data sharing enabled – when the widget provider is not running.
+
+## Implementation Principles
+
+**Figure 1** Updating widget content through a proxy
+
+![UpdateWidgetByProxyPrinciple](figures/UpdateWidgetByProxyPrinciple.png)
+
+Compared with the [implementation of the ArkTS widget](../application-models/arkts-ui-widget-working-principles.md#implementation-principles) alone, updating through a proxy involves the data management service and data provider.
+
+- Data management service: provides a mechanism for data sharing among multiple applications.
+- Data provider: must be a system application that has data sharing enabled. The shared data is identified through the defined **key** + **subscriberId** combination.
+
+Processing flow of the widget provider (indicated by the blue arrows in the figure):
+
+1. The widget provider sets the **dataProxyEnabled** field to **true** in the **form_config.json** file to enable the update-through-proxy feature.
+> **NOTE**
+>
+> After the update-through-proxy feature is enabled, the settings for [updating periodically](../application-models/arkts-ui-widget-update-by-time.md) do not work.
+
+2. In the [onAddForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onaddform) callback, the widget provider returns the **key** + **subscriberId** combination defined by the data provider to the Widget Manager.
+
+3. Widget Manager parses the subscription information of the widget provider and registers a subscription instance with the data management service.
+
+Processing flow of the widget update proxy (indicated by the red arrows in the figure):
+
+1. The data provider uses the **key** + **subscriberId** combination as the data ID to store data to the database.
+2. The data management service detects the change in the database and publishes the new data to all currently registered subscription instances.
+3. The Widget Manager parses data from the subscription instance and sends the data to the widget rendering service.
+4. The widget rendering service runs the widget page code **widgets.abc**, renders based on the new data, and sends the rendered data to the widget component (../reference/arkui-ts/ts-basic-components-formcomponent.md) corresponding to the widget host.
+
+There are two types of shared data provided by the data provider:
+
+- Ephemeral data: data that exists only for a specific period of time and can be subscribed to by system and non-system applications alike.
+
+- Persistent data: data that persists over time and can only be subscribed to by system applications.
+
+The update-through-proxy configuration varies by the type of shared data.
+
+
+## Widget Provider Development (Ephemeral Data)
+
+- Set the **dataProxyEnabled** field to **true** in the **form_config.json** file to enable the update-through-proxy feature.
+  ```json
+  {
+    "forms": [
+      {
+        "name": "widget",
+        "description": "This is a service widget.",
+        "src": "./ets/widget/pages/WidgetCard.ets",
+        "uiSyntax": "arkts",
+        "window": {
+          "designWidth": 720,
+          "autoDesignWidth": true
+        },
+        "colorMode": "auto",
+        "isDefault": true,
+        "updateEnabled": true,
+        "scheduledUpdateTime": "10:30",
+        "defaultDimension": "2*2",
+        "supportDimensions": ["2*2"],
+        "dataProxyEnabled": true // Enable the update-through-proxy feature.
+      }
+    ]
+  }
+  ```
+
+- Configure the subscription information [proxies](../reference/apis/js-apis-app-form-formBindingData.md#proxydata) in the [onAddForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onaddform) callback and return the information to the Widget Manager through [formBinding](../reference/apis/js-apis-app-form-formBindingData.md#formbindingdata). In this example, **key** is set to **detail** and **subscriberId** is set to **11**.
+  > **NOTE**
+  >
+  > The value of **key** can be a URI or a simple string. The default value of **subscriberId** is the value of **formId**. The actual value depends on the definition of the data provider.
+  ```ts
+  import formBindingData from '@ohos.app.form.formBindingData';
+  
+  let dataShareHelper;
+  onAddForm(want) {
+    let formData = {};
+    let proxies = [
+      {
+        "key": "detail",
+        "subscriberId": "11"
+      }
+    ]
+    let formBinding = formBindingData.createFormBindingData(formData);
+    formBinding["proxies"] = proxies;
+    return formBinding;
+  }
+  ```
+
+- In the widget page code file **widgets.abc**, use the variable in LocalStorage to obtain the subscribed data. In this example, the subscribed data is obtained through **'detail'** and displayed in the **\<Text>** component.
+  ```ts
+  let storage = new LocalStorage();
+  @Entry(storage)
+  @Component
+  struct Index {
+    @LocalStorageProp('detail') detail: string = 'Loading...';
+  
+    build() {
+      Row() {
+        Column() {
+          Text(this.detail)
+            .fontSize('12vp')
+            .textAlign(TextAlign.Center)
+            .width('100%')
+            .height('15%')
+        }
+  	  .width('100%')
+      }
+  	.height('100%')
+    }
+  }
+  ```
+
+## Widget Provider Development (Persistent Data; for System Applications Only)
+- Set the **dataProxyEnabled** field to **true** in the **form_config.json** file to enable the update-through-proxy feature.
+  ```json
+  {
+    "forms": [
+      {
+        "name": "widget",
+        "description": "This is a service widget.",
+        "src": "./ets/widget/pages/WidgetCard.ets",
+        "uiSyntax": "arkts",
+        "window": {
+          "designWidth": 720,
+          "autoDesignWidth": true
+        },
+        "colorMode": "auto",
+        "isDefault": true,
+        "updateEnabled": true,
+        "scheduledUpdateTime": "10:30",
+        "defaultDimension": "2*2",
+        "supportDimensions": ["2*2"],
+        "dataProxyEnabled": true // Enable the update-through-proxy feature.
+      }
+    ]
+  }
+  ```
+
+- Add a subscription template ([addTemplate]([../reference/apis/js-apis-data-dataShare.md#addtemplate10)) to the [onAddForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onaddform) callback and use the template predicates to notify the database of the subscribed data conditions. Then, configure the subscription information [proxies](../reference/apis/js-apis-app-form-formBindingData.md#proxydata) and return it to the Widget Manager through [formBinding](../reference/apis/js-apis-app-form-formBindingData.md#formbindingdata). In the example, the predicate is set to **"list": "select type from TBL00 limit 0,1"**, indicating that the first data record in the **type** column is obtained from the **TBL00** database. The data is returned to the widget page code file **widgets.abc** in {"list":[{"type":"value0"}]} format.
+
+  > **NOTE**
+  >
+  > - The value of **key** is a URI, which depends on the definition of the data release party.
+  > - The value of **subscriberId** can be customized. Ensure that the value of **subscriberId** in **addTemplate** is the same as that of **proxies.subscriberId**.
+  ```ts
+  import formBindingData from '@ohos.app.form.formBindingData';
+  import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
+  import dataShare from '@ohos.data.dataShare'
+
+  let dataShareHelper;
+  onAddForm(want) {
+    let template = {
+      predicates : {
+        "list" : "select type from TBL00 limit 0,1"
+      },
+      scheduler: ""
+    }
+    let subscriberId = "111";
+    dataShare.createDataShareHelper(this.context, "datashareproxy://com.example.myapplication", {isProxy : true}).then((data) => {
+      dataShareHelper = data;
+      dataShareHelper.addTemplate("datashareproxy://com.example.myapplication/test", subscriberId, template);
+    })
+
+    let formData = {};
+    let proxies = [
+      {
+        "key": "datashareproxy://com.example.myapplication/test",
+        "subscriberId": subscriberId
+      }
+    ]
+    let formBinding = formBindingData.createFormBindingData(formData);
+    formBinding["proxies"] = proxies;
+
+    return formBinding;
+  }
+  ```
+
+- In the widget page code file **widgets.abc**, use the variable in LocalStorage to obtain the subscribed data. In the example, the subscribed data is obtained through **'list'**, and the value of the first element is displayed on the **\<Text>** component.
+  ```ts
+  let storage = new LocalStorage();
+  @Entry(storage)
+  @Component
+  struct WidgetCard {
+    readonly ACTION_TYPE: string = 'router';
+    readonly ABILITY_NAME: string = 'EntryAbility';
+    readonly MESSAGE: string = 'add detail';
+    readonly FULL_WIDTH_PERCENT: string = '100%';
+    readonly FULL_HEIGHT_PERCENT: string = '100%';
+    @LocalStorageProp('list') list: Array<object> = [{"type": "a"}];
+  
+    build() {
+      Row() {
+        Column() {
+          Text((this.list[0]["type"]))
+            .fontSize($r('app.float.font_size'))
+        }
+        .width(this.FULL_WIDTH_PERCENT)
+      }
+      .height(this.FULL_HEIGHT_PERCENT)
+      .onClick(() => {
+        postCardAction(this, {
+          "action": this.ACTION_TYPE,
+          "abilityName": this.ABILITY_NAME,
+          "params": {
+            "message": this.MESSAGE
+          }
+        })
+      })
+    }
+  }
+  ```
+
+## Data Provider Development
+
+For details, see [Data Management](../database/data-mgmt-overview.md).
+<!--no_check-->
\ No newline at end of file

en/application-dev/application-models/arkts-ui-widget-update-by-status.md

 # Updating Widget Content by State
 
+There are cases where multiple copies of the same widget are added to the home screen to accommodate different needs. In these cases, the widget content needs to be dynamically updated based on the state. This topic exemplifies how this is implemented.
 
-Multiple widgets of the same application can be configured to implement different features. For example, two weather widgets can be added to the home screen: one for displaying the weather of London, and the other Beijing. The widget is set to be updated at 07:00 every morning. It needs to detect the configured city, and then updates the city-specific weather information. The following example describes how to dynamically update the widget content based on the state.
+In the following example, two copies of the weather widget are added to the home screen: one for displaying the weather of London, and the other Beijing, both configured to be updated at 07:00 every morning. The widget provider detects the target city, and then displays the city-specific weather information on the widgets.
 
 
 - Widget configuration file: Configure the widget to be updated at 07:00 every morning.
@@ -74,7 +75,7 @@ Multiple widgets of the same application can be configured to implement differen
         }
   
         Row() {// Content that is updated only in state A
-          Text('State A: ')
+          Text ('State A:')
           Text(this.textA)
         }
   
@@ -94,7 +95,7 @@ Multiple widgets of the same application can be configured to implement differen
   import formProvider from '@ohos.app.form.formProvider';
   import formBindingData from '@ohos.app.form.formBindingData';
   import FormExtensionAbility from '@ohos.app.form.FormExtensionAbility';
-  import dataStorage from '@ohos.data.storage'
+  import dataPreferences from '@ohos.data.preferences';
   
   export default class EntryFormAbility extends FormExtensionAbility {
     onAddForm(want) {
@@ -102,10 +103,10 @@ Multiple widgets of the same application can be configured to implement differen
       let isTempCard: boolean = want.parameters[formInfo.FormParam.TEMPORARY_KEY];
       if (isTempCard === false) {// If the widget is a normal one, the widget information is persisted.
         console.info('Not temp card, init db for:' + formId);
-        let storeDB = dataStorage.getStorageSync(this.context.filesDir + 'myStore')
-        storeDB.putSync('A' + formId, 'false');
-        storeDB.putSync('B' + formId, 'false');
-        storeDB.flushSync();
+        let storeDB = dataPreferences.getPreferences(this.context, 'mystore')
+        storeDB.put('A' + formId, 'false');
+        storeDB.put('B' + formId, 'false');
+        storeDB.flush();
       }
       let formData = {};
       return formBindingData.createFormBindingData(formData);
@@ -113,24 +114,24 @@ Multiple widgets of the same application can be configured to implement differen
   
     onRemoveForm(formId) {
       console.info('onRemoveForm, formId:' + formId);
-      let storeDB = dataStorage.getStorageSync(this.context.filesDir + 'myStore')
-      storeDB.deleteSync('A' + formId);
-      storeDB.deleteSync('B' + formId);
+      let storeDB = dataPreferences.getPreferences(this.context, 'mystore')
+      storeDB.delete('A' + formId);
+      storeDB.delete('B' + formId);
     }
   
     // If the widget is a temporary one, it is recommended that the widget information be persisted when the widget is converted to a normal one.
     onCastToNormalForm(formId) {
       console.info('onCastToNormalForm, formId:' + formId);
-      let storeDB = dataStorage.getStorageSync(this.context.filesDir + 'myStore')
-      storeDB.putSync('A' + formId, 'false');
-      storeDB.putSync('B' + formId, 'false');
-      storeDB.flushSync();
+      let storeDB = dataPreferences.getPreferences(this.context, 'myStore')
+      storeDB.put('A' + formId, 'false');
+      storeDB.put('B' + formId, 'false');
+      storeDB.flush();
     }
   
     onUpdateForm(formId) {
-      let storeDB = dataStorage.getStorageSync(this.context.filesDir + 'myStore')
-      let stateA = storeDB.getSync('A' + formId, 'false').toString()
-      let stateB = storeDB.getSync('B' + formId, 'false').toString()
+      let storeDB = dataPreferences.getPreferences(this.context, 'myStore')
+      let stateA = storeDB.get('A' + formId, 'false').toString()
+      let stateB = storeDB.get('B' + formId, 'false').toString()
       // Update textA in state A.
       if (stateA === 'true') {
         let formInfo = formBindingData.createFormBindingData({
@@ -150,21 +151,22 @@ Multiple widgets of the same application can be configured to implement differen
     onFormEvent(formId, message) {
       // Store the widget state.
       console.info('onFormEvent formId:' + formId + 'msg:' + message);
-      let storeDB = dataStorage.getStorageSync(this.context.filesDir + 'myStore')
+      let storeDB = dataPreferences.getPreferences(this.context, 'myStore')
       let msg = JSON.parse(message)
       if (msg.selectA != undefined) {
         console.info('onFormEvent selectA info:' + msg.selectA);
-        storeDB.putSync('A' + formId, msg.selectA);
+        storeDB.put('A' + formId, msg.selectA);
       }
       if (msg.selectB != undefined) {
         console.info('onFormEvent selectB info:' + msg.selectB);
-        storeDB.putSync('B' + formId, msg.selectB);
+        storeDB.put('B' + formId, msg.selectB);
       }
-      storeDB.flushSync();
+      storeDB.flush();
     }
   };
   ```
 
 
 > **NOTE**
-> When the local database is used for widget information persistence, it is recommended that [TEMPORARY_KEY](../reference/apis/js-apis-app-form-formInfo.md#formparam) be used to determine whether the currently added widget is a normal one in the [onAddForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onaddform) lifecycle callback. If the widget is a normal one, the widget information is directly persisted. If the widget is a temporary one, the widget information is persisted when the widget is converted to a normal one ([onCastToNormalForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#oncasttonormalform)). In addition, the persistent widget information needs to be deleted when the widget is destroyed ([onRemoveForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onremoveform)), preventing the database size from continuously increasing due to repeated widget addition and deletion.
+>
+> When the local database is used for widget information persistence, it is recommended that [TEMPORARY_KEY](../reference/apis/js-apis-app-form-formInfo.md#formparam) be used in the [onAddForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onaddform) lifecycle callback to determine whether the currently added widget is a normal one. If the widget is a normal one, the widget information is directly persisted. If the widget is a temporary one, the widget information is persisted when the widget is converted to a normal one ([onCastToNormalForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#oncasttonormalform)). In addition, the persistent widget information needs to be deleted when the widget is destroyed ([onRemoveForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onremoveform)), preventing the database size from continuously increasing due to repeated widget addition and deletion.

en/application-dev/application-models/arkts-ui-widget-update-by-time.md

@@ -5,12 +5,12 @@ Before configuring a widget to update periodically, enable the periodic update f
 The widget framework provides the following modes of updating widgets periodically:
 
 
-- Set the update interval: The widget will be updated at the specified interval. You can specify the interval by setting the [updateDuration](arkts-ui-widget-configuration.md) field in the **form_config.json** file. For example, you can configure the widget to update once an hour.
-  
+- Setting the update interval: The widget will be updated at the specified interval by calling [onUpdateForm](../reference/apis/js-apis-app-form-formExtensionAbility.md#onupdateform). You can specify the interval by setting the [updateDuration](arkts-ui-widget-configuration.md) field in the **form_config.json** file. For example, you can configure the widget to update once an hour.
+
   > **NOTE**
   >
   > **updateDuration** takes precedence over **scheduledUpdateTime**. If both are specified, the value specified by **updateDuration** is used.
-  
+
   ```json
   {
     "forms": [
@@ -26,22 +26,22 @@ The widget framework provides the following modes of updating widgets periodical
         "colorMode": "auto",
         "isDefault": true,
         "updateEnabled": true, // Enable the periodic update feature.
-        "scheduledUpdateTime": "10:30",                               
-        "updateDuration": 2, // Set the interval to update the widget. The value is a natural number, in the unit of 30 minutes.
+        "scheduledUpdateTime": "10:30",
+        "updateDuration": 2, // Set the update interval. The value is a natural number, in the unit of 30 minutes.
         "defaultDimension": "2*2",
         "supportDimensions": ["2*2"]
       }
     ]
   }
   ```
-  
-- Set the scheduled update time: The widget will be updated at the scheduled time every day. You can specify the time by setting the [scheduledUpdateTime](arkts-ui-widget-configuration.md) field in the **form_config.json** file. For example, you can configure the widget to update at 10:30 a.m. every day.
-  
+
+- Setting the scheduled update time: The widget will be updated at the scheduled time every day. You can specify the time by setting the [scheduledUpdateTime](arkts-ui-widget-configuration.md) field in the **form_config.json** file. For example, you can configure the widget to update at 10:30 a.m. every day.
+
   > **NOTE**
   >
   > **updateDuration** takes precedence over **scheduledUpdateTime**. For the **scheduledUpdateTime** settings to take effect, set **updateDuration** to **0**.
-  
-  
+
+
   ```json
   {
     "forms": [
@@ -65,12 +65,12 @@ The widget framework provides the following modes of updating widgets periodical
     ]
   }
   ```
-  
-- Set the next update time: The widget will be updated next time at the specified time. You can specify the time by calling the [setFormNextRefreshTime()](../reference/apis/js-apis-app-form-formProvider.md#setformnextrefreshtime) API. The minimum update interval is 5 minutes. For example, you can configure the widget to update within 5 minutes after the API is called.
-  
+
+- Setting the next update time: The widget will be updated next time at the specified time. You can specify the time by calling the [setFormNextRefreshTime()](../reference/apis/js-apis-app-form-formProvider.md#setformnextrefreshtime) API. The minimum update interval is 5 minutes. For example, you can configure the widget to update within 5 minutes after the API is called.
+
   ```ts
   import formProvider from '@ohos.app.form.formProvider';
-  
+
   let formId = '123456789'; // Use the actual widget ID in real-world scenarios.
   try {
     // Configure the widget to update in 5 minutes.
@@ -88,12 +88,10 @@ The widget framework provides the following modes of updating widgets periodical
   ```
 
 
-When periodic update is triggered, the system calls the [onUpdateForm()](../reference/apis/js-apis-app-form-formExtensionAbility.md#onupdateform) lifecycle callback of the FormExtensionAbility. In the callback, [updateForm()](../reference/apis/js-apis-app-form-formProvider.md#updateform) can be used to update the widget by the provider. For details about how to use **onUpdateForm()**, see [Updating Widget Content Through FormExtensionAbility](arkts-ui-widget-event-formextensionability.md).
+When periodic update is triggered, the system calls the [onUpdateForm()](../reference/apis/js-apis-app-form-formExtensionAbility.md#onupdateform) lifecycle callback of the FormExtensionAbility. In the callback, [updateForm()](../reference/apis/js-apis-app-form-formProvider.md#updateform) can be used to update the widget. For details about how to use **onUpdateForm()**, see [Updating Widget Content Through FormExtensionAbility](arkts-ui-widget-event-formextensionability.md).
 
 
 > **NOTE**
-> 1. Each widget can be updated at the specified interval for a maximum of 50 times every day, including updates triggered by setting [updateDuration](arkts-ui-widget-configuration.md) or calling [setFormNextRefreshTime()](../reference/apis/js-apis-app-form-formProvider.md#setformnextrefreshtime). When the limit is reached, the widget cannot be updated in this mode again. The number of update times is reset at 00:00 every day.
-> 
-> 2. The same timer is used for timing updates at the specified interval. Therefore, the first scheduled update of widgets may have a maximum deviation of 30 minutes. For example, the first widget A (updated every half an hour) is added at 03:20. The timer starts and triggers an update every half an hour. The second widget B (updated every half an hour) is added at 03:40. When the timer event is triggered at 03:50, widget A is updated, and widget B will be updated at 04:20 next time.
-> 
-> 3. Updates at the specified interval and updates at the scheduled time are triggered only when the screen is on. When the screen is off, the update action is merely recorded. When the screen is on, the update action is performed.
+> - Each widget can be updated at the specified interval for a maximum of 50 times every day, including updates triggered by setting [updateDuration](arkts-ui-widget-configuration.md) or calling [setFormNextRefreshTime()](../reference/apis/js-apis-app-form-formProvider.md#setformnextrefreshtime). When the limit is reached, the widget cannot be updated in this mode again. The number of update times is reset at 00:00 every day.
+>- A single timer is used for timing updates at the specified interval. Therefore, if a widget is configured to update at scheduled intervals, the first scheduled update may have a maximum deviation of 30 minutes. For example, if widget A (updated every half an hour) is added at 03:20 and widget B (also updated every half an hour) is added at 03:40, the first update of widget B has a deviation of 10 minutes to the expected time: The timer starts at 03:20 when widget A is added, triggers an update for widget A at 03:50, and triggers another update for widget B at 04:20 (instead of 04:10 as expected).
+> - Updates at the specified interval and updates at the scheduled time are triggered only when the screen is on. The update action is merely recorded when the screen is off and is performed once the screen is on.

en/application-dev/application-models/arkts-ui-widget-working-principles.md

@@ -3,42 +3,45 @@
 
 ## Implementation Principles
 
-  **Figure 1** ArkTS widget implementation principles 
+**Figure 1** ArkTS widget implementation principles
+
 ![WidgetPrinciple](figures/WidgetPrinciple.png)
 
 - Widget host: an application that displays the widget content and controls the widget location. Only the system application can function as a widget host.
 
 - Widget provider: an application that provides the widget content to display and controls how widget components are laid out and how they interact with users.
 
-- Widget Manager: a resident agent that manages widgets in the system. It provides the [formProvider](../reference/apis/js-apis-app-form-formProvider.md) and [formHost](../reference/apis/js-apis-app-form-formHost.md) APIs as well as widget management, usage, and periodic updates. 
+- Widget Manager: a resident agent that manages widgets in the system. It provides the [formProvider](../reference/apis/js-apis-app-form-formProvider.md) and [formHost](../reference/apis/js-apis-app-form-formHost.md) APIs as well as the APIs for widget management, usage, and periodic updates.
 
 - Widget rendering service: a service that manages widget rendering instances. Widget rendering instances are bound to the [widget components](../reference/arkui-ts/ts-basic-components-formcomponent.md) on the widget host on a one-to-one basis. The widget rendering service runs the widget page code **widgets.abc** for rendering, and sends the rendered data to the corresponding widget component on the widget host.
 
   **Figure 2** Working principles of the ArkTS widget rendering service 
 ![WidgetRender](figures/WidgetRender.png)
 
-Unlike JS widgets, ArkTS widgets support logic code running. To avoid potential ArkTS widget issues from affecting the use of applications, the widget page code **widgets.abc** is executed by the widget rendering service, which is managed by the Widget Manager. Each widget component of a widget host corresponds to a rendering instance in the widget rendering service. Rendering instances of an application provider run in the same virtual machine operating environment, and rendering instances of different application providers run in different virtual machine operating environments. In this way, the resources and state data are isolated between widgets of different application providers. During development, pay attention to the use of the [globalThis](uiability-data-sync-with-ui.md#using-globalthis-between-uiability-and-page) object. Use one **globalThis** object for widgets by the same application provider, and different **globalThis** objects for widgets by different application providers.
+Unlike JS widgets, ArkTS widgets support logic code running. The widget page code **widgets.abc** is executed by the widget rendering service, which is managed by the Widget Manager. Each widget component of a widget host corresponds to a rendering instance in the widget rendering service. Rendering instances of a widget provider run in the same virtual machine operating environment, and rendering instances of different widget providers run in different virtual machine operating environments. In this way, the resources and state data are isolated between widgets of different widget providers. During development, pay attention to the use of the [globalThis](uiability-data-sync-with-ui.md#using-globalthis-between-uiability-and-page) object. Use one **globalThis** object for widgets from the same widget provider, and different **globalThis** objects for widgets from different widget providers.
 
 
 ## Advantages of ArkTS Widgets
 
-As a quick entry to applications, ArkTS widgets have the following advantages over JS widgets:
+As a quick entry to applications, ArkTS widgets outperform JS widgets in the following aspects:
 
 - Improved development experience and efficiency, thanks to the unified development paradigm
+  
   ArkTS widgets share the same declarative UI development framework as application pages. This means that the page layouts can be directly reused in widgets, improving development experience and efficiency.
-
-    **Figure 3** Comparison of widget project structures 
+  
+  **Figure 3** Comparison of widget project structures
+  
   ![WidgetProject](figures/WidgetProject.png)
-
+  
 - More widget features
-  - Animation: The ArkTS widget supports the [attribute animation](../reference/arkui-ts/ts-animatorproperty.md) and [explicit animation](../reference/arkui-ts/ts-explicit-animation.md) capabilities, which can be leveraged to deliver a more engaging experience.
-  - Custom drawing: The ArkTS widget allows you to draw graphics with the [Canvas](../reference/arkui-ts/ts-components-canvas-canvas.md) component to present information more vividly.
-  - Logic code execution: The capability to run logic code in widgets means that service logic can be self-closed in widgets, expanding the service application scenarios of widgets.
+  - Animation: ArkTS widgets support the [attribute animation](../reference/arkui-ts/ts-animatorproperty.md) and [explicit animation](../reference/arkui-ts/ts-explicit-animation.md) capabilities, which can be leveraged to deliver a more engaging experience.
+  - Custom drawing: ArkTS widgets allow you to draw graphics with the [\<Canvas>](../reference/arkui-ts/ts-components-canvas-canvas.md) component to present information more vividly.
+  - Logic code execution: The capability to run logic code in widgets means that service logic can be self-closed in widgets, expanding the use cases of widgets.
 
 
 ## Constraints on ArkTS Widgets
 
-Compared with JS widgets, ArkTS widgets provide more capabilities, but they are also more prone to malicious behavior. The ArkTS widget is displayed in the widget host, which is usually the home screen. To ensure user experience and power consumption, the ArkTS widget capability is restricted as follows:
+Compared with JS widgets, ArkTS widgets provide more capabilities, but they are also more prone to malicious behavior. To account for the impact on the widget host – typically the home screen, ArkTS widgets are subject to the following restrictions:
 
 - The .so file cannot be loaded.
 
@@ -46,12 +49,14 @@ Compared with JS widgets, ArkTS widgets provide more capabilities, but they are
 
 - Only [partial](arkts-ui-widget-page-overview.md) components, events, animations, data management, state management, and API capabilities of the declarative paradigm are supported.
 
-- The event processing of the widget is independent of that of the widget host. It is recommended that you do not use the left and right sliding components when the widget host supports left and right swipes to prevent gesture conflicts.
+- The event processing of the widget is independent of that of the widget host. To prevent gesture conflicts, avoid using swipers in the widget when the widget host supports left and right swipes.
 
-The following features are coming to ArkTS widgets in later versions:
+In addition, ArkTS widgets do not support the following features:
 
-- Breakpoint debugging
-
-- import statements
+- Importing modules
 
 - Instant preview
+
+- Breakpoint debugging.
+
+- Hot reload

en/application-dev/application-models/atomic-services-support-sharing.md

+# Setting Atomic Services to Support Sharing
+By means of sharing, users can quickly access atomic services and use their features.
+
+## How to Develop
+In the sharing scenario, there are two parties involved: a target application that shares data and an application that obtains the shared data. The two can be physically the same. The target application uses the **onShare()** lifecycle callback to set the data to share. After the target application is started, you can run the **hdc shell aa dump -a** command to check the started services and processes and find its mission ID. After the current application is started, call the **abilityManager.acquireShareData()** API with the mission ID passed in to obtain the shared data.
+> **NOTE**
+>
+> The mission ID of the target application can also be obtained by calling [missionManager.getMissionInfos()](../reference/apis/js-apis-app-ability-missionManager.md#getmissioninfos).
+
+1. The target application calls **UIAbility.onShare()** provided by the UIAbility component to set the data to share. **ohos.extra.param.key.contentTitle** indicates the title of the content to share in the sharing box, **ohos.extra.param.key.shareAbstract** provides an abstract description of the content, and **ohos.extra.param.key.shareUrl** indicates the online address of the service. You need to set these three items as objects, with the key set to **title**, **abstract**, and **url**, respectively.
+
+   ```ts
+   import AbilityConstant from '@ohos.app.ability.AbilityConstant';
+   class MyUIAbility extends UIAbility {
+       onShare(wantParams) {
+           console.log('onShare');
+           wantParams['ohos.extra.param.key.contentTitle'] = {title: "W3"};
+           wantParams['ohos.extra.param.key.shareAbstract'] = {abstract: "communication for huawei employee"};
+           wantParams['ohos.extra.param.key.shareUrl'] = {url: "w3.huawei.com"};
+       }
+   }
+   ```
+
+2. The current application calls **abilityManager.acquireShareData()** to obtain the data shared by the target application. **missionId** indicates the target application's mission ID, which can be obtained by running the **hdc shell aa dump -a** command or calling the **missionManager.getMissionInfos()** API after the target application is started. **wantParam** indicates the data shared by the target application through the **UIAbility.onShare()** lifecycle callback.
+
+   ```ts
+   import abilityManager from '@ohos.app.ability.abilityManager';
+   try {
+       abilityManager.acquireShareData(1, (err, wantParam) => {
+           if (err) {
+               console.error(`acquireShareData fail, err: ${JSON.stringify(err)}`);
+           } else {
+               console.log(`acquireShareData success, data: ${JSON.stringify(wantParam)}`);
+           }
+       });
+   } catch (paramError) {
+       console.error(`error.code: ${JSON.stringify(paramError.code)}, error.message: ${JSON.stringify(paramError.message)}`);
+   }
+   ```

en/application-dev/application-models/common-event-overview.md

@@ -7,8 +7,7 @@ OpenHarmony provides Common Event Service (CES) for applications to subscribe to
 Common events are classified into system common events and custom common events.
 
 
-- System common events: defined in CES. Only system applications and system services can publish system common events, such as HAP installation, update, and uninstall. For details about the supported system common events, see [Support](../reference/apis/js-apis-commonEventManager.md#support).
-
+- System common events: defined in CES. Currently, only system applications and system services can publish system common events, such as HAP installation, update, and uninstall. For details about the supported system common events, see [System Common Events](../reference/apis/commonEventManager-definitions.md).
 - Custom common events: customized by applications to implement cross-process event communication.
 
 
@@ -16,9 +15,7 @@ Common events are also classified into unordered, ordered, and sticky common eve
 
 
 - Unordered common events: common events that CES forwards regardless of whether subscribers receive the events and when they subscribe to the events.
-
-- Ordered common events: common events that CES forwards based on the subscriber priority. CES forwards common events to the subscriber with lower priority only after receiving a reply from the previous subscriber with higher priority. Subscribers with the same priority receive common events in a random order.
-
+- Ordered common events: common events that CES forwards based on the subscriber priority. CES preferentially forwards an ordered common event to the subscriber with higher priority, waits until the subscriber receives the event, and then forwards the events to the subscriber with lower priority. Subscribers with the same priority receive common events in a random order.
 - Sticky common events: common events that can be sent to a subscriber before or after they initiate a subscription. Only system applications and system services can send sticky common events, which remain in the system after being sent. The sends must first request the **ohos.permission.COMMONEVENT_STICKY** permission. For details about the configuration, see [Permission Application Guide](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file). 
 
 

en/application-dev/application-models/common-event-remove-sticky.md

-# Removing Sticky Common Events
+# Removing Sticky Common Events (for System Applications Only)
 
 
 ## When to Use
@@ -16,21 +16,26 @@ For details, see [Common Event](../reference/apis/js-apis-commonEventManager.md)
 
 ## How to Develop
 
-1. Import the module.
-   
+1. Request the **ohos.permission.COMMONEVENT_STICKY** permission. For details, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file).
+
+2. Import the module.
+
    ```ts
    import commonEventManager from '@ohos.commonEventManager';
    ```
 
-2. The sticky common event to be removed must have been released by the application. For details about how to release sticky common events, see [Publishing Common Events](common-event-publish.md).
+3. Call the [removeStickyCommonEvent()](../reference/apis/js-apis-commonEventManager.md#commoneventmanagerremovestickycommonevent10) API to remove the target sticky common event.
+
+   > **NOTE**
+   >
+   > The sticky common event to be removed must have been released by the application. For details about how to release sticky common events, see [Publishing Common Events](common-event-publish.md).
 
    ```ts
-   CommonEventManager.removeStickyCommonEvent("sticky_event", (err) => { // sticky_event indicates the name of the sticky common event to remove.
-       if (err) {
-           console.info(`Remove sticky event AsyncCallback failed, errCode: ${err.code}, errMes: ${err.message}`);
-           return;
-       }
-       console.info(`Remove sticky event AsyncCallback success`);
-       }
+   commonEventManager.removeStickyCommonEvent("sticky_event", (err) => { // sticky_event indicates the name of the target sticky common event.
+     if (err) {
+       console.error(`Failed to remove sticky common event. Code is ${err.code}, message is ${err.message}`);
+       return;
+     }
+     console.info(`Succeeded in removeing sticky event.`);
    });
    ```

en/application-dev/application-models/common-event-static-subscription.md

@@ -2,38 +2,46 @@
 
 ## When to Use
 
-A static subscriber is started once it receives a target event published by the system or application. At the same time, the **onReceiveEvent** callback is triggered, in which you can implement the service logic. For example, if an application needs to execute some initialization tasks during device power-on, the application can subscribe to the power-on event in static mode. After receiving the power-on event, the application is started to execute the initialization tasks. Subscribing to a common event in static mode is achieved by configuring a declaration file and implementing a class that inherits from **StaticSubscriberExtensionAbility**. Note that this subscribing mode has negative impact on system power consumption. Therefore, exercise caution when using this mode.
+A static subscriber is started once it receives a target event published by the system or application. At the same time, the [onReceiveEvent()](../reference/apis/js-apis-application-staticSubscriberExtensionAbility.md#staticsubscriberextensionabilityonreceiveevent) callback is triggered.
+
+You can implement the service logic in the [onReceiveEvent()](../reference/apis/js-apis-application-staticSubscriberExtensionAbility.md#staticsubscriberextensionabilityonreceiveevent) callback. For example, if an application needs to execute some initialization tasks during device power-on, the application can subscribe to the power-on event in static mode. After receiving the power-on event, the application is started to execute the initialization tasks.
+
+Subscribing to a common event in static mode is achieved by configuring a declaration file and implementing a class that inherits from [StaticSubscriberExtensionAbility](../reference/apis/js-apis-application-staticSubscriberExtensionAbility.md).
+
+> **NOTE**
+>
+> The static subscription mode has negative impact on system power consumption. Therefore, exercise caution when using this mode.
 
 ## How to Develop
 
-1. Declaring a Static Subscriber
+1. Declaring a static subscriber.
 
-   To declare a static subscriber, create an ExtensionAbility, which is derived from the **StaticSubscriberExtensionAbility** class, in the project. The sample code is as follows:
+   To declare a static subscriber, create an ExtensionAbility, which is derived from the **StaticSubscriberExtensionAbility** class, in the project.
+
+   You can implement service logic in the **onReceiveEvent()** callback.
 
    ```ts
    import StaticSubscriberExtensionAbility from '@ohos.application.StaticSubscriberExtensionAbility'
    
    export default class StaticSubscriber extends StaticSubscriberExtensionAbility {
-       onReceiveEvent(event) {
-           console.log('onReceiveEvent, event:' + event.event);
-       }
+     onReceiveEvent(event) {
+       console.info('onReceiveEvent, event: ' + event.event);
+     }
    }
    ```
 
-   You can implement service logic in the **onReceiveEvent** callback.
-
-2. Project Configuration for a Static Subscriber
+2. Configure static subscriber settings.
 
-   After writing the static subscriber code, configure the subscriber in the **module.json5** file. The configuration format is as follows:
+   After writing the static subscriber code, configure the subscriber in the [module.json5](../quick-start/module-configuration-file.md) file.
 
    ```ts
    {
      "module": {
-       ......
+       ...
        "extensionAbilities": [
          {
            "name": "StaticSubscriber",
-           "srcEntry": "./ets/StaticSubscriber/StaticSubscriber.ts",
+           "srcEntry": "./ets/staticsubscriber/StaticSubscriber.ts",
            "description": "$string:StaticSubscriber_desc",
            "icon": "$media:icon",
            "label": "$string:StaticSubscriber_label",
@@ -47,14 +55,14 @@ A static subscriber is started once it receives a target event published by the
            ]
          }
        ]
-       ......
+       ...
      }
    }
    ```
 
-   Pay attention to the following fields in the JSON file:
+   Some fields in the file are described as follows:
 
-   - **srcEntry**: 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**.
 
@@ -62,42 +70,46 @@ A static subscriber is started once it receives a target event published by the
         - **name**: name of the ExtensionAbility. For a static subscriber, declare the name as **ohos.extension.staticSubscriber** for successful identification.
         - **resource**: path that stores the ExtensionAbility configuration, which is customizable. In this example, the path is **resources/base/profile/subscribe.json**.
 
-     A level-2 configuration file pointed to by **metadata** must be in the following format:
 
-     ```ts
-     {
-       "commonEvents": [
-         {
-           "name": "xxx",
-           "permission": "xxx",
-           "events":[
-             "xxx"
-           ]
-         }
-       ]
-     }
-     ```
+3. Configure the level-2 configuration file to which the metadata points.
 
-     If the level-2 configuration file is not declared in this format, the file cannot be identified. The fields are described as follows:
+   ```json
+   {
+     "commonEvents": [
+       {
+         "name": "xxx",
+         "permission": "xxx",
+         "events":[
+           "xxx"
+         ]
+       }
+     ]
+   }
+   ```
 
-     - **name**: name of the ExtensionAbility, which must be the same as the name of **extensionAbility** declared in **module.json5**.
+   If the level-2 configuration file is not declared in this format, the file cannot be identified. Some fields in the file are described as follows:
 
-     - **permission**: permission required for the publisher. If a publisher without the required permission attempts to publish an event, the event is regarded as invalid and will not be published.
+   - **name**: name of the ExtensionAbility, which must be the same as the name of **extensionAbility** declared in **module.json5**.
+   - **permission**: permission required for the publisher. If a publisher without the required permission attempts to publish an event, the event is regarded as invalid and will not be published.
+   - **events**: list of target events to subscribe to.
 
-     - **events**: list of target events to subscribe to.
+4. Modify the [preset configuration file](https://gitee.com/openharmony/vendor_hihope/blob/master/rk3568/preinstall-config/install_list_permissions.json) of the device, that is, the **/system/etc/app/install_list_permission.json** file on the device. When the device is started, this file is read. During application installation, the common event type specified by **allowCommonEvent** in the file is authorized. The **install_list_permission.json** file contains the following fields:
 
-3. Device System Configuration
+   - **bundleName**: bundle name of the application.
+   - **app_signature**: fingerprint information of the application. For details, see [Application Privilege Configuration Guide](../../device-dev/subsystems/subsys-app-privilege-config-guide.md#configuration-in-install_list_capabilityjson).
+   - **allowCommonEvent**: type of common event that can be started by static broadcast.
 
-    In the device system configuration file **/system/etc/app/install_list_capability.json**, add the bundle name of the static subscriber.
+   > **NOTE**
+   >
+   > The **install_list_permissions.json** file is available only for preinstalled applications.
 
-    ```json
-   {
-    "install_list": [
-            {
-                "bundleName": "ohos.extension.staticSubscriber",
-                "allowCommonEvent": ["usual.event.A", "usual.event.B"],
-            }
-        ]
-    }
+   ```json
+   [
+     {
+       "bundleName": "com.example.myapplication", 
+       "app_signature": ["****"], 
+       "allowCommonEvent": ["usual.event.A", "usual.event.B"]
+     }
+   ]
    ```
 

en/application-dev/application-models/common-event-subscription-overview.md

 # Common Event Subscription Overview
 
-​The common event service provides two subscription modes: dynamic and static. The biggest difference between these two modes is that dynamic subscription requires the application to be running, while static subscription does not.
+The common event service provides two subscription modes: dynamic and static. The biggest difference between these two modes is that dynamic subscription requires the application to be running, while static subscription does not.
 
 - In dynamic subscription mode, a subscriber subscribes to common events by calling an API during the running period. For details, see [Subscribing to Common Events in Dynamic Mode](common-event-subscription.md).
 
-- In static subscription mode, a subscriber subscribes to common events by configuring a declaration file and implementing a class that inherits from StaticSubscriberExtensionAbility. For details, see [Subscribing to Common Events in Static Mode](common-event-static-subscription.md).
+- In static subscription mode, a subscriber subscribes to common events by configuring a declaration file and implementing a class that inherits from **StaticSubscriberExtensionAbility**. For details, see [Subscribing to Common Events in Static Mode](common-event-static-subscription.md).

en/application-dev/application-models/common-event-subscription.md

@@ -32,7 +32,7 @@ For details about the APIs, see [API Reference](../reference/apis/js-apis-common
    let subscriber = null;
    // Subscriber information.
    let subscribeInfo = {
-       events: ["usual.event.SCREEN_OFF"], // Subscribe to the common event screen-off.
+     events: ["usual.event.SCREEN_OFF"], // Subscribe to the common event screen-off.
    }
    ```
 
@@ -41,13 +41,13 @@ For details about the APIs, see [API Reference](../reference/apis/js-apis-common
    ```ts
    // Callback for subscriber creation.
    commonEventManager.createSubscriber(subscribeInfo, (err, data) => {
-       if (err) {
-           console.error(`[CommonEvent] CreateSubscriberCallBack err=${JSON.stringify(err)}`);
-       } else {
-           console.info(`[CommonEvent] CreateSubscriber success`);
-           subscriber = data;
-           // Callback for common event subscription.
-       }
+     if (err) {
+       console.error(`Failed to create subscriber. Code is ${err.code}, message is ${err.message}`);
+       return;
+     }
+     console.info('Succeeded in creating subscriber.');
+     subscriber = data;
+     // Callback for common event subscription.
    })
    ```
 
@@ -56,14 +56,13 @@ For details about the APIs, see [API Reference](../reference/apis/js-apis-common
    ```ts
    // Callback for common event subscription.
    if (subscriber !== null) {
-       commonEventManager.subscribe(subscriber, (err, data) => {
-           if (err) {
-               console.error(`[CommonEvent] SubscribeCallBack err=${JSON.stringify(err)}`);
-           } else {
-               console.info(`[CommonEvent] SubscribeCallBack data=${JSON.stringify(data)}`);
-           }
-       })
+     commonEventManager.subscribe(subscriber, (err, data) => {
+       if (err) {
+         console.error(`Failed to subscribe common event. Code is ${err.code}, message is ${err.message}`);
+         return;
+       }
+     })
    } else {
-       console.error(`[CommonEvent] Need create subscriber`);
+     console.error(`Need create subscriber`);
    }
    ```

en/application-dev/application-models/component-startup-rules-fa.md

@@ -12,7 +12,7 @@ Component startup refers to the behavior of starting or connecting to an applica
 To deliver a better user experience, OpenHarmony restricts the following behavior:
 
 
-- A background application randomly displays a dialog box, such as an ads pop-up.
+- A background application randomly displays a dialog box, such as an ad pop-up.
 
 - Background applications wake up each other. This type of behavior occupies system resources and increases power consumption, or even causes system frozen.
 
@@ -34,14 +34,14 @@ In view of this, OpenHarmony formulates a set of component startup rules, as fol
 - **Before starting the ServiceAbility or DataAbility component of an application, verify the AssociateWakeUp field of the target application.**
   - This rule applies only to cross-application scenarios.
   - This rule is valid only when the target component is ServiceAbility or DataAbility.
-  - The ServiceAbility and DataAbility of an application can be accessed by others only when **AssociateWakeUp** of the target application is set to **true**.
+  - The ServiceAbility and DataAbility of an application can be accessed by other applications only when **AssociateWakeUp** of the target application is set to **true**.
   - The **AssociateWakeUp** field can be configured only for preset applications. For other applications, this field is set to **false** by default.
 
 
 > **NOTE**
 > 1. Component startup control has been implemented since OpenHarmony v3.2 Release.
 > 
-> 2. The new component startup rules are more strict than the original ones. You must be familiar with the new startup rules to prevent service exceptions.
+> 2. The new component startup rules are more strict than the original ones. Get familiar with the new startup rules to prevent service exceptions.
 
  
 

en/application-dev/application-models/configuration-file-diff.md

@@ -4,8 +4,8 @@
 The FA model uses the [config.json file](../quick-start/application-configuration-file-overview-fa.md) to describe the basic information about an application. An application can have multiple modules, and each module has a **config.json** file. The **config.json** file consists of three parts: **app**, **deviceConfig**, and **module**. The **app** tag is used to configure application-level attributes. If an application has multiple modules, the **app** configuration in each **config.json** file must be consistent.
 
 
-The stage model uses the [app.json5](../quick-start/app-configuration-file.md) and [module.json](../quick-start/module-configuration-file.md) files to describe the basic information about an application. An application can have multiple modules but only one **app.json5** file. This file is used to configure application-level attributes and takes effect for all the modules. Each module has a **module.json5** file, which is used to configure module-level attributes and takes effect only for the current module.
+The stage model uses the [app.json5](../quick-start/app-configuration-file.md) and [module.json](../quick-start/module-configuration-file.md) files to describe the basic information about an application. An application can have multiple modules but only one **app.json5** file. This file is used to configure application-level attributes and the configuration applies to all the modules. Each module has a **module.json5** file, which is used to configure module-level attributes and the configuration applies only for the current module.
 
-**Figure 1** Configuration file differences 
-![comparison-of-configuration-file](figures/comparison-of-configuration-file.png)
+**Figure 1** Configuration file differences
 
+![comparison-of-configuration-file](figures/comparison-of-configuration-file.png)
\ No newline at end of file

en/application-dev/application-models/connect-serviceability.md

@@ -16,14 +16,14 @@ The following sample code enables the PageAbility to create connection callback
 
 ```ts
 import rpc from "@ohos.rpc"
-import prompt from '@system.prompt'
+import promptAction from '@ohos.promptAction'
 import featureAbility from '@ohos.ability.featureAbility'
 
 let option = {
   onConnect: function onConnectCallback(element, proxy) {
     console.info(`onConnectLocalService onConnectDone`)
     if (proxy === null) {
-      prompt.showToast({
+      promptAction.showToast({
         message: "Connect service failed"
       })
       return
@@ -33,19 +33,19 @@ let option = {
     let option = new rpc.MessageOption()
     data.writeInterfaceToken("connect.test.token")
     proxy.sendRequest(0, data, reply, option)
-    prompt.showToast({
+    promptAction.showToast({
       message: "Connect service success"
     })
   },
   onDisconnect: function onDisconnectCallback(element) {
     console.info(`onConnectLocalService onDisconnectDone element:${element}`)
-    prompt.showToast({
+    promptAction.showToast({
       message: "Disconnect service success"
     })
   },
   onFailed: function onFailedCallback(code) {
     console.info(`onConnectLocalService onFailed errCode:${code}`)
-    prompt.showToast({
+    promptAction.showToast({
       message: "Connect local service onFailed"
     })
   }

en/application-dev/application-models/context-switch.md

 # Context Switching
 
 
-  | API in the FA Model| Corresponding d.ts File in the Stage Model| Corresponding API or Field in the Stage Model| 
+  | API in the FA Model| Corresponding .d.ts File in the Stage Model| Corresponding API or Field in the Stage Model| 
 | -------- | -------- | -------- |
 | [getOrCreateLocalDir(callback:AsyncCallback&lt;string&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextgetorcreatelocaldir7)<br>[getOrCreateLocalDir():Promise&lt;string&gt;;](../reference/apis/js-apis-inner-app-context.md#contextgetorcreatelocaldir7-1) | There is no corresponding API in the stage model.| Applications developed on the stage model do not have the operation permission in the application root directory. Therefore, no corresponding API is provided.|
 | [verifyPermission(permission:string,options:PermissionOptions,callback:AsyncCallback&lt;number&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextverifypermission7)<br>[verifyPermission(permission:string,callback:AsyncCallback&lt;number&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextverifypermission7-1)<br>[verifyPermission(permission:string,options?:PermissionOptions):Promise&lt;number&gt;;](../reference/apis/js-apis-inner-app-context.md#contextverifypermission7-2) | \@ohos.abilityAccessCtrl.d.ts | [verifyAccessTokenSync(tokenID: number, permissionName: Permissions): GrantStatus;](../reference/apis/js-apis-abilityAccessCtrl.md#verifyaccesstokensync9)<br>[verifyAccessToken(tokenID: number, permissionName: Permissions): Promise&lt;GrantStatus&gt;;](../reference/apis/js-apis-abilityAccessCtrl.md#verifyaccesstoken9) |
-| [requestPermissionsFromUser(permissions:Array&lt;string&gt;,requestCode:number,resultCallback:AsyncCallback&lt;PermissionRequestResult&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextrequestpermissionsfromuser7)<br/>[requestPermissionsFromUser(permissions:Array&lt;string&gt;,requestCode:number):Promise&lt;PermissionRequestResult&gt;;](../reference/apis/js-apis-inner-app-context.md#contextrequestpermissionsfromuser7-1) | \@ohos.abilityAccessCtrl.d.ts | [requestPermissionsFromUser(context: Context, permissionList: Array&lt;Permissions&gt;, requestCallback: AsyncCallback&lt;PermissionRequestResult&gt;) : void;](../reference/apis/js-apis-abilityAccessCtrl.md#requestpermissionsfromuser9)<br/>[requestPermissionsFromUser(context: Context, permissionList: Array&lt;Permissions&gt;) : Promise&lt;PermissionRequestResult&gt;;](../reference/apis/js-apis-abilityAccessCtrl.md#requestpermissionsfromuser9-1) |
+| [requestPermissionsFromUser(permissions:Array&lt;string&gt;,requestCode:number,resultCallback:AsyncCallback&lt;PermissionRequestResult&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextrequestpermissionsfromuser7)<br>[requestPermissionsFromUser(permissions:Array&lt;string&gt;,requestCode:number):Promise&lt;PermissionRequestResult&gt;;](../reference/apis/js-apis-inner-app-context.md#contextrequestpermissionsfromuser7-1) | \@ohos.abilityAccessCtrl.d.ts | [requestPermissionsFromUser(context: Context, permissionList: Array&lt;Permissions&gt;, requestCallback: AsyncCallback&lt;PermissionRequestResult&gt;) : void;](../reference/apis/js-apis-abilityAccessCtrl.md#requestpermissionsfromuser9)<br>[requestPermissionsFromUser(context: Context, permissionList: Array&lt;Permissions&gt;) : Promise&lt;PermissionRequestResult&gt;;](../reference/apis/js-apis-abilityAccessCtrl.md#requestpermissionsfromuser9-1) |
 | [getApplicationInfo(callback:AsyncCallback&lt;ApplicationInfo&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextgetapplicationinfo7)<br>[getApplicationInfo():Promise&lt;ApplicationInfo&gt;;](../reference/apis/js-apis-inner-app-context.md#contextgetapplicationinfo7-1) | application\Context.d.ts | [applicationInfo: ApplicationInfo;](../reference/apis/js-apis-inner-application-context.md#attributes)|
 | [getBundleName(callback : AsyncCallback&lt;string&gt;): void;](../reference/apis/js-apis-inner-app-context.md#contextgetbundlename7)<br>[getBundleName(): Promise&lt;string&gt;;](../reference/apis/js-apis-inner-app-context.md#contextgetbundlename7-1) | application\UIAbilityContext.d.ts | [abilityInfo.bundleName: string;](../reference/apis/js-apis-inner-application-uiAbilityContext.md#attributes)|
 | [getDisplayOrientation(callback : AsyncCallback&lt;bundle.DisplayOrientation&gt;): void;](../reference/apis/js-apis-inner-app-context.md#contextgetdisplayorientation7)<br>[getDisplayOrientation(): Promise&lt;bundle.DisplayOrientation&gt;;](../reference/apis/js-apis-inner-app-context.md#contextgetdisplayorientation7-1) | \@ohos.screen.d.ts | [readonly orientation: Orientation;](../reference/apis/js-apis-screen.md#orientation) |
@@ -26,3 +26,5 @@
 | [getAbilityInfo(callback:AsyncCallback&lt;AbilityInfo&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextgetabilityinfo7)<br>[getAbilityInfo():Promise&lt;AbilityInfo&gt;;](../reference/apis/js-apis-inner-app-context.md#contextgetabilityinfo7-1) | application\UIAbilityContext.d.ts | [abilityInfo: AbilityInfo;](../reference/apis/js-apis-inner-application-uiAbilityContext.md#attributes)|
 | [isUpdatingConfigurations(callback:AsyncCallback&lt;boolean&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextisupdatingconfigurations7)<br>[isUpdatingConfigurations():Promise&lt;boolean&gt;;](../reference/apis/js-apis-inner-app-context.md#contextisupdatingconfigurations7-1) | There is no corresponding API in the stage model.| OpenHarmony applications do not restart when the system environment changes. The **onConfigurationUpdated** callback is invoked to notify the applications of the changes. This API provides an empty implementation in the FA model, and the stage model does not provide a corresponding API.|
 | [printDrawnCompleted(callback:AsyncCallback&lt;void&gt;):void;](../reference/apis/js-apis-inner-app-context.md#contextprintdrawncompleted7)<br>[printDrawnCompleted():Promise&lt;void&gt;;](../reference/apis/js-apis-inner-app-context.md#contextprintdrawncompleted7-1) | There is no corresponding API in the stage model.| This API provides an empty implementation in the FA model. The stage model does not provide a corresponding API.|
+
+ <!--no_check--> 
\ No newline at end of file

en/application-dev/application-models/create-dataability.md

@@ -9,18 +9,18 @@ The following sample code shows how to create a DataAbility:
 ```ts
 import featureAbility from '@ohos.ability.featureAbility'
 import dataAbility from '@ohos.data.dataAbility'
-import dataRdb from '@ohos.data.rdb'
+import relationalStore from '@ohos.data.relationalStore'
 
 const TABLE_NAME = 'book'
 const STORE_CONFIG = { name: 'book.db' }
 const SQL_CREATE_TABLE = 'CREATE TABLE IF NOT EXISTS book(id INTEGER PRIMARY KEY AUTOINCREMENT, name TEXT NOT NULL, introduction TEXT NOT NULL)'
-let rdbStore: dataRdb.RdbStore = undefined
+let rdbStore: relationalStore.RdbStore = undefined
 
 export default {
   onInitialized(abilityInfo) {
     console.info('DataAbility onInitialized, abilityInfo:' + abilityInfo.bundleName)
     let context = featureAbility.getContext()
-    dataRdb.getRdbStore(context, STORE_CONFIG, 1, (err, store) => {
+    relationalStore.getRdbStore(context, STORE_CONFIG, (err, store) => {
       console.info('DataAbility getRdbStore callback')
       store.executeSql(SQL_CREATE_TABLE, [])
       rdbStore = store

en/application-dev/application-models/data-share-via-want.md

@@ -48,9 +48,9 @@ function implicitStartAbility() {
     }
   }
   context.startAbility(wantInfo).then(() => {
-    // ...
+    ...
   }).catch((err) => {
-    // ...
+    ...
   })
 }
 ```
@@ -66,8 +66,7 @@ In the preceding code, under the custom field **parameters**, the following **ab
 - **ability.picker.fileSizes**: file size, in bytes.
 - **ability.picker.fileNames** and **ability.picker.fileSizes** are arrays and have a one-to-one mapping.
 
-The following figure shows an example. 
-
+The following figure shows an example.  
 ![](figures/ability-startup-with-implicit-want2.png)
 
 ## Shared Party
@@ -77,17 +76,17 @@ To enable the shared party to identify the shared content, configure **skills**
 ```json
 {
   "module": {
-    // ...
+    ...
     "abilities": [
       {
-        // ...
+        ...
         "skills": [
           {
-            // ...
+            ...
             "actions": [
               "action.system.home",
               "ohos.want.action.sendData"
-              // ...
+              ...
             ],
             "uris": [
               {
@@ -102,7 +101,7 @@ To enable the shared party to identify the shared content, configure **skills**
 }
 ```
 
-After the user selects an application, the Want nested in the **ability.want.params.INTENT** field is passed to that application. The UIAbility of the shared party, after being started, can call [onCreate()](../reference/apis/js-apis-app-ability-uiAbility.md#uiabilityoncreate) or [onNewWant()](../reference/apis/js-apis-app-ability-uiAbility.md#uiabilityonnewwant) to obtain the passed Want.
+After the user selects an application, the Want nested in the **ability.want.params.INTENT** field is passed to that application. After the UIAbility of the application starts, the application obtains **want** information from [**onCreate()**](../reference/apis/js-apis-app-ability-uiAbility.md#uiabilityoncreate) or [**onNewWant()**](../reference/apis/js-apis-app-ability-uiAbility.md#uiabilityonnewwant).
 
 The following is an example of the Want obtained. You can use the FD of the shared file to perform required operations.
 

en/application-dev/application-models/dataability-switch.md

@@ -7,9 +7,9 @@ The DataAbility component in the FA model corresponds to the DataShareExtensionA
 The DataShareExtensionAbility class provides system APIs. Only system applications can create DataShareExtensionAbility instances. Therefore, DataAbility switching adopts different policies for system applications and third-party applications.  
 
 
-## Switching a DataAbility of a System Application
+## Switching a DataAbility for a System Application
 
-The procedure for switching a DataAbility of a system application is similar to the procedure of PageAbility switching.
+The procedure for switching a DataAbility for a system application is similar to the procedure of PageAbility switching.
 
 1. Create a DataShareExtensionAbility in the stage model.
 
@@ -34,7 +34,7 @@ The procedure for switching a DataAbility of a system application is similar to
    | call?(method: string, arg: string, extras: PacMap, callback: AsyncCallback<PacMap>): void | NA | This method is not provided in the stage model. You need to implement the functionality based on service functions.|
 
 
-## Switching a DataAbility of a Third-Party Application
+## Switching a DataAbility for a Third-Party Application
 
 In the stage model, third-party applications cannot provide data services for other third-party applications. You can select a switching solution based on your service requirements.
 

en/application-dev/application-models/dataabilityhelper-switch.md

 # DataAbilityHelper 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| 
 | -------- | -------- | -------- |
 | [openFile(uri: string, mode: string, callback: AsyncCallback&lt;number&gt;): void;](../reference/apis/js-apis-inner-ability-dataAbilityHelper.md#dataabilityhelperopenfile)<br>[openFile(uri: string, mode: string): Promise&lt;number&gt;;](../reference/apis/js-apis-inner-ability-dataAbilityHelper.md#dataabilityhelperopenfile-1) | \@ohos.data.fileAccess.d.ts | [openFile(uri: string, flags: OPENFLAGS) : Promise&lt;number&gt;;](../reference/apis/js-apis-fileAccess.md#fileaccesshelperopenfile)<br>[openFile(uri: string, flags: OPENFLAGS, callback: AsyncCallback&lt;number&gt;) : void;](../reference/apis/js-apis-fileAccess.md#fileaccesshelperopenfile) |
 | [on(type: 'dataChange', uri: string, callback: AsyncCallback&lt;void&gt;): void;](../reference/apis/js-apis-inner-ability-dataAbilityHelper.md#dataabilityhelperon) | \@ohos.data.dataShare.d.ts | [on(type: 'dataChange', uri: string, callback: AsyncCallback&lt;void&gt;): void;](../reference/apis/js-apis-data-dataShare.md#ondatachange) |

en/application-dev/application-models/datashareextensionability.md

-# 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 [Cross-Application Data Sharing Overview](../database/share-device-data-across-apps-overview.md).

en/application-dev/application-models/enterprise-extensionAbility.md

-# EnterpriseAdminExtensionAbility Development
+# EnterpriseAdminExtensionAbility
 
 ## Introduction to EnterpriseAdminExtensionAbility
 
@@ -8,34 +8,35 @@ EnterpriseAdminExtensionAbility is a mandatory component for Mobile Device Manag
 
 EnterpriseAdminExtensionAbility is applicable only to enterprise administrator applications.
 
-## Observing Activation/Deactivation of a Device Administrator Application and Installation/Removal of an Application
+
+## Observing Activation/Deactivation of a Device Administrator Application and Installation/Uninstallation of an Application
 
 ### Overview
 
-**onAdminEnabled**: When an enterprise administrator or employee deploys an MDM application and activates the device administrator application, this callback is invoked to notify the MDM application that the DeviceAdmin permission is activated. The initialization policy of the MDM application can set in **onAdminEnabled**.
+**onAdminEnabled**: called when an enterprise administrator or employee deploys an MDM application and enables the DeviceAdmin permission for the application. The MDM application can set the initialization policy in the **onAdminEnabled** callback.
 
-**onAdminDisabled**: When the device administrator application is deactivated, the callback is invoked to notify the MDM application that the DeviceAdmin permission is deactivated.
+**onAdminDisabled**: called when the system or employee disables the DeviceAdmin permission to notify the enterprise administrator that the device is no longer managed.
 
-**onBundleAdded**: The enterprise administrator can subscribe to application installation and uninstallation events. When an application is installed on an enterprise device, the MDM application reports the event in this callback to notify the enterprise administrator.
+**onBundleAdded**: The enterprise administrator can subscribe to application installation events. When an application is installed on an enterprise device, the MDM application reports the event in this callback to notify the enterprise administrator.
 
-**onBundleRemoved**: When an application is removed from an enterprise device, the MDM application reports the event in this callback to notify the enterprise administrator.
+**onBundleRemoved**: The enterprise administrator can subscribe to application uninstallation events. When an application is uninstalled on an enterprise device, the MDM application reports the event in this callback to notify the enterprise administrator.
 
 ### 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 | onBundleRemoved(bundleName: string): void | Called when an application is removed from a device.            |
+| EnterpriseAdminExtensionAbility | onAdminEnabled(): void                    | Called when the device administrator application is disabled.  |
+| EnterpriseAdminExtensionAbility | onAdminDisabled(): void                   | Called when the device administrator application is enabled.|
+| EnterpriseAdminExtensionAbility | onBundleAdded(bundleName: string): void   | Called when the MDM application is installed.            |
+| EnterpriseAdminExtensionAbility | onBundleRemoved(bundleName: string): void | Called when the MDM application is uninstalled.            |
 
 ### 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 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.
+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. Customize a class that inherits from **EnterpriseAdminExtensionAbility** and add the required 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';

en/application-dev/application-models/explicit-implicit-want-mappings.md

 # Matching Rules of Explicit Want and Implicit Want
 
-Both explicit Want and implicit Want can be used to match an ability to start based on certain rules. These rules determine how the parameters set in Want match the configuration file declared by the target ability.
+Both explicit [Want](../reference/apis/js-apis-app-ability-want.md) and implicit [Want](../reference/apis/js-apis-app-ability-want.md) can be used to match an application component to start based on certain rules. These rules determine how the parameters set in [want](../reference/apis/js-apis-app-ability-want.md) match the configuration file declared by the target application component.
 
 ## Matching Rules of Explicit Want
 
 
-The table below describes the matching rules of explicit Want.
+The table below describes the matching rules of explicit [Want](../reference/apis/js-apis-app-ability-want.md).
 
 | Name| Type| Matching Item| Mandatory| Rule Description|
 | -------- | -------- | -------- | -------- | -------- |
-| deviceId | string | Yes| No| If this field is unspecified, only abilities on the local device are matched.|
+| deviceId | string | Yes| No| If this field is unspecified, only application components on the local device are matched.|
 | bundleName | string | Yes| Yes| If **abilityName** is specified but **bundleName** is unspecified, the matching fails.|
-| moduleName | string | Yes| No| If this field is unspecified and multiple modules with the same ability name exist in the application, the first ability is matched by default.|
+| moduleName | string | Yes| No| If this field is unspecified and multiple modules with the same ability name exist in the application, the first application component is matched by default.|
 | abilityName | string | Yes| Yes| To use explicit Want, this field must be specified.|
-| uri | string | No| No| This field is not used for matching. It is passed to the target ability as a parameter.|
-| type | string | No| No| This field is not used for matching. It is passed to the target ability as a parameter.|
-| action | string | No| No| This field is not used for matching. It is passed to the target ability as a parameter.|
-| entities | Array<string> | No| No| This field is not used for matching. It is passed to the target ability as a parameter.|
+| uri | string | No| No| This field is not used for matching. It is passed to the target application component as a parameter.|
+| type | string | No| No| This field is not used for matching. It is passed to the target application component as a parameter.|
+| action | string | No| No| This field is not used for matching. It is passed to the target application component as a parameter.|
+| entities | Array<string> | No| No| This field is not used for matching. It is passed to the target application component as a parameter.|
 | flags | number | No| No| This field is not used for matching and is directly transferred to the system for processing. It is generally used to set runtime information, such as URI data authorization.|
-| parameters | {[key: string]: any} | No| No| This field is not used for matching. It is passed to the target ability as a parameter.|
+| parameters | {[key: string]: any} | No| No| This field is not used for matching. It is passed to the target application component as a parameter.|
 
 ## Matching Rules for Implicit Want
 
-The table below describes the matching rules of implicit Want.
+The table below describes the matching rules of implicit [Want](../reference/apis/js-apis-app-ability-want.md).
 
 | Name       | Type                          | Matching Item| Mandatory| Rule Description                                                        |
 | ----------- | ------------------------------ | ------ | ---- | ------------------------------------------------------------ |
@@ -35,30 +35,32 @@ The table below describes the matching rules of implicit Want.
 | action      | string                         | Yes    | No  |                                                              |
 | entities    | Array<string>            | Yes    | No  |                                                              |
 | flags       | number                         | No    | No  | This field is not used for matching and is directly transferred to the system for processing. It is generally used to set runtime information, such as URI data authorization.|
-| parameters  | {[key: string]: any} | No    | No  | This field is not used for matching. It is passed to the target ability as a parameter.         |
+| parameters  | {[key: string]: any} | No    | No  | This field is not used for matching. It is passed to the target application component as a parameter.        |
 
 Get familiar with the following about implicit Want:
 
 
 - The **want** parameter passed by the caller indicates the operation to be performed by the caller. It also provides data and application type restrictions.
 
-- The **skills** field declares the capabilities of the target ability. For details, see [the skills tag](../quick-start/module-configuration-file.md#skills) in the [module.json5 file](../quick-start/module-configuration-file.md).
+- The **skills** field declares the capabilities of the target application component. For details, see [the skills tag](../quick-start/module-configuration-file.md#skills) in the [module.json5 file](../quick-start/module-configuration-file.md).
 
 
-The system matches the **want** parameter (including the **action**, **entities**, **uri**, and **type** attributes) passed by the caller against the **skills** configuration (including the **actions**, **entities**, **uris**, and **type** attributes) of the abilities one by one. When all the four attributes are matched, a dialog box is displayed for users to select a matched application.
+The system matches the **want** parameter (including the **action**, **entities**, **uri**, and **type** attributes) passed by the caller against the **skills** configuration (including the **actions**, **entities**, **uris**, and **type** attributes) of the application components one by one. When all the four attributes are matched, a dialog box is displayed for users to select a matched application.
 
 
 ### Matching Rules of action in the want Parameter
 
-The system matches the **action** attribute in the **want** parameter passed by the caller against **actions** under **skills** of the abilities.
+The system matches the **action** attribute in the **want** parameter passed by the caller against **actions** under **skills** of the application components.
 
-- If **action** in the passed **want** parameter is specified but **actions** under **skills** of an ability is unspecified, the matching fails.
+- If **action** in the passed **want** parameter is unspecified and **actions** under **skills** of an application component is unspecified, the matching fails.
 
-- If **action** in the passed **want** parameter is unspecified but **actions** under **skills** of an ability is specified, the matching is successful.
+- If **action** in the passed **want** parameter is specified but **actions** under **skills** of an application component is unspecified, the matching fails.
 
-- If **action** in the passed **want** parameter is specified, and **actions** under **skills** of an ability is specified and contains **action** in the passed **want** parameter, the matching is successful.
+- If **action** in the passed **want** parameter is unspecified but **actions** under **skills** of an application component is specified, the matching is successful.
 
-- If **action** in the passed **want** parameter is specified, and **actions** under **skills** of an ability is specified but does not contain **action** in the passed **want** parameter, the matching fails.
+- If **action** in the passed **want** parameter is specified, and **actions** under **skills** of an application component is specified and contains **action** in the passed **want** parameter, the matching is successful.
+
+- If **action** in the passed **want** parameter is specified, and **actions** under **skills** of an application component is specified but does not contain **action** in the passed **want** parameter, the matching fails.
 
   **Figure 1** Matching rules of action in the want parameter
 
@@ -67,55 +69,56 @@ The system matches the **action** attribute in the **want** parameter passed by
 
 ### Matching Rules of entities in the want Parameter
 
-The system matches the **entities** attribute in the **want** parameter passed by the caller against **entities** under **skills** of the abilities.
+The system matches the **entities** attribute in the **want** parameter passed by the caller against **entities** under **skills** of the application components.
 
-- If **entities** in the passed **want** parameter is unspecified but **entities** under **skills** of an ability is specified, the matching is successful.
+- If **entities** in the passed **want** parameter is unspecified but **entities** under **skills** of an application component is specified, the matching is successful.
 
-- If **entities** in the passed **want** parameter is unspecified but **entities** under **skills** of an ability is unspecified, the matching is successful.
+- If **entities** in the passed **want** parameter is unspecified but **entities** under **skills** of an application component is unspecified, the matching is successful.
 
-- If **entities** in the passed **want** parameter is specified but **entities** under **skills** of an ability is unspecified, the matching fails.
+- If **entities** in the passed **want** parameter is specified but **entities** under **skills** of an application component is unspecified, the matching fails.
 
-- If **entities** in the passed **want** parameter is specified, and **entities** under **skills** of an ability is specified and contains **entities** in the passed **want** parameter, the matching is successful.
+- If **entities** in the passed **want** parameter is specified, and **entities** under **skills** of an application component is specified and contains **entities** in the passed **want** parameter, the matching is successful.
 
-- If **entities** in the passed **want** parameter is specified, and **entities** under **skills** of an ability is specified but does not contain **entities** in the passed **want** parameter, the matching fails.
+- If **entities** in the passed **want** parameter is specified, and **entities** under **skills** of an application component is specified but does not contain **entities** in the passed **want** parameter, the matching fails.
 
-  **Figure 2** Matching rule of entities in the want parameter
+  **Figure 2** Matching rules of entities in the want parameter
 
   ![want-entities](figures/want-entities.png)  
 
 
 ### Matching Rules of uri and type in the want Parameter
 
-When the **uri** and **type** parameters are specified in the **want** parameter to initiate a component startup request, the system traverses the list of installed components and matches the **uris** array under **skills** of the abilities one by one. If one of the **uris** arrays under **skills** matches the **uri** and **type** in the passed **want**, the matching is successful.
+When the **uri** and **type** parameters are specified in the **want** parameter to initiate an application component startup request, the system traverses the list of installed components and matches the **uris** array under **skills** of the application components one by one. If one of the **uris** arrays under **skills** matches the **uri** and **type** in the passed **want**, the matching is successful.
 
 There are four combinations of **uri** and **type** settings. The matching rules are as follows:
 
 - Neither **uri** or **type** is specified in the **want** parameter.
-  - If the **uris** array under **skills** of an ability is unspecified, the matching is successful.
-  - If the **uris** array under **skills** of an ability contains an URI element whose **scheme** and **type** are unspecified, the matching is successful.
+  - If the **uris** array under **skills** of an application component is unspecified, the matching is successful.
+  - If the **uris** array under **skills** of an application component contains an URI element whose **scheme** and **type** are unspecified, the matching is successful.
   - In other cases, the matching fails.
 
 - Only **uri** is specified in the **want** parameter.
-  - If the **uris** array under **skills** of an ability is unspecified, the matching fails.
-  - If the **uris** array under **skills** of an ability contains an element whose [uri is matched](#matching-rules-of-uri) and **type** is unspecified, the matching is successful. Otherwise, the matching fails.
+  - If the **uris** array under **skills** of an application component is unspecified, the matching fails.
+  - If the **uris** array under **skills** of an application component contains an element whose [uri is matched](#matching-rules-of-uri) and **type** is unspecified, the matching is successful. Otherwise, the matching fails.
 
 - Only **type** is specified in the **want** parameter.
-  - If the **uris** array under **skills** of an ability is unspecified, the matching fails.
-  - If the **uris** array under **skills** of an ability contains an URI element whose **scheme** is unspecified and [type is matched](#matching-rules-of-type), the matching is successful. Otherwise, the matching fails.
+  - If the **uris** array under **skills** of an application component is unspecified, the matching fails.
+  - If the **uris** array under **skills** of an application component contains an URI element whose **scheme** is unspecified and [type is matched](#matching-rules-of-type), the matching is successful. Otherwise, the matching fails.
 
-- Both **uri** and **type** are specified in the **want** parameter, as shown in Figure 3.
-  - If the **uris** array under **skills** of an ability is unspecified, the matching fails.
-  - If the **uris** array under **skills** of an ability contains an element whose [uri is matched](#matching-rules-of-uri) and [type is matched](#matching-rules-of-type), the matching is successful. Otherwise, the matching fails.
+- Both **uri** and **type** are specified in the **want** parameter, as shown below.
+  - If the **uris** array under **skills** of an application component is unspecified, the matching fails.
+  - If the **uris** array under **skills** of an application component contains an element whose [uri is matched](#matching-rules-of-uri) and [type is matched](#matching-rules-of-type), the matching is successful. Otherwise, the matching fails.
 
-Leftmost URI matching: When only **scheme**, a combination of **scheme** and **host**, or a combination of **scheme**, **host**, and **port** is configured in the **uris** array under **skills** of the ability,
-the matching is successful only if the leftmost URI in the passed **want** parameter matches **scheme**, the combination of **scheme** and **host**, or the combination of **scheme**, **host**, and **port**.
+Leftmost URI matching: When only **scheme**, a combination of **scheme** and **host**, or a combination of **scheme**, **host**, and **port** is configured in the **uris** array under **skills** of the application component, the matching is successful only if the leftmost URI in the passed **want** parameter matches **scheme**, the combination of **scheme** and **host**, or the combination of **scheme**, **host**, and **port**.
 
 **Figure 3** Matching rules when uri and type are specified in the want parameter
 
-  ![want-uri-type1](figures/want-uri-type1.png)  
+![want-uri-type1](figures/want-uri-type1.png)  
 
+To simplify the description:
 
-To simplify the description, **uri** and **type** passed in the **want** parameter are called **w_uri** and **w_type**, respectively; the **uris** array under **skills** of an ability to match is called **s_uris**; each element in the array is called **s_uri**. Matching is performed from top to bottom.
+- **uri** in the **want** parameter passed in by the caller is called **w_uri**; each element in the **uris** array under **skills** of the application component to match is called **s_uri**.
+- **type** in the **want** parameter passed in by the caller is called **w_type**; the type in the **uris** array under **skills** of the application component to match is called **s_type**.
 
 **Figure 4** Matching rules of uri and type in the want parameter
 
@@ -124,7 +127,7 @@ To simplify the description, **uri** and **type** passed in the **want** paramet
 
 ### Matching Rules of uri
 
-To simplify the description, **uri** in the passed **want** parameter is called **w_uri**; **uri** under **skills** of an ability to match is called **s_uri**. The matching rules are as follows:
+The rules are as follows:
 
 - If **scheme** of **s_uri** is unspecified and **w_uri** is unspecified, the matching is successful. Otherwise, the matching fails.
 
@@ -142,18 +145,15 @@ To simplify the description, **uri** in the passed **want** parameter is called
 
 > **NOTE**
 >
-> The **scheme**, **host**, **port**, **path**, **pathStartWith**, and **pathRegex** attributes of **uris** under **skills** of an ability are concatenated. If **path**, **pathStartWith**, and **pathRegex** are declared in sequence, **uris** can be concatenated into the following expressions:
-> 
-> - **Full path expression**: `scheme://host:port/path`
-> 
-> - **Prefix expression**: `scheme://host:port/pathStartWith`
-> 
-> - **Regular expression**: `scheme://host:port/pathRegex`
+> The **scheme**, **host**, **port**, **path**, **pathStartWith**, and **pathRegex** attributes of **uris** under **skills** of an application component are concatenated. If **path**, **pathStartWith**, and **pathRegex** are declared in sequence, **uris** can be concatenated into the following expressions:
 >
 > - **Prefix URI expression**: When only **scheme**, a combination of **scheme** and **host**, or a combination of **scheme**, **host**, and **port** is configured in the configuration file, the matching is successful if a URI prefixed with the configuration file is passed in.
 >     * `scheme://`
 >     * `scheme://host`
 >     * `scheme://host:port`
+> - **Full path expression**: `scheme://host:port/path`
+> - **Prefix expression**: `scheme://host:port/pathStartWith`
+> - **Regular expression**: `scheme://host:port/pathRegex`
 
 
 ### Matching Rules of type
@@ -162,7 +162,7 @@ To simplify the description, **uri** in the passed **want** parameter is called
 >
 > The matching rules of **type** described in this section are based on the fact that **type** in the **want** parameter is specified. If **type** is unspecified, follow the [matching rules of uri and type in the want parameter](#matching-rules-of-uri-and-type-in-the-want-parameter).
 
-To simplify the description, **uri** in the passed **want** parameter is called **w_type**, and **type** of **uris** under **skills** of an ability to match is called **s_type**. The matching rules are as follows:
+The matching rules are as follows:
 
 - If **s_type** is unspecified, the matching fails.
 

en/application-dev/application-models/extensionability-overview.md

-# ExtensionAbility Component Overview
+# ExtensionAbility Overview
 
 
-The ExtensionAbility component is used for specific scenarios such as widgets and input methods.
+The ExtensionAbility component is used for specific scenarios such as widget development and input method development.
 
 
-An [ExtensionAbilityType](../reference/apis/js-apis-bundleManager.md#extensionabilitytype) is provided for every specific scenario. All types of ExtensionAbility components are managed by the corresponding system services in a unified manner. For example, the InputMethodExtensionAbility component is managed by the input method management service. The following ExtensionAbility types are supported:
+An [ExtensionAbility type](../reference/apis/js-apis-bundleManager.md#extensionabilitytype) is provided for every specific scenario. All types of ExtensionAbility components are managed by the corresponding system services in a unified manner. For example, the InputMethodExtensionAbility component is managed by the input method management service. The following ExtensionAbility types are supported:
 
 
 - [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md): ExtensionAbility component of the form type, which provides APIs related to widgets.
 
 - [WorkSchedulerExtensionAbility](../reference/apis/js-apis-WorkSchedulerExtensionAbility.md): ExtensionAbility component of the work_scheduler type, which provides callbacks for Work Scheduler tasks.
 
-- [InputMethodExtensionAbility](../reference/apis/js-apis-inputmethod.md): ExtensionAbility component of the input_method type, which provides an input method framework that can be used to hide the keyboard, obtain the list of installed input methods, display the dialog box for input method selection, and more.
+- [InputMethodExtensionAbility](../reference/apis/js-apis-inputmethod.md): ExtensionAbility component of the input_method type, which is used to develop input method applications.
 
-- [ServiceExtensionAbility](../reference/apis/js-apis-app-ability-serviceExtensionAbility.md): ExtensionAbility component of the service type, which provides APIs related to background service scenarios.
+- [ServiceExtensionAbility](../reference/apis/js-apis-app-ability-serviceExtensionAbility.md): ExtensionAbility component of the service type, which provides APIs related to background services.
 
 - [AccessibilityExtensionAbility](../reference/apis/js-apis-application-accessibilityExtensionAbility.md): ExtensionAbility component of the accessibility type, which provides APIs related to the accessibility feature.
 
-- [DataShareExtensionAbility](../reference/apis/js-apis-application-dataShareExtensionAbility.md): ExtensionAbility component of the data_share type, which provides APIs for data sharing.
+- [DataShareExtensionAbility (for system applications only)](../reference/apis/js-apis-application-dataShareExtensionAbility.md): ExtensionAbility component of the data_share type, which provides APIs for data sharing.
 
 - [StaticSubscriberExtensionAbility](../reference/apis/js-apis-application-staticSubscriberExtensionAbility.md): ExtensionAbility component of the static_subscriber type, which provides APIs for static broadcast.
 
-- [WindowExtensionAbility](../reference/apis/js-apis-application-windowExtensionAbility.md): ExtensionAbility component of the window type, which allows a system application to be embedded in and displayed over another application.
+- [WindowExtensionAbility (for system applications only)](../reference/apis/js-apis-application-windowExtensionAbility.md): ExtensionAbility component of the window type, which allows a system application to be embedded in and displayed over another application.
 
 - [EnterpriseAdminExtensionAbility](../reference/apis/js-apis-EnterpriseAdminExtensionAbility.md): ExtensionAbility component of the enterprise_admin type, which provides APIs for processing enterprise management events, such as application installation events on devices and events indicating too many incorrect screen-lock password attempts.
 
 > **NOTE**
->
-> 1. Third-party applications cannot implement ServiceExtensionAbility, DataShareExtensionAbility, StaticSubscriberExtensionAbility, or WindowExtensionAbility.
->
-> 2. To implement transaction processing in the background for a third-party application, use background tasks rather than ServiceExtensionAbility. For details, see [Background Task](../task-management/background-task-overview.md).
->
-> 3. Third-party applications can use other types of ExtensionAbility components that have been defined.
+> 
+>- Third-party applications cannot implement ServiceExtensionAbility, DataShareExtensionAbility, StaticSubscriberExtensionAbility, or WindowExtensionAbility. They can use other types of ExtensionAbility components that have been defined.
+> 
+>- To implement transaction processing in the background for a third-party application, use background tasks rather than ServiceExtensionAbility. For details, see [Background Task](../task-management/background-task-overview.md).
+
 
 ## Using ExtensionAbility of the Specified Type
 
-All types of ExtensionAbility components are started by the corresponding system management service, rather than applications, so that their lifecycles are under control by the system. The caller of the ExtensionAbility component does not need to care about its lifecycle.
+Each type of ExtensionAbility component is started by the corresponding system management service, rather than applications, so that its lifecycle is under system control. The caller of the ExtensionAbility component does not need to care about its lifecycle.
 
 The following uses [InputMethodExtensionAbility](../reference/apis/js-apis-inputmethod.md) as an example. As shown in the figure below, when an application calls the InputMethodExtensionAbility component, the input method management service is called first. The input method management service starts the InputMethodExtensionAbility component, returns the component to the application, and starts to manage its lifecycle.
 
@@ -46,23 +45,21 @@ The following uses [InputMethodExtensionAbility](../reference/apis/js-apis-input
 
 ## Implementing ExtensionAbility of the Specified Type
 
-The following uses [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md) as an example. The widget framework provides the base class [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md). You derive this base class to create your own class (such as **MyFormExtensionAbility**), implement the callbacks, such as **onCreate()** and **onUpdateForm()**, to provide specific widget functionalities. For details, see [FormExtensionAbility](service-widget-overview.md).
+The following uses [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md) as an example. The widget framework provides the base class [FormExtensionAbility](../reference/apis/js-apis-app-form-formExtensionAbility.md). You can derive this base class to create your own class (for example, **MyFormExtensionAbility**) and implement the callbacks, such as **onCreate()** and **onUpdateForm()**, to provide specific widget features. For details, see [FormExtensionAbility](service-widget-overview.md).
 
-You do not need to care when to add or delete a widget. The lifecycle of the FormExtensionAbility instance and the lifecycle of the ExtensionAbility process where the FormExtensionAbility instance is located are scheduled and managed by FormManagerService.
+You do not need to care when to add or delete a widget. The lifecycle of the FormExtensionAbility instance and the lifecycle of the ExtensionAbility process where the FormExtensionAbility instance is located are managed by FormManagerService.
 
 ![form_extension](figures/form_extension.png)
 
 
 > **NOTE**
 >
-> For an application, all ExtensionAbility components of the same type run in an independent process, whereas UIAbility, ServiceExtensionAbility, and DataShareExtensionAbility run in another independent process. For details, see [Process Model (Stage Model)](process-model-stage.md).
-> 
-> For example, an application has one UIAbility component, one ServiceExtensionAbility, one DataShareExtensionAbility, two FormExtensionAbility, and one ImeExtensionAbility. When the application is running, there are three processes:
-> 
+> For an application, all ExtensionAbility components of the same type run in an independent process, whereas the UIAbility, ServiceExtensionAbility, and DataShareExtensionAbility components run in another independent process. For details, see [Process Model (Stage Model)](process-model-stage.md).
+>
+> For example, if an application has one UIAbility component, one ServiceExtensionAbility component, one DataShareExtensionAbility component, two FormExtensionAbility components, and one ImeExtensionAbility component, there will be three processes when the application is running.
+>
 > - UIAbility, ServiceExtensionAbility, and DataShareExtensionAbility run in an independent process.
-> 
+>
 > - The two FormExtensionAbility components run in an independent process.
-> 
+>
 > - The two ImeExtensionAbility components run in an independent process.
-
- <!--no_check--> 
\ No newline at end of file

en/application-dev/application-models/fa-model-development-overview.md

@@ -8,8 +8,8 @@ During application development based on the Feature Ability (FA) model, the foll
 
 | Task| Introduction| Guide|
 | -------- | -------- | -------- |
-| Application component development| Use the PageAbility, ServiceAbility, DataAbility, and widgets of the FA model to develop applications.| - [Application- or Component-Level Configuration](application-component-configuration-fa.md)<br>- [PageAbility Component](pageability-overview.md)<br>- [ServiceAbility Component](serviceability-overview.md)<br>- [DataAbility Component](dataability-overview.md)<br>- [Widget Development](Widget-development-fa.md)<br>- [Context](application-context-fa.md)<br>- [Want](want-fa.md) |
-| Inter-process communication (IPC)| Learn the process model and common IPC modes of the FA model.| [Common Events](common-event-fa.md)<br>[Background Services](rpc.md) |
-| Inter-thread communication| Learn the thread model and common inter-thread communication modes of the FA model.| [Inter-Thread Communication](itc-fa-overview.md)|
+| Application component development| Use the PageAbility, ServiceAbility, DataAbility, and widgets of the FA model to develop applications.| - [Application- or Component-Level Configuration](application-component-configuration-fa.md)<br>- [PageAbility Component](pageability-overview.md)<br>- [ServiceAbility Component](serviceability-overview.md)<br>- [DataAbility Component](dataability-overview.md)<br>- [Widget Development](widget-development-fa.md)<br>- [Context](application-context-fa.md)<br>- [Want](want-fa.md)|
+| Process model| Learn the process model and common IPC modes of the FA model.| [Common Events](common-event-fa.md)<br>[Background Services](rpc.md)|
+| Thread model| Learn the thread model and common inter-thread communication modes of the FA model.| [Inter-Thread Communication](itc-fa-overview.md)|
 | Mission management| Learn the basic concepts and typical scenarios of mission management in the FA model.| [Mission Management](mission-management-fa.md)|
-| Application configuration file| Learn the requirements for developing application configuration files in the FA model.| [Application Configuration File](config-file-fa.md) |
+| Application configuration file| Learn the requirements for developing application configuration files in the FA model.| [Application Configuration File](config-file-fa.md)|

en/application-dev/application-models/fa-stage-interaction-overview.md

@@ -4,22 +4,23 @@
 The FA model is supported by API version 8 and earlier versions, and the stage model is recommended since API version 9. The FA model and stage model have their respective components. The FA model provides three types of application components: PageAbility, ServiceAbility, and DataAbility. The stage model provides two types of application components: UIAbility and ExtensionAbility.
 
 
-You cannot use both models for the development of an application (see the figure below). However, a device (system) can contain applications developed on both models (scenario 3 in the figure below). In this case, their components may interact with each other.
+You cannot use both models for the development of an application (see the figure below). However, a device (system) can contain applications developed on different models (scenario 3 in the figure below). In this case, their components may interact with each other.
+
+**Figure 1** Coexistent application components of the FA model and stage model
 
-Figure 1 Coexistent application components of the FA model and stage model 
 ![coexistence-of-FAandStage](figures/coexistence-of-FAandStage.png)
 
 
-The following table lists the possible interaction scenarios. You must pay attention to the concerns listed below during your application development.
+The following table lists the possible interaction scenarios and the concerns of each scenario.
 
 
-Table 1 Application component interaction scenarios
+**Table 1** Application component interaction scenarios
 
 | Interaction Scenario| Concerns|
 | -------- | -------- |
-| [Starting a UIAbility from the FA Model](start-uiability-from-fa.md) | Set **bundleName** and **abilityName** in the **want** parameter to the bundle name and ability name of the UIAbility in the stage model.|
-| [Connecting to a ServiceExtensionAbility from the FA Model](bind-serviceextensionability-from-fa.md) | Set **bundleName** and **abilityName** in the **want** parameter to the bundle name and ability name of the ServiceExtensionAbility in the stage model.|
-| [Accessing a DataShareExtensionAbility from the FA Model](access-datashareextensionability-from-fa.md) | No code modification is required. However, you need to understand the API compatibility of **DataShareHelper** and **DataAbilityHelper**.|
-| [Starting a PageAbility from the Stage Model](start-pageability-from-stage.md) | Set **bundleName** and **abilityName** in the **want** parameter to the bundle name and ability name of the PageAbility in the FA model.|
-| [Connecting to a ServiceAbility from the Stage Model](bind-serviceability-from-stage.md) | Set **bundleName** and **abilityName** in the **want** parameter to the bundle name and ability name of the ServiceAbility in the FA model.|
-| Accessing a DataAbility from the Stage Model | This type of access is not supported.|
+| [Starting a UIAbility from the FA Model](start-uiability-from-fa.md)| Set **bundleName** and **abilityName** in the **want** parameter to the bundle name and ability name of the UIAbility in the stage model.|
+| [Connecting to a ServiceExtensionAbility from the FA Model](bind-serviceextensionability-from-fa.md)| Set **bundleName** and **abilityName** in the **want** parameter to the bundle name and ability name of the ServiceExtensionAbility in the stage model.|
+| [Accessing a DataShareExtensionAbility from the FA Model](access-datashareextensionability-from-fa.md)| No code modification is required. However, you need to understand the API compatibility of **DataShareHelper** and **DataAbilityHelper**.|
+| [Starting a PageAbility from the Stage Model](start-pageability-from-stage.md)| Set **bundleName** and **abilityName** in the **want** parameter to the bundle name and ability name of the PageAbility in the FA model.|
+| [Connecting to a ServiceAbility from the Stage Model](bind-serviceability-from-stage.md)| Set **bundleName** and **abilityName** in the **want** parameter to the bundle name and ability name of the ServiceAbility in the FA model.|
+| Accessing a DataAbility from the Stage Model| This type of access is not supported.|

en/application-dev/application-models/featureability-switch.md

 # featureAbility 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| 
 | -------- | -------- | -------- |
-| [getWant(callback: AsyncCallback&lt;Want&gt;): void;](../reference/apis/js-apis-ability-featureAbility.md#featureabilitygetwant)<br>[getWant(): Promise&lt;Want&gt;;](../reference/apis/js-apis-ability-featureAbility.md#featureabilitygetwant-1) | \@ohos.app.ability.UIAbility.d.ts | [launchWant: Want;](../reference/apis/js-apis-app-ability-uiAbility.md#attributes)|
+| [getWant(callback: AsyncCallback&lt;Want&gt;): void;](../reference/apis/js-apis-ability-featureAbility.md#featureabilitygetwant)<br>[getWant(): Promise&lt;Want&gt;;](../reference/apis/js-apis-ability-featureAbility.md#featureabilitygetwant-1) | \@ohos.app.ability.UIAbility.d.ts | [launchWant: Want;](../reference/apis/js-apis-app-ability-uiAbility.md#attributes)| 
 | [startAbility(parameter: StartAbilityParameter, callback: AsyncCallback&lt;number&gt;): void;](../reference/apis/js-apis-ability-featureAbility.md#featureabilitystartability)<br>[startAbility(parameter: StartAbilityParameter): Promise&lt;number&gt;;](../reference/apis/js-apis-ability-featureAbility.md#featureabilitystartability-1) | application\UIAbilityContext.d.ts | [startAbility(want: Want, callback: AsyncCallback&lt;void&gt;): void;](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstartability)<br>[startAbility(want: Want, options: StartOptions, callback: AsyncCallback&lt;void&gt;): void;](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstartability-1)<br>[startAbility(want: Want, options?: StartOptions): Promise&lt;void&gt;;](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstartability-2) |
 | [getContext(): Context;](../reference/apis/js-apis-ability-featureAbility.md#featureabilitygetcontext) | \@ohos.app.ability.UIAbility.d.ts | [context: UIAbilityContext;](../reference/apis/js-apis-app-ability-uiAbility.md#attributes)|
 | [startAbilityForResult(parameter: StartAbilityParameter, callback: AsyncCallback&lt;AbilityResult&gt;): void;](../reference/apis/js-apis-ability-featureAbility.md#featureabilitystartabilityforresult7)<br>[startAbilityForResult(parameter: StartAbilityParameter): Promise&lt;AbilityResult&gt;;](../reference/apis/js-apis-ability-featureAbility.md#featureabilitystartabilityforresult7-1) | application\UIAbilityContext.d.ts | [startAbilityForResult(want: Want, callback: AsyncCallback&lt;AbilityResult&gt;): void;](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstartabilityforresult)<br>[startAbilityForResult(want: Want, options: StartOptions, callback: AsyncCallback&lt;AbilityResult&gt;): void;](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstartabilityforresult-1)<br>[startAbilityForResult(want: Want, options?: StartOptions): Promise&lt;AbilityResult&gt;;](../reference/apis/js-apis-inner-application-uiAbilityContext.md#abilitycontextstartabilityforresult-2) |

en/application-dev/application-models/hop-cross-device-migration.md

@@ -3,7 +3,7 @@
 
 ## When to Use
 
-The main task of cross-device migration is to migrate the current task (including the page control status) of an application to the target device so that the task can continue on it. Cross-device migration supports the following functionalities:
+The main task of cross-device migration is to migrate the current task (including the page control status) of an application to the target device so that the task can continue on it. Cross-device migration supports the following features:
 
 - Storage and restoration of custom data
 
@@ -16,7 +16,8 @@ The main task of cross-device migration is to migrate the current task (includin
 
 The following figure shows the cross-device migration process.
 
-**Figure 1** Cross-device migration process 
+**Figure 1** Cross-device migration process
+
 ![hop-cross-device-migration](figures/hop-cross-device-migration.png)
 
 
@@ -49,27 +50,27 @@ The table below describes the main APIs used for cross-device migration. For det
 
 1. Request the **ohos.permission.DISTRIBUTED_DATASYNC** permission. For details, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file).
 
-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).
+2. Display a dialog box to ask for 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. Configure the fields related to cross-device migration in the configuration file.
 
    Configure the application to support migration.
    Set the **continuable** field in the **module.json5** file to **true**. The default value is **false**. If this parameter is set to **false**, the application cannot be continued on the target device.
-   
-   
-      ```json
-      {
-        "module": {
-          // ...
-          "abilities": [
-            {
-              // ...
-              "continuable": true,
-            }
-          ]
-        }
-      }
-      ```
+
+
+   ```json
+   {
+     "module": {
+       ...
+       "abilities": [
+         {
+           ...
+           "continuable": true,
+         }
+       ]
+     }
+   }
+   ```
 
    Configure the application launch type. For details, see [UIAbility Component Launch Type](uiability-launch-type.md).
 
@@ -79,23 +80,23 @@ The table below describes the main APIs used for cross-device migration. For det
 
    - Checking application compatibility: You can obtain the version number of the target application from **wantParam** and check the compatibility between the target application and the current application.
 
-   - Making a migration decision: You can determine whether to support the migration based on the return value of **onContinue()**. For details about the return value, see [Available APIs](#available-apis).
+   - Making a migration decision: You can determine whether to support the migration based on the return value of **onContinue()**. For details about the return values, see [Available APIs](#available-apis).
 
      The sample code is as follows:
      
-     ```ts
-     import UIAbility from '@ohos.app.ability.UIAbility';
-     import AbilityConstant from '@ohos.app.ability.AbilityConstant';
-     
-     onContinue(wantParam : {[key: string]: any}) {         
-         console.info(`onContinue version = ${wantParam.version}, targetDevice: ${wantParam.targetDevice}`)         
-         let workInput = AppStorage.Get<string>('ContinueWork');         
-         // Set the user input data into wantParam.        
-         wantParam["work"] = workInput // set user input data into want params         
-         console.info(`onContinue input = ${wantParam["input"]}`);         
-         return AbilityConstant.OnContinueResult.AGREE     
-     }
-     ```
+   ```ts
+   import UIAbility from '@ohos.app.ability.UIAbility';
+   import AbilityConstant from '@ohos.app.ability.AbilityConstant';
+   
+   onContinue(wantParam : {[key: string]: any}) {         
+       console.info(`onContinue version = ${wantParam.version}, targetDevice: ${wantParam.targetDevice}`)         
+       let workInput = AppStorage.Get<string>('ContinueWork');         
+       // Set the user input data into wantParam.        
+       wantParam["work"] = workInput // set user input data into want params         
+       console.info(`onContinue input = ${wantParam["input"]}`);         
+       return AbilityConstant.OnContinueResult.AGREE     
+   }
+   ```
 
 5. Implement **onCreate()** and **onNewWant()** in the UIAbility of the target application to implement data restoration.
    - Implementation example of **onCreate** in the multi-instance scenario

en/application-dev/application-models/hop-multi-device-collaboration.md

@@ -3,7 +3,7 @@
 
 ## When to Use
 
-Multi-device coordination involves the following scenarios:
+Multi-device collaboration involves the following scenarios:
 
 - [Starting UIAbility or ServiceExtensionAbility Across Devices (No Data Returned)](#starting-uiability-or-serviceextensionability-across-devices-no-data-returned)
 
@@ -18,13 +18,14 @@ Multi-device coordination involves the following scenarios:
 
 The figure below shows the multi-device collaboration process.
 
-**Figure 1** Multi-device collaboration process 
+**Figure 1** Multi-device collaboration process
+
 ![hop-multi-device-collaboration](figures/hop-multi-device-collaboration.png)
 
 
 ## Constraints
 
-- Since multi-device collaboration task management is not available, you can obtain the device list by developing system applications. Access to third-party applications is not supported.
+- Since multi-device collaboration task management is not available, you can obtain the device list by developing system applications. Third-party applications cannot access the device list.
 
 - Multi-device collaboration must comply with [Inter-Device Component Startup Rules](component-startup-rules.md#inter-device-component-startup-rules).
 
@@ -51,7 +52,7 @@ On device A, touch the **Start** button provided by the initiator application to
 
 1. Request the **ohos.permission.DISTRIBUTED_DATASYNC** permission. For details, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file).
 
-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).
+2. Display a dialog box to ask for 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. Obtain the device ID of the target device.
 
@@ -63,7 +64,7 @@ On device A, touch the **Start** button provided by the initiator application to
        // createDeviceManager is a system API.
        deviceManager.createDeviceManager('ohos.samples.demo', (err, dm) => {
            if (err) {
-               // ...
+               ...
                return
            }
            dmClass = dm
@@ -94,13 +95,13 @@ On device A, touch the **Start** button provided by the initiator application to
    }
    // context is the AbilityContext of the initiator UIAbility.
    this.context.startAbility(want).then(() => {
-       // ...
+       ...
    }).catch((err) => {
-       // ...
+       ...
    })
    ```
 
-5. Call stopServiceExtensionAbility(../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstopserviceextensionability) to stop the ServiceExtensionAbility when it is no longer required on device B. (This API cannot be used to stop a UIAbility. Users must manually stop a UIAbility through task management.)
+5. Call [stopServiceExtensionAbility](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstopserviceextensionability) to stop the ServiceExtensionAbility when it is no longer required on device B. (This API cannot be used to stop a UIAbility. Users must manually stop a UIAbility through task management.)
 
    ```ts
    let want = {
@@ -119,7 +120,7 @@ On device A, touch the **Start** button provided by the initiator application to
 
 ## Starting UIAbility Across Devices (Data Returned)
 
-On device A, touch the **Start** button provided by the initiator application to start a specified UIAbility on device B. When the UIAbility on device B exits, a value is sent back to the initiator application.
+On device A, touch the **Start** button provided by the initiator application to start a specified UIAbility on device B. When the UIAbility on device B exits, a value is returned to the initiator application.
 
 
 ### Available APIs
@@ -137,7 +138,7 @@ On device A, touch the **Start** button provided by the initiator application to
 
 1. Request the **ohos.permission.DISTRIBUTED_DATASYNC** permission. For details, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file).
 
-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).
+2. Display a dialog box to ask for 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. Set the target component parameters on the initiator, and call **startAbilityForResult()** to start the target UIAbility. **data** in the asynchronous callback is used to receive the information returned by the target UIAbility to the initiator UIAbility after the target UIAbility terminates itself. For details about how to implement **getRemoteDeviceId()**, see [Starting UIAbility or ServiceExtensionAbility Across Devices (No Data Returned)](#starting-uiability-or-serviceextensionability-across-devices-no-data-returned).
 
@@ -150,13 +151,13 @@ On device A, touch the **Start** button provided by the initiator application to
    }
    // context is the AbilityContext of the initiator UIAbility.
    this.context.startAbilityForResult(want).then((data) => {
-       // ...
+       ...
    }).catch((err) => {
-       // ...
+       ...
    })
    ```
 
-4. After the UIAbility task at the target device is complete, call **terminateSelfWithResult()** to return the data to the initiator UIAbility.
+4. After the UIAbility task on the target device is complete, call **terminateSelfWithResult()** to return the data to the initiator UIAbility.
 
    ```ts
    const RESULT_CODE: number = 1001;
@@ -170,7 +171,7 @@ On device A, touch the **Start** button provided by the initiator application to
    }
    // context is the AbilityContext of the target UIAbility.
    this.context.terminateSelfWithResult(abilityResult, (err) => {
-       // ...
+       ...
    });
    ```
 
@@ -179,17 +180,17 @@ On device A, touch the **Start** button provided by the initiator application to
    ```ts
    const RESULT_CODE: number = 1001;
    
-   // ...
+   ...
    
    // context is the UIAbilityContext of the initiator UIAbility.
    this.context.startAbilityForResult(want).then((data) => {
        if (data?.resultCode === RESULT_CODE) {
            // Parse the information returned by the target UIAbility.
            let info = data.want?.parameters?.info
-           // ...
+           ...
        }
    }).catch((err) => {
-       // ...
+       ...
    })
    ```
 
@@ -214,7 +215,7 @@ A system application can connect to a service on another device by calling [conn
 
 1. Request the **ohos.permission.DISTRIBUTED_DATASYNC** permission. For details, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file).
 
-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).
+2. Display a dialog box to ask for 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. (Optional) [Implement a background service](serviceextensionability.md#implementing-a-background-service). Perform this operation only if no background service is available.
 
@@ -223,7 +224,7 @@ A system application can connect to a service on another device by calling [conn
    - Set the target component parameters, including the target device ID, bundle name, and ability name.
    - Call **connectServiceExtensionAbility** to initiate a connection.
    - Receive the service handle returned by the target device when the connection is successful.
-   - Perform cross-device invoking and obtain the result returned by the target service.
+   - Perform cross-device call and obtain the result returned by the target service.
      
       ```ts
       import rpc from '@ohos.rpc';
@@ -311,7 +312,7 @@ The following describes how to implement multi-device collaboration through cros
 
 1. Request the **ohos.permission.DISTRIBUTED_DATASYNC** permission. For details, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file).
 
-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).
+2. Display a dialog box to ask for 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 the CalleeAbility.
    
@@ -444,10 +445,10 @@ The following describes how to implement multi-device collaboration through cros
                    // Register the onRemoteStateChange listener of the CallerAbility.
                    try {
                         caller.onRemoteStateChange((str) => {
-                            console.log('Remote state changed ' + str);
+                            console.info('Remote state changed ' + str);
                         });
                     } catch (error) {
-                        console.log('Caller.onRemoteStateChange catch error, error.code: ${JSON.stringify(error.code)}, error.message: ${JSON.stringify(error.message)}');
+                        console.info('Caller.onRemoteStateChange catch error, error.code: ${JSON.stringify(error.code)}, error.message: ${JSON.stringify(error.message)}');
                     }
                }
            }).catch((error) => {

en/application-dev/application-models/inputmethodextentionability.md

-# InputMethodExtensionAbility Development
+# InputMethodExtensionAbility
 
-[InputMethodExtensionAbility](../reference/apis/js-apis-inputmethod-extension-ability.md) is an ExtensionAbility component of the inputMethod type that provides extension capabilities for the input method framework.
+## When to Use
+[InputMethodExtensionAbility](../reference/apis/js-apis-inputmethod-extension-ability.md), inherited from [ExtensionAbility](extensionability-overview.md), is used for developing input method applications.
 
-InputMethodExtensionAbility can be started or connected by other application components to process transactions in the background based on the request of the caller.
+The entire lifecycle of the [InputMethodExtensionAbility](../reference/apis/js-apis-inputmethod-extension-ability.md) instance and the owning ExtensionAbility process is scheduled and managed by the input method framework. The input method framework provides the [InputMethodExtensionAbility](../reference/apis/js-apis-inputmethod-extension-ability.md) base class. Derive this base class to implement initialization and resource clearing.
 
-
-InputMethodExtensionAbility provides related capabilities through the [InputMethodExtensionContext](../reference/apis/js-apis-inputmethod-extension-context.md).
+[InputMethodExtensionAbility](../reference/apis/js-apis-inputmethod-extension-ability.md) provides related capabilities through [InputMethodExtensionContext](../reference/apis/js-apis-inputmethod-extension-context.md).
 
 
 ## Implementing an Input Method Application
@@ -13,15 +13,13 @@ InputMethodExtensionAbility provides related capabilities through the [InputMeth
 InputMethodExtensionAbility provides the **onCreate()** and **onDestory()** callbacks, as described below. Override them as required.  
 
 - **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.
-  
+
   > **NOTE**
   >
   > If a service has been created, starting it again does not trigger the **onCreate()** callback.
-  
+
 - **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.
 
 
@@ -29,7 +27,7 @@ InputMethodExtensionAbility provides the **onCreate()** and **onDestory()** call
 
 To implement an input method application, manually create an InputMethodExtensionAbility component in DevEco Studio. The procedure is as follows:
 
-In the **ets** directory of the target module, right-click and choose **New** > **Extention Ability** > **InputMethod** to a minimum template of InputMethodExtensionAbility.
+In the **ets** directory of the target module, right-click and choose **New** > **Extension Ability** > **InputMethod** to a minimum template of InputMethodExtensionAbility.
 
 > **NOTE**
 > 
@@ -70,7 +68,7 @@ The minimum template contains four files: **KeyboardController.ts**, **InputMeth
    
      onDestroy() {
        console.log("onDestroy.");
-       this.context.destroy();
+       this.keyboardController.onDestroy(); // Destroy the window and deregister the event listener.
      }
    }
    ```
@@ -109,7 +107,6 @@ The minimum template contains four files: **KeyboardController.ts**, **InputMeth
        this.unRegisterListener();		// Deregister the event listener.
        let win = windowManager.findWindow(this.windowName);
        win.destroyWindow();				// Destroy the window.
-       this.mContext.terminateSelf();	// Terminate the InputMethodExtensionAbility service.
      }
    
      private initWindow(): void		// Initialize the window.
@@ -159,7 +156,7 @@ The minimum template contains four files: **KeyboardController.ts**, **InputMeth
        })
        globalThis.inputAbility.on('inputStop', (imeId) => {
          if (imeId == "Bundle name/Ability name") {
-           this.onDestroy();
+           this.mContext.destroy(); // Destroy the InputMethodExtensionAbility service.
          }
        });
      }
@@ -233,7 +230,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.
 
-   ```ts
+   ```ets
    import { numberSourceListData, sourceListType } from './keyboardKeyData'
    
    @Component
@@ -342,12 +339,12 @@ 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 **srcEntry** to the code path of the InputMethodExtensionAbility component.
+5. Register the InputMethodExtensionAbility in the [module.json5 file](../quick-start/module-configuration-file.md) corresponding to the **Module** project. Set **type** to **"inputMethod"** and **srcEntry** to the code path of the InputMethodExtensionAbility component.
 
    ```ts
    {
      "module": {
-       // ...
+       ...
        "extensionAbilities": [
          {
            "description": "inputMethod",
@@ -364,3 +361,47 @@ The minimum template contains four files: **KeyboardController.ts**, **InputMeth
 
 
 
+## Restrictions
+
+To reduce the risk of abuse of the InputMethodExtensionAbility by third-party applications, the invoking of APIs in the following modules is restricted in the InputMethodExtensionAbility:
+
+> **NOTE**
+>
+> - If a restricted module is imported, no error is reported during compilation, but an incorrect value (**undefined**) is returned during running. As a result, the module does not take effect.
+> - Currently, access to the [@ohos.multimedia.audio (Audio Management)](../reference/apis/js-apis-audio.md) module is allowed, with compliance with the following rules:
+>   - Users who deny the recording permission should still be allowed to use the non-voice-input features of the input method application.
+>   - Recording-related services are allowed only when the InputMethodExtensionAbility is in the foreground. For example, perform recording only when the soft keyboard is in the foreground and the user is proactively using the voice input method; stop recording when the application is switched to the background.
+>   - Applications will see increasingly stringent measures against violations with the preceding rules, and any violation may result in function exceptions.
+
+**Restricted modules:**
+
+- [@ohos.ability.featureAbility (FeatureAbility)](../reference/apis/js-apis-ability-featureAbility.md)
+- [@ohos.ability.particleAbility (ParticleAbility)](../reference/apis/js-apis-ability-particleAbility.md)
+- [@ohos.account.distributedAccount (Distributed Account Management)](../reference/apis/js-apis-distributed-account.md)
+- [@ohos.backgroundTaskManager (Background Task Management)](../reference/apis/js-apis-backgroundTaskManager.md)
+- [@ohos.bluetooth (Bluetooth)](../reference/apis/js-apis-bluetooth.md)
+- [@ohos.bluetoothManager (Bluetooth)](../reference/apis/js-apis-bluetoothManager.md)
+- [@ohos.connectedTag (Active Tags)](../reference/apis/js-apis-connectedTag.md)
+- [@ohos.geolocation (Geolocation)](../reference/apis/js-apis-geolocation.md)
+- [@ohos.geoLocationManager (Geolocation Manager)](../reference/apis/js-apis-geoLocationManager.md)
+- [@ohos.nfc.cardEmulation (Standard NFC Card Emulation)](../reference/apis/js-apis-cardEmulation.md)
+- [@ohos.nfc.controller (Standard NFC)](../reference/apis/js-apis-nfcController.md)
+- [@ohos.nfc.tag (Standard NFC Tags)](../reference/apis/js-apis-nfcTag.md)
+- [@ohos.reminderAgent (Reminder Agent)](../reference/apis/js-apis-reminderAgent.md)
+- [@ohos.reminderAgentManager (reminderAgentManager)](../reference/apis/js-apis-reminderAgentManager.md)
+- [@ohos.sensor (Sensor)](../reference/apis/js-apis-sensor.md)
+- [@ohos.telephony.call (Call)](../reference/apis/js-apis-call.md)
+- [@ohos.telephony.data (Cellular Data)](../reference/apis/js-apis-telephony-data.md)
+- [@ohos.telephony.observer (observer)](../reference/apis/js-apis-observer.md)
+- [@ohos.telephony.radio (Network Search)](../reference/apis/js-apis-radio.md)
+- [@ohos.telephony.sim (SIM Management)](../reference/apis/js-apis-sim.md)
+- [@ohos.telephony.sms (SMS)](../reference/apis/js-apis-sms.md)
+- [@ohos.wallpaper (Wallpaper)](../reference/apis/js-apis-wallpaper.md)
+- [@ohos.wifiext (WLAN Extension)](../reference/apis/js-apis-wifiext.md)
+- [@ohos.wifiManager (WLAN)](../reference/apis/js-apis-wifiManager.md)
+- [@ohos.wifiManagerExt (WLAN Extension Interface)](../reference/apis/js-apis-wifiManagerExt.md)
+- [@system.geolocation (Geolocation)](../reference/apis/js-apis-system-location.md)
+- [nfctech (Standard NFC Technologies)](../reference/apis/js-apis-nfctech.md)
+- [tagSession (Standard NFC Tag Session)](../reference/apis/js-apis-tagSession.md)
+
+

en/application-dev/application-models/inter-device-interaction-hop-overview.md

@@ -3,7 +3,7 @@
 
 ## When to Use
 
-As the all-scenario, multi-device lifestyle becomes popular, users have an increasing number of devices. Each device provides users with what they need in a certain scenario. For example, watches allow users to view information in a timely manner, and smart TVs bring them an immersive watching experience. However, each device has its limitation, for example, typing text on a smart TV is frustrating as it is much more difficult than on a mobile device. If multiple devices can sense each other through a distributed OS and together form a super device, the strengths of each device can be fully exerted to provide a more natural and smoother distributed experience for users.
+As the all-scenario, multi-device lifestyle becomes popular, users have an increasing number of devices. Each device provides users with what they need in a certain scenario. For example, watches allow users to view information in a timely manner, and smart TVs bring them an immersive watching experience. However, each device has its limitations, for example, typing text on a smart TV is frustrating as it is much more difficult than on a mobile device. If multiple devices can sense each other through a distributed OS and together form a super device, the strengths of each device can be fully exerted to provide a more natural and smoother distributed experience for users.
 
 In OpenHarmony, distributed operations across devices are called continuation (previously named hopping), which is further classified into [cross-device migration](hop-cross-device-migration.md) and [multi-device collaboration](hop-multi-device-collaboration.md). To implement continuation, cross-device interaction capabilities of application components are required. Currently, these capabilities are open only to system applications.
 
@@ -20,7 +20,7 @@ In OpenHarmony, distributed operations across devices are called continuation (p
 
 - **Multi-device collaboration**
 
-  Multi-device collaboration enables collaboration between multiple devices, providing users with more efficient and immersive experience than with a single device. A typical multi-device collaboration scenario is as follows: Application A on the tablet is used as the answer board, and application B on the smart TV is used for live broadcast, delivering a better online class experience. From the perspective of application development, multi-device collaboration enables different UIAbility or ServiceExtensionAbility components to run simultaneously or alternately on multiple devices to provide a complete service, or enables the same UIAbility and ServiceExtensionAbility component to run simultaneously on multiple devices to provide a complete service.
+  Multi-device collaboration provides users with more efficient and immersive experience than with a single device. A typical multi-device collaboration scenario is as follows: Application A on the tablet is used as the answer board, and application B on the smart TV is used for live broadcast, delivering a better online class experience. From the perspective of application development, multi-device collaboration enables different UIAbility or ServiceExtensionAbility components to run simultaneously or alternately on multiple devices to provide a complete service, or enables the same UIAbility and ServiceExtensionAbility component to run simultaneously on multiple devices to provide a complete service.
 
 
 ## Continuation Architecture
@@ -35,9 +35,9 @@ OpenHarmony provides a set of APIs for you to implement continuation in your app
 
 The following figure shows the continuation architecture.
 
-  **Figure 1** Continuation architecture
+**Figure 1** Continuation architecture
 
-  ![hop-structure](figures/hop-structure.png) 
+ ![hop-structure](figures/hop-structure.png)  
 
 - Cross-device migration task management: The initiator accepts a migration request from the user, provides a migration entry, and displays the migration result. (This capability is unavailable yet.)
 
@@ -47,4 +47,4 @@ The following figure shows the continuation architecture.
 
 - Distributed security authentication: provides an E2E encrypted channel for cross-device transmission between applications to ensure that the right person uses the right data through the right device.
 
-- DSoftBus: functions as a unified communication base for a wide range of devices such as tablets, wearables, and smart TVs, and enables unified distributed communication between these devices.
+- DSoftBus: functions as a unified communication base for a wide range of devices, such as tablets, wearables, and smart TVs, and enables unified distributed communication between these devices.

en/application-dev/application-models/itc-with-emitter.md

@@ -13,12 +13,12 @@ To develop the Emitter mode, perform the following steps:
 
    // Define an event with eventId 1.
    let event = {
-       eventId: 1
+     eventId: 1
    };
 
    // Trigger the callback after the event with eventId 1 is received.
    let callback = (eventData) => {
-       console.info('event callback');
+     console.info('event callback');
    };
 
    // Subscribe to the event with eventId 1.
@@ -29,21 +29,21 @@ To develop the Emitter mode, perform the following steps:
 
    ```ts
    import emitter from "@ohos.events.emitter";
-
+   
    // Define an event with eventId 1 and priority Low.
    let event = {
-       eventId: 1,
-       priority: emitter.EventPriority.LOW
+     eventId: 1,
+     priority: emitter.EventPriority.LOW
    };
-
+   
    let eventData = {
-       data: {
-           "content": "c",
-           "id": 1,
-           "isEmpty": false,
-       }
+     data: {
+       "content": "c",
+       "id": 1,
+       "isEmpty": false,
+     }
    };
-
+   
    // Emit the event with eventId 1 and event content eventData.
    emitter.emit(event, eventData);
    ```

en/application-dev/application-models/itc-with-worker.md

@@ -9,13 +9,13 @@ To develop the Worker mode, perform the following steps:
 1. Configure the **buildOption** field in the [module-level build-profile.json5](https://developer.harmonyos.com/en/docs/documentation/doc-guides/ohos-building-configuration-0000001218440654#section6887184182020) file of the project.
 
    ```ts
-     "buildOption": {
-       "sourceOption": {
-         "workers": [
-           "./src/main/ets/workers/worker.ts"
-         ]
-       }
+   "buildOption": {
+     "sourceOption": {
+       "workers": [
+         "./src/main/ets/workers/worker.ts"
+       ]
      }
+   }
    ```
 
 2. Create the **worker.ts** file based on the configuration in **build-profile.json5**.
@@ -27,9 +27,9 @@ To develop the Worker mode, perform the following steps:
 
    // Process messages from the main thread.
    parent.onmessage = function(message) {
-       console.info("onmessage: " + message)
-       // Send a message to the main thread.
-       parent.postMessage("message from worker thread.")
+     console.info("onmessage: " + message)
+     // Send a message to the main thread.
+     parent.postMessage("message from worker thread.")
    }
    ```
 
@@ -46,10 +46,10 @@ To develop the Worker mode, perform the following steps:
 
       // Process messages from the worker thread.
       wk.onmessage = function(message) {
-          console.info("message from worker: " + message)
+        console.info("message from worker: " + message)
 
-          // Stop the worker thread based on service requirements.
-          wk.terminate()
+        // Stop the worker thread based on service requirements.
+        wk.terminate();
       }
       ```
 
@@ -57,23 +57,22 @@ To develop the Worker mode, perform the following steps:
 
       ```ts
       import worker from '@ohos.worker';
-
+      
       let wk = new worker.ThreadWorker("../workers/worker.ts");
-
+      
       // Send a message to the worker thread.
       wk.postMessage("message from main thread.")
-
+      
       // Process messages from the worker thread.
       wk.onmessage = function(message) {
-          console.info("message from worker: " + message)
-
-          // Stop the worker thread based on service requirements.
-          wk.terminate()
+        console.info("message from worker: " + message)
+      
+        // Stop the worker thread based on service requirements.
+        wk.terminate();
       }
       ```
 
 > **NOTE**
-> 
+>
 > - If the relative path of **worker.ts** configured in **build-profile.json5** is **./src/main/ets/workers/worker.ts**, pass in the path **entry/ets/workers/worker.ts** when creating a worker thread in the stage model, and pass in the path **../workers/worker.ts** when creating a worker thread in the FA model.
-> 
 > - For details about the data types supported between the main thread and worker thread, see [Sequenceable Data Types](../reference/apis/js-apis-worker.md#sequenceable-data-types).

en/application-dev/application-models/js-ui-widget-development.md

@@ -16,13 +16,13 @@ The widget host consists of the following modules:
 
 - Widget usage: provides operations such as creating, deleting, or updating a widget.
 
-- Communication adapter: provided by the OpenHarmony SDK for communication with the Widget Manager. It sends widget-related operations to the Widget Manager.
+- Communication adapter: provided by the SDK for communication with the Widget Manager. It sends widget-related operations to the Widget Manager.
 
 The Widget Manager consists of the following modules:
 
 - Periodic updater: starts a scheduled task based on the update policy to periodically update a widget after it is added to the Widget Manager.
 
-- Cache manager: caches view information of a widget after it is added to the Widget Manager to directly return the cached data when the widget is obtained next time. This reduces the latency greatly.
+- Cache manager: caches view information of a widget after it is added to the Widget Manager. This enables the cached data to be directly returned when the widget is obtained next time, greatly reducing the latency.
 
 - Lifecycle manager: suspends update when a widget is switched to the background or is blocked, and updates and/or clears widget data during upgrade and deletion.
 
@@ -36,9 +36,10 @@ The widget provider consists of the following modules:
 
 - Instance manager: implemented by the widget provider developer for persistent management of widget instances allocated by the Widget Manager.
 
-- Communication adapter: provided by the OpenHarmony SDK for communication with the Widget Manager. It pushes update data to the Widget Manager.
+- Communication adapter: provided by the SDK for communication with the Widget Manager. It pushes update data to the Widget Manager.
 
 > **NOTE**
+>
 > You only need to develop the widget provider. The system automatically handles the work of the widget host and Widget Manager.
 
 
@@ -48,14 +49,14 @@ The **FormExtensionAbility** class has the following APIs. For details, see [For
 
 | Name| Description|
 | -------- | -------- |
-| onAddForm(want: Want): formBindingData.FormBindingData | Called to notify the widget provider that a widget has been created.|
-| onCastToNormalForm(formId: string): void | Called to notify the widget provider that a temporary widget has been converted to a normal one.|
-| onUpdateForm(formId: string): void | Called to notify the widget provider that a widget has been updated.|
-| onChangeFormVisibility(newStatus: { [key: string]: number }): void | Called to notify the widget provider of the change in widget visibility.|
-| onFormEvent(formId: string, message: string): void | Called to instruct the widget provider to receive and process a widget event.|
-| onRemoveForm(formId: string): void | Called to notify the widget provider that a widget has been destroyed.|
-| onConfigurationUpdate(config: Configuration): void | Called when the configuration of the environment where the widget is running is updated.|
-| onShareForm?(formId: string): { [key: string]: any } | Called by the widget provider to receive shared widget data.|
+| onAddForm(want: Want): formBindingData.FormBindingData | Called to notify the widget provider that a widget is being created.|
+| onCastToNormalForm(formId: string): void | Called to notify the widget provider that a temporary widget is being converted to a normal one.|
+| onUpdateForm(formId: string): void | Called to notify the widget provider that a widget is being updated.|
+| onChangeFormVisibility(newStatus: { [key: string]: number }): void | Called to notify the widget provider that the widget visibility status is being changed.|
+| onFormEvent(formId: string, message: string): void | Called to instruct the widget provider to process a widget event.|
+| onRemoveForm(formId: string): void | Called to notify the widget provider that a widget is being destroyed.|
+| onConfigurationUpdate(config: Configuration): void | Called when the configuration of the environment where the widget is running is being updated.|
+| onShareForm?(formId: string): { [key: string]: any } | Called to notify the widget provider that the widget host is sharing the widget data.|
 
 The **FormProvider** class has the following APIs. For details, see [FormProvider](../reference/apis/js-apis-app-form-formProvider.md).
 
@@ -79,11 +80,11 @@ The widget provider development based on the [stage model](stage-model-developme
 
 - [Creating a FormExtensionAbility Instance](#creating-a-formextensionability-instance): Develop the lifecycle callback functions of FormExtensionAbility.
 
-- [Configuring the Widget Configuration Files](#configuring-the-widget-configuration-files): Configure the application configuration file **module.json5** and profile configuration file.
+- [Configuring the Widget Configuration File](#configuring-the-widget-configuration-file): Configure the application configuration file **module.json5** and profile configuration file.
 
-- [Persistently Storing Widget Data](#persistently-storing-widget-data): This operation is a form of widget data exchange.
+- [Persistently Storing Widget Data](#persistently-storing-widget-data): Manage widget data persistence.
 
-- [Updating Widget Data](#updating-widget-data): Call **updateForm()** to update the information displayed on a widget.
+- [Updating Widget Data](#updating-widget-data): Call **updateForm()** to update the information displayed in a widget.
 
 - [Developing the Widget UI Page](#developing-the-widget-ui-page): Use HML+CSS+JSON to develop a JS widget UI page.
 
@@ -92,7 +93,7 @@ The widget provider development based on the [stage model](stage-model-developme
 
 ### Creating a FormExtensionAbility Instance
 
-To create a widget in the stage model, implement the lifecycle callbacks of **FormExtensionAbility**. Generate a widget template by referring to [Developing a Service Widget](https://developer.harmonyos.com/en/docs/documentation/doc-guides/ohos-development-service-widget-0000001263280425).
+To create a widget in the stage model, you need to implement the lifecycle callbacks of FormExtensionAbility. Generate a widget template and then perform the following:
 
 1. Import related modules to **EntryFormAbility.ts**.
 
@@ -102,7 +103,7 @@ To create a widget in the stage model, implement the lifecycle callbacks of **Fo
    import formBindingData from '@ohos.app.form.formBindingData';
    import formInfo from '@ohos.app.form.formInfo';
    import formProvider from '@ohos.app.form.formProvider';
-   import dataStorage from '@ohos.data.storage';
+   import dataPreferences from '@ohos.data.preferences';
    ```
 
 2. Implement the FormExtension lifecycle callbacks in **EntryFormAbility.ts**.
@@ -121,7 +122,7 @@ To create a widget in the stage model, implement the lifecycle callbacks of **Fo
            return formData;
        }
        onCastToNormalForm(formId) {
-           // Called when the widget host converts the temporary widget into a normal one. The widget provider should do something to respond to the conversion.
+           // Called when a temporary widget is being converted into a normal one. The widget provider should respond to the conversion.
            console.info('[EntryFormAbility] onCastToNormalForm');
        }
        onUpdateForm(formId) {
@@ -158,6 +159,7 @@ To create a widget in the stage model, implement the lifecycle callbacks of **Fo
    ```
 
 > **NOTE**
+>
 > FormExtensionAbility cannot reside in the background. Therefore, continuous tasks cannot be processed in the widget lifecycle callbacks.
 
 
@@ -190,7 +192,7 @@ To create a widget in the stage model, implement the lifecycle callbacks of **Fo
    }
    ```
 
-2. Configure the widget configuration information. In the **metadata** configuration item of FormExtensionAbility, you can specify the resource index of specific configuration information of the widget. For example, if resource is set to **$profile:form_config**, **form_config.json** in the **resources/base/profile/** directory of the development view is used as the profile configuration file of the widget. The following table describes the internal field structure.
+2. Configure the widget configuration information. In the **metadata** configuration item of FormExtensionAbility, you can specify the resource index of specific configuration information of the widget. For example, if **resource** is set to **$profile:form_config**, **form_config.json** in the **resources/base/profile/** directory of the development view is used as the profile configuration file of the widget. The following table describes the internal structure of the profile configuration file.
 
    **Table 1** Widget profile configuration file
 
@@ -204,7 +206,7 @@ To create a widget in the stage model, implement the lifecycle callbacks of **Fo
    | colorMode | Color mode of the widget.<br>- **auto**: auto-adaptive color mode<br>- **dark**: dark color mode<br>- **light**: light color mode| String| Yes (initial value: **auto**)|
    | supportDimensions | Grid styles supported by the widget.<br>- **1 * 2**: indicates a grid with one row and two columns.<br>- **2 * 2**: indicates a grid with two rows and two columns.<br>- **2 * 4**: indicates a grid with two rows and four columns.<br>- **4 * 4**: indicates a grid with four rows and four columns.| String array| No|
    | defaultDimension | Default grid style of the widget. The value must be available in the **supportDimensions** array of the widget.| String| No|
-   | updateEnabled | Whether the widget can be updated periodically.<br>- **true**: The widget can be updated at a specified interval (**updateDuration**) or at the scheduled time (**scheduledUpdateTime**). **updateDuration** takes precedence over **scheduledUpdateTime**.<br>- **false**: The widget cannot be updated periodically.| Boolean| No|
+   | updateEnabled | Whether the widget can be updated periodically.<br>- **true**: The widget can be updated at a specified interval (**updateDuration**) or at the scheduled time (**scheduledUpdateTime**). **updateDuration** takes precedence over **scheduledUpdateTime**. If both are specified, the value specified by **updateDuration** is used.<br>- **false**: The widget cannot be updated periodically.| Boolean| No|
    | scheduledUpdateTime | Scheduled time to update the widget. The value is in 24-hour format and accurate to minute.<br>**updateDuration** takes precedence over **scheduledUpdateTime**. If both are specified, the value specified by **updateDuration** is used.| String| Yes (initial value: **0:0**)|
    | updateDuration | Interval to update the widget. The value is a natural number, in the unit of 30 minutes.<br>If the value is **0**, this field does not take effect.<br>If the value is a positive integer *N*, the interval is calculated by multiplying *N* and 30 minutes.<br>**updateDuration** takes precedence over **scheduledUpdateTime**. If both are specified, the value specified by **updateDuration** is used.| Number| Yes (initial value: **0**)|
    | formConfigAbility | Link to a specific page of the application. The value is a URI.| String| Yes (initial value: left empty)|
@@ -255,7 +257,7 @@ async function storeFormInfo(formId: string, formName: string, tempFlag: boolean
         "updateCount": 0
     };
     try {
-        const storage = await dataStorage.getStorage(DATA_STORAGE_PATH);
+        const storage = await dataPreferences.getPreferences(this.context, DATA_STORAGE_PATH);
         // put form info
         await storage.put(formId, JSON.stringify(formInfo));
         console.info(`[EntryFormAbility] storeFormInfo, put form info successfully, formId: ${formId}`);
@@ -294,8 +296,8 @@ You should override **onRemoveForm** to implement widget data deletion.
 const DATA_STORAGE_PATH = "/data/storage/el2/base/haps/form_store";
 async function deleteFormInfo(formId: string) {
     try {
-        const storage = await dataStorage.getStorage(DATA_STORAGE_PATH);
-        // del form info
+        const storage = await dataPreferences.getPreferences(this.context, DATA_STORAGE_PATH);
+        // Delete the widget information.
         await storage.delete(formId);
         console.info(`[EntryFormAbility] deleteFormInfo, del form info successfully, formId: ${formId}`);
         await storage.flush();
@@ -317,7 +319,7 @@ export default class EntryFormAbility extends FormExtension {
 }
 ```
 
-For details about how to implement persistent data storage, see [Persisting Preferences Data](../database/data-persistence-by-preferences.md).
+For details about how to implement persistent data storage, see [Application Data Persistence](../database/app-data-persistence-overview.md).
 
 The **Want** object passed in by the widget host to the widget provider contains a flag that specifies whether the requested widget is normal or temporary.
 
@@ -449,14 +451,14 @@ The key steps are as follows:
 
    - **action**: **"router"**, which indicates a router event.
    - **abilityName**: name of the UIAbility to redirect to (PageAbility component in the FA model and UIAbility component in the stage model). For example, the default UIAbility name of the stage model created by DevEco Studio is EntryAbility.
-   - **params**: custom parameters passed to the target UIAbility. Set them as required. The value can be obtained from **parameters** in **want** used for starting the target UIAbility. For example, in the lifecycle function **onCreate** of the main ability in the stage model, you can obtain **want** and its **parameters** field.
+   - **params**: custom parameters passed to the target UIAbility. Set them as required. The value can be obtained from **parameters** in **want** used for starting the target UIAbility. For example, in the lifecycle function **onCreate** of the MainAbility in the stage model, you can obtain **want** and its **parameters** field.
 
 3. Set the message event.
 
    - **action**: **"message"**, which indicates a message event.
    - **params**: custom parameters of the message event. Set them as required. The value can be obtained from **message** in the widget lifecycle function **onFormEvent()**.
 
-The following is an example:
+The following are examples:
 
 - HML file:
 
@@ -545,7 +547,7 @@ The following is an example:
   }
   ```
 
-- Receive the router event and obtain parameters in UIAbility.
+- Receive the router event in UIAbility and obtain parameters.
 
 
   ```ts

en/application-dev/application-models/lifecycleapp-switch.md

 # 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).|
@@ -14,7 +14,7 @@
 | 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.|
+| 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 an 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.|
 | onInactive?(): void; | \@ohos.app.ability.UIAbility.d.ts | [onBackground(): void;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityonbackground) |
 | onActive?(): void; | \@ohos.app.ability.UIAbility.d.ts | [onForeground(): void;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityonforeground) |
 | onNewWant?(want: Want): void; | \@ohos.app.ability.UIAbility.d.ts | [onNewWant(want: Want, launchParams: AbilityConstant.LaunchParam): void;](../reference/apis/js-apis-app-ability-uiAbility.md#abilityonnewwant) |

en/application-dev/application-models/lifecycledata-switch.md

 # LifecycleData 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| 
 | -------- | -------- | -------- |
 | update?(uri: string, valueBucket: rdb.ValuesBucket, predicates: dataAbility.DataAbilityPredicates, callback: AsyncCallback<number>): void; | \@ohos.application.DataShareExtensionAbility.d.ts | [update?(uri: string, predicates: dataSharePredicates.DataSharePredicates, valueBucket: ValuesBucket, callback: AsyncCallback<number>): void;](../reference/apis/js-apis-application-dataShareExtensionAbility.md#update) |
 | query?(uri: string, columns: Array<string>, predicates: dataAbility.DataAbilityPredicates, callback: AsyncCallback<ResultSet>): void; | \@ohos.application.DataShareExtensionAbility.d.ts | [query?(uri: string, predicates: dataSharePredicates.DataSharePredicates, columns: Array<string>, callback: AsyncCallback<Object>): void;](../reference/apis/js-apis-application-dataShareExtensionAbility.md#query) |

en/application-dev/application-models/lifecycleform-switch.md

 # LifecycleForm 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| 
 | -------- | -------- | -------- |
 | onCreate?(want: Want): formBindingData.FormBindingData; | \@ohos.app.form.FormExtensionAbility.d.ts | [onAddForm(want: Want): formBindingData.FormBindingData;](../reference/apis/js-apis-app-form-formExtensionAbility.md#onaddform) |
 | onCastToNormal?(formId: string): void; | \@ohos.app.form.FormExtensionAbility.d.ts | [onCastToNormalForm(formId: string): void;](../reference/apis/js-apis-app-form-formExtensionAbility.md#oncasttonormalform) |

en/application-dev/application-models/lifecycleservice-switch.md

 # LifecycleService 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| 
 | -------- | -------- | -------- |
 | onStart?(): void; | \@ohos.app.ability.ServiceExtensionAbility.d.ts | [onCreate(want: Want): void;](../reference/apis/js-apis-app-ability-serviceExtensionAbility.md#serviceextensionabilityoncreate) |
 | onCommand?(want: Want, startId: number): void; | \@ohos.app.ability.ServiceExtensionAbility.d.ts | [onRequest(want: Want, startId: number): void;](../reference/apis/js-apis-app-ability-serviceExtensionAbility.md#serviceextensionabilityonrequest) |  |

en/application-dev/application-models/medialibrary-switch.md

 # mediaLibrary 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| 
 | -------- | -------- | -------- |
 | [getMediaLibrary(): MediaLibrary;](../reference/apis/js-apis-medialibrary.md#medialibrarygetmedialibrary) | \@ohos.multimedia.mediaLibrary.d.ts | [getMediaLibrary(context: Context): MediaLibrary;](../reference/apis/js-apis-medialibrary.md#medialibrarygetmedialibrary8) |

en/application-dev/application-models/mission-management-launch-type.md

-# Mission Management and Launch Type
+# Mission and Launch Type
 
 
 One UIAbility instance corresponds to one mission. The number of UIAbility instances is related to the UIAbility launch type, specified by **launchType**, which is configured in the **config.json** file in the FA model and the [module.json5](../quick-start/module-configuration-file.md) file in the stage model.
@@ -11,13 +11,13 @@ The following describes how the mission list manager manages the UIAbility insta
   
   ![mission-and-singleton](figures/mission-and-singleton.png)
   
-- **multiton**: Each time [startAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartability) is called, a **UIAbility** instance is created in the application process.
+- **multiton**: Each time [startAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartability) is called, a UIAbility instance is created in the application process.
   
   **Figure 2** Missions and multiton mode
   
   ![mission-and-multiton](figures/mission-and-multiton.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 a UIAbility instance.
   
   **Figure 3** Missions and specified mode
   

en/application-dev/application-models/mission-management-overview.md

@@ -4,7 +4,7 @@
 Before getting started with the development of mission management, be familiar with the following concepts related to mission management:
 
 
-- AbilityRecord: minimum unit for the system service to manage a UIAbility instance. It corresponds to a UIAbility component instance of an application.
+- AbilityRecord: minimum unit for the system service to manage a UIAbility instance. It corresponds to a UIAbility component instance of an application. A maximum of 512 UIAbility instances can be managed on the system service side.
 
 - MissionRecord: minimum unit for mission management. One MissionRecord has only one AbilityRecord. In other words, a UIAbility component instance corresponds to a mission.
 
@@ -30,42 +30,42 @@ Missions are managed by system applications (such as home screen), rather than t
 
 A UIAbility instance corresponds to an independent mission. Therefore, when an application calls [startAbility()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextstartability) to start a UIAbility, a mission is created.
 
-To call [missionManager](../reference/apis/js-apis-application-missionManager.md) to manage missions, the home screen application must request the **ohos.permission.MANAGE_MISSIONS** permission. For details about the configuration, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file).
+1. To call [missionManager](../reference/apis/js-apis-application-missionManager.md) to manage missions, the home screen application must request the **ohos.permission.MANAGE_MISSIONS** permission. For details about the configuration, see [Declaring Permissions in the Configuration File](../security/accesstoken-guidelines.md#declaring-permissions-in-the-configuration-file).
 
-You can use **missionManager** to manage missions, for example, listening for mission changes, obtaining mission information or snapshots, and clearing, locking, or unlocking missions.
+2. You can use **missionManager** to manage missions, for example, listening for mission changes, obtaining mission information or snapshots, and clearing, locking, or unlocking missions.
 
    ```ts
    import missionManager from '@ohos.app.ability.missionManager'
    
    let listener = {
-       // Listen for mission creation.
-       onMissionCreated: function (mission) {
-           console.info("--------onMissionCreated-------")
-       },
-       // Listen for mission destruction.
-       onMissionDestroyed: function (mission) {
-           console.info("--------onMissionDestroyed-------")
-       },
-       // Listen for mission snapshot changes.
-       onMissionSnapshotChanged: function (mission) {
-           console.info("--------onMissionSnapshotChanged-------")
-       },
-       // Listen for switching the mission to the foreground.
-       onMissionMovedToFront: function (mission) {
-           console.info("--------onMissionMovedToFront-------")
-       },
-       // Listen for mission icon changes.
-       onMissionIconUpdated: function (mission, icon) {
-           console.info("--------onMissionIconUpdated-------")
-       },
-       // Listen for mission name changes.
-       onMissionLabelUpdated: function (mission) {
-           console.info("--------onMissionLabelUpdated-------")
-       },
-       // Listen for mission closure events.
-       onMissionClosed: function (mission) {
-           console.info("--------onMissionClosed-------")
-       }
+     // Listen for mission creation.
+     onMissionCreated: function (mission) {
+       console.info("--------onMissionCreated-------")
+     },
+     // Listen for mission destruction.
+     onMissionDestroyed: function (mission) {
+       console.info("--------onMissionDestroyed-------")
+     },
+     // Listen for mission snapshot changes.
+     onMissionSnapshotChanged: function (mission) {
+       console.info("--------onMissionSnapshotChanged-------")
+     },
+     // Listen for switching the mission to the foreground.
+     onMissionMovedToFront: function (mission) {
+       console.info("--------onMissionMovedToFront-------")
+     },
+     // Listen for mission icon changes.
+     onMissionIconUpdated: function (mission, icon) {
+       console.info("--------onMissionIconUpdated-------")
+     },
+     // Listen for mission name changes.
+     onMissionLabelUpdated: function (mission) {
+       console.info("--------onMissionLabelUpdated-------")
+     },
+     // Listen for mission closure events.
+     onMissionClosed: function (mission) {
+       console.info("--------onMissionClosed-------")
+     }
    };
    
    // 1. Register a mission change listener.
@@ -73,56 +73,56 @@ You can use **missionManager** to manage missions, for example, listening for mi
    
    // 2. Obtain the latest 20 missions in the system.
    missionManager.getMissionInfos("", 20, (error, missions) => {
-       console.info("getMissionInfos is called, error.code = " + error.code);
-       console.info("size = " + missions.length);
-       console.info("missions = " + JSON.stringify(missions));
+     console.info("getMissionInfos is called, error.code = " + error.code);
+     console.info("size = " + missions.length);
+     console.info("missions = " + JSON.stringify(missions));
    });
    
    // 3. Obtain the detailed information about a mission.
    let missionId = 11; // The mission ID 11 is only an example.
    let mission = missionManager.getMissionInfo("", missionId).catch(function (err) {
-       console.info(err);
+     console.info(err);
    });
    
    // 4. Obtain the mission snapshot.
    missionManager.getMissionSnapShot("", missionId, (error, snapshot) => {
-       console.info("getMissionSnapShot is called, error.code = " + error.code);
-       console.info("bundleName = " + snapshot.ability.bundleName);
+     console.info("getMissionSnapShot is called, error.code = " + error.code);
+     console.info("bundleName = " + snapshot.ability.bundleName);
    })
    
    // 5. Obtain the low-resolution mission snapshot.
    missionManager.getLowResolutionMissionSnapShot("", missionId, (error, snapshot) => {
-       console.info("getLowResolutionMissionSnapShot is called, error.code = " + error.code);
-       console.info("bundleName = " + snapshot.ability.bundleName);
+     console.info("getLowResolutionMissionSnapShot is called, error.code = " + error.code);
+     console.info("bundleName = " + snapshot.ability.bundleName);
    })
    
    // 6. Lock or unlock the mission.
    missionManager.lockMission(missionId).then(() => {
-       console.info("lockMission is called ");
+     console.info("lockMission is called ");
    });
    
    missionManager.unlockMission(missionId).then(() => {
-       console.info("unlockMission is called ");
+     console.info("unlockMission is called ");
    });
    
    // 7. Switch the mission to the foreground.
    missionManager.moveMissionToFront(missionId).then(() => {
-       console.info("moveMissionToFront is called ");
+     console.info("moveMissionToFront is called ");
    });
    
    // 8. Clear a single mission.
    missionManager.clearMission(missionId).then(() => {
-       console.info("clearMission is called ");
+     console.info("clearMission is called ");
    });
    
    // 9. Clear all missions.
    missionManager.clearAllMissions().catch(function (err) {
-       console.info(err);
+     console.info(err);
    });
    
    // 10. Deregister the mission change listener.
    missionManager.off('mission', listenerId, (error) => {
-       console.info("unregisterMissionListener");
+     console.info("unregisterMissionListener");
    })
    ```
 

en/application-dev/application-models/mission-set-icon-name-for-task-snapshot.md

@@ -17,19 +17,22 @@ This document describes the following operations:
 
 ## Setting a Mission Snapshot Icon (for System Applications Only)
 
-Call [UIAbilityContext.setMissionIcon()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextsetmissionicon) to set the icon of a mission snapshot. The icon is an object of the [PixelMap](../reference/apis/js-apis-image.md#pixelmap7) type. For details about how to obtain the context, see [Obtaining the Context of UIAbility](uiability-usage.md#obtaining-the-context-of-uiability).
+Call [UIAbilityContext.setMissionIcon()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextsetmissionicon) to set the icon of a mission snapshot. For details about how to obtain the context, see [Obtaining the Context of UIAbility](uiability-usage.md#obtaining-the-context-of-uiability). For details about how to obtain the PixelMap information in the example, see [Image Decoding](../media/image-decoding.md).
+
 ```ts
-let imagePixelMap: PixelMap = undefined; // Obtain the PixelMap information.
+let context = ...; // UIAbilityContext
+let pixelMap: PixelMap =...; // PixelMap information of the image.
 
-this.context.setMissionIcon(imagePixelMap, (err) => {
-  console.error(`setMissionLabel failed, code is ${err.code}, message is ${err.message}`);
+context.setMissionIcon(pixelMap, (err) => {
+  if (err.code) {
+    console.error(`Failed to set mission icon. Code is ${err.code}, message is ${err.message}`);
+  }
 })
 ```
 
 The display effect is shown below.
 
 Figure 2 Mission snapshot icon
-
 ![](figures/mission-set-task-snapshot-icon.png)
 
 ## Setting a Mission Snapshot Name
@@ -37,15 +40,16 @@ Figure 2 Mission snapshot icon
 Call [UIAbilityContext.setMissionLabel()](../reference/apis/js-apis-inner-application-uiAbilityContext.md#uiabilitycontextsetmissionlabel) to set the name of a mission snapshot.
 
 ```ts
-this.context.setMissionLabel('test').then(() => {
-  console.info('setMissionLabel succeeded.');
+let context = ...; // UIAbilityContext
+
+context.setMissionLabel('test').then(() => {
+  console.info('Succeeded in seting mission label.');
 }).catch((err) => {
-  console.error(`setMissionLabel failed, code is ${err.code}, message is ${err.message}`);
+  console.error(`Failed to set mission label. Code is ${err.code}, message is ${err.message}`);
 });
 ```
 
 The display effect is shown below.
 
 Figure 3 Mission snapshot name
-
 ![](figures/mission-set-task-snapshot-label.png)

en/application-dev/application-models/model-switch-overview.md

@@ -5,19 +5,23 @@ Perform the following operations to switch a declarative paradigm-based applicat
 
 
 - Project switch: Create an application project of the stage model.
+
   ![model-switch-overview1](figures/model-switch-overview1.png)
 
 - [Configuration file switch](configuration-file-diff.md): Switch **config.json** to **app.json5** and **module.json5**.
+
   ![model-switch-overview2](figures/model-switch-overview2.png)
 
 - [Component switch](pageability-switch.md): Switch the PageAbility, ServiceAbility, and DataAbility components of the FA model to the UIAbility and ExtensionAbility components of the stage model. The figure below shows only the switching from PageAbility to UIAbility. The left part is the FA model, and **app.ets** is the PageAbility component. The right part is the stage model, and **EntryAbility.ts** is the UIAbility component.
 
-![model-switch-overview3](figures/model-switch-overview3.png)
+  ![model-switch-overview3](figures/model-switch-overview3.png)
 
 - [Widget switch](widget-switch.md): Switch the FormAbility component of the FA model to the FormExtensionAbility component of the stage model. In the figure below, **Service Widget** is FormAbility in the FA model and FormExtensionAbility in the stage model.
+
   ![model-switch-overview4](figures/model-switch-overview4.png)
 
   ![model-switch-overview5](figures/model-switch-overview5.png)
 
 - [API switch](api-switch-overview.md): Switch the APIs with the **FAModelOnly** tag used in the FA model to the recommended APIs in the stage model.
+
   ![model-switch-overview6](figures/model-switch-overview6.png)

en/application-dev/application-models/module-switch.md

 # Switching of module
 
 
-When switching an application from the FA model to the stage model, you must migrate the configurations under the **module** tag in the **config.json** file to the **module** tag in the **module.json5** file.
+When switching an application from the FA model to the stage model, migrate the configurations under **module** in the **config.json** file to **module** in the **module.json5** file.
 
-###   Table 1 module Comparison
+**Table 1** module comparison
 
 | Field Name in the FA Model| Field Description| Field Name in the Stage Model| Difference|
 | -------- | -------- | -------- | -------- |
@@ -15,8 +15,8 @@ When switching an application from the FA model to the stage model, you must mig
 | moduleType in the distro object| Type of the HAP file. The value can be **entry** or **feature**. For the HAR type, set this field to **har**.| type | The field name is changed.|
 | installationFree in the distro object| Whether the HAP file supports the installation-free feature.| installationFree | The field name is changed.|
 | deliveryWithInstall in the distro object| Whether the HAP file is installed with the application.| deliveryWithInstall | The field name is changed.|
-| metaData | Metadata of the HAP file.| metadata | See [Table 2](#table-2-metadata-comparison).|
-| abilities | All abilities in the current module.| abilities | See [Table 5](#table-5-abilities-comparison).|
+| metaData | Metadata of the HAP file.| metadata | For details, see Table 2.|
+| abilities | All abilities in the current module.| abilities | For details, see Table 5.|
 | js | A set of JS modules developed using ArkUI. Each element in the set represents the information about a JS module.| pages | The stage model retains **pages** under the **module** tag. The window configuration is the lower level of **pages**.|
 | 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.|
@@ -27,40 +27,40 @@ When switching an application from the FA model to the stage model, you must mig
 | entryTheme | Keyword of an OpenHarmony internal theme.| / | This configuration is not supported in the stage model.|
 
 
-### Table 2 metaData Comparison
+**Table 2** metaData comparison
 
-| Field Name Under metaData in the FA Model| Field Description| Field Name Under metaData in the Stage Model| Difference|
+| Field Name in the FA Model| Field Description| Field Name in the Stage Model| Difference|
 | -------- | -------- | -------- | -------- |
 | parameters | Metadata of the parameters to be passed for calling the ability.| / | This configuration is not supported in the stage model.|
 | results | Metadata of the ability return value.| / | This configuration is not supported in the stage model.|
-| customizeData | Custom metadata of the parent component. **parameters** and **results** cannot be configured in **application**.| metadata | See [Table 3](#table-3-comparison-between-customizedata-under-metadata-in-the-fa-model-and-metadata-in-the-stage-model).|
+| customizeData | Custom metadata of the parent component. **parameters** and **results** cannot be configured in **application**.| metadata | **For details**, see Table 3.|
 
-### Table 3 Comparison Between customizeData Under metaData in the FA Model and metadata in the Stage Model
+**Table 3** Comparison between customizeData under metaData in the FA model and metadata in the stage Model
 
-| Field Name Under customizeData in metaData in the FA Model| Field Description| Field Name Under metaData in the Stage Model| Difference|
+| Field Name in the FA Model| Field Description| Field Name in the Stage Model| Difference|
 | -------- | -------- | -------- | -------- |
 | 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
 
 | Example in the FA Model| Example in the Stage Model|
 | -------- | -------- |
 | "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>}] |
 
 
-### Table 5 abilities Comparison
+**Table 5** abilities comparison
 
 | Field Name Under abilities in the FA Model| Field Description| Field Name Under abilities in the Stage Model| Difference|
 | -------- | -------- | -------- | -------- |
 | process | Name of the process running the application or ability.| / | The stage model does not support configuration of **process** under **abilities**. The configuration of **process** is available under the **module** tag.|
 | uri | URI of the ability.| / | This configuration is not supported in the stage model.|
 | deviceCapability | Device capabilities required to run the ability.| / | This configuration is not supported in the stage model.|
-| metaData | Metadata of the ability.| metadata | See [Table 2](#table-2-metadata-comparison).|
+| metaData | Metadata of the ability.| metadata | For details, see Table 2.|
 | type | Ability type.| / | This configuration is not supported in the stage model.|
-| grantPermission | Whether permissions can be granted for any data in the ability.| / | The stage model does not support such a configuration under **abilities**.|
+| grantPermission | Whether permissions can be granted to any data in the ability.| / | The stage model does not support such a configuration under **abilities**.|
 | readPermission | Permission required for reading data in the ability. This field applies only to the ability using the Data template.| / | In the stage model, this configuration is available under **extensionAbilities**, but not **abilities**.|
 | writePermission | Permission required for writing data to the ability.| / | In the stage model, this configuration is available under **extensionAbilities**, but not **abilities**.|
 | configChanges | System configurations that the ability concerns.| / | This configuration is not supported in the stage model.|

en/application-dev/application-models/page-mission-stack.md

@@ -5,7 +5,8 @@
 
 A single UIAbility component can implement multiple pages and redirection between these pages. The redirection relationship inside the UIAbility component is called page stack, which is managed by the ArkUI framework. For example, Page1 -> Page2 -> Page3 of UIAbility1 and PageA -> PageB -> PageC of UIAbility2 in the figure below are two page stacks.
 
-  **Figure 1** Page stack 
+**Figure 1** Page stack
+
 ![mission-record](figures/mission-record.png)
 
 - A page stack is formed as follows (Steps 2, 3, 5, and 6 are page redirection and managed by ArkUI):

en/application-dev/application-models/pageability-launch-type.md

@@ -5,7 +5,7 @@ Depending on the launch type, the action performed when the PageAbility starts d
 
 **Table 1** PageAbility launch types
 
-| Launch Type| Meaning        | Description|
+| 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**.|
@@ -16,13 +16,13 @@ You can set **launchType** in the **config.json** file to configure the launch t
 ```json
 {
   "module": {
-    // ...
+    ...
     "abilities": [
       {
         // singleton means the singleton mode.
         // standard means the multiton mode.
         "launchType": "standard",
-        // ...
+        ...
       }
     ]
   }

en/application-dev/application-models/pageability-switch.md

@@ -27,7 +27,7 @@ The PageAbility lifecycle is basically the same as the UIAbility lifecycle. The
 3. Adjust the migrated code, since the methods of loading pages are different.
 
    - In the FA model, you can configure the page to be loaded by setting page information in **config.json**.
-   - In the stage model, you must call **windowStage.loadContent** in the **onWindowStageCreate** callback to load a page.
+   - In the stage model, call **windowStage.loadContent** in the **onWindowStageCreate** callback to load a page.
 
    For example, to load the **pages/Index** page after the ability is started, use the following code in the **config.json** file in the FA model:
 

en/application-dev/application-models/particleability-switch.md

 # particleAbility 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| 
 | -------- | -------- | -------- |
 | [startAbility(parameter: StartAbilityParameter, callback: AsyncCallback&lt;number&gt;): void;](../reference/apis/js-apis-ability-particleAbility.md#particleabilitystartability)<br>[startAbility(parameter: StartAbilityParameter): Promise&lt;number&gt;;](../reference/apis/js-apis-ability-particleAbility.md#particleabilitystartability-1) | application\ServiceExtensionContext.d.ts | [startAbility(want: Want, callback: AsyncCallback&lt;void&gt;): void;](../reference/apis/js-apis-inner-application-serviceExtensionContext.md#serviceextensioncontextstartability)<br>[startAbility(want: Want, options: StartOptions, callback: AsyncCallback&lt;void&gt;): void;](../reference/apis/js-apis-inner-application-serviceExtensionContext.md#serviceextensioncontextstartability-2)<br>[startAbility(want: Want, options?: StartOptions): Promise&lt;void&gt;;](../reference/apis/js-apis-inner-application-serviceExtensionContext.md#serviceextensioncontextstartability-1)<br>[startServiceExtensionAbility(want: Want, callback: AsyncCallback&lt;void&gt;): void;](../reference/apis/js-apis-inner-application-serviceExtensionContext.md#serviceextensioncontextstartserviceextensionability)<br>[startServiceExtensionAbility(want: Want): Promise&lt;void&gt;;](../reference/apis/js-apis-inner-application-serviceExtensionContext.md#serviceextensioncontextstartserviceextensionability-1) |
 | [terminateSelf(callback: AsyncCallback&lt;void&gt;): void;](../reference/apis/js-apis-ability-particleAbility.md#particleabilityterminateself)<br>[terminateSelf(): Promise&lt;void&gt;;](../reference/apis/js-apis-ability-particleAbility.md#particleabilityterminateself-1) | application\ServiceExtensionContext.d.ts | [terminateSelf(callback: AsyncCallback&lt;void&gt;): void;](../reference/apis/js-apis-inner-application-serviceExtensionContext.md#serviceextensioncontextterminateself)<br>[terminateSelf(): Promise&lt;void&gt;;](../reference/apis/js-apis-inner-application-serviceExtensionContext.md#serviceextensioncontextterminateself-1) |
@@ -10,3 +10,5 @@
 | [acquireDataAbilityHelper(uri: string): DataAbilityHelper;](../reference/apis/js-apis-ability-particleAbility.md#particleabilityacquiredataabilityhelper) | \@ohos.data.dataShare.d.ts<br>[\@ohos.data.fileAccess.d.ts | [createDataShareHelper(context: Context, uri: string, callback: AsyncCallback&lt;DataShareHelper&gt;): void;](../reference/apis/js-apis-data-dataShare.md#datasharecreatedatasharehelper)<br>[createDataShareHelper(context: Context, uri: string): Promise&lt;DataShareHelper&gt;;](../reference/apis/js-apis-data-dataShare.md#datasharecreatedatasharehelper-1)<br>[createFileAccessHelper(context: Context): FileAccessHelper;](../reference/apis/js-apis-fileAccess.md#fileaccesscreatefileaccesshelper-1)<br>[createFileAccessHelper(context: Context, wants: Array&lt;Want&gt;): FileAccessHelper;](../reference/apis/js-apis-fileAccess.md#fileaccesscreatefileaccesshelper) |
 | [startBackgroundRunning(id: number, request: NotificationRequest, callback: AsyncCallback&lt;void&gt;): void;](../reference/apis/js-apis-ability-particleAbility.md#particleabilitystartbackgroundrunning)<br>[startBackgroundRunning(id: number, request: NotificationRequest): Promise&lt;void&gt;;](../reference/apis/js-apis-ability-particleAbility.md#particleabilitystartbackgroundrunning-1) | \@ohos.resourceschedule.backgroundTaskManager.d.ts | [startBackgroundRunning(context: Context, bgMode: BackgroundMode, wantAgent: WantAgent, callback: AsyncCallback): void;](../reference/apis/js-apis-resourceschedule-backgroundTaskManager.md#backgroundtaskmanagerstartbackgroundrunningcallback)<br>[startBackgroundRunning(context: Context, bgMode: BackgroundMode, wantAgent: WantAgent): Promise&lt;void&gt;;](../reference/apis/js-apis-resourceschedule-backgroundTaskManager.md#backgroundtaskmanagerstartbackgroundrunningpromise) |
 | [cancelBackgroundRunning(callback: AsyncCallback&lt;void&gt;): void;](../reference/apis/js-apis-ability-particleAbility.md#particleabilitycancelbackgroundrunning)<br>[cancelBackgroundRunning(): Promise&lt;void&gt;;](../reference/apis/js-apis-ability-particleAbility.md#particleabilitycancelbackgroundrunning-1) | \@ohos.resourceschedule.backgroundTaskManager.d.ts | [stopBackgroundRunning(context: Context, callback: AsyncCallback): void;](../reference/apis/js-apis-resourceschedule-backgroundTaskManager.md#backgroundtaskmanagerstopbackgroundrunningcallback)<br>[stopBackgroundRunning(context: Context): Promise&lt;void&gt;;](../reference/apis/js-apis-resourceschedule-backgroundTaskManager.md#backgroundtaskmanagerstopbackgroundrunningpromise) |
+
+ <!--no_check--> 
\ No newline at end of file

en/application-dev/application-models/process-model-fa.md

-# Process Model (FA Model)
+# Process Model Overview (FA Model)
 
 
 The OpenHarmony process model is shown below.
@@ -8,9 +8,9 @@ The OpenHarmony process model is shown below.
 
 - WebView has an independent rendering process, which is **Render process** in yellow in the figure.
 
-  **Figure 1** Process model 
+**Figure 1** Process model
 
-  ![process-model-fa](figures/process-model-fa.png)
+![process-model-fa](figures/process-model-fa.png)
 
 
 OpenHarmony provides two inter-process communication (IPC) mechanisms.
@@ -19,4 +19,3 @@ OpenHarmony provides two inter-process communication (IPC) mechanisms.
 - [Common Events](common-event-fa.md): This mechanism is used in one-to-many communication scenarios. Multiple subscribers may receive events at the same time.
 
 - [Background Services](rpc.md): This mechanism is implemented through [ServiceAbility](serviceability-overview.md).
-

en/application-dev/application-models/process-model-stage.md

-# Process Model (Stage Model)
+# Process Model Overview (Stage Model)
 
 
 The OpenHarmony process model is shown below.
 
 
 - All UIAbility, ServiceExtensionAbility, and DataShareExtensionAbility components of an application (with the same bundle name) run in an independent process, which is **Main process** in green in the figure.
-
-- The ExtensionAbility components of the same type (except ServiceExtensionAbility and DataShareExtensionAbility) of an application (with the same bundle name) run in an independent process, which is **FormExtensionAbility process**, **InputMethodExtensionAbility process**, and other **ExtensionAbility process** in blue in the figure.
-
+- All ExtensionAbility components of the same type (except ServiceExtensionAbility and DataShareExtensionAbility) of an application (with the same bundle name) run in an independent process, which is **FormExtensionAbility process**, **InputMethodExtensionAbility process**, and other **ExtensionAbility process** in blue in the figure.
 - WebView has an independent rendering process, which is **Render process** in yellow in the figure.
 
-  **Figure 1** Process model 
+**Figure 1** Process model
+
 ![process-model](figures/process-model.png)
 
 > NOTE
@@ -20,7 +19,8 @@ The OpenHarmony process model is shown below.
 
 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.
 
-**Figure 2** Multi-process 
+**Figure 2** Multi-process
+
 ![multi-process](figures/multi-process.png)
 
 

en/application-dev/application-models/redirection-rules.md

@@ -21,11 +21,11 @@ To enable an ability to be called by any application, configure the **config.jso
 ```ts
 {
   "module": {
-    // ...
+    ...
     "abilities": [
       {
         "visible": "true",
-        // ...
+        ...
       }
     ]
   }

en/application-dev/application-models/request-switch.md

 # request 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| 
 | -------- | -------- | -------- |
 | [download(config: DownloadConfig, callback: AsyncCallback&lt;DownloadTask&gt;): void;](../reference/apis//js-apis-request.md#requestdownload-1)<br>[download(config: DownloadConfig): Promise&lt;DownloadTask&gt;;](../reference/apis/js-apis-request.md#requestdownload) | \@ohos.request.d.ts | [downloadFile(context: BaseContext, config: DownloadConfig, callback: AsyncCallback&lt;DownloadTask&gt;): void;](../reference/apis/js-apis-request.md#requestdownloadfile9-1)<br>[downloadFile(context: BaseContext, config: DownloadConfig): Promise&lt;DownloadTask&gt;;](../reference/apis/js-apis-request.md#requestdownloadfile9) |
 | [upload(config: UploadConfig, callback: AsyncCallback&lt;UploadTask&gt;): void;](../reference/apis/js-apis-request.md#requestupload-1)<br>[upload(config: UploadConfig): Promise&lt;UploadTask&gt;;](../reference/apis/js-apis-request.md#requestupload) | \@ohos.request.d.ts | [uploadFile(context: BaseContext, config: UploadConfig, callback: AsyncCallback&lt;UploadTask&gt;): void;](../reference/apis/js-apis-request.md#requestuploadfile9-1)<br>[uploadFile(context: BaseContext, config: UploadConfig): Promise&lt;UploadTask&gt;;](../reference/apis/js-apis-request.md#requestuploadfile9) |