modules: readme files regenerated - ndb_redis ... [skip ci]

src/modules/ndb_redis/README

@@ -51,7 +51,7 @@ Carsten Bock
 
               4.1. redis_cmd(srvname, command, ..., replyid)
               4.2. redis_pipe_cmd(srvname, command, ..., replyid)
-              4.3. redis_execute([srvname])
+              4.3. redis_execute(srvname)
               4.4. redis_free(replyid)
 
    List of Examples
@@ -87,7 +87,7 @@ Chapter 1. Admin Guide
 
         4.1. redis_cmd(srvname, command, ..., replyid)
         4.2. redis_pipe_cmd(srvname, command, ..., replyid)
-        4.3. redis_execute([srvname])
+        4.3. redis_execute(srvname)
         4.4. redis_free(replyid)
 
 1. Overview
@@ -215,7 +215,7 @@ modparam("ndb_redis", "cluster", 1)
 
    4.1. redis_cmd(srvname, command, ..., replyid)
    4.2. redis_pipe_cmd(srvname, command, ..., replyid)
-   4.3. redis_execute([srvname])
+   4.3. redis_execute(srvname)
    4.4. redis_free(replyid)
 
 4.1.  redis_cmd(srvname, command, ..., replyid)
@@ -293,17 +293,13 @@ if(redis_cmd("srvN", "HMGET foo_key field1 field3", "r")) {
    If cluster parameter is set to 1, this function will log an error and
    do nothing.
 
-4.3.  redis_execute([srvname])
+4.3.  redis_execute(srvname)
 
    Sends commands to REDIS server identified by srvname. Commands are
    added with redis_pipe_cmd function, and will be stored for an existing
    REDIS server. When this function is called all the commands will be
    sent in a single message to the REDIS server.
 
-   If this function is called without any parameters, it will iterate
-   through all existing servers and send the existing pipelined commands
-   for them.
-
    When using redis_cmd together with redis_pipe_cmd it is recommended
    that a call to redis_execute is made before calling redis_cmd in case
    there are pipelined commands, otherwise when calling redis_cmd, if
@@ -321,14 +317,14 @@ After several redis command calls:
 
         redis_pipe_cmd("srvB", "SET ruri $ru", "r2");
 
-        redis_pipe_cmd("srvC", "GET foo", "r3");
+        redis_pipe_cmd("srvB", "GET foo", "r3");
 
 Send the data and retrieve the results:
         redis_execute("srvA"); //send command to srvA and wait for reply. Store
 the reply in r1
 
-        redis_execute(); //send remaining commands (the set to srvB and get to s
-rvC), wait for replies, and store the replies in r2 and r3
+        redis_execute("srvB"); //send command to srvA and wait for reply. Store
+the replies in r2 (for SET ruri $ru) and r3 (for GET foo)
 
 Using both redis_cmd and redis_pipe_cmd:
         redis_pipe_cmd("srvA", "SET foo bar", "r1");