replaced redisAssert() with redisAssertWithInfo() in a shitload of places.

[redis.git] / CLUSTER

diff --git a/CLUSTER b/CLUSTER
index be903711a3a78d690dacbfbec4ebb86b1d4eaf56..f8c2daf98779a63ff342b645ea26231798879eb3 100644 (file)
--- a/CLUSTER
+++ b/CLUSTER
@@ -1,7 +1,7 @@
 CLUSTER README
 ==============
 
 CLUSTER README
 ==============
 

-Redis Cluster is currenty a work in progress, however there are a few things
+Redis Cluster is currently a work in progress, however there are a few things

 that you can do already with it to see how it works.
 
 The following guide show you how to setup a three nodes cluster and issue some
 that you can do already with it to see how it works.
 
 The following guide show you how to setup a three nodes cluster and issue some


@@ -21,7 +21,7 @@ basic command against it.
 TODO
 ====
 
 TODO
 ====
 

-*** WARNING: all the following problably has some meaning only for
+*** WARNING: all the following probably has some meaning only for

 *** me (antirez), most info are not updated, so please consider this file
 *** as a private TODO list / brainstorming.
 
 *** me (antirez), most info are not updated, so please consider this file
 *** as a private TODO list / brainstorming.
 


@@ -72,7 +72,7 @@ With -MOVED the client should update its hash slots table to reflect the fact th
        alive table if the received alive timestamp is more recent the
        one present in the node local table.
 
        alive table if the received alive timestamp is more recent the
        one present in the node local table.
 

-       In the ping packet every node "gossip" information is somethig like
+       In the ping packet every node "gossip" information is something like

        this:
 
        <ip>:<port>:<status>:<pingsent_timestamp>:<pongreceived_timestamp>
        this:
 
        <ip>:<port>:<status>:<pingsent_timestamp>:<pongreceived_timestamp>