diff --git a/en/device-dev/kernel/kernel-small-bundles-fs-virtual.md b/en/device-dev/kernel/kernel-small-bundles-fs-virtual.md
index 2d90df4720aafd107b21196ecd589878f3b191ff..28af039691b91fbc5196f7e3d266ba1efadb7098 100644
--- a/en/device-dev/kernel/kernel-small-bundles-fs-virtual.md
+++ b/en/device-dev/kernel/kernel-small-bundles-fs-virtual.md
@@ -238,7 +238,7 @@ In the following table, "√" indicates that the corresponding file system suppo
×
|
-readlink
+ |
readline
|
Reads a soft link.
|
diff --git a/en/device-dev/subsystems/subsys-boot-init-service.md b/en/device-dev/subsystems/subsys-boot-init-service.md
index e4b553c941198faea09e1b48bdffb1adba1d43de..dbbfee684673226663b9b61d931937e3bf0472ac 100644
--- a/en/device-dev/subsystems/subsys-boot-init-service.md
+++ b/en/device-dev/subsystems/subsys-boot-init-service.md
@@ -125,7 +125,7 @@ By parsing the *.cfg file, you can obtain **service** fields, a
| importance | Standard system: service priority
Small system: service importance|
Standard system: The service priority ranges from -20 to 19. A value beyond the range is invalid.
Small system: The value 0 indicates an unimportant process and a value greater than 0 indicates an important process.| Small and standard systems|
| caps | Capabilities required by the current service. They are evaluated based on the capabilities supported by the security subsystem and configured in accordance with the principle of least permission.| Type: number or string array. If you set the value to a number, use the standard Linux capability. If you set the value to a string array, use the standard macro name.| Small and standard systems|
| critical | Suppression mechanism for services. If the number of times a service is restarted exceeds the value N within the specified period T, the system will be restarted.|
Standard system:
Type: int array, for example, "critical": [M, N, T].
- M: enable flag (0: disable; 1: enable).
- N: number of times the service is started.
- T: period of time, in seconds.
Both M and N are greater than 0.
Small and standard systems:
Type: int, for example, "critical": M.
M: enable flag (0: disable; 1: enable).
By default, N is 4 and T is 20.| Standard system|
- | cpucore | Number of CPU cores bound to the service.| Type: int array, for example, "cpucore": [N1, N2, ...]. N1 and N2 indicate the indices of the CPU cores to be bound. For a single-core device, cpucore is 0.| Standard system|
+ | cpucore | Number of CPU cores bound to the service.| Type: int array, for example, "cpucore": [N1, N2, ...]. N1 and N2 indicate the indicate of the CPU cores to be bound. For a single-core device, cpucore is 0.| Standard system|
| d-caps | Distributed service capability.| Type: string array, for example, "d-caps": ["OHOS_DMS"].| Standard system|
| apl | Ability privilege level.| Type: string, for example, "apl": "system_core".
The value can be system_core (default), normal, or system_basic.| Standard system|
| start-mode | Service startup mode.| Type: string, for example, **"start-mode": "condition"**.
The value can be boot, normal, or condition. For details, see [init service startup control](#section56901555918).| Standard system|
diff --git a/en/device-dev/subsystems/subsys-boot-overview.md b/en/device-dev/subsystems/subsys-boot-overview.md
index d00edfbbcc0b2ee3347fd2b3d06f8ac0b269ce6a..fefaeb0640b6e8fb26b0a2c6670aee88d21f4dcd 100644
--- a/en/device-dev/subsystems/subsys-boot-overview.md
+++ b/en/device-dev/subsystems/subsys-boot-overview.md
@@ -301,7 +301,7 @@ On each development board, you need to partition the memory to store the precedi
After a device node is created, mount it to the corresponding partition. The code is as follows:
```
- int MountRequriedPartitions(const Fstab *fstab)
+ int MountRequiredPartitions(const Fstab *fstab)
{
INIT_ERROR_CHECK(fstab != NULL, return -1, "Failed fstab is NULL");
int rc;
diff --git a/en/device-dev/subsystems/subsys-build-chip_solution.md b/en/device-dev/subsystems/subsys-build-chip_solution.md
index 46476aaa2111fbc0846754b1158af5ca2cc3bcb6..d17ae28761672e36e2da463bfd548ee3e6e91056 100644
--- a/en/device-dev/subsystems/subsys-build-chip_solution.md
+++ b/en/device-dev/subsystems/subsys-build-chip_solution.md
@@ -73,7 +73,7 @@ The following uses the RTL8720 development board provided by Realtek as an examp
# Note: The default toolchain is "ohos-clang". It's not mandatory if you use the default toochain.
board_toolchain = "gcc-arm-none-eabi"
- # The toolchain path instatlled, it's not mandatory if you have added toolchian path to your ~/.bashrc.
+ # The toolchain path instatlled, it's not mandatory if you have added toolchain path to your ~/.bashrc.
board_toolchain_path =
rebase_path("//prebuilts/gcc/linux-x86/arm/gcc-arm-none-eabi/bin",
root_build_dir)
diff --git a/en/device-dev/subsystems/subsys-tel-guide.md b/en/device-dev/subsystems/subsys-tel-guide.md
index 31dd6c07026fe181b6638f557a41e57c6314c824..9b204051bd6742a6cd6afbf550d67f8ac8186c9e 100644
--- a/en/device-dev/subsystems/subsys-tel-guide.md
+++ b/en/device-dev/subsystems/subsys-tel-guide.md
@@ -428,7 +428,7 @@ The following table describes the API for reporting modem events.
case CALL_CLIR_SUPPRESSION:
clir = "i";
break; /* suppression */
- case CALL_CLIR_SUBSCRIPTION_DEFUALT:
+ case CALL_CLIR_SUBSCRIPTION_DEFUALT1:
default:
clir = "";
break; /* subscription default */
diff --git a/en/device-dev/subsystems/subsys-xts-guide.md b/en/device-dev/subsystems/subsys-xts-guide.md
index 70b6dded52079b8da901940f5968eaae512add75..8f8996cbbf7aa5604632bfd7f5a3bf09fd0da677 100644
--- a/en/device-dev/subsystems/subsys-xts-guide.md
+++ b/en/device-dev/subsystems/subsys-xts-guide.md
@@ -370,7 +370,7 @@ The test cases are developed with the JavaScript language and must meet the prog
| beforeEach | Presets a test-case-level action executed before each test case is executed. The number of execution times is the same as the number of test cases defined by it. You can pass the action function as the only parameter. | No |
| afterEach | Presets a test-case-level clear action executed after each test case is executed. The number of execution times is the same as the number of test cases defined by it. You can pass the clear function as the only parameter. | No |
| describe | Defines a test suite. You can pass two parameters: test suite name and test suite function. The describe statement supports nesting. You can use beforeall, beforeEach, afterEach, and afterAll in each describe statement. | Yes |
-| it | Defines a test case. You can pass three parameters: test case name, filter parameter, and test case function.
**Filter parameter:**
The value is a 32-bit integer. Setting different bits to 1 means different configurations.
- Setting bit 0 to **1** means bypassing the filter.
- Setting bits 0-10 to **1** specifies the test case type, which can be FUNCTION (function test), PERFORMANCE (performance test), POWER (power consumption test), RELIABILITY (reliability test), SECURITY (security compliance test), GLOBAL (integrity test), COMPATIBILITY (compatibility test), USER (user test), STANDARD (standard test), SAFETY (security feature test), and RESILIENCE (resilience test), respectively.
- Setting bits 16-18 to **1** specifies the test case scale, which can be SMALL (small-scale test), MEDIUM (medium-scale test), and LARGE (large-scale test), respectively.
- Seting bits 24-28 to **1** specifies the test level, which can be LEVEL0 (level-0 test), LEVEL1 (level-1 test), LEVEL2 (level-2 test), LEVEL3 (level-3 test), and LEVEL4 (level-4 test), respectively.
| Yes |
+| it | Defines a test case. You can pass three parameters: test case name, filter parameter, and test case function.
**Filter parameter:**
The value is a 32-bit integer. Setting different bits to 1 means different configurations.
- Setting bit 0 to **1** means bypassing the filter.
- Setting bits 0-10 to **1** specifies the test case type, which can be FUNCTION (function test), PERFORMANCE (performance test), POWER (power consumption test), RELIABILITY (reliability test), SECURITY (security compliance test), GLOBAL (integrity test), COMPATIBILITY (compatibility test), USER (user test), STANDARD (standard test), SAFETY (security feature test), and RESILIENCE (resilience test), respectively.
- Setting bits 16-18 to **1** specifies the test case scale, which can be SMALL (small-scale test), MEDIUM (medium-scale test), and LARGE (large-scale test), respectively.
- Setting bits 24-28 to **1** specifies the test level, which can be LEVEL0 (level-0 test), LEVEL1 (level-1 test), LEVEL2 (level-2 test), LEVEL3 (level-3 test), and LEVEL4 (level-4 test), respectively.
| Yes |
Use the standard syntax of Jasmine to write test cases. The ES6 specification is supported.
diff --git a/zh-cn/device-dev/kernel/kernel-mini-appx-lib.md b/zh-cn/device-dev/kernel/kernel-mini-appx-lib.md
index d2f4b54be58063e23b8f7fc145e96c555b4e27ca..82f007c8c3d6ed95d8be4f0a4a119ca54398aecb 100644
--- a/zh-cn/device-dev/kernel/kernel-mini-appx-lib.md
+++ b/zh-cn/device-dev/kernel/kernel-mini-appx-lib.md
@@ -204,7 +204,7 @@ OpenHarmony内核使用**musl libc**库以及自研接口，支持部分标准PO
| \#include <assert.h> | void assert(scalar expression); | 断言为假终止线程 |
| \#include <pthread.h> | int pthread_cond_destroy(pthread_cond_t \*cond); | 销毁条件变量 |
| \#include <pthread.h> | int pthread_cond_init(pthread_cond_t \*restrict co
nd, const pthread_condattr_t \*restrict attr); | 初始化条件变量 |
-| \#include <pthread.h> | int pthread_cond_timedwait(pthread_cond_t \*restr
ict cond, pthread_mutex_t \*restrict mutex, const st
ruct timespec \*restrict abstime); | 等待条件 |
+| \#include <pthread.h> | int pthread_cond_timedwait(pthread_cond_t \*restr
ict cond, pthread_mutex_t \*restrict mutex, const struct timespec \*restrict abstime); | 等待条件 |
| \#include <pthread.h> | int pthread_condattr_init(pthread_condattr_t \*attr); | 初始化条件变量属性对象 |
| \#include <pthread.h> | int pthread_mutex_unlock(pthread_mutex_t \*mutex); | 解锁互斥锁 |
| \#include <pthread.h> | int pthread_create(pthread_t \*thread, const pthread_
attr_t \*attr, void \*(\*start_routine)(void \*), void \*arg); | 创建一个新的线程 |
diff --git a/zh-cn/device-dev/kernel/kernel-mini-extend-cpup.md b/zh-cn/device-dev/kernel/kernel-mini-extend-cpup.md
index 9c5831f228d0ab6a019f7c022bb7d345dd3bbd9b..8e9c2c00dc6c237a67e9c4d76ec7e086f589c8d0 100644
--- a/zh-cn/device-dev/kernel/kernel-mini-extend-cpup.md
+++ b/zh-cn/device-dev/kernel/kernel-mini-extend-cpup.md
@@ -122,17 +122,17 @@ UINT32 ItCpupTest(VOID)
usleep(100);
- /* 获取当前系统cpu占用率 */
+ /* 获取当前系统CPU占用率 */
cpupUse = LOS_SysCpuUsage();
printf("the current system cpu usage is: %u.%u\n",
cpupUse / LOS_CPUP_PRECISION_MULT, cpupUse % LOS_CPUP_PRECISION_MULT);
cpupUse = LOS_HistorySysCpuUsage(CPU_LESS_THAN_1S);
- /* 获取指定任务的cpu占用率，该测试例程中指定的任务为以上创建的cpup测试任务 */
+ /* 获取指定任务的CPU占用率，该测试例程中指定的任务为以上创建的cpup测试任务 */
printf("the history system cpu usage in all time：%u.%u\n",
cpupUse / LOS_CPUP_PRECISION_MULT, cpupUse % LOS_CPUP_PRECISION_MULT);
cpupUse = LOS_TaskCpuUsage(g_cpuTestTaskID);
- /* 获取指定历史任务在系统启动到现在的cpu占用率，该测试例程中指定的任务为以上创建的cpup测试任务 */
+ /* 获取指定历史任务在系统启动到现在的CPU占用率，该测试例程中指定的任务为以上创建的cpup测试任务 */
printf("cpu usage of the cpupTestTask:\n TaskID: %d\n usage: %u.%u\n",
g_cpuTestTaskID, cpupUse / LOS_CPUP_PRECISION_MULT, cpupUse % LOS_CPUP_PRECISION_MULT);
cpupUse = LOS_HistoryTaskCpuUsage(g_cpuTestTaskID, CPU_LESS_THAN_1S);
diff --git a/zh-cn/device-dev/kernel/kernel-mini-extend-dynamic-loading.md b/zh-cn/device-dev/kernel/kernel-mini-extend-dynamic-loading.md
index b54322512502bdae48997ccbcc8f656db40eb0cb..15abf87dbb2db2faff8657dd58c74feaec2a0573 100644
--- a/zh-cn/device-dev/kernel/kernel-mini-extend-dynamic-loading.md
+++ b/zh-cn/device-dev/kernel/kernel-mini-extend-dynamic-loading.md
@@ -96,7 +96,7 @@ Program Headers:
4. “-z max-page-size=4”链接选项：二进制文件中可加载段的对齐字节数为4，可节约内存，可用于动态库。
-5. “-mcpu=”需要指定对应的cpu架构。
+5. “-mcpu=”需要指定对应的CPU架构。
## 约束
diff --git a/zh-cn/device-dev/kernel/kernel-mini-memory-perf.md b/zh-cn/device-dev/kernel/kernel-mini-memory-perf.md
index d03c39beaad79becaab9112ce36c430483e27d8c..6803d34b7a8c07b660a56ae000d39ece93aef518 100644
--- a/zh-cn/device-dev/kernel/kernel-mini-memory-perf.md
+++ b/zh-cn/device-dev/kernel/kernel-mini-memory-perf.md
@@ -50,7 +50,7 @@ OpenHarmony LiteOS-A内核的Perf模块提供下面几种功能，接口详细
LOS_PerfNotifyHookReg(Example_PerfNotifyHook);
```
-4. 若perf采样的buffer涉及到cpu 跨cache，则用户可通过注册刷cache的钩子，进行cache同步。 示例如下：
+4. 若perf采样的buffer涉及到CPU跨cache，则用户可通过注册刷cache的钩子，进行cache同步。 示例如下：
```
VOID Example_PerfFlushHook(VOID *addr, UINT32 size)
diff --git a/zh-cn/device-dev/kernel/kernel-small-basic-process-thread.md b/zh-cn/device-dev/kernel/kernel-small-basic-process-thread.md
index e5dc3baad0229fbd450390a8391f3f333f6d2f89..a7934c306676f213033cf5b644d15555ecda34c9 100644
--- a/zh-cn/device-dev/kernel/kernel-small-basic-process-thread.md
+++ b/zh-cn/device-dev/kernel/kernel-small-basic-process-thread.md
@@ -74,7 +74,7 @@ OpenHarmony 任务管理模块提供任务创建、任务延时、任务挂起
| 任务调度的控制 | - LOS_TaskLock：锁任务调度
- LOS_TaskUnlock：解锁任务调度 |
| 任务优先级的控制 | - LOS_CurTaskPriSet：设置当前任务的优先级
- LOS_TaskPriSet：设置指定任务的优先级
- LOS_TaskPriGet：获取指定任务的优先级 |
| 任务信息获取 | - LOS_CurTaskIDGet：获取当前任务的ID
- LOS_TaskInfoGet：获取指定任务的信息 |
-| 任务绑核操作 | - LOS_TaskCpuAffiSet：绑定指定任务到指定cpu上运行，仅在多核下使用
- LOS_TaskCpuAffiGet：获取指定任务的绑核信息，仅在多核下使用 |
+| 任务绑核操作 | - LOS_TaskCpuAffiSet：绑定指定任务到指定CPU上运行，仅在多核下使用
- LOS_TaskCpuAffiGet：获取指定任务的绑核信息，仅在多核下使用 |
| 任务调度参数的控制 | - LOS_GetTaskScheduler：获取指定任务的调度策略
- LOS_SetTaskScheduler:设置指定任务的调度参数，包括优先级和调度策略 |
| 系统支持的最大任务数 | LOS_GetSystemTaskMaximum |
diff --git a/zh-cn/device-dev/kernel/kernel-small-debug-process-cpu.md b/zh-cn/device-dev/kernel/kernel-small-debug-process-cpu.md
index 89a46e053ec053321e9f667ba59d74c1f8013b56..7e84b5195532059544f948b4dd6661fcf318640f 100644
--- a/zh-cn/device-dev/kernel/kernel-small-debug-process-cpu.md
+++ b/zh-cn/device-dev/kernel/kernel-small-debug-process-cpu.md
@@ -135,11 +135,11 @@ UINT32 ItCpupTest(VOID)
usleep(100);
- /* 获取当前系统历史cpu占用率 */
+ /* 获取当前系统历史CPU占用率 */
cpupUse = LOS_HistorySysCpuUsage(CPU_LESS_THAN_1S);
printf("the history system cpu usage in all time：%u.%u\n",
cpupUse / LOS_CPUP_PRECISION_MULT, cpupUse % LOS_CPUP_PRECISION_MULT);
- /* 获取指定任务的cpu占用率，该测试例程中指定的任务为以上创建的cpup测试任务 */
+ /* 获取指定任务的CPU占用率，该测试例程中指定的任务为以上创建的cpup测试任务 */
cpupUse = LOS_HistoryTaskCpuUsage(g_cpuTestTaskID, CPU_LESS_THAN_1S);
printf("cpu usage of the cpupTestTask in all time:\n TaskID: %d\n usage: %u.%u\n",
g_cpuTestTaskID, cpupUse / LOS_CPUP_PRECISION_MULT, cpupUse % LOS_CPUP_PRECISION_MULT);
diff --git a/zh-cn/device-dev/porting/Readme-CN.md b/zh-cn/device-dev/porting/Readme-CN.md
index e838579f9185afdb7da4a1f1028dedd48793689f..6881fa3d3f4952992005b1399383af66b7bc9498 100644
--- a/zh-cn/device-dev/porting/Readme-CN.md
+++ b/zh-cn/device-dev/porting/Readme-CN.md
@@ -11,7 +11,7 @@
## 代码准备
-目前OpenHarmony已经为各厂家创建了仓库并在openharmony-sig中进行孵化。参与孵化仓开发，需要使用如下方法初始化和下载代码。
+目前OpenHarmony已经为各厂家创建了仓库并在OpenHarmony-sig中进行孵化。参与孵化仓开发，需要使用如下方法初始化和下载代码。
```shell
repo init -u https://gitee.com/openharmony-sig/manifest.git -b master -m devboard.xml --no-repo-verify
diff --git a/zh-cn/device-dev/porting/porting-minichip-kernel.md b/zh-cn/device-dev/porting/porting-minichip-kernel.md
index b7917d9fff8183b0721bfa750f12b52739618197..0090640ec8c250b87c2edec6596b51668629a6e1 100644
--- a/zh-cn/device-dev/porting/porting-minichip-kernel.md
+++ b/zh-cn/device-dev/porting/porting-minichip-kernel.md
@@ -183,7 +183,7 @@ kernel/liteos_m/arch # 不同版本路径有差异
```
declare_args() {
enable_ohos_kernel_liteos_m_cppsupport = true # cpp支持
- enable_ohos_kernel_liteos_m_cpup = true # cpu占用率支持
+ enable_ohos_kernel_liteos_m_cpup = true # CPU占用率支持
enable_ohos_kernel_liteos_m_exchook = true # 异常处理支持
enable_ohos_kernel_liteos_m_kal = true # kal接口支持
enable_ohos_kernel_liteos_m_fs = true # 文件系统支持
diff --git a/zh-cn/device-dev/porting/porting-stm32f407-on-minisystem-eth.md b/zh-cn/device-dev/porting/porting-stm32f407-on-minisystem-eth.md
index 6d30ba1b1b9b0432e40659c6124a6042e05d2950..29de44f87158ba6f2d54bbe62de2a98413161f38 100644
--- a/zh-cn/device-dev/porting/porting-stm32f407-on-minisystem-eth.md
+++ b/zh-cn/device-dev/porting/porting-stm32f407-on-minisystem-eth.md
@@ -158,7 +158,7 @@ orsource "../../device/soc/*/Kconfig.liteos_m.series"
orsource "../../device/soc/*/Kconfig.liteos_m.soc"
```
-3. 在`//device/borad/talkweb`下参考如下目录结构创建相应的Kconfig文件：
+3. 在`//device/board/talkweb`下参考如下目录结构创建相应的Kconfig文件：
```
.
diff --git a/zh-cn/device-dev/subsystems/subsys-application-framework-overview.md b/zh-cn/device-dev/subsystems/subsys-application-framework-overview.md
index 89266e3b2ccd625b018c4cd848ca137075496419..94256f8699c966e78dd1b5219383bc511eb56dd1 100644
--- a/zh-cn/device-dev/subsystems/subsys-application-framework-overview.md
+++ b/zh-cn/device-dev/subsystems/subsys-application-framework-overview.md
@@ -58,7 +58,7 @@
- 配置变更导致系统暂时销毁Page并重建。
- 系统出于资源管理目的，自动触发对处于BACKGROUND状态Page的销毁。
-- **AbilityKit**：Ability框架提供给开发者的开发包，开发者基于该开发包可以开发出基于Ability组件的应用。基于Ability组件开发的应用有两种类型：基于Javascript语言开发的Ability（JS Ability）和基于C/C++语言开发的Ability（Native Ability）。JS应用开发框架是开发者开发JS Ability所用到框架，是在AbilityKit基础封装的包含JS UI组件的一套方便开发者能够迅速开发Ability应用的框架。
+- **AbilityKit**：Ability框架提供给开发者的开发包，开发者基于该开发包可以开发出基于Ability组件的应用。基于Ability组件开发的应用有两种类型：基于JavaScript语言开发的Ability（JS Ability）和基于C/C++语言开发的Ability（Native Ability）。JS应用开发框架是开发者开发JS Ability所用到框架，是在AbilityKit基础封装的包含JS UI组件的一套方便开发者能够迅速开发Ability应用的框架。
- **AbilityLoader**：负责注册和加载开发者Ability的模块。开发者开发的Ability先要调用AbilityLoader的注册接口注册到框架中，接着Ability启动时会被实例化。
diff --git a/zh-cn/device-dev/subsystems/subsys-boot-init-service.md b/zh-cn/device-dev/subsystems/subsys-boot-init-service.md
index bc80a40f813ff7648cd1e9007650bf6a8d192454..56b376389cb2cd9823b55d56c54e8408347424c5 100644
--- a/zh-cn/device-dev/subsystems/subsys-boot-init-service.md
+++ b/zh-cn/device-dev/subsystems/subsys-boot-init-service.md
@@ -70,7 +70,7 @@
进程启动时，支持在配置文件中配置服务进程的绑核、优先级、MAC信息以及AccessToken信息。
- - init提供修改\*.cfg配置文件，为服务进程提供cpu绑核功能。
+ - init提供修改\*.cfg配置文件，为服务进程提供CPU绑核功能。
- init提供修改\*.cfg配置文件，为服务进程提供优先级设置。
- init提供修改\*.cfg配置文件，为服务提供MAC信息设置，即服务的SELinux标签（需要selinux支持）。
- init提供修改\*.cfg配置文件，为服务提供设置AccessToken, 为系统服务进程设置其分布式Capability能力（仅标准系统以上提供）。
@@ -125,7 +125,7 @@
| importance | 小型系统和标准系统 |
标准系统：当前服务优先级
小型系统：标记服务重要性 |
标准系统中: 服务优先级取值范围 [-20， 19]，超出为无效设置。
小型系统中：0 : 不重启系统；非0 : 重启系统 |
| caps | 小型系统和标准系统 | 当前服务所需的capability值，根据安全子系统已支持的capability，评估所需的capability，遵循最小权限原则配置。| 类型：数字或者字符串数组，在配置数字时，按linux标准的capability进行配置。字符串时，使用标准定义的宏的名字进行配置。 |
| critical | 标准系统 | 为服务提供抑制机制，服务在配置时间 T 内，频繁重启次数超过设置次数 N 重启系统。 |
标准系统中： 类型：int[]，如："critical" : [M, N, T]，
其中M：使能标志位（0：不使能；1：使能）， N：频繁拉起服务次数， T：时间(单位：秒)。M > 0; N > 0。
小型系统中 & 标准系统中：类型：int，如："critical" : M，
其中 M：使能标志位（0：不使能；1：使能）。 默认拉起服务次数：4次， 时间：20秒 。|
- | cpucore | 标准系统 | 服务需要的绑定的cpu核心数 | 类型：int型数组， 如"cpucore" : [N1, N2, ...], N1， N2均为需要绑定的cpu核索引， 如单核设备 cpucore : [0]。 |
+ | cpucore | 标准系统 | 服务需要的绑定的CPU核心数 | 类型：int型数组， 如"cpucore" : [N1, N2, ...], N1， N2均为需要绑定的cpu核索引， 如单核设备 cpucore : [0]。 |
| d-caps | 标准系统 | 服务分布式能力。| 类型：字符串数组， 如 "d-caps" : ["OHOS_DMS"]。 |
| apl | 标准系统 | 服务能力特权级别。 | 类型：字符串， 如 "apl" : "system_core"。
目前支持"system_core"（默认值）, "normal", "system_basic"。 |
| start-mode | 标准系统 | 服务的启动模式。 | 类型：字符串， 如 "start-mode" : "condition"。
目前支持"boot", "normal", "condition"。具体说明参考：[init服务启动控制](#section56901555918)。 |
diff --git a/zh-cn/device-dev/subsystems/subsys-boot-overview.md b/zh-cn/device-dev/subsystems/subsys-boot-overview.md
index ac86a7df8e5c36b018054535b62b0090b54a526f..69fd385b94244c0c8e92c289d419ce4db1267e49 100644
--- a/zh-cn/device-dev/subsystems/subsys-boot-overview.md
+++ b/zh-cn/device-dev/subsystems/subsys-boot-overview.md
@@ -305,7 +305,7 @@
设备节点创建完成后，即可挂载对应分区，主要接口如下：
```
- int MountRequriedPartitions(const Fstab *fstab)
+ int MountRequiredPartitions(const Fstab *fstab)
{
INIT_ERROR_CHECK(fstab != NULL, return -1, "Failed fstab is NULL");
int rc;
diff --git a/zh-cn/device-dev/subsystems/subsys-build-all.md b/zh-cn/device-dev/subsystems/subsys-build-all.md
index ac3498020fbb96f7bcd4a94164df2f6b7fe9931e..8faeb4169ce64b2398f5b86c25c54125f402ea41 100644
--- a/zh-cn/device-dev/subsystems/subsys-build-all.md
+++ b/zh-cn/device-dev/subsystems/subsys-build-all.md
@@ -287,7 +287,7 @@ optional arguments:
--compact-mode compatible with standard build system set to false if we use build.sh as build entrance
--gn-args GN_ARGS specifies gn build arguments, eg: --gn-args="foo="bar" enable=true blah=7"
--keep-ninja-going keeps ninja going until 1000000 jobs fail
- --build-only-gn only do gn parse, donot run ninja
+ --build-only-gn only do gn parse, do not run ninja
--log-level LOG_LEVEL
specifies the log level during compilationyou can select three levels: debug, info and error
--fast-rebuild it will skip prepare, preloader, gn_gen steps so we can enable it only when there is no change
diff --git a/zh-cn/device-dev/subsystems/subsys-build-chip_solution.md b/zh-cn/device-dev/subsystems/subsys-build-chip_solution.md
index 23ec6c60076a63e5e0c26fd2891cda4820dbea3e..b4e39553e4a4a42e94672bfaecbf36136e571169 100644
--- a/zh-cn/device-dev/subsystems/subsys-build-chip_solution.md
+++ b/zh-cn/device-dev/subsystems/subsys-build-chip_solution.md
@@ -46,7 +46,7 @@
mkdir -p device/board/realtek/rtl8720
```
-2. 创建内核适配目录，并编写开发板编译配置config.gni文件。 以realtek的“rtl8720“开发板的liteos_a适配为例，device/board/realtek/rtl8720/liteo_a/config.gni的内容如下：
+2. 创建内核适配目录，并编写开发板编译配置config.gni文件。 以realtek的“rtl8720“开发板的liteos_a适配为例，device/board/realtek/rtl8720/liteos_a/config.gni的内容如下：
```shell
# Kernel type, e.g. "linux", "liteos_a", "liteos_m".
diff --git a/zh-cn/device-dev/subsystems/subsys-build-gn-hap-compilation-guide.md b/zh-cn/device-dev/subsystems/subsys-build-gn-hap-compilation-guide.md
index dd3fcbf4a726c36a3cc67c1d6d3d653f6aa629ec..c645347cdbb2a7de6d162e3fd2e62371378fc048 100644
--- a/zh-cn/device-dev/subsystems/subsys-build-gn-hap-compilation-guide.md
+++ b/zh-cn/device-dev/subsystems/subsys-build-gn-hap-compilation-guide.md
@@ -38,7 +38,7 @@
| js2abc | 是否需要将该HAP的js代码转换为ARK的字节码。|
| ets2abc | 是否需要将该HAP的ets代码转换为ARK的字节码。|
| certificate_profile | HAP对应的授权文件，用于签名。|
-| certificate_file | 证书文件，证书文件和授权文件，应用开发者需要去openharmony官网申请。|
+| certificate_file | 证书文件，证书文件和授权文件，应用开发者需要去OpenHarmony官网申请。|
| keystore_path | keystore文件，用于签名。|
| keystore_password | keystore的密码，用于签名。|
| key_alias | key的别名。|
diff --git a/zh-cn/device-dev/subsystems/subsys-build-module.md b/zh-cn/device-dev/subsystems/subsys-build-module.md
index 4c1ad37bc1f5b7fd218a2d27c9784faeb81ac831..060c3e8cd1de8b643d28172f663400a785f2512e 100644
--- a/zh-cn/device-dev/subsystems/subsys-build-module.md
+++ b/zh-cn/device-dev/subsystems/subsys-build-module.md
@@ -1,7 +1,7 @@
# 模块
## 模块配置规则
-编译子系统通过模块、部件和产品三层配置来实现编译和打包。模块就是编译子系统的一个目标，包括（动态库、静态库、配置文件、预编译模块等）。模块要定义属于哪个部件，一个模块只能归属于一个部件。Openharmony使用定制化的Gn模板来配置模块规则，Gn语法相关的基础知识请参考[官网手册](https://gn.googlesource.com/gn/+/main/docs/reference.md)。
+编译子系统通过模块、部件和产品三层配置来实现编译和打包。模块就是编译子系统的一个目标，包括（动态库、静态库、配置文件、预编译模块等）。模块要定义属于哪个部件，一个模块只能归属于一个部件。OpenHarmony使用定制化的Gn模板来配置模块规则，Gn语法相关的基础知识请参考[官网手册](https://gn.googlesource.com/gn/+/main/docs/reference.md)。
以下是常用的模块配置规则：
diff --git a/zh-cn/device-dev/subsystems/subsys-toolchain-hdc-guide.md b/zh-cn/device-dev/subsystems/subsys-toolchain-hdc-guide.md
index 679209f76d8a7cf233891e62761057cacdfdb30b..3adc1b4f8bdbf1a9384a3279bf47c21dabffff40 100644
--- a/zh-cn/device-dev/subsystems/subsys-toolchain-hdc-guide.md
+++ b/zh-cn/device-dev/subsystems/subsys-toolchain-hdc-guide.md
@@ -279,7 +279,7 @@ hdc_std -s severIP:8710 list targets
```
- **tmode usb**
- 执行后设备端对应daemon进程重启，并首先选用usb连接方式。
+ 执行后设备端对应daemon进程重启，并首先选用USB连接方式。
**表10** 命令说明
@@ -297,7 +297,7 @@ hdc_std -s severIP:8710 list targets
```
- **tmode port port-number**
- 执行后设备端对应daemon进程重启，并优先使用网络方式连接设备，如果连接设备失败，再选择usb连接。
+ 执行后设备端对应daemon进程重启，并优先使用网络方式连接设备，如果连接设备失败，再选择USB连接。
**表11** 命令说明
diff --git a/zh-cn/device-dev/subsystems/subsys-toolchain-hiperf.md b/zh-cn/device-dev/subsystems/subsys-toolchain-hiperf.md
index b6c2765d8206ab2cc2f6779ff2d4288f9ba873e0..461e3f1dcd4036741d1bf5721c86789c0098262f 100644
--- a/zh-cn/device-dev/subsystems/subsys-toolchain-hiperf.md
+++ b/zh-cn/device-dev/subsystems/subsys-toolchain-hiperf.md
@@ -138,8 +138,8 @@ Usage: hiperf record [options]
| --no-inherit | 不监听目标线程或者进程启动的子线程。 |
| -p | 指定需要监听的进程。 |
| -t | 指定需要监听的线程。 |
-| --offcpu | 监听cpu调度事件，它等价于 --period 1 -e sched:sched_switch 事件。 |
-| -j <_branch_filter1_>[,_branch_filter2_]... | 监听分支预测事件。分支预测就是指令存在多个if else判定的情况下，cpu去预测下一步即将执行哪一条指令。 |
+| --offcpu | 监听CPU调度事件，它等价于 --period 1 -e sched:sched_switch 事件。 |
+| -j <_branch_filter1_>[,_branch_filter2_]... | 监听分支预测事件。分支预测就是指令存在多个if else判定的情况下，CPU去预测下一步即将执行哪一条指令。 |
| -s / --call-stack <_fp \\| dwarf[,size]_> | 设置用户栈的回栈方式，支持fp和dwarf两种方式。dwarf 后面可以指定采样的用户堆栈大小，默认是 65528。 |
| --delay-unwind | 延迟回栈，等到采样结束再进行回栈。 |
| --disable-unwind | 不进行回栈，用户的寄存器和堆栈数据会保存在perf.data中，供离线回栈使用。 |