update docs

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

en/application-dev/reference/apis/js-apis-system-parameter.md

 # System Parameter
 
-> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+> **NOTE**
 > - The initial APIs of this module are supported since API version 6. Newly added APIs will be marked with a superscript to indicate their earliest API version.
 > - This is a system API and cannot be called by third-party applications.
 
@@ -203,9 +203,9 @@ try {
 ```
 
 
-## parameter.set(key: string, def?: string)
+## parameter.set
 
-set(key: string, def?: string): Promise<string>
+set(key: string, value: string): Promise<void>
 
 Sets a value for the attribute with the specified key. This API uses a promise to return the result.
 
@@ -222,7 +222,7 @@ Sets a value for the attribute with the specified key. This API uses a promise t
 
 | Type| Description|
 | -------- | -------- |
-| Promise<string> | Promise used to return the execution result.|
+| Promise<void> | Promise used to return the execution result.|
 
 **Example**
 

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

 # Toggle
 
-
-> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+>  **NOTE**<br>
 > This component is supported since API version 8. Updates will be marked with a superscript to indicate their earliest API version.
 
 
@@ -12,7 +11,7 @@ None
 
 ## Child Components
 
-None
+Not supported
 
 
 ## APIs
@@ -20,42 +19,43 @@ None
 Toggle(options: { type: ToggleType, isOn?: boolean })
 
 - Parameters
-    | Name | Type | Mandatory | Default Value | Description |
+  | Name| Type| Mandatory| Default Value| Description|
   | -------- | -------- | -------- | -------- | -------- |
-  | type | ToggleType | Yes | - | Type of the toggle. |
-  | isOn | boolean | No | false | Initial state of the toggle.<br/>> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br/>> If **isOn** is not set during component creation, the selected state can be retained during component reuse. If **isOn** is set, the selected state needs to be retained during component reuse after the selected state is recorded using an event method. |
+  | type | ToggleType | Yes| - | Type of the toggle.|
+  | isOn | boolean | No| false | Whether the toggle is turned on. The value **true** means that the toggle is turned on, and **false** means the opposite.|
 
 
 - ToggleType enums
-    | Name | Description | 
+  | Name| Description|
   | -------- | -------- |
-  | Checkbox | A checkbox is provided. The text setting of the child component does not take effect. If the text setting is required, you can place the **&lt;Text&gt;** component and the current component in the layout component. | 
-  | Button | A button is provided. If the text setting is available, the corresponding text content is displayed inside the button. | 
-  | Switch | A switch is provided. The text setting of the child component does not take effect. If the text setting is required, you can place the **&lt;Text&gt;** component and the current component in the layout component. | 
+  | Checkbox | A checkbox is provided, where the **\<Text>** settings can take effect only when it is placed with the current component in a layout component.<br>> **NOTE**<br><br>> The default value of the universal attribute [padding](ts-universal-attributes-size.md) is as follows:<br>{<br>&nbsp;top: 14 vp,<br>&nbsp;right: 6 vp,<br>&nbsp;bottom: 14 vp,<br>&nbsp;left: 6 vp<br> } |
+  | Button | A button is provided. The set text string, if any, will be displayed inside the button.|
+  | Switch | A switch is provided, where the **\<Text>** settings can take effect only when it is placed with the current component in a layout component.<br>> **NOTE**<br><br>> The default value of the universal attribute [padding](ts-universal-attributes-size.md) is as follows:<br>{<br>&nbsp;top: 12 vp,<br>&nbsp;right: 12 vp,<br>&nbsp;bottom: 12 vp,<br>&nbsp;left: 12 vp<br> } |
 
 
 ## Attributes
 
-  | Name | Type | Default Value | Description | 
+| Name| Parameter| Default Value| Description|
 | -------- | -------- | -------- | -------- |
-| selectedColor | Color | - | Background color of the toggle when it is enabled. | 
-| switchPointColor | Color | - | Color of the circular slider of the **Switch** type.<br/>> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br/>> This attribute is valid only when type is set to **ToggleType.Switch**. | 
+| selectedColor | Color | - | Background color of the component when it is turned on.|
+| switchPointColor | Color | - | Color of the circular slider when the component is of the **Switch** type.<br>> **NOTE**<br>> This attribute is valid only when **type** is set to **ToggleType.Switch**. |
 
 
 ## Events
 
-  | Name | Description | 
+| Name| Description|
 | -------- | -------- |
-| onChange(callback: (isOn: boolean) =&gt; void) | Triggered when the switch status changes. | 
+| onChange(callback:&nbsp;(isOn:&nbsp;boolean)&nbsp;=&gt;&nbsp;void) | Triggered when the toggle status changes.|
 
 
 ## Example
 
-
-```
+```ts
+// xxx.ets
 @Entry
 @Component
 struct ToggleExample {
+
   build() {
     Column({ space: 10 }) {
       Text('type: Switch').fontSize(12).fontColor(0xcccccc).width('90%')

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

 # XComponent
 
-  > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+  > **NOTE**<br>
   > This component is supported since API version 8. Updates will be marked with a superscript to indicate their earliest API version.
 
   The **\<XComponent>** can accept and display the EGL/OpenGLES and media data input.
@@ -19,20 +19,20 @@
 
   - Name
 
-    | Name       | Type                                     | Mandatory| Description                                                        |
-    | ----------- | --------------------------------------------- | ---- | ------------------------------------------------------------ |
-    | id          | string                                        | Yes  | Unique ID of the component. The value can contain a maximum of 128 characters.                   |
-    | type        | string                                        | Yes  | Type of the component. The options are as follows:<br>-**surface**: The content of this component is displayed individually, without being combined with that of other components.<br>-**component**: The content of this component is displayed after having been combined with that of other components.<br>This API is defined but not implemented in OpenHarmony 3.1 Release. It will be available for use in OpenHarmony 3.1 MR.|
-    | libraryname | string                                        | No  | Name of the dynamic library generated after compilation at the application native layer.                            |
+    | Name        | Type                                    | Mandatory | Description                                                        |
+    | ----------- | --------------------------------------- | --------- | ------------------------------------------------------------ |
+    | id          | string                                        | Yes | Unique ID of the component. The value can contain a maximum of 128 characters.                   |
+    | type        | string                                        | Yes | Type of the component. The options are as follows:<br>- **surface**: The content of this component is displayed individually, without being combined with that of other components.<br>- **component**: The content of this component is displayed after having been combined with that of other components. |
+    | libraryname | string                                        | No  | Name of the dynamic library generated after compilation at the application native layer. |
     | controller  | [XComponentController](#XComponentController) | No  | Controller bound to the component, which can be used to invoke methods of the component.              |
 
 
 ## Events
 
-| Name                           | Description                |
+| Name                            | Description              |
 | ------------------------------- | ------------------------ |
-| onLoad(context?: object) => void | Triggered when the plug-in is loaded.|
-| onDestroy() => void             | Triggered when the plug-in is destroyed.|
+| onLoad(context?: object) => void | Triggered when the plug-in is loaded. |
+| onDestroy() => void              | Triggered when the plug-in is destroyed. |
 
 ## XComponentController
 
@@ -52,9 +52,9 @@ Obtains the ID of the surface held by the **\<XComponent>**. The ID can be used
 
   - Return value
 
-    | Type  | Description                       |
+    | Type   | Description                 |
     | ------ | --------------------------- |
-    | string | ID of the surface held by the **\<XComponent>**.|
+    | string | ID of the surface held by the **\<XComponent>**. |
 
 ### setXComponentSurfaceSize
 
@@ -64,10 +64,10 @@ Sets the width and height of the surface held by the **\<XComponent>**.
 
 - Parameters
 
-  | Name       | Type| Mandatory| Default Value| Description                         |
+  | Name       | Type | Mandatory | Default Value | Description              |
   | ------------- | -------- | ---- | ------ | ----------------------------- |
-  | surfaceWidth  | number   | Yes  | -      | Width of the surface held by the **\<XComponent>**.|
-  | surfaceHeight | number   | Yes  | -      | Height of the surface held by the **\<XComponent>**.|
+  | surfaceWidth  | number   | Yes  | -      | Width of the surface held by the **\<XComponent>**. |
+  | surfaceHeight | number   | Yes  | -      | Height of the surface held by the **\<XComponent>**. |
 
 ### getXComponentContext
 
@@ -85,7 +85,8 @@ Obtains the context of an **\<XComponent>** object.
 
 Provide a surface-type **\<XComponent>** to support capabilities such as camera preview.
 
-```
+```ts
+// xxx.ets
 import camera from '@ohos.multimedia.camera';
 @Entry
 @Component

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

 # Image Effect Configuration
 
 
-> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+> **NOTE**
 > This attribute is supported since API version 7. Updates will be marked with a superscript to indicate their earliest API version.
 
 
@@ -25,7 +25,7 @@ None
 | invert | number | 0 | Inverts the input image. The input parameter is an image inversion ratio. The value **1** indicates complete inversion. The value **0** indicates that the image does not change. The unit is percentage. |
 | colorBlend <sup>8+</sup> | Color | - | Adds the color blend effect to the current component. The input parameter is the blended color. |
 | sepia | number | 0 | Converts the image color to sepia. The input parameter is an image inversion ratio. The value **1** indicates the image is completely sepia. The value **0** indicates that the image does not change. The unit is percentage. |
-| hueRotate | Angle | 0deg | Adds the hue rotation effect to the current component. The input parameter is a rotation angle. If the input value is **0deg**, the image does not change (because the default rotation angle is **0deg**). The input parameter does not have the maximum value. If the value exceeds **360deg**, the image is rotated one ore more circles. |
+| hueRotate | number \| string | '0deg' |Adds the hue rotation effect to the current component. The input parameter is a rotation angle. If the input value is **0deg**, the image does not change (because the default rotation angle is **0deg**). The input parameter does not have the maximum value. If the value exceeds **360deg**, the image is rotated for one more circle. In other words, the value **370deg** has the same effect as **10deg**.|
 
 
 ## Example

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

@@ -28,7 +28,7 @@
     - Running a Hello World Program
         - Hi3861 Development Board
             - [Setting Up the Hi3861 Development Board Environment](quickstart-lite-steps-hi3861-setting.md)
-            - [Writing a Hello World Program](quickstart-lite-steps-hi3861-application-framework.md)
+            - [Writing a Hello World Program](quickstart-lite-steps-hi3861-helloworld.md)
             - [Building](quickstart-lite-steps-hi3861-building.md)
             - [Burning](quickstart-lite-steps-hi3861-burn.md)
             - [Networking](quickstart-lite-steps-hi3861-netconfig.md)
@@ -36,7 +36,7 @@
             - [Running](quickstart-lite-steps-hi3861-running.md)
         - Hi3516 Development Board
             - [Setting Up the Hi3516 Development Board Environment](quickstart-lite-steps-hi3516-setting.md)
-            - [Writing a Hello World Program](quickstart-lite-steps-hi3516-application-framework.md)
+            - [Writing a Hello World Program](quickstart-lite-steps-hi3516-helloworld.md)
             - [Building](quickstart-lite-steps-hi3516-building.md)
             - [Burning](quickstart-lite-steps-hi3516-burn.md)
             - [Running](quickstart-lite-steps-hi3516-running.md)
@@ -75,7 +75,7 @@
     - [Setting Up Environments for Standard System](quickstart-standard-env-setup.md)
     - Running a Hello World Program
         - Hi3516 Development Board
-            - [Writing a Hello World Program](quickstart-standard-running-hi3516-create.md)
+            - [Writing a Hello World Program](quickstart-std-3516-create.md)
             - [Building](quickstart-standard-running-hi3516-build.md)
             - [Burning](quickstart-standard-running-hi3516-burning.md)
             - [Running](quickstart-standard-running-hi3516-running.md)

en/device-dev/quick-start/quickstart-docker-lite.md

-# Getting Started with Mini and Small Systems (Installation Package Mode)
-
-
-
-- **[Mini and Small System Overview](quickstart-lite-overview.md)**
-
-- **[Setting Up Environments for the Mini and Small Systems](quickstart-lite-env-setup.md)**
-
-- **[Running a Hello World Program](quickstart-lite-steps.md)**
-
-- **[FAQs](quickstart-lite-env-setup-faqs.md)**
-
-- **[Appendix](quickstart-lite-appendix.md)**

en/device-dev/quick-start/quickstart-ide-lite-appendix.md

-# Appendix
-
-
-
-- **[Introduction to Development Boards](quickstart-ide-lite-board-introduction.md)**

en/device-dev/quick-start/quickstart-ide-lite-board-introduction.md

-# Introduction to Development Boards
-
-
-
-- **[Introduction to the Hi3861 Development Board](quickstart-ide-lite-introduction-hi3861.md)**
-
-- **[Introduction to the Hi3516 Development Board](quickstart-ide-lite-introduction-hi3516.md)**

en/device-dev/quick-start/quickstart-ide-lite-create-project.md

-# Creating a Source Code Project
+# Importing a Source Code Project
 
 
 After [setting up the Windows+Ubuntu hybrid development environment](../quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md) and [obtaining source code](../quick-start/quickstart-ide-lite-sourcecode-acquire.md), perform the following steps to create a source code project in Windows:
@@ -15,7 +15,7 @@ After [setting up the Windows+Ubuntu hybrid development environment](../quick-st
 
    ![en-us_image_0000001271477045](figures/en-us_image_0000001271477045.png)
 
-3. If you select to open the OpenHarmony source code, a message will be displayed indicating that the project is not a DevEco Device Tool project. Click **Import** to continue.
+3. If this is the first time you import a project, a message will be displayed indicating that the project is not a DevEco Device Tool project. Click **Import** to continue.
 
    ![en-us_image_0000001135394334](figures/en-us_image_0000001135394334.png)
 

en/device-dev/quick-start/quickstart-ide-lite-env-setup-win-ubuntu.md

@@ -11,15 +11,18 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits
 
 - Windows: Windows 10 (64-bit)
 
-- Ubuntu: Ubuntu 20.04 or later; recommended memory: 16 GB or higher.
+- Ubuntu: Ubuntu 20.04 or later; recommended memory: 16 GB or higher
 
-- User name: cannot contain Chinese characters
+- User name (Ubuntu): cannot contain Chinese characters
 
 - DevEco Device Tool: 3.0 Release
 
 
 ## Setting Up the Ubuntu Development Environment
 
+> ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+> If the Ubuntu system has not been set up yet, set it up on a virtual machine running Windows. Then, configure the Ubuntu basic environment.
+
 1. Make sure the Ubuntu shell environment is **bash**.
    1. Run the following command and check whether the command output is **bash**. If the command output is not **bash**, go to step 2.
       
@@ -55,14 +58,15 @@ In the Windows+Ubuntu hybrid development environment, you can enjoy the benefits
 
 4. Run the following command to install DevEco Device Tool, where **devicetool-linux-tool-3.0.0.401.sh** indicates the installation file name.
 
-   > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
-   > During the installation, the setup wizard automatically checks whether Python 3.8 or 3.9 is installed. If Python 3.8 or 3.9 is not installed, the setup wizard displays the "Do you want to continue?" message; enter **Y** to allow the setup wizard to automatically install Python.
-
-   
    ```
    sudo ./devicetool-linux-tool-3.0.0.401.sh
    ```
-
+   > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br>
+   > During the installation, the setup wizard automatically checks whether Python 3.8 or 3.9 is installed. If Python 3.8 or 3.9 is not installed, the setup wizard displays the "Do you want to continue?" message; enter **Y** to allow the setup wizard to automatically install Python.
+   > 
+   > During the installation, the page for agreeing to the user agreement and privacy statement is displayed. Read and agree to the user agreement and privacy statement.
+   > 
+   > If this page is not displayed and the installation exits, run the apt-get install whiptail command, then the installation command.
    Wait until the "Deveco Device Tool successfully installed." message is displayed.
 
    ![en-us_image_0000001198722374](figures/en-us_image_0000001198722374.png)
@@ -76,7 +80,7 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
 
 2. Decompress the DevEco Device Tool package, double-click the installer, and then click **Next**.
 
-3. Set the installation path of DevEco Device Tool and click **Next**. You are advised to install DevEco Device Tool in a non-system drive.
+3. Set the installation path of DevEco Device Tool to a path that does not contain any Chinese characters, and then click **Next**. You are advised to install DevEco Device Tool in a non-system drive.
 
    > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
    > If you have installed DevEco Device Tool 3.0 Beta2 or earlier, the earlier version will be uninstalled before you install a new version. If the following error message is displayed during the uninstallation, click **Ignore** to continue the installation. This error does not affect the installation of the new version.
@@ -101,11 +105,14 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
 
        ![en-us_image_0000001193983334](figures/en-us_image_0000001193983334.png)
 
-5. In the dialog box shown below, click **Next** to download and install the tools..
+5. In the dialog box shown below, click **Next**.
 
    ![en-us_image_0000001239634067](figures/en-us_image_0000001239634067.png)
 
-6. Wait for the DevEco Device Tool setup wizard to automatically install DevEco Device Tool. After the installation is complete, click **Finish** to close the setup wizard.
+6. Read the user agreement and privacy statement carefully, select I accept the licenses, and click **Next**.
+
+   ![en-us_image_0000001307019009](figures/en-us_image_0000001307019009.png)
+7. Wait for the DevEco Device Tool setup wizard to automatically install DevEco Device Tool. After the installation is complete, click **Finish** to close the setup wizard.
 
    ![en-us_image_0000001239650137](figures/en-us_image_0000001239650137.png)
 
@@ -174,29 +181,9 @@ To remotely access the Ubuntu environment through Windows and enjoy the benefits
    ![en-us_image_0000001215720398](figures/en-us_image_0000001215720398.png)
 
 5. In the displayed dialog box, select **Linux**, select **Continue**, and enter the password for logging in to the remote computer.
+   > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
+   > To eliminate the need for frequently entering the password for logging in to the remote computer, set an SSH public key.
 
    ![en-us_image_0000001215897530](figures/en-us_image_0000001215897530.png)
 
    After the connection is successful, the plug-in is automatically installed in the .vscode-server folder on the remote computer. After the installation is complete, reload Visual Studio Code in Windows as prompted. Then you can develop, compile, and burn source code in DevEco Device Tool on Windows.
-
-
-### Registering the Public Key for Accessing the Ubuntu Environment
-
-After the preceding operations are complete, you can remotely connect to the Ubuntu environment through Windows for development. However, you need to frequently enter the remote connection password. To eliminate this need, you can use the SSH public key.
-
-1. Open the Git bash CLI and run the following command to generate an SSH public key. During command execution, perform operations as prompted. Set **username** and **ip** to the user name and IP address you use for connecting to the Ubuntu system.
-   
-   ```
-   ssh-keygen -t rsa
-   ssh-copy-id -i ~/.ssh/id_rsa.pub username@ip
-   ```
-
-   ![en-us_image_0000001271532317](figures/en-us_image_0000001271532317.png)
-
-2. In Visual Studio Code, click the remote connection setting button and open the **config** file.
-
-   ![en-us_image_0000001226034634](figures/en-us_image_0000001226034634.png)
-
-3. In the **config** file, add the SSK key file information, as shown below. Then save the file.
-
-   ![en-us_image_0000001270356233](figures/en-us_image_0000001270356233.png)

en/device-dev/quick-start/quickstart-ide-lite-env-setup.md

-# Environment Preparation
-
-
-
-- **[Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-lite-env-setup-win-ubuntu.md)**
-
-- **[Obtaining Source Code](quickstart-ide-lite-sourcecode-acquire.md)**
-

en/device-dev/quick-start/quickstart-ide-lite-introduction-hi3861.md

@@ -7,7 +7,7 @@ Hi3861 is a 2 x 5 cm development board. It is a 2.4 GHz WLAN SoC chip that highl
 
 **Figure 1** Hi3861 development board
 
-  ![en-us_image_0000001226634692](figures/en-us_image_0000001226634692.png)
+![en-us_image_0000001226634692](figures/en-us_image_0000001226634692.png)
 
 The Hi3861 development board can also be connected to the Hi3861 mother board to expand its peripheral capabilities. The following figure shows the Hi3861 mother board.
 

en/device-dev/quick-start/quickstart-ide-lite-overview.md

@@ -10,7 +10,7 @@ To accommodate different developer habits, OpenHarmony provides two modes for ge
 - IDE mode: DevEco Device Tool is used for one-stop development, covering dependency installation, building, burning, and running.
 
 - Installation package mode: Dependency download and installation as well as building operations are performed using commands. Burning and running are performed in DevEco Device Tool.
-  OpenHarmony also provides the [Docker environment](../get-code/gettools-acquire.md), which can significantly simplify the environment configuration before compilation. You can build your source code in the Docker environment if you are more accustomed to using the installation package mode.
+  OpenHarmony also provides the [Docker environment](https://gitee.com/openharmony/docs/blob/master/en/device-dev/get-code/gettools-acquire.md), which can significantly simplify the environment configuration before compilation. You can build your source code in the Docker environment if you are more accustomed to using the installation package mode.
 
 This document exemplifies how to use the IDE mode. For details about the installation package mode, see [Getting Started with Mini and Small Systems (Installation Package Mode)](../quick-start/quickstart-lite-overview.md).
 

en/device-dev/quick-start/quickstart-ide-lite-sourcecode-acquire.md

@@ -10,7 +10,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
 
 2. Register an SSH public key for access to Gitee.
 
-3. Install the git client and git-lfs.
+3. Install the git client and git-lfs if they are unavailable.
 
      Update the software source:
      
@@ -18,14 +18,14 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
    sudo apt-get update
    ```
 
-     Run the following command to install the tools:
-     
+    Run the following command to install the tools:
+   
    ```
    sudo apt-get install git git-lfs
    ```
 
 4. Configure user information.
-     
+   
    ```
    git config --global user.name "yourname"
    git config --global user.email "your-email-address"
@@ -33,7 +33,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
    ```
 
 5. Run the following commands to install the **repo** tool:
-     
+   
    ```
    curl https://gitee.com/oschina/repo/raw/fork_flow/repo-py3 -o /usr/local/bin/repo  # If you do not have the access permission to this directory, download the tool to any other accessible directory and configure the directory to the environment variable.
    chmod a+x /usr/local/bin/repo
@@ -58,7 +58,7 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
 
   Method 2: Use the **repo** tool to download the source code over HTTPS.
 
-    
+  
   ```
   repo init -u https://gitee.com/openharmony/manifest.git -b master --no-repo-verify
   repo sync -c
@@ -70,10 +70,10 @@ In the Ubuntu environment, perform the following steps to obtain the OpenHarmony
   For details about how to obtain the source code of an OpenHarmony release, see the [Release-Notes](../../release-notes/Readme.md).
 
 
-## Running prebuilts
+### Running prebuilts
+
+Go to the root directory of the source code and run the following script to install the compiler and binary tool:
 
-  Go to the root directory of the source code and run the following script to install the compiler and binary tool:
-  
 ```
 bash build/prebuilts_download.sh
 ```

en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md

 # Burning
 
 
+Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
+
+
 Hi3516D V300 supports burning through the USB port, network port, and serial port. This document describes how to burn source code through the USB port. The operations are performed in Windows.
 
 
 1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3516D V300 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3516.md).
