Refined from engineering feedback

Author: flang-msft

articles/azure-cache-for-redis/cache-how-to-scale.md

@@ -369,9 +369,9 @@ Scaling time depends on a few factors. Here are some factors that can affect how
 - High write requests: Higher number of writes mean more data replicates across nodes or shards
 - High server load: Higher server load means the Redis server is busy and limited CPU cycles are available to complete data redistribution
 
-Scaling a cache is non-trivial action and can take a long time. It is hard to estimate the time to scale.
+Scaling a cache is non-trivial action and can take a long time.
 
-Based on real world examples, the time to scale cache with one to two shards can be 1 to 2 hours when the cache is not under heavy loads. However, if you have more shards, time-to-scale does not increase in a linear fashion.
+Based on real world examples, the time to scale cache with one to two shards can be 1 to 2 hours when the cache is not under heavy loads.If you have more shards, the time to scale doesn't increase in a linear way.
 
 ### How can I tell when scaling is complete?