Top40 refresh: Edit pass

Manika Dhiman · Manika Dhiman · commit 9a9dd6b02dd7 · 2025-02-27T14:43:08.000-08:00
diff --git a/azure-local/concepts/data-collection.md b/azure-local/concepts/data-collection.md
@@ -5,7 +5,7 @@ author: jasongerend
 ms.author: jgerend
 ms.topic: conceptual
 ms.service: azure-local
-ms.date: 04/24/2023
+ms.date: 02/27/2025
 ---
 
 # Azure Stack HCI data collection
@@ -14,7 +14,7 @@ ms.date: 04/24/2023
 
 [!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
 
-This topic describes required data collected to keep Azure Stack HCI secure, up to date, and working as expected.
+This article describes required data collected to keep Azure Stack HCI secure, up to date, and working as expected.
 
 Customer data, including the names, metadata, configuration, and contents of your on-premises virtual machines (VMs) is never sent to the cloud unless you turn on additional services like Azure Backup or Azure Site Recovery, or unless you enroll those VMs individually into cloud management services like Azure Arc.
 
@@ -27,7 +27,7 @@ We do collect diagnostic data. The data described below is required for Microsof
 
 This Azure Stack HCI data:
 
-- is not sent to Microsoft until the product is registered with Azure. When Azure Stack HCI is unregistered, this data collection stops.
+- isn't sent to Microsoft until the product is registered with Azure. When Azure Stack HCI is unregistered, this data collection stops.
 - is logged to the Microsoft-AzureStack-HCI/Analytic event channel.
 - is in JSON format, so that system administrators can examine and analyze the data being sent.
 
@@ -97,7 +97,7 @@ Azure Stack HCI collects:
        } 
    }
    ```
- 
+
 The output should look something like this:
 
 ```shell
diff --git a/azure-local/concepts/nested-virtualization.md b/azure-local/concepts/nested-virtualization.md
@@ -5,7 +5,7 @@ author: jasongerend
 ms.author: jgerend
 ms.topic: conceptual
 ms.service: azure-local
-ms.date: 04/17/2023
+ms.date: 02/27/2025
 ---
 
 # Nested virtualization in Azure Stack HCI
@@ -17,7 +17,7 @@ ms.date: 04/17/2023
 Nested virtualization is a feature that lets you run Hyper-V inside a Hyper-V virtual machine (VM). This allows you to maximize your hardware investments and gain flexibility in evaluation and testing scenarios.
 
    > [!IMPORTANT]
-   > Because Azure Stack HCI is intended as a virtualization host where you run all of your workloads in VMs, nested virtualization is not supported in production environments. For production use, Azure Stack HCI should be deployed on validated physical hardware.
+   > Because Azure Stack HCI is intended as a virtualization host where you run all of your workloads in VMs, nested virtualization isn't supported in production environments. For production use, Azure Stack HCI should be deployed on validated physical hardware.
 
 Some scenarios in which nested virtualization can be useful are:
 
