Merge pull request #293441 from spelluru/egridfreshness01214

Event Grid - freshness 2

Author: prmerger-automator[bot]

articles/event-grid/communication-services-voice-video-events.md

@@ -1,10 +1,11 @@
 ---
-title: Azure Communication Services - Voice and video calling events
+title: Azure Communication Services - events 
 description: This article describes how to use Azure Communication Services as an Event Grid event source for voice and video calling Events.
-ms.topic: conceptual
-ms.date: 12/02/2022
+ms.topic: concept-article
+ms.date: 01/22/2025
 author: VikramDhumal
 ms.author: vikramdh
+# Customer intent: I want to know what events are supported by Azure Communication Services through Azure Event Grid. 
 ---
 
 # Azure Communication Services - Voice and video calling events
@@ -22,7 +23,7 @@ Azure Communication Services emits the following voice and video calling event t
 | [Microsoft.Communication.CallEnded](#microsoftcommunicationcallended)   | Published when a call ends  |
 | [Microsoft.Communication.CallParticipantAdded](#microsoftcommunicationcallparticipantadded) | Published when a participant is added to a call AND they join it |
 | [Microsoft.Communication.CallParticipantRemoved](#microsoftcommunicationcallparticipantremoved) | Published when a participant leaves or is removed from a call  |
-| [Microsoft.Communication.IncomingCall](#microsoftcommunicationincomingcall) | Published when there is an incoming call  |
+| [Microsoft.Communication.IncomingCall](#microsoftcommunicationincomingcall) | Published when there's an incoming call  |
 
 ## Event responses
 
@@ -280,10 +281,10 @@ This section contains an example of what that data would look like for each even
 ```
 
 ## Limitations
-Aside from `IncomingCall`, Calling events are only available for Azure Communication Services VoIP users. PSTN, bots, echo bot and Teams users events are excluded.
-No calling events will be available for Azure Communication Services - Teams meeting interop call.
+Aside from `IncomingCall`, Calling events are only available for Azure Communication Services VoIP users. Public Switched Telephone Network (PSTN), bots, echo bot, and Teams users events are excluded.
+No calling events are available for Azure Communication Services - Teams meeting interop call.
 
-`IncomingCall` events have support for Azure Communication Services VoIP users and PSTN numbers. For more details on which scenarios can trigger `IncomingCall` events, see the following [Incoming call concepts](../communication-services/concepts/call-automation/incoming-call-notification.md) documentation. 
+`IncomingCall` events have support for Azure Communication Services VoIP users and PSTN numbers. For more information about scenarios that can trigger `IncomingCall` events, see the following [Incoming call concepts](../communication-services/concepts/call-automation/incoming-call-notification.md) documentation. 
 
-## Next steps
+## Related content
 See the following tutorial: [Quickstart: Handle voice and video calling events](../communication-services/quickstarts/voice-video-calling/handle-calling-events.md).

articles/event-grid/how-to-filter-events.md

@@ -1,9 +1,10 @@
 ---
 title: How to filter events for Azure Event Grid
 description: This article shows how to filter events (by event type, by subject, by operators and data, etc.) when creating an Event Grid subscription. 
-ms.topic: conceptual
+ms.topic: how-to
 ms.custom: devx-track-azurecli, devx-track-azurepowershell
-ms.date: 09/25/2023
+ms.date: 01/22/2025
+# Customer intent: I want to know how to subscribe for a subset of events from a source by filtering them. 
 ---
 
 # Filter events for Event Grid
@@ -150,7 +151,7 @@ az eventgrid event-subscription create \
 For an existing event subscription: 
 
 1. On the **Event Subscription** page, select **Enable subject filtering**. 
-1. Enter values for one or more of the following fields: **Subject begins with** and **Subject ends with**. In the following options both options are selected. 
+1. Enter values for one or more of the following fields: **Subject begins with** and **Subject ends with**. In the following example, both options are selected. 
 
     :::image type="content" source="./media/how-to-filter-events/subject-filter-example.png" alt-text="Screenshot of Event Subscription page with subject filtering example.":::
 1. Select **Case-sensitive subject matching** option if you want the subject of the event to match the case of the filters specified. 
@@ -360,5 +361,5 @@ event='[ {"id": "'"$RANDOM"'", "eventType": "recordInserted", "subject": "myapp/
 curl -X POST -H "aeg-sas-key: $key" -d "$event" $topicEndpoint
 ```
 
-## Next steps
+## Related content
 To learn more about filters (event types, subject, and advanced), see [Understand event filtering for Event Grid subscriptions](event-filtering.md). 

articles/event-grid/troubleshoot-subscription-validation.md

@@ -1,8 +1,9 @@
 ---
 title: Azure Event Grid - Troubleshooting subscription validation
-description: This article shows you how you can troubleshoot subscription validations. 
-ms.topic: conceptual
-ms.date: 09/28/2021
+description: This article shows you how you can troubleshoot subscription validations for Event Grid events and cloud events. 
+ms.topic: how-to
+ms.date: 01/22/2025
+# Customer intent: I want to know how to troubleshoot issues with event subscriptions in Azure Event Grid. 
 ---
 
 # Troubleshoot Azure Event Grid subscription validations
@@ -21,7 +22,7 @@ During event subscription creation, if you're seeing an error message such as `T
 > [!IMPORTANT]
 > For detailed information on endpoint validation for webhooks, see [Webhook event delivery](end-point-validation-cloud-events-schema.md).
 
-Here is a sample **SubscriptionValidationEvent** JSON you can send using a tool such as CURL: 
+Here's a sample **SubscriptionValidationEvent** JSON you can send using a tool such as CURL: 
 
 ```json
 [
@@ -40,7 +41,7 @@ Here is a sample **SubscriptionValidationEvent** JSON you can send using a tool
 ]
 ```
 
-Here is the sample successful response:
+Here's the sample successful response:
 
 ```json
 {
@@ -58,12 +59,10 @@ curl -X POST -d '[{"id": "2d1781af-3a4c-4d7c-bd0c-e34b19da4e66","topic": "/subsc
 
 
 
-To learn more about Event Grid event validation for webhooks, see [Endpoint validation with event grid events](end-point-validation-cloud-events-schema.md).
+To learn more about Event Grid event validation for webhooks, see [Endpoint validation with Event Grid events](end-point-validation-cloud-events-schema.md).
 
 ## Validate cloud event subscription
 Use the **HTTP OPTIONS** method for validation with cloud events. To learn more about cloud event validation for webhooks, see [Endpoint validation with cloud events](end-point-validation-cloud-events-schema.md).
 
-## Troubleshoot event subscription validation
-
-## Next steps
+## Related content
 If you need more help, post your issue in the [Stack Overflow forum](https://stackoverflow.com/questions/tagged/azure-eventgrid) or open a [support ticket](https://azure.microsoft.com/support/options/).