diff --git a/en/application-dev/reference/apis/js-apis-settings.md b/en/application-dev/reference/apis/js-apis-settings.md index a546ee0cc3fc95d286b1f2a835998426372c874a..9371381ea8d39f48410d925bd0b28b441f6a9be6 100644 --- a/en/application-dev/reference/apis/js-apis-settings.md +++ b/en/application-dev/reference/apis/js-apis-settings.md @@ -1,6 +1,6 @@ # Settings -This module provides APIs for setting data items. +The **Settings** module provides APIs for setting data items. > **NOTE** > diff --git a/en/device-dev/porting/porting-asr582x-combo-demo.md b/en/device-dev/porting/porting-asr582x-combo-demo.md index a172ea23a2332b3ed96b9d137c7a546752d38f98..7f6dbeca13a06096f90bf9ab948474df4d60ffab 100644 --- a/en/device-dev/porting/porting-asr582x-combo-demo.md +++ b/en/device-dev/porting/porting-asr582x-combo-demo.md @@ -473,7 +473,7 @@ The compilation option entry of the subsystem is in the `config.json` file of th The source code of the lwIP component is stored in `//third_party/lwip`. The kernel in OpenHarmony is customized in `//kernel/liteos_m/components/net/lwip-2.1`, including the redefinition of some interfaces and structures. -For details about the porting process, see [lwIP Module Adaptation](https://gitee.com/openharmony/docs/blob/master/en/device-dev/porting/porting-chip-board-lwip.md). +For details about the porting process, see [lwIP Module Adaptation](porting-chip-board-lwip.md ). In this example, the path for setting lwip in the `config.json` file is as follows: diff --git a/en/device-dev/porting/porting-linux-kernel.md b/en/device-dev/porting/porting-linux-kernel.md index cbe6bef55a6b9ad6ad69f33da16c6d51843a7256..6fa66b28ca4ec24072947b93dd9701e9e96be29b 100644 --- a/en/device-dev/porting/porting-linux-kernel.md +++ b/en/device-dev/porting/porting-linux-kernel.md @@ -206,10 +206,10 @@ The HDF test cases are used to verify basic functions of the HDF framework and p **Test Case Build and Test Method** -Use the [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-toolchain-hdc-guide.md) tool to push the test case execution file to the device and execute the test cases. The procedure is as follows: +Use the [hdc_std](../subsystems/subsys-toolchain-hdc-guide.md) tool to push the test case execution file to the device and execute the test cases. The procedure is as follows: 1. Build the HDF test cases. -2. Use the **hdc\_std** tool to push the test case execution file to the device. +2. Use the **hdc_std** tool to push the test case execution file to the device. 3. Go to the **data/test** directory of the device and execute the test file. The procedure is as follows: @@ -226,7 +226,7 @@ The procedure is as follows: 2. Copy the test files to the target device \(Raspberry Pi in this example\). - Method 1: Use the [hdc\_std](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-toolchain-hdc-guide.md) tool. + Method 1: Use the [hdc_std](../subsystems/subsys-toolchain-hdc-guide.md) tool. 1. Create the **data/test** directory in Raspberry Pi. diff --git a/en/device-dev/quick-start/quickstart-ide-lite-overview.md b/en/device-dev/quick-start/quickstart-ide-lite-overview.md index 2b3ee5c0f0257ec2c4a3d29c41a922a62114923a..f23028f755bd48bb7c7f6ce8f1c05370551565ab 100644 --- a/en/device-dev/quick-start/quickstart-ide-lite-overview.md +++ b/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](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. + 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. 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). diff --git a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md index 3368ed019c26a482af6ae90de4602c23a59a9a45..c6efd108c057cf6191eb0259bbb6355eca133f02 100644 --- a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md +++ b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3516-burn.md @@ -7,7 +7,7 @@ Burning is the process of downloading compiled program files to a development bo 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). +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](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: > diff --git a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md index aa19ccf3d77feb92aa41c127887d9a66ecadacc6..5449e2f1c3d5e08d0eaee62f06e45842f015f4a7 100644 --- a/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md +++ b/en/device-dev/quick-start/quickstart-ide-lite-steps-hi3861-burn.md @@ -5,7 +5,7 @@ Burning is the process of downloading compiled program files to a development bo 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). +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](quickstart-lite-introduction-hi3861.md). 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). diff --git a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md index dad8d48305a2b4451e397e06f13aa5976446ca96..919e4c1f9c7cee049b392f476ccc7818f614cab1 100644 --- a/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md +++ b/en/device-dev/quick-start/quickstart-ide-standard-running-hi3516-burning.md @@ -4,7 +4,7 @@ To burn source code to Hi3516D V300 through the USB 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 Hi3516D V300 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3516.md). +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](quickstart-lite-introduction-hi3516.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). diff --git a/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md b/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md index 9e453a954d7a3ee8a1e8ec5676c39e8ef30d0ca1..3d0fa106dad97fd0d0085664b5a844d32d013627 100644 --- a/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md +++ b/en/device-dev/quick-start/quickstart-lite-steps-hi3516-burn.md @@ -38,7 +38,7 @@ After the building is complete, ensure that you can [remotely access the Ubuntu After the source code is imported, 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 Hi3516D V300 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3516.md). +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](quickstart-lite-introduction-hi3516.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). diff --git a/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md b/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md index 46974e89328fec671bae02e748ea393b1d147914..ae60ee8b8894a07cdf00f6cba807d44a469d93fc 100644 --- a/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md +++ b/en/device-dev/quick-start/quickstart-lite-steps-hi3861-burn.md @@ -38,7 +38,7 @@ After the building is complete, ensure that you can [remotely access the Ubuntu After the source code is imported, 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). +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](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). diff --git a/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md b/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md index 4c1e34c22be466aca3721ac696aa6ae306eae58b..4f5338ea93dc190c43af70fa96f68483d9ab37a6 100644 --- a/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md +++ b/en/device-dev/quick-start/quickstart-standard-running-hi3516-burning.md @@ -38,7 +38,7 @@ After the building is complete, ensure that you can [remotely access the Ubuntu After the source code is imported, 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 Hi3516D V300 Development Board](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-introduction-hi3516.md). +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](quickstart-lite-introduction-hi3516.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).