updates2

Author: LiSeda

articles/azure-resource-manager/bicep/deploy-to-resource-group.md

@@ -76,7 +76,7 @@ You can deploy a resource from within a resource-group-scope Bicep file at the f
 - [The subscription](#scope-to-subscription)
 - [The tenant](#scope-to-tenant)
 
-### Scope to the target resource group
+### Scope to target resource group
 
 To deploy resources to the target resource group, add those resources to the Bicep file.
 
@@ -89,7 +89,7 @@ resource exampleResource 'Microsoft.Storage/storageAccounts@2023-04-01' = {
 
 For an example template, see [Deploy to target resource group](#deploy-to-target-resource-group).
 
-### Scope to a different resource group
+### Scope to different resource group
 
 To deploy resources to a resource group that isn't the target resource group, add a [module](modules.md). Use the [`resourceGroup` function](bicep-functions-scope.md#resourcegroup) to set the `scope` property for that module.
 

articles/azure-resource-manager/bicep/deployment-script-bicep.md

@@ -24,7 +24,7 @@ The benefits of deployment scripts include:
 - You can allow passing command-line arguments to the script.
 - You can specify script outputs and pass them back to the deployment.
 
-The deployment script resource is available only in the regions where Azure Container Instances is available. For more information, see [Resource availability & quota limits for ACI](/azure/container-instances/container-instances-resource-and-quota-limits) and [Products available by region](https://azure.microsoft.com/en-us/explore/global-infrastructure/products-by-region/).
+The deployment script resource is available only in the regions where Azure Container Instances is available. For more information, see [Resource availability & quota limits for ACI](/azure/container-instances/container-instances-resource-and-quota-limits) and [Products available by region](https://azure.microsoft.com/explore/global-infrastructure/products-by-region/).
 
 > [!WARNING]
 > The deployment script service requires two extra resources to run and troubleshoot scripts: a storage account and a container instance. Generally, the service cleans up these resources after the deployment script finishes. You incur charges for these resources until they're removed.