Merge pull request #110380 from xyh1/patch-108

minor update

Author: PRMerger18

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

@@ -17,7 +17,7 @@ This article provides the properties and schema for blob storage events. For an
 For a list of sample scripts and tutorials, see [Storage event source](event-sources.md#storage).
 
 >[!NOTE]
-> Only storage accounts of kind **StorageV2 (general purpose v2)** and **BlobStorage** support event integration. **Storage (genral purpose v1)** does *not* support integration with Event Grid.
+> Only storage accounts of kind **StorageV2 (general purpose v2)**, **BlockBlobStorage**, and **BlobStorage** support event integration. **Storage (genral purpose v1)** does *not* support integration with Event Grid.
 
 ## List of events for Blob REST APIs
 
@@ -33,7 +33,7 @@ These events are triggered when a client creates, replaces, or deletes a blob by
 
 ## List of the events for Azure Data Lake Storage Gen 2 REST APIs
 
-These events are triggered if you enable a hierarchical namespace on the storage account, and clients call Azure Data Lake Storage Gen2 REST APIs.
+These events are triggered if you enable a hierarchical namespace on the storage account, and clients call Azure Data Lake Storage Gen2 REST APIs. For more information bout Azure Data Lake Storage Gen2, see [Introduction to Azure Data Lake Storage Gen2](../storage/blobs/data-lake-storage-introduction.md).
 
 |Event name|Description|
 |----------|-----------|
@@ -85,7 +85,7 @@ This section contains an example of what that data would look like for each blob
 
 ### Microsoft.Storage.BlobCreated event (Data Lake Storage Gen2)
 
-If the blob storage account has a hierarchical namespace, the data looks similar to the previous example with the exception of the these changes:
+If the blob storage account has a hierarchical namespace, the data looks similar to the previous example with the exception of these changes:
 
 * The `dataVersion` key is set to a value of `2`.
 
@@ -150,7 +150,7 @@ If the blob storage account has a hierarchical namespace, the data looks similar
 
 ### Microsoft.Storage.BlobDeleted event (Data Lake Storage Gen2)
 
-If the blob storage account has a hierarchical namespace, the data looks similar to the previous example with the exception of the these changes:
+If the blob storage account has a hierarchical namespace, the data looks similar to the previous example with the exception of these changes:
 
 * The `dataVersion` key is set to a value of `2`.
 

articles/storage/blobs/storage-blob-event-overview.md

@@ -3,7 +3,7 @@ title: Reacting to Azure Blob storage events | Microsoft Docs
 description: Use Azure Event Grid to subscribe to Blob storage events. 
 author: normesta
 ms.author: normesta
-ms.date: 01/30/2018
+ms.date: 04/06/2020
 ms.topic: conceptual
 ms.service: storage
 ms.subservice: blobs
@@ -12,15 +12,15 @@ ms.reviewer: cbrooks
 
 # Reacting to Blob storage events
 
-Azure Storage events allow applications to react to events, such as the creation and deletion of blobs. It does so without the need for complicated code or expensive and inefficient polling services.
+Azure Storage events allow applications to react to events, such as the creation and deletion of blobs. It does so without the need for complicated code or expensive and inefficient polling services. The best part is you only pay for what you use.
 
-Events are pushed using [Azure Event Grid](https://azure.microsoft.com/services/event-grid/) to subscribers such as Azure Functions, Azure Logic Apps, or even to your own http listener. The best part is you only pay for what you use.
+Blob storage events are pushed using [Azure Event Grid](https://azure.microsoft.com/services/event-grid/) to subscribers such as Azure Functions, Azure Logic Apps, or even to your own http listener. Event Grid provides reliable event delivery to your applications through rich retry policies and dead-lettering.
 
-Blob storage sends events to Event Grid which provides reliable event delivery to your applications through rich retry policies and dead-lettering.
+See the [Blob storage events schema](../../event-grid/event-schema-blob-storage.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json) article to view the full list of the events that Blob storage supports.
 
 Common Blob storage event scenarios include image or video processing, search indexing, or any file-oriented workflow. Asynchronous file uploads are a great fit for events. When changes are infrequent, but your scenario requires immediate responsiveness, event-based architecture can be especially efficient.
 
-If you want to try this out now, see any of these quickstart articles:
+If you want to try blob storage events, see any of these quickstart articles:
 
 |If you want to use this tool:    |See this article: |
 |--|-|
@@ -34,7 +34,7 @@ To view in-depth examples of reacting to Blob storage events by using Azure func
 - [Tutorial: Automate resizing uploaded images using Event Grid](https://docs.microsoft.com/azure/event-grid/resize-images-on-storage-blob-upload-event?tabs=dotnet)
 
 >[!NOTE]
-> Only storage accounts of kind **StorageV2 (general purpose v2)** and **BlobStorage** support event integration. **Storage (genral purpose v1)** does *not* support integration with Event Grid.
+> Only storage accounts of kind **StorageV2 (general purpose v2)**, **BlockBlobStorage**, and **BlobStorage** support event integration. **Storage (genral purpose v1)** does *not* support integration with Event Grid.
 
 ## The event model
 
@@ -93,6 +93,7 @@ Applications that handle Blob storage events should follow a few recommended pra
 > * 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 after some delay, use the etag fields to understand if your information about objects is still up-to-date. To learn how to use the etag field, see [Managing concurrency in Blob storage](https://docs.microsoft.com/azure/storage/common/storage-concurrency?toc=%2fazure%2fstorage%2fblobs%2ftoc.json#managing-concurrency-in-blob-storage). 
 > * As messages can arrive out of order, use the sequencer fields to understand the order of events on any particular object. The sequencer field is a string value that represents the logical sequence of events for any particular blob name. You can use standard string comparison to understand the relative sequence of two events on the same blob name.
+> Storage events guarantees at-least-once delivery to subscribers, which ensures that all messages are outputted. However due to retries or availability of subscriptions, duplicate messages may occasionally occur.
 > * Use the blobType field to understand what type of operations are allowed on the blob, and which client library types you should use to access the blob. Valid values are either `BlockBlob` or `PageBlob`. 
 > * Use the url field with the `CloudBlockBlob` and `CloudAppendBlob` constructors to access the blob.
 > * Ignore fields you don't understand. This practice will help keep you resilient to new features that might be added in the future.
@@ -104,4 +105,5 @@ Applications that handle Blob storage events should follow a few recommended pra
 Learn more about Event Grid and give Blob storage events a try:
 
 - [About Event Grid](../../event-grid/overview.md)
+- [Blob storage events schema](../../event-grid/event-schema-blob-storage.md?toc=%2fazure%2fstorage%2fblobs%2ftoc.json)
 - [Route Blob storage Events to a custom web endpoint](storage-blob-event-quickstart.md)