almost

Author: georgewallace

raw-migrated-files/toc.yml

@@ -118,15 +118,13 @@ toc:
       - file: elasticsearch/elasticsearch-reference/monitor-elasticsearch-cluster.md
       - file: elasticsearch/elasticsearch-reference/monitoring-overview.md
       - file: elasticsearch/elasticsearch-reference/monitoring-production.md
-      - file: elasticsearch/elasticsearch-reference/recovery-prioritization.md
       - file: elasticsearch/elasticsearch-reference/scalability.md
       - file: elasticsearch/elasticsearch-reference/search-with-synonyms.md
       - file: elasticsearch/elasticsearch-reference/secure-cluster.md
       - file: elasticsearch/elasticsearch-reference/secure-monitoring.md
       - file: elasticsearch/elasticsearch-reference/security-files.md
       - file: elasticsearch/elasticsearch-reference/security-limitations.md
       - file: elasticsearch/elasticsearch-reference/semantic-search-inference.md
-      - file: elasticsearch/elasticsearch-reference/shard-allocation-filtering.md
       - file: elasticsearch/elasticsearch-reference/shard-request-cache.md
   - file: ingest-docs/fleet/index.md
   - file: ingest-docs/ingest-overview/index.md

troubleshoot/kibana/task-manager.md

@@ -819,7 +819,7 @@ These rough calculations give you a lower bound to the required throughput, whic
 
 Given these inferred attributes, it would be safe to assume that a single {{kib}} instance with default settings **would not** provide the required throughput. It is possible that scaling horizontally by adding a couple more {{kib}} instances will.
 
-For details on scaling Task Manager, see [Scaling guidance](../../deploy-manage/production-guidance/.md#task-manager-scaling-guidance).
+For details on scaling Task Manager, see [Scaling guidance](../../deploy-manage/production-guidance/kibana-task-manager-scaling-considerations.md#task-manager-scaling-guidance).
 
 
 ### Evaluate the Capacity Estimation [task-manager-health-evaluate-the-capacity-estimation]