Fix syntax in failure domains param section

GH#60048

Author: maxwelldb

modules/installation-configuration-parameters.adoc

@@ -1093,10 +1093,12 @@ For more information about the support scope of Red Hat Technology Preview featu
 Beginning with {product-title} 4.13, there is a unified definition of failure domains for {rh-openstack} deployments that covers all supported availability zone types. You can use failure domains to control related aspects of Nova, Neutron, and Cinder configurations from a single place. 
 
 In {rh-openstack}, a port describes a network connection and maps to an interface inside a compute machine. A port also:
+
 * Is defined by a network or by one more or subnets
 * Connects a machine to one or more subnets
 
 Failure domains group the services of your deployment by using ports. If you use failure domains, each machine connects to:
+
 * The `portTarget` object with the ID `control-plane` while that object exists.
 * All non-control-plane `portTarget` objects within its own failure domain.
 * All networks in the machine pool's `additionalNetworkIDs` list.
@@ -1126,16 +1128,16 @@ To configure failure domains for a machine pool, edit availability zone and port
 
 |`platform.openstack.failuredomains.portTargets.portTarget.network`
 |Required. The name or ID of the network to attach to machines in the failure domain.
-|A `network` object that contains either a name or UUID. For example:
-+
+a|A `network` object that contains either a name or UUID. For example:
+
 [source,yaml]
 ----
 network:
   id: 8db6a48e-375b-4caa-b20b-5b9a7218bfe6
 ----
-+
+
 or:
-+
+
 [source,yaml]
 ----
 network:

modules/installation-osp-failure-domains-config.adoc

@@ -13,7 +13,7 @@ The following section of an `install-config.yaml` file demonstrates the use of f
 
 [source,yaml]
 ----
-...
+# ...
 controlPlane:
   name: master
   platform:
@@ -39,5 +39,5 @@ controlPlane:
           network:
             id: 8e4b4e0d-3865-4a9b-a769-559270271242
 featureSet: TechPreviewNoUpgrade
-...
+# ...
 ----