diff --git a/doc/developer-guides/hld/index.rst b/doc/developer-guides/hld/index.rst
index 973e01cd8..33ccd0ea6 100644
--- a/doc/developer-guides/hld/index.rst
+++ b/doc/developer-guides/hld/index.rst
@@ -3,10 +3,10 @@
 High-Level Design Guides
 ########################
 
-The ACRN Hypervisor acts as a host with full control of the processors
+The ACRN hypervisor acts as a host with full control of the processors
 and the hardware (physical memory, interrupt management, and I/O). It
-provides the User OS with an abstraction of a virtual platform, allowing
-the guest to behave as if it were executing directly on a physical
+provides the guest VM with an abstraction of a virtual platform, allowing
+the guest VM to behave as if it were executing directly on a physical
 processor.
 
 These chapters describe the ACRN architecture, high-level design,
diff --git a/doc/introduction/index.rst b/doc/introduction/index.rst
index 576d0d35f..107d6a41c 100644
--- a/doc/introduction/index.rst
+++ b/doc/introduction/index.rst
@@ -158,7 +158,7 @@ the Service VM since they may rely on its mediation services for device access.
 The Service VM owns most of the devices including the platform devices, and
 provides I/O mediation. The notable exceptions are the devices assigned to the
 pre-launched User VM. Some PCIe devices may be passed through to the
-post-launched User OSes via the VM configuration.
+post-launched User VMs via the VM configuration.
 
 The ACRN hypervisor also runs the ACRN VM manager to collect running
 information of the User VMs, and controls the User VMs such as starting,