Modified content based on Tanja's feedback

xml/utilities.xml

@@ -480,27 +480,27 @@ Average:    92.08    211.70 1097.30     0.26 12010.28      0.00      0.00      0
       The value should not drop below 30.
      </para>
      <note>
-      <title>Understanding and addressing %vmeff values exceeding 100% in modern Linux
+      <title>Understanding and addressing <guimenu>%vmeff</guimenu> values exceeding 100% in modern Linux
       kernels</title>
       <para>
-       A %vmeff value exceeding 100% means that the number of pages reclaimed (pgsteal) is reported
-       as higher than the number of pages scanned (pgscank) during memory reclamation. This is
+       A <guimenu>%vmeff</guimenu> value exceeding 100% means that the number of pages reclaimed (<guimenu>pgsteal</guimenu>) is reported
+       as higher than the number of pages scanned (<guimenu>pgscank</guimenu>) during memory reclamation. This is
        unexpected because under normal circumstances, the kernel should not reclaim more pages than it scans.
       </para>
       <para>
        In modern Linux kernels (5.x and higher), changes in memory management and page reclamation
-       accounting make %vmeff less reliable as a measure of virtual memory efficiency. These
+       accounting make <guimenu>%vmeff</guimenu> less reliable as a measure of virtual memory efficiency. These
        changes include separating background and direct reclaim metrics, tracking memory operations
        with greater granularity, introducing deferred reclamation, and adding support for NUMA-aware
        and cgroup-based memory management. Such updates can cause tools like <command>sar</command>
-       to misinterpret metrics like pgsteal and pgscank, resulting in %vmeff value
+       to misinterpret metrics like <guimenu>pgsteal</guimenu> and <guimenu>pgscank</guimenu>, resulting in <guimenu>%vmeff</guimenu> value
        exceeding 100% in certain situations.
       </para>
       <para>
-       If %vmeff exceeds 100%, avoid using it as a performance indicator. Instead, analyze memory
-       performance by monitoring pgpgin/s and pgpgout/s for paging activity, majflt/s and fault/s
+       If <guimenu>%vmeff</guimenu> exceeds 100%, avoid using it as a performance indicator. Instead, analyze memory
+       performance by monitoring <guimenu>pgpgin/s</guimenu> and <guimenu>pgpgout/s</guimenu> for paging activity, <guimenu>majflt/s</guimenu> and <guimenu>fault/s</guimenu>
        for page faults, and memory utilization details in <filename>/proc/meminfo</filename> (for
-       example, Active, Inactive, Dirty and Writeback). Additionally, correlate these metrics with
+       example, <guimenu>Active</guimenu>, <guimenu>Inactive</guimenu>, <guimenu>Dirty</guimenu> and <guimenu>Writeback</guimenu>). Additionally, correlate these metrics with
        application-level performance and I/O patterns to identify potential memory bottlenecks or
        inefficiencies.
       </para>