freshness on Config Event conceptual article

Author: jpconnock

articles/azure-app-configuration/concept-app-configuration-event.md

@@ -1,19 +1,19 @@
 ---
-title: Reacting to Azure App Configuration key-value events | Microsoft Docs
+title: Reacting to Azure App Configuration key-value events
 description: Use Azure Event Grid to subscribe to App Configuration events. 
 services: azure-app-configuration,event-grid 
 author: jimmyca
 
 ms.author: jimmyca
-ms.date: 05/30/2019
+ms.date: 02/20/2020
 ms.topic: article
 ms.service: azure-app-configuration
 
 ---
 
 # Reacting to Azure App Configuration events
 
-Azure App Configuration events enable applications to react to changes in key-values. This is done without the need for complicated code or expensive and inefficient polling services. Instead, events are pushed through [Azure Event Grid](https://azure.microsoft.com/services/event-grid/) to subscribers such as [Azure Functions](https://azure.microsoft.com/services/functions/), [Azure Logic Apps](https://azure.microsoft.com/services/logic-apps/), or even to your own custom http listener, and you only pay for what you use.
+Azure App Configuration events enable applications to react to changes in key-values. This is done without the need for complicated code or expensive and inefficient polling services. Instead, events are pushed through [Azure Event Grid](https://azure.microsoft.com/services/event-grid/) to subscribers such as [Azure Functions](https://azure.microsoft.com/services/functions/), [Azure Logic Apps](https://azure.microsoft.com/services/logic-apps/), or even to your own custom http listener. Critically, you only pay for what you use.
 
 Azure App Configuration events are sent to the Azure Event Grid which provides reliable delivery services to your applications through rich retry policies and dead-letter delivery. To learn more, see [Event Grid message delivery and retry](https://docs.microsoft.com/azure/event-grid/delivery-and-retry).
 
@@ -70,11 +70,12 @@ Here is an example of a KeyValueModified event:
 For more information, see [Azure App Configuration events schema](../event-grid/event-schema-app-configuration.md).
 
 ## Practices for consuming events
-Applications that handle App Configuration events should follow a few recommended practices:
+Applications that handle App Configuration events should follow these recommended practices:
 > [!div class="checklist"]
-> * As multiple subscriptions can be configured to route events to the same event handler, it is important not to assume events are from a particular source, but to check the topic of the message to ensure that it comes from the App Configuration you are expecting.
-> * Similarly, check that the eventType is one you are prepared to process, and do not assume that all events you receive will be the types you expect.
-> * As messages can arrive out of order and after some delay, use the etag fields to understand if your information about objects is still up-to-date.  Also, use the sequencer fields to understand the order of events on any particular object.
+> * Multiple subscriptions can be configured to route events to the same event handler, so do not assume events are from a particular source. Instead, check the topic of the message to ensure the App Configuration instance sending the event.
+> * Check the eventType and do not assume that all events you receive will be the types you expect.
+> * Use the etag fields to understand if your information about objects is still up-to-date.  
+> * Use the sequencer fields to understand the order of events on any particular object.
 > * Use the subject field to access the key-value that was modified.