Update _tuning-your-cluster/index.md

Co-authored-by: Nathan Bower <[email protected]>
Signed-off-by: Naarcha-AWS <[email protected]>

_tuning-your-cluster/index.md

@@ -200,7 +200,7 @@ You can set custom node attributes on OpenSearch nodes to be used for shard allo
 
 Shard allocation awareness attempts to separate primary and replica shards across multiple zones, because two shard copies can not be placed on the same node. When only one zone is available, such as after a zone failure, OpenSearch allocates replica shards to the only remaining zone. For example, if your index has a total 5 shard copies (1 primary and 4 replicas) and nodes in 3 distinct zones, then OpenSearch will perform the following to allocate all 5 shard copies: 
 
-- Allocate less than 2 shards per zone, which means you'll need at least 2 nodes in 2 zones.
+- Allocate fewer than 2 shards per zone, which will require at least 2 nodes in 2 zones.
 - Allocate the last shard in the third zone, with at least 1 node needed in the third zone.
 
 Alternatively, if you have 3 nodes in the first zone and 1 node in each remaining zone, then OpenSearch will allocate: