Merge pull request #105666 from jlichwa/patch-17

Update event-grid-overview.md

Author: GitHubber17

articles/key-vault/event-grid-overview.md

@@ -1,17 +1,17 @@
 ---
-title: 'Tutorial: Monitoring Key Vault with Azure Event Grid'
-description: 'Tutorial: Use Azure Event Grid to subscribe to Key Vault events'
-services: media-services
+title: 'Monitoring Key Vault with Azure Event Grid'
+description: 'Use Azure Event Grid to subscribe to Key Vault events'
+services: key-vault
 author: msmbaldwin
 manager: rkarlin
 
 ms.service: key-vault
-ms.topic: tutorial
+ms.topic: conceptual
 ms.date: 11/12/2019
 ms.author: mbaldwin
 ---
 
-# Tutorial: Monitoring Key Vault with Azure Event Grid (preview)
+# Monitoring Key Vault with Azure Event Grid (preview)
 
 Key Vault integration with Event Grid is currently in preview. It allows users to be notified when the status of a secret stored in key vault has changed. A status change is defined as a secret that is about to expire (within 30 days of expiration), a secret that has expired, or a secret that has a new version available. Notifications for all three secret types (key, certificate, and secret) are supported.
 
@@ -24,9 +24,9 @@ Event grid uses [event subscriptions](../event-grid/concepts.md#event-subscripti
 For more information, see the [Key Vault event schema](../event-grid/event-schema-key-vault.md).
 
 > [!WARNING]
-> Events are triggered only on new versions of a secret after the subscription is set. For an existing secret, you must generate a new version.
+> Notification events are triggered only on new versions of secrets, keys and certificates, and you must first subscribe to the event on your key vault in order to receive these notifications.
 > 
-> Certificate events are only triggered when a certificate is automatically renewed through issuance policy.
+> You will receive notification events on certificates only when the certificate is automatically renewed according to the policy you have specified for your certificate.
 
 ## Practices for consuming events