date and minor acrolinx fixes

Author: greg-lindsay

articles/application-gateway/application-gateway-faq.yml

@@ -6,7 +6,7 @@ metadata:
   author: greg-lindsay
   ms.service: application-gateway
   ms.topic: faq
-  ms.date: 11/06/2023
+  ms.date: 02/26/2024
   ms.author: greglin
   ms.custom: references_regions, devx-track-azurepowershell
 title: Frequently asked questions about Application Gateway
@@ -202,7 +202,7 @@ sections:
 
       - question: Can I change the virtual network or subnet for an existing application gateway?
         answer: |
-          You can move an application gateway across subnets within the same virtual network only. It's supported with v1 with a public and private frontend (dynamic allocation) and v2 with a public frontend only. We cannot move the application gateway to another subnet if the private frontend IP configuration is statically allocated. The application gateway should be in a *Stopped* state to perform this action. Stopping or starting v1 changes the public IP. This operation can only be done by using Azure PowerShell and the Azure CLI by running the following commands:
+          You can move an application gateway across subnets within the same virtual network only. It's supported with v1 with a public and private frontend (dynamic allocation) and v2 with a public frontend only. We can't move the application gateway to another subnet if the private frontend IP configuration is statically allocated. The application gateway should be in a *Stopped* state to perform this action. Stopping or starting v1 changes the public IP. This operation can only be done by using Azure PowerShell and the Azure CLI by running the following commands:
           
           **Azure PowerShell**
 
@@ -473,7 +473,7 @@ sections:
         answer: Yes. Both Layer 7 and Layer 4 routing through application gateway use the same frontend IP configuration. This way, you can direct all your clients to a single IP address (public or private) and the same gateway resource will route them based on the configured listener protocols and the ports.
 
       - question: Can I use TCP or TLS proxy for HTTP(S) traffic?
-        answer: While the HTTP(S) traffic can be served through L4 proxy protocols as well, we do not recommend doing so. The L7 proxy solution of Application Gateway offers greater control and security over the HTTP(S) protocols through advanced features such Rewrites, Session Affinity, Redirection, WebSockets, WAF and more.
+        answer: While the HTTP(S) traffic can be served through L4 proxy protocols as well, we don't recommend doing so. The L7 proxy solution of Application Gateway offers greater control and security over the HTTP(S) protocols through advanced features such Rewrites, Session Affinity, Redirection, WebSockets, WAF and more.
 
       - question: What are the property names for Layer 4 proxy?
         answer: |
@@ -501,25 +501,25 @@ sections:
         answer: Absolutely. Similar to Layer 7 proxy, you can add a private endpoint to the backend pool of your application gateway. This private endpoint must be deployed in an adjacent subnet of the same virtual network of your application gateway.
 
       - question: Does Application Gateway use Keepalive connection for backend servers?
-        answer: It does not use Keepalive for backend connections. For each incoming request on the frontend listener connection, Application Gateway initiates a new backend connection to fulfill that request.
+        answer: It doesn't use Keepalive for backend connections. For each incoming request on the frontend listener connection, Application Gateway initiates a new backend connection to fulfill that request.
 
       - question: Which IP address does the backend server see when a connection is established with Application Gateway?
-        answer: The backend server sees the IP address of the application gateway. Currently, we do not support “Client IP preservation” through which the backend application can be made aware of the original client’s IP address.
+        answer: The backend server sees the IP address of the application gateway. Currently, we don't support “Client IP preservation” through which the backend application can be made aware of the original client’s IP address.
 
       - question: How can I set the SSL policy for TLS listeners?
-        answer: The same SSL policy configuration is applicable for both Layer 7 (HTTPS) as well as Layer 4 (TLS). Currently, we do not support SSL Profile (listener-specific SSL policy or Mutual Authentication) for TLS listeners.
+        answer: The same SSL policy configuration is applicable for both Layer 7 (HTTPS) as well as Layer 4 (TLS). Currently, we don't support SSL Profile (listener-specific SSL policy or Mutual Authentication) for TLS listeners.
 
       - question: Does Application Gateway support session affinity for Layer 4 routing?
-        answer: No. Routing a client to the same backend server is not supported at the moment. The connections will be distributed in a round-robin manner to the servers in a backend pool.
+        answer: No. Routing a client to the same backend server isn't supported at the moment. The connections will be distributed in a round-robin manner to the servers in a backend pool.
 
       - question: Does the autoscale feature work with Layer 4 proxy?
         answer: Yes, the autoscale feature will operate for spikes and reductions in traffic for TLS or TCP protocol as well.
 
       - question: Is Web Application Firewall (WAF) supported for Layer 4 traffic?
-        answer: The Web Application Firewall (WAF) capabilities will not work for Layer 4 usage.
+        answer: The Web Application Firewall (WAF) capabilities won't work for Layer 4 usage.
 
       - question: Does Application Gateway’s Layer 4 proxy support UDP protocol?
-        answer: No. UDP support is not available at this time.
+        answer: No. UDP support isn't available at this time.
 
   - name: Configuration - ingress controller for AKS
     questions:

articles/application-gateway/how-to-tcp-tls-proxy.md

@@ -6,7 +6,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: how-to
-ms.date: 10/26/2023
+ms.date: 02/26/2024
 ms.author: greglin
 ---
 

articles/application-gateway/monitor-application-gateway-reference.md

@@ -6,7 +6,7 @@ ms.author: greglin
 ms.topic: conceptual
 ms.service: application-gateway
 ms.custom: subject-monitoring
-ms.date: 08/17/2023
+ms.date: 02/26/2024
 ---
 <!-- VERSION 2.2
 Template for monitoring data reference article for Azure services. This article is support for the main "Monitoring [servicename]" article for the service. -->

articles/application-gateway/monitor-application-gateway.md

@@ -5,7 +5,7 @@ author: greg-lindsay
 ms.author: greglin
 ms.service: application-gateway
 ms.topic: conceptual
-ms.date: 10/16/2023
+ms.date: 02/26/2024
 ---
 
 <!-- VERSION 2.2

articles/application-gateway/multiple-site-overview.md

@@ -4,7 +4,7 @@ description: This article provides an overview of the Azure Application Gateway
 services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
-ms.date: 08/23/2023
+ms.date: 02/26/2024
 ms.author: greglin
 ms.topic: conceptual
 ---

articles/application-gateway/overview-v2.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: overview
-ms.date: 09/22/2023
+ms.date: 02/26/2024
 ms.author: greglin
 ms.custom: references_regions
 ---

articles/application-gateway/tcp-tls-proxy-overview.md

@@ -5,7 +5,7 @@ services: application-gateway
 author: greg-lindsay
 ms.service: application-gateway
 ms.topic: conceptual
-ms.date: 09/22/2023
+ms.date: 02/26/2024
 ms.author: greglin
 ---