summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorKristján Valur Jónsson <sweskman@gmail.com>2022-06-24 17:05:19 +0000
committermichael-grunder <michael.grunder@gmail.com>2022-06-26 14:42:08 -0700
commit1343988cee4b774d19864be9c9134fbaf6daf09b (patch)
treeb44081bf58b9c4662060d3d0cc0e384ca684108b /README.md
parent47b57aa243120c9678bb1a01d6a9a3da70894d6f (diff)
Fix typos
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/README.md b/README.md
index a99776c..c0cd902 100644
--- a/README.md
+++ b/README.md
@@ -356,7 +356,7 @@ have the following prototype:
void(const redisAsyncContext *c, int status);
```
-On a *connect*, the `status` argument is set to `REDIS_OK` if the connection attempted. In this
+On a *connect*, the `status` argument is set to `REDIS_OK` if the connection attempt succeeded. In this
case, the context is ready to accept commands. If it is called with `REDIS_ERR` then the
connection attempt failed. The `err` field in the context can be accessed to find out the cause of the error.
After a failed connection attempt, the context object is automatically freed by the libary after calling
@@ -375,7 +375,7 @@ api will return `REDIS_ERR`. The function to set the callbacks have the followin
int redisAsyncSetConnectCallback(redisAsyncContext *ac, redisConnectCallback *fn);
int redisAsyncSetDisconnectCallback(redisAsyncContext *ac, redisDisconnectCallback *fn);
```
-`ac->data` may be used to pass user data to both of these this callbacks. An typical implementation
+`ac->data` may be used to pass user data to both of thes callbacks. An typical implementation
might look something like this:
```c
void appOnConnect(redisAsyncContext *c, int status)