+   > ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**
+   > If you are using the remote access mode (Windows + Ubuntu on the local VM), disable the USB control of the VM as follows to ensure that the development board is connected to the USB port of the host:
+   > 
+   > - VMware: Configure the device to connect to the host under **Preferences** > **USB** and remove the USB controller from the VM settings.
+   > 
+   > - VirtualBox: Deselect **Enable USB Controller** in the USB device options under Ubuntu settings.
 
-2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment).
+2. If your computer does not have the USB port driver or USB-to-serial driver, install it by following the instructions in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board) or [Installing the Serial Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695), depending on the missing driver.
 
+3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu build environment) and the local computer (Windows build environment).
    - If ![en-us_image_0000001261315939](figures/en-us_image_0000001261315939.png) is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required.
    - If ![en-us_image_0000001261515989](figures/en-us_image_0000001261515989.png) is displayed, click the connect icon.
 
    ![en-us_image_0000001261395999](figures/en-us_image_0000001261395999.png)
 
-   > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br/>
-   > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step.
+   > ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**
+   > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid build environment). If the local access mode (Windows or Ubuntu build environment) is used, skip this step.
 
-3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
+4. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
 
    ![en-us_image_0000001216516128](figures/en-us_image_0000001216516128.png)
 
-   > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
-   > If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on the Hi3516 or Hi3518 Series Development Boards](https://device.harmonyos.com/en/docs/documentation/guide/hi3516_hi3518-drivers-0000001050743695).
-
-4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
+5. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
 
    ![en-us_image_0000001198566364](figures/en-us_image_0000001198566364.png)
 
-5. On the **hi3516dv300** tab page, set the burning options.
-
+6. On the **hi3516dv300** tab page, set the burning options.
    - **upload_partitions**: Select the file to be burnt. By default, the **fastboot**, **kernel**, **rootfs**, and **userfs** files are burnt at the same time.
    - **upload_port**: Select the serial port number obtained.
    - **upload_protocol**: Select the burning protocol **hiburn-usb**.
 
    ![en-us_image_0000001223190441](figures/en-us_image_0000001223190441.png)
 
-6. Check the preset information of the files to be burnt and modify them when necessary. The files to be burnt include **fastboot**, **kernel**, **rootfs**, and **userfs**.
-
-   1. On the **hi3516dv300_fastboot** tab, select the items to be modified in **New Option**, such as **partition_bin**, **partition_addr**, and **partition_length**.
-
-       ![en-us_image_0000001198889702](figures/en-us_image_0000001198889702.png)
-
-   2. In **Partition Options**, modify the items selected in the preceding step.
-
-       > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
-       > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
+7. In **Partitions**, check the preset burning settings of the files to be burnt.
 
-       ![en-us_image_0000001243290907](figures/en-us_image_0000001243290907.png)
+   ![en-us_image_0000001312778829](figures/en-us_image_0000001312778829.png)
 
-   3. Follow the same procedure to modify the information about the **kernel**, **rootfs**, and **userfs** files.
+    To modify the burning settings for a specific file, click ![en-us_image_0000001312898911](figures/en-us_image_0000001312898911.png) next to the file.
+   > ![icon-note.gif](../public_sys-resources/icon-note.gif) **NOTE**
+   > Set the start address and length of the partition based on the size of the files to be burnt. Make sure the size of the partition is greater than that of the files to be burnt and the partition addresses of the files to be burnt do not overlap.
 
-7. When you finish modifying, click **Save** on the top.
+   ![en-us_image_0000001312780249](figures/en-us_image_0000001312780249.png)
 
-8. Go to **hi3516dv300** > **Upload** to start burning.
+8. When you finish modifying, click **Save** on the top.
 
-   > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
-   > If this is the first time you burn source code to the Hi3516D V300 or Hi3518E V300 board, the message "not find the Devices" may be displayed. In this case, follow the steps in [Installing the USB Port Driver on the Hi3516D V300 or Hi3518E V300 Development Board](https://device.harmonyos.com/en/docs/documentation/guide/usb_driver-0000001058690393) and start burning again.
+9. Go to **hi3516dv300** > **Upload** to transfer the files to be burnt from Ubuntu to Windows. When the "Operation paused, Please press Enter key to continue" message is displayed, which indicates that the transfer is complete, press **Enter** to start burning.
 
-   ![en-us_image_0000001267231481](figures/en-us_image_0000001267231481.png)
+   ![en-us_image_0000001266887264](figures/en-us_image_0000001266887264.png)
 
-9. When the following information is displayed in the Terminal window, press and hold the reset button, remove and insert the USB cable, and release the reset button to start burning.
+10. When the following information is displayed in the **TERMINAL** window, press and hold the reset button within 15 seconds, remove and insert the USB cable, and release the reset button to start burning.
 
-   ![en-us_image_0000001114129426](figures/en-us_image_0000001114129426.png)
+    ![en-us_image_0000001114129426](figures/en-us_image_0000001114129426.png)
 
-   If the following message is displayed, it indicates that the burning is successful.
+    If the following message is displayed, it indicates that the burning is successful.
 
-   ![en-us_image_0000001160649343](figures/en-us_image_0000001160649343.png)
+    ![en-us_image_0000001160649343](figures/en-us_image_0000001160649343.png)
 
-10. When the burning is successful, perform the operations in Running an Image to start the system.
+11. When the burning is successful, perform the operations in Running to start the system.

en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-running.md

@@ -30,13 +30,13 @@ After burning is completed, you need to configure the bootloader to run the Open
 After the system is started, perform the following steps to run the Hello World program:
 
 1. Go to the **bin** directory on the startup page.
-     
+   
    ```
    cd bin
    ```
 
 2. Run the following command to run the **helloworld** program:
-     
+   
    ```
    ./helloworld
    ```
@@ -48,4 +48,4 @@ After the system is started, perform the following steps to run the Hello World
 
 ## Next
 
-Congratulations! You have finished all steps! Proceed to [develop a sample camera with a screen](https://gitee.com/openharmony/docs/blob/master/en/device-dev/guide/device-camera.md) to better familiarize yourself with OpenHarmony development.
+Congratulations! You have finished all steps! Proceed to [develop a sample camera with a screen](../guide/device-camera-control-overview.md) to better familiarize yourself with OpenHarmony development.

en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516.md

-# Hi3516 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-ide-lite-steps-hi3516-application-framework.md)**
-
-- **[Building](quickstart-ide-lite-steps-hi3516-building.md)**
-
-- **[Burning](quickstart-ide-lite-steps-hi3516-burn.md)**
-
-- **[Running](quickstart-ide-lite-steps-hi3516-running.md)**

en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md

 # Burning
 
+Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
 
 Hi3861 V100 supports burning through the serial port. To burn source code through the serial port in Windows, perform the following steps:
 
 
 1. Connect the computer and the target development board through the serial port and USB port. For details, see [Introduction to the Hi3861 V100 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3861.md).
 
-2. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment).
+2. If your computer does not have the USB-to-serial driver, install it by following the instructions in [Installing the Serial Port Driver on Hi3861 V100](https://device.harmonyos.com/en/docs/documentation/guide/hi3861-drivers-0000001058153433).
+
+3. In DevEco Device Tool, choose **REMOTE DEVELOPMENT** > **Local PC** to check the connection status between the remote computer (Ubuntu development environment) and the local computer (Windows development environment).
 
    - If ![en-us_image_0000001261315939](figures/en-us_image_0000001261315939.png) is displayed on the right of **Local PC**, the remote computer is connected to the local computer. In this case, no further action is required.
    - If ![en-us_image_0000001261515989](figures/en-us_image_0000001261515989.png) is displayed, click the connect icon.
@@ -16,18 +19,17 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug
    > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
    > This operation is required only in remote access mode (in the Windows+Ubuntu hybrid development environment). If the local access mode (Windows or Ubuntu development environment) is used, skip this step.
 
-3. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
+4. Check the serial port number in **QUICK ACCESS** > **DevEco Home** > **Device** in DevEco Device Tool.
 
    ![en-us_image_0000001216274840](figures/en-us_image_0000001216274840.png)
 
-   > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**
-   > If the serial port number is not displayed correctly, follow the steps described in [Installing the Serial Port Driver on Hi3861 V100](https://device.harmonyos.com/en/docs/documentation/guide/hi3861-drivers-0000001058153433).
+   
 
-4. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
+5. Choose **QUICK ACCESS** > **DevEco Home** > **Projects**, and then click **Settings**.
 
    ![en-us_image_0000001198943768](figures/en-us_image_0000001198943768.png)
 
-5. On the **hi3861** tab page, set the burning options.
+6. On the **hi3861** tab page, set the burning options.
 
    - **upload_port**: Select the serial port number obtained.
    - **upload_protocol**: Select the burning protocol **hiburn-serial**.
@@ -35,22 +37,24 @@ Hi3861 V100 supports burning through the serial port. To burn source code throug
 
    ![en-us_image_0000001243704061](figures/en-us_image_0000001243704061.png)
 
-6. Check the preset information of the files to be burnt and modify them when necessary.
+7. In **Partitions**, check the preset burning settings of the files to be burnt.
+
+   ![en-us_image_000000131299335](figures/en-us_image_000000131299335.png)
 
-   On the **hi3861_app** tab page, select **partition_bin** from **New Option**, and set the path of the file to be burnt.
+   To modify the burning settings for a specific file, click ![en-us_image_0000001312898911](figures/en-us_image_0000001312898911.png) next to the file.
 
-   ![en-us_image_0000001260919759](figures/en-us_image_0000001260919759.png)
+   ![en-us_image_0000001312912501](figures/en-us_image_0000001312912501.png)
 
-7. When you finish modifying, click **Save** on the top.
+8. When you finish modifying, click **Save** on the top.
 
-8. Click **Open** to open the project file. Then, choose **PROJECT TASKS** > **hi3861** > **Upload** to start burning.
+9. Click **Open** to open the project file. Then, choose **PROJECT TASKS** > **hi3861** > **Upload** to start burning.
 
    ![en-us_image_0000001216440138](figures/en-us_image_0000001216440138.png)
 
-9. When the following information is displayed, press the RST button on the development board to restart it.
+10. When the following information is displayed, press the RST button on the development board within 15 seconds to restart it.
 
    ![en-us_image_0000001198466090](figures/en-us_image_0000001198466090.png)
 
-10. Wait until the burning is complete. When the following message is displayed, the burning is successful.
+   When the following message is displayed, the burning is successful.
 
-    ![en-us_image_0000001216761476](figures/en-us_image_0000001216761476.png)
+   ![en-us_image_0000001216761476](figures/en-us_image_0000001216761476.png)
\ No newline at end of file

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

-# Hi3861 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-ide-lite-steps-hi3861-application-framework.md)**
-
-- **[Building](quickstart-ide-lite-steps-hi3861-building.md)**
-
-- **[Burning](quickstart-ide-lite-steps-hi3861-burn.md)**
-
-- **[Networking](quickstart-ide-lite-steps-hi3861-netconfig.md)**
-
-- **[Debugging and Verification](quickstart-ide-lite-steps-hi3861-debug.md)**
-
-- **[Running](quickstart-ide-lite-steps-hi3861-running.md)**

en/device-dev/quick-start/quickstart-ide-lite-steps.md

-# Running a Hello World Program
-
-
-
-- **[Hi3861 Development Board](quickstart-ide-lite-steps-hi3861.md)**
-
-- **[Hi3516 Development Board](quickstart-ide-lite-steps-hi3516.md)**

en/device-dev/quick-start/quickstart-ide-lite.md

-# Getting Started with Mini and Small Systems (IDE Mode)
-
-
-
-- **[Mini and Small System Overview](quickstart-ide-lite-overview.md)**
-
-- **[Environment Preparation](quickstart-ide-lite-env-setup.md)**
-
-- **[Creating a Source Code Project](quickstart-ide-lite-create-project.md)**
-
-- **[Running a Hello World Program](quickstart-ide-lite-steps.md)**
-
-- **[Appendix](quickstart-ide-lite-appendix.md)**

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

-# Appendix
-
-
-
-- **[Introduction to Development Boards](quickstart-ide-standard-board-introduction.md)**

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

-# Introduction to Development Boards
-
-
-
-- **[Introduction to the Hi3516 Development Board](quickstart-ide-standard-board-introduction-hi3516.md)**
-
-- **[Introduction to the RK3568 Development Board](quickstart-ide-standard-board-introduction-rk3568.md)**

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

-# Creating a Source Code Project
+# Importing a Source Code Project
 
 
 After [setting up the Windows+Ubuntu hybrid development environment](../quick-start/quickstart-ide-standard-env-setup-win-ubuntu.md) and [obtaining source code](../quick-start/quickstart-ide-standard-sourcecode-acquire.md), perform the following steps to create a source code project in Windows:

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

-# Environment Preparation
-
-
-
-- **[Setting Up the Windows+Ubuntu Hybrid Development Environment](quickstart-ide-standard-env-setup-win-ubuntu.md)**
-
-- **[Obtaining Source Code](quickstart-ide-standard-sourcecode-acquire.md)**

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

-# Hi3516 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-ide-standard-running-hi3516-create.md)**
-
-- **[Building](quickstart-ide-standard-running-hi3516-build.md)**
-
-- **[Burning](quickstart-ide-standard-running-hi3516-burning.md)**
-
-- **[Running](quickstart-ide-standard-running-hi3516-running.md)**

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

-# RK3568 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-ide-standard-running-rk3568-create.md)**
-
-- **[Building](quickstart-ide-standard-running-rk3568-build.md)**
-
-- **[Burning](quickstart-ide-standard-running-rk3568-burning.md)**
-
-- **[Running](quickstart-ide-standard-running-rk3568-running.md)**

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

-# Running a Hello World Program
-
-
-
-- **[Hi3516 Development Board](quickstart-ide-standard-running-hi3516.md)**
-
-- **[RK3568 Development Board](quickstart-ide-standard-running-rk3568.md)**

en/device-dev/quick-start/quickstart-lite-appendix.md

-# Appendix
-
-
-
-- **[Introduction to Development Boards](quickstart-lite-board-introduction.md)**
-
-- **[Reference](quickstart-lite-reference.md)**

en/device-dev/quick-start/quickstart-lite-board-introduction.md

-# Introduction to Development Boards
-
-
-
-- **[Introduction to the Hi3861 Development Board](quickstart-lite-introduction-hi3861.md)**
-
-- **[Introduction to the Hi3516 Development Board](quickstart-lite-introduction-hi3516.md)**

en/device-dev/quick-start/quickstart-lite-env-setup-faqs.md

-# FAQs
-
-
-
-- **[Fixing hb Installation Issues](quickstart-lite-faq-hb.md)**
-
-- **[Fixing Compilation Issues](quickstart-lite-faq-compose.md)**
-
-- **[Fixing Burning Issues](quickstart-lite-faq-burning.md)**

en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md

 # Burning
 
 
-Hi3516D V300 supports burning through the USB port, network port, and serial port. This document describes how to burn source code through the USB port. The operations are performed in Windows.
+Burning is the process of downloading compiled program files to a development board to provide a basis for subsequent debugging. With the one-click burning function of DevEco Device Tool, you can burn images on development boards quickly and efficiently.
 
 
 ### Importing Source Code

en/device-dev/quick-start/quickstart-lite-steps-hi3516.md

-# Hi3516 Development Board
-
-
-
-- **[Setting Up the Hi3516 Development Board Environment](quickstart-lite-steps-hi3516-setting.md)**
-
-- **[Writing a Hello World Program](quickstart-lite-steps-hi3516-application-framework.md)**
-
-- **[Building](quickstart-lite-steps-hi3516-building.md)**
-
-- **[Burning](quickstart-lite-steps-hi3516-burn.md)**
-
-- **[Running](quickstart-lite-steps-hi3516-running.md)**

en/device-dev/quick-start/quickstart-lite-steps-hi3861.md

-# Hi3861 Development Board
-
-
-
-- **[Setting Up the Hi3861 Development Board Environment](quickstart-lite-steps-hi3861-setting.md)**
-
-- **[Writing a Hello World Program](quickstart-lite-steps-hi3861-application-framework.md)**
-
-- **[Building](quickstart-lite-steps-hi3861-building.md)**
-
-- **[Burning](quickstart-lite-steps-hi3861-burn.md)**
-
-- **[Networking](quickstart-lite-steps-hi3861-netconfig.md)**
-
-- **[Debugging and Verification](quickstart-lite-steps-hi3861-debug.md)**
-
-- **[Running](quickstart-lite-steps-hi3861-running.md)**
-

en/device-dev/quick-start/quickstart-lite-steps.md

-# Running a Hello World Program
-
-
-
-- **[Hi3861 Development Board](quickstart-lite-steps-hi3861.md)**
-
-- **[Hi3516 Development Board](quickstart-lite-steps-hi3516.md)**

en/device-dev/quick-start/quickstart-standard-appendix.md

-# Appendix
-
-
-
-- **[Introduction to Development Boards](quickstart-standard-board-introduction.md)**
-
-- **[Reference](quickstart-standard-reference.md)**

en/device-dev/quick-start/quickstart-standard-board-introduction.md

-# Introduction to Development Boards
-
-
-
-- **[Introduction to the Hi3516 Development Board](quickstart-standard-board-introduction-hi3516.md)**
-
-- **[Introduction to the RK3568 Development Board](quickstart-standard-board-introduction-rk3568.md)**

en/device-dev/quick-start/quickstart-standard-docker.md

-# Getting Started with Standard System (Using the Installation Package)
-
-
-
-- **[Standard System Overview](quickstart-standard-overview.md)**
-
-- **[Setting Up Environments for Standard System](quickstart-standard-env-setup.md)**
-
-- **[Running a Hello World Project](quickstart-standard-running.md)**
-
-- **[FAQs](quickstart-standard-faqs.md)**
-
-- **[Appendix](quickstart-standard-appendix.md)**

en/device-dev/quick-start/quickstart-standard-faqs.md

-# FAQs
-
-
-
-- **[Fixing hb Installation Issues](quickstart-standard-faq-hb.md)**
-
-- **[Fixing Compilation Issues](quickstart-standard-faq-compose.md)**
-
-- **[Fixing Burning Issues](quickstart-standard-faq-burning.md)**
-

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

-# Getting Started with Standard System (IDE Mode)
-
-
-
-- **[Standard System Overview](quickstart-ide-standard-overview.md)**
-
-- **[Environment Preparation](quickstart-ide-standard-env-setup.md)**
-
-- **[Creating a Source Code Project](quickstart-ide-standard-create-project.md)**
-
-- **[Running a Hello World Program](quickstart-ide-standard-running.md)**
-
-- **[Appendix](quickstart-ide-standard-appendix.md)**

en/device-dev/quick-start/quickstart-standard-running-hi3516.md

-# Hi3516 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-standard-running-hi3516-create.md)**
-
-- **[Building](quickstart-standard-running-hi3516-build.md)**
-
-- **[Burning](quickstart-standard-running-hi3516-burning.md)**
-
-- **[Running](quickstart-standard-running-hi3516-running.md)**

en/device-dev/quick-start/quickstart-standard-running-rk3568.md

-# RK3568 Development Board
-
-
-
-- **[Writing a Hello World Program](quickstart-standard-running-rk3568-create.md)**
-
-- **[Building](quickstart-standard-running-rk3568-build.md)**
-
-- **[Burning](quickstart-standard-running-rk3568-burning.md)**
-
-- **[Running](quickstart-standard-running-rk3568-running.md)**

en/device-dev/quick-start/quickstart-standard-running.md

-# Running a Hello World Program
-
-
-
-- **[Hi3516 Development Board](quickstart-standard-running-hi3516.md)**
-
-- **[RK3568 Development Board](quickstart-standard-running-rk3568.md)**

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

-# Getting Started
-
-
-
-- **[Getting Started with Mini and Small Systems](quickstart-lite.md)**
-
-- **[Getting Started with Standard System](quickstart-standard.md)**

en/device-dev/website.md

@@ -11,13 +11,13 @@
 
           - [Obtaining Source Code](quick-start/quickstart-ide-lite-sourcecode-acquire.md)
 
-      - [Creating a Source Code Project](quick-start/quickstart-ide-lite-create-project.md)
+      - [Importing a Source Code Project](quick-start/quickstart-ide-lite-create-project.md)
 
       - Running a Hello World Program
 
           - Hi3861 Development Board
 
-              - [Writing a Hello World Program](quick-start/quickstart-ide-lite-steps-hi3861-application-framework.md)
+              - [Writing a Hello World Program](quick-start/quickstart-ide-lite-steps-hi3861-helloworld.md)
 
               - [Building](quick-start/quickstart-ide-lite-steps-hi3861-building.md)
 
@@ -31,7 +31,7 @@
 
           - Hi3516 Development Board
 
-              - [Writing a Hello World Program](quick-start/quickstart-ide-lite-steps-hi3516-application-framework.md)
+              - [Writing a Hello World Program](quick-start/quickstart-ide-lite-steps-hi3516-helloworld.md)
 
               - [Building](quick-start/quickstart-ide-lite-steps-hi3516-building.md)
 
@@ -57,7 +57,7 @@
 
               - [Setting Up the Hi3861 Development Board Environment](quick-start/quickstart-lite-steps-hi3861-setting.md)
 
-              - [Writing a Hello World Program](quick-start/quickstart-lite-steps-hi3861-application-framework.md)
+              - [Writing a Hello World Program](quick-start/quickstart-lite-steps-hi3861-helloworld.md)
 
               - [Building](quick-start/quickstart-lite-steps-hi3861-building.md)
 
@@ -73,7 +73,7 @@
 
               - [Setting Up the Hi3516 Development Board Environment](quick-start/quickstart-lite-steps-hi3516-setting.md)
 
-              - [Writing a Hello World Program](quick-start/quickstart-lite-steps-hi3516-application-framework.md)
+              - [Writing a Hello World Program](quick-start/quickstart-lite-steps-hi3516-helloworld.md)
 
               - [Building](quick-start/quickstart-lite-steps-hi3516-building.md)
 
@@ -109,7 +109,7 @@
 
           - [Obtaining Source Code](quick-start/quickstart-ide-standard-sourcecode-acquire.md)
 
-      - [Creating a Source Code Project](quick-start/quickstart-ide-standard-create-project.md)
+      - [Importing a Source Code Project](quick-start/quickstart-ide-standard-create-project.md)
 
       - Running a Hello World Program
 
@@ -723,28 +723,24 @@
 
     - Peripheral Driver Usage
 
+      - [Audio](driver/driver-peripherals-audio-des.md)
+      - [Camera](driver/driver-peripherals-camera-des.md)
+      - [Face_auth](driver/driver-peripherals-face_auth-des.md)
       - [LCD](driver/driver-peripherals-lcd-des.md)
-
-      - [Touchscreen](driver/driver-peripherals-touch-des.md)
-
+      - [Light](driver/driver-peripherals-light-des.md)
+      - [Pin_auth](driver/driver-peripherals-pinauth-des.md)
       - [Sensor](driver/driver-peripherals-sensor-des.md)
-
-      - [WLAN](driver/driver-peripherals-external-des.md)
-
-      - [Audio](driver/driver-peripherals-audio-des.md)
-
+      - [Touchscreen](driver/driver-peripherals-touch-des.md)
       - [USB](driver/driver-peripherals-usb-des.md)
-
-      - [Camera](driver/driver-peripherals-camera-des.md)
-
+      - [User_auth](driver/driver-peripherals-user-auth-des.md)
       - [Vibrator](driver/driver-peripherals-vibrator-des.md)
-
-      - [Light](driver/driver-peripherals-light-des.md)
+      - [WLAN](driver/driver-peripherals-external-des.md)
   - Compilation and Building
     - [Building Mini and Small Systems](subsystems/subsys-build-mini-lite.md)
     - [Building the Standard System](subsystems/subsys-build-standard-large.md)
     - [Build System Coding Specifications and Best Practices](subsystems/subsys-build-gn-coding-style-and-best-practice.md)
     - [Building the Kconfig Visual Configuration](subsystems/subsys-build-gn-kconfig-visual-config-guide.md)
+    - [HAP Build Guide](subsystems/subsys-build-gn-hap-compilation-guide.md)
   - [Distributed Remote Startup](subsystems/subsys-remote-start.md)
   - Graphics
     - [Graphics Overview](subsystems/subsys-graphics-overview.md)