!3787 更正文档中的错误链接

Merge pull request !3787 from wusongqing/E0509

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

@@ -4,7 +4,7 @@
 >
 > The initial APIs of this module are supported since API version 6. Newly added APIs will be marked with a superscript to indicate their earliest API version.
 >
-> The APIs of API version 9 is of the Canary version and are for trial use only. The API call may be unstable.
+> The APIs of API version 9 are of the canary version and are for trial use only. The API call may be unstable.
 
 ## Modules to Import
 

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

@@ -127,9 +127,9 @@ zlib.unzipFile(inFile, outFile, options).then((data) => {
 
 | Name                       | Description                                                        |
 | --------------------------- | ------------------------------------------------------------ |
-| level?: CompressLeve        | See [zip.CompressLevel](#zip.CompressLevel).|
-| memLevel?: MemLevel         | See [zip.MemLevel](#zip.MemLevel)       |
-| strategy?: CompressStrategy | See [zip.CompressStrategy](#zip.CompressStrategy)|
+| level?: CompressLeve        | See [zip.CompressLevel](#zipcompresslevel). |
+| memLevel?: MemLevel         | See [zip.MemLevel](#zipmemlevel)     |
+| strategy?: CompressStrategy | See [zip.CompressStrategy](#zipcompressstrategy) |
 
 ## zip.MemLevel
 

en/device-dev/hpm-part/hpm-part-development.md

@@ -6,6 +6,7 @@
 You can search for common development resources on [DevEco Marketplace](https://repo.harmonyos.com) and import required resources to your projects through dependencies. If you cannot find the desired resources there, develop the resources on your own and publish them in the form of an HPM Part. To develop HPM Parts, install the hpm-cli tool first.
 
 > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+>
 > You are advised to perform the following operations on Ubuntu 18.04 or later.
 
 
@@ -17,24 +18,25 @@ The hpm-cli tool is developed based on Node.js. Therefore, you must install Node
 ### Installing Node.js and hpm-cli
 
 1. Install Node.js.
-   Download Node.js from its official website and install it on your local PC.
-
-   You are advised to install the latest LTS version (not earlier than 12.x) of [Node.js](https://nodejs.org/).
-
+   
+Download Node.js from its official website and install it on your local PC.
+   
+You are advised to install the latest LTS version (not earlier than 12.x) of [Node.js](https://nodejs.org/).
+   
 2. Install the hpm-cli tool using **npm** delivered with **Node.js**. Run the following command:
-     
+
    ```
    npm install -g @ohos/hpm-cli
    ```
 
 3. Run the following command to check whether the installation is successful. If a hpm version is displayed, the installation is successful.
-     
+
    ```
    hpm -V or hpm --version
    ```
 
 4. (Optional) Run the following command to update the hpm version if needed:
-     
+
    ```
    npm update -g @ohos/hpm-cli
    ```
@@ -44,13 +46,13 @@ The hpm-cli tool is developed based on Node.js. Therefore, you must install Node
 
 After hpm-cli is installed, run the following command to view the hpm configuration:
 
-  
+
 ```
 hpm config
 ```
 
-  The default hpm configuration is displayed upon successful command execution. You can modify the default configuration as required. The following lists the common hpm configuration:
-  
+The default hpm configuration is displayed upon successful command execution. You can modify the default configuration as required. The following lists the common hpm configuration:
+
 ```
 registry = https://hpm.harmonyos.com
 ### login Settings
@@ -82,16 +84,17 @@ You can create an HPM Part by using a template or define an existing project as
 ### Creating an HPM Part Using a Template
 
 1. Run the following command to create a directory:
-     
+   
    ```
    hpm init -t default  mybundle
    ```
 
    > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
-   > -In the preceding command, **default** indicates that the **default** template is used. You can use another template such as **simple** or **dist**.
-
+   >
+> In the preceding command, **default** indicates that the **default** template is used. You can use another template such as **simple** or **dist**.
+   
      The generated directory structure is as follows:
-     
+   
    ```
    /
    ├── headers            # Header file (example)
@@ -103,10 +106,10 @@ You can create an HPM Part by using a template or define an existing project as
    └── Makefile           # Build description file (example)
    └── README.md           # Readme file
    
-   ```
-
+```
+   
 2. Write the code and build script of the HPM Part.
-     
+   
    ```
    hpm init -t {templatename} -d {dir} {name}
    ```
@@ -120,14 +123,14 @@ You can create an HPM Part by using a template or define an existing project as
 
 The hpm-cli tool provides a few default templates. More templates are available on [DevEco Marketplace](https://repo.harmonyos.com). You can run the **hpm search -t template** command to search for a template stored on [DevEco Marketplace](https://repo.harmonyos.com).
 
-![zh-cn_image_0000001217486680](figures/zh-cn_image_0000001217486680.png)
+![en-us_image_0000001217486680](figures/en-us_image_0000001217486680.png)
 
 
 ### Defining an Existing Project as an HPM Part
 
 If you have a code project and need to distribute it on the HPM platform, run the following command in the project directory, for example, **mybundle2**:
 
-  
+
 ```
 hpm init
 ```
@@ -137,7 +140,7 @@ hpm init
 2. Enter the version and description. A **bundle.json** file will be generated in the current directory.
 
 3. Open the **bundle.json** file.
-     
+   
    ```
    $ hpm init
    Your bundle will be created in directory ~\demo\mybundle2
@@ -148,7 +151,7 @@ hpm init
    ```
 
 4. Modify other information (such as the author, code repository, code directories, scripts, and dependencies) in **bundle.json**. An example is shown below:
-     
+   
    ```
    {
    "name": "mybundle2",
@@ -177,7 +180,7 @@ In the distribution metadata file, define the dependent HPM Parts and how to bui
 
 The following uses the **bundle.json** file as an example. In this example, the **dist** command uses the **hb** framework.
 
-  
+
 ```
 {
 "name": "@your/dist_name",
@@ -225,7 +228,7 @@ The hpm-cli tool supports command integration so that you can select any build t
 
 This section describes how to build an executable file named **helloworld** in the **app** directory.
 
-  
+
 ```
 app
 ├── BUILD.gn
@@ -237,7 +240,7 @@ app
 
 Create a **BUILD.gn** file in the same directory as **helloworld.c**.
 
-  
+
 ```
 touch BUILD.gn
 vim BUILD.gn
@@ -245,7 +248,7 @@ vim BUILD.gn
 
 The following is an example of **BUILD.gn**:
 
-  
+
 ```
 executable("hello_world") {
     sources = [
@@ -268,28 +271,28 @@ executable("hello_world") {
 
 Run the following command to start the build:
 
-  
+
 ```
 hpm build
 ```
 
 After all build operations are complete, the message "build succeed" is displayed. You need to check the build result.
 
-![zh-cn_image_0000001262166533](figures/zh-cn_image_0000001262166533.png)
+![en-us_image_0000001262166533](figures/en-us_image_0000001262166533.png)
 
 
 ### Building an Image
 
 Run the following command in the root directory of the current distribution:
 
-  
+
 ```
 hpm dist
 ```
 
 The hpm-cli tool automatically starts the build. After the build is complete, an image file will be generated, as shown below:
 
-  
+
 ```
 out
 |-xxdist.img
@@ -303,7 +306,7 @@ To publish an HPM Part, you must obtain an account and create an organization (o
 
 After that, generate a public key on the local PC based on your invitation code (which can be obtained on the **My profile** page on [DevEco Marketplace](https://repo.harmonyos.com)), and configure the public key on the **My profile** page.
 
-  
+
 ```
 hpm config set loginUser {your-invitation-code}
 hpm gen-keys
@@ -315,7 +318,7 @@ Now you have the permission to publish HPM Parts in your organization.
 
 In the directory where the HPM Part is located, run the following command to pack and publish the HPM Part:
 
-  
+
 ```
 hpm publish
 ```
@@ -346,13 +349,13 @@ Visit [DevEco Marketplace](https://repo.harmonyos.com), search for HPM Parts tha
 4. Run the **hpm build** command to perform build and output the build result.
 
   Run the following command in your project. Make sure that the project directory contains the **bundle.json** file.
-  
+
 ```
 $ hpm install @scope/the_bundle
 ```
 
   The referenced HPM Part will be installed under **ohos_bundle** in the directory where your project is located. The directory structure is as follows:
-  
+
 ```
 project
 ├── ohos_bundle            
@@ -368,7 +371,7 @@ project
 
 Open the **bundle.json** file. You will see that the HPM Part has been introduced to the dependencies of your project.
 
-  
+
 ```
 {
 "dependencies": {
@@ -379,7 +382,7 @@ Open the **bundle.json** file. You will see that the HPM Part has been introduce
 
 You can edit the dependencies of multiple HPM Parts in this file.
 
-  
+
 ```
 {
 "dependencies": {
@@ -399,13 +402,13 @@ Run the **hpm install** command again to download and install all HPM Parts that
 If the referenced HPM Part is shared by multiple projects, for example, the compiler toolchain, you can install it globally.
 
   Run the following command in your project. Make sure that the project directory contains the **bundle.json** file.
-  
+
 ```
 $ hpm install -g @scope/the_tool
 ```
 
   The referenced HPM Part will be installed in the directory specified by the **globalRepo** parameter of the **hpm config** command.
-  
+
 ```
 ~\.hpm\global\ohos_bundles            
 │   └── scope
@@ -415,7 +418,7 @@ $ hpm install -g @scope/the_tool
 > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
 > - For an HPM Part installed in a project, you can reference it using the environment variable **DEP_SCOPE_bundle_name** when running the hpm build command.
 >     For example, after you run **hpm i \@opensource/gn** to install an HPM Part, edit the build script in the **bundle.json** file as follows:
->     
+>    
 >   ```
 >   "scripts": {
 >       "build": "${DEP_OPENSOURCE_gn}/gn  --version"
@@ -425,14 +428,14 @@ $ hpm install -g @scope/the_tool
 >   Then, you can run the **hpm build** command to call gn functions.
 > 
 > - For a globally installed HPM Part, you can directly call the HPM Part using an environment variable or reference the HPM Part using the **${key}/tool_name** parameter in the **hpm config set key value** command. Example:
->     
+>    
 >   ```
 >   hpm i -g @ohos/opensource/gn
 >   hpm config BUILD_SYS_GN ~/.hpm/global/ohos_bundles/opensource/gn
 >   ```
 > 
 >     You can edit the build script in the **bundle.json** file as follows:
->     
+>    
 >   ```
 >   "scripts": {
 >       "build": "${BUILD_SYS_GN}/gn  --version"

en/device-dev/subsystems/Readme-EN.md

@@ -53,7 +53,7 @@
   - [Sensor Usage Guidelines](subsys-sensor-guide.md)
   - [Sensor Usage Example](subsys-sensor-demo.md)
 - [USB](subsys-usbservice.md)
-  - [[USB Overview](subsys-usbservice-overview.md)
+  - [USB Overview](subsys-usbservice-overview.md)
   - [USB Usage Guidelines](subsys-usbservice-guide.md)
   - [USB Usage Example](subsys-usbservice-demo.md)
 - [Application Framework](subsys-application-framework.md)
@@ -61,10 +61,10 @@
   - [Setting Up a Development Environment](subsys-application-framework-envbuild.md)
   - [Development Guidelines](subsys-application-framework-guide.md)
   - [Development Example](subsys-application-framework-demo.md)
-- [OTA Upgrade](subsys-ota-guide.md)
-- [Telephony Service ](subsys-tel.md)
-  - [Telephony Service](telephony-service.md)
-  - [Development Guidelines](development-guidelines.md)
+- [OTA Update](subsys-ota-guide.md)
+- [Telephony ](subsys-tel.md)
+  - [Telephony Overview](subsys-tel-overview.md)
+  - [Telephony Development](subsys-tel-guide.md)
 - [Security](subsys-security.md)
   - [Overview](subsys-security-overview.md)
   - [Development on Application Signature Verification](subsys-security-sigverify.md)
@@ -80,7 +80,7 @@
   - [syspara Module](subsys-boot-syspara.md)
   - [FAQs](subsys-boot-faqs.md)
   - [Reference](subsys-boot-ref.md)
-- [Testing](subsys-testguide-test.md)
+- [Test](subsys-testguide-test.md)
 - [DFX](subsys-dfx.md)
   - [DFX](subsys-dfx-overview.md)
   - [HiLog Development](subsys-dfx-hilog-rich.md)

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

-# Subsystems
+# Telephony
 
--   [Telephony Service](telephony-service.md)
-    -   [Telephony Service](telephony-service.md)
-    -   [Development Guidelines](development-guidelines.md)
+-   [Telephony Overview](subsys-tel-overview.md)
+-   [Telephony Development](subsys-tel-guide.md)
 

en/device-dev/subsystems/subsys.md

 # Subsystem Development Guidelines<a name="EN-US_TOPIC_0000001111199452"></a>
 
 -   **[Compilation and Building](subsys-build.md)**  
-
 -   **[Distributed Remote Startup](subsys-remote-start.md)**  
-
 -   **[Graphics](subsys-graphics.md)**  
-
 -   **[Multimedia](subsys-multimedia.md)**  
-
 -   **[Data Management](subsys-data.md)**  
-
 -   **[Utils](subsys-utils.md)**  
-
 -   **[AI Framework](subsys-aiframework.md)**  
-
 -   **[Sensors](subsys-sensor.md)**  
-
 -   **[Application Framework](subsys-application-framework.md)**  
-
--   **[OTA Upgrade](subsys-ota-guide.md)**  
-
+-   **[OTA Update](subsys-ota-guide.md)**  
+-   **[Telephony](subsys-tel.md)**
 -   **[Security](subsys-security.md)**  
-
 -   **[Startup](subsys-boot.md)**  
-
--   **[Testing](subsys-testguide-test.md)**  
-
+-   **[Test](subsys-testguide-test.md)**  
 -   **[DFX](subsys-dfx.md)**  
-
 -   **[R&D Tools](subsys-toolchain.md)**  
-
 -   **[XTS](subsys-xts-guide.md)**  
 
 

zh-cn/device-dev/quick-start/quickstart-ide-lite-steps-hi3861.md

@@ -12,4 +12,5 @@
 
 - **[调试验证](quickstart-ide-lite-steps-hi3861-debug.md)**
 
-- **[运行](quickstart-ide-lite-steps-hi3816-running.md)**
+- **[运行](quickstart-ide-lite-steps-hi3861-running.md)**
\ No newline at end of file
+