OSDOCS-11423:removing redundant prerequisites

Author: brendan-daly-red-hat

modules/installation-azure-create-dns-zones.adoc

@@ -40,12 +40,6 @@ cluster deployment and might already exist in your organization for the desired
 ====
 endif::ash[]
 
-.Prerequisites
-
-* Configure an Azure account.
-
-* Generate the Ignition config files for your cluster.
-
 .Procedure
 
 ifndef::ash[]

modules/installation-azure-create-resource-group-and-identity.adoc

@@ -27,8 +27,6 @@ endif::ash[]
 
 .Prerequisites
 
-* Configure an Azure account.
-
 * Generate the Ignition config files for your cluster.
 
 .Procedure

modules/installation-azure-user-infra-deploying-rhcos.adoc

@@ -26,10 +26,6 @@ You must use a valid {op-system-first} image for Microsoft {cp} for your
 
 .Prerequisites
 
-* Configure an Azure account.
-
-* Generate the Ignition config files for your cluster.
-
 * Store the {op-system} virtual hard disk (VHD) cluster image in an Azure storage container.
 
 * Store the bootstrap Ignition config file in an Azure storage container.

modules/installation-azure-user-infra-uploading-rhcos.adoc

@@ -39,13 +39,6 @@ ifdef::ash-ipi[]
 You must download the {op-system} virtual hard disk (VHD) cluster image and upload it to your Azure Stack Hub environment so that it is accessible during deployment.
 endif::ash-ipi[]
 
-.Prerequisites
-
-* Configure an Azure account.
-ifndef::ash-ipi[]
-* Generate the Ignition config files for your cluster.
-endif::ash-ipi[]
-
 .Procedure
 
 ifndef::ash-ipi[]
@@ -78,7 +71,7 @@ $ export ACCOUNT_KEY=`az storage account keys list -g ${RESOURCE_GROUP} --accoun
 ifdef::azure[]
 [source,terminal]
 ----
-$ export VHD_URL=`openshift-install coreos print-stream-json | jq -r '.architectures.<architecture>."rhel-coreos-extensions"."azure-disk".url'` 
+$ export VHD_URL=`openshift-install coreos print-stream-json | jq -r '.architectures.<architecture>."rhel-coreos-extensions"."azure-disk".url'`
 ----
 +
 where:

modules/installation-azure-user-infra-wait-for-bootstrap.adoc

@@ -27,12 +27,6 @@ the Ignition config files that you generated with the installation program.
 
 .Prerequisites
 
-* Configure an Azure account.
-* Generate the Ignition config files for your cluster.
-* Create and configure a VNet and associated subnets in {cp}.
-* Create and configure networking and load balancers in {cp}.
-* Create control plane and compute roles.
-* Create the bootstrap machine.
 * Create the control plane machines.
 
 .Procedure

modules/installation-creating-azure-bootstrap.adoc

@@ -35,9 +35,6 @@ support with your installation logs.
 
 .Prerequisites
 
-* Configure an Azure account.
-* Generate the Ignition config files for your cluster.
-* Create and configure a VNet and associated subnets in {cp}.
 * Create and configure networking and load balancers in {cp}.
 * Create control plane and compute roles.
 
@@ -101,7 +98,7 @@ $ az deployment group create -g ${RESOURCE_GROUP} \
 ----
 <1> The bootstrap Ignition content for the bootstrap cluster.
 <2> The base name to be used in resource names; this is usually the cluster's infrastructure ID.
-<3> Optional: Specify the size of the bootstrap VM. Use a VM size compatible with your specified architecture. If this value is not defined, the default value from the template is set. 
+<3> Optional: Specify the size of the bootstrap VM. Use a VM size compatible with your specified architecture. If this value is not defined, the default value from the template is set.
 endif::azure[]
 ifdef::ash[]
 [source,terminal]

modules/installation-creating-azure-control-plane.adoc

@@ -36,11 +36,6 @@ If you do not use the provided ARM template to create your control plane machine
 
 .Prerequisites
 
-* Configure an Azure account.
-* Generate the Ignition config files for your cluster.
-* Create and configure a VNet and associated subnets in {cp}.
-* Create and configure networking and load balancers in {cp}.
-* Create control plane and compute roles.
 * Create the bootstrap machine.
 
 .Procedure
@@ -69,7 +64,7 @@ $ az deployment group create -g ${RESOURCE_GROUP} \
 ----
 <1> The Ignition content for the control plane nodes.
 <2> The base name to be used in resource names; this is usually the cluster's infrastructure ID.
-<3> Optional: Specify the size of the Control Plane VM. Use a VM size compatible with your specified architecture. If this value is not defined, the default value from the template is set. 
+<3> Optional: Specify the size of the Control Plane VM. Use a VM size compatible with your specified architecture. If this value is not defined, the default value from the template is set.
 endif::azure[]
 ifdef::ash[]
 [source,terminal]

modules/installation-creating-azure-dns.adoc

@@ -42,8 +42,6 @@ support with your installation logs.
 
 .Prerequisites
 
-* Configure an Azure account.
-* Generate the Ignition config files for your cluster.
 * Create and configure a VNet and associated subnets in {cp}.
 
 .Procedure

modules/installation-creating-azure-vnet.adoc

@@ -33,11 +33,6 @@ If your cluster does not initialize correctly, you might have to contact Red Hat
 support with your installation logs.
 ====
 
-.Prerequisites
-
-* Configure an Azure account.
-* Generate the Ignition config files for your cluster.
-
 .Procedure
 
 . Copy the template from the *ARM template for the VNet* section of this topic

modules/installation-creating-azure-worker.adoc

@@ -47,16 +47,6 @@ endif::azure[]
 
 If you do not use the provided ARM template to create your control plane machines, you must review the provided information and manually create the infrastructure. If your cluster does not initialize correctly, consider contacting Red Hat support with your installation logs.
 
-.Prerequisites
-
-* Configure an Azure account.
-* Generate the Ignition config files for your cluster.
-* Create and configure a VNet and associated subnets in {cp}.
-* Create and configure networking and load balancers in {cp}.
-* Create control plane and compute roles.
-* Create the bootstrap machine.
-* Create the control plane machines.
-
 .Procedure
 
 . Copy the template from the *ARM template for worker machines*