updates based on PR review comments

Author: guywi-ms

articles/azure-monitor/alerts/log-alert-rule-health.md

@@ -69,7 +69,7 @@ This table describes the possible resource health status values for a log search
 |NSP validation failed |The query is failing because of NSP validations issues.| Review your network security perimeter rules to ensure your alert rule is correctly configured.|
 |Active alerts limit exceeded |Alert evaluation failed due to exceeding the limit of fired (non- resolved) alerts per day.     |See [Azure Monitor service limits](../service-limits.md).   |
 |Dimension combinations limit exceeded | Alert evaluation failed due to exceeding the allowed limit of dimension combinations values meeting the threshold.|See [Azure Monitor service limits](../service-limits.md).     |
-|Unavailable for unknown reason | Today, the report health status is supported only for rules with a frequency of 15 minutes or lower.| For using Resource Health the fequency should be 5 minutes or lower. |
+|Unavailable for unknown reason | Today, the report health status is supported only for rules with a frequency of 15 minutes or lower.| For using Resource Health, the frequency should be 5 minutes or lower. |
 
 
 ## Add a new resource health alert

articles/azure-monitor/cost-meters.md

@@ -33,7 +33,7 @@ The following table lists the meters used to bill for data ingestion in your Log
 | Standalone (legacy tier)  | Log Analytics | Pay-as-you-go Data Analyzed | no | 
 | Standard (legacy tier)  | Log Analytics | Standard Data Analyzed | no |
 | Premium (legacy tier)  | Log Analytics | Premium Data Analyzed | no |
