fixed H2 bug

Author: HeidiSteen

articles/search/search-get-started-arm.md

@@ -12,7 +12,7 @@ ms.custom:
   - mode-arm
   - devx-track-arm-template
   - ignite-2023
-ms.date: 06/29/2023
+ms.date: 04/24/2023
 ---
 
 # Quickstart: Deploy Azure AI Search using an Azure Resource Manager template

articles/search/search-get-started-text.md

@@ -13,19 +13,19 @@ ms.custom:
   - devx-track-python
   - ignite-2023
 ms.topic: quickstart
-ms.date: 06/09/2023
+ms.date: 04/24/2024
 ---
 
 # Quickstart: Full text search using the Azure SDKs
 
 Learn how to use the **Azure.Search.Documents** client library in an Azure SDK to create, load, and query a search index using sample data for [**full text search**](search-lucene-query-architecture.md). Full text search uses Apache Lucene for indexing and queries, and a BM25 ranking algorithm for scoring results.
 
-This quickstart has [steps](#create-load-and-query-an-index) for the following SDKs:
+This quickstart has steps for the following SDKs:
 
-+ [Azure SDK for .NET](/dotnet/api/overview/azure/search.documents-readme)
-+ [Azure SDK for Python](/python/api/overview/azure/search-documents-readme)
-+ [Azure SDK for Java](/java/api/overview/azure/search-documents-readme)
-+ [Azure SDK for JavaScript](/javascript/api/overview/azure/search-documents-readme)
++ [Azure SDK for .NET](?tabs=dotnet#create-load-and-query-an-index)
++ [Azure SDK for Python](?tabs=python#create-load-and-query-an-index)
++ [Azure SDK for Java](?tabs=java#create-load-and-query-an-index)
++ [Azure SDK for JavaScript](?tabs=javascript#create-load-and-query-an-index)
 
 ## Prerequisites
 

articles/search/search-howto-concurrency.md

@@ -33,9 +33,9 @@ Every time you update a resource, its ETag changes automatically. When you imple
 > [!Note]
 > There is only one mechanism for concurrency. It's always used regardless of which API or SDK is used for resource updates.
 
-## Use cases and sample code
+## Example
 
-The following code demonstrates optimistic concurrency for an update operation. It fails the second update because the object's ETag is changed by a previous update. More specifically, when the ETag in the request header no longer matches the ETag of the object, the search service return a status 400 bad request message, and the update fails.
+The following code demonstrates optimistic concurrency for an update operation. It fails the second update because the object's ETag is changed by a previous update. More specifically, when the ETag in the request header no longer matches the ETag of the object, the search service return a status code of 400 (bad request), and the update fails.
 
 ```csharp
 using Azure;