Fixed all correctness issues reported by acrolinx

Author: HeidiSteen

articles/search/search-howto-index-azure-data-lake-storage.md

@@ -190,7 +190,7 @@ By default, most blobs are indexed as a single search document in the index, inc
 + [Indexing JSON blobs](search-howto-index-json-blobs.md)
 + [Indexing CSV blobs](search-howto-index-csv-blobs.md)
 
-A compound or embedded document (such as a ZIP archive, a Word document with embedded Outlook email containing attachments, or a .MSG file with attachments) is also indexed as a single document. For example, all images extracted from the attachments of an .MSG file will be returned in the normalized_images field. If you have images, consider adding [AI enrichment](cognitive-search-concept-intro.md) to get more search utility from that content.
+A compound or embedded document (such as a ZIP archive, a Word document with embedded Outlook email containing attachments, or an .MSG file with attachments) is also indexed as a single document. For example, all images extracted from the attachments of an .MSG file will be returned in the normalized_images field. If you have images, consider adding [AI enrichment](cognitive-search-concept-intro.md) to get more search utility from that content.
 
 Textual content of a document is extracted into a string field named "content".
 

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

@@ -250,7 +250,7 @@ Add the following metadata properties and values to blobs in Blob Storage. When
 | Property name | Property value | Explanation |
 | ------------- | -------------- | ----------- |
 | "AzureSearch_Skip" |`"true"` |Instructs the blob indexer to completely skip the blob. Neither metadata nor content extraction is attempted. This is useful when a particular blob fails repeatedly and interrupts the indexing process. |
