Merge pull request #105823 from amotley/abmotley/update_indexer_errors_title

Update Indexer Errors Title to Coincide with Message Change

Author: PRMerger9

articles/search/cognitive-search-common-errors-warnings.md

@@ -148,9 +148,9 @@ The document was read and processed, but the indexer could not add it to the sea
 
 <a name="could-not-index-document-because-the-indexer-data-to-index-was-invalid"/>
 
-## Error: Could not index document because the indexer data to index was invalid
+## Error: Could not index document because some of the document's data was not valid
 
-The document was read and processed, but due to a mismatch in the configuration of the index fields and the nature of the data extracted by the indexer, it could not be added to the search index. This can happen due to:
+The document was read and processed by the indexer, but due to a mismatch in the configuration of the index fields and the data extracted and processed by the indexer, it could not be added to the search index. This can happen due to:
 
 | Reason | Details/Example
 | --- | ---
@@ -162,12 +162,11 @@ The document was read and processed, but due to a mismatch in the configuration
 
 In all these cases, refer to [Supported Data types](https://docs.microsoft.com/rest/api/searchservice/supported-data-types) and [Data type map for indexers](https://docs.microsoft.com/rest/api/searchservice/data-type-map-for-indexers-in-azure-search) to make sure that you build the index schema correctly and have set up appropriate [indexer field mappings](search-indexer-field-mappings.md). The error message will include details that can help track down the source of the mismatch.
 
-<a name="could-not-process-document-within-indexer-max-run-time"/>
-
 ## Error: Integrated change tracking policy cannot be used because table has a composite primary key
 
 This applies to SQL tables, and usually happens when the key is either defined as a composite key or, when the table has defined a unique clustered index (as in a SQL index, not an Azure Search index). The main reason is that the key attribute is modified to be a composite primary key in the case of a [unique clustered index](https://docs.microsoft.com/sql/relational-databases/indexes/clustered-and-nonclustered-indexes-described?view=sql-server-ver15). In that case, make sure that your SQL table does not have a unique clustered index, or that you map the key field to a field that is guaranteed not to have duplicate values.
 
+<a name="could-not-process-document-within-indexer-max-run-time"/>
 
 ## Error: Could not process document within indexer max run time