Merge pull request #40976 from johnwilkins/IBM-Style-Guide

IBM Style Guide: Moved (Optional) to the beginning of the title

Author: ahardin-rh

modules/ipi-install-configure-network-components-to-run-on-the-control-plane.adoc

@@ -1,8 +1,8 @@
 // This is included in the following assemblies:
 //
 // ipi-install-configuration-files.adoc
-[id='configure-network-components-to-run-on-the-control-plane_{context}']
 
+[id='configure-network-components-to-run-on-the-control-plane_{context}']
 = (Optional) Configure network components to run on the control plane
 
 You can configure networking components to run exclusively on the control plane nodes. By default, {product-title} allows any node in the machine config pool to host the `ingressVIP` virtual IP address. However, some environments deploy worker nodes in separate subnets from the control plane nodes. When deploying remote workers in separate subnets, you must place the `ingressVIP` virtual IP address exclusively with the control plane nodes.

modules/ipi-install-configuring-managed-secure-boot-in-the-install-config-file.adoc

@@ -1,9 +1,9 @@
 // This is included in the following assemblies:
 //
 // installing/installing_bare_metal_ipi/ipi-install-configuration-files.adoc
-[id="configuring-managed-secure-boot-in-the-install-config-file_{context}"]
 
-= Configuring managed Secure Boot in the `install-config.yaml` file (optional)
+[id="configuring-managed-secure-boot-in-the-install-config-file_{context}"]
+= (Optional) Configuring managed Secure Boot in the `install-config.yaml` file
 
 You can enable managed Secure Boot when deploying an installer-provisioned cluster using Redfish BMC addressing, such as `redfish`, `redfish-virtualmedia`, or `idrac-virtualmedia`. To enable managed Secure Boot, add the `bootMode` configuration setting to each node:
 

modules/ipi-install-configuring-ntp-for-disconnected-clusters.adoc

@@ -2,9 +2,9 @@
 //
 // installing/installing_bare_metal_ipi/ipi-install-configuration-files
 // installing/installing_bare_metal_ipi/ipi-install-post-installation-configuration.adoc
-[id="configuring-ntp-for-disconnected-clusters_{context}"]
 
-= Configuring NTP for disconnected clusters (optional)
+[id="configuring-ntp-for-disconnected-clusters_{context}"]
+= (Optional) Configuring NTP for disconnected clusters
 
 //This procedure can be executed as a day 1 or day 2 operation with minor differences.
 //The conditional text picks up the context and displays the appropriate alternate steps.

modules/ipi-install-creating-a-disconnected-registry.adoc

@@ -4,8 +4,7 @@
 // install/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc
 
 [id="ipi-install-creating-a-disconnected-registry_{context}"]
-
-= Creating a disconnected registry (optional)
+= (Optional) Creating a disconnected registry
 
 In some cases, you might want to install an {product-title} cluster using a local copy of the installation registry. This could be for enhancing network efficiency because the cluster nodes are on a network that does not have access to the internet.
 

modules/ipi-install-creating-an-rhcos-images-cache.adoc

@@ -3,7 +3,7 @@
 //  *installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc
 
 [id="ipi-install-creating-an-rhcos-images-cache_{context}"]
-= Creating an {op-system} images cache (optional)
+= (Optional) Creating an {op-system} images cache
 
 To employ image caching, you must download two images: the {op-system-first} image used by the bootstrap VM and the {op-system} image used by the installer to provision the different nodes. Image caching is optional, but especially useful when running the installer on a network with limited bandwidth.
 

modules/ipi-install-modifying-install-config-for-dual-stack-network.adoc

@@ -3,8 +3,7 @@
 // ipi-install-configuration-files.adoc
 
 [id='modifying-install-config-for-dual-stack-network_{context}']
-
-= Modifying the `install-config.yaml` file for dual-stack network (optional)
+= (Optional) Modifying the `install-config.yaml` file for dual-stack network
 
 To deploy an {product-title} cluster with dual-stack networking, edit the `machineNetwork`, `clusterNetwork`, and `serviceNetwork` configuration settings in the `install-config.yaml` file. Each setting must have two CIDR entries each. Ensure the first CIDR entry is the IPv4 setting and the second CIDR entry is the IPv6 setting.
 

modules/ipi-install-modifying-install-config-for-no-provisioning-network.adoc

@@ -3,8 +3,7 @@
 // ipi-install-configuration-files.adoc
 
 [id='modifying-install-config-for-no-provisioning-network_{context}']
-
-= Modifying the `install-config.yaml` file for no `provisioning` network (optional)
+= (Optional) Modifying the `install-config.yaml` file for no `provisioning` network
 
 To deploy an {product-title} cluster without a `provisioning` network, make the following changes to the `install-config.yaml` file.
 

modules/ipi-install-setting-proxy-settings-within-install-config.adoc

@@ -1,9 +1,9 @@
 // This is included in the following assemblies:
 //
 // ipi-install-configuration-files.adoc
-[id='ipi-install-setting-proxy-settings-within-install-config_{context}']
 
-= Setting proxy settings within the `install-config.yaml` file (optional)
+[id='ipi-install-setting-proxy-settings-within-install-config_{context}']
+= (Optional) Setting proxy settings within the `install-config.yaml` file
 
 To deploy an {product-title} cluster using a proxy, make the following changes to the `install-config.yaml` file.