freshness updates

Author: davidsmatlak

articles/governance/resource-graph/reference/keyboard-shortcuts.md

@@ -1,16 +1,14 @@
 ---
 title: Keyboard shortcuts in the Azure portal for Azure Resource Graph Explorer
 description: Azure Resource Graph Explorer in the Azure portal supports keyboard shortcuts to help you perform actions and navigate.
-ms.date: 08/17/2021
+ms.date: 07/11/2024
 ms.topic: reference
 ms.custom: accessibility
 ---
+
 # Keyboard shortcuts for Azure Resource Graph Explorer
 
-This article lists the keyboard shortcuts that work in the Azure Resource Graph Explorer page of the
-Azure portal. For a list of global keyboard shortcuts or a list of keyboard shortcuts available for
-other pages, visit
-[Keyboard shortcuts in the Azure portal](../../../azure-portal/azure-portal-keyboard-shortcuts.md).
+This article lists the keyboard shortcuts that work in the Azure Resource Graph Explorer page of the Azure portal. For a list of global keyboard shortcuts or a list of keyboard shortcuts available for other pages, visit [Keyboard shortcuts in the Azure portal](../../../azure-portal/azure-portal-keyboard-shortcuts.md).
 
 ## Keyboard shortcuts for editing queries
 
@@ -62,4 +60,4 @@ other pages, visit
 ## Next steps
 
 - [Keyboard shortcuts in the Azure portal](../../../azure-portal/azure-portal-keyboard-shortcuts.md)
-- [Query language for Resource Graph](../concepts/query-language.md)
+- [Understanding the Azure Resource Graph query language](../concepts/query-language.md)

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

@@ -1,20 +1,17 @@
 ---
-title: Troubleshoot common errors
+title: Troubleshoot common errors for Azure Resource Graph
 description: Learn how to troubleshoot issues with the various SDKs while querying Azure resources with Azure Resource Graph.
-ms.date: 08/17/2021
+ms.date: 07/11/2024
 ms.topic: troubleshooting
 ---
 
 # Troubleshoot errors using Azure Resource Graph
 
-You may run into errors when querying Azure resources with Azure Resource Graph. This article
-describes various errors that may occur and how to resolve them.
+You might run into errors when querying Azure resources with Azure Resource Graph. This article describes various errors that might occur and how to resolve them.
 
 ## Finding error details
 
-Most errors are the result of an issue while running a query with Azure Resource Graph. When a query
-fails, the SDK provides details about the failed query. This information indicates the issue so that
-it can be fixed and a later query succeeds.
+Most errors are the result of an issue while running a query with Azure Resource Graph. When a query fails, the SDK provides details about the failed query. This information indicates the issue so that it can be fixed and a later query succeeds.
 
 ## General errors
 
@@ -26,10 +23,7 @@ Customers making large or frequent resource queries have requests throttled.
 
 #### Cause
 
