Merge pull request #72166 from jeana-redhat/outpost-lb-docs-tweak

rewording CLB statement

Author: kalexand-rh

modules/aws-outposts-load-balancer-clb.adoc

@@ -6,10 +6,10 @@
 [id="aws-outposts-load-balancer-clb_{context}"]
 = Using AWS Classic Load Balancers in an AWS VPC cluster extended into an Outpost
 
-AWS Outposts racks cannot run AWS Classic Load Balancers, but Classic Load Balancers in the AWS VPC cluster can target edge compute nodes in the Outpost if edge and cloud-based subnets are in the same availability zone.
+AWS Outposts infrastructure cannot run AWS Classic Load Balancers, but Classic Load Balancers in the AWS VPC cluster can target edge compute nodes in the Outpost if edge and cloud-based subnets are in the same availability zone.
 As a result, Classic Load Balancers on the VPC cluster might schedule pods on either of these node types.
 
-Scheduling the workloads on edge compute nodes is supported, but can introduce latency.
+Scheduling the workloads on edge compute nodes and cloud-based compute nodes can introduce latency.
 If you want to prevent a Classic Load Balancer in the VPC cluster from targeting Outpost edge compute nodes, you can apply labels to the cloud-based compute nodes and configure the Classic Load Balancer to only schedule on nodes with the applied labels.
 
 [NOTE]