update

Author: tfitzmac

articles/azure-resource-manager/templates/cross-resource-group-deployment.md

@@ -5,18 +5,18 @@ ms.topic: conceptual
 ms.date: 05/18/2020
 ---
 
-# Deploy Azure resources to more than one subscription or resource group
+# Deploy Azure resources across subscriptions or resource groups
 
-Resource Manager enables you to use nested templates to target more than one subscription and resource group.
+Resource Manager enables you to target more than one resource group in a single deployment. You use nested templates to specify resource groups that are different than the resource group in the deployment operation. The resource groups can exist in different subscriptions.
 
 > [!NOTE]
-> You can deploy to 800 resource groups in a single deployment. Typically, this limitation means you can deploy to one resource group specified for the parent template, and up to 799 resource groups in nested or linked deployments. However, if your parent template contains only nested or linked templates and does not itself deploy any resources, then you can include up to 800 resource groups in nested or linked deployments.
+> You can deploy to **800** resource groups in a single deployment. Typically, this limitation means you can deploy to one resource group specified for the parent template, and up to 799 resource groups in nested or linked deployments. However, if your parent template contains only nested or linked templates and does not itself deploy any resources, then you can include up to 800 resource groups in nested or linked deployments.
 
 ## Specify subscription and resource group
 
-To target a resource group that is different than the one for parent template, use a [nested or linked template](linked-templates.md). Within the `Microsoft.Resources/deployments` resource type, specify values for the `subscriptionId` and `resourceGroup` properties.
+To target a resource group that is different than the one for parent template, use a [nested or linked template](linked-templates.md). Within the deployment resource type, specify values for the subscription ID and resource group.
 
-:::code language="json" source="~/resourcemanager-templates/azure-resource-manager/crosssubscription.json" range="38-43" highlight="2,5-6":::
+:::code language="json" source="~/resourcemanager-templates/azure-resource-manager/crosssubscription.json" range="38-43" highlight="5-6":::
 
 If you don't specify the subscription ID or resource group, the subscription and resource group from the parent template are used. All the resource groups must exist before running the deployment.
 

articles/azure-resource-manager/templates/deploy-to-subscription.md

@@ -2,13 +2,16 @@
 title: Deploy resources to subscription
 description: Describes how to create a resource group in an Azure Resource Manager template. It also shows how to deploy resources at the Azure subscription scope.
 ms.topic: conceptual
-ms.date: 05/07/2020
+ms.date: 05/18/2020
 ---
 
 # Create resource groups and resources at the subscription level
 
 To simplify the management of resources in your Azure subscription, you can define and assign [policies](../../governance/policy/overview.md) or [role-based access controls](../../role-based-access-control/overview.md) across the subscription. With subscription level templates, you declaratively apply policies and assign roles at the subscription. You can also create resource groups and deploy resources.
 
+> [!NOTE]
+> You can deploy to up to 800 resource groups in a subscription level deployment.
+
 To deploy templates at the subscription level, use Azure CLI, PowerShell, or REST API. The Azure portal doesn't support deployment in the subscription level.
 
 ## Supported resources

articles/azure-resource-manager/templates/toc.yml

@@ -236,7 +236,7 @@
       href: deploy-to-management-group.md
     - name: Tenant
       href: deploy-to-tenant.md
-    - name: Multiple resource groups or subscriptions
+    - name: Across resource groups
       href: cross-resource-group-deployment.md
   - name: Provide parameters
     items: