Fix some titles

marciw · marciw · commit 7459bc598d2f · 2025-02-10T09:40:48.000-05:00
diff --git a/troubleshoot/elasticsearch/add-repository.md b/troubleshoot/elasticsearch/add-repository.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Broken repositories
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/add-repository.html
 ---
 
-# Troubleshooting broken repositories [add-repository]
+# Troubleshoot broken repositories [add-repository]
 
 There are several situations where the [Health API](https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html) might report an issue regarding the integrity of snapshot repositories in the cluster. The following pages explain the recommended actions for diagnosing corrupted, unknown, and invalid repositories:
 
diff --git a/troubleshoot/elasticsearch/add-tier.md b/troubleshoot/elasticsearch/add-tier.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Add a missing tier
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/add-tier.html
 ---
diff --git a/troubleshoot/elasticsearch/allow-all-cluster-allocation.md b/troubleshoot/elasticsearch/allow-all-cluster-allocation.md
@@ -1,5 +1,6 @@
 ---
-mapped_pages:
+navigation_title: Allow data allocation
+mapped_pages: 
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/allow-all-cluster-allocation.html
 ---
 
diff --git a/troubleshoot/elasticsearch/allow-all-index-allocation.md b/troubleshoot/elasticsearch/allow-all-index-allocation.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Allow index allocation
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/allow-all-index-allocation.html
 ---
diff --git a/troubleshoot/elasticsearch/corruption-troubleshooting.md b/troubleshoot/elasticsearch/corruption-troubleshooting.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Data corruption
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/corruption-troubleshooting.html
 ---
 
-# Troubleshooting corruption [corruption-troubleshooting]
+# Troubleshoot data corruption [corruption-troubleshooting]
 
 {{es}} expects that the data it reads from disk is exactly the data it previously wrote. If it detects that the data on disk is different from what it wrote then it will report some kind of exception such as:
 
diff --git a/troubleshoot/elasticsearch/decrease-disk-usage-data-node.md b/troubleshoot/elasticsearch/decrease-disk-usage-data-node.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Decrease disk usage
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/decrease-disk-usage-data-node.html
 ---
diff --git a/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md b/troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md
@@ -3,7 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-corrupted-repositories.html
 ---
 