-| "AzureSearch_SkipContent" |`"true"` |This is equivalent of "dataToExtract" : "allMetadata" setting described [above](#PartsOfBlobToIndex) scoped to a particular blob. |
+| "AzureSearch_SkipContent" |`"true"` |This is equivalent to the `"dataToExtract" : "allMetadata"` setting described [above](#PartsOfBlobToIndex) scoped to a particular blob. |
 
 ## How to index large datasets
 

articles/search/search-howto-managed-identities-cosmos-db.md

@@ -37,7 +37,7 @@ Create the data source and provide either a system-assigned managed identity or
 
 The [REST API](/rest/api/searchservice/create-data-source), Azure portal, and the [.NET SDK](/dotnet/api/azure.search.documents.indexes.models.searchindexerdatasourcetype) support using a system-assigned managed identity. 
 
-When connecting with a system-assigned managed identity, the only change to the data source definition is the format of the "credentials" property. You'll provide the database name and a ResourceId that has no account key or password. The ResourceId must include the subscription ID of Cosmos DB, the resource group, and the Cosmos DB account name.
+When you're connecting with a system-assigned managed identity, the only change to the data source definition is the format of the "credentials" property. You'll provide the database name and a ResourceId that has no account key or password. The ResourceId must include the subscription ID of Cosmos DB, the resource group, and the Cosmos DB account name.
 
 * For SQL collections, the connection string does not require an ApiKind. 
 * For MongoDB collections, add "ApiKind=MongoDb" to the connection string. 
@@ -66,7 +66,7 @@ api-key: [Search service admin key]
 
 ### User-assigned managed identity (preview)
 
-The 2021-04-30-preview REST API supports connections based on a user-assigned managed identity. When connecting with a user-assigned managed identity, there are two changes to the data source definition:
+The 2021-04-30-preview REST API supports connections based on a user-assigned managed identity. When you're connecting with a user-assigned managed identity, there are two changes to the data source definition:
 
 * First, the format of the "credentials" property is the database name and a ResourceId that has no account key or password. The ResourceId must include the subscription ID of Cosmos DB, the resource group, and the Cosmos DB account name.
 

articles/search/search-howto-managed-identities-data-sources.md

@@ -92,7 +92,7 @@ You can use the Management REST API instead of the portal to assign a user manag
 
 ### [**Azure PowerShell**](#tab/ps-sys)
 
-See [Create a search service with a system assigned managed identity (Azure PowerShellP](search-manage-powershell.md#create-a-service-with-a-system-assigned-managed-identity).
+See [Create a search service with a system assigned managed identity (Azure PowerShell](search-manage-powershell.md#create-a-service-with-a-system-assigned-managed-identity).
 
 ### [**Azure CLI**](#tab/cli-sys)
 

articles/search/search-howto-managed-identities-sql.md

@@ -90,7 +90,7 @@ Create the data source and provide either a system-assigned managed identity or
 
 The [REST API](/rest/api/searchservice/create-data-source), Azure portal, and the [.NET SDK](/dotnet/api/azure.search.documents.indexes.models.searchindexerdatasourceconnection) support system-assigned managed identity. 
 
-When connecting with a system-assigned managed identity, the only change to the data source definition is the format of the "credentials" property. You'll provide an Initial Catalog or Database name and a ResourceId that has no account key or password. The ResourceId must include the subscription ID of Azure SQL Database, the resource group of SQL Database, and the name of the SQL database.
+When you're connecting with a system-assigned managed identity, the only change to the data source definition is the format of the "credentials" property. You'll provide an Initial Catalog or Database name and a ResourceId that has no account key or password. The ResourceId must include the subscription ID of Azure SQL Database, the resource group of SQL Database, and the name of the SQL database.
 
 Here is an example of how to create a data source to index data from a storage account using the [Create Data Source](/rest/api/searchservice/create-data-source) REST API and a managed identity connection string. The managed identity connection string format is the same for the REST API, .NET SDK, and the Azure portal.
 
@@ -113,7 +113,7 @@ api-key: [admin key]
 
 ### User-assigned managed identity (preview)
 
-The 2021-04-30-preview REST API supports connections based on a user-assigned managed identity. When connecting with a user-assigned managed identity, there are two changes to the data source definition:
+The 2021-04-30-preview REST API supports connections based on a user-assigned managed identity. When you're connecting with a user-assigned managed identity, there are two changes to the data source definition:
 
 * First, the format of the "credentials" property is an Initial Catalog or Database name and a ResourceId that has no account key or password. The ResourceId must include the subscription ID of Azure SQL Database, the resource group of SQL Database, and the name of the SQL database. This is the same format as the system-assigned managed identity.
 

articles/search/search-howto-managed-identities-storage.md

@@ -45,7 +45,7 @@ Create the data source and provide either a system-assigned managed identity or
 
 The [REST API](/rest/api/searchservice/create-data-source), Azure portal, and the [.NET SDK](/dotnet/api/azure.search.documents.indexes.models.searchindexerdatasourceconnection) support using a system-assigned managed identity.
 
-When connecting with a system-assigned managed identity, the only change to the data source definition is the format of the "credentials" property. You'll provide a ResourceId that has no account key or password. The ResourceId must include the subscription ID of the storage account, the resource group of the storage account, and the storage account name.
+When you're connecting with a system-assigned managed identity, the only change to the data source definition is the format of the "credentials" property. You'll provide a ResourceId that has no account key or password. The ResourceId must include the subscription ID of the storage account, the resource group of the storage account, and the storage account name.
 
 Here is an example of how to create a data source to index data from a storage account using the [Create Data Source](/rest/api/searchservice/create-data-source) REST API and a managed identity connection string. The managed identity connection string format is the same for the REST API, .NET SDK, and the Azure portal.
 
@@ -68,7 +68,7 @@ api-key: [admin key]
 
 ### User-assigned managed identity (preview)
 
-The 2021-04-30-preview REST API supports connections based on a user-assigned managed identity. When connecting with a user-assigned managed identity, there are two changes to the data source definition:
+The 2021-04-30-preview REST API supports connections based on a user-assigned managed identity. When you're connecting with a user-assigned managed identity, there are two changes to the data source definition:
 
 * First, the format of the "credentials" property is a ResourceId that has no account key or password. The ResourceId must include the subscription ID of the storage account, the resource group of the storage account, and the storage account name. This is the same format as the system-assigned managed identity.
 

articles/search/whats-new.md

@@ -58,7 +58,7 @@ Learn what's new in the service. Bookmark this page to keep up to date with serv
 | [Spell check query terms (preview)](speller-how-to-add.md) | Before query terms reach the search engine, you can have them checked for spelling errors. The `speller` option works with any query type (simple, full, or semantic). |  Public preview, REST only, api-version=2020-06-30-Preview|
 | [SharePoint indexer (preview)](search-howto-index-sharepoint-online.md) | This indexer connects you to a SharePoint site so that you can index content from a document library. | Public preview, REST only, api-version=2020-06-30-Preview |
 | [Normalizers (preview)](search-normalizers.md) | Normalizers provide simple text pre-processing: consistent casing, accent removal, and ASCII folding, without invoking the full text analysis chain.| Public preview, REST only, api-version=2020-06-30-Preview |
-| [Custom Entity Lookup skill](cognitive-search-skill-custom-entity-lookup.md ) |  A cognitive skill that looks for text from a custom, user-defined list of words and phrases. Using this list, it labels all documents with any matching entities. The skill also supports a degree of fuzzy matching that can be applied to find matches that are similar but not quite exact. | Generally available. |
+| [Custom Entity Lookup skill](cognitive-search-skill-custom-entity-lookup.md ) |  A cognitive skill that looks for text from a custom, user-defined list of words and phrases. From this list, the skill labels all documents with any matching entities. The skill also supports a degree of fuzzy matching that can be applied to find matches that are similar but not quite exact. | Generally available. |
 
 ## February 2021
 
@@ -125,7 +125,7 @@ Learn what's new in the service. Bookmark this page to keep up to date with serv
 
 ## New service name
 
-Azure Search was renamed to **Azure Cognitive Search** in October 2019 to reflect the expanded (yet optional) use of cognitive skills and AI processing in core operations. API versions, NuGet packages, namespaces, and endpoints are unchanged. New and existing search solutions are unaffected by the service name change.
+Azure Search was renamed to **Azure Cognitive Search** in October 2019 to reflect the expanded (yet optional) use of cognitive skills and AI processing in service operations. API versions, NuGet packages, namespaces, and endpoints are unchanged. New and existing search solutions are unaffected by the service name change.
 
 ## Service updates