diff --git a/en/application-dev/application-models/hop-cross-device-migration.md b/en/application-dev/application-models/hop-cross-device-migration.md
index d26f4b452febf4e7683e319e703ac350f0525857..12c1739060ecc51f0234e13a7c23fc54ed1d80f8 100644
--- a/en/application-dev/application-models/hop-cross-device-migration.md
+++ b/en/application-dev/application-models/hop-cross-device-migration.md
@@ -75,7 +75,7 @@ The table below describes the main APIs used for cross-device migration. For det
Configure the application launch type. For details, see [UIAbility Component Launch Type](uiability-launch-type.md).
4. Implement [onContinue()](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncontinue) in the UIAbility of the initiator.
- [onContinue()](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncontinue) is called on the initiator. You can save the data in this method to implement application compatibility check and migration decision.
+ [onContinue()](../reference/apis/js-apis-app-ability-uiAbility.md#abilityoncontinue) is called on the initiator. You can save the data in this method to implement application compatibility check and migration decision.
- Saving migrated data: You can save the data to be migrated in key-value pairs in **wantParam**.
- Checking application compatibility: You can obtain the version number of the target application from **wantParam** and check the compatibility between the target application and the current application.
diff --git a/en/application-dev/napi/purgeable-memory-guidelines.md b/en/application-dev/napi/purgeable-memory-guidelines.md
index 706786d429b492f79f86c4c108cf8e3e63940def..fb35ff1d30a6f0e02e69bf68bfa4e1721eaf9589 100644
--- a/en/application-dev/napi/purgeable-memory-guidelines.md
+++ b/en/application-dev/napi/purgeable-memory-guidelines.md
@@ -75,7 +75,7 @@ The following steps describe how to use the native purgeable memory APIs to appl
OH_PurgeableMemory* pPurgmem = OH_PurgeableMemory_Create(DATASIZE, FactorialFunc, &pdata);
```
-3. Perfrom a read operation on the **PurgeableMemory** object.
+3. Perform a read operation on the **PurgeableMemory** object.
```c++
// Define an object type based on the service requirements.
class ReqObj;
diff --git a/en/application-dev/reference/apis/js-apis-buffer.md b/en/application-dev/reference/apis/js-apis-buffer.md
index f50bdfe83cca98808fbb79237bd21194ec30b7a4..3542b213ddb8f76303337083d875db1ad5958414 100644
--- a/en/application-dev/reference/apis/js-apis-buffer.md
+++ b/en/application-dev/reference/apis/js-apis-buffer.md
@@ -1162,7 +1162,7 @@ let result = buf1.writeFloatLE(0xcabcbcbc, 0);
readInt8(offset?: number): number
-Reads a 8-bit signed integer from this **Buffer** instance at the specified offset.
+Reads an 8-bit signed integer from this **Buffer** instance at the specified offset.
**System capability**: SystemCapability.Utils.Lang
@@ -1449,7 +1449,7 @@ let result = buf1.writeIntLE(0x123456789011, 0, 6);
readUInt8(offset?: number): number
-Reads a 8-bit unsigned integer from this **Buffer** instance at the specified offset.
+Reads an 8-bit unsigned integer from this **Buffer** instance at the specified offset.
**System capability**: SystemCapability.Utils.Lang
@@ -2326,7 +2326,7 @@ let result = buf.writeFloatLE(0xcafebabe, 0);
writeInt8(value: number, offset?: number): number
-Writes a 8-bit signed integer to this **Buffer** instance at the specified offset.
+Writes an 8-bit signed integer to this **Buffer** instance at the specified offset.
**System capability**: SystemCapability.Utils.Lang
@@ -2606,7 +2606,7 @@ let result = buf.writeIntLE(0x1234567890ab, 0, 6);
writeUInt8(value: number, offset?: number): number
-Writes a 8-bit unsigned integer to this **Buffer** instance at the specified offset.
+Writes an 8-bit unsigned integer to this **Buffer** instance at the specified offset.
**System capability**: SystemCapability.Utils.Lang
diff --git a/en/application-dev/reference/apis/js-apis-image.md b/en/application-dev/reference/apis/js-apis-image.md
index f3f4531585703f266dc3e13a3959d8ca64ce1e66..a098cef0c801348beeb9a0b43dfecfb19232e8e4 100644
--- a/en/application-dev/reference/apis/js-apis-image.md
+++ b/en/application-dev/reference/apis/js-apis-image.md
@@ -2837,7 +2837,7 @@ Describes the color components of an image.
## Supplementary Information
### SVG Tags
-The SVG tags are supported since API verison 10. The used version is (SVG) 1.1. Currently, the following tags are supported:
+The SVG tags are supported since API version 10. The used version is (SVG) 1.1. Currently, the following tags are supported:
- a
- circla
- clipPath
diff --git a/en/application-dev/reference/apis/js-apis-util.md b/en/application-dev/reference/apis/js-apis-util.md
index c049c8f2a2a4a3cc3a37bc47c5672da9cb4bb3fe..940b37ae2ad177ae64adaa6caeef0884f4dd2c8f 100755
--- a/en/application-dev/reference/apis/js-apis-util.md
+++ b/en/application-dev/reference/apis/js-apis-util.md
@@ -683,7 +683,7 @@ Encodes the input content.
## RationalNumber8+
-Provides APIs to compare rational numbers and obtain numerators and denominators. For example, the **toString()** API can be used to convert a rational number into a strings.
+Provides APIs to compare rational numbers and obtain numerators and denominators. For example, the **toString()** API can be used to convert a rational number into a string.
### constructor9+
diff --git a/en/application-dev/tools/packing-tool.md b/en/application-dev/tools/packing-tool.md
index dd219250333636f96f715530b3ef8c86f0810223..9122bded7287fd0cd5538e337f406ca481c55ab4 100644
--- a/en/application-dev/tools/packing-tool.md
+++ b/en/application-dev/tools/packing-tool.md
@@ -1,7 +1,7 @@
# Packing Tool
## Overview
-The packing tool packs compiled files for installation and release. The packing tool supports the generation of HAP (an application package), APP (application set to launch to the application market), HQF (quick fix package), APPQF (quick fix package to launch to the application market ), HAR (static shared library), and HSP (dynamic shared library) files. The unpacking tool is used to unpack the HAP, APP, HQF, APPQF, HAR, and HSP files and parse the HAP, HSP, APP, and APPQF files. Generally, the packing process is automatically carried out in DevEco Studio. However, you can also use the JAR package of the packing tool to pack files. The JAR package is stored in the **toolchains** directory in the SDK path.
+The packing tool packs compiled files for installation and release. The packing tool supports the generation of HAP (an application package), APP (application set to launch to the application market), HQF (quick fix package), APPQF (quick fix package to launch to the application market), HAR (statically shared library), and HSP (dynamically shared library) files. The unpacking tool is used to unpack the HAP, APP, HQF, APPQF, HAR, and HSP files and parse the HAP, HSP, APP, and APPQF files. Generally, the packing process is automatically carried out in DevEco Studio. However, you can also use the JAR package of the packing tool to pack files. The JAR package is stored in the **toolchains** directory in the SDK path.
## Packing Commands
diff --git a/en/application-dev/tools/unpacking-tool.md b/en/application-dev/tools/unpacking-tool.md
index 008b3d67ec2eafe4c4c6a6d16f7028768f6dcbab..3b9571faaf6ac451a4e261037289aca664f6ecf6 100644
--- a/en/application-dev/tools/unpacking-tool.md
+++ b/en/application-dev/tools/unpacking-tool.md
@@ -1,7 +1,7 @@
# Unpacking Tool
-The unpacking tool is a commissioning tool used to unpack HAP (an application package), HAR (static shared library), HSP (dynamic shared library), and APP (application set to launch to the application market) files. It also provides Java APIs to parse the HAP, APP, and HSP files.
+The unpacking tool is a commissioning tool used to unpack HAP (an application package), HAR (statically shared library), HSP (dynamically shared library), and APP (application set to launch to the application market) files. It also provides Java APIs to parse the HAP, APP, and HSP files.
The **app_unpacking_tool.jar** package can be found in the OpenHarmony SDK downloaded locally.