Addressing comments

Author: sunasing

articles/azure-monitor/containers/prometheus-metrics-troubleshoot.md

@@ -182,11 +182,9 @@ Refer to [service quotas and limits](../service-limits.md#prometheus-metrics) fo
 
 ## Creation of Azure Monitor Workspace failed due to Azure Policy evaluation
 
-If creation of Azure Monitor Workspace fails with an error saying "*Resource 'resourcename' was disallowed by policy*", there might an Azure policy that enforces a name for your Azure resources or resource groups.
+If creation of Azure Monitor Workspace fails with an error saying "*Resource 'resource-name-xyz' was disallowed by policy*", there might an Azure policy that is preventing the resource to be created. If there is a policy that enforces a naming convention for your Azure resources or resource groups, you will need to create an exemption for the naming convention for creation of an Azure Monitor Workspace.
 
-When you create an Azure Monitor workspace, by default a data collection rule and a data collection endpoint in the form "*azure-monitor-workspace-name*" will automatically be created in a resource group in the form "*MA_azure-monitor-workspace-name_location_managed*". Currently there is no way to change the names of these resources.
-
-You can set an exemption on the Azure Policy to exempt the above resources from policy evaluation. See [Azure Policy exemption structure](../../governance/policy/concepts/exemption-structure.md).
+When you create an Azure Monitor workspace, by default a data collection rule and a data collection endpoint in the form "*azure-monitor-workspace-name*" will automatically be created in a resource group in the form "*MA_azure-monitor-workspace-name_location_managed*". Currently there is no way to change the names of these resources, and you will need to set an exemption on the Azure Policy to exempt the above resources from policy evaluation. See [Azure Policy exemption structure](../../governance/policy/concepts/exemption-structure.md).
 
 ## Next steps