Merge pull request #262951 from spelluru/freshnessupdates0110

Event Grid freshness review

Author: prmerger-automator[bot]

articles/event-grid/event-schema-blob-storage.md

@@ -2,7 +2,7 @@
 title: Azure Blob Storage as Event Grid source
 description: Describes the properties that are provided for blob storage events with Azure Event Grid
 ms.topic: conceptual
-ms.date: 12/02/2022
+ms.date: 01/10/2024
 ---
 
 # Azure Blob Storage as an Event Grid source
@@ -642,7 +642,7 @@ If the blob storage account uses SFTP to create or overwrite a blob, then the da
 
 * The `data.api` key is set to the string `SftpCreate` or `SftpCommit`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `contentType` key is set to `application/octet-stream`.
 
@@ -689,7 +689,7 @@ If the blob storage account uses SFTP to delete a blob, then the data looks simi
 
 * The `data.api` key is set to the string `SftpRemove`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `contentType` key is set to `application/octet-stream`.
 
@@ -726,7 +726,7 @@ If the blob storage account uses SFTP to rename a blob, then the data looks simi
 
 * The `data.api` key is set to the string `SftpRename`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `identity` key is included in the data set. This corresponds to the local user used for SFTP authentication.
 
@@ -761,7 +761,7 @@ If the blob storage account uses SFTP to create a directory, then the data looks
 
 * The `data.api` key is set to the string `SftpMakeDir`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `identity` key is included in the data set. This corresponds to the local user used for SFTP authentication.
 
@@ -794,7 +794,7 @@ If the blob storage account uses SFTP to rename a directory, then the data looks
 
 * The `data.api` key is set to the string `SftpRename`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `identity` key is included in the data set. This corresponds to the local user used for SFTP authentication.
 
@@ -828,7 +828,7 @@ If the blob storage account uses SFTP to delete a directory, then the data looks
 
 * The `data.api` key is set to the string `SftpRemoveDir`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `identity` key is included in the data set. This corresponds to the local user used for SFTP authentication.
 
@@ -866,7 +866,7 @@ If the blob storage account uses SFTP to create or overwrite a blob, then the da
 
 * The `data.api` key is set to the string `SftpCreate` or `SftpCommit`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `contentType` key is set to `application/octet-stream`.
 
@@ -912,7 +912,7 @@ If the blob storage account uses SFTP to delete a blob, then the data looks simi
 
 * The `data.api` key is set to the string `SftpRemove`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `contentType` key is set to `application/octet-stream`.
 
@@ -948,7 +948,7 @@ If the blob storage account uses SFTP to rename a blob, then the data looks simi
 
 * The `data.api` key is set to the string `SftpRename`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `identity` key is included in the data set. This corresponds to the local user used for SFTP authentication.
 
@@ -982,7 +982,7 @@ If the blob storage account uses SFTP to create a directory, then the data looks
 
 * The `data.api` key is set to the string `SftpMakeDir`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `identity` key is included in the data set. This corresponds to the local user used for SFTP authentication.
 
@@ -1014,7 +1014,7 @@ If the blob storage account uses SFTP to rename a directory, then the data looks
 
 * The `data.api` key is set to the string `SftpRename`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `identity` key is included in the data set. This corresponds to the local user used for SFTP authentication.
 
@@ -1047,7 +1047,7 @@ If the blob storage account uses SFTP to delete a directory, then the data looks
 
 * The `data.api` key is set to the string `SftpRemoveDir`.
 
-* The `clientRequestId` key is not included.
+* The `clientRequestId` key isn't included.
 
 * The `identity` key is included in the data set. This corresponds to the local user used for SFTP authentication.
 
@@ -1082,7 +1082,7 @@ These events are triggered when the actions defined by a policy are performed.
 
  |Event name |Description|
  |----------|-----------|
