Merge pull request #63877 from EricPonvelle/OSDOCS-6913.2_Typos

OSDOCS-6913: Cleaned up some extra typos

Author: EricPonvelle

modules/rosa-sts-interactive-cluster-creation-mode-options.adoc

@@ -69,7 +69,7 @@ The ROSA with Hosted Control Planes functionality is currently offered as a Tech
 |Specify the IP address range for services. The range must be large enough to accommodate your workload. The address block must not overlap with any external service accessed from within the cluster. The default is `172.30.0.0/16`. It is recommended that the address ranges are the same between clusters.
 
 |`Pod CIDR`
-|Specify the IP address range for pods. The range must be large enough to accommodate your workload. The address block must not overlap with any external service accessed from within the cluster. The default is `10.128.0.0/14`. It is recommended that they are the same between clusters.
+|Specify the IP address range for pods. The range must be large enough to accommodate your workload. The address block must not overlap with any external service accessed from within the cluster. The default is `10.128.0.0/14`. It is recommended that the address ranges are the same between clusters.
 
 |`Install into an existing VPC (optional)`
 |Install a cluster into an existing AWS VPC. To use this option, your VPC must have 2 subnets for each availability zone that you are installing the cluster into. The default is `No`.
@@ -117,7 +117,7 @@ By enabling etcd encryption for the key values in etcd, you will incur a perform
 |Disable monitoring for user-defined projects. Monitoring for user-defined projects is enabled by default.
 
 |`Route Selector for ingress (optional)`
-|Specify the route selector for your ingress. The format should be a comma-separated list of `key=value`. If you do not specify a label, all routes will be exposed on both routers. For legacy ingress support, these labels are inclusion labels; otherwise, they are treated as exclusion label.
+|Specify the route selector for your ingress. The format should be a comma-separated list of key-value pairs. If you do not specify a label, all routes will be exposed on both routers. For legacy ingress support, these labels are inclusion labels; otherwise, they are treated as exclusion labels.
 
 |`Excluded namespaces for ingress (optional)`
 |Specify the excluded namespaces for your ingress. The format should be a comma-separated list `value1, value2...`. If you do not specify any values, all namespaces will be exposed.