Streamlining common schema docs

Author: AbbyMSFT

articles/azure-monitor/alerts/alerts-common-schema.md

@@ -8,21 +8,19 @@ ms.reviewer: ofmanor
 
 # Common alert schema
 
-This article describes what the common alert schema is, the benefits of using it, and how to enable it.
+The common alert schema standardizes the consumption experience for alert notifications in Azure. Historically, activity log, metric, and log alerts each had their own email templates and webhook schemas. The common alert schema provides one standardized consistent consistent schema for all alert notifications. 
 
-## What is the common alert schema?
+A standardized schema can help you minimize the number of integrations, which makes the process of managing and maintaining them a much simpler task. Future alert payload enrichments like customization and diagnostic enrichment will only surface in the common schema.
 
-The common alert schema standardizes the consumption experience for alert notifications in Azure. Today, Azure has three alert types, metric, log, and activity log. Historically, they've had their own email templates and webhook schemas. With the common alert schema, you can now receive alert notifications with a consistent schema.
+The new schema also enables a richer alert consumption experience across both the Azure portal and the Azure mobile app.
 
-Any alert instance describes the resource that was affected and the cause of the alert. These instances are described in the common schema in the following sections:
+> [!NOTE]
+> Alerts generated by [VM insights](../vm/vminsights-overview.md) currently don't support the common schema.
 
-- **Essentials**: Standardized fields, common across all alert types, describe what resource the alert is on along with other common alert metadata. Examples include severity or description.
+All alert instances include information about the affected resource and the cause of the alert in these sections:
+- **Essentials**: Standardized fields, common across all alert types, describe what resource the alert is on along with other common alert metadata. Examples include severity or description. For example, if you want to route alert instances to specific teams based on criteria such as a resource group, you can use the essential fields to provide standardized routing logic for all alert types. The field teams can then use the context fields for their investigation.
 - **Alert context**: These fields describe the cause of the alert, with fields that vary based on the alert type. For example, a metric alert would have fields like the metric name and metric value in the alert context. An activity log alert would have information about the event that generated the alert.
 
-You might want to route the alert instance to a specific team based on a pivot such as a resource group. The common schema uses the essential fields to provide standardized routing logic for all alert types. The team can use the context fields for their investigation.
-
-As a result, you can potentially have fewer integrations, which makes the process of managing and maintaining them a much simpler task. Future alert payload enrichments like customization and diagnostic enrichment will only surface in the common schema.
-
 ## What enhancements does the common alert schema bring?
 
 You'll see the benefits of using a common alert schema in your alert notifications. A common alert schema provides these benefits:
@@ -32,11 +30,11 @@ You'll see the benefits of using a common alert schema in your alert notificatio
 | Email | A consistent and detailed email template. You can use it to easily diagnose issues at a glance. Embedded deep links to the alert instance on the portal and the affected resource ensure that you can quickly jump into the remediation process. |
 | Webhook/Azure Logic Apps/Azure Functions/Azure Automation runbook | A consistent JSON structure for all alert types. You can use it to easily build integrations across the different alert types. |
 
-The new schema will also enable a richer alert consumption experience across both the Azure portal and the Azure mobile app in the immediate future.
+
 
 Learn more about the [schema definitions for webhooks, Logic Apps, Azure Functions, and Automation runbooks](./alerts-common-schema-definitions.md).
 
-> [!NOTE]
+
 > The following actions don't support the common alert schema ITSM Connector.
 
 ## How do I enable the common alert schema?
@@ -46,7 +44,7 @@ Use action groups in the Azure portal or use the REST API to enable the common a
 > [!NOTE]
 > Smart detection alerts support the common schema by default. No opt-in is required.
 >
-> Alerts generated by [VM insights](../vm/vminsights-overview.md) currently don't support the common schema.
+> 
 >
 
 ### Through the Azure portal