local and viewing events

Author: ddematheu2

articles/communication-services/how-tos/event-grid/local-testing-event-grid.md

@@ -1,7 +1,7 @@
 ---
 title: Test your Event Grid handler locally
 titleSuffix: An Azure Communication Services how-to document
-description: "In this how-to document, you can learn how to locally test your Event Grid handler for Azure Communication Services events with Postman"
+description: In this how-to document, you can learn how to locally test your Event Grid handler for Azure Communication Services events with Postman.
 author: ddematheu2
 manager: shahen
 services: azure-communication-services
@@ -32,7 +32,7 @@ ngrok http 7071
 
 1. Open Postman and create a new request.
 
-    ![Postman body](media/postman_body.png)
+    ![Screenshot of Postman body configuration](media/postman_body.png)
 
 2. Select the `POST` method.
 
@@ -68,10 +68,10 @@ ngrok http 7071
    - `Content-Type`: `application/json`
    - `aeg-event-type`: `Notification`
 
-    ![Postman headers](media/postman_header.png)
+    ![Screenshot of Postman headers configuration](media/postman_header.png)
 
 6. Select the `Send` button to trigger the event.
 
-    ![Postman send](media/postman_send.png)
+    ![Screenshot of Postman send button](media/postman_send.png)
 
     At this point, an event should trigger in your Azure Function. You can verify the event by looking at the execution of your Azure Function. You can then validate that the function is doing its job correctly.

articles/communication-services/how-tos/event-grid/media/postman_body.png

@@ -1,7 +1,7 @@
 ---
 title: Validate Azure Communication Services events
 titleSuffix: An Azure Communication Services how-to document
-description: "In this how-to document, you can learn how to validate Azure Communication Services events with RequestBin or Azure Event Viewer"
+description: In this how-to document, you can learn how to validate Azure Communication Services events with RequestBin or Azure Event Viewer.
 author: ddematheu2
 manager: shahen
 services: azure-communication-services
@@ -13,7 +13,7 @@ ms.service: azure-communication-services
 
 # Validate Azure Communication Services events
 
-As developers are getting started with Azure Communication Services, they often want to validate that their events are being sent by their resource. This document shows you how to validate that your events are being sent by your Azure Communication Services resource using Azure Event Grid viewer or RequestBin. 
+This document shows you how to validate that your Azure Communication Services resource sends events using Azure Event Grid viewer or RequestBin. 
 
 ## Pre-requisites
 
@@ -23,9 +23,9 @@ As developers are getting started with Azure Communication Services, they often
 
 If you already have an Azure Event Grid viewer deployed or would like to have a more robust viewer in place, you can follow instructions to [deploy it](/samples/azure-samples/azure-event-grid-viewer/azure-event-grid-viewer/). You need the endpoint generated by the Event Grid viewer.
 
-Alternatively, if you want a quick and easy way to validate your events, you can use [RequestBin](https://requestbin.com/). RequestBin offers two modalities to pick from. If you want to quickly test your events, you can use the [public endpoint](https://requestbin.com/r) set up. This public endpoints makes event data accessible to anyone with a URL. If you prefer to keep it private, you can create a RequestBin account and create a private endpoint. See RequestBin for more information about [public vs private endpoints](https://requestbin.com/docs/#public-vs-private-endpoints).
+Alternatively, if you want a quick and easy way to validate your events, you can use [RequestBin](https://requestbin.com/). RequestBin offers two modalities to pick from. If you want to quickly test your events, you can use the [public endpoint](https://requestbin.com/r) setup. These public endpoints make event data accessible to anyone with a URL. If you prefer to keep it private, you can create a RequestBin account and create a private endpoint. For more information, see RequestBin [public vs private endpoints](https://requestbin.com/docs/#public-vs-private-endpoints).
 
-![request bin url](./media/requestbin-url.png)
+![Screenshot of RequestBin URL configuration](./media/requestbin-url.png)
 
 The next steps are the same for both options.
 
@@ -43,7 +43,7 @@ The next steps are the same for both options.
 
 2. (Optional, only if using RequestBin) You need to copy the `validationURL` on the first event the gets posted to your endpoint. You need to paste that URL on your browser to validate the endpoint. The page should saw 'Webhook successfully validated as a subscription endpoint'.
 
-![request bin validation](./media/validation-request-bin.png)
+![Screenshot showing event in RequestBin](./media/validation-request-bin.png)
 
 ## View events