!6210 【文档体验官】【英文】Ability文件夹一致性问题修改

Merge pull request !6210 from wusongqing/EN0701

en/application-dev/ability/ability-assistant-guidelines.md

@@ -65,18 +65,18 @@ The ability assistant enables you to start applications, atomic services, and te
   
 - **dump**
 
-  Prints ability related information.
+  Prints ability-related information.
 
   | Name             | Level-2 Parameter            | Description                                                    |
   | ----------------- | -------------------- | ------------------------------------------------------------ |
   | -h/--help         | -                    | Prints help information.                                                  |
   | -a/--all          | -                    | Prints ability information in all missions.                                |
-  | -l/--mission-list | type (All logs are printed if this parameter is left unspecified.)| Prints mission stack information.<br>The following values are available for **type**:<br>NORMAL <br>DEFAULT_STANDARD<br>DEFAULT_SINGLE<br>LAUNCHER |
+  | -l/--mission-list | type (All logs are printed if this parameter is left unspecified.)| Prints mission stack information.<br>The following values are available for **type**:<br>- NORMAL <br>- DEFAULT_STANDARD<br>- DEFAULT_SINGLE<br>- LAUNCHER |
   | -e/--extension    | elementName          | Prints extended component information.                                          |
-  | -u/--userId       | UserId               | Prints stack information of a specified user ID. This parameter must be used together with other parameters. Example commands: aa **dump -a -u 100** and **aa dump -d -u 100**.|
+  | -u/--userId       | UserId               | Prints stack information of a specified user ID. This parameter must be used together with other parameters. <br/>Example commands: aa **dump -a -u 100** and **aa dump -d -u 100**. |
   | -d/--data         | - | Prints Data ability information.                                          |
   | -i/--ability      | AbilityRecord ID     | Prints detailed information about a specified ability.                                     |
-  | -c/--client       | - | Prints detailed ability information. This parameter must be used together with other parameters. Example commands: **aa dump -a -c** and **aa dump -i 21 -c**.|
+  | -c/--client       | - | Prints detailed ability information. This parameter must be used together with other parameters. <br/>Example commands: **aa dump -a -c** and **aa dump -i 21 -c**. |
   
   **Method**
   

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

@@ -13,7 +13,7 @@ The stage model is designed to make it easier to develop complex applications in
 | -------------- | ------------------------------------------------------------ | -------------------------------------------------------- |
 | Development mode     | Web-like APIs are provided. The UI development is the same as that of the stage model.                    | Object-oriented development mode is provided. The UI development is the same as that of the FA model.            |
 | Engine instance      | Each ability in a process exclusively uses a JS VM engine instance.              | Multiple abilities in a process share one JS VM engine instance.      |
-| Intra-process object sharing| Not supported                                                    | Supported                                                  |
+| Intra-process object sharing| Not supported.                                                  | Supported.                                                 |
 | Bundle description file    | The `config.json` file is used to describe the HAP and component information. Each component must use a fixed file name.| The `module.json` file is used to describe the HAP and component information. The entry file name can be specified.|
 | Component          | Four types of components are provided: Page ability (used for UI page display), Service ability (used to provide services), Data ability (used for data sharing), and Form ability (used to provide widgets).| Two types of components are provided: Ability (used for UI page display) and Extension (scenario-based service extension).  |
 

en/application-dev/ability/fa-serviceability.md

@@ -238,7 +238,7 @@ You can use either of the following methods to connect to a Service ability:
     }
     ```
 
-### Connecting to a Remote Service Ability (Applying only to System Applications)
+### Connecting to a Remote Service Ability
 
 >**NOTE**
 >

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

@@ -8,7 +8,7 @@ The following figure shows the design ideas of the stage model.
 
 ![stagedesign](figures/stagedesign.png)
 
-​        The stage model is designed based on the following considerations:
+The stage model is designed based on the following considerations:
 
 - **Balance between application capabilities and overall system power consumption**
 

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

@@ -12,7 +12,8 @@ Basic concepts:
 - Widget host: an application that displays the widget content and controls the position where the widget is displayed in the host application.
 - Widget Manager: a resident agent that manages widgets added to the system and provides functions such as periodic widget update.
 
-> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+> **NOTE**
+>
 > The widget host and provider do not keep running all the time. The Widget Manager starts the widget provider to obtain widget information when a widget is added, deleted, or updated.
 
 You only need to develop widget content as the widget provider. The system automatically handles the work done by the widget host and Widget Manager.
@@ -187,7 +188,7 @@ To create a widget in the stage model, implement the lifecycle callbacks of **Fo
   {
       "forms": [{
           "name": "widget",
-          "description": "This is a service widget.",
+          "description": "This is a widget.",
           "src": "./js/widget/pages/index/index",
           "window": {
               "autoDesignWidth": true,

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

@@ -39,7 +39,7 @@ OpenHarmony does not support creation of a Service Extension ability for third-p
    ```
 
 
-2. Customize a class that inherits from **ServiceExtensionAbility** in the .ts file in the directory where the Service Extension ability is defined and overwrite the lifecycle callbacks of the base class. The code sample is as follows:
+2. Customize a class that inherits from **ServiceExtensionAbility** in the .ts file in the directory where the Service Extension ability is defined and override the lifecycle callbacks of the base class. The code sample is as follows:
 
     ```js
     import rpc from '@ohos.rpc'