Fixed bookmark, ran Acrolinx to boost score for one article.

Author: LouisBerner

azure-local/manage/troubleshoot-deployment.md

@@ -51,7 +51,7 @@ The multi-step resolution process includes the following steps:
 - [Clean up the Edge Device Azure Resource with incorrect VM switch information](#clean-up-the-edge-device-azure-resource-with-incorrect-vm-switch-information)
 - [Refresh the cloud data](#refresh-the-cloud-edgedevices-data)
 - [Restart the deployment via Azure portal](#restart-the-deployment-via-azure-portal)
-- [Recreate the lock on the seed node resource](#recreate-the-lock-on-the-seed-node-resource)
+- [Recreate the lock on the seed node](#recreate-the-lock-on-the-seed-node)
 
 > [!NOTE]
 > All the steps in this article need to be performed on the seed node.

azure-local/manage/troubleshoot-sdn-deployment.md

@@ -17,7 +17,7 @@ This article provides guidance on how to troubleshoot issues that you may encoun
 
 If the deployment of virtual machines (VM) for the various SDN components, including Network Controller, Software Load Balancer, or Gateway times out, you see the following error:
 
-*....is not ready after the 1800 second timeout.*
+*....isn't ready after the 1,800 second timeout.*
 
 You may see this message in Windows Admin Center during the deployment of Network Controller, Software Load Balancer, or Gateway.
 
@@ -31,7 +31,7 @@ To identify and troubleshoot the cause of the failure in your SDN deployment thr
 
 - [Verify connectivity to the SDN URI or SDN cluster](#verify-connectivity-to-the-sdn-uri-or-sdn-cluster).
 
-After you've completed these checks and resolved any identified issues through troubleshooting, proceed with deploying SDN again. We also recommend [collecting logs](#collect-logs-for-sdn-components) to determine why the deployment of an SDN VM had failed.
+After you've completed these checks and resolved any identified issues through troubleshooting, proceed with deploying SDN again. We also recommend [collecting logs](#collect-logs-for-sdn-components) to determine why the deployment of an SDN VM failed.
 
 ### Download the correct VHDX file
 
@@ -61,7 +61,7 @@ Follow these steps to verify connectivity of the management network VLAN:
 
 ### Ensure that Windows Defender and firewall policies permit WinRM connectivity
 
-You must enable Windows Remote Management (WinRM) and PowerShell remoting to start configuration on the Network Controller VMs that have been deployed. If this is not done, a timeout error occurs.
+You must enable Windows Remote Management (WinRM) and PowerShell remoting to start configuration on the Network Controller VMs that deployed. If this isn't done, a timeout error occurs.
 
 To verify or enable WinRM and PowerShell remoting, perform these steps:
 
@@ -127,7 +127,7 @@ After enabling dynamic DNS, you may be able to move the `SDNAPI` microservice by
 
 ## Collect logs for SDN components
 
-After successfully troubleshooting the deployment issue, we recommend collecting logs to determine why the deployment of an SDN VM had failed.
+After successfully troubleshooting the deployment issue, we recommend collecting logs to determine why the deployment of an SDN VM failed.
 
 Follow these steps to collect guest logs for the SDN VM: