updated event handler articles

Author: spelluru

articles/event-grid/event-handlers.md

@@ -11,19 +11,17 @@ ms.author: spelluru
 ---
 
 # Event handlers in Azure Event Grid
+An event handler is the place where the event is sent. The handler takes some further action to process the event. Several Azure services are automatically configured to handle events. You can also use any webhook for handling events. The webhook doesn't need to be hosted in Azure to handle events. Event Grid only supports HTTPS webhook endpoints.
 
-An event handler is the place where the event is sent. The handler takes some further action to process the event. Several Azure services are automatically configured to handle events. You can also use any WebHook for handling events. The WebHook doesn't need to be hosted in Azure to handle events. Event Grid only supports HTTPS WebHook endpoints.
-
+## Supported event handlers
 Here are the supported event handlers: 
 
-- [WebHooks](handler-webhooks.md). Azure Automation runbooks and Logic Apps are supported via webhooks. 
+- [Webhooks](handler-webhooks.md). Azure Automation runbooks and Logic Apps are supported via webhooks. 
 - [Azure functions](handler-functions.md)
 - [Event hubs](handler-event-hubs.md)
 - [Relay hybrid connections](handler-relay-hybrid-connections.md)
 - [Service Bus queues and topics](handler-service-bus.md)
 - [Storage queues](handler-storage-queues.md)
 
 ## Next steps
-
-* For an introduction to Event Grid, see [About Event Grid](overview.md).
-* To quickly get started using Event Grid, see [Create and route custom events with Azure Event Grid](custom-event-quickstart.md).
+- For an introduction to Event Grid, see [About Event Grid](overview.md).

articles/event-grid/handler-event-hubs.md

@@ -10,30 +10,31 @@ ms.date: 05/11/2020
 ms.author: spelluru
 ---
 
-# Event hub as an event handler for Event Grid events
+# Event hub as an event handler for Azure Event Grid events
 An event handler is the place where the event is sent. The handler takes an action to process the event. Several Azure services are automatically configured to handle events and **Azure Event Hubs** is one of them. 
 
-Use **Event Hubs** when your solution gets events faster than it can process the events. Then, your application can process events from Event Hubs at its own schedule. You can scale your event processing to handle the incoming events.
+Use **Event Hubs** when your solution gets events from Event Grid faster than it can process the events. Once the events are in an event hub, your application can process events from the event hub at its own schedule. You can scale your event processing to handle the incoming events.
 
 ## Examples
+See the following examples: 
 
 |Title  |Description  |
 |---------|---------|
