incorporating feedback

Author: ShawnJackson

includes/vpn-gateway-customer-controlled-gateway-maintenance-faq.md

@@ -20,11 +20,11 @@ The Network Gateways scope includes gateway resources in networking services. Th
 
 ### Which maintenance does customer-controlled maintenance support?
 
-Azure services go through periodic maintenance updates to improve functionality, reliability, performance, and security. After you configure a maintenance window for your resources, guest OS and service maintenance are performed during that window. Customer-controlled maintenance doesn't cover updates beyond the host updates (for example, TOR and power) and critical security updates.  
+Azure services go through periodic maintenance updates to improve functionality, reliability, performance, and security. After you configure a maintenance window for your resources, guest OS maintenance and service maintenance are performed during that window. Customer-controlled maintenance doesn't cover host updates (beyond the host updates for Power, for example) and critical security updates.
 
 ### Can I get advanced notification of the maintenance?
 
-At this time, you can't get advanced notification for the maintenance of network gateway resources.
+At this time, you can't get advanced notification for the maintenance of Network Gateway REST API resources.
 
 ### Can I configure a maintenance window shorter than five hours?
 
@@ -54,7 +54,7 @@ It might take up to 24 hours for Network Gateways to follow the maintenance sche
 
 ### Are there any limitations on using customer-controlled maintenance based on the Basic SKU public IP address?
 
-Yes. Gateway resources that use a Basic SKU public IP address can have service updates only after the customer-controlled maintenance schedule. For these gateways, guest OS maintenance does *not* follow the customer-controlled maintenance schedule because of infrastructure limitations.
+Yes. Customer-controlled maintenance doesn't work for resources that use Basic SKU public IP addresses, except in the case of service updates. For these gateways, guest OS maintenance does *not* follow the customer-controlled maintenance schedule because of infrastructure limitations.
 
 ### How should I plan maintenance windows when using VPN and ExpressRoute in a coexistence scenario?
 

includes/vpn-gateway-deprecate-sku-faq.md

@@ -6,9 +6,9 @@ ms.service: vpn-gateway
 ms.topic: include
 ---
 
-### Can I create a new gateway by using the Standard or High Performance SKU after the deprecation announcement on November 30, 2023?
+### Can I create a new gateway that uses a Standard or High Performance SKU after the deprecation announcement on November 30, 2023?
 
-No. As of December 1, 2023, you can't create gateways by using the Standard or High Performance SKU. You can create gateways by using VpnGw1 and VpnGw2 for the same price as the Standard and High Performance SKUs, listed respectively on the [pricing page](https://azure.microsoft.com/pricing/details/vpn-gateway/).
+No. As of December 1, 2023, you can't create gateways that use Standard or High Performance SKUs. You can create gateways that use VpnGw1 and VpnGw2 SKUs for the same price as the Standard and High Performance SKUs, listed respectively on the [pricing page](https://azure.microsoft.com/pricing/details/vpn-gateway/).
 
 ### How long will my existing gateways be supported on the Standard and High Performance SKUs?
 
@@ -20,25 +20,25 @@ No, there's no action required right now. You can migrate your gateways starting
 
 ### Which SKU can I migrate my gateway to?
 
-When gateway SKU migration becomes available, you can migrate your gateways as follows:
+When gateway SKU migration becomes available, SKUs can be migrated as follows:
 
 * Standard to VpnGw1
 * High Performance to VpnGw2
 
 ### What if I want to migrate to an AZ SKU?
 
-You can't migrate gateways from a deprecated SKU to an AZ SKU. However, all gateways that are still using the Standard or High Performance SKU after September 30, 2025, will be migrated and upgraded automatically to the AZ SKUs as follows:
+You can't migrate your deprecated SKU to an AZ SKU. However, all gateways that are still using the Standard or High Performance SKU after September 30, 2025, will be migrated and upgraded automatically to the AZ SKUs as follows:
 
 * Standard to VpnGw1AZ
 * High Performance to VpnGw2AZ
 
