diff --git a/doc/services/virtualization/ivshmem.rst b/doc/services/virtualization/ivshmem.rst
index 7da8e05bf5e..673b083794c 100644
--- a/doc/services/virtualization/ivshmem.rst
+++ b/doc/services/virtualization/ivshmem.rst
@@ -16,7 +16,7 @@ it might be necessary to make VMs aware of each other, or aware of the host.
 This is made possible by exposing a shared memory among parties via a feature
 called ivshmem, which stands for inter-VM Shared Memory.
 
-The Two types are supported: a plain shared memory (ivshmem-plain) or a shared
+The two types are supported: a plain shared memory (ivshmem-plain) or a shared
 memory with the ability for a VM to generate an interruption on another, and
 thus to be interrupted as well itself (ivshmem-doorbell).
 
@@ -26,13 +26,13 @@ Please refer to the official `Qemu ivshmem documentation
 Support
 *******
 
-Zephyr supports both version: plain and doorbell. Ivshmem driver can be build
+Zephyr supports both versions: plain and doorbell. Ivshmem driver can be built
 by enabling :kconfig:option:`CONFIG_IVSHMEM`. By default, this will expose the plain
 version. :kconfig:option:`CONFIG_IVSHMEM_DOORBELL` needs to be enabled to get the
 doorbell version.
 
 Because the doorbell version uses MSI-X vectors to support notification vectors,
-the :kconfig:option:`CONFIG_IVSHMEM_MSI_X_VECTORS` has to be tweaked to the amount of
+the :kconfig:option:`CONFIG_IVSHMEM_MSI_X_VECTORS` has to be tweaked to the number of
 vectors that will be needed.
 
 Note that a tiny shell module can be exposed to test the ivshmem feature by