-Azure Resource Graph allocates a quota number for each user based on a time window. For example, a
-user can send at most 15 queries within every 5-second window without being throttled. The quota
-value is determined by many factors and is subject to change. For more information, see
-[Throttling in Azure Resource Graph](../overview.md#throttling).
+Azure Resource Graph allocates a quota number for each user based on a time window. For example, a user can send at most 15 queries within every 5-second window without being throttled. The quota value is determined by many factors and is subject to change. For more information, see [Throttling in Azure Resource Graph](../overview.md#throttling).
 
 #### Resolution
 
@@ -44,19 +38,15 @@ There are several methods of dealing with throttled requests:
 
 #### Issue
 
-Customers with access to more than 1,000 subscriptions, including cross-tenant subscriptions with
-[Azure Lighthouse](../../../lighthouse/overview.md), can't fetch data across all subscriptions in a
-single call to Azure Resource Graph.
+Customers with access to more than 1,000 subscriptions, including cross-tenant subscriptions with [Azure Lighthouse](../../../lighthouse/overview.md), can't fetch data across all subscriptions in a single call to Azure Resource Graph.
 
 #### Cause
 
-Azure CLI and PowerShell forward only the first 1,000 subscriptions to Azure Resource Graph. The
-REST API for Azure Resource Graph accepts a maximum number of subscriptions to perform the query on.
+Azure CLI and PowerShell forward only the first 1,000 subscriptions to Azure Resource Graph. The REST API for Azure Resource Graph accepts a maximum number of subscriptions to perform the query on.
 
 #### Resolution
 
-Batch requests for the query with a subset of subscriptions to stay under the 1,000 subscription
-limit. The solution is using the **Subscription** parameter in PowerShell.
+Batch requests for the query with a subset of subscriptions to stay under the 1,000 subscription limit. The solution is using the **Subscription** parameter in PowerShell.
 
 ```azurepowershell-interactive
 # Replace this query with your own
@@ -85,46 +75,34 @@ $response
 
 #### Issue
 
-Customers querying the Azure Resource Graph REST API get a _500_ (Internal Server Error) response
-returned.
+Customers querying the Azure Resource Graph REST API get a _500_ (Internal Server Error) response returned.
 
 #### Cause
 
-The Azure Resource Graph REST API only supports a `Content-Type` of **application/json**. Some REST
-tools or agents default to **text/plain**, which is unsupported by the REST API.
+The Azure Resource Graph REST API only supports a `Content-Type` of `application/json`. Some REST tools or agents default to `text/plain`, which is unsupported by the REST API.
 
 #### Resolution
 
-Validate that the tool or agent you're using to query Azure Resource Graph has the REST API header
-`Content-Type` configured for **application/json**.
+Validate that the tool or agent you're using to query Azure Resource Graph has the REST API header `Content-Type` configured for `application/json`.
 
 ### Scenario: No read permission to all subscriptions in list
 
 #### Issue
 
-Customers that explicitly pass a list of subscriptions with an Azure Resource Graph query get a
-_403_ (Forbidden) response.
+Customers that explicitly pass a list of subscriptions with an Azure Resource Graph query get a _403_ (Forbidden) response.
 
 #### Cause
 
-If the customer doesn't have read permission to all the provided subscriptions, the request is
-denied because of lack of appropriate security rights.
+If the customer doesn't have read permission to all the provided subscriptions, the request is denied because of lack of appropriate security rights.
 
 #### Resolution
 
-Include at least one subscription in the subscription list that the customer running the query has
-at least read access to. For more information, see
-[Permissions in Azure Resource Graph](../overview.md#permissions-in-azure-resource-graph).
+Include at least one subscription in the subscription list that the customer running the query has at least read access to. For more information, see [Permissions in Azure Resource Graph](../overview.md#permissions-in-azure-resource-graph).
 
 ## Next steps
 
-If you didn't see your problem or are unable to solve your issue, visit one of the following
-channels for more support:
+If you didn't see your problem or are unable to solve your issue, visit one of the following channels for more support:
 
-- Get answers from Azure experts through
-  [Azure Forums](https://azure.microsoft.com/support/forums/).
-- Connect with [@AzureSupport](https://twitter.com/azuresupport) - the official Microsoft Azure
-  account for improving customer experience by connecting the Azure community to the right
-  resources: answers, support, and experts.
-- If you need more help, you can file an Azure support incident. Go to the
-  [Azure support site](https://azure.microsoft.com/support/options/) and select **Get Support**.
+- Get answers from Azure experts through [Azure Forums](https://azure.microsoft.com/support/forums/).
+- Connect with [@AzureSupport](https://twitter.com/azuresupport) - the official Microsoft Azure account for improving customer experience by connecting the Azure community to the right resources: answers, support, and experts.
+- If you need more help, you can file an Azure support incident. Go to the [Azure support site](https://azure.microsoft.com/support/options/) and select **Get Support**.