From b9d170a4d5f48166d8bb5738a510fff445a84d86 Mon Sep 17 00:00:00 2001
From: Charles Inglis <32555877+cinglis-msft@users.noreply.github.com>
Date: Mon, 13 Apr 2020 09:35:03 -0700
Subject: [PATCH] fix space between [] and () for md link

---
 .../deployment/update/update-compliance-configuration-script.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/windows/deployment/update/update-compliance-configuration-script.md b/windows/deployment/update/update-compliance-configuration-script.md
index fd14c25d99..2167039e0c 100644
--- a/windows/deployment/update/update-compliance-configuration-script.md
+++ b/windows/deployment/update/update-compliance-configuration-script.md
@@ -41,7 +41,7 @@ When using the script in the context of troubleshooting, use `Pilot`. Enter `Run
 2. Configure `commercialIDValue` to your CommercialID. To get your CommercialID, see [Getting your CommercialID](update-compliance-get-started.md#get-your-commercialid).
 3. Run the script. The script must be run in System context.
 4. Examine the Logs output for any issues. If there were issues:
-   - Compare Logs output with the required settings covered in [Manually Configuring Devices for Update Compliance] (update-compliance-configuration-manual.md).
+   - Compare Logs output with the required settings covered in [Manually Configuring Devices for Update Compliance](update-compliance-configuration-manual.md).
    - Examine the script errors and refer to the [script error reference](#script-error-reference) on how to interpret the codes.
    - Make the necessary corrections and run the script again.
 5. When you no longer have issues, proceed to using the script for more broad deployment with the `Deployment` folder.