Skip to content

Commit a891708

Browse files
committed
minor edits
1 parent d334a73 commit a891708

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/update-manager/guidance-migration-azure.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -38,7 +38,7 @@ Specifically for update management or patching, as per your requirements, you ca
3838

3939
> [!NOTE]
4040
> - To manage clients/devices, Intune is the recommended Microsoft solution.
41-
> - Azure Update Manager does not provide migration support for Azure VMs in MCM. For example, configurations.
41+
> - Azure Update Manager doesn't provide migration support for Azure VMs in MCM. For example, configurations.
4242
4343
## Software update management capability map
4444

@@ -60,7 +60,7 @@ As a first step in MCM user's journey towards Azure Update Manager, you need to
6060
> - Azure Update Manager doesn't support client ordevices.
6161
> - This article helps you start using Azure Update Manager to manage software updates or patches to servers currently managed by MCM.
6262
> - Azure Update Manager and MCM co-existence means that once Azure Update Manager is enabled, MCM should only be used for capabilities other than software updates management.
63-
> - Azure Update Manager and MCM should not be used simultaneously to manage software updates or patches to same set of servers.
63+
> - Azure Update Manager and MCM shouldn't be used simultaneously to manage software updates or patches to same set of servers.
6464
6565
### Prerequisites for Azure Update Manager and MCM co-existence
6666

0 commit comments

Comments
 (0)