ARM deployment history auto grooming at tenant and the mg scope.

Author: mumian

articles/azure-resource-manager/templates/deployment-history-deletions.md

@@ -58,9 +58,9 @@ If the current user doesn't have the required permissions, automatic deletion is
 
 You can opt out of automatic deletions from the history. **Use this option only when you want to manage the deployment history yourself.** The limit of 800 deployments in the history is still enforced. If you exceed 800 deployments, you'll receive an error and your deployment will fail.
 
-To disable automatic deletions at the tenant or management group level, open a support ticket with the deployment resource provider (RP) team.
+To disable automatic deletions at the tenant or the management group scope, open a support ticket with the deployment resource provider (RP) team.
 
-To disable automatic deletions at the subscription level, register the `Microsoft.Resources/DisableDeploymentGrooming` feature flag. When you register the feature flag, you opt out of automatic deletions for the entire Azure subscription. You can't opt out for only a particular resource group. To reenable automatic deletions, unregister the feature flag.
+To disable automatic deletions at the subscription scope, register the `Microsoft.Resources/DisableDeploymentGrooming` feature flag. When you register the feature flag, you opt out of automatic deletions for the entire Azure subscription. You can't opt out for only a particular resource group. To reenable automatic deletions, unregister the feature flag.
 
 # [PowerShell](#tab/azure-powershell)