Fix link

Author: Arvind Krishnaa Jagannathan

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

@@ -114,7 +114,7 @@ The document was read and processed, but the indexer could not add it to the sea
 | --- | --- | --- |
 | A field contains a term that is too large | A term in your document is larger than the [32 KB limit](search-limits-quotas-capacity.md#api-request-limits) | You can avoid this restriction by ensuring the field is not configured as filterable, facetable, or sortable.
 | Document is too large to be indexed | A document is larger than the [maximum api request size](search-limits-quotas-capacity.md#api-request-limits) | [How to index large data sets](search-howto-large-index.md)
-| Failed to establish connection to update index. Search service is under heavy load. | Trouble connecting to the target index (that persists after retries) because the service is under other load, such as querying or indexing. | [Scale up your search service](search-capacity-planning)
+| Failed to establish connection to update index. Search service is under heavy load. | Trouble connecting to the target index (that persists after retries) because the service is under other load, such as querying or indexing. | [Scale up your search service](search-capacity-planning.md)
 | Failed to establish connection to update index. Search service is currently down/Search service is undergoing a transition. | Search service is being patched for service update, or is in the middle of a topology reconfiguration. | Configure service with at least 3 replicas for 99.9% availability per [SLA documentation](https://azure.microsoft.com/support/legal/sla/search/v1_0/)
 | Failed to establish connection to update index. An unknown failure occurred. | Failure in the underlying compute/networking resource (rare) | Configure indexers to [run on a schedule](search-howto-schedule-indexers.md) to pick up from a failed state.