Fixed blocking errors

Author: HeidiSteen

articles/search/search-howto-monitor-indexers.md

@@ -28,21 +28,21 @@ You can see the current status of all of your indexers in your search service Ov
 | **Failed** | The number of errors exceeded **Max failed items** and indexing has stopped. |
 | **Reset** | The indexer's internal change tracking state was reset. The indexer will run in full, refreshing all documents, and not just those with newer timestamps. |
 
-You can click on an indexer in the list to see more details about the indexer's current and recent runs.
+You can select on an indexer in the list to see more details about the indexer's current and recent runs.
 
    ![Indexer summary and execution history](media/search-monitor-indexers/indexer-summary.png "Indexer summary and execution history")
 
 The **Indexer summary** chart displays a graph of the number of documents processed in its most recent runs.
 
-The **Execution details** list shows up to 50 of the most recent execution results. Click on an execution result in the list to see specifics about that run. This includes its start and end times, and any errors and warnings that occurred.
+The **Execution details** list shows up to 50 of the most recent execution results. Select on an execution result in the list to see specifics about that run. This includes its start and end times, and any errors and warnings that occurred.
 
    ![Indexer execution details](media/search-monitor-indexers/indexer-execution.png "Indexer execution details")
 
-If there were document-specific problems during the run, they will be listed in the Errors and Warnings fields.
+If there were document-specific problems during the run, they'll be listed in the Errors and Warnings fields.
 
    ![Indexer details with errors](media/search-monitor-indexers/indexer-execution-error.png "Indexer details with errors")
 
-Warnings are common with some types of indexers, and do not always indicate a problem. For example indexers that use Cognitive Services can report warnings when image or PDF files don't contain any text to process. 
+Warnings are common with some types of indexers, and don't always indicate a problem. For example indexers that use Cognitive Services can report warnings when image or PDF files don't contain any text to process. 
 
 For more information about investigating indexer errors and warnings, see [Indexer troubleshooting guidance](search-indexer-troubleshooting.md).
 
@@ -55,13 +55,13 @@ Metric views can be filtered or split up by a set of predefined dimensions.
 | Metric Name  |  Description | Dimensions  | Sample use cases |
 |---|---|---|---|
 | Document processed count  | Shows the number of indexer processed documents.  | Data source name, failed, index name, indexer name, skillset name  | <br> - Can be referenced as a rough measure of throughput (number of documents processed by indexer over time) <br> - Set up to alert on failed documents | 
-|  Skill execution invocation count | Shows the number of skill invocations. | Data source name, failed, index name, indexer name, skill name, skill type, skillset name | <br> - Reference to ensure skills are invoked as expected by comparing relative invocation numbers between skills and number of skill invocation to the number of documents. <br> - Set up to alert on failed skill invocations |
+|  Skill execution invocation count | Shows the number of skill invocations. | Data source name, failed, index name, indexer name, skill name, skill type, skillset name | <br> - Reference to ensure skills are invoked as expected by comparing relative invocation numbers between skills and number of skill invocations to the number of documents. <br> - Set up to alert on failed skill invocations |
 
 The screenshot below shows the number of documents processed by indexers within a service over an hour, split up by indexer name.
 
    ![Indexer documents processed metric](media/search-monitor-indexers/indexers-documents-processed-metric.png "Indexer documents processed metric")
 
-You can also configure the graph to see the number of skill invocation over the same hour interval.
+You can also configure the graph to see the number of skill invocations over the same hour interval.
 
    ![Indexer skills invoked metric](media/search-monitor-indexers/indexers-skill-invocation-metric.png "Indexer skill invocation metric")
 
@@ -107,13 +107,13 @@ The response contains overall indexer status, the last (or in-progress) indexer
 
 Execution history contains up to the 50 most recent runs, which are sorted in reverse chronological order (most recent first).
 
-Note there are two different status values. The top level status is for the indexer itself. A indexer status of **running** means the indexer is set up correctly and available to run, but not that it's currently running.
+Note there are two different status values. The top level status is for the indexer itself. An indexer status of **running** means the indexer is set up correctly and available to run, but not that it's currently running.
 
 Each run of the indexer also has its own status that indicates whether that specific execution is ongoing (**running**), or already completed with a **success**, **transientFailure**, or **persistentFailure** status. 
 
 When an indexer is reset to refresh its change tracking state, a separate execution history entry is added with a **Reset** status.
 
-For more details about status codes and indexer monitoring data, see [Get Indexer Status](/rest/api/searchservice/get-indexer-status).
+For more information about status codes and indexer monitoring data, see [Get Indexer Status](/rest/api/searchservice/get-indexer-status).
 
 ## Monitor using .NET
 
@@ -163,15 +163,15 @@ Latest run
   Document Errors: 0, Warnings: 0
 ```
 
-Note there are two different status values. The top-level status is the status of the indexer itself. A indexer status of **Running** means that the indexer is set up correctly and available for execution, but not that it is currently executing.
+Note there are two different status values. The top-level status is the status of the indexer itself. An indexer status of **Running** means that the indexer is set up correctly and available for execution, but not that it's currently executing.
 
 Each run of the indexer also has its own status for whether that specific execution is ongoing (**Running**), or was already completed with a **Success** or **TransientError** status. 
 
 When an indexer is reset to refresh its change tracking state, a separate history entry is added with a **Reset** status.
 
 ## Next steps
 
-For more details about status codes and indexer monitoring information, refer to the following API reference:
+For more information about status codes and indexer monitoring information, see the following API reference:
 
 * [GetIndexerStatus (REST API)](/rest/api/searchservice/get-indexer-status)
 * [IndexerStatus](/dotnet/api/azure.search.documents.indexes.models.indexerstatus)

articles/search/search-modeling-multitenant-saas-applications.md

@@ -74,7 +74,7 @@ Azure Cognitive Search offers a few boundaries that can be used to isolate tenan
 
 ## Modeling multitenancy with Azure Cognitive Search
 
-In the case of a multitenant scenario, the application developer consumes one or more search services and divide their tenants among services, indexes, or both. Azure Cognitive Search has a few common patterns when modeling a multitenant scenario:
+In the case of a multitenant scenario, the application developer consumes one or more search services and divides their tenants among services, indexes, or both. Azure Cognitive Search has a few common patterns when modeling a multitenant scenario:
 
 + *One index per tenant:* Each tenant has its own index within a search service that is shared with other tenants.