Merge pull request #17860 from LouisBerner/v-loberner-ado-427701-may-freshness

Updated for freshness + Acrolinx.

Author: prmerger-automator[bot]

azure-local/concepts/software-defined-networking.md

@@ -5,7 +5,7 @@ author: AnirbanPaul
 ms.author: anpaul
 ms.topic: conceptual
 ms.service: azure-local
-ms.date: 04/17/2023
+ms.date: 05/06/2025
 ---
 
 # Software Defined Networking (SDN) in Azure Stack HCI and Windows Server
@@ -21,7 +21,7 @@ Virtual network elements such as [Hyper-V Virtual Switch](/windows-server/virtua
 There are three major SDN components, and you can choose which you want to deploy: Network Controller, Software Load Balancer, and Gateway.
 
    > [!NOTE]
-   > SDN is not supported on stretched (multi-site) clusters.
+   > SDN isn't supported on stretched (multi-site) clusters.
 
 ## Network Controller
 
@@ -45,7 +45,7 @@ You have the option to [deploy SDN Network Controller using SDN Express](../mana
 Gateways are used for routing network traffic between a virtual network and another network, either local or remote. Gateways can be used to:
 
 - Create secure site-to-site IPsec connections between SDN virtual networks and external customer networks over the internet.
-- Create Generic Routing Encapsulation (GRE) connections between SDN virtual networks and external networks. The difference between site-to-site connections and GRE connections is that the latter is not an encrypted connection. For more information about GRE connectivity scenarios, see [GRE Tunneling in Windows Server](/windows-server/remote/remote-access/ras-gateway/gre-tunneling-windows-server).
+- Create Generic Routing Encapsulation (GRE) connections between SDN virtual networks and external networks. The difference between site-to-site connections and GRE connections is that the latter isn't an encrypted connection. For more information about GRE connectivity scenarios, see [GRE Tunneling in Windows Server](/windows-server/remote/remote-access/ras-gateway/gre-tunneling-windows-server).
 - Create Layer 3 connections between SDN virtual networks and external networks. In this case, the SDN gateway simply acts as a router between your virtual network and the external network.
 
 Gateways use [Border Gateway Protocol](/windows-server/remote/remote-access/bgp/border-gateway-protocol-bgp) to advertise GRE endpoints and establish point-to-point connections. SDN deployment creates a default gateway pool that supports all connection types. Within this pool, you can specify how many gateways are reserved on standby in case an active gateway fails.

azure-local/concepts/system-requirements.md

@@ -6,7 +6,7 @@ ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
 ms.custom: references_regions
-ms.date: 04/29/2025
+ms.date: 05/06/2025
 ---
 
 # System requirements for Azure Stack HCI, version 22H2
@@ -112,7 +112,7 @@ For best results, adhere to the following requirements:
 An Azure Stack HCI cluster requires a reliable high-bandwidth, low-latency network connection between each server node.
 
 - Verify at least one network adapter is available and dedicated for cluster management.
-- Verify that physical switches in your network are configured to allow traffic on any VLANs you'll use.
+- Verify that physical switches in your network are configured to allow traffic on any VLANs you use.
 
 For physical networking considerations and requirements, see [Physical network requirements](physical-network-requirements.md).
 
@@ -153,7 +153,7 @@ If you use Windows Admin Center to [create](../deploy/create-cluster.md) or [man
 
 - If you're running Windows Admin Center on a server (instead of a local PC), use an account that's a member of the Gateway Administrators group, or the local Administrators group on the Windows Admin Center server.
 
-- Verify that your Windows Admin Center management computer is joined to the same Active Directory domain in which you'll create the cluster, or joined to a fully trusted domain. The servers that you'll cluster don't need to belong to the domain yet; they can be added to the domain during cluster creation.
+- Verify that your Windows Admin Center management computer is joined to the same Active Directory domain in which you create the cluster, or joined to a fully trusted domain. The servers that you'll cluster don't need to belong to the domain yet; they can be added to the domain during cluster creation.
 
 ## Maximum supported hardware specifications
 

azure-local/deploy/deployment-arc-register-server-permissions.md

@@ -3,7 +3,7 @@ title: Register your Azure Local machines with Azure Arc and assign permissions
 description: Learn how to Register your Azure Local machines with Azure Arc and assign permissions for deployment. 
 author: alkohli
 ms.topic: how-to
-ms.date: 05/05/2025
+ms.date: 05/06/2025
 ms.author: alkohli
 ms.service: azure-local
 ms.custom: devx-track-azurepowershell

azure-local/deploy/deployment-azure-resource-manager-template.md

@@ -3,7 +3,7 @@ title: Azure Resource Manager template deployment for Azure Local, version 23H2
 description: Learn how to prepare and then deploy Azure Local instance, version 23H2 using the Azure Resource Manager template.
 author: alkohli
 ms.topic: how-to
-ms.date: 05/01/2025
+ms.date: 05/06/2025
 ms.author: alkohli
 ms.reviewer: alkohli
 ms.service: azure-local
@@ -58,7 +58,7 @@ A Resource Manager template creates and assigns all the resource permissions req
 With all the prerequisite and preparation steps complete, you're ready to deploy using a known good and tested Resource Manager deployment template and corresponding parameters JSON file. Use the parameters contained in the JSON file to fill out all values, including the values generated previously.
 
 > [!IMPORTANT]
-> In this release, make sure that all the parameters contained in the JSON value are filled out including the ones that have a null value. If there are null values, then those need to be populated or the validation fails.
+> In this release, make sure that all the parameters contained in the JSON value are filled out including the ones that have a null value. If there are null values, then those parameters need to be populated or the validation fails.
 
 1. In the Azure portal, go to **Home** and select **+ Create a resource**.
 

azure-local/manage/maintain-servers.md

@@ -5,7 +5,7 @@ author: alkohli
 ms.author: alkohli
 ms.topic: how-to
 ms.service: azure-local
-ms.date: 04/29/2025
+ms.date: 05/06/2025
 ---
 
 # Failover cluster maintenance procedures
@@ -40,7 +40,7 @@ Before either shutting down or restarting a server, you should pause the server
 
    *Pause server(s) for maintenance: Are you sure you want to pause server(s)? This moves workloads, such as virtual machines, to other servers in the cluster.​*
 
-3. Select **yes** to pause the server and initiate the drain process. The server status shows as **In maintenance, Draining**, and roles such as Hyper-V and VMs will immediately begin live migrating to other server(s) in the cluster. This can take a few minutes. No roles can be added to the server until it's resumed. When the draining process is finished, the server status shows as **In maintenance, Drain completed**. The operating system performs an automatic safety check to ensure it's safe to proceed. If there are unhealthy volumes, it stops and alerts you that it's not safe to proceed.
+3. Select **yes** to pause the server and initiate the drain process. The server status shows as **In maintenance, Draining**, and roles such as Hyper-V and VMs immediately begin live migrating to other server(s) in the cluster. This can take a few minutes. No roles can be added to the server until it resumes. When the draining process is finished, the server status shows as **In maintenance, Drain completed**. The operating system performs an automatic safety check to ensure it's safe to proceed. If there are unhealthy volumes, it stops and alerts you that it's not safe to proceed.
 
 ### Shut down the server
 
@@ -168,7 +168,7 @@ Resume-ClusterNode –Failback Immediate
 
 To do this in Failover Cluster Manager, go to **Nodes**, right-click the node, and then select **Resume** > **Fail Roles Back**.
 
-Once the server has resumed, it shows as **Up** in PowerShell and Failover Cluster Manager.
+Once the server resumes, it shows as **Up** in PowerShell and Failover Cluster Manager.
 
 ### Wait for storage to resync
 

azure-local/manage/witness.md

@@ -3,7 +3,7 @@ title: Set up a cluster witness
 description: Learn how to set up a cluster witness 
 author: alkohli 
 ms.topic: how-to
-ms.date: 04/29/2025
+ms.date: 05/06/2025
 ms.author: alkohli 
 ms.reviewer: stevenek 
 ---
@@ -24,7 +24,7 @@ To learn more about cluster witnesses and quorum, see [Understanding cluster and
 
 ## Before you begin
 
-Before you can create a cloud witness, you must have an Azure account and subscription, and register your Azure Stack HCI cluster with Azure. See the following articles for more information:
+Before you can create a cloud witness, you must have an Azure account and subscription, and register your Azure Stack HCI cluster with Azure. For more information, see the following articles:
 
 - Make sure that port 443 is open in your firewalls and that `*.core.windows.net` is included in any firewall allowlists you're using between the cluster and Azure Storage. For details, see [Required firewall URLs](../concepts/firewall-requirements.md).
 - If your network uses a proxy server for internet access, you must [configure proxy settings for Azure Stack HCI](./configure-proxy-settings.md).