acrolinx

Author: craigshoemaker

articles/container-apps/ingress-overview.md

@@ -55,7 +55,7 @@ With HTTP ingress enabled, your container app has:
 - 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)
-- Request timeout is 240 seconds
+- Request time out is 240 seconds
 
 #### HTTP headers
 
@@ -64,7 +64,7 @@ HTTP ingress adds headers to pass metadata about the client request to your cont
 | Header | Description | Values |
 |---|---|---|
 | `X-Forwarded-Proto` | Protocol used by the client to connect with the Container Apps service. | `http` or `https` |
-| `X-Forwarded-For` | The IP address of the client that sent the request. | IP address of the sender. If specified in intital request, it will be overwritten. |
+| `X-Forwarded-For` | The IP address of the client that sent the request. | IP address of the sender. If specified in initial request, it is overwritten. |
 | `X-Forwarded-Host` | The host name the client used to connect with the Container Apps service. |  |
 | `X-Forwarded-Client-Cert` | The client certificate if `clientCertificateMode` is set. | Semicolon separated list of Hash, Cert, and Chain. For example: `Hash=....;Cert="...";Chain="...";` |
 
@@ -89,21 +89,21 @@ In addition to the main HTTP/TCP port for your container apps, you might expose
 
 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.
+- More 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.
+- Any externally exposed extra TCP ports must be unique across the entire Container Apps environment. This includes all external extra TCP ports, external main TCP ports, and 80/443 ports used by built-in HTTP ingress. If the extra ports are internal, you can share the same port by multiple apps.
 
-- If an exposed port isn't provided, the exposed port will default to match the target port.
+- If an exposed port isn't provided, the exposed port defaults 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 five additional ports per app. If additional ports are required, please open a support request.
+- There's a maximum of five additional ports per app. If additional ports are required, 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.
+- Only the main ingress port supports built-in HTTP features such as CORS and session affinity. When running HTTP on top of the extra TCP ports, these built-in features aren't supported.
 
-- Port number `36985` is a reserved for internal health checks and isn't available to TCP applications or additional exposed ports on HTTP applications.
+- Port number `36985` is a reserved for internal health checks and isn't available to TCP applications or extra exposed ports on HTTP applications.
 
-For more information on how to enable additional ports, see [Configure ingress for your app](ingress-how-to.md#use-additional-tcp-ports).
+For more information on how to enable extra ports, see [Configure ingress for your app](ingress-how-to.md#use-additional-tcp-ports).
 
 ## Domain names
 
@@ -133,7 +133,7 @@ Containers Apps allows you to split incoming traffic between active revisions. W
 
 ## Session affinity
 
-Session affinity, also known as sticky sessions, is a feature that allows you to route all HTTP requests from a client to the same container app replica. This feature is useful for stateful applications that require a consistent connection to the same replica.  For more information, see [Session affinity](sticky-sessions.md).
+Session affinity, also known as sticky sessions, is a feature that allows you to route all HTTP requests from a client to the same container app replica. This feature is useful for stateful applications that require a consistent connection to the same replica. For more information, see [Session affinity](sticky-sessions.md).
 
 ## Cross origin resource sharing (CORS)