rewording and clarifying section

Author: thekofimensah

troubleshoot/elasticsearch/high-cpu-usage.md

@@ -103,16 +103,16 @@ For details on diagnosing and resolving these issues, refer to [](hotspotting.md
 
 ### Oversharding [high-cpu-usage-oversharding]
 
-If your Elasticsearch cluster contains a large number of shards, you might be facing an oversharding issue.
-
-Oversharding occurs when there are too many shards, causing each shard to be smaller than optimal. While Elasticsearch doesn’t have a strict minimum shard size, an excessive number of small shards can negatively impact performance. Each shard consumes cluster resources since Elasticsearch must maintain metadata and manage shard states across all nodes.
+Oversharding occurs when a cluster has too many shards, often times caused by shards being smaller than optimal. While Elasticsearch doesn’t have a strict minimum shard size, an excessive number of small shards can negatively impact performance. Each shard consumes cluster resources since Elasticsearch must maintain metadata and manage shard states across all nodes.
 
 If you have too many small shards, you can address this by doing the following:
 
 * Removing empty or unused indices.
 * Deleting or closing indices containing outdated or unnecessary data.
 * Reindexing smaller shards into fewer, larger shards to optimize cluster performance.
 
+If your shards are sized correctly but you are still experiencing oversharding, creating a more aggressive [index lifecycle management strategy](/manage-data/lifecycle/index-lifecycle-management.md) or deleting old indices can help reduce the number of shards.
+
 For more information, refer to [](/deploy-manage/production-guidance/optimize-performance/size-shards.md).
 
 ### Additional recommendations