Updates

Author: alkohli

azure-local/upgrade/upgrade-22h2-to-23h2-powershell.md

@@ -29,9 +29,9 @@ This article describes how to upgrade the operating system (OS) for Azure Local
 
 With the 2505 release, a direct upgrade path from version 20349.xxxx (22H2) to version 26100.xxxx (24H2) is available. Skipping the upgrade to the version 26100.xxxx is one less upgrade hop and helps reduce reboots and maintenance planning prior to the solution upgrade.
 
-    - Make sure to consult with your hardware vendor to determine if version 26100.xxxx OS is supported before performing the upgrade.
-    - After the OS upgrade, you can wait for the solution upgrade and the drivers to become available. This option is currently in preview and is not recommended for production workloads.
-    - There is an exception to the preceding recommendation if you are using stretch clusters. Stretch clusters should directly move to version 26100.xxxx (24H2) in 2508. This version contains critical bug fixes.
+- Make sure to consult with your hardware vendor to determine if version 26100.xxxx OS is supported before performing the upgrade.
+- After the OS upgrade, you can wait for the solution upgrade and the drivers to become available. This option is currently in preview and is not recommended for production workloads.
+- There is an exception to the preceding recommendation if you are using stretch clusters. Stretch clusters should directly move to version 26100.xxxx (24H2) in 2508. This version contains critical bug fixes.
 
 For more information about the various upgrade paths, see the blog post on [Upgrade Azure Local to new OS version](https://techcommunity.microsoft.com/blog/azurearcblog/upgrade-azure-local-operating-system-to-new-version/4423827).
 

azure-stack/zone-pivot-groups.yml

@@ -91,7 +91,7 @@ groups:
   - id: os-23h2
     title: To 25398.xxxx 
   - id: os-24h2
-    title: To 261000.xxxx 
+    title: To 26100.xxxx 
 # BELOW: entries inherited from github.com/microsoftdocs/azure-docs-pr/articles/zone-pivot-groups.yml for reuse.
 # For consistency across Docs. This includes: client OSes, languages, etc.