minor edits

Author: AbbyMSFT

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

@@ -24,13 +24,14 @@ The new schema enables a richer alert consumption experience across both the Azu
 > [!NOTE]
 > Alerts generated by [VM insights](../vm/vminsights-overview.md) do not support the common schema.
 
+## Structure of the common schema 
+
 The common schema includes information about the affected resource and the cause of the alert in these sections:
 - **Essentials**: Standardized fields, used by all alert types that describe the resource affected by the alert and common alert metadata, such as severity or description.
 
     If you want to route alert instances to specific teams based on criteria such as a resource group, you can use the fields in the **Essentials** section to provide routing logic for all alert types. The teams that receive the alert notification can then use the context fields for their investigation.
 - **Alert context**: Fields that vary depending on the type of the alert. The alert context fields describe the cause of the alert. 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.
 
-
 ## Sample alert payload
 
 ```json
@@ -84,7 +85,7 @@ The common schema includes information about the affected resource and the cause
 }
 ```
 
-## Essentials
+## Essentials fields
 
 | Field | Description|
 |:---|:---|
@@ -104,7 +105,7 @@ The common schema includes information about the affected resource and the cause
 |alertContextVersion | The version number for the `alertContext` section. |
 
 
-## Alert context for metric alerts
+## Alert context fields for metric alerts
 
 ### Sample metric alert with a static threshold and the monitoringService = `Platform`
 
@@ -198,7 +199,7 @@ The common schema includes information about the affected resource and the cause
 }
 ```
 
-## Alert context for Log alerts
+## Alert context fields for Log alerts
 
 > [!NOTE]
 > When you enable the common schema, the fields in the payload are reset to the common schema fields. Therefore, log alerts have these limitations regarding the common schema:
@@ -397,7 +398,7 @@ The common schema includes information about the affected resource and the cause
 }
 ```
 
-## Alert context for activity log alerts
+## Alert context fields for activity log alerts
 
 ### Sample activity log alert when the monitoringService = Activity Log - Administrative
 
@@ -589,7 +590,9 @@ The common schema includes information about the affected resource and the cause
 }
 ```
 
-## Alert context for Prometheus alerts
+## Alert context fields for Prometheus alerts
+
+### Sample Prometheus alert
 
 ```json
 {