Skip to content

Commit 6a80ae4

Browse files
authored
Acrolinx and metadata fix
1 parent 36e8468 commit 6a80ae4

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

azure-local/manage/trusted-launch-automatic-state-transfer.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ This example shows a Trusted launch Arc VM running Windows 11 guest with BitLock
5252
> [!NOTE]
5353
> If vTPM state wasn't preserved during VM migration, VM startup would result in BitLocker recovery during guest boot up. You would be prompted for the BitLocker recovery password when you attempted to sign on to the Windows 11 guest. This situation occurs because the boot measurement (stored in the vTPM) of the migrated VM on the destination node is different from that of the original VM.
5454
55-
1. Force the VM to failover to another machine in the system.
55+
1. Force the VM to fail over to another machine in the system.
5656
5757
1. Confirm the owner node of the VM using the following command.
5858

azure-local/manage/trusted-launch-vm-overview.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
---
22
title: Overview for Trusted launch for Azure Arc VMs on Azure Local
3-
description: Learn about Trusted launch for Azure Arc VMs on Azure Local
3+
description: Learn about Trusted launch for Azure Arc VMs on Azure Local.
44
ms.topic: conceptual
55
author: alkohli
66
ms.author: alkohli

0 commit comments

Comments
 (0)