Merge pull request #36506 from codyhoag/install-image-updates

Update installer images and tweak machine names

Author: codyhoag

images/create-nodes.png

@@ -63,15 +63,15 @@ If you do not use infrastructure that the installation program provisioned, you
 * Cluster networking, including the DNS records and required subnets
 * Storage for the cluster infrastructure and applications
 
-If your cluster uses user-provisioned infrastructure, you have the option of adding RHEL worker machines to your cluster.
+If your cluster uses user-provisioned infrastructure, you have the option of adding {op-system-base} compute machines to your cluster.
 
 [discrete]
 == Installation process details
 
 Because each machine in the cluster requires information about the cluster when it is provisioned, {product-title} uses a temporary _bootstrap_ machine during initial configuration to provide the required information to the permanent control plane. It boots by using an Ignition config file that describes how to create the cluster. The bootstrap machine creates the control plane machines that make up the control plane. The control plane machines then create the compute machines, which are also known as worker machines. The following figure illustrates this process:
 
-.Creating the bootstrap, master, and worker machines
-image::create-nodes.png[Creating bootstrap, master, and worker machines]
+.Creating the bootstrap, control plane, and compute machines
+image::create-nodes.png[Creating bootstrap, control plane, and compute machines]
 
 After the cluster machines initialize, the bootstrap machine is destroyed. All clusters use the bootstrap process to initialize the cluster, but if you provision the infrastructure for your cluster, you must complete many of the steps manually.
 
@@ -90,7 +90,7 @@ Bootstrapping a cluster involves the following steps:
 . The temporary control plane shuts down and passes control to the production control plane.
 . The bootstrap machine injects {product-title} components into the production control plane.
 . The installation program shuts down the bootstrap machine. (Requires manual intervention if you provision the infrastructure)
-. The control plane sets up the worker nodes.
+. The control plane sets up the compute nodes.
 . The control plane installs additional services in the form of a set of Operators.
 
-The result of this bootstrapping process is a fully running {product-title} cluster. The cluster then downloads and configures remaining components needed for the day-to-day operation, including the creation of worker machines in supported environments.
+The result of this bootstrapping process is a fully running {product-title} cluster. The cluster then downloads and configures remaining components needed for the day-to-day operation, including the creation of compute machines in supported environments.