BZ1979956: Round 2 of edits on the main branch

tmulquee · tmulquee · commit d94b4bf2028c · 2022-11-15T15:15:33.000Z
diff --git a/installing/installing_bare_metal_ipi/ipi-install-overview.adoc b/installing/installing_bare_metal_ipi/ipi-install-overview.adoc
@@ -4,19 +4,21 @@
 include::_attributes/common-attributes.adoc[]
 :context: ipi-install
 
-Installer-provisioned installation on bare metal nodes deploys and configures the infrastructure that a {product-title} cluster runs on. This guide provides a methodology to achieving a successful installer-provisioned bare-metal installation. The following diagram illustrates the installation environment in phase 1 of deployment.
+toc::[]
+
+Installer-provisioned installation on bare metal nodes deploys and configures the infrastructure that a {product-title} cluster runs on. This guide provides a methodology to achieving a successful installer-provisioned bare-metal installation. The following diagram illustrates the installation environment in phase 1 of deployment:
 
 image::210_OpenShift_Baremetal_IPI_Deployment_updates_0122_1.png[Deployment phase one]
 
 For the installation, the key elements in the previous diagram are:
 
 - **Provisioner**: A physical machine that runs the installation program and hosts the bootstrap VM that deploys the controller of a new {product-title} cluster.
-- **Bootstrap VM**: A virtual machine that assists in the process of deploying an {product-title} cluster.
-- **Network bridges**: The bootstrap VM connects to the bare-metal network and to the provisioning network, if present, via network bridges, `eno1` and `eno2`.
+- **Bootstrap VM**: A virtual machine used in the process of deploying an {product-title} cluster.
+- **Network bridges**: The bootstrap VM connects to the bare metal network and to the provisioning network, if present, via network bridges, `eno1` and `eno2`.
 
 In phase 2 of the deployment, the provisioner destroys the bootstrap VM automatically and moves the virtual IP addresses (VIPs) to the appropriate nodes. The API VIP moves to the control plane nodes and the Ingress VIP moves to the worker nodes.
 
-The following diagram illustrates phase 2 of deployment.
+The following diagram illustrates phase 2 of deployment:
 
 image::210_OpenShift_Baremetal_IPI_Deployment_updates_0122_2.png[Deployment phase two]
 
diff --git a/modules/ipi-install-troubleshooting-bootstrap-vm.adoc b/modules/ipi-install-troubleshooting-bootstrap-vm.adoc
@@ -94,7 +94,7 @@ $ ssh core@172.22.0.2
 
 If you are not successful logging in to the bootstrap VM, you have likely encountered one of the following scenarios:
 
-* You cannot reach the `172.22.0.0/24` network. Verify the network connectivity between the provisioner and the `provisioning` network bridge. This issue may occur if you are using a `provisioning` network.
+* You cannot reach the `172.22.0.0/24` network. Verify the network connectivity between the provisioner and the `provisioning` network bridge. This issue might occur if you are using a `provisioning` network.
 `
 * You cannot reach the bootstrap VM through the public network. When attempting
 to SSH via `baremetal` network, verify connectivity on the

Original file line number	Diff line number	Diff line change
`@@ -94,7 +94,7 @@ $ ssh [email protected]`
`94`	`94`
`95`	`95`	`If you are not successful logging in to the bootstrap VM, you have likely encountered one of the following scenarios:`
`96`	`96`
`97`		-* You cannot reach the `172.22.0.0/24` network. Verify the network connectivity between the provisioner and the `provisioning` network bridge. This issue may occur if you are using a `provisioning` network.
	`97`	+* You cannot reach the `172.22.0.0/24` network. Verify the network connectivity between the provisioner and the `provisioning` network bridge. This issue might occur if you are using a `provisioning` network.
`98`	`98`	`
`99`	`99`	`* You cannot reach the bootstrap VM through the public network. When attempting`
`100`	`100`	to SSH via `baremetal` network, verify connectivity on the