Made changes in accord with review

Author: flang-msft

articles/azure-cache-for-redis/cache-troubleshoot-server.md

@@ -69,7 +69,7 @@ If the `used_memory_rss` value is higher than 1.5 times the `used_memory` metric
 1. Memory usage is close to the max memory limit for the cache, or
 2. `UsedMemory_RSS` is higher than the Max Memory limit, potentially resulting in page faulting in memory.
 
-If a cache is fragmented and is running under high memory pressure, the system does a failover to try recovering Resident Set Size (RSS) memory. If the system is functioning normally, that is, the replica is up and reachable, then reboot of the primary node always results in a failover to the replica. For fragmentation, after the failover is initiated and replica has promoted itself, the primary node is recycled.
+If a cache is fragmented and is running under high memory pressure, the system does a failover to try recovering Resident Set Size (RSS) memory.
 
 Redis exposes two stats, `used_memory` and `used_memory_rss`, through the [INFO](https://redis.io/commands/info) command that can help you identify this issue. You can [view these metrics](cache-how-to-monitor.md#view-metrics-with-azure-monitor-metrics-explorer) using the portal.