Code review changes

Author: gregg-miskelly

docs/debugger/adapting-to-removal-of-windows-arm32-dotnet-debugging.md renamed to docs/debugger/adapt-to-removal-of-windows-arm32-dotnet-debugging.md

@@ -1,5 +1,5 @@
 ---
-title: "Adapting To Removal of Windows Arm32 .NET Debugging"
+title: "Adapt to removal of Windows Arm32 .NET debugging"
 description: Provides guidance on how to adapt to the removal of Windows Arm32 .NET Debugging support
 ms.date: "12/12/2024"
 ms.topic: "error-reference"
@@ -13,17 +13,17 @@ manager: mijacobs
 ms.subservice: debug-diagnostics
 ---
 
-# Adapting To Removal of Windows Arm32 .NET Debugging
+# Adapt to removal of Windows Arm32 .NET debugging
 
 .NET support for Windows on Arm32 has ended. Debugging support for this platform will be removed from Visual Studio 2022 starting with the 17.14 update. This article lists potential options for customers currently debugging .NET Code on  Windows Arm32. 
 
 
 ## Option 1: Run code in an Arm64 process 
 
-If your device runs Arm64 Windows or can be upgraded to it, the easiest way is to migrate the debugged process from Arm32 to Arm64. How to do switch to Arm64 depends on the type of project being used: 
+If your device runs Arm64 Windows or can be upgraded to it, the easiest way is to migrate the debugged process from Arm32 to Arm64. How to manage the switch to Arm64 depends on the type of project you're using: 
 
 * For Universal Windows Platform (UWP) apps, see [Update app architecture from Arm32 to Arm64](/windows/arm/arm32-to-arm64). 
-* For processes that have their own native executable which is self-hosting the .NET Runtime, the native project needs to be configured to target Arm64. 
+* For processes that have their own native executable that's self-hosting the .NET Runtime, the native project needs to be configured to target Arm64. 
 * If the executable project is a .NET project, then something is likely specifying the `RuntimeIdentifier` MSBuild property. `RuntimeIdentifier` should be updated to target `win-arm64` instead of `win-arm` (or similar runtime IDs). 
 
 
@@ -34,12 +34,12 @@ Visual Studio 17.12 can be used from the Long-Term Servicing Channel (LTSC). For
 
 ## Option 3: Start without debugging 
 
+If you have a project that you still want to run but doesn't require debugging, use **Debug->Start without debugging** to run the project. Since the debugger isn't available, you would need to diagnose any problems by using logging. 
+
 > [!NOTE]
 > This option is not recommended since .NET support for Windows on Arm32 has ended.
 
-If you have a project that you still want to run but doesn't require debugging, 'Debug->Start without debugging' can be used to run the project. Since the debugger isn't available, any problem would need to be diagnosed using logging. 
-
 
 ## Option 4: Target Linux 
 
-The .NET Runtime continues to support Arm32 Linux. For IoT hardware which isn't capable of running Arm64 Windows but is capable of running Arm32 Linux, the only supported path for running .NET Code on that hardware would be to switch to Linux.
+The .NET Runtime continues to support Arm32 Linux. For IoT hardware that isn't capable of running Arm64 Windows but is capable of running Arm32 Linux, the only supported path for running .NET Code on that hardware would be to switch to Linux.

docs/debugger/toc.yml

@@ -294,8 +294,8 @@
         href: error-unable-to-connect-to-the-machine-name-the-machine-cannot-be-found-on-the-network.md
       - name: Remote machine does not appear in a Remote Connections dialog
         href: error-remote-machine-does-not-appear-in-a-remote-connections-dialog.md
-      - name: Adapting To Removal of Windows ARM32 .NET Debugging
-        href: adapting-to-removal-of-windows-arm32-dotnet-debugging.md
+      - name: Adapt to removal of Windows Arm32 .NET debugging
+        href: adapt-to-removal-of-windows-arm32-dotnet-debugging.md
   - name: Attach to process
     items:
     - name: Attach to running processes with the debugger