cleanup pt 1

[shainaraskas]

Summary

Fixes applies information on several troubleshooting pages. Did the following additional labor:

• Restructured some tabbed content: some ECH/self tab splits were actually Kibana/ES API splits. Others were ECE+ECH/ECK+self splits
• Added some hints around applicability for "shoulder" docs (e.g. discovery is much more automated in ECE/ECH/ECK, but the docs are still helpful
• Fixed some linting stuff

Applicability was determined based on supporting documentation (e.g. availability of snapshot/restore plugins) and accessibility of the troubleshooting paths provided. Will get a double-check probably from Edu on my gut feelings

Generative AI disclosure

1. Did you use a generative AI (GenAI) tool to assist in creating this contribution?

• Yes
• No

Confirmed assumptions about troubleshooting applicability with chatgpt

[github-actions]

Vale Linting Results

Summary: 16 suggestions found

💡 Suggestions (16)

File	Line	Rule	Message
troubleshoot/elasticsearch/decrease-disk-usage-data-node.md	24	Elastic.Versions	Use 'and later' instead of 'and higher' when referring to versions.
troubleshoot/elasticsearch/decrease-disk-usage-data-node.md	41	Elastic.Wordiness	Consider using 'to' instead of 'In order to'.
troubleshoot/elasticsearch/decrease-disk-usage-data-node.md	85	Elastic.FutureTense	'won't go' might be in future tense. Write in the present tense to describe the state of the product as it is now.
troubleshoot/elasticsearch/diagnose-unassigned-shards.md	20	Elastic.Wordiness	Consider using 'to' instead of 'In order to'.
troubleshoot/elasticsearch/diagnose-unassigned-shards.md	133	Elastic.WordChoice	Consider using 'cannot' instead of 'unable', unless the term is in the UI.
troubleshoot/elasticsearch/diagnosing-corrupted-repositories.md	15	Elastic.FutureTense	'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now.
troubleshoot/elasticsearch/discovery-troubleshooting.md	13	Elastic.Wordiness	Consider using 'usually' instead of 'In most cases'.
troubleshoot/elasticsearch/discovery-troubleshooting.md	15	Elastic.FutureTense	'won't work' might be in future tense. Write in the present tense to describe the state of the product as it is now.
troubleshoot/elasticsearch/discovery-troubleshooting.md	17	Elastic.WordChoice	Consider using 'cannot' instead of 'unable', unless the term is in the UI.
troubleshoot/elasticsearch/discovery-troubleshooting.md	19	Elastic.WordChoice	Consider using 'cannot' instead of 'unable', unless the term is in the UI.
troubleshoot/elasticsearch/discovery-troubleshooting.md	42	Elastic.FutureTense	'will also' might be in future tense. Write in the present tense to describe the state of the product as it is now.
troubleshoot/elasticsearch/discovery-troubleshooting.md	69	Elastic.FutureTense	'will be' might be in future tense. Write in the present tense to describe the state of the product as it is now.
troubleshoot/elasticsearch/discovery-troubleshooting.md	69	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'See', unless the term is in the UI.
troubleshoot/elasticsearch/discovery-troubleshooting.md	78	Elastic.WordChoice	Consider using 'refer to (if it's a document), view (if it's a UI element)' instead of 'see', unless the term is in the UI.
troubleshoot/elasticsearch/fix-watermark-errors.md	102	Elastic.Wordiness	Consider using 'to' instead of 'in order to'.
troubleshoot/elasticsearch/fix-watermark-errors.md	102	Elastic.FutureTense	'will block' might be in future tense. Write in the present tense to describe the state of the product as it is now.