diff --git a/misc/config_tools/schema/VMtypes.xsd b/misc/config_tools/schema/VMtypes.xsd
index be2720a55..6ea3d3f90 100644
--- a/misc/config_tools/schema/VMtypes.xsd
+++ b/misc/config_tools/schema/VMtypes.xsd
@@ -86,8 +86,7 @@ to.</xs:documentation>
       <xs:annotation>
         <xs:documentation>Configure each CPU in VMs to a desired CLOS ID in the ``VM`` section of the
 scenario file. Follow :ref:`rdt_detection_capabilities`
-to identify the maximum supported CLOS ID that can be used. Default
-value ``0``.</xs:documentation>
+to identify the maximum supported CLOS ID that can be used.</xs:documentation>
       </xs:annotation>
     </xs:element>
   </xs:sequence>
diff --git a/misc/config_tools/schema/config.xsd b/misc/config_tools/schema/config.xsd
index f94722316..6e1699e41 100644
--- a/misc/config_tools/schema/config.xsd
+++ b/misc/config_tools/schema/config.xsd
@@ -24,17 +24,17 @@ hypervisor shell.</xs:documentation>
     <xs:element name="SERIAL_CONSOLE" type="SerialConsoleOptions" default="/dev/ttyS0">
       <xs:annotation>
         <xs:documentation>Specify the host serial device used for hypervisor debugging.
-This entry is valid if and only if `hv.DEBUG_OPTIONS.RELEASE` is n.
-This entry impacts the content of `vm.(legacy_vuart id="0").base` when `vm.vm_type` is SOS_VM,
-which specifies the PIO base for Service VM legacy vUART 0 (used for console).
-The determination of the PIO base for Service VM legacy vUART 0 follows the rules below:
+This option is only valid if :option:`hv.DEBUG_OPTIONS.RELEASE` is set to ``n``.
+This option impacts the content of ``vm.(legacy_vuart id="0").base`` when :option:`vm.vm_type` is ``SOS_VM``,
+which specifies the PIO base for Service VM legacy vUART 0 (used for the console).
+The PIO base for the Service VM's legacy vUART 0 is determined using these rules:
 
-- If hv.DEBUG_OPTIONS.SERIAL_CONSOLE is one of [ttys0, ttys1, ttys2, ttys3] and it's a PIO in the
-  native environment, the PIO base of Service VM legacy vUART 0 would be the same as the PIO base
-  corresponding to hv.DEBUG_OPTIONS.SERIAL_CONSOLE in the native environment.
-- Otherwise, a PIO base would be assigned to Service VM legacy vUART 0 from the available PIO list.
+- If :option:`hv.DEBUG_OPTIONS.SERIAL_CONSOLE` is ``ttys0``, ``ttys1``, ``ttys2``, or ``ttys3`` and it is a PIO in the
+  native environment, the PIO base of the Service VM legacy vUART 0 would be the same as the PIO base
+  corresponding to :option:`hv.DEBUG_OPTIONS.SERIAL_CONSOLE` in the native environment.
+- Otherwise, a PIO base would be assigned to the Service VM legacy vUART 0 from the available PIO list.
 
-The above logic is implemented in the configuration tools.</xs:documentation>
+This logic is implemented in the configuration tools.</xs:documentation>
       </xs:annotation>
     </xs:element>
     <xs:element name="MEM_LOGLEVEL" type="LogLevelType" default="5">
@@ -292,8 +292,8 @@ initialization.</xs:documentation>
     </xs:element>
     <xs:element name="MAX_MSIX_TABLE_NUM" default="64">
         <xs:annotation>
-          <xs:documentation>Pre-defined maximum number of virtual MSI-X Table entries per device.
-If this value is empty, then the default value will be calculated from the board XML file.</xs:documentation>
+          <xs:documentation>Pre-defined maximum number of virtual MSI-X table entries per device.
+If this value is empty, then the default value will be calculated from information in the board XML file.</xs:documentation>
         </xs:annotation>
       <xs:simpleType>
         <xs:annotation>
diff --git a/misc/config_tools/schema/types.xsd b/misc/config_tools/schema/types.xsd
index 25a107ed1..d3ab25252 100644
--- a/misc/config_tools/schema/types.xsd
+++ b/misc/config_tools/schema/types.xsd
@@ -179,9 +179,9 @@ value ``n``.</xs:documentation>
       <xs:annotation>
         <xs:documentation>Specify the cache capacity bitmask for the CLOS; only continuous '1' bits
 are allowed. The value will be ignored when hardware does not support RDT.
-This entry takes effect only if `hv.FEATURES.RDT.RDT_ENABLED` is y.
-As `vm.clos.vcpu_clos` specifies the index of the CLOS to be associated with the given vCPU,
-`hv.FEATURES.RDT.CLOS_MASK` of that CLOS would impact the performance of the given vCPU.</xs:documentation>
+This option takes effect only if :option:`hv.FEATURES.RDT.RDT_ENABLED` is set to ``y``.
+As :option:`vm.clos.vcpu_clos` specifies the index of the CLOS to be associated with the given vCPU,
+:option:`hv.FEATURES.RDT.CLOS_MASK` of that CLOS would impact the performance of the given vCPU.</xs:documentation>
       </xs:annotation>
     </xs:element>
     <xs:element name="MBA_DELAY" type="xs:string" minOccurs="0"  maxOccurs="unbounded">