Merge pull request #55321 from mletalie/OSDOCS-4915

Updating ROSA docs to match AWS docs in regards to NLB, ELB, CLB, etc.

Author: mburke5678

modules/ccs-aws-provisioned.adoc

@@ -48,7 +48,7 @@ Volume requirements for each EC2 instance:
 [id="aws-policy-elastic-load-balancers_{context}"]
 == Elastic load balancers
 
-Up to two Network Elastic Load Balancers (ELBs) for API and up to two Classic ELBs for application router. For more information, see the link:https://aws.amazon.com/elasticloadbalancing/features/#Details_for_Elastic_Load_Balancing_Products[ELB documentation for AWS].
+Up to two Network Load Balancers (NLBs) for API and up to two Classic Load Balancers (CLBs) for application router. For more information, see the link:https://aws.amazon.com/elasticloadbalancing/features/#Details_for_Elastic_Load_Balancing_Products[ELB documentation for AWS].
 
 [id="aws-policy-s3-storage_{context}"]
 == S3 storage

modules/dedicated-configuring-your-application-routes.adoc

@@ -6,8 +6,7 @@
 = Configuring your application routes
 
 When your cluster is provisioned, an AWS elastic load balancer (ELB) is created
-to route application traffic into the cluster. The domain for your ELB is
-configured to route application traffic via
+to route application traffic into the cluster. The domain for your ELB is configured to route application traffic via
 `http(s)://*.<cluster-id>.<shard-id>.p1.openshiftapps.com`. The `<shard-id>` is a
 random four-character string assigned to your cluster at creation time.
 

modules/installation-aws-permissions.adoc

@@ -155,7 +155,7 @@ If you use an existing VPC, your account does not require these permissions for
 
 [NOTE]
 =====
-If you have not created an elastic load balancer (ELB) in your AWS account, the IAM user also requires the `iam:CreateServiceLinkedRole` permission.
+If you have not created a load balancer in your AWS account, the IAM user also requires the `iam:CreateServiceLinkedRole` permission.
 =====
 ====
 

modules/rosa-aws-provisioned.adoc

@@ -49,9 +49,9 @@ Clusters deployed before the release of {OCP} 4.11 use gp2 type storage by defau
 ====
 
 [id="rosa-elastic-load-balancers_{context}"]
-== Elastic load balancers
+== Elastic Load Balancing
 
-Up to two Network Elastic Load Balancers (ELBs) for API and up to two Classic ELBs for application router. For more information, see the link:https://aws.amazon.com/elasticloadbalancing/features/#Details_for_Elastic_Load_Balancing_Products[ELB documentation for AWS].
+Up to two Network Load Balancers (NLBs) for API and up to two Classic Load Balancers (CLBs) for application router. For more information, see the link:https://aws.amazon.com/elasticloadbalancing/features/#Details_for_Elastic_Load_Balancing_Products[ELB documentation for AWS].
 
 [id="rosa-s3-storage_{context}"]
 == S3 storage

modules/rosa-sts-aws-requirements-account.adoc

@@ -15,7 +15,7 @@ Quota verification checks your AWS quota, but it does not compare your consumpti
 * Your AWS account should not be transferable to Red Hat.
 * You should not impose additional AWS usage restrictions beyond the defined roles and policies on Red Hat activities. Imposing restrictions will severely hinder Red Hat's ability to respond to incidents.
 * You may deploy native AWS services within the same AWS account.
-* Your account must have a service-linked role set up as it is required for elastic load balancers (ELBs) to be configured. See the "Creating the service role for the elastic load balancer (ELB)" link in the Additional resources for information about creating a service-linked role for your ELB if you have not created a load balancer in your AWS account previously.
+* Your account must have a service-linked role set up as it is required for Elastic Load Balancing (ELB) to be configured. See the "Creating the Elastic Load Balancing (ELB) service-linked role" link in the Additional resources for information about creating a service-linked role for your ELB if you have not created a load balancer in your AWS account previously.
 +
 [NOTE]
 ====

modules/rosa-troubleshooting-elb-service-role.adoc

@@ -2,10 +2,10 @@
 //
 // * rosa_getting_started_sts/rosa-sts-aws-prereqs.adoc
 :_content-type: PROCEDURE
-[id="rosa-troubleshooting-elb-serivce-role_{context}"]
-= Creating the service role for the elastic load balancer (ELB)
+[id="rosa-troubleshooting-elb-service-role_{context}"]
+= Creating the Elastic Load Balancing (ELB) service-linked role
 
-If you have not created a load balancer in your AWS account, it is possible that the service role for the elastic load balancer (ELB) might not exist yet. You may receive the following error:
+If you have not created a load balancer in your AWS account, it is possible that the service-linked role for Elastic Load Balancing (ELB) might not exist yet. You may receive the following error:
 
 [source,terminal]
 ----

rosa_planning/rosa-sts-aws-prereqs.adoc

@@ -29,7 +29,7 @@ include::modules/rosa-sts-aws-requirements-account.adoc[leveloffset=+2]
 [id="additional-resources_aws-account-requirements_{context}"]
 .Additional resources
 * xref:../rosa_planning/rosa-limits-scalability.adoc#rosa-limits-scalability[Limits and scalability]
-* xref:../rosa_support/rosa-troubleshooting-deployments.adoc#rosa-troubleshooting-general-deployment-elb[Creating the service role for the elastic load balancer (ELB)]
+* xref:../rosa_support/rosa-troubleshooting-deployments.adoc#rosa-troubleshooting-general-deployment-elb[Creating the Elastic Load Balancing (ELB) service-linked role]
 
 include::modules/rosa-sts-aws-requirements-access-req.adoc[leveloffset=+2]