doc: fix doc misspellings

Fix documentation misspellings missed during the regular review.

Signed-off-by: David B. Kinder <david.b.kinder@intel.com>

doc/developer-guides/hld/hld-power-management.rst

@@ -86,7 +86,7 @@ Intercept Policy
 ================
 
 Hypervisor should be able to restrict guest's
-P/C-state request, with a user-customized poligy.
+P/C-state request, with a user-customized policy.
 
 Hypervisor should intercept guest P-state request and validate whether
 it is a valid P-state. Any invalid P-state (e.g. doesn't exist in CPU state

doc/developer-guides/hld/hld-virtio-devices.rst

@@ -377,7 +377,7 @@ Irqfd implementation
 
 The irqfd module is implemented in VHM, and can enhance an registered
 eventfd to inject an interrupt to a guest OS when the eventfd gets
-signalled. :numref:`irqfd-workflow` shows the general flow for irqfd.
+signaled. :numref:`irqfd-workflow` shows the general flow for irqfd.
 
 .. figure:: images/virtio-hld-image60.png
    :align: center

doc/developer-guides/hld/hld-vm-management.rst

@@ -102,7 +102,7 @@ IOC to keep doing this power cycle method, or change to another power
 cycle method. SOS-LCS heartbeat can also set RTC timer to IOC.
 
 SOS-LCS handles SHUTDOWN, SUSPEND, and REBOOT acrn-manager messages
-request from Acrnd. When these messages are received, SOS-LCS switchs IOC
+request from Acrnd. When these messages are received, SOS-LCS switches IOC
 power cycle method to shutdown, suspend, and reboot, respectively.
 
 SOS-LCS handles WAKEUP_REASON acrn-manager messages request from Acrnd.

doc/developer-guides/hld/virtio-blk.rst

@@ -51,7 +51,7 @@ writethrough is set as the default mode, as it can make sure every write
 operation queued to the virtio-blk FE driver layer is submitted to
 hardware storage.
 
-During initialization, virito-blk will allocate 64 ioreq buffers in a
+During initialization, virtio-blk will allocate 64 ioreq buffers in a
 shared ring used to store the I/O requests.  The freeq, busyq, and pendq
 shown in :numref:`virtio-blk-be` are used to manage requests. Each
 virtio-blk device starts 8 worker threads to process request

doc/developer-guides/l1tf.rst

@@ -61,7 +61,7 @@ There are mainly three attack scenarios considered in ACRN:
 - Normal_world -> secure_world attack (Android specific)
 
 Malicious user space is not a concern to ACRN hypervisor, because
-every guest runs in VMX non-root. It is reponsibility of guest kernel
+every guest runs in VMX non-root. It is responsibility of guest kernel
 to protect itself from malicious user space attack.
 
 Intel® SGX/SMM related attacks are mitigated by using latest microcode.
@@ -197,7 +197,7 @@ guests and then put these virtual seeds into uncached memory,
 at the same time flush & erase physical seed.
 
 If all security data are identified and put in uncached
-meomry in a specific deployment, then it is not necessary to
+memory in a specific deployment, then it is not necessary to
 prevent guest -> hypervisor attack, since there is nothing
 useful to be attacked.
 
@@ -223,7 +223,7 @@ Core-based scheduling
 
 If Hyper-Threading is enabled, it's important to avoid running
 sensitive context (if containing security data which a given VM
-has no premission to access) on the same physical core that runs
+has no permission to access) on the same physical core that runs
 said VM. It requires scheduler enhancement to enable core-based
 scheduling policy, so all threads on the same core are always
 scheduled to the same VM. Also there are some further actions

doc/developer-guides/modularity.rst

@@ -58,7 +58,7 @@ Measuring Complexity
 ====================
 
 ACRN uses the number of functions and the cyclomatic complexity [CC]_ of each
-function to measure the complexity of a module. Concrete criterias on complexity
+function to measure the complexity of a module. Concrete criteria on complexity
 will be determined while enhancing the modularity of the hypervisor. The current
 recommendation is to limit the cyclomatic complexity of a function under 20.