-| [Quickstart: route custom events to Azure Event Hubs with Azure CLI and Event Grid](custom-event-to-eventhub.md) | Sends a custom event to an event hub for processing by an application. |
-| [Resource Manager template: custom topic and Event Hubs endpoint](https://github.com/Azure/azure-quickstart-templates/tree/master/101-event-grid-event-hubs-handler)| A Resource Manager template that creates a subscription for a custom topic. It sends events to an Azure Event Hubs. |
+| [Quickstart: Route custom events to Azure Event Hubs with Azure CLI](custom-event-to-eventhub.md) | Sends a custom event to an event hub for processing by an application. |
+| [Resource Manager template: Create an Event Grid custom topic and send events to an event hub](https://github.com/Azure/azure-quickstart-templates/tree/master/101-event-grid-event-hubs-handler)| A Resource Manager template that creates a subscription for a custom topic. It sends events to an Azure Event Hubs. |
 
 ## Message properties
-Set the following message headers when sending events as messages to an **event hub**.
+If you use an **event hub** as an event handler for events from Event Grid, set the following message headers: 
 
 | Property name | Description |
 | ------------- | ----------- | 
 | aeg-subscription-name | Name of event subscription. |
-| aeg-delivery-count | Number of attempts made for the event. Example: "1" |
-| aeg-event-type | Event type. Example: "Microsoft.Storage.blobCreated" | 
-| aeg-metadata-version | Metadata version of the event. Example: "1". For **Event Grid event schema**, this property represents the metadata version and for **cloud event schema**, it represents the **spec version**. |
-| aeg-data-version | Data version of the event. Example: "1". Default value: "". For **Event Grid event schema**, this property represents the data version and for **cloud event schema**, it doesn't apply. |
+| aeg-delivery-count | <p>Number of attempts made for the event.</p> <p>Example: "1"</p> |
+| aeg-event-type | <p>Type of the event.</p><p> Example: "Microsoft.Storage.blobCreated"</p> | 
+| aeg-metadata-version | <p>Metadata version of the event.</p> <p>Example: "1".</p><p> For **Event Grid event schema**, this property represents the metadata version and for **cloud event schema**, it represents the **spec version**. </p>|
+| aeg-data-version | <p>Data version of the event.</p><p>Example: "1".</p><p>For **Event Grid event schema**, this property represents the data version and for **cloud event schema**, it doesn't apply.</p> |
 | aeg-output-event-id | ID of the Event Grid event. |
 
 
 ## Next steps
-For an introduction to Event Grid, see [About Event Grid](overview.md).
+See the [Event handlers](event-handlers.md) article for a list of supported event handlers. 

articles/event-grid/handler-functions.md

@@ -14,7 +14,7 @@ ms.author: spelluru
 
 An event handler is the place where the event is sent. The handler takes an action to process the event. Several Azure services are automatically configured to handle events and **Azure Functions** is one of them. 
 
-Use **Azure Functions** for serverless response to events. When using an Azure function as the handler, use the Event Grid trigger instead of generic HTTP triggers. Event Grid automatically validates Event Grid Function triggers. With generic HTTP triggers, you must implement the [validation response](webhook-event-delivery.md).
+Use **Azure Functions** in a serverless architecture to respond to events from Event Grid. When using an Azure function as the handler, use the Event Grid trigger instead of the generic HTTP trigger. Event Grid automatically validates Event Grid triggers. With generic HTTP triggers, you must implement the [validation response](webhook-event-delivery.md) yourself.
 
 For more information, see [Event Grid trigger for Azure Functions](../azure-functions/functions-bindings-event-grid.md) for an overview of using the Event Grid trigger in functions.
 
@@ -25,8 +25,8 @@ For more information, see [Event Grid trigger for Azure Functions](../azure-func
 | [Quickstart: Handle events with function](custom-event-to-function.md) | Sends a custom event to a function for processing. |
 | [Tutorial: automate resizing uploaded images using Event Grid](resize-images-on-storage-blob-upload-event.md) | Users upload images through web app to storage account. When a storage blob is created, Event Grid sends an event to the function app, which resizes the uploaded image. |
 | [Tutorial: stream big data into a data warehouse](event-grid-event-hubs-integration.md) | When Event Hubs creates a Capture file, Event Grid sends an event to a function app. The app retrieves the Capture file and migrates data to a data warehouse. |
-| [Tutorial: Azure Service Bus to Azure Event Grid integration examples](../service-bus-messaging/service-bus-to-event-grid-integration-example.md?toc=%2fazure%2fevent-grid%2ftoc.json) | Event Grid sends messages from Service Bus topic to function app and logic app. |
+| [Tutorial: Azure Service Bus to Azure Event Grid integration examples](../service-bus-messaging/service-bus-to-event-grid-integration-example.md?toc=%2fazure%2fevent-grid%2ftoc.json) | Event Grid sends messages from Service Bus topic to a function app and a logic app. |
 
 
 ## Next steps
-For an introduction to Event Grid, see [About Event Grid](overview.md).
+See the [Event handlers](event-handlers.md) article for a list of supported event handlers. 

articles/event-grid/handler-relay-hybrid-connections.md

@@ -11,15 +11,16 @@ ms.author: spelluru
 ---
 
 # Relay Hybrid connection as an event handler for Azure Event Grid events
-An event handler is the place where the event is sent. The handler takes some further action to process the event. Several Azure services are automatically configured to handle events and **Azure Relay** is one of them. Use Azure **Relay Hybrid Connections** to send events to applications that are within an enterprise network and don't have a publicly accessible endpoint.
+An event handler is the place where the event is sent. The handler takes some further action to process the event. Several Azure services are automatically configured to handle events and **Azure Relay** is one of them. 
+
+Use Azure **Relay Hybrid Connections** to send events to applications that are within an enterprise network and don't have a publicly accessible endpoint.
 
 ## Tutorials
+See the following tutorial for an example of using an Azure Relay hybrid connection as an event handler. 
 
 |Title  |Description  |
 |---------|---------|
 | [Tutorial: send events to hybrid connection](custom-event-to-hybrid-connection.md) | Sends a custom event to an existing hybrid connection for processing by a listener application. |
 
 ## Next steps
-
-* For an introduction to Event Grid, see [About Event Grid](overview.md).
-* To quickly get started using Event Grid, see [Create and route custom events with Azure Event Grid](custom-event-quickstart.md).
+See the [Event handlers](event-handlers.md) article for a list of supported event handlers. 

articles/event-grid/handler-service-bus.md

@@ -13,21 +13,18 @@ ms.author: spelluru
 # Service Bus queues and topics as event handlers for Azure Event Grid events
 An event handler is the place where the event is sent. The handler takes some further action to process the event. Several Azure services are automatically configured to handle events and **Azure Service Bus** is one of them. 
 
+You can use a Service queue or topic as a handler for events from Event Grid. 
 
 ## Service Bus queues
 You can route events in Event Grid directly to Service Bus queues for use in buffering or command & control scenarios in enterprise applications.
 
-In the Azure portal, while creating an event subscription, select "Service Bus Queue" as endpoint type and then click "select an endpoint" in order to choose a Service Bus queue.
+In the Azure portal, while creating an event subscription, select **Service Bus Queue** as endpoint type and then click **select an endpoint** to choose a Service Bus queue.
 
 ### Using CLI to add a Service Bus queue handler
 
 For Azure CLI, the following example subscribes and connects an event grid topic to a Service Bus queue:
 
 ```azurecli-interactive
-# If you haven't already installed the extension, do it now.
-# This extension is required for preview features.
-az extension add --name eventgrid
-
 az eventgrid event-subscription create \
     --name <my-event-subscription> \
     --source-resource-id /subscriptions/{SubID}/resourceGroups/{RG}/providers/Microsoft.EventGrid/topics/topic1 \
@@ -37,19 +34,15 @@ az eventgrid event-subscription create \
 
 ## Service Bus topics
 
-You can route events in Event Grid directly to Service Bus topics in order to handle Azure system events with Service Bus topics, or for command & control messaging scenarios.
+You can route events in Event Grid directly to Service Bus topics to handle Azure system events with Service Bus topics, or for command & control messaging scenarios.
 
-In the Azure portal, while creating an event subscription, select "Service Bus Topic" as endpoint type and then click "select and endpoint" in order to choose a Service Bus topic.
+In the Azure portal, while creating an event subscription, select **Service Bus Topic** as endpoint type and then click **select and endpoint** to choose a Service Bus topic.
 
 ### Using CLI to add a Service Bus topic handler
 
 For Azure CLI, the following example subscribes and connects an event grid topic to a Service Bus queue:
 
 ```azurecli-interactive
-# If you haven't already installed the extension, do it now.
-# This extension is required for preview features.
-az extension add --name eventgrid
-
 az eventgrid event-subscription create \
     --name <my-event-subscription> \
     --source-resource-id /subscriptions/{SubID}/resourceGroups/{RG}/providers/Microsoft.EventGrid/topics/topic1 \
@@ -58,23 +51,20 @@ az eventgrid event-subscription create \
 ```
 
 ## Message properties
-Set the following message properties when sending events as messages to a Service Bus endpoint.
+If you use a **Service Bus topic or queue** as an event handler for events from Event Grid, set the following message headers: 
 
 | Property name | Description |
 | ------------- | ----------- | 
 | aeg-subscription-name | Name of event subscription. |
-| aeg-delivery-count | Number of attempts made for the event. Example: "1" |
-| aeg-event-type | Event type. Example: "Microsoft.Storage.blobCreated" | 
-| aeg-metadata-version | Metadata version of the event. Example: "1". For **Event Grid event schema**, this property represents the metadata version and for **cloud event schema**, it represents the **spec version**. |
-| aeg-data-version | Data version of the event. Example: "1". Default value: "". For **Event Grid event schema**, this property represents the data version and for **cloud event schema**, it doesn't apply. |
-| aeg-output-event-id | ID of the Event Grid event. |
+| aeg-delivery-count | <p>Number of attempts made for the event.</p> <p>Example: "1"</p> |
+| aeg-event-type | <p>Type of the event.</p><p> Example: "Microsoft.Storage.blobCreated"</p> | 
+| aeg-metadata-version | <p>Metadata version of the event.</p> <p>Example: "1".</p><p> For **Event Grid event schema**, this property represents the metadata version and for **cloud event schema**, it represents the **spec version**. </p>|
+| aeg-data-version | <p>Data version of the event.</p><p>Example: "1".</p><p>For **Event Grid event schema**, this property represents the data version and for **cloud event schema**, it doesn't apply.</p> |
 
 ## Message headers
-When sending events to a Service Bus endpoint (queue or topic) as brokered messages, the `messageid` of the brokered message is the **event ID**.
+When sending an event to a Service Bus queue or topic as a brokered message, the `messageid` of the brokered message is the **event ID**.
 
 The event ID will be maintained across redelivery of the event so that you can avoid duplicate deliveries by turning on **duplicate detection** on the service bus entity. We recommend that you enable duration of the duplicate detection on the Service Bus entity to be either the time-to-live (TTL) of the event or max retry duration, whichever is longer.
 
 ## Next steps
-
-* For an introduction to Event Grid, see [About Event Grid](overview.md).
-* To quickly get started using Event Grid, see [Create and route custom events with Azure Event Grid](custom-event-quickstart.md).
+See the [Event handlers](event-handlers.md) article for a list of supported event handlers. 

articles/event-grid/handler-storage-queues.md

@@ -16,12 +16,11 @@ An event handler is the place where the event is sent. The handler takes some fu
 Use **Queue Storage** to receive events that need to be pulled. You might use Queue storage when you have a long running process that takes too long to respond. By sending events to Queue storage, the app can pull and process events on its own schedule.
 
 ## Examples
+See the following tutorial for an example of using Queue storage as an event handler. 
 
 |Title  |Description  |
 |---------|---------|
 | [Quickstart: route custom events to Azure Queue storage with Azure CLI and Event Grid](custom-event-to-queue-storage.md) | Describes how to send custom events to a Queue storage. |
 
 ## Next steps
-
-* For an introduction to Event Grid, see [About Event Grid](overview.md).
-* To quickly get started using Event Grid, see [Create and route custom events with Azure Event Grid](custom-event-quickstart.md).
+See the [Event handlers](event-handlers.md) article for a list of supported event handlers.