SME edits

Author: johnmarco

articles/openshift/azure-redhat-openshift-release-notes.md

@@ -17,7 +17,7 @@ Azure Red Hat OpenShift receives improvements on an ongoing basis. To stay up to
 
 To create a private cluster without a public IP address, you can now add the parameter `--outbound-type UserDefinedRouting` to the `aro create` command. See [Create a private cluster without a public IP address](howto-create-private-cluster-4x.md#create-a-private-cluster-without-a-public-ip-address) for details.
 
-When creating a cluster, the `--outbound` type must be either `LoadBalancer` (the default) or `UserDefinedRouting`.
+A cluster that is deployed with this feature and is running version 4.11 or higher, can be scaled to 120 nodes and 30,000 pods.
 
 ## Version 4.12 - August 2023
 

articles/openshift/openshift-faq.yml

@@ -31,7 +31,7 @@ sections:
         answer: |
           The actual number of supported pods depends on an application’s memory, CPU, and storage requirements.
           
-          Azure Red Hat OpenShift 4.x has a 250 pod-per-node limit and a 60 compute node limit. These limits cap the maximum number of pods supported in a cluster to 250×60 = 15,000. If the cluster is created with the `--outbound-type UserDefinedRouting` parameter and runs version 4.11 or higher, the limits are 120 compute nodes and 30,000 pods.
+          Azure Red Hat OpenShift 4.x has a 250 pod-per-node limit and a 60 compute node limit. These limits cap the maximum number of pods supported in a cluster to 250×60 = 15,000. If the cluster is created using User Defined Routing (UDR) and runs version 4.11 or higher, the limits are 120 compute nodes and 30,000 pods.
           
       - question: Can a cluster have compute nodes across multiple Azure regions?
         answer: No. All nodes in an Azure Red Hat OpenShift cluster must originate in the same Azure region.