Merge pull request #4869 from illfated/win_update_typo

Update how-windows-update-works.md: amend typo

windows/deployment/update/how-windows-update-works.md

@@ -16,7 +16,7 @@ ms.topic: article
 ---
 
 # How does Windows Update work?
-
+
 > Applies to: Windows 10
 
 The Windows Update workflow has four core areas of functionality: 
@@ -35,7 +35,7 @@ The Windows Update workflow has four core areas of functionality:
 5. The arbiter stages the downloaded files.
 
 
-### Install
+### Install
 1. Orchestrator initiates the installation.
 2. The arbiter calls the installer to install the package.
 
@@ -96,8 +96,8 @@ When users start scanning in Windows Update through the Settings panel, the foll
 - The Windows Update engine treats every service as a separate entity, even though multiple services may contain the same updates. 
    ![Windows Update scan log 2](images/update-scan-log-2.png)
 - Common service IDs 
-
-   >[!IMPORTANT]
+
+   > [!IMPORTANT]
    > ServiceId here identifies a client abstraction, not any specific service in the cloud. No assumption should be made of which server a serviceId is pointing to, it's totally controlled by the SLS responses. 
  
 |Service|ServiceId|
@@ -116,8 +116,8 @@ Common update failure is caused due to network issues. To find the root of the i
 - Look for "ProtocolTalker" messages to see client-server sync network traffic. 
 - "SOAP faults" can be either client- or server-side issues; read the message. 
 - The WU client uses SLS (Service Locator Service) to discover the configurations and endpoints of Microsoft network update sources – WU, MU, Flighting. 
-
-   >[!NOTE]
+
+   > [!NOTE]
    > Warning messages for SLS can be ignored if the search is against WSUS/SCCM. 
 
 - On sites that only use WSUS/SCCM, the SLS may be blocked at the firewall. In this case the SLS request will fail, and can’t scan against Windows Update or Microsoft Update but can still scan against WSUS/SCCM, since it’s locally configured.