- | [Microsoft.Storage.BlobInventoryPolicyCompleted](#microsoftstorageblobinventorypolicycompleted-event) |Triggered when the inventory run completes for a rule that is defined an inventory policy. This event also occurs if the inventory run fails with a user error before it starts to run. For example, an invalid policy, or an error that occurs when a destination container is not present will trigger the event.   |
+ | [Microsoft.Storage.BlobInventoryPolicyCompleted](#microsoftstorageblobinventorypolicycompleted-event) |Triggered when the inventory run completes for a rule that is defined an inventory policy. This event also occurs if the inventory run fails with a user error before it starts to run. For example, an invalid policy, or an error that occurs when a destination container isn't present will trigger the event.   |
  | [Microsoft.Storage.LifecyclePolicyCompleted](#microsoftstoragelifecyclepolicycompleted-event) |Triggered when the actions defined by a lifecycle management policy are performed. |
 
 ### Example events

articles/event-grid/handler-webhooks.md

@@ -2,7 +2,7 @@
 title: Webhooks as event handlers for Azure Event Grid events
 description: Describes how you can use webhooks as event handlers for Azure Event Grid events. Azure Automation runbooks and logic apps are supported as event handlers via webhooks. 
 ms.topic: conceptual
-ms.date: 11/17/2022
+ms.date: 01/10/2024
 ---
 
 # Webhooks, Automation runbooks, Logic Apps as event handlers for Azure Event Grid events

articles/event-grid/receive-events.md

@@ -1,8 +1,8 @@
 ---
 title: Receive events from Azure Event Grid to an HTTP endpoint
-description: Describes how to validate an HTTP endpoint, then receive and deserialize Events from Azure Event Grid
+description: Describes how to validate an HTTP endpoint, then receive and deserialize Events from Azure Event Grid.
 ms.topic: conceptual
-ms.date: 11/14/2022
+ms.date: 01/10/2024
 ms.devlang: csharp, javascript
 ms.custom: devx-track-csharp
 ---
@@ -12,7 +12,7 @@ ms.custom: devx-track-csharp
 This article describes how to [validate an HTTP endpoint](webhook-event-delivery.md) to receive events from an Event Subscription and then receive and deserialize events. This article uses an Azure Function for demonstration purposes, however the same concepts apply regardless of where the application is hosted.
 
 > [!NOTE]
-> It is recommended that you use an [Event Grid Trigger](../azure-functions/functions-bindings-event-grid.md) when triggering an Azure Function with Event Grid. It provides an easier and quicker integration between Event Grid and Azure Functions. However, please note that Azure Functions' Event Grid trigger does not support the scenario where the hosted code needs to control the HTTP status code returned to Event Grid. Given this limitation, your code running on an Azure Function would not be able to return a 5XX error to initiate an event delivery retry by Event Grid, for example.
+> We recommend that you use an [Event Grid Trigger](../azure-functions/functions-bindings-event-grid.md) when triggering an Azure Function with Event Grid. It provides an easier and quicker integration between Event Grid and Azure Functions. However, note that Azure Functions' Event Grid trigger does not support the scenario where the hosted code needs to control the HTTP status code returned to Event Grid. Given this limitation, your code running on an Azure Function would not be able to return a 5XX error to initiate an event delivery retry by Event Grid, for example.
 
 ## Prerequisites
 
@@ -28,7 +28,7 @@ SDKs for other languages are available via the [Publish SDKs](./sdk-overview.md#
 
 The first thing you want to do is handle `Microsoft.EventGrid.SubscriptionValidationEvent` events. Every time someone subscribes to an event, Event Grid sends a validation event to the endpoint with a `validationCode` in the data payload. The endpoint is required to echo this back in the response body to [prove the endpoint is valid and owned by you](webhook-event-delivery.md). If you're using an [Event Grid Trigger](../azure-functions/functions-bindings-event-grid.md) rather than a WebHook triggered Function, endpoint validation is handled for you. If you use a third-party API service (like [Zapier](https://zapier.com/) or [IFTTT](https://ifttt.com/)), you might not be able to programmatically echo the validation code. For those services, you can manually validate the subscription by using a validation URL that is sent in the subscription validation event. Copy that URL in the `validationUrl` property and send a GET request either through a REST client or your web browser.
 
-In C#, the `ParseMany()` method is used to deserialize a `BinaryData` instance containing 1 or more events into an array of `EventGridEvent`. If you knew ahead of time that you are deserializing only a single event, you could use the `Parse` method instead.
+In C#, the `ParseMany()` method is used to deserialize a `BinaryData` instance containing one or more events into an array of `EventGridEvent`. If you knew ahead of time that you are deserializing only a single event, you could use the `Parse` method instead.
 
 To programmatically echo the validation code, use the following code.
 
@@ -257,7 +257,7 @@ You should see the blob URL output in the function log:
 2022-11-14T22:40:46.346 [Information] Executed 'Function1' (Succeeded, Id=8429137d-9245-438c-8206-f9e85ef5dd61, Duration=387ms)
 ```
 
-You can also test by creating a Blob storage account or General Purpose V2 (GPv2) Storage account, [adding an event subscription](../storage/blobs/storage-blob-event-quickstart.md), and setting the endpoint to the function URL:
+You can also test by creating a Blob storage account or General Purpose V2 Storage account, [adding an event subscription](../storage/blobs/storage-blob-event-quickstart.md), and setting the endpoint to the function URL:
 
 ![Function URL](./media/receive-events/function-url.png)