Acrolinx

Author: JackStromberg

articles/application-gateway/for-containers/application-gateway-for-containers-components.md

@@ -108,5 +108,5 @@ Application Gateway for Containers enforces the following timeouts as requests a
 | ------- | --------- | ----------- |
 | Request Timeout | 60 seconds | time for which AGC waits for the backend target response. |
 | HTTP Idle Timeout | 5 minutes | idle timeout before closing an HTTP connection. |
-| Stream Idle Timeout | 5 minutes | idle timeout before closing an individual streams carried by an HTTP connection. |
+| Stream Idle Timeout | 5 minutes | idle timeout before closing an individual stream carried by an HTTP connection. |
 | Upstream Connect Timeout | 5 seconds | time for establishing a connection to the backend target. |

articles/application-gateway/for-containers/how-to-url-redirect-ingress-api.md

@@ -21,7 +21,7 @@ URL redirects take advantage of the [RequestRedirect rule filter](https://gatewa
 ## Redirection
 A redirect sets the response status code returned to clients to understand the purpose of the redirect. The following types of redirection are supported:
 
-- 301 (Moved permanently): Indicates that the target resource has been assigned a new permanent URI. Any future references to this resource uses one of the enclosed URIs. Use 301 status code for HTTP to HTTPS redirection.
+- 301 (Moved permanently): Indicates that the target resource has been assigned a new permanent URI. Any future references to this resource use one of the enclosed URIs. Use 301 status code for HTTP to HTTPS redirection.
 - 302 (Found): Indicates that the target resource is temporarily under a different URI. Since the redirection can change on occasion, the client should continue to use the effective request URI for future requests.
 
 ## Redirection capabilities