README.md in redis_failover-0.1.1 vs README.md in redis_failover-0.2.0

@@ -1,6 +1,6 @@
-# Redis Failover Client/Server
+# Automatic Redis Failover Client/Server
 
 Redis Failover attempts to provides a full automatic master/slave failover solution for Ruby. Redis does not provide
 an automatic failover capability when configured for master/slave replication. When the master node dies,
 a new master must be manually brought online and assigned as the slave's new master. This manual
 switch-over is not desirable in high traffic sites where Redis is a critical part of the overall
@@ -16,10 +16,12 @@
 All existing slaves will be automatically reconfigured to point to the new master for replication.
 All nodes marked as unreachable will be periodically checked to see if they have been brought back online.
 If so, the newly reachable nodes will be configured as slaves and brought back into the list of live
 servers. Note that detection of a node going down should be nearly instantaneous, since the mechanism
 used to keep tabs on a node is via a blocking Redis BLPOP call (no polling). This call fails nearly
-immediately when the node actually goes offline.
+immediately when the node actually goes offline. To avoid false positives (i.e., intermittent flaky
+network interruption), the server will only mark a node as unreachable if it fails to communicate with
+it 3 times (this is configurable via --max-failures, see configuration options below).
 
 This gem provides a RedisFailover::Client wrapper that is master/slave aware. The client is configured
 with a single host/port pair that points to redis failover server. The client will automatically
 connect to the server to find out the current state of the world (i.e., who's the current master and
 who are the current slaves). The client also acts as a load balancer in that it will automatically