Merge pull request #73400 from watfordgnf/patch-2

Update automation-solution-vm-management-config.md

Author: ktoliver

articles/automation/automation-solution-vm-management-config.md

@@ -52,7 +52,7 @@ You can enable either targeting the action against a subscription and resource g
     > [!NOTE]
     > The value for **Target ResourceGroup Names** is stored as the values for both `External_Start_ResourceGroupNames` and `External_Stop_ResourceGroupNames`. For further granularity, you can modify each of these variables to target different resource groups. For start action, use `External_Start_ResourceGroupNames`, and use `External_Stop_ResourceGroupNames` for stop action. VMs are automatically added to the start and stop schedules.
 
-## <a name="tags"></a>Scenario 2: Start/Stop VMS in sequence by using tags
+## <a name="tags"></a>Scenario 2: Start/Stop VMs in sequence by using tags
 
 In an environment that includes two or more components on multiple VMs supporting a distributed workload, supporting the sequence in which components are started and stopped in order is important.