Merge pull request #45611 from johnwilkins/BZ2004210-4

BZ#2004210: Restructuring modules and ensuring compliance with style guide.

Author: ahardin-rh

installing/installing_bare_metal_ipi/ipi-install-installation-workflow.adoc

@@ -17,10 +17,22 @@ include::modules/ipi-install-extracting-the-openshift-installer.adoc[leveloffset
 include::modules/ipi-install-creating-an-rhcos-images-cache.adoc[leveloffset=+1]
 
 [id="ipi-install-configuration-files"]
-== Configuration files
+== Configuring the install-config.yaml file
 
 include::modules/ipi-install-configuring-the-install-config-file.adoc[leveloffset=+2]
 
+include::modules/ipi-install-additional-install-config-parameters.adoc[leveloffset=+2]
+
+include::modules/ipi-install-bmc-addressing.adoc[leveloffset=+2]
+
+include::modules/ipi-install-bmc-addressing-for-dell-idrac.adoc[leveloffset=+2]
+
+include::modules/ipi-install-bmc-addressing-for-hpe-ilo.adoc[leveloffset=+2]
+
+include::modules/ipi-install-bmc-addressing-for-fujitsu-irmc.adoc[leveloffset=+2]
+
+include::modules/ipi-install-root-device-hints.adoc[leveloffset=+2]
+
 include::modules/ipi-install-setting-proxy-settings-within-install-config.adoc[leveloffset=+2]
 
 include::modules/ipi-install-modifying-install-config-for-no-provisioning-network.adoc[leveloffset=+2]
@@ -30,38 +42,29 @@ include::modules/ipi-install-modifying-install-config-for-dual-stack-network.ado
 include::modules/ipi-install-configuring-host-network-interfaces-in-the-install-config.yaml-file.adoc[leveloffset=+2]
 
 [role="_additional-resources"]
-.Additional resources
+== Additional resources
 
 * xref:../../release_notes/ocp-4-11-release-notes.adoc#ocp-4-11-known-issues[OpenShift Container Platform 4.11 release notes]
 
 include::modules/ipi-install-configuring-managed-secure-boot-in-the-install-config-file.adoc[leveloffset=+2]
 
-include::modules/ipi-install-additional-install-config-parameters.adoc[leveloffset=+2]
-
-include::modules/ipi-install-bmc-addressing.adoc[leveloffset=+2]
-
-include::modules/ipi-install-bmc-addressing-for-dell-idrac.adoc[leveloffset=+2]
-
-include::modules/ipi-install-bmc-addressing-for-hpe-ilo.adoc[leveloffset=+2]
-
-include::modules/ipi-install-bmc-addressing-for-fujitsu-irmc.adoc[leveloffset=+2]
-
-include::modules/ipi-install-root-device-hints.adoc[leveloffset=+2]
+[id="ipi-install-manifest-configuration-files"]
+== Manifest configuration files
 
 include::modules/ipi-install-creating-the-openshift-manifests.adoc[leveloffset=+2]
 
 include::modules/ipi-install-configuring-ntp-for-disconnected-clusters.adoc[leveloffset=+2]
 
 include::modules/ipi-install-configure-network-components-to-run-on-the-control-plane.adoc[leveloffset=+2]
 
+include::modules/ipi-install-deploying-routers-on-worker-nodes.adoc[leveloffset=+2]
+
 include::modules/ipi-install-configuring-bios-for-worker-node.adoc[leveloffset=+2]
 
 include::modules/ipi-install-configuring-raid-for-worker-node.adoc[leveloffset=+2]
 
 include::modules/ipi-install-creating-a-disconnected-registry.adoc[leveloffset=+1]
 
-include::modules/ipi-install-deploying-routers-on-worker-nodes.adoc[leveloffset=+1]
-
 include::modules/ipi-install-validation-checklist-for-installation.adoc[leveloffset=+1]
 
 include::modules/ipi-install-deploying-the-cluster-via-the-openshift-installer.adoc[leveloffset=+1]
@@ -71,6 +74,6 @@ include::modules/ipi-install-following-the-installation.adoc[leveloffset=+1]
 include::modules/ipi-install-verifying-static-ip-address-configuration.adoc[leveloffset=+1]
 
 [role="_additional-resources"]
-.Additional resources
+== Additional resources
 
 * xref:../../updating/understanding-upgrade-channels-release.adoc#understanding-upgrade-channels_understanding-upgrade-channels-releases[{product-title} upgrade channels and releases]

modules/ipi-install-additional-install-config-parameters.adoc

@@ -203,6 +203,6 @@ You must provide a valid MAC address from the host if you disabled the `provisio
 
 | `networkConfig`
 |
-| Set this optional parameter to configure the network interface of a host. See "(Optional) Configuring host network interfaces in the `install-config.yaml` file" for additional details.
+| Set this optional parameter to configure the network interface of a host. See "(Optional) Configuring host network interfaces" for additional details.
 
 |===

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

@@ -4,7 +4,7 @@
 
 :_content-type: PROCEDURE
 [id='configure-network-components-to-run-on-the-control-plane_{context}']
-= (Optional) Configure network components to run on the control plane
+= (Optional) Configuring 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-bios-for-worker-node.adoc

@@ -4,7 +4,7 @@
 
 :_content-type: PROCEDURE
 [id="configuring-bios-for-worker-node_{context}"]
-= Configuring the BIOS for worker nodes
+= (Optional) Configuring the BIOS for worker nodes
 
 The following procedure configures the BIOS for a worker node during the installation process.
 

modules/ipi-install-configuring-host-network-interfaces-in-the-install-config.yaml-file.adoc

@@ -4,7 +4,7 @@
 
 :_content-type: PROCEDURE
 [id="configuring-host-network-interfaces-in-the-install-config-yaml-file_{context}"]
-= (Optional) Configuring host network interfaces in the `install-config.yaml` file
+= (Optional) Configuring host network interfaces
 
 During installation, you can set the `networkConfig` configuration setting in the `install-config.yaml` file to configure host network interfaces using NMState. To use the `networkConfig` configuration setting, you must provide an NMState YAML configuration.
 

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

@@ -4,7 +4,7 @@
 
 :_content-type: PROCEDURE
 [id="configuring-managed-secure-boot-in-the-install-config-file_{context}"]
-= (Optional) Configuring managed Secure Boot in the `install-config.yaml` file
+= (Optional) Configuring managed Secure Boot
 
 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-raid-for-worker-node.adoc

@@ -4,18 +4,19 @@
 
 :_content-type: PROCEDURE
 [id="configuring-raid-for-worker-node_{context}"]
-= Configuring RAID for worker nodes
+= (Optional) Configuring RAID for worker nodes
 
-The following procedure configures RAID (Redundant Array of Independent Disks) for the worker node during the installation process.
+The following procedure configures a redundant array of independent disks (RAID) for the worker node during the installation process.
 
 [NOTE]
 ====
-. Only nodes with BMC (Baseboard Management Controller) type `irmc` are supported. Other types of nodes are currently not supported.
-. If you want to configure hardware RAID for the node, make sure the node has a RAID controller.
+. Only nodes with baseboard management controller (BMC) type `irmc` are supported. Other types of nodes are currently not supported.
+. If you want to configure a hardware RAID for the node, make sure the node has a RAID controller.
 ====
 
 .Procedure
-. Create manifests.
+
+. Create the manifests.
 
 . Modify the BMH (Bare Metal Host) file corresponding to the worker:
 +
@@ -55,4 +56,4 @@ spec:
 +
 .. If you do not add a `raid` field in the `spec` section, the original RAID configuration is not deleted, and no new configuration will be performed.
 
-. Create cluster.
+. Create the cluster.