TOC & Acrolinx updates

Author: v-tappelgate

support/windows-client/setup-upgrade-and-drivers/use-windows-setup-compatibility-scan-logs-to-identify-blocking-issues.md

@@ -24,7 +24,7 @@ During a feature update or in-place upgrade, Windows Setup runs a compatibility
 
 ## Symptoms
 
-You run a Windows feature update or an in-place upgrade on a Windows computer. The Windows Setup process fails, and produces the `0xC1900208` error code. This code indicates a compatibility issue. Typically, this means that the computer has an application or driver that's not compatible with the new version or feature update. This might be true even if the incompatible application or driver has already been uninstalled.
+You run a Windows feature update or an in-place upgrade on a Windows computer. The Windows Setup process fails, and produces the `0xC1900208` error code. This code indicates a compatibility issue. The computer has an application or driver that's not compatible with the new version or feature update. You might see this issue even if the incompatible application or driver has already been uninstalled.
 
 > [!NOTE]  
 > If Windows Setup produces the `0xC1900210` code, then there are no compatibility issues.
@@ -35,7 +35,7 @@ You run a Windows feature update or an in-place upgrade on a Windows computer. T
 > If you want to test compatibility before you deploy a feature update or in-place upgrade at scale (by using Microsoft Intune or Microsoft Endpoint Manager), review [How to test compatibility at scale](#how-to-test-compatibility-at-scale). That section describes special considerations and techniques to supplement the following procedure.
 
 1. Use the compatibility scan logs (CompatData\*.xml or \*_APPRAISER_HumanReadable.xml) to identify the blocking issue. For more information, see [How to use the compatibility scan logs to identify the blocking issue](#how-to-use-the-compatibility-scan-logs-to-identify-the-blocking-issue).
-1. Fix the problematic application or driver. For example, uninstall it or upgrade it to a compatible version. If the human-readable log points to a specific file, and the related application or driver has already been installed, remove the indicated file.
+1. Fix the problematic application or driver. For example, uninstall it or upgrade it to a compatible version. If the human-readable log points to a specific file, and the related application or driver has already been uninstalled, remove the indicated file.
 1. If you intend to use the same media for the next setup attempt, clear the setup-related caches:
 
    - Empty the C:\Windows\SoftwareDistribution\Download folder.
@@ -50,7 +50,7 @@ You run a Windows feature update or an in-place upgrade on a Windows computer. T
 
    For more information, see [Windows Setup Command-Line Options: /Compat](/windows-hardware/manufacture/desktop/windows-setup-command-line-options?view=windows-11#compat).
 
-1. Re-check the logs to make sure that the issue doesn't recur, and that Setup generated the `0xC1900210` code. If it generated the `0xC1900208` code, review the logs for further compatibility issues.
+1. Recheck the logs to make sure that the issue doesn't recur, and that Setup generated the `0xC1900210` code. If it generated the `0xC1900208` code, review the logs for further compatibility issues.
 1. When the compatibility checks pass, retry the upgrade.
 
 ### How to use the compatibility scan logs to identify the blocking issue
@@ -60,16 +60,16 @@ Over the course of the setup process, Windows Setup stores logs in different loc
 > [!TIP]  
 > These folders are hidden. To make sure that you can search the folders, in File Explorer, select **View** and make sure that **Hidden items** is selected.
 
-- Logs that're stored during the Downlevel, OOBE, or Rollback stages of the Setup process: C:\\$WINDOWS.~BT\\Sources\\Panther\\CompatData\<date-time>.xml.
+- Logs that Setup stores during the Downlevel, OOBE, or Rollback stages of the Setup process: C:\\$WINDOWS.~BT\\Sources\\Panther\\CompatData\<date-time>.xml.
 
   > [!NOTE]  
   > In this file path, \<date-time> represents the data and time when the file was created. The latest timestamp is most relevant to the troubleshooting process.
 
    :::image type="content" source="./media/use-windows-setup-compatibility-scan-logs-to-identify-blocking-issues/list-of-compatdata-log-files.png" alt-text="Screenshot that shows a directory listing the compatibility log files.":::
 
-- Logs that're stored after the OOBE stage of the Setup process: C:\Windows\Panther\.
+- Logs that Setup stores after the OOBE stage of the Setup process: C:\Windows\Panther\.
 
-- Human readable log that's stored by the compatibility appraiser: Search the operating system drive for \*_APPRAISER_HumanReadable.xml.
+- Human readable log that the compatibility appraiser stores: Search the operating system drive for \*_APPRAISER_HumanReadable.xml.
 
 For more information about Setup log files, see [Windows upgrade log files](/windows/deployment/upgrade/log-files).
 
@@ -96,7 +96,7 @@ Open the most recent CompatData\<date-time>.xml.xml and search for the following
 
 #### Using the \*_APPRAISER_HumanReadable.xml file
 
-The human-readable log file uses a flattened, easier-to-scan XML than the CompatData logs. You can use this log to find exact file paths to files that block Setup, including .exe or .dll files that're left behind after you uninstalled an application. To find this information, follow these steps:
+The human-readable log file uses a flattened, easier-to-scan XML than the CompatData logs. You can use this log to find exact file paths to files that block Setup, including .exe or .dll files that are left behind after you uninstalled an application. To find this information, follow these steps:
 
 1. Open the most recent \*_APPRAISER_HumanReadable.xml file, and then search for the **DT_ANY_FMC_BlockingApplication=True** string.
 
@@ -114,13 +114,13 @@ To help resolve compatibility issues, use the [SetupDiag](/windows/deployment/up
 SetupDiag.exe /LogsPath "C:\Temp\WindowsSetupLogs" /Output "C:\Temp\SetupDiag-Results.txt"
 ```
 
-You can aggregate SetupDiag outputs into into your reporting pipeline.
+You can aggregate SetupDiag outputs into your reporting pipeline.
 
 ## More information
 
 Microsoft Compatibility Appraiser creates registry entries in the `HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion\AppCompatFlags` subkey. This process runs as the \Microsoft\Windows\Application Experience\Microsoft Compatibility Appraiser scheduled task. 
 
-Windows inbox and appraiser processes and Dynamic update processes write and refresh compatibility intelligence when they run scans. Windows Setup, Windows Update, and enterprise tools then use this information to to decide if a device is ready for a target release without running a full upgrade.
+Windows inbox and appraiser processes and Dynamic update processes write and refresh compatibility intelligence when they run scans. Windows Setup, Windows Update, and enterprise tools then use this information to decide if a device is ready for a target release without running a full upgrade.
 
 ## References
 

support/windows-client/toc.yml

@@ -879,6 +879,8 @@ items:
       href: ./setup-upgrade-and-drivers/winre-cannot-built-deploy-image-captured-non-uefi-computer.md
     - name: You can't access an EFI system partition
       href: ./setup-upgrade-and-drivers/cant-access-efi-system-partition.md
+    - name: How to use the Windows Setup compatibility scan logs to identify blocking issues
+      href: ./setup-upgrade-and-drivers/use-windows-setup-compatibility-scan-logs-to-identify-blocking-issues.md
   - name: Power management
     items:
     - name: Desktop wakes up unexpectedly from sleep or hibernation