summaryrefslogtreecommitdiff
path: root/deps/hiredis/README.md
diff options
context:
space:
mode:
Diffstat (limited to 'deps/hiredis/README.md')
-rw-r--r--deps/hiredis/README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/deps/hiredis/README.md b/deps/hiredis/README.md
index e39ff0c1b..5a77cd381 100644
--- a/deps/hiredis/README.md
+++ b/deps/hiredis/README.md
@@ -108,7 +108,7 @@ was received:
* **`REDIS_REPLY_ARRAY`**:
* A multi bulk reply. The number of elements in the multi bulk reply is stored in
`reply->elements`. Every element in the multi bulk reply is a `redisReply` object as well
- and can be accessed via `reply->elements[..index..]`.
+ and can be accessed via `reply->element[..index..]`.
Redis may reply with nested arrays but this is fully supported.
Replies should be freed using the `freeReplyObject()` function.
@@ -171,7 +171,7 @@ the latter means an error occurred while reading a reply. Just as with the other
the `err` field in the context can be used to find out what the cause of this error is.
The following examples shows a simple pipeline (resulting in only a single call to `write(2)` and
-a single call to `write(2)`):
+a single call to `read(2)`):
redisReply *reply;
redisAppendCommand(context,"SET foo bar");