-After your gateways are automatically migrated and upgraded to the AZ SKUs, you can resize within that SKU family if necessary. For AZ SKU pricing, see the [pricing page](https://azure.microsoft.com/pricing/details/vpn-gateway/). For throughput information by SKU, see [About gateway SKUs](https://go.microsoft.com/fwlink/?linkid=2256302).
+You can use this strategy to have your SKUs automatically migrated and upgraded to an AZ SKU. You can then resize your SKU within that SKU family if necessary. For AZ SKU pricing, see the [pricing page](https://azure.microsoft.com/pricing/details/vpn-gateway/). For throughput information by SKU, see [About gateway SKUs](https://go.microsoft.com/fwlink/?linkid=2256302).
 
 ### Will there be any pricing difference for my gateways after migration?
 
-If you migrate your gateways by September 30, 2025, there will be no pricing difference. VpnGw1 and VpnGw2 SKUs are offered at the same price as Standard and High Performance SKUs, respectively.
+If you migrate your SKUs by September 30, 2025, there will be no pricing difference. VpnGw1 and VpnGw2 SKUs are offered at the same price as Standard and High Performance SKUs, respectively.
 
-If you don't migrate by that date, your gateways will automatically be migrated and upgraded to AZ SKUs. In that case, there's a pricing difference.
+If you don't migrate by that date, your SKUs will automatically be migrated and upgraded to AZ SKUs. In that case, there's a pricing difference.
 
 ### Will there be any performance impact on my gateways with this migration?
 

includes/vpn-gateway-faq-bgp-include.md

@@ -31,7 +31,7 @@ You can't specify these ASNs for your on-premises VPN devices when you're connec
 
 ### Can I use 32-bit (4-byte) ASNs?
 
-Yes, Azure VPN Gateway now supports 32-bit (4-byte) ASNs. To configure a VPN gateway by using ASN in decimal format, use Azure PowerShell, the Azure CLI, or the Azure SDK.
+Yes, Azure VPN Gateway now supports 32-bit (4-byte) ASNs. To configure by using ASN in decimal format, use Azure PowerShell, the Azure CLI, or the Azure SDK.
 
 ### What private ASNs can I use?
 

includes/vpn-gateway-faq-p2s-all-include.md

@@ -54,7 +54,7 @@ Depending on the VPN client software that you use, you might be able to connect
 
 ### Can I configure a point-to-site client to connect to multiple virtual networks at the same time?
 
-Yes. Point-to-site client connections to a virtual network gateway deployed in a VNet that's peered with other VNets might have access to other peered VNets. Point-to-site clients can connect to peered VNets as long as the peered VNets use the **Use remote gateways** or **Allow gateway transit** feature. For more information, see [About point-to-site VPN routing](../articles/vpn-gateway/vpn-gateway-about-point-to-site-routing.md).
+Yes. Point-to-site client connections to a VPN gateway deployed in a VNet that's peered with other VNets can have access to the other peered VNets, as long as they meet certain configuration criteria. For a point-to-site client to have access to a peered VNet, the peered VNet (the VNet without the gateway) must be configured with the **Use remote gateways** attribute. The VNet with the VPN gateway must be configured with **Allow gateway transit**. For more information, see [About point-to-site VPN routing](../articles/vpn-gateway/vpn-gateway-about-point-to-site-routing.md).
 
 ### How much throughput can I expect through site-to-site or point-to-site connections?
 

includes/vpn-gateway-faq-p2s-azurecert-include.md

@@ -7,7 +7,7 @@
 ---
 
 
-### What should I do if I get a certificate mismatch when connecting through certificate authentication?
+### What should I do if I get a certificate mismatch for a point-to-site certificate authentication connection?
 
 Clear the **Verify the server's identity by validating the certificate** checkbox. Or, add the server's fully qualified domain name (FQDN) along with the certificate when you're creating a profile manually. You can do this by running `rasphone` from a command prompt and selecting the profile from the dropdown list.