diff --git a/en/device-dev/get-code/sourcecode-acquire.md b/en/device-dev/get-code/sourcecode-acquire.md
index 0b256136c03180b55b15bac57767dc29a22aab87..0b1af9cae0b40167b423233668edf1f47fa27a75 100644
--- a/en/device-dev/get-code/sourcecode-acquire.md
+++ b/en/device-dev/get-code/sourcecode-acquire.md
@@ -106,7 +106,7 @@ This document describes how to acquire OpenHarmony source code and provides its
- Obtaining the source code of other OpenHarmony releases
- For details about how to obtain the source code of other OpenHarmony releases, see the [Release Notes](https://gitee.com/openharmony/docs/blob/master/en/release-notes/Readme.md).
+ For details about how to obtain the source code of other OpenHarmony releases, see the [Release Notes](../../release-notes/Readme.md).
## Method 2: Acquiring Source Code from HPM
@@ -192,7 +192,7 @@ You must install **Node.js** and HPM on your local PC. The installation proced
To ensure the download performance, you are advised to download the source code or the corresponding solution from the image library of the respective site listed in the table below.
> **NOTE:**
->- The table below provides only the sites for downloading the latest OpenHarmony master and LTS code. For details about how to obtain the source code of earlier versions, see the [Release Notes](https://gitee.com/openharmony/docs/blob/master/en/release-notes/Readme.md).
+>- The table below provides only the sites for downloading the latest OpenHarmony master and LTS code. For details about how to obtain the source code of earlier versions, see the [Release Notes](../../release-notes/Readme.md).
>- The Master 1.0 version is no longer maintained.
**Table 1** Sites for acquiring source code from image sites
diff --git a/en/device-dev/kernel/kernel-small-start-user.md b/en/device-dev/kernel/kernel-small-start-user.md
index 106e557d153e9cb1b33a2567fe42d68a736f007d..09461e6b4192191ee3d55c8965c2a0fd059d9fac 100644
--- a/en/device-dev/kernel/kernel-small-start-user.md
+++ b/en/device-dev/kernel/kernel-small-start-user.md
@@ -39,7 +39,7 @@ During system startup, **OsUserInitProcess** is called to start the **init**
- Starts key system programs or services, such as shell.
> **NOTE:**
- >In OpenHarmony, the **init** process reads the **/etc/init.cfg** file and runs specified commands or starts specified processes based on configurations. For details, see [init Module](https://gitee.com/openharmony/docs/blob/master/en/device-dev/subsystems/subsys-boot-init.md).
+ >In OpenHarmony, the **init** process reads the **/etc/init.cfg** file and runs specified commands or starts specified processes based on configurations. For details, see [init Module](../subsystems/subsys-boot-init.md).
- Monitors the process for reclaiming the orphan process and clears the zombie processes in child processes.
@@ -48,7 +48,7 @@ During system startup, **OsUserInitProcess** is called to start the **init**
Common compilation modes of user-space programs include:
-1. [Compilation using the framework](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-steps-board3516-running.md)
+1. [Compilation using the framework](../quick-start/quickstart-lite-steps-board3516-running.md)
2. Manual compilation
Example:
@@ -57,7 +57,7 @@ Common compilation modes of user-space programs include:
clang --target=arm-liteos --sysroot=prebuilts/lite/sysroot -o helloworld helloworld.c
```
- Before running the **clang** command, install the LLVM compiler. For details, see [Installing LLVM](https://gitee.com/openharmony/docs/blob/master/en/device-dev/quick-start/quickstart-lite-env-setup-lin.md).
+ Before running the **clang** command, install the LLVM compiler. For details, see [Installing LLVM](../quick-start/quickstart-lite-env-setup-lin.md).
**--target=arm-liteos**: specifies that the compilation platform is arm-liteos.
diff --git a/en/device-dev/porting/porting-chip-prepare-knows.md b/en/device-dev/porting/porting-chip-prepare-knows.md
index 7de3a048b0efbc10bb17984f495b16d971dc1d34..d968489ab8fbb67f3a5d77bd2cdcf3e309569bf5 100644
--- a/en/device-dev/porting/porting-chip-prepare-knows.md
+++ b/en/device-dev/porting/porting-chip-prepare-knows.md
@@ -79,6 +79,6 @@ The **device** directory of OpenHarmony is the adaptation directory for the ba
## Porting Specifications
-- The porting must comply with the basic OpenHarmony principles described in [Contribution](https://gitee.com/openharmony/docs/blob/master/en/contribute/contribution.md).
+- The porting must comply with the basic OpenHarmony principles described in [Contribution](../../contribute/contribution.md).
- The code required for third-party SoC adaptation is stored in the **device**, **vendor**, and **arch** directories. Naming and usage of these directories must comply with specified naming and usage specifications. For details, see [Directory Specifications](porting-chip-kernel-overview.md) and [Board-Level Directory Specifications](porting-chip-board-overview.md#section6204129143013).
diff --git a/en/device-dev/porting/porting-smallchip-prepare-needs.md b/en/device-dev/porting/porting-smallchip-prepare-needs.md
index 685a2a7a8cd49654abc2326776f3b8f276372af2..4a92950491273dbebec06e6da37ef5a242675b41 100644
--- a/en/device-dev/porting/porting-smallchip-prepare-needs.md
+++ b/en/device-dev/porting/porting-smallchip-prepare-needs.md
@@ -1,6 +1,6 @@
# Before You Start
-This document provides guidance on how to port the Linux and LiteOS Cortex-A kernels on the OpenHarmony [small system](https://device.harmonyos.com/en/docs/start/introduce/oem_minitinier_des-0000001105598722) to a development board. It is intended for developers with experience in developing embedded systems. Before following instructions in this document, it is recommended that you familiarize yourself with [OpenHarmony](https://gitee.com/openharmony/docs/blob/master/en/OpenHarmony-Overview.md), including its technical architecture, directory structure, kernel subsystem, and driver subsystem. The following table lists the development boards that have been adapted to the small system.
+This document provides guidance on how to port the Linux and LiteOS Cortex-A kernels on the OpenHarmony [small system](../quick-start/quickstart-lite-overview.md) to a development board. It is intended for developers with experience in developing embedded systems. Before following instructions in this document, it is recommended that you familiarize yourself with [OpenHarmony](../../OpenHarmony-Overview.md), including its technical architecture, directory structure, kernel subsystem, and driver subsystem. The following table lists the development boards that have been adapted to the small system.
**Table 1** Development boards compatible with the OpenHarmony small system
diff --git a/en/device-dev/subsystems/subsys-application-framework-envbuild.md b/en/device-dev/subsystems/subsys-application-framework-envbuild.md
index 26aaaea82d6a99b193d1345d36e4ffda76ec0e62..bf8f8616f24a1f8d18793c365caa395166c27294 100644
--- a/en/device-dev/subsystems/subsys-application-framework-envbuild.md
+++ b/en/device-dev/subsystems/subsys-application-framework-envbuild.md
@@ -3,5 +3,5 @@
- Development board: Hi3516D V300
- [Download the source code](../get-code/sourcecode-acquire.md)
-- [Build the application framework](https://gitee.com/openharmony/docs/blob/master/en/readme/application-framework.md).
+- Build the application framework.
diff --git a/zh-cn/device-dev/get-code/sourcecode-acquire.md b/zh-cn/device-dev/get-code/sourcecode-acquire.md
index 66b9a1ff68a0c49c7a846c88690056f65e9c472c..dcdeeecdf7018bdfb932e9be7472e659ee71eff8 100644
--- a/zh-cn/device-dev/get-code/sourcecode-acquire.md
+++ b/zh-cn/device-dev/get-code/sourcecode-acquire.md
@@ -104,7 +104,7 @@ OpenHarmony是由开放原子开源基金会(OpenAtom Foundation)孵化及
repo forall -c 'git lfs pull'
```
-- OpenHarmony其他版本源码获取方式请参考版本[Release-Notes](https://gitee.com/openharmony/docs/blob/master/zh-cn/release-notes/Readme.md)。
+- OpenHarmony其他版本源码获取方式请参考版本[Release-Notes](../../release-notes/Readme.md)。
## 获取方式2:从HPM获取
@@ -189,7 +189,7 @@ OpenHarmony是由开放原子开源基金会(OpenAtom Foundation)孵化及
为了获得更好的下载性能,您可以选择从以下站点的镜像库获取源码或者对应的解决方案。
> **说明:**
->- 本部分只提供OpenHarmony Master最新版本和LTS最新版本的源码获取方式, 其他版本源码获取方式以及具体版本信息请参考[Release-Notes](https://gitee.com/openharmony/docs/blob/master/zh-cn/release-notes/Readme.md)。
+>- 本部分只提供OpenHarmony Master最新版本和LTS最新版本的源码获取方式, 其他版本源码获取方式以及具体版本信息请参考[Release-Notes](../../release-notes/Readme.md)。
>- 当前Master 1.0版本已经不再维护。
**表 1** 源码获取路径
diff --git a/zh-cn/device-dev/kernel/kernel-small-start-user.md b/zh-cn/device-dev/kernel/kernel-small-start-user.md
index d8feb2a066db4796bc2fb9705422a9644b54ad6c..77797471fdbf044bca1c8983e6884f07d71580d1 100644
--- a/zh-cn/device-dev/kernel/kernel-small-start-user.md
+++ b/zh-cn/device-dev/kernel/kernel-small-start-user.md
@@ -39,7 +39,7 @@ LITE_USER_SEC_ENTRY VOID OsUserInit(VOID *args)
- 启动关键系统程序或服务,如交互进程shell。
> **说明:**
- >在OpenHarmony 中**init**进程通过读取/etc/init.cfg,根据配置执行指定命令,或启动指定进程(详见:[init启动引导](https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/subsystems/subsys-boot-init.md))。
+ >在OpenHarmony 中**init**进程通过读取/etc/init.cfg,根据配置执行指定命令,或启动指定进程(详见:[init启动引导](../subsystems/subsys-boot-init.md))。
- 监控回收孤儿进程,清理子进程中的僵尸进程。
@@ -48,7 +48,7 @@ LITE_USER_SEC_ENTRY VOID OsUserInit(VOID *args)
用户态程序常见编译方式有如下两种:
-1. [利用框架编译用户态进程](https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/quick-start/quickstart-lite-steps-hi3516-running.md)。
+1. [利用框架编译用户态进程](../quick-start/quickstart-lite-steps-hi3516-running.md)。
2. 手动编译
实例:
@@ -57,7 +57,7 @@ LITE_USER_SEC_ENTRY VOID OsUserInit(VOID *args)
clang --target=arm-liteos --sysroot=prebuilts/lite/sysroot -o helloworld helloworld.c
```
- **clang**:参考[LLVM安装指导](https://gitee.com/openharmony/docs/blob/master/zh-cn/device-dev/quick-start/quickstart-lite-env-setup-linux.md)安装LLVM编译器。
+ **clang**:参考[LLVM安装指导](../quick-start/quickstart-lite-env-setup-linux.md)安装LLVM编译器。
**--target**:--target=arm-liteos,指定编译平台为arm-liteos。
diff --git a/zh-cn/device-dev/porting/oem_transplant_chip_prepare_knows.md b/zh-cn/device-dev/porting/oem_transplant_chip_prepare_knows.md
index 4de0e275eef061e53fa143d15c56cd7a61862ec4..078f325731cf8828aa03008e8612f13265e603a6 100644
--- a/zh-cn/device-dev/porting/oem_transplant_chip_prepare_knows.md
+++ b/zh-cn/device-dev/porting/oem_transplant_chip_prepare_knows.md
@@ -79,6 +79,6 @@ OpenHarmony的device目录是基础芯片的适配目录,如果在三方芯片
## 移植规范
-- 满足OpenHarmony[开源贡献基本规范和准则](https://gitee.com/openharmony/docs/blob/master/zh-cn/contribute/%E5%8F%82%E4%B8%8E%E8%B4%A1%E7%8C%AE.md)。
+- 满足OpenHarmony[开源贡献基本规范和准则](../../contribute/参与贡献.md)。
- 三方芯片适配所需要贡献的代码主要在device、vendor和arch三个目录,参照[内核目录规范](porting-chip-kernel-overview.md)和[板级目录规范](porting-chip-board-overview.md#section6204129143013)满足基本目录命名和使用规范。
diff --git a/zh-cn/device-dev/porting/porting-smallchip-prepare-needs.md b/zh-cn/device-dev/porting/porting-smallchip-prepare-needs.md
index afe392369f2eb34c0c5a8dcf5a6204850347dd11..0217107b8523b98e36f72b89fe9a98f79fd528fd 100644
--- a/zh-cn/device-dev/porting/porting-smallchip-prepare-needs.md
+++ b/zh-cn/device-dev/porting/porting-smallchip-prepare-needs.md
@@ -1,6 +1,6 @@
# 移植须知
-本文详细介绍如何将OpenHarmony[小型系统](https://device.harmonyos.com/cn/docs/start/introduce/oem_start_guide-0000001054913231)的linux和LiteOS-A内核移植到新的开发板上,要求读者具有一定的嵌入式系统开发经验。建议先查看[入门指导](https://gitee.com/openharmony/docs/blob/master/zh-cn/OpenHarmony-Overview_zh.md),以了解OpenHarmony软件架构、目录结构、内核子系统和驱动子系统相关知识。当前小型系统已适配的开发板如下表所示:
+本文详细介绍如何将OpenHarmony[小型系统](../quick-start/quickstart-lite-overview.md)的linux和LiteOS-A内核移植到新的开发板上,要求读者具有一定的嵌入式系统开发经验。建议先查看[入门指导](../../OpenHarmony-Overview_zh.md),以了解OpenHarmony软件架构、目录结构、内核子系统和驱动子系统相关知识。当前小型系统已适配的开发板如下表所示:
**表 1** OpenHarmony小型系统已适配的开发板
diff --git a/zh-cn/device-dev/subsystems/subsys-application-framework-envbuild.md b/zh-cn/device-dev/subsystems/subsys-application-framework-envbuild.md
index 182aea265b994e46add0b4ab22ad8bab8bbf8153..e84d391fdfdcee5fe1c030720dcf6396ef88eb02 100644
--- a/zh-cn/device-dev/subsystems/subsys-application-framework-envbuild.md
+++ b/zh-cn/device-dev/subsystems/subsys-application-framework-envbuild.md
@@ -3,5 +3,5 @@
- 开发板:Hi3516DV300
- [下载源码](../get-code/sourcecode-acquire.md)
-- [编译用户程序框架](https://gitee.com/openharmony/docs/blob/master/zh-cn/readme/%E7%94%A8%E6%88%B7%E7%A8%8B%E5%BA%8F%E6%A1%86%E6%9E%B6%E5%AD%90%E7%B3%BB%E7%BB%9F.md)
+- [编译用户程序框架](../../readme/用户程序框架子系统.md)