Merge pull request #286133 from pauljewellmsft/patch-1

Update concurrency-manage.md

Author: prmerger-automator[bot]

articles/storage/blobs/concurrency-manage.md

@@ -1,19 +1,19 @@
 ---
-title: Managing concurrency in Blob storage
+title: Manage concurrency in Blob Storage
 titleSuffix: Azure Storage
 description: Learn how to manage multiple writers to a blob by implementing either optimistic or pessimistic concurrency in your application. Optimistic concurrency checks the ETag value for a blob and compares it to the ETag provided. Pessimistic concurrency uses an exclusive lease to lock the blob to other writers.
 services: storage
 author: pauljewellmsft
 
 ms.service: azure-blob-storage
 ms.topic: conceptual
-ms.date: 04/05/2023
+ms.date: 09/04/2024
 ms.author: pauljewell
 ms.devlang: csharp
 ms.custom: devx-track-csharp
 ---
 
-# Managing Concurrency in Blob storage
+# Manage concurrency in Blob Storage
 
 Modern applications often have multiple users viewing and updating data simultaneously. Application developers need to think carefully about how to provide a predictable experience to their end users, particularly for scenarios where multiple users can update the same data. There are three main data concurrency strategies that developers typically consider:
 

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

@@ -93,7 +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.
 
-- While most messages arrive in near real-time, there is no service level agreement around the time it takes for a message to arrive. In some instances, it might take few minutes for the message to arrive. 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](./concurrency-manage.md?toc=/azure/storage/blobs/toc.json#managing-concurrency-in-blob-storage).  
+- While most messages arrive in near real-time, there is no service level agreement around the time it takes for a message to arrive. In some instances, it might take few minutes for the message to arrive. 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 [Manage concurrency in Blob Storage](./concurrency-manage.md?toc=/azure/storage/blobs/toc.json#manage-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.