Merge pull request #278611 from davidsmatlak/ds-arg-alerts-freshness-20240618

ARG alerts docs freshness update

Author: prmerger-automator[bot]

articles/governance/resource-graph/alerts-query-quickstart.md

@@ -1,7 +1,7 @@
 ---
 title: How Azure Resource Graph uses alerts to monitor resources
 description: In this quickstart, you learn how to create monitoring alerts for Azure resources using an Azure Resource Graph query and a Log Analytics workspace.
-ms.date: 05/16/2024
+ms.date: 06/18/2024
 ms.topic: quickstart
 ---
 

articles/governance/resource-graph/overview.md

@@ -1,17 +1,14 @@
 ---
 title: Overview of Azure Resource Graph
 description: Understand how the Azure Resource Graph service enables complex querying of resources at scale across subscriptions and tenants.
-ms.date: 05/08/2024
+ms.date: 06/18/2024
 ms.topic: overview
 ms.custom: devx-track-arm-template
 ---
 
 # What is Azure Resource Graph?
 
-Azure Resource Graph is an Azure service designed to extend Azure Resource Management by
-providing efficient and performant resource exploration with the ability to query at scale across a
-given set of subscriptions so that you can effectively govern your environment. These queries
-provide the following abilities:
+Azure Resource Graph is an Azure service designed to extend Azure Resource Management by providing efficient and performant resource exploration. Resource Graph has the ability to query at scale across a given set of subscriptions so that you can effectively govern your environment. These queries provide the following abilities:
 
 - Query resources with complex filtering, grouping, and sorting by resource properties.
 - Explore resources iteratively based on governance requirements.
@@ -61,7 +58,7 @@ With Azure Resource Graph, you can:
 
 ## How Resource Graph is kept current
 
-When an Azure resource is updated, Azure Resource Manager notifies Azure Resource Graph about the change. Azure Resource Graph then updates its database. Azure Resource Graph also does a regular _full scan_. This scan ensures that Azure Resource Graph data is current if there are missed notifications or when a resource is updated outside of Azure Resource Manager.
+When an Azure resource is updated, Azure Resource Manager notifies Azure Resource Graph about the change. Azure Resource Graph then updates its database. Azure Resource Graph also does a regular _full scan_. This scan ensures that Azure Resource Graph data is current if there are missed notifications. Or when a resource is updated outside of Azure Resource Manager.
 
 > [!NOTE]
 > Resource Graph uses a `GET` to the latest non-preview application programming interface (API) of each resource provider to gather

articles/governance/resource-graph/samples/alerts-samples.md

@@ -1,7 +1,7 @@
 ---
 title: Azure Resource Graph alerts sample queries
 description: Sample queries that can be used to create alerts for your Azure resources using an Azure Resource Graph query and a Log Analytics workspace.
-ms.date: 03/20/2024
+ms.date: 06/18/2024
 ms.topic: sample
 ---
 

articles/governance/resource-graph/troubleshoot/alerts.md

@@ -1,7 +1,7 @@
 ---
 title: Troubleshoot Azure Resource Graph alerts
 description: Learn how to troubleshoot issues with Azure Resource Graph alerts integration with Log Analytics.
-ms.date: 11/07/2023
+ms.date: 06/18/2024
 ms.topic: troubleshooting
 ---
 
@@ -46,7 +46,7 @@ Azure Resource Graph has pagination in its dedicated APIs. But with the way Log
 
 The managed identity for your alert must have the role [Log Analytics Contributor](../../../role-based-access-control/built-in-roles.md#log-analytics-contributor) or [Log Analytics Reader](../../../role-based-access-control/built-in-roles.md#log-analytics-reader). The role provides the permissions to get monitoring information.
 
-When you set up an alert, the results can be different than the result after the alert is fired. The reason is that a fired alert is run using a managed identity, but when you manually test an alert it uses the user's identity.
+When you set up an alert, the results can be different than the result after the alert is fired. The reason is that a fired alert is run using a managed identity. But when you manually test an alert, it uses the user's identity.
 
 ## Table names