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/tutorials/acrn-secure-boot-with-grub.rst

@@ -243,7 +243,7 @@ Creating UEFI Secure Boot Key
 The keys to be enrolled in UEFI firmware: :file:`PK.der`, :file:`KEK.der`, :file:`db.der`.
 The keys to sign bootloader image: :file:`grubx64.efi`, :file:`db.key` , :file:`db.crt`.
 
-Sign GRUB Image With Db Key
+Sign GRUB Image With db Key
 ===========================
 
     sbsign --key db.key --cert db.crt path/to/grubx64.efi

doc/tutorials/enable_ivshmem.rst

@@ -1,6 +1,6 @@
 .. _enable_ivshmem:
 
-Enable Inter-Vm Communication Based on Ivshmem
+Enable Inter-VM Communication Based on Ivshmem
 ##############################################
 
 You can use inter-VM communication based on the ``ivshmem`` dm-land
@@ -9,7 +9,7 @@ solution or hv-land solution, according to the usage scenario needs.
 While both solutions can be used at the same time, VMs using different
 solutions cannot communicate with each other.
 
-Ivshmem Dm-Land Usage
+Ivshmem DM-Land Usage
 *********************
 
 Add this line as an ``acrn-dm`` boot parameter::
@@ -35,7 +35,7 @@ where
 
 .. _ivshmem-hv:
 
-Ivshmem Hv-Land Usage
+Ivshmem HV-Land Usage
 *********************
 
 The ``ivshmem`` hv-land solution is disabled by default in ACRN. You
@@ -94,10 +94,10 @@ to applications.
 .. note:: Notification is supported only for HV-land ivshmem devices. (Future
    support may include notification for DM-land ivshmem devices.)
 
-Inter-Vm Communication Examples
+Inter-VM Communication Examples
 *******************************
 
-Dm-Land Example
+DM-Land Example
 ===============
 
 This example uses dm-land inter-VM communication between two
@@ -167,7 +167,7 @@ Linux-based post-launched VMs (VM1 and VM2).
    - For VM1 use ``ls -lh /sys/bus/pci/devices/0000:00:06.0/uio``
    - For VM2 use ``ls -lh /sys/bus/pci/devices/0000:00:05.0/uio``
 
-Hv-Land Example
+HV-Land Example
 ===============
 
 This example uses hv-land inter-VM communication between two

doc/tutorials/realtime_performance_tuning.rst

@@ -9,7 +9,7 @@ real-time performance analysis. Two parts are included:
 - Method to trace ``vmexit`` occurrences for analysis.
 - Method to collect Performance Monitoring Counters information for tuning based on Performance Monitoring Unit, or PMU.
 
-Vmexit Analysis for ACRN RT Performance
+vmexit Analysis for ACRN RT Performance
 ***************************************
 
 ``vmexit`` are triggered in response to certain instructions and events and are
@@ -149,7 +149,7 @@ Note that Precise Event Based Sampling (PEBS) is not yet enabled in the VM.
       value64 = hva2hpa(vcpu->arch.msr_bitmap);
       exec_vmwrite64(VMX_MSR_BITMAP_FULL, value64);
 
-Perf/Pmu Tools in Performance Analysis
+Perf/PMU Tools in Performance Analysis
 ======================================
 
 After exposing PMU-related CPUID/MSRs to the VM, performance analysis tools

doc/tutorials/trustyACRN.rst

@@ -256,7 +256,7 @@ section, we'll focus on two major components:
 See :ref:`trusty_tee` for additional details of Trusty implementation in
 ACRN.
 
-One-Vm, Two-Worlds
+One-VM, Two-Worlds
 ==================
 
 As previously mentioned, Trusty Secure Monitor could be any

doc/tutorials/using_windows_as_uos.rst

@@ -257,7 +257,7 @@ ACRN Windows Verified Feature List
                    , "Microsoft Store",              "OK"
                    , "3D Viewer",                    "OK"
 
-Explanation for Acrn-Dm Popular Command Lines
+Explanation for acrn-dm Popular Command Lines
 *********************************************
 
 .. note:: Use these acrn-dm command line entries according to your

doc/tutorials/using_yp.rst

@@ -16,7 +16,7 @@ components, and software components.  Layers are repositories containing
 related sets of instructions that tell the Yocto Project build system
 what to do.
 
-The Meta-Acrn Layer
+The meta-acrn Layer
 *******************
 
 The meta-acrn layer integrates the ACRN hypervisor with OpenEmbedded,