Aug 16 approved and ready to publish

MicrosoftDocs · Aug 16, 2024 · e9cefb9 · e9cefb9
1 parent 3fbea49
commit e9cefb9
Show file tree

Hide file tree

Showing 3 changed files with 4 additions and 4 deletions.
diff --git a/docs/global-secure-access/how-to-install-windows-client.md b/docs/global-secure-access/how-to-install-windows-client.md
@@ -3,7 +3,7 @@ title: The Global Secure Access client for Windows
 description: The Global Secure Access client secures network traffic at the end-user device. This article describes how to download and install the Windows client.
 ms.service: global-secure-access
 ms.topic: how-to
-ms.date: 08/13/2024
+ms.date: 08/16/2024
 ms.author: jayrusso
 author: HULKsmashGithub
 manager: amycolannino

diff --git a/...-secure-access/troubleshoot-global-secure-access-client-advanced-diagnostics.md b/...-secure-access/troubleshoot-global-secure-access-client-advanced-diagnostics.md
@@ -3,7 +3,7 @@ title: "Troubleshoot the Global Secure Access client: diagnostics"
 description: Troubleshoot the Global Secure Access client using the health check tab in the advanced diagnostics utility.
 ms.service: global-secure-access
 ms.topic: troubleshooting
-ms.date: 08/13/2024
+ms.date: 08/16/2024
 ms.author: jayrusso
 author: HULKsmashGithub
 manager: amycolannino

diff --git a/...ure-access/troubleshoot-global-secure-access-client-diagnostics-health-check.md b/...ure-access/troubleshoot-global-secure-access-client-diagnostics-health-check.md
@@ -3,7 +3,7 @@ title: "Troubleshoot the Global Secure Access client: Health check"
 description: Troubleshoot the Global Secure Access client using the Health check tab in the Advanced diagnostics utility.
 ms.service: global-secure-access
 ms.topic: troubleshooting
-ms.date: 08/13/2024
+ms.date: 08/16/2024
 ms.author: jayrusso
 author: HULKsmashGithub
 manager: amycolannino
@@ -270,7 +270,7 @@ If the test fails:
 This test checks whether the proxy is configured on the device. If the end-user device is configured to use a proxy for outgoing traffic to the internet, you must exclude the destination IPs/FQDNs acquired by the client with a Proxy Auto-Configuration (PAC) file or with the Web Proxy Auto-Discovery (WPAD) protocol.
 
 #### Change the PAC file
-Add the FQDNs/IPs to be tunneled to Global Secure Access edge as exclusions in the PAC file, so that HTTP requests for these destinations won’t be redirected to the proxy. (These FQDNs/IPs are also set to be tunneled to Global Secure Access in the forwarding profile.)
+Add the IPs/FQDNs to be tunneled to Global Secure Access edge as exclusions in the PAC file, so that HTTP requests for these destinations won't redirect to the proxy. (These IPs/FQDNs are also set to tunnel to Global Secure Access in the forwarding profile.)
 To show the client's health status properly, add the FQDN used for health probing to the exclusions list: `.edgediagnostic.globalsecureaccess.microsoft.com`.
 
 Example PAC file containing exclusions: