BZ1921110-fixed list and errant asterisk

Author: skrthomas

modules/nodes-scheduler-default-predicates.adoc

@@ -37,7 +37,7 @@ The `MaxEBSVolumeCount` predicate checks the maximum number of volumes that can
 {"name" : "MaxEBSVolumeCount"}
 ----
 
-The *MaxAzureDiskVolumeCount` predicate checks the maximum number of Azure Disk Volumes.
+The `MaxAzureDiskVolumeCount` predicate checks the maximum number of Azure Disk Volumes.
 
 [source,yaml]
 ----
@@ -59,6 +59,7 @@ The `CheckNodeUnschedulable` predicate checks if a pod can be scheduled on a nod
 ----
 
 The `CheckVolumeBinding` predicate evaluates if a pod can fit based on the volumes, it requests, for both bound and unbound PVCs.
+
 * For PVCs that are bound, the predicate checks that the corresponding PV's node affinity is satisfied by the given node.
 * For PVCs that are unbound, the predicate searched for available PVs that can satisfy the PVC requirements and that
 the PV node affinity is satisfied by the given node.
@@ -104,7 +105,7 @@ The `MatchInterPodAffinity` predicate checks if the pod affinity/anti-affinity r
 [NOTE]
 ====
 The `CheckNode-*` predicates cannot be used if the Taint Nodes By Condition feature is enabled.
-The Taint Nodes By Condition feature is enabled by default.  
+The Taint Nodes By Condition feature is enabled by default.
 ====
 
 The `CheckNodeCondition` predicate checks if a pod can be scheduled on a node reporting *out of disk*, *network unavailable*, or *not ready* conditions.
@@ -190,7 +191,7 @@ defined in the pod.
 
 // per sjenning Nope
 
-You can configure these predicates in the scheduler policy Configmap 
+You can configure these predicates in the scheduler policy Configmap
 in the `openshift-config` project, to add labels to affect
 how the predicate functions.