diff --git a/docs/en/docs/ApplicationDev/using-gcc-for-compilation.md b/docs/en/docs/ApplicationDev/using-gcc-for-compilation.md
index 84997d895bba8099d2bc4a18020fbc4f2b37ed07..cffaff6ece7f3dddf5cfe21167b5f99e2da3c423 100644
--- a/docs/en/docs/ApplicationDev/using-gcc-for-compilation.md
+++ b/docs/en/docs/ApplicationDev/using-gcc-for-compilation.md
@@ -254,7 +254,7 @@ A library is mature and reusable code that has been written for use. Each progra
 
 The library file name is prefixed with lib and suffixed with .so \(dynamic library\) or .a \(static library\). The middle part is the user-defined library file name, for example, libfoo.so or libfoo.a. Because all library files comply with the same specifications, the  **lib**  prefix can be omitted when the  **-l**  option specifies the name of the linked library file. That is, when GCC processes  **-lfoo**, the library file  **libfoo.so**  or  **libfoo.a**  is automatically linked. When creating a library, you must specify the full file name  **libfoo.so**  or  **libfoo.a**.
 
-Libraries are classified into static libraries and dynamic libraries based on the linking time. The static library links and packs the target file .o generated by assembly and the referenced library into an executable file in the linking phase. The dynamic library is not linked to the target code when the program is compiled, but is loaded when the program is run. The differences are as follows:
+Libraries are classified into static libraries and dynamic libraries based on the linking time. The static library links and packs the target file .o generated by assembly and the referenced library into an executable file in the linking phase. The dynamic library is not linked to the target code when the program is compiled, but is loaded when the program is run. The differences are as follows.
 
 - The resource usage is different.