Skip to content

Commit 8de983f

Browse files
committed
Fixed blacking issues from PR review
1 parent e4e9c9e commit 8de983f

File tree

3 files changed

+3
-3
lines changed

3 files changed

+3
-3
lines changed

azure-local/manage/gpu-preparation.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
title: Prepare GPUs for Azure Local instance.
2+
title: Prepare GPUs for Azure Local instance
33
description: Learn how to prepare GPUs for an Azure Local instance.
44
author: alkohli
55
ms.author: alkohli

azure-local/manage/vm-activate.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -25,7 +25,7 @@ For more information, see [Compare options](#compare-options).
2525

2626
Next, activate your Windows Server VMs:
2727

28-
- Azure Local supportes Automatic VM Activation (AVMA), a method that binds VM activation to the Azure Local machine and activates the Windows Server VM when it starts up.
28+
- Azure Local supports Automatic VM Activation (AVMA), a method that binds VM activation to the Azure Local machine and activates the Windows Server VM when it starts up.
2929
- If you're using Windows Server subscription, AVMA is automatically enabled on the Azure Local machines. You can immediately activate Windows Server VMs against the system using [generic AVMA client keys](/windows-server/get-started/automatic-vm-activation?tabs=server2025#avma-keys).
3030
- If you're using Azure Hybrid Benefit, you must use the corresponding keys associated with your Windows Server license and apply them using your chosen activation method. One of the most convenient ways is to exchange them to use AVMA by enabling Windows Server subscription.
3131
- To use other methods to activate Windows Server VMs, see [Key Management Services (KMS) activation planning](/windows-server/get-started/kms-activation-planning).

azure-local/oem-license.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -91,7 +91,7 @@ Here are some examples of mixed-mode scenarios that aren't supported:
9191
|Varying operating systems or versions. | Running different operating systems or different versions of the same operating system across the nodes in a cluster isn't supported.|
9292
|Different billing on machines. | Mixing machine hardware sold with an Azure Stack HCI OEM license and machine hardware purchased with a regular Azure subscription isn't supported.|
9393

94-
For support with billing issues related to mixed node scenarios, file an Azure support request through [the Azure Portal](https://portal.azure.com).
94+
For support with billing issues related to mixed node scenarios, file an Azure support request through [the Azure portal](https://portal.azure.com).
9595

9696
## Next step
9797

0 commit comments

Comments
 (0)