Removed legacy TOC and adjusted language

Author: thekofimensah

troubleshoot/elasticsearch.md

@@ -30,12 +30,6 @@ If you're using {{ech}}, you can use AutoOps to monitor your cluster. AutoOps si
 * [](/troubleshoot/elasticsearch/increase-cluster-shard-limit.md)
 * [](/troubleshoot/elasticsearch/corruption-troubleshooting.md)
 
-## Errors [troubleshooting-errors]
-
-* [](/troubleshoot/elasticsearch/all-shards-failed.md)
-* [](/troubleshoot/elasticsearch/failed-to-parse-field-of-type.md)
-* [](/troubleshoot/elasticsearch/unable-to-retrieve-node-fs-stats.md)
-* [](/troubleshoot/elasticsearch/unable-to-parse-response-body.md)
 
 ## Management [troubleshooting-management]
 

troubleshoot/elasticsearch/security/token-invalid-expired.md

@@ -13,11 +13,13 @@ navigation_title: "Error: Token invalid or expired"
 
 ```console
 Error: token expired
+```
 
+```console
 Error: invalid token
 ```
 
-This error occurs when {{es}} receives a request containing an invalid or expired token during authentication. It's typically caused by missing, incorrect, or outdated tokens. If an invalid or expired token is used, {{es}} rejects the request.
+These errors occur when {{es}} receives a request containing an invalid or expired token during authentication. It's typically caused by missing, incorrect, or outdated tokens. If an invalid or expired token is used, {{es}} rejects the request.
 
 ## Invalid token