Fixed broken link

Author: HeidiSteen

articles/search/cognitive-search-concept-annotations-syntax.md

@@ -50,7 +50,7 @@ The following list includes several common examples:
 + `/document/pages/*` or `/document/sentences/*` become the context if you're breaking a large document into smaller chunks for processing. If "context" is `/document/pages/*`, the skill executes once over each page in the document. Because there might be more than one page or sentence, you'll append `/*` to catch them all.
 + `/document/normalized_images/*` is created during document cracking if the document contains images. All paths to images start with normalized_images. Since there are often multiple images embedded in a document, append `/*`.
 
-Examples in the remainder of this article are based on the "content" field generated automatically by [Azure Blob indexers](search-howto-indexing-azure-blob-storage.md) as part of the [document cracking](search-indexer-overview.md#document-cracking) phase. When referring to documents from a Blob container, use a format such as `"/document/content"`, where the "content" field is part of the "document".
+Examples in the remainder of this article are based on the "content" field generated automatically by [Azure blob indexers](search-howto-indexing-azure-blob-storage.md) as part of the [document cracking](search-indexer-overview.md#document-cracking) phase. When referring to documents from a Blob container, use a format such as `"/document/content"`, where the "content" field is part of the "document".
 
 <a name="example-1"></a>
 

articles/search/cognitive-search-skill-image-analysis.md

@@ -49,7 +49,7 @@ Parameters are case-sensitive.
 
 | Input name  | Description                                          |
 |---------------|------------------------------------------------------|
-| `image`         | Complex Type. Currently only works with "/document/normalized_images" field, produced by the Azure Blob indexer when ```imageAction``` is set to a value other than ```none```. |
+| `image`         | Complex Type. Currently only works with "/document/normalized_images" field, produced by the Azure blob indexer when ```imageAction``` is set to a value other than ```none```. |
 
 ## Skill outputs
 

articles/search/cognitive-search-skill-ocr.md

@@ -52,7 +52,7 @@ In previous versions, there was a parameter called "textExtractionAlgorithm" to
 
 | Input name      | Description                                          |
 |---------------|------------------------------------------------------|
-| `image`         | Complex Type. Currently only works with "/document/normalized_images" field, produced by the Azure Blob indexer when ```imageAction``` is set to a value other than ```none```. |
+| `image`         | Complex Type. Currently only works with "/document/normalized_images" field, produced by the Azure blob indexer when ```imageAction``` is set to a value other than ```none```. |
 
 ## Skill outputs
 

articles/search/search-blob-storage-integration.md

@@ -66,23 +66,23 @@ Textual content of a document is extracted into a string field named "content".
   > [!NOTE]
   > Azure AI Search imposes [indexer limits](search-limits-quotas-capacity.md#indexer-limits) on how much text it extracts depending on the pricing tier. A warning will appear in the indexer status response if documents are truncated.  
 
-## Use a Blob indexer for content extraction
+## Use a blob indexer for content extraction
 
 An *indexer* is a data-source-aware subservice in Azure AI Search, equipped with internal logic for sampling data, reading and retrieving data and metadata, and serializing data from native formats into JSON documents for subsequent import. 
 
 Blobs in Azure Storage are indexed using the [blob indexer](search-howto-indexing-azure-blob-storage.md). You can invoke this indexer by using the **Azure AI Search** command in Azure Storage, the **Import data** wizard, a REST API, or the .NET SDK. In code, you use this indexer by setting the type, and by providing connection information that includes an Azure Storage account along with a blob container. You can subset your blobs by creating a virtual directory, which you can then pass as a parameter, or by filtering on a file type extension.
 
 An indexer ["cracks a document"](search-indexer-overview.md#document-cracking), opening a blob to inspect content. After connecting to the data source, it's the first step in the pipeline. For blob data, this is where PDF, Office docs, and other content types are detected. Document cracking with text extraction is no charge. If your blobs contain image content, images are ignored unless you [add AI enrichment](cognitive-search-concept-intro.md). Standard indexing applies only to text content.
 
-The Blob indexer comes with configuration parameters and supports change tracking if the underlying data provides sufficient information. You can learn more about the core functionality in [Blob indexer](search-howto-indexing-azure-blob-storage.md).
+The Azure blob indexer comes with configuration parameters and supports change tracking if the underlying data provides sufficient information. You can learn more about the core functionality in [Index data from Azure Blob Storage](search-howto-indexing-azure-blob-storage.md).
 
 ### Supported access tiers
 
 Blob storage [access tiers](../storage/blobs/access-tiers-overview.md) include hot, cool, and archive. Only hot and cool can be accessed by indexers. 
 
 ### Supported content types
 
-By running a Blob indexer over a container, you can extract text and metadata from the following content types with a single query:
+By running a blob indexer over a container, you can extract text and metadata from the following content types with a single query:
 
 [!INCLUDE [search-blob-data-sources](../../includes/search-blob-data-sources.md)]
 

articles/search/search-how-to-create-search-index.md

@@ -34,7 +34,7 @@ In this article, learn the steps for defining and publishing a search index. Cre
 
 ## Document keys
 
-A search index has one required field: a document key. A document key is the unique identifier of a search document. In Azure AI Search, it must be a string, and it must originate from unique values in the data source that's providing the content to be indexed. A search service doesn't generate key values, but in some scenarios (such as the [Azure Table indexer](search-howto-indexing-azure-tables.md)) it synthesizes existing values to create a unique key for the documents being indexed.
+A search index has one required field: a document key. A document key is the unique identifier of a search document. In Azure AI Search, it must be a string, and it must originate from unique values in the data source that's providing the content to be indexed. A search service doesn't generate key values, but in some scenarios (such as the [Azure table indexer](search-howto-indexing-azure-tables.md)) it synthesizes existing values to create a unique key for the documents being indexed.
 
 During incremental indexing, where new and updated content is indexed, incoming documents with new keys are added, while incoming documents with existing keys are either merged or overwritten, depending on whether index fields are null or populated.
 

articles/search/search-howto-index-cosmosdb.md

@@ -311,7 +311,7 @@ If you're using a [custom query to retrieve documents](#flatten-structures), mak
 
 In some cases, even if your query contains an `ORDER BY [collection alias]._ts` clause, Azure AI Search might not infer that the query is ordered by the `_ts`. You can tell Azure AI Search that results are ordered by setting the `assumeOrderByHighWaterMarkColumn` configuration property. 
 
-To specify this hint, [create or update your indexer definition](#configure-and-run-the-azure-cosmos-db-indexer) as follows: 
+To specify this hint, [create or update your indexer definition](#configure-and-run-the-azure-cosmos-db-for-nosql-indexer) as follows: 
 
 ```http
 {

articles/search/search-howto-index-json-blobs.md

@@ -1,7 +1,7 @@
 ---
 title: Search over JSON blobs
 titleSuffix: Azure AI Search
-description: Extract searchable text from JSON blobs using the Blob indexer in Azure AI Search. Indexers provide indexing automation for supported data sources like Azure Blob Storage.
+description: Extract searchable text from JSON blobs using the blob indexer in Azure AI Search. Indexers provide indexing automation for supported data sources like Azure Blob Storage.
 
 manager: nitinme
 author: HeidiSteen

articles/search/search-howto-index-one-to-many-blobs.md

@@ -1,7 +1,7 @@
 ---
 title: Index blobs containing multiple documents
 titleSuffix: Azure AI Search
-description: Crawl Azure blobs for text content using the Azure AI Search Blob indexer, where each blob might yield one or more search index documents.
+description: Crawl Azure blobs for text content using the Azure blob indexer, where each blob might yield one or more search index documents.
 
 manager: nitinme
 author: arv100kri

articles/search/search-howto-index-sharepoint-online.md

@@ -64,7 +64,7 @@ Here are the limitations of this feature:
 
 Here are the considerations when using this feature:
 
-+ If you need a SharePoint content indexing solution in a production environment, consider creating a custom connector with [SharePoint Webhooks](/sharepoint/dev/apis/webhooks/overview-sharepoint-webhooks), calling [Microsoft Graph API](/graph/use-the-api) to export the data to an Azure Blob container, and then use the [Azure Blob indexer](search-howto-indexing-azure-blob-storage.md) for incremental indexing.
++ If you need a SharePoint content indexing solution in a production environment, consider creating a custom connector with [SharePoint Webhooks](/sharepoint/dev/apis/webhooks/overview-sharepoint-webhooks), calling [Microsoft Graph API](/graph/use-the-api) to export the data to an Azure Blob container, and then use the [Azure blob indexer](search-howto-indexing-azure-blob-storage.md) for incremental indexing.
 
 <!-- + There could be Microsoft 365 processes that update SharePoint file system-metadata (based on different configurations in SharePoint) and will cause the SharePoint Online indexer to trigger. Make sure that you test your setup and understand the document processing count prior to using any AI enrichment. Since this is a third-party connector to Azure (SharePoint is located in Microsoft 365), SharePoint configuration is not checked by the indexer. -->
 

articles/search/search-howto-indexing-azure-blob-storage.md

@@ -1,7 +1,7 @@
 ---
-title: Azure Blob indexer
+title: Azure blob indexer
 titleSuffix: Azure AI Search
-description: Set up an Azure Blob indexer to automate indexing of blob content for full text search operations and knowledge mining in Azure AI Search.
+description: Set up an Azure blob indexer to automate indexing of blob content for full text search operations and knowledge mining in Azure AI Search.
 author: gmndrg
 ms.author: gimondra
 manager: nitinme