update docs

Signed-off-by: Nge-yafang <geyafang@huawei.com>

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

 # Basics
 
+-   Getting Started
+    -   [Preparations](start-overview.md)
+    -   [Getting Started with eTS](start-with-ets.md)
+    -   [Getting Started with JavaScript in the Traditional Coding Approach](start-with-js.md)
+    -   [Getting Started with JavaScript in the Low-Code Approach](start-with-js-low-code.md)
+
 -   Development Fundamentals
     -   [Directory Structure](package-structure.md)
     -   [Resource File](basic-resource-file-categories.md)

en/application-dev/quick-start/start-overview.md

+# Preparations
+
+This document is intended for novices at developing OpenHarmony applications. It will introduce you to the OpenHarmony project directory structure and application development process, by walking you through a stripped-down, real-world example – building two pages and implementing redirection between pages. The following figure shows how the pages look on the DevEco Studio Previewer.
+
+
+![en-us_image_0000001261809595](figures/en-us_image_0000001261809595.png)
+
+
+Before you begin, there are some basic concepts that will help you better understand OpenHarmony: UI framework and ability.
+
+
+## Basic Concepts
+
+
+### UI Framework
+
+OpenHarmony provides a UI development framework, known as ArkUI. ArkUI provides capabilities you may need for application UI development, including a wide array of components, layout calculation, animation, UI interaction, and drawing capabilities.
+
+ArkUI comes with two development paradigms: JavaScript-based web-like development paradigm (web-like development paradigm for short) and TypeScript-based declarative development paradigm (declarative development paradigm for short). You can choose whichever development paradigm that aligns with your practice.
+
+| **Development Paradigm** | **Language** | **UI Update Mode** | **Applicable To** | **Intended Audience** |
+| -------- | -------- | -------- | -------- | -------- |
+| Web-like development paradigm | JavaScript | Data-driven | Applications and service widgets with simple UIs | Frontend web developers |
+| Declarative development paradigm | Extended TypeScript (eTS) | Data-driven | Applications involving technological sophistication and teamwork | Mobile application and system application developers |
+
+For DevEco Studio V2.2 Beta1 and later versions, both the traditional coding mode and the low-code mode are supported when the JS language is used for development. On the OpenHarmony low-code development pages, you can design your app UI in an efficient, intuitive manner, with a wide array of UI editing features complying with [JS Development Specifications](../reference/apis).
+
+
+### Ability
+
+An ability is an abstraction of a capability that an application can provide. The **Ability** class is an essential component to OpenHarmony applications. An application may provide various capabilities, and so it can have multiple abilities. These abilities can be deployed together or independently from each other.
+
+Abilities are classified into two types: [Feature Ability (FA)](../../glossary.md#f) and [Particle Ability (PA)](../../glossary.md#p). Each type has their respective templates for different capabilities. FAs support only the Page template (also called the [Page ability](../ability/fa-pageability.md)), which is used to provide the capability of interacting with users. A Page ability consists of one or more pages. The figure below shows the relationship between a Page ability and pages.
+
+![en-us_image_0000001215206886](figures/en-us_image_0000001215206886.png)
+
+This document provides a Page ability instance with two pages. For more information about ability development, see [Ability Development](../ability/ability-brief.md).
+
+
+## Tool Preparation
+
+1. Install the latest version of [DevEco Studio](https://developer.harmonyos.com/cn/develop/deveco-studio#download_beta).
+
+2. Install DevEco Studio and configure the development environment. For details, see [Configuring the OpenHarmony SDK](https://developer.harmonyos.com/en/docs/documentation/doc-guides/ohos-setting-up-environment-0000001263160443).
+
+When you are done, follow the instructions in [Getting Started with eTS](start-with-ets.md),[Getting Started with JavaScript in the Traditional Coding Approach](start-with-js.md), and [Getting Started with JavaScript in the Low-Code Approach](start-with-js-low-code.md).

en/application-dev/quick-start/start-with-ets.md

+# Getting Started with eTS
+
+> ![icon-note.gif](public_sys-resources/icon-note.gif) **Note：**
+> To use eTS, your DevEco Studio must be V3.0.0.601 Beta1 or later.
+> 
+> For best possible results, use [DevEco Studio V3.0.0.900 Beta3](https://developer.harmonyos.com/cn/develop/deveco-studio#download_beta) for your development.
+
+
+## Creating an eTS Project
+
+1. Open DevEco Studio, choose **File** > **New** > **Create Project**, select **Empty Ability**, and click **Next**.
+   ![en-us_image_0000001223556342](figures/en-us_image_0000001223556342.png)
+
+2. On the project configuration page, set **UI Syntax** to **eTS** and retain the default values for other parameters.
+   ![en-us_image_0000001223716826](figures/en-us_image_0000001223716826.png)
+
+3. Click **Finish**. DevEco Studio will automatically generate the sample code and resources that match your project type. Wait until the project is created.
+
+
+## eTS Project Files
+
+- **entry** : OpenHarmony project module, which can be built into an ability package (HAP).
+  - **src > main > ets** : a collection of eTS source code.
+  - **src > main > ets > MainAbility** : entry to your application/service.
+  - **src > main > ets > MainAbility > pages** : pages contained in **MainAbility**.
+  - **src > main > ets > MainAbility > app.ets** : ability lifecycle file.
+  - **src > main > resources** : a collection of resource files used by your application/service, such as graphics, multimedia, character strings, and layout files.
+  - **src > main > config.json** : module configuration file. This file describes the global configuration information of the application/service, the device-specific configuration information, and the configuration information of the HAP file.
+  - **build-profile.json5** : module information and build configuration options, including **buildOption target**.
+  - **hvigorfile.js** : module-level compilation and build task script. You can customize related tasks and code implementation.
+- **build-profile.json5** : application-level configuration information, including the signature and product configuration.
+- **hvigorfile.js** : application-level compilation and build task script.
+
+
+## Building the First Page
+
+1. Use the **Text** component.
+   After the project synchronization is complete, choose **entry** > **src** > **main** > **ets** > **MainAbility** > **pages** in the **Project** window and open the **index.ets** file. You can see that the file contains a **<Text>** component. The sample code in the **index.ets** file is shown below:
+
+   
+   ```
+   @Entry
+   @Component
+   struct Index {
+     @State message: string = 'Hello World'
+   
+     build() {
+       Row() {
+         Column() {
+           Text(this.message)
+             .fontSize(50)
+             .fontWeight(FontWeight.Bold)
+         }
+         .width('100%')
+       }
+       .height('100%')
+     }
+   }
+   ```
+
+2. Add a **<Button>** component.
+   On the default page, add a **<Button>** component to accept user clicks and implement redirection to another page. The sample code in the **index.ets** file is shown below:
+
+   
+   ```
+   @Entry
+   @Component
+   struct Index {
+     @State message: string = 'Hello World'
+   
+     build() {
+       Row() {
+         Column() {
+           Text(this.message)
+             .fontSize(50)
+             .fontWeight(FontWeight.Bold)
+           // Add a button to accept user clicks.
+           Button() {
+             Text('Next')
+               .fontSize(30)
+               .fontWeight(FontWeight.Bold)
+           }
+           .type(ButtonType.Capsule)
+           .margin({
+             top: 20
+           })
+           .backgroundColor('#0D9FFB')
+           .width('40%')
+           .height('5%')
+         }
+         .width('100%')
+       }
+       .height('100%')
+     }
+   }
+   ```
+
+3. On the toolbar in the upper right corner of the editing window, click **Previewer** to open the Previewer. Below is how the first page looks on the Previewer.
+   
+   ![en-us_image_0000001216239356](figures/en-us_image_0000001216239356.png)
+
+
+## Building the Second Page
+
+1. Create the second page.
+   In the **Project** window, choose **entry** > **src** > **main** > **ets** > **MainAbility**, right-click the **pages** folder, choose **New** > **Page**, name the page **second**, and click **Finish**. Below is the structure of the **pages** folder:
+
+   ![en-us_image_0000001223397122](figures/en-us_image_0000001223397122.png)
+
+2. Add **<Text>** and **<Button>** components.
+   Add **<Text>** and **<Button>** components and set their styles, as you do for the first page. The sample code in the **second.ets** file is shown below:
+
+   
+   ```
+   @Entry
+   @Component
+   struct Second {
+     @State message: string = 'Hi there'
+   
+     build() {
+       Row() {
+         Column() {
+           Text(this.message)
+             .fontSize(50)
+             .fontWeight(FontWeight.Bold)
+           Button() {
+             Text('Back')
+               .fontSize(25)
+               .fontWeight(FontWeight.Bold)
+           }
+           .type(ButtonType.Capsule)
+           .margin({
+             top: 20
+           })
+           .backgroundColor('#0D9FFB')
+           .width('40%')
+           .height('5%')
+         }
+         .width('100%')
+       }
+       .height('100%')
+     }
+   }
+   ```
+
+
+## Implementing Page Redirection
+
+You can implement page redirection through the page router, which finds the target page based on the page URI. Import the **router** module and then perform the steps below:
+
+1. Implement redirection from the first page to the second page.
+   In the **index.ets** file of the first page, bind the **onClick** event to the **Next** button so that clicking the button redirects the user to the second page. The sample code in the **index.ets** file is shown below:
+
+   
+   ```
+   import router from '@system.router';
+   
+   @Entry
+   @Component
+   struct Index {
+     @State message: string = 'Hello World'
+   
+     build() {
+       Row() {
+         Column() {
+           Text(this.message)
+             .fontSize(50)
+             .fontWeight(FontWeight.Bold)
+           // Add a button to accept user clicks.
+           Button() {
+             Text('Next')
+               .fontSize(30)
+               .fontWeight(FontWeight.Bold)
+           }
+           .type(ButtonType.Capsule)
+           .margin({
+             top: 20
+           })
+           .backgroundColor('#0D9FFB')
+           .width('40%')
+           .height('5%')
+           // Bind the onClick event to the Next button so that clicking the button redirects the user to the second page.
+           .onClick(() => {
+             router.push({ uri: 'pages/second' })
+           })
+         }
+         .width('100%')
+       }
+       .height('100%')
+     }
+   }
+   ```
+
+2. Implement redirection from the second page to the first page.
+   In the **second.ets** file of the second page, bind the **onClick** event to the **Back** button so that clicking the button redirects the user back to the first page. The sample code in the **second.ets** file is shown below:
+
+   
+   ```
+   import router from '@system.router';
+   
+   @Entry
+   @Component
+   struct Second {
+     @State message: string = 'Hi there'
+   
+     build() {
+       Row() {
+         Column() {
+           Text(this.message)
+             .fontSize(50)
+             .fontWeight(FontWeight.Bold)
+           Button() {
+             Text('Back')
+               .fontSize(25)
+               .fontWeight(FontWeight.Bold)
+           }
+           .type(ButtonType.Capsule)
+           .margin({
+             top: 20
+           })
+           .backgroundColor('#0D9FFB')
+           .width('40%')
+           .height('5%')
+           // Bind the onClick event to the Back button so that clicking the button redirects the user back to the first page.
+           .onClick(() => {
+             router.back()
+           })
+         }
+         .width('100%')
+       }
+       .height('100%')
+     }
+   }
+   ```
+
+3. Open the **index.ets** file and click ![en-us_image_0000001262219043](figures/en-us_image_0000001262219043.png) in the Previewer to refresh the file. The figure below shows the effect.
+   ![en-us_image_0000001260684127](figures/en-us_image_0000001260684127.png)
+
+
+## Running the Application on a Real Device
+
+1. Connect the development board running the OpenHarmony standard system to the computer.
+
+2. Choose **File** > **Project Structure** > **Project** > **Signing Configs**, select **Automatically generate signing**, wait until the automatic signing is complete, and click **OK**, as shown below.
+   ![en-us_image_0000001268077317](figures/en-us_image_0000001268077317.png)
+
+3. On the toolbar in the upper right corner of the editing window, click ![en-us_image_0000001262206247](figures/en-us_image_0000001262206247.png). The display effect is shown in the figure below.
+   ![en-us_image_0000001217526428](figures/en-us_image_0000001217526428.png)
+
+Congratulations! You have finished developing your OpenHarmony application in eTS. To learn more about OpenHarmony, see [OpenHarmony Overview](../application-dev-guide.md)

en/application-dev/quick-start/start-with-js-low-code.md

+# Getting Started with JavaScript in the Low-Code Approach
+
+> ![icon-note.gif](public_sys-resources/icon-note.gif) **Note：**
+> This feature will be available in DevEco Studio V2.2 Beta1 and later versions.
+> 
+> For best possible results, use [DevEco Studio V3.0.0.900 Beta3](https://developer.harmonyos.com/cn/develop/deveco-studio#download_beta) for your development.
+
+
+On the OpenHarmony low-code development pages, you can design your app UI in an efficient, intuitive manner, with a wide array of UI editing features complying with [JS Development Specifications](../reference/apis).
+
+
+You can develop applications or services in the low-code approach using either of the following methods:
+
+
+- Create a project that supports low-code development. This method is used as an example in this topic.
+
+- In an existing project, create a Visual file for development.
+
+
+## Creating a Project That Supports Low-Code Development
+
+> ![icon-note.gif](public_sys-resources/icon-note.gif) **Note：**
+> This feature is available in DevEco Studio 3.0 Beta2 and later versions and works with compileSdkVersion 7 or later.
+
+1. Open DevEco Studio, choose **File** > **New** > **Create Project**, select **Empty Ability**, and click **Next**.
+   ![en-us_image_0000001268198893](figures/en-us_image_0000001268198893.png)
+2. Go to the project configuration page, select **Enable Super Visual**, set **UI Syntax** to **JS**, and retain the default values for other parameters.
+
+  ![en-us_image_0000001223717294](figures/en-us_image_0000001223717294.png)
+
+3. Click **Finish**. DevEco Studio will automatically generate the sample code and resources that match your project type. Wait until the project is created.
+
+
+## Low-code Project Files
+
+After the project synchronization is complete, a low-code directory structure is automatically generated in the project, as shown below.
+
+![en-us_image_0000001223558810](figures/en-us_image_0000001223558810.png)
+
+- **entry > src > main > js > MainAbility > pages > index > index.js** : defines logical relationships, such as data and events, used on low-code pages. For details, see [JavaScript](../ui/js-framework-syntax-js.md). If multiple low-code development pages are created, a page folder and the corresponding **.js** file will be created for each of these pages.
+  > ![icon-note.gif](public_sys-resources/icon-note.gif) **Note：**
+  > To avoid build errors when using the low-code development page, make sure the directory where the corresponding **.js** file is located does not contain **.hml** or **.css** files. For example, in the preceding example, no **.hml** or **.css** file is allowed in **js** > **MainAbility** > **pages** > **index**.
+- **entry > src > main > supervisual > MainAbility > pages > index > index.visual** : stores the data model of the low-code development page. You can double-click the file to open the low-code development page. If multiple low-code development pages are created, a page folder and the corresponding **.visual** file will be created for each of these pages.
+
+
+## Building the First Page
+
+After the project synchronization is complete, the default first page contains the **Div** and **Text** (**Hello World**) components. To better understand low-code development, we'll delete these template components from the canvas and set the page from scratch.
+
+Add **Div**, **Text**, and **Button** components to the first page.
+
+1. Delete the existing template components from the canvas.<a name= delete_origin_content></a>
+   Open the index.visual file, right-click the existing template components on the canvas, and choose **Delete** from the shortcut menu to delete them. Below is an illustration of the operations.
+
+   ![en-us_image_0000001216600980](figures/en-us_image_0000001216600980.gif)
+
+2. Add a **Div** component and set its styles and attributes.<a name = add_container></a>
+   Drag the **Div** component from the **UI Control** area to the canvas. In the **Attributes &amp; Styles** area on the right, click ![en-us_image_0000001260226691](figures/en-us_image_0000001260226691.png)**General** and set **Height** to **100%** so that the component fills the entire screen. Click ![en-us_image_0000001215226858](figures/en-us_image_0000001215226858.png)**Flex**, set **FlexDirection** to **column** so that the main axis of the component is vertical, and set both **JustifyContent** and **AlignItems** to **center** so that the child components of the **Div** component are centered along the main axis and cross axis. Below is an illustration of the operations.
+
+   ![en-us_image_0000001216448880](figures/en-us_image_0000001216448880.gif)
+
+3. Add a **Text** component.
+   Drag the **Text** component from the **UI Control** area to the center area of the **Div** component. In the **Attributes &amp; Styles** area, click ![en-us_image_0000001215066868](figures/en-us_image_0000001215066868.png)**Properties** and set **Content** of the **Text** component to **Hello World**. Click ![en-us_image_0000001215386842](figures/en-us_image_0000001215386842.png)**Feature**, and set **FontSize** to **60px** and **TextAlign** to **center**. Then, select the **Text** component on the canvas and drag its corners to fully display the text. Below is an illustration of the operations.
+
+   ![en-us_image_0000001216446670](figures/en-us_image_0000001216446670.gif)
+
+4. Add a **Button** component.
+   Drag the **Button** component from the **UI Control** area to a position under the **Text** component on the canvas. In the **Attributes &amp; Styles** area on the right, click ![en-us_image_0000001260106745](figures/en-us_image_0000001260106745.png)**Properties** and set **Value** of the **Button** component to **Next**. Click ![en-us_image_0000001259866741](figures/en-us_image_0000001259866741.png)**Feature** and set **FontSize** to **40px**. Then, select the **Button** component on the canvas and drag its corners to fully display the text. Below is an illustration of the operations.
+
+   ![en-us_image_0000001260928361](figures/en-us_image_0000001260928361.gif)
+
+5. On the toolbar in the upper right corner of the editing window, click **Previewer** to open the Previewer. Below is how the first page looks on the Previewer.
+   ![en-us_image_0000001216288558](figures/en-us_image_0000001216288558.png)
+
+
+## Building the Second Page
+
+1. Create the second page.
+   In the **Project** window, choose **entry** &gt; **src** &gt; **main** &gt; **js** &gt; **MainAbility**, right-click the **pages** folder, choose **New** &gt; **Visual**, name the page **second**, and click **Finish**. Below is the structure of the **pages** folder:
+
+   ![en-us_image_0000001223882030](figures/en-us_image_0000001223882030.png)
+
+2. [Delete the existing template components from the canvas.](#delete_origin_content)
+
+3. [Add a Div component and set its styles and attributes.](#add_container)
+
+4. Add a **Text** component.
+   Drag the **Text** component from the **UI Control** area to the center area of the **Div** component. In the **Attributes &amp; Styles** area, click ![en-us_image_0000001260227453](figures/en-us_image_0000001260227453.png)**Properties** and set **Content** of the **Text** component to **Hi there**. Click ![en-us_image_0000001260107497](figures/en-us_image_0000001260107497.png)**Feature**, and set **FontSize** to **60px** and **TextAlign** to **center**. Then, select the **Text** component on the canvas and drag its corners to fully display the text. Below is an illustration of the operations.
+
+   ![en-us_image_0000001216614132](figures/en-us_image_0000001216614132.gif)
+
+5. Add a **Button** component.
+   Drag the **Button** component from the **UI Control** area to a position under the **Text** component on the canvas. In the **Attributes &amp; Styles** area on the right, click ![en-us_image_0000001215227618](figures/en-us_image_0000001215227618.png)**Properties** and set **Value** of the **Button** component to **Back**. Click ![en-us_image_0000001259987441](figures/en-us_image_0000001259987441.png)**Feature** and set **FontSize** to **40px**. Then, select the **Button** component on the canvas and drag its corners to fully display the text. Below is an illustration of the operations.
+
+   ![en-us_image_0000001261017331](figures/en-us_image_0000001261017331.gif)
+
+
+## Implementing Page Redirection
+
+You can implement page redirection through the [page router](../ui/ui-js-building-ui-routes.md), which finds the target page based on the page URI. Import the **router** module and then perform the steps below:
+
+1. Implement redirection from the first page to the second page.
+     In the files of the first page, bind the **onclick** method to the button so that clicking the button redirects the user to the second page. This operation needs to be completed in both .js and .visual files.
+   - In the **index.js** file:
+     
+     ```
+     import router from '@system.router';  
+     
+     export default {     
+         onclick() {         
+             router.push({             
+                 uri:'pages/second/second', // Specify the page to be redirected to.
+             })     
+         } 
+     }
+     ```
+   
+   - In the index.visual file, select the **Button** component on the canvas. In the **Attributes &amp; Styles** area, click ![en-us_image_0000001215388136](figures/en-us_image_0000001215388136.png)**Events** and set **Click** to **onclick**.
+     
+     ![en-us_image_0000001223722586](figures/en-us_image_0000001223722586.png)
+
+2. Implement redirection from the second page to the first page.
+   In the files of the second page, bind the **back** method to the **Back** button so that clicking the button redirects the user back to the first page.
+
+   This operation needs to be completed in both .js and .visual files.
+
+   - In the **second.js** file:
+     
+      ```
+      import router from '@system.router';  
+      
+      export default {     
+          back() {         
+              router.back()     
+          } 
+      }
+      ```
+   - In the second.visual file, select the **Button** component on the canvas. In the **Attributes &amp; Styles** area, click ![en-us_image_0000001215388262](figures/en-us_image_0000001215388262.png)**Events** and set **Click** to **back**.
+
+   ![en-us_image_0000001268082945](figures/en-us_image_0000001268082945.png)
+
+3. Open the **index.visual** or **index.js** file and click ![en-us_image_0000001261979271](figures/en-us_image_0000001261979271.png) in the Previewer to refresh the file. The figure below shows the effect.
+   ![en-us_image_0000001261142799](figures/en-us_image_0000001261142799.png)
+
+
+## Running the Application on a Real Device
+
+1. Connect the development board running the OpenHarmony standard system to the computer.
+
+2. Choose **File** &gt; **Project Structure** &gt; **Project** &gt; **Signing Configs**, select **Automatically generate signing**, wait until the automatic signing is complete, and click **OK**, as shown below.
+   ![en-us_image_0000001268283201](figures/en-us_image_0000001268283201.png)
+
+3. On the toolbar in the upper right corner of the editing window, click ![en-us_image_0000001262207811](figures/en-us_image_0000001262207811.png). The display effect is shown in the figure below.
+   ![en-us_image_0000001262127855](figures/en-us_image_0000001262127855.png)
+
+Congratulations! You have finished developing your OpenHarmony app in JavaScript in the low-code approach. To learn more about OpenHarmony, see [OpenHarmony Overview](../application-dev-guide.md)

en/application-dev/quick-start/start-with-js.md

+# Getting Started with JavaScript in the Traditional Coding Approach
+
+> ![icon-note.gif](public_sys-resources/icon-note.gif) **Note：**
+> For best possible results, use [DevEco Studio V3.0.0.900 Beta3](https://developer.harmonyos.com/cn/develop/deveco-studio#download_beta) for your development.
+
+
+## Creating a JavaScript Project
+
+1. Open DevEco Studio, choose **File** > **New** > **Create Project**, select **Empty Ability**, and click **Next**.
+   ![en-us_image_0000001223558814](figures/en-us_image_0000001223558814.png)
+
+2. On the project configuration page, set **UI Syntax** to **JS** and retain the default values for other parameters.
+   ![en-us_image_0000001223877162](figures/en-us_image_0000001223877162.png)
+
+3. Click **Finish**. DevEco Studio will automatically generate the sample code and resources that match your project type. Wait until the project is created.
+
+
+## JavaScript Project Files
+
+- **entry** : OpenHarmony project module, which can be built into an ability package (HAP).
+  - **src > main > js** : a collection of JS source code.
+  - **src > main > js > MainAbility** : entry to your application/service.
+  - **src > main > js > MainAbility > i18n** : resources in different languages, for example, UI strings and image paths.
+  - **src > main > js > MainAbility > pages** : pages contained in **MainAbility**.
+  - **src > main > js > MainAbility > app.js** : ability lifecycle file.
+  - **src > main > resources** : a collection of resource files used by your application/service, such as graphics, multimedia, character strings, and layout files.
+  - **src > main > config.json** : module configuration file. This file describes the global configuration information of the application/service, the device-specific configuration information, and the configuration information of the HAP file.
+  - **build-profile.json5** : module information and build configuration options, including **buildOption target**.
+  - **hvigorfile.js** : module-level compilation and build task script. You can customize related tasks and code implementation.
+- **build-profile.json5** : application-level configuration information, including the signature and product configuration.
+- **hvigorfile.js** : application-level compilation and build task script.
+
+
+## Building the First Page
+
+1. Use the **Text** component.
+   After the project synchronization is complete, choose **entry** > **src** > **main** > **js** > **MainAbility** > **pages** > **index** in the **Project** window and open the **index.hml** file. You can see that the file contains a **<Text>** component. The sample code in the **index.hml** file is shown below:
+
+   
+   ```
+   <div class="container">
+       <text class="title">
+           Hello World
+       </text>
+   </div>
+   ```
+
+2. Add a button and bind the **onclick** method to this button.
+   On the default page, add an **&lt;input&gt;** component of the button type to accept user clicks and implement redirection to another page. The sample code in the **index.hml** file is shown below:
+
+   
+   ```
+   <div class="container">
+       <text class="title">
+           Hello World
+       </text>
+   
+   <!-- Add a button, set its value to Next, and bind the onclick method to the button. -->
+       <input class="btn" type="button" value="Next" onclick="onclick"></input>
+   </div>
+   ```
+
+3. Set the page style in the **index.css** file.
+   From the **Project** window, choose **entry** &gt; **src** &gt; **main** &gt; **js** &gt; **MainAbility** &gt; **pages** &gt; **index**, open the **index.css** file, and set the page styles, such as the width, height, font size, and spacing. The sample code in the **index.css** file is shown below:
+
+   
+   ```
+   .container {
+       display: flex;
+       flex-direction: column;
+       justify-content: center;
+       align-items: center;
+       left: 0px;
+       top: 0px;
+       width: 100%;
+       height: 100%;
+   }
+   
+   .title {
+       font-size: 100px;
+       font-weight: bold;
+       text-align: center;
+       width: 100%;
+       margin: 10px;
+   }
+   
+   .btn {
+       font-size: 60px;
+       font-weight: bold;
+       text-align: center;
+       width: 40%;
+       height: 5%;
+       margin-top: 20px;
+   }
+   ```
+
+4. On the toolbar in the upper right corner of the editing window, click **Previewer** to open the Previewer. Below is how the first page looks on the Previewer.
+   
+   ![en-us_image_0000001216084724](figures/en-us_image_0000001216084724.png)
+
+
+## Building the Second Page
+
+1. Create the second page.
+   In the **Project** window, choose **entry** &gt; **src** &gt; **main** &gt; **js** &gt; **MainAbility**, right-click the **pages** folder, choose **New** &gt; **Page**, name the page **second**, and click **Finish**. Below is the structure of the **second** folder:
+
+   ![en-us_image_0000001223877210](figures/en-us_image_0000001223877210.png)
+
+2. Add **&lt;Text&gt;** and **&lt;Button&gt;** components.
+   Add **&lt;Text&gt;** and **&lt;Button&gt;** components and set their styles, as you do for the first page. The sample code in the **second.hml** file is shown below:
+
+   
+   ```
+   <div class="container">
+       <text class="title">
+           Hi there
+       </text>
+   
+   <!-- Add a button, set the value to Back, and bind the back method to the button.-->
+       <input class="btn" type="button" value="Back" onclick="back"></input>
+   </div>
+   ```
+
+3. Set the page style in the **second.css** file. The sample code in the **second.css** file is shown below:
+   
+   ```
+   .container {
+       display: flex;
+       flex-direction: column;
+       justify-content: center;
+       align-items: center;
+       left: 0px;
+       top: 0px;
+       width: 100%;
+       height: 100%;
+   }
+   
+   .title {
+       font-size: 100px;
+       font-weight: bold;
+       text-align: center;
+       width: 100%;
+       margin: 10px;
+   }
+   
+   .btn {
+       font-size: 60px;
+       font-weight: bold;
+       text-align: center;
+       width: 40%;
+       height: 5%;
+       margin-top: 20px;
+   }
+   ```
+
+
+## Implementing Page Redirection
+
+You can implement page redirection through the [page router](../ui/ui-js-building-ui-routes.md), which finds the target page based on the page URI. Import the **router** module and then perform the steps below:
+
+1. Implement redirection from the first page to the second page.
+   In the **index.js** file of the first page, bind the **onclick** method to the button so that clicking the button redirects the user to the second page. The sample code in the **index.js** file is shown below:
+
+   
+   ```
+   import router from '@system.router';
+   
+   export default {
+       onclick: function () {
+           router.push({
+               uri: "pages/second/second"
+           })
+       }
+   }
+   ```
+
+2. Implement redirection from the second page to the first page.
+   In the **second.ets** file of the second page, bind the **back** method to the **Back** button so that clicking the button redirects the user back to the first page. The sample code in the **second.js** file is shown below:
+
+   
+   ```
+   import router from '@system.router';
+   
+   export default {
+       back: function () {
+           router.back()
+       }
+   }
+   ```
+
+3. Open any file in the **index** folder and click ![en-us_image_0000001262339067](figures/en-us_image_0000001262339067.png) in the Previewer to refresh the file. The figure below shows the effect.
+   ![en-us_image_0000001216269940](figures/en-us_image_0000001216269940.png)
+
+
+## Running the Application on a Real Device
+
+1. Connect the development board running the OpenHarmony standard system to the computer.
+
+2. Choose **File** &gt; **Project Structure** &gt; **Project** &gt; **Signing Configs**, select **Automatically generate signing**, wait until the automatic signing is complete, and click **OK**, as shown below.
+   ![en-us_image_0000001223557290](figures/en-us_image_0000001223557290.png)
+
+3. On the toolbar in the upper right corner of the editing window, click ![en-us_image_0000001217047316](figures/en-us_image_0000001217047316.png). The display effect is shown in the figure below.
+   ![en-us_image_0000001217527892](figures/en-us_image_0000001217527892.png)
+
+Congratulations! You have finished developing your OpenHarmony application in JavaScript in the traditional coding approach. To learn more about OpenHarmony, see [OpenHarmony Overview](../application-dev-guide.md)

en/application-dev/reference/apis/Readme-EN.md

@@ -24,7 +24,6 @@
     -   [User Authentication](js-apis-useriam-userauth.md)
     -   [Access Control](js-apis-abilityAccessCtrl.md)
 - Data Management
-    -   [Lightweight Storage<sup>9+</sup>](js-apis-data-preferences.md)
     -   [Lightweight Storage](js-apis-data-storage.md)
     -   [Distributed Data Management](js-apis-distributed-data.md)
     -   [Relational Database](js-apis-data-rdb.md)
@@ -80,6 +79,7 @@
     -   [Console Logs](js-apis-basic-features-logs.md)
     -   [Page Routing](js-apis-basic-features-routes.md)
     -   [Timer](js-apis-basic-features-timer.md)
+    -   [Screen Lock Management](js-apis-screen-lock.md)
     -   [Setting the System Time](js-apis-system-time.md)
     -   [Wallpaper](js-apis-wallpaper.md)
     -   [Pasteboard](js-apis-pasteboard.md)

en/application-dev/reference/apis/js-apis-data-storage.md

@@ -4,7 +4,7 @@ Lightweight storage provides applications with data processing capability and al
 
 
 > ![icon-note.gif](public_sys-resources/icon-note.gif) **NOTE**<br/>
-> 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. <br/>The APIs of this module are no longer maintained since API Version 9. You are advised to use [@ohos.data.preferences](js-apis-data-preferences.md).
+> 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. 
 
 
 ## Modules to Import
@@ -45,7 +45,7 @@ Reads a file and loads the data to the **Storage** instance in synchronous mode.
   ```
   import dataStorage from '@ohos.data.storage'
   import featureAbility from '@ohos.ability.featureAbility'
-
+  
   var context = featureAbility.getContext()
   var path = await context.getFilesDir()
   let storage = dataStorage.getStorageSync(path + '/mystore')
@@ -72,7 +72,7 @@ Reads a file and loads the data to the **Storage** instance. This method uses an
   ```
   import dataStorage from '@ohos.data.storage'
   import featureAbility from '@ohos.ability.featureAbility'
-
+  
   var context = featureAbility.getContext()
   var path = await context.getFilesDir()
   dataStorage.getStorage(path + '/mystore', function (err, storage) {
@@ -108,7 +108,7 @@ Reads a file and loads the data to the **Storage** instance. This method uses a
   ```
   import dataStorage from '@ohos.data.storage'
   import featureAbility from '@ohos.ability.featureAbility'
-
+  
   var context = featureAbility.getContext()
   var path = await context.getFilesDir()
   let promisegetSt = dataStorage.getStorage(path + '/mystore')

en/application-dev/reference/apis/js-apis-screen-lock.md

+# Screen Lock Management
+
+
+> ![icon-note.gif](public_sys-resources/icon-note.gif) **Note：**
+> The initial APIs of this module are supported since API version 7. Newly added APIs will be marked with a superscript to indicate their earliest API version.
+
+
+## Modules to Import
+
+
+```
+import screenlock from '@ohos.screenLock';
+```
+
+
+## screenlock.isScreenLocked
+
+isScreenLocked(callback: AsyncCallback<boolean>): void
+
+Checks whether the screen is locked. This method uses an asynchronous callback to return the result.
+
+**System capability**: SystemCapability.MiscServices.ScreenLock
+
+- Parameters
+    | Name | Type | Mandatory | Description |
+  | -------- | -------- | -------- | -------- |
+  | callback | AsyncCallback<boolean> | Yes | Callback used to return the result. If **true** is returned, the screen is locked. If **false** is returned, the screen is not locked. |
+
+- Example
+  
+  ```
+  screenlock.isScreenLocked((err, data)=>{      
+     if (err) {
+          console.error('isScreenLocked callback error -> ${JSON.stringify(err)}');
+          return;    
+     }
+     console.info('isScreenLocked callback success data -> ${JSON.stringify(data)}');
+  });
+  ```
+
+
+## screenlock.isScreenLocked
+
+isScreenLocked(): Promise<boolean>
+
+Checks whether the screen is locked. This method uses a promise to return the result.
+
+**System capability**: SystemCapability.MiscServices.ScreenLock
+
+- Return Values
+    | Type | Description |
+  | -------- | -------- |
+  | Promise<boolean> | Promise used to return the result. |
+
+- Example
+  
+  ```
+  screenlock.isScreenLocked().then((data) => {
+      console.log('isScreenLocked success: data -> ${JSON.stringify(data)}');
+  }).catch((err) => {
+      console.error('isScreenLocked fail, promise: err -> ${JSON.stringify(err)}');
+  });
+  ```
+
+
+## screenlock.isSecureMode
+
+isSecureMode(callback: AsyncCallback<boolean>): void
+
+
+Checks whether a device is in secure mode. This method uses an asynchronous callback to return the result.
+
+
+**System capability**: SystemCapability.MiscServices.ScreenLock
+
+
+- Parameters
+    | Name | Type | Mandatory | Description |
+  | -------- | -------- | -------- | -------- |
+  | callback | AsyncCallback<boolean> | Yes | Callback used to return the result. If **true** is returned, the device is in secure mode. If **false** is returned, the device is not in secure mode. |
+
+- Example
+  
+  ```
+  screenlock.isSecureMode((err, data)=>{      
+     if (err) {
+          console.error('isSecureMode callback error -> ${JSON.stringify(err)}');
+          return;    
+     }
+     console.info('isSecureMode callback success data -> ${JSON.stringify(err)}');
+  });
+  ```
+
+
+## screenlock.isSecureMode
+
+isSecureMode(): Promise<boolean>
+
+Checks whether a device is in secure mode. This method uses a promise to return the result.
+
+**System capability**: SystemCapability.MiscServices.ScreenLock
+
+- Return Values
+    | Type | Description |
+  | -------- | -------- |
+  | Promise<boolean> | Promise used to return the result. |
+
+- Example
+  
+  ```
+  screenlock.isSecureMode().then((data) => {
+      console.log('isSecureMode success: data->${JSON.stringify(data)}');
+  }).catch((err) => {
+      console.error('isSecureMode fail, promise: err->${JSON.stringify(err)}');
+  });
+  ```
+
+
+## screenlock.unlockScreen
+
+unlockScreen(callback: AsyncCallback<void>): void
+
+
+Unlocks the screen. This method uses an asynchronous callback to return the result.
+
+
+**System capability**: SystemCapability.MiscServices.ScreenLock
+
+
+- Parameters
+    | Name | Type | Mandatory | Description |
+  | -------- | -------- | -------- | -------- |
+  | callback | AsyncCallback<void> | Yes | Callback function. If the callback fails, an error message is returned. |
+
+- Example
+  
+  ```
+  screenlock.unlockScreen((err)=>{      
+     if (err) {
+          console.error('unlockScreen callback error -> ${JSON.stringify(err)}');
+          return;    
+     }
+     console.info('unlockScreen callback success');
+  });
+  ```
+
+
+## screenlock.unlockScreen
+
+unlockScreen(): Promise<void>
+
+Unlocks the screen. This method uses a promise to return the result.
+
+**System capability**: SystemCapability.MiscServices.ScreenLock
+
+- Return Values
+    | Type | Description |
+  | -------- | -------- |
+  | Promise<void> | Promise used to return the result. |
+
+- Example
+  
+  ```
+  screenlock.unlockScreen().then(() => {
+      console.log('unlockScreen success');
+  }).catch((err) => {
+      console.error('unlockScreen fail, promise: err->${JSON.stringify(err)}');
+  });
+  ```

zh-cn/application-dev/quick-start/start-overview.md

@@ -23,18 +23,18 @@ OpenHarmony提供了一套UI开发框架，即方舟开发框架（ArkUI框架
 | 类Web开发范式 | JS语言 | 数据驱动更新 | 界面较为简单的程序应用和卡片 | Web前端开发人员 |
 | 声明式开发范式 | 扩展的TS语言（eTS） | 数据驱动更新 | 复杂度较大、团队合作度较高的程序 | 移动系统应用开发人员、系统应用开发人员 |
 
-对于DevEco Studio V2.2 Beta1及更高版本，在使用JS语言开发时，除传统代码方式外，还支持使用低代码方式。OpenHarmony低代码开发方式具有丰富的UI界面编辑功能，遵循[JS开发规范](../references/apis)，通过可视化界面开发方式快速构建布局，可有效降低用户的上手成本并提升用户构建UI界面的效率。
+对于DevEco Studio V2.2 Beta1及更高版本，在使用JS语言开发时，除传统代码方式外，还支持使用低代码方式。OpenHarmony低代码开发方式具有丰富的UI界面编辑功能，遵循[JS开发规范](../reference/apis)，通过可视化界面开发方式快速构建布局，可有效降低用户的上手成本并提升用户构建UI界面的效率。
 
 
 ### Ability
 
-[Ability](../ability/ability-brief.md)是应用所具备能力的抽象，也是应用程序的重要组成部分。一个应用可以具备多种能力（即可以包含多个Ability）。OpenHarmony支持应用以Ability为单位进行部署。
+Ability是应用所具备能力的抽象，也是应用程序的重要组成部分。一个应用可以具备多种能力（即可以包含多个Ability）。OpenHarmony支持应用以Ability为单位进行部署。
 
 Ability可以分为[FA（Feature Ability）](../../glossary.md#f)和[PA（Particle Ability）](../../glossary.md#p)两种类型，每种类型为开发者提供了不同的模板，以便实现不同的业务功能。其中，FA支持[Page Ability](../ability/fa-pageability.md)模板，以提供与用户交互的能力。一个Page Ability可以含有一个或多个页面（即Page），Page Ability与Page的关系如下图所示：
 
 ![zh-cn_image_0000001215206886](figures/zh-cn_image_0000001215206886.png)
 
-快速入门提供了一个含有两个页面的Page Ability实例。更多Ability的开发内容及指导，请参见[Ability开发](../ability/Readme-CN.md)。
+快速入门提供了一个含有两个页面的Page Ability实例。更多Ability的开发内容及指导，请参见[Ability开发](../ability/ability-brief.md)。
 
 
 ## 工具准备

zh-cn/application-dev/quick-start/start-with-ets.md

@@ -20,24 +20,24 @@
 
 ## eTS工程项目文件
 
-- **entry**：OpenHarmony工程模块，编译构建生成一个Hap包。
-  - **src > main > ets**：用于存放ets源码。
-  - **src > main > ets > MainAbility**：应用/服务的入口。
-  - **src > main > ets > MainAbility > pages**：MainAbility包含的页面。
-  - **src > main > ets > MainAbility > app.ets**：承载Ability生命周期。
-  - **src > main > resources**：用于存放应用/服务所用到的资源文件，如图形、多媒体、字符串、布局文件等。
-  - **src > main > config.json**：模块配置文件。主要包含HAP包的配置信息、应用在具体设备上的配置信息以及应用的全局配置信息。
-  - **build-profile.json5**：模块的模块信息 、编译信息配置项，包括 buildOption target配置等。
-  - **hvigorfile.js**：模块级编译构建任务脚本，开发者可以自定义相关任务和代码实现。
+- **entry** ：OpenHarmony工程模块，编译构建生成一个Hap包。
+  - **src > main > ets** ：用于存放ets源码。
+  - **src > main > ets > MainAbility** ：应用/服务的入口。
+  - **src > main > ets > MainAbility > pages** ：MainAbility包含的页面。
+  - **src > main > ets > MainAbility > app.ets** ：承载Ability生命周期。
+  - **src > main > resources** ：用于存放应用/服务所用到的资源文件，如图形、多媒体、字符串、布局文件等。
+  - **src > main > config.json** ：模块配置文件。主要包含HAP包的配置信息、应用/服务在具体设备上的配置信息以及应用/服务的全局配置信息。
+  - **build-profile.json5** ：模块的模块信息 、编译信息配置项，包括 buildOption target配置等。
+  - **hvigorfile.js** ：模块级编译构建任务脚本，开发者可以自定义相关任务和代码实现。
 
-- **build-profile.json5**：应用级配置信息，包括签名、产品配置等。
+- **build-profile.json5** ：应用级配置信息，包括签名、产品配置等。
 
-- **hvigorfile.js**：应用级编译构建任务脚本。
+- **hvigorfile.js** ：应用级编译构建任务脚本。
 
 
 ## 构建第一个页面
 
-1. **文本组件。**
+1. **使用文本组件。**
    工程同步完成后，在“**Project**”窗口，点击“**entry > src > main > ets > MainAbility > pages**”，打开“**index.ets**”文件，可以看到页面由Text组件组成。“**index.ets**”文件的示例如下：
 
    
@@ -98,7 +98,8 @@
    }
    ```
 
-3. **在编辑窗口右上角的侧边工具栏，点击Previewer，打开预览器。**第一个页面效果如下图所示：
+3. **在编辑窗口右上角的侧边工具栏，点击Previewer，打开预览器。** 第一个页面效果如下图所示：
+
    ![zh-cn_image_0000001216239356](figures/zh-cn_image_0000001216239356.png)
 
 
@@ -235,7 +236,8 @@
    }
    ```
 
-3. **打开index.ets文件，点击预览器中的**![zh-cn_image_0000001262219043](figures/zh-cn_image_0000001262219043.png)**按钮进行刷新。**效果如下图所示：
+3. **打开index.ets文件，点击预览器中的** ![zh-cn_image_0000001262219043](figures/zh-cn_image_0000001262219043.png) **按钮进行刷新。** 效果如下图所示：
+
    ![zh-cn_image_0000001260684127](figures/zh-cn_image_0000001260684127.png)
 
 
@@ -247,6 +249,7 @@
    ![zh-cn_image_0000001268077317](figures/zh-cn_image_0000001268077317.png)
 
 3. 在编辑窗口右上角的工具栏，点击![zh-cn_image_0000001262206247](figures/zh-cn_image_0000001262206247.png)按钮运行。效果如下图所示：
+
    ![zh-cn_image_0000001217526428](figures/zh-cn_image_0000001217526428.png)
 
 恭喜您已经使用eTS语言开发完成了第一个OpenHarmony应用，快来[探索更多的OpenHarmony功能](../application-dev-guide.md)吧。

zh-cn/application-dev/quick-start/start-with-js-low-code.md

@@ -26,7 +26,7 @@ OpenHarmony低代码开发方式具有丰富的UI界面编辑功能，遵循[JS
 1. 打开**DevEco Studio**，点击**File** > **New > Create Project**，选择模板“**Empty Ability**”，点击**Next**进行下一步配置。
    ![zh-cn_image_0000001268198893](figures/zh-cn_image_0000001268198893.png)
 
-2. 进入配置工程界面，打开“**Enable Visual Enable**”开关**，UI Syntax**选择“**JS**”，其他参数保持默认设置即可。
+2. 进入配置工程界面，打开“**Enable Super Visual**”开关，**UI Syntax**选择“**JS**”，其他参数保持默认设置即可。
    ![zh-cn_image_0000001223717294](figures/zh-cn_image_0000001223717294.png)
 
 3. 点击**Finish**，工具会自动生成示例代码和相关资源，等待工程创建完成。
@@ -38,11 +38,12 @@ OpenHarmony低代码开发方式具有丰富的UI界面编辑功能，遵循[JS
 
 ![zh-cn_image_0000001223558810](figures/zh-cn_image_0000001223558810.png)
 
-- **entry > src > main > js > MainAbility > pages > index > index.js**：低代码页面的逻辑描述文件，定义了页面里所用到的所有的逻辑关系，比如数据、事件等，详情请参考[JS语法参考](../ui/js-framework-syntax-js.md)。如果创建了多个低代码页面，则pages目录下会生成多个页面文件夹及对应的js文件。
+- **entry > src > main > js > MainAbility > pages > index > index.js** ：低代码页面的逻辑描述文件，定义了页面里所用到的所有的逻辑关系，比如数据、事件等，详情请参考[JS语法参考](../ui/js-framework-syntax-js.md)。如果创建了多个低代码页面，则pages目录下会生成多个页面文件夹及对应的js文件。
+  
   > ![icon-note.gif](public_sys-resources/icon-note.gif) **说明：**
-  > 使用低代码页面开发时，其关联js文件的同级目录中不能包含hml和css页面，例如上图中的**js > MainAbility > pages > index**目录下不能包含hml与css文件，否则会出现编译报错。
-
-- **entry > src > main > supervisual > MainAbility > pages > index > index.visual**：visual文件存储低代码页面的数据模型，双击该文件即可打开低代码页面，进行可视化开发设计。如果创建了多个低代码页面，则pages目录下会生成多个页面文件夹及对应的visual文件。
+  > 使用低代码页面开发时，其关联js文件的同级目录中不能包含hml和css页面，例如上图中的 **js > MainAbility > pages > index** 目录下不能包含hml与css文件，否则会出现编译报错。
+  
+- **entry > src > main > supervisual > MainAbility > pages > index > index.visual** ：visual文件存储低代码页面的数据模型，双击该文件即可打开低代码页面，进行可视化开发设计。如果创建了多个低代码页面，则pages目录下会生成多个页面文件夹及对应的visual文件。
 
 
 ## 构建第一个页面
@@ -71,7 +72,7 @@ OpenHarmony低代码开发方式具有丰富的UI界面编辑功能，遵循[JS
 
    ![zh-cn_image_0000001260928361](figures/zh-cn_image_0000001260928361.gif)
 
-5. **在编辑窗口右上角的侧边工具栏，点击Previewer，打开预览器。**第一个页面效果如下图所示：
+5. **在编辑窗口右上角的侧边工具栏，点击Previewer，打开预览器。** 第一个页面效果如下图所示：
    ![zh-cn_image_0000001216288558](figures/zh-cn_image_0000001216288558.png)
 
 
@@ -110,14 +111,15 @@ OpenHarmony低代码开发方式具有丰富的UI界面编辑功能，遵循[JS
      
      export default {     
          onclick() {         
-             router.push ({             
+             router.push({             
                  uri:'pages/second/second', // 指定要跳转的页面         
              })     
          } 
      }
      ```
    
-   - “**index.viusal**”： 打开index.visual，选中画布上的Button组件。点击右侧属性样式栏中的事件图标![zh-cn_image_0000001215388136](figures/zh-cn_image_0000001215388136.png)（Events），鼠标点击Click事件的输入框，选择onclick，如下所示：
+   - “**index.visual**”： 打开index.visual，选中画布上的Button组件。点击右侧属性样式栏中的事件图标![zh-cn_image_0000001215388136](figures/zh-cn_image_0000001215388136.png)（Events），鼠标点击Click事件的输入框，选择onclick，如下所示：
+
      ![zh-cn_image_0000001223722586](figures/zh-cn_image_0000001223722586.png)
 
 2. **第二个页面返回到第一个页面。**
@@ -132,15 +134,16 @@ OpenHarmony低代码开发方式具有丰富的UI界面编辑功能，遵循[JS
       
       export default {     
           back() {         
-              router.back ()     
+              router.back()     
           } 
       }
       ```
-   - “**second.viusal**”： 打开second.visual，选中画布上的Button组件。点击右侧属性样式栏中的事件图标![zh-cn_image_0000001215388262](figures/zh-cn_image_0000001215388262.png)（Events），鼠标点击Click事件的输入框，选择back，如下所示：
+   - “**second.visual**”： 打开second.visual，选中画布上的Button组件。点击右侧属性样式栏中的事件图标![zh-cn_image_0000001215388262](figures/zh-cn_image_0000001215388262.png)（Events），鼠标点击Click事件的输入框，选择back，如下所示：
 
    ![zh-cn_image_0000001268082945](figures/zh-cn_image_0000001268082945.png)
 
-3. **打开index.visual或index.js文件，点击预览器中的**![zh-cn_image_0000001261979271](figures/zh-cn_image_0000001261979271.png)**按钮进行刷新。**效果如下图所示：
+3. **打开index.visual或index.js文件，点击预览器中的** ![zh-cn_image_0000001261979271](figures/zh-cn_image_0000001261979271.png) **按钮进行刷新。** 效果如下图所示：
+
    ![zh-cn_image_0000001261142799](figures/zh-cn_image_0000001261142799.png)
 
 
@@ -148,10 +151,11 @@ OpenHarmony低代码开发方式具有丰富的UI界面编辑功能，遵循[JS
 
 1. 将搭载OpenHarmony标准系统的开发板与电脑连接。
 
-2. 点击**File >Project Structure** > **Project >  Signing Configs**界面勾选“**Automatically generate signing**”，等待自动签名完成即可，点击“**OK**”。如下图所示：
+2. 点击**File > Project Structure** > **Project >  Signing Configs**界面勾选“**Automatically generate signing**”，等待自动签名完成即可，点击“**OK**”。如下图所示：
    ![zh-cn_image_0000001268283201](figures/zh-cn_image_0000001268283201.png)
 
 3. 在编辑窗口右上角的工具栏，点击![zh-cn_image_0000001262207811](figures/zh-cn_image_0000001262207811.png)按钮运行。效果如下图所示：
+
    ![zh-cn_image_0000001262127855](figures/zh-cn_image_0000001262127855.png)
 
 恭喜您已经使用JS语言开发（低代码方式）完成了第一个OpenHarmony应用，快来[探索更多的OpenHarmony功能](../application-dev-guide.md)吧。