nits

Author: cachai2

articles/container-apps/ingress-how-to.md

@@ -150,7 +150,7 @@ Disable ingress for your container app by omitting the `ingress` configuration p
 You can expose additional TCP ports from your application. To learn more, see the [ingress concept article](ingress-overview.md#additional-tcp-ports).
 
 > [Note]
-> To use this preview feature, you must have the containerapp CLI extension. Run `az extension add -n containerapp` in order to install the latest version of the containerapp CLI extension.
+> To use this preview feature, you must have the container apps CLI extension. Run `az extension add -n containerapp` in order to install the latest version of the container apps CLI extension.
 
 
 ::: zone pivot="azure-cli"

articles/container-apps/ingress-overview.md

@@ -48,8 +48,8 @@ With HTTP ingress enabled, your container app has:
 
 - Support for TLS termination
 - Support for HTTP/1.1 and HTTP/2
-- Support for WebSocket and gRPC
-- HTTPS endpoints that always use TLS 1.2 or 1.3, terminated at the ingress point
+- Support for  WebSocket and gRPC
+- HTTPS endpoints that always use TLS 1.2, terminated at the ingress point
 - Endpoints that expose ports 80 (for HTTP) and 443 (for HTTPS)
   - By default, HTTP requests to port 80 are automatically redirected to HTTPS on 443
 - A fully qualified domain name (FQDN)
@@ -82,13 +82,16 @@ With TCP ingress enabled, your container app:
 
 In addition to the main HTTP/TCP port for your container apps, you might expose additional TCP ports to enable applications that accept TCP connections on multiple ports. This feature is in preview.
 
+> [!NOTE]
+> As the feature is in preview, make sure you are using the latest preview version of the container apps CLI extension.
+
 The following apply to additional TCP ports:
 - Additional TCP ports can only be external if the app itself is set as external and the container app is using a custom VNet.
 - Any externally exposed additional TCP ports must be unique across the entire Container Apps environment. This includes all external additional TCP ports, external main TCP ports, and 80/443 ports used by built-in HTTP ingress. If the additional ports are internal, the same port can be shared by multiple apps.
-- If an exposed port isn't provided, the exposed port will default to match the target port.
-- Each target port must be unique, and the same target port can't be exposed on different exposed ports.
-- There's a maximum of 5 additional ports per app. If additional ports are required, please open a support request.
-- Only the main ingress port supports built-in HTTP features such as CORS and session affinity. When running HTTP on top of the additional TCP ports, these built-in features aren't supported.
+- If an exposed port is not provided, the exposed port will default to match the target port.
+- Each target port must be unique, and the same target port cannot be exposed on different exposed ports.
+- There is a maximum of 5 additional ports per app. If additional ports are required, please open a support request.
+- Only the main ingress port supports built-in HTTP features such as CORS and session affinity. When running HTTP on top of the additional TCP ports, these built-in features are not supported.
 
 Visit the [how to article on ingress](ingress-how-to.md#use-additional-tcp-ports) for more information on how to enable additional ports for your container apps.