-| (any) | Azure Monitor | Free Benefit - M365 Defender Data Ingestion | yes |
+| (any) | Azure Monitor | Free Benefit - Microsoft 365 Defender Data Ingestion | yes |
 
 
 The **Standard Data Included per Node** meter is used both for the Log Analytics [Per Node tier](logs/cost-logs.md#per-node-pricing-tier) data allowance, and also the [Defender for Servers data allowance](logs/cost-logs.md#workspaces-with-microsoft-defender-for-cloud), for workspaces in any pricing tier. 

articles/azure-monitor/includes/waf-containers-cost.md

@@ -23,7 +23,7 @@ ms.date: 03/30/2023
 
 | Recommendation | Benefit |
 |:---|:---|
-| Enable collection of metrics through the Azure Monitor managed service for Prometheus. Be sure you do not enable to also send Prometheus metrics to Log Analytics Workspace.  | You can use [Azure Monitor managed service for Prometheus](https://aka.ms/managedpromdocumentation) for scraping Prometheus metrics from your cluster by [enabling Managed Prometheus](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana). Note that you can configure Container insights to [collect Prometheus metrics in your Log Analytics workspace](../containers/container-insights-prometheus-logs.md), however this is not recommended as this is redundant with the data in Managed Prometheus and will result in additional cost. For details, see [Managed Prometheus pricing](https://azure.microsoft.com/pricing/details/monitor/). |
+| Enable collection of metrics through the Azure Monitor managed service for Prometheus. Be sure you do not also send Prometheus metrics to a Log Analytics Workspace.  | You can use [Azure Monitor managed service for Prometheus](https://aka.ms/managedpromdocumentation) for scraping Prometheus metrics from your cluster by [enabling Managed Prometheus](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana). Note that you can configure Container insights to [collect Prometheus metrics in your Log Analytics workspace](../containers/container-insights-prometheus-logs.md), however this is not recommended as this is redundant with the data in Managed Prometheus and will result in additional cost. For details, see [Managed Prometheus pricing](https://azure.microsoft.com/pricing/details/monitor/). |
 | Configure agent to modify data collection in Container insights. |  Analyze the data collected by Container insights as described in [Controlling ingestion to reduce cost](../containers/container-insights-cost.md#control-ingestion-to-reduce-cost) and adjust your configuration to stop collection of data you don't need. |
 | Modify settings for collection of metric data by Container insights. | See [Enable cost optimization settings](../containers/container-insights-cost-config.md) for details on modifying both the frequency that metric data is collected and the namespaces that are collected by  Container insights. |
 | Disable Container insights collection of metric data if you don't use the Container insights experience in the Azure portal. | Container insights collects many of the same metric values as [Managed Prometheus](../containers/kubernetes-monitoring-enable.md#enable-prometheus-and-grafana). You can disable collection of these metrics by configuring Container insights to only collect **Logs and events** as described in [Enable cost optimization settings in Container insights](../containers/container-insights-cost-config.md#enable-cost-settings). This configuration disables the Container insights experience in the Azure portal, but you can use Grafana to visualize Prometheus metrics and Log Analytics to analyze log data collected by Container insights. |

articles/azure-monitor/logs/create-custom-table-auxiliary.md

@@ -5,6 +5,7 @@ author: guywi-ms
 ms.author: guywild
 ms.reviewer: adi.biran
 ms.service: azure-monitor
+ms.custom: references_regions
 ms.topic: how-to 
 ms.date: 07/21/2024
 # Customer intent: As a Log Analytics workspace administrator, I want to create a custom table with the Auxiliary table plan, so that I can ingest and retain data at a low cost for auditing and compliance.

articles/azure-monitor/logs/data-retention-configure.md

@@ -3,7 +3,7 @@ title: Manage data retention in a Log Analytics workspace
 description: Configure retention settings for a table in a Log Analytics workspace in Azure Monitor.
 ms.reviewer: adi.biran
 ms.topic: conceptual
-ms.date: 7/01/2024
+ms.date: 7/22/2024
 # Customer intent: As an Azure account administrator, I want to manage data retention for each table in my Log Analytics workspace based on my account's data usage and retention needs.
 ---
 
@@ -150,7 +150,7 @@ Set-AzOperationalInsightsWorkspace -ResourceGroupName "myResourceGroup" -Name "M
 
 ## Configure table-level retention
 
-By default, all tables with the Analytics data plan inherit the [Log Analytics workspace's default interactive retention setting](#configure-the-default-interactive-retention-period-of-analytics-tables) and have no long-term retention. You can increase the interactive retention period of Anlytics tables to up to 730 days at an [extra cost](https://azure.microsoft.com/pricing/details/monitor/). 
+By default, all tables with the Analytics data plan inherit the [Log Analytics workspace's default interactive retention setting](#configure-the-default-interactive-retention-period-of-analytics-tables) and have no long-term retention. You can increase the interactive retention period of Analytics tables to up to 730 days at an [extra cost](https://azure.microsoft.com/pricing/details/monitor/). 
 
 To add long-term retention to a table with any data plan, set **total retention** to up to 12 years (4,383 days). The Auxiliary table plan is currently in public preview, during which the plan's total retention is fixed at 365 days.
 

articles/azure-monitor/logs/log-analytics-workspace-overview.md

@@ -64,7 +64,7 @@ For example, you might have [diagnostic settings](../essentials/diagnostic-setti
 
 ## Cost
 
-There's no direct cost for creating or maintaining a workspace. You're charged for the data you ingest into the workspace and for data retention, based on the each table's [table plan](data-platform-logs.md#table-plans).
+There's no direct cost for creating or maintaining a workspace. You're charged for the data you ingest into the workspace and for data retention, based on each table's [table plan](data-platform-logs.md#table-plans).
 
 For information on pricing, see [Azure Monitor pricing](https://azure.microsoft.com/pricing/details/monitor/). For guidance on how to reduce your costs, see [Azure Monitor best practices - Cost management](../best-practices-cost.md). If you're using your Log Analytics workspace with services other than Azure Monitor, see the documentation for those services for pricing information.
 

articles/azure-monitor/logs/media/data-retention-configure/interactive-auxiliary-retention-log-analytics-workspace.png

@@ -2,7 +2,7 @@
 title: Run search jobs in Azure Monitor
 description: Search jobs are asynchronous log queries in Azure Monitor that make results available as a table for further analytics.
 ms.topic: conceptual
-ms.date: 05/30/2024
+ms.date: 07/22/2024
 ms.custom: references_regions
 author: guywi-ms
 ms.author: guywild
@@ -24,7 +24,7 @@ Search jobs are asynchronous queries that fetch records into a new search table
 
 Use a search job when the log query timeout of 10 minutes isn't sufficient to search through large volumes of data or if you're running a slow query.
 
-Search jobs also let you retrieve records from [long-term retention](data-retention-configure.md) and [tables with the Basic and Auxiliary plans](data-platform-logs.md#table-plans) into a new Analaytics table where you can take advantage of Azure Monitor Log's full analytics capabilities. In this way, running a search job can be an alternative to:
+Search jobs also let you retrieve records from [long-term retention](data-retention-configure.md) and [tables with the Basic and Auxiliary plans](data-platform-logs.md#table-plans) into a new Analytics table where you can take advantage of Azure Monitor Log's full analytics capabilities. In this way, running a search job can be an alternative to:
 
 - [Restoring data from long-term retention](restore.md) for a specific time range.