-# Diagnosing corrupted repositories [diagnosing-corrupted-repositories]
+# Diagnose corrupted repositories [diagnosing-corrupted-repositories]
 
 Multiple {{es}} deployments are writing to the same snapshot repository. {{es}} doesn’t support this configuration and only one cluster is allowed to write to the same repository. See [Repository contents](../../deploy-manage/tools/snapshot-and-restore.md#snapshot-repository-contents) for potential side-effects of corruption of the repository contents, which may not be resolved by the following guide. To remedy the situation mark the repository as read-only or remove it from all the other deployments, and re-add (recreate) the repository in the current deployment:
 
diff --git a/troubleshoot/elasticsearch/diagnosing-invalid-repositories.md b/troubleshoot/elasticsearch/diagnosing-invalid-repositories.md
@@ -3,7 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-invalid-repositories.html
 ---
 
-# Diagnosing invalid repositories [diagnosing-invalid-repositories]
+# Diagnose invalid repositories [diagnosing-invalid-repositories]
 
 When an {{es}} node faces an unexpected exception when trying to instantiate a snapshot repository, it will mark the repository as "invalid" and write a warning to the log file. Use the following steps to diagnose the underlying cause of this issue:
 
diff --git a/troubleshoot/elasticsearch/diagnosing-unknown-repositories.md b/troubleshoot/elasticsearch/diagnosing-unknown-repositories.md
@@ -3,7 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/diagnosing-unknown-repositories.html
 ---
 
-# Diagnosing unknown repositories [diagnosing-unknown-repositories]
+# Diagnose unknown repositories [diagnosing-unknown-repositories]
 
 When a snapshot repository is marked as "unknown", it means that an {{es}} node is unable to instantiate the repository due to an unknown repository type. This is usually caused by a missing plugin on the node. Make sure each node in the cluster has the required plugins by following the following steps:
 
diff --git a/troubleshoot/elasticsearch/discovery-troubleshooting.md b/troubleshoot/elasticsearch/discovery-troubleshooting.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Discovery
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/discovery-troubleshooting.html
 ---
 
-# Troubleshooting discovery [discovery-troubleshooting]
+# Troubleshoot discovery [discovery-troubleshooting]
 
 In most cases, the discovery and election process completes quickly, and the master node remains elected for a long period of time.
 
diff --git a/troubleshoot/elasticsearch/increase-capacity-data-node.md b/troubleshoot/elasticsearch/increase-capacity-data-node.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Increase disk capacity
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-capacity-data-node.html
 ---
diff --git a/troubleshoot/elasticsearch/increase-cluster-shard-limit.md b/troubleshoot/elasticsearch/increase-cluster-shard-limit.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Total number of shards per node reached
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-cluster-shard-limit.html
 ---
diff --git a/troubleshoot/elasticsearch/increase-shard-limit.md b/troubleshoot/elasticsearch/increase-shard-limit.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Total number of shards for an index exceeded
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/increase-shard-limit.html
 ---
diff --git a/troubleshoot/elasticsearch/monitoring-troubleshooting.md b/troubleshoot/elasticsearch/monitoring-troubleshooting.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Monitoring
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/monitoring-troubleshooting.html
 ---
 
-# Troubleshooting monitoring [monitoring-troubleshooting]
+# Troubleshoot monitoring [monitoring-troubleshooting]
 
 Use the information in this section to troubleshoot common problems and find answers for frequently asked questions. See also [Troubleshooting monitoring in {{ls}}](https://www.elastic.co/guide/en/logstash/current/monitoring-troubleshooting.html).
 
diff --git a/troubleshoot/elasticsearch/red-yellow-cluster-status.md b/troubleshoot/elasticsearch/red-yellow-cluster-status.md
@@ -1,4 +1,5 @@
 ---
+navigation_title: Red or yellow health status
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/red-yellow-cluster-status.html
 ---
diff --git a/troubleshoot/elasticsearch/repeated-snapshot-failures.md b/troubleshoot/elasticsearch/repeated-snapshot-failures.md
@@ -3,7 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/repeated-snapshot-failures.html
 ---
 
-# Addressing repeated snapshot policy failures [repeated-snapshot-failures]
+# Fix repeated snapshot policy failures [repeated-snapshot-failures]
 
 Repeated snapshot failures are usually an indicator of a problem with your deployment. Continuous failures of automated snapshots can leave a deployment without recovery options in cases of data loss or outages.
 
diff --git a/troubleshoot/elasticsearch/start-slm.md b/troubleshoot/elasticsearch/start-slm.md
@@ -3,7 +3,7 @@ mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/start-slm.html
 ---
 
-# Start Snapshot Lifecycle Management [start-slm]
+# Start snapshot lifecycle management [start-slm]
 
 Automatic snapshot lifecycle management is currently disabled. New backup snapshots will not be created automatically.
 
diff --git a/troubleshoot/elasticsearch/transform-troubleshooting.md b/troubleshoot/elasticsearch/transform-troubleshooting.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Transforms
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/transform-troubleshooting.html
 ---
 
-# Troubleshooting transforms [transform-troubleshooting]
+# Troubleshoot transforms [transform-troubleshooting]
 
 Use the information in this section to troubleshoot common problems.
 
diff --git a/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md b/troubleshoot/elasticsearch/troubleshoot-migrate-to-tiers.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Mix of data tiers and node roles
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshoot-migrate-to-tiers.html
 ---
 
-# Indices mix index allocation filters with data tiers node roles to move through data tiers [troubleshoot-migrate-to-tiers]
+# Mix of index allocation filters and data tier node roles [troubleshoot-migrate-to-tiers]
 
 Elasticsearch standardized the implementation of [hot-warm-cold architectures](https://www.elastic.co/blog/elasticsearch-data-lifecycle-management-with-data-tiers) to [data tiers](../../manage-data/lifecycle/data-tiers.md) in version 7.10. Some indices and deployments might have not fully transitioned to [data tiers](../../manage-data/lifecycle/data-tiers.md) and mix the new way of implementing the hot-warm-cold architecture with [legacy](../../deploy-manage/distributed-architecture/shard-allocation-relocation-recovery/index-level-shard-allocation.md) based node attributes.
 
diff --git a/troubleshoot/elasticsearch/troubleshooting-searches.md b/troubleshoot/elasticsearch/troubleshooting-searches.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Searches
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting-searches.html
 ---
 
-# Troubleshooting searches [troubleshooting-searches]
+# Troubleshoot searches [troubleshooting-searches]
 
 When you query your data, Elasticsearch may return an error, no search results, or results in an unexpected order. This guide describes how to troubleshoot searches.
 
diff --git a/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md b/troubleshoot/elasticsearch/troubleshooting-shards-capacity-issues.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Shard capacity issues
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting-shards-capacity-issues.html
 ---
 
-# Troubleshooting shards capacity health issues [troubleshooting-shards-capacity-issues]
+# Troubleshoot shard capacity health issues [troubleshooting-shards-capacity-issues]
 
 {{es}} limits the maximum number of shards to be held per node using the [`cluster.max_shards_per_node`](https://www.elastic.co/guide/en/elasticsearch/reference/current/misc-cluster-settings.html#cluster-max-shards-per-node) and [`cluster.max_shards_per_node.frozen`](https://www.elastic.co/guide/en/elasticsearch/reference/current/misc-cluster-settings.html#cluster-max-shards-per-node-frozen) settings. The current shards capacity of the cluster is available in the [health API shards capacity section](https://www.elastic.co/guide/en/elasticsearch/reference/current/health-api.html#health-api-response-details-shards-capacity).
 
diff --git a/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md b/troubleshoot/elasticsearch/troubleshooting-unbalanced-cluster.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Unbalanced cluster
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting-unbalanced-cluster.html
 ---
 
-# Troubleshooting an unbalanced cluster [troubleshooting-unbalanced-cluster]
+# Troubleshoot an unbalanced cluster [troubleshooting-unbalanced-cluster]
 
 Elasticsearch balances shards across data tiers to achieve a good compromise between:
 
diff --git a/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md b/troubleshoot/elasticsearch/troubleshooting-unstable-cluster.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Unstable cluster
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/troubleshooting-unstable-cluster.html
 ---
 
-# Troubleshooting an unstable cluster [troubleshooting-unstable-cluster]
+# Troubleshoot an unstable cluster [troubleshooting-unstable-cluster]
 
 Normally, a node will only leave a cluster if deliberately shut down. If a node leaves the cluster unexpectedly, it’s important to address the cause. A cluster in which nodes leave unexpectedly is unstable and can create several issues. For instance:
 
diff --git a/troubleshoot/elasticsearch/watcher-troubleshooting.md b/troubleshoot/elasticsearch/watcher-troubleshooting.md
@@ -1,9 +1,10 @@
 ---
+navigation_title: Watcher
 mapped_pages:
   - https://www.elastic.co/guide/en/elasticsearch/reference/current/watcher-troubleshooting.html
 ---
 
-# Troubleshooting Watcher [watcher-troubleshooting]
+# Troubleshoot Watcher [watcher-troubleshooting]
 
 
 ## Dynamic mapping error when trying to add a watch [_dynamic_mapping_error_when_trying_to_add_a_watch] 

Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,5 @@`
`1`	`1`	`---`
	`2`	`+navigation_title: Add a missing tier`
`2`	`3`	`mapped_pages:`
`3`	`4`	`- https://www.elastic.co/guide/en/elasticsearch/reference/current/add-tier.html`
`4`	`5`	`---`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,5 @@`
`1`	`1`	`---`
	`2`	`+navigation_title: Allow index allocation`
`2`	`3`	`mapped_pages:`
`3`	`4`	`- https://www.elastic.co/guide/en/elasticsearch/reference/current/allow-all-index-allocation.html`
`4`	`5`	`---`
Original file line number	Diff line number	Diff line change
`@@ -1,4 +1,5 @@`
`1`	`1`	`---`
	`2`	`+navigation_title: Decrease disk usage`
`2`	`3`	`mapped_pages:`
`3`	`4`	`- https://www.elastic.co/guide/en/elasticsearch/reference/current/decrease-disk-usage-data-node.html`
`4`	`5`	`---`