diff --git a/en/Development-And-Common-Documents/KVM_Virtual_Machines.md b/en/Development-And-Common-Documents/KVM_Virtual_Machines.md
index 9a4f1f67..6cb86e5e 100644
--- a/en/Development-And-Common-Documents/KVM_Virtual_Machines.md
+++ b/en/Development-And-Common-Documents/KVM_Virtual_Machines.md
@@ -101,15 +101,15 @@ Open the virt-manager GUI by typing `sudo virt-manager` in the terminal or click
 
 ![](./assets/KVM/addstep1.png)
 
-2) Select the installation source (ISO) and virtual machine system format (such as red hat Linux 8 or something like that) and click forward
+2) Select the installation source (ISO) and virtual machine system format (such as red hat Linux 8 or something like that) and click forward.
 
 ![](./assets/KVM/addstep2.png)
 
-3) Enter the virtual machine memory, the number of cpu cores (can not be greater than the number of host cores), click forward
+3) Enter the virtual machine memory, the number of cpu cores (can not be greater than the number of host cores), click forward.
 
 ![](./assets/KVM/addstep3.png)
 
-4) Select the disk image (virtual machine installation should also have a virtual disk, right), here we create a 40G disk, click forward
+4) Select the disk image (virtual machine installation should also have a virtual disk, right), here we create a 40G disk, click forward.
 
 > Note: The default disk image path here is /var/lib/libirt/images/*.qcow2, while if we need to use an already created disk image or need to customize the storage location of the disk image, you can select "Select or create custom storage"
 
@@ -121,7 +121,7 @@ Open the virt-manager GUI by typing `sudo virt-manager` in the terminal or click
 
 ![](./assets/KVM/addstep5.png)
 
-6) At this point, it is time to enter the installation of the virtual machine system
+6) At this point, it is time to enter the installation of the virtual machine system.
 
 ![](./assets/KVM/ossetup.png)
 
@@ -224,7 +224,7 @@ You can find that the storage space has changed back to 196K.
 
 > 2. Mount the qcow2 disk image on the host system
 
-qcow2 is essentially a virtual disk image, so the contents of this disk image partition can be read on the host system by mounting the disk image partition (if it is a virtual machine disk, you need to operate with the virtual machine turned off).
+qcow2 is essentially a virtual disk image, so the contents of this disk image partition can be read on the host system by mounting the disk image partition (in the case of a virtual machine disk, this needs to be done with the virtual machine turned off).
 
 
 > 3. When creating a virtual machine, there is a prompt that the 'libvirt-qemu' user does not have permission to search for directory-related records, and the creation is unsuccessful.