@@ -42,7 +42,7 @@ To configure nested virtualization on a VM using PowerShell, see [Run Hyper-V in
 ## Nested virtualization processor support
 
 Azure Stack HCI, version 21H2 adds support for nested virtualization on AMD processors. Now you can run nested virtualization on first generation EPYC processors or newer generations (Naples, Rome, Milan).
- 
+
 Prerequisites:
 
 - Azure Stack HCI, version 21H2
diff --git a/azure-local/manage/cluster-powershell.md b/azure-local/manage/cluster-powershell.md
@@ -3,7 +3,7 @@ title: Manage Azure Stack HCI and Windows Server clusters using PowerShell
 description: Learn how to manage clusters on Azure Stack HCI and Windows Server using PowerShell
 author: JasonGerend
 ms.topic: how-to
-ms.date: 04/17/2023
+ms.date: 02/27/2025
 ms.author: jgerend
 ms.reviewer: stevenek
 ---
@@ -14,7 +14,9 @@ ms.reviewer: stevenek
 
 [!INCLUDE [azure-local-banner-22h2](../includes/azure-local-banner-22h2.md)]
 
-Windows PowerShell can be used to manage resources and configure features on your Azure Stack HCI and Windows Server clusters.
+This article describes how to manage Azure Stack HCI and Windows Server clusters using PowerShell.
+
+You can use Windows PowerShell to manage resources and configure features on your Azure Stack HCI and Windows Server clusters.
 
 You manage clusters from a remote computer, rather than on a host server in a cluster. This remote computer is called the management computer.
 
diff --git a/azure-local/manage/convert-to-stretched-cluster.md b/azure-local/manage/convert-to-stretched-cluster.md
@@ -5,7 +5,7 @@ ms.topic: how-to
 author: jasongerend
 ms.author: jgerend
 ms.reviewer: stevenek
-ms.date: 09/16/2021
+ms.date: 02/27/2025
 ---
 
 # Convert to a stretched Azure Stack HCI cluster
@@ -27,8 +27,8 @@ Refer to your OEM-provided documentation when adding new server hardware for use
 Follow these steps to prep the new server nodes:
 
 1. Place the new physical servers in the rack and cable them appropriately.
-1. Enable physical switch ports and adjust access control lists (ACLs) and VLAN IDs if applicable.
-1. Configure the correct IP address in the baseboard management controller (BMC) and apply all BIOS settings per OEM instructions.
+1. Enable physical switch ports and adjust access control lists and VLAN IDs if applicable.
+1. Configure the correct IP address in the baseboard management controller and apply all BIOS settings per OEM instructions.
 1. Apply the current firmware baseline to all components by using the tools that are provided by your OEM.
 1. Run OEM validation tests to ensure hardware homogeneity with the existing clustered servers.
 1. Install the Azure Stack HCI operating system on the new server. For detailed information, see [Deploy Azure Stack HCI](/azure-stack/hci/deploy/operating-system).
@@ -61,24 +61,24 @@ Ok, let's begin:
 
 1. List the site and server nodes currently in the cluster and create a `Sites.xml` file:
 
-    ~~~PowerShell
+    ```powershell
     Get-ClusterFaultDomainXML | out-file sites.xml
-    ~~~
+    ```
 
 1. Navigate to where the `Sites.xml` file is located on your management computer and open the file. For example, if there are two nodes currently in the cluster, the `Sites.xml` file will look like this:
 
-    ~~~cmd
+    ```PowerShell
     <Topology>
         <Site Name="Site1" Description="" Location="">
             <Node Name="NODE1" Description="" Location="">
             <Node Name="NODE2" Description="" Location="">
         </Site>
     <Topology>
-    ~~~
+    ```
 
 1. Using this example, add a new site name and the two new servers to the site so that the `Sites.xml` file looks like this:
 
-    ~~~PowerShell
+    ```powershell
     <Topology>
         <Site Name="Site1" Description="" Location="">
             <Node Name="NODE1" Description="" Location="">
@@ -89,42 +89,42 @@ Ok, let's begin:
             <Node Name="NODE4" Description="" Location="">
         </Site>
     <Topology>
-    ~~~
+    ```
 
 1. Modify the site (fault domain) information. The first command sets a variable to obtain and display the contents of the `Sites.xml` file. The second command sets the modification based on the variable `$XML`, as follows:
 
-    ~~~PowerShell
+    ```powershell
     $XML = Get-Content .\sites.xml | out-string
     Set-ClusterFaultDomainXML -xml $XML
-    ~~~
+    ```
 
 1. Verify that the modifications you made are correct:
 
-    ~~~PowerShell
+    ```powershell
     Get-ClusterFaultDomain
-    ~~~
+    ```
 
 ## Add new server nodes
 
 Once the sites have been created, you next add the new servers to the cluster. These servers would be added to the new site as specified previously and a new pool of the drives is also created.
 
 1. Using the `Add-ClusterNode` cmdlet, add the new server nodes to the cluster:
 
-    ~~~PowerShell
+    ```powershell
     Add-ClusterNode -Name NODE3, NODE4
-    ~~~
+    ```
 
 1. Once the servers are added, verify that they are in the correct new site using the following:
 
-    ~~~PowerShell
+    ```powershell
     Get-ClusterFaultDomain
-    ~~~
+    ```
 
 1. Verify the new drive pool is created. This may take a few minutes to create the storage pool from the newly added nodes:
 
-    ~~~PowerShell
+    ```powershell
     Get-StoragePool
-    ~~~
+    ```
 
 ## Create disks and replication
 
@@ -134,5 +134,5 @@ With Storage Replica, all disks must be of the same size and attributes. When cr
 
 ## Next steps
 
-- [Create volumes on Azure Stack HCI and Windows Server clusters](/windows-server/storage/storage-spaces/create-volumes)
-- [Stretch Cluster Replication Using Shared Storage](/windows-server/storage/storage-replica/stretch-cluster-replication-using-shared-storage)
+- [Create volumes on Azure Stack HCI and Windows Server clusters](/windows-server/storage/storage-spaces/create-volumes).
+- [Stretch cluster replication using shared storage](/windows-server/storage/storage-replica/stretch-cluster-replication-using-shared-storage).
diff --git a/azure-local/manage/create-stretched-volumes.md b/azure-local/manage/create-stretched-volumes.md
@@ -5,7 +5,7 @@ author: jasongerend
 ms.author: jgerend
 ms.reviewer: stevenek
 ms.topic: how-to
-ms.date: 05/16/2022
+ms.date: 02/27/2025
 ---
 
 # Create stretched cluster volumes and set up replication
@@ -112,7 +112,7 @@ Creating volumes and virtual disks for stretched clusters is a bit more involved
     Add-ClusterSharedVolume -Name 'Cluster Virtual Disk (Disk1)'
     ```
 
-You are done creating volumes, and ready to set up Storage Replica for replication.
+You're done creating volumes, and ready to set up Storage Replica for replication.
 
 ## Set up replication using PowerShell
 
@@ -142,7 +142,7 @@ In addition, the `Test-SRTopology` cmdlet will also measure:
 
 Once Test-SRTopology completes, it will create an .html file (TestSrTopologyReport with date and time) in your Windows Temp folder. Any warning or failures should be reviewed as they could cause Storage Replica to not be properly created.
 
-An example command that would run for 5 hours would be:
+An example command that would run for five hours would be:
 
 ```powershell
 Test-SRTopology -SourceComputerName Server1 -SourceVolumeName W: -SourceLogVolumeName X: -DestinationComputerName Server3 -DestinationVolumeName Y: -DestinationLogVolumeName Z: -DurationInMinutes 300 -ResultPath c:\temp
diff --git a/azure-local/manage/languages.md b/azure-local/manage/languages.md
@@ -4,7 +4,7 @@ description: This topic provides guidance on how to change languages in the Azur
 author: jasongerend
 ms.author: jgerend
 ms.topic: how-to
-ms.date: 02/26/2024
+ms.date: 02/27/2025
 ---
 
 # Change languages in Azure Stack HCI
@@ -22,7 +22,8 @@ This article explains how to change languages in:
 - Server Core in the Azure Stack HCI operating system
 
 ## Change the language in the management PC
-If you are using Windows 10 on your management PC, you can install a language pack for use in Windows 10, the apps you use, and the websites that you visit. You also can change your keyboard language, and set the input language in a language-preference order for websites and apps.
+
+If you're using Windows 10 on your management PC, you can install a language pack for use in Windows 10, the apps you use, and the websites that you visit. You also can change your keyboard language, and set the input language in a language-preference order for websites and apps.
 
 Changing either the language that you use in Windows 10 or the keyboard language doesn't affect the display language in Windows Admin Center.
 
@@ -32,6 +33,7 @@ Changing either the language that you use in Windows 10 or the keyboard language
 To learn more, see [Manage the input and display language settings in Windows 10](https://support.microsoft.com/help/4496404/windows-10-manage-the-input-and-display-language).
 
 ## Change the language in Windows Admin Center
+
 You can change the language in Windows Admin Center and the region format as needed according to your location. Changing either of these options in Windows Admin Center has no effect on the language setting of the management PC running Windows 10.
 
 To change the language in Windows Admin Center:
@@ -44,11 +46,13 @@ To change the language in Windows Admin Center:
 To learn more, see [Windows Admin Center Settings](/windows-server/manage/windows-admin-center/configure/settings).
 
 ## Change the language in Microsoft Edge
+
 You can add supported languages to Microsoft Edge, and reorder your language preferences in the browser. You also can add a foreign language translator extension to the browser to get translations.
 
 To learn more, see [Microsoft Edge language support](/deployedge/microsoft-edge-supported-languages).
 
 ## Change the language in Server Core
+
 If you need to change the language in Server Core of the Azure Stack HCI operating system, we recommend doing so after clustering your servers. You can add supported language packs to Server Core, and then change the language and keyboard layout to the one you want to use. You can also use a Windows PowerShell command to override the current language and keyboard input method.
 
 Each language pack is installed in the directory *%SystemRoot%\System32\\%Language-ID%*. For example, *C:\Windows\System32\es-ES* is the location of the Spanish language pack. Each language pack is about 50 MB. If you want to install all 38 language packs, the size of the required image that you create is about 2 GB.
@@ -80,4 +84,4 @@ To manually obtain and add language packs to the operating system:
 ## Next steps
 For more information, see also:
 
-- [Add or remove servers for an Azure Stack HCI cluster](./add-cluster.md)
+- [Add or remove servers for an Azure Stack HCI cluster](./add-cluster.md).
