doc: update another few mis-handled titles

After grand update of all titles to use title-case, we found some more
that needed a manual tweak.

Signed-off-by: Geoffroy Van Cutsem <geoffroy.vancutsem@intel.com>

doc/developer-guides/hld/hld-devicemodel.rst

@@ -302,7 +302,7 @@ hypercall to the hypervisor. There are two exceptions:
 
    Architecture of ACRN VHM
 
-VHM Ioctl Interfaces
+VHM ioctl Interfaces
 ====================
 
 .. note:: Reference API documents for General interface, VM Management,

doc/developer-guides/hld/hld-trace-log.rst

@@ -30,7 +30,7 @@ is allowed to put data into that sbuf in HV, and a single consumer is
 allowed to get data from sbuf in Service VM. Therefore, no lock is required to
 synchronize access by the producer and consumer.
 
-Sbuf APIs
+sbuf APIs
 =========
 
 The sbuf APIs are defined in ``hypervisor/include/debug/sbuf.h``.

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

@@ -608,7 +608,7 @@ APIs Provided by VBS-K Modules in Service OS
                virtio_vqs_index_get
                virtio_dev_reset
 
-VHOST APIS
+VHOST APIs
 ==========
 
 APIs Provided by DM

doc/developer-guides/hld/hv-partitionmode.rst

@@ -123,7 +123,7 @@ e820 info for all the guests.
 | RESERVED               |
 +------------------------+
 
-Platform Info - Mptable
+Platform Info - mptable
 =======================
 
 ACRN, in partition mode, uses mptable to convey platform info to each
@@ -181,15 +181,15 @@ the Service VM startup in sharing mode.
 Inter-Processor Interrupt (IPI) Handling
 ========================================
 
-Guests W/O LAPIC Passthrough
-----------------------------
+Guests Without LAPIC Passthrough
+--------------------------------
 
 For guests without LAPIC passthrough, IPIs between guest CPUs are handled in
 the same way as sharing mode in ACRN. Refer to :ref:`virtual-interrupt-hld`
 for more details.
 
-Guests W/ LAPIC Passthrough
----------------------------
+Guests With LAPIC Passthrough
+-----------------------------
 
 ACRN supports passthrough if and only if the guest is using x2APIC mode
 for the vLAPIC. In LAPIC passthrough mode, writes to the Interrupt Command
@@ -291,8 +291,8 @@ writes are discarded.
 Interrupt Delivery
 ==================
 
-Guests W/O LAPIC Passthrough
-----------------------------
+Guests Without LAPIC Passthrough
+--------------------------------
 
 In partition mode of ACRN, interrupts stay disabled after a vmexit.  The
 processor does not take interrupts when it is executing in VMX root
@@ -307,8 +307,8 @@ for device interrupts.
    :align: center
 
 
-Guests W/ LAPIC Passthrough
----------------------------
+Guests With LAPIC Passthrough
+-----------------------------
 
 For guests with LAPIC passthrough, ACRN does not configure vmexit upon
 external interrupts. There is no vmexit upon device interrupts and they are
@@ -320,13 +320,13 @@ Hypervisor IPI Service
 ACRN needs IPIs for events such as flushing TLBs across CPUs, sending virtual
 device interrupts (e.g. vUART to vCPUs), and others.
 
-Guests W/O LAPIC Passthrough
-----------------------------
+Guests Without LAPIC Passthrough
+--------------------------------
 
 Hypervisor IPIs work the same way as in sharing mode.
 
-Guests W/ LAPIC Passthrough
----------------------------
+Guests With LAPIC Passthrough
+-----------------------------
 
 Since external interrupts are passthrough to the guest IDT, IPIs do not
 trigger vmexit. ACRN uses NMI delivery mode and the NMI exiting is
@@ -344,8 +344,8 @@ For a guest console in partition mode, ACRN provides an option to pass
 ``vmid`` as an argument to ``vm_console``. vmid is the same as the one
 developers use in the guest configuration.
 
-Guests W/O LAPIC Passthrough
-----------------------------
+Guests Without LAPIC Passthrough
+--------------------------------
 
 Works the same way as sharing mode.
 

doc/developer-guides/hld/ivshmem-hld.rst

@@ -1,6 +1,6 @@
 .. _ivshmem-hld:
 
-ACRN Shared Memory Based Inter-Vm Communication
+ACRN Shared Memory Based Inter-VM Communication
 ###############################################
 
 ACRN supports inter-virtual machine communication based on a shared
@@ -8,7 +8,7 @@ memory mechanism. The ACRN device model or hypervisor emulates a virtual
 PCI device (called an ``ivshmem`` device) to expose the base address and
 size of this shared memory.
 
-Inter-Vm Communication Overview
+Inter-VM Communication Overview
 *******************************
 
 .. figure:: images/ivshmem-architecture.png
@@ -129,11 +129,11 @@ Usage
 
 For usage information, see :ref:`enable_ivshmem`
 
-Inter-Vm Communication Security Hardening (BKMs)
+Inter-VM Communication Security Hardening (BKMs)
 ************************************************
 
 As previously highlighted, ACRN 2.0 provides the capability to create shared
-memory regions between Post-Launch user VMs known as "Inter-VM Communication".
+memory regions between Post-Launched User VMs known as "Inter-VM Communication".
 This mechanism is based on ivshmem v1.0 exposing virtual PCI devices for the
 shared regions (in Service VM's memory for this release). This feature adopts a
 community-approved design for shared memory between VMs, following same

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

@@ -35,7 +35,7 @@ The feature bits supported by the BE device are shown as follows:
   Device can toggle its cache between writeback and writethrough modes.
 
 
-Virtio-BLK-Be Design
+Virtio-BLK BE Design
 ********************
 
 .. figure:: images/virtio-blk-image02.png

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

@@ -1,6 +1,6 @@
  .. _virtio-gpio:
 
-Virtio-Gpio
+Virtio-GPIO
 ###########
 
 virtio-gpio provides a virtual GPIO controller, which will map part of

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

@@ -1,6 +1,6 @@
 .. _virtio-i2c:
 
-Virtio-I2c
+Virtio-I2C
 ##########
 
 Virtio-i2c provides a virtual I2C adapter that supports mapping multiple