!1264 PR1227已完成，请审核

Merge pull request !1264 from Annie_wang/OpenHarmony-3.0-LTS

en/device-dev/kernel/kernel-mini-extend-file-littlefs-guide.md

@@ -2,7 +2,7 @@
 
 -   [Sample Code](#section1034515054620)
 
-When porting LittleFS to a new hardware device, you need to declare  **lfs\_config**:
+Before porting LittleFS to a new hardware device, declare  **lfs\_config**:
 
 ```
 const struct lfs_config cfg = {
@@ -23,15 +23,15 @@ const struct lfs_config cfg = {
 };
 ```
 
-**.read**,  **.prog**,  **.erase**, and  **.sync**  correspond to the read, write, erase, and synchronization APIs at the bottom layer of the hardware platform, respectively.
+**.read**,  **.prog**,  **.erase**, and  **.sync**  correspond to the underlying read, write, erase, and synchronization APIs of the hardware platform, respectively.
 
-**read\_size**  indicates the number of bytes read each time. You can set it to a value greater than the physical read unit to improve performance. This value determines the size of the read cache. However, if the value is too large, more memory is consumed.
+**read\_size** indicates the number of bytes read each time. You can set it to a value greater than the physical read unit to improve performance. This value determines the size of the read cache. However, if the value is too large, more memory is consumed.
 
-**prog\_size**  indicates the number of bytes written each time. You can set it to a value greater than the physical write unit to improve performance. This value determines the size of the write cache and must be an integral multiple of  **read\_size**. However, if the value is too large, more memory is consumed.
+**prog\_size** indicates the number of bytes written each time. You can set it to a value greater than the physical write unit to improve performance. This value determines the size of the write cache and must be an integral multiple of **read\_size**. However, if the value is too large, more memory is consumed.
 
-**block\_size**: indicates the number of bytes in each erase block. The value can be greater than that of the physical erase unit. However, a smaller value is recommended because each file occupies at least one block. The value must be an integral multiple of  **prog\_size**.
+**block\_size** indicates the number of bytes in each erase block. The value can be greater than that of the physical erase unit. However, a smaller value is recommended because each file occupies at least one block. The value must be an integral multiple of **prog\_size**.
 
-**block\_count**  indicates the number of blocks that can be erased, which depends on the capacity of the block device and the size of the block to be erased \(**block\_size**\).
+**block\_count** indicates the number of blocks that can be erased, which depends on the capacity of the block device and the size of the block to be erased \(**block\_size**\).
 
 ## Sample Code<a name="section1034515054620"></a>
 

en/device-dev/subsystems/subsys-build-mini-lite.md

@@ -623,7 +623,7 @@ The following uses the RTL8720 development board provided by Realtek as an examp
 
 2.  Create a directory for kernel adaptation and build the  **config.gni**  file of the development board.
 
-    For example, to adapt the LiteOS Cortex-M kernel to the RTL8720 development board, configure the  **device/realtek/rtl8720/liteos\_a/config.gni**  file as follows:
+    For example, to adapt the LiteOS-A kernel to the RTL8720 development board, configure the  **device/realtek/rtl8720/liteos\_a/config.gni**  file as follows:
 
     ```
     # Kernel type, e.g. "linux", "liteos_a", "liteos_m".