@@ -148,7 +148,7 @@ keys and values as a dict to these commands.
148
148
ZINCRBY
149
149
^^^^^^^
150
150
151
- redis-py 2.X accidentily modified the argument order of ZINCRBY, swapping the
151
+ redis-py 2.X accidentally modified the argument order of ZINCRBY, swapping the
152
152
order of value and amount. ZINCRBY now looks like:
153
153
154
154
.. code-block :: pycon
@@ -231,7 +231,7 @@ to the official command syntax. There are a few exceptions:
231
231
<https://github.com/andymccurdy/redis-py/issues/151#issuecomment-1545015> `_
232
232
for details).
233
233
* **SCAN/SSCAN/HSCAN/ZSCAN **: The \* SCAN commands are implemented as they
234
- exist in the Redis documentation. In addition, each command has an equivilant
234
+ exist in the Redis documentation. In addition, each command has an equivalent
235
235
iterator method. These are purely for convenience so the user doesn't have
236
236
to keep track of the cursor while iterating. Use the
237
237
scan_iter/sscan_iter/hscan_iter/zscan_iter methods for this behavior.
@@ -301,7 +301,7 @@ To combat this, redis-py can issue regular health checks to assess the
301
301
liveliness of a connection just before issuing a command. Users can pass
302
302
``health_check_interval=N `` to the Redis or ConnectionPool classes or
303
303
as a query argument within a Redis URL. The value of ``health_check_interval ``
304
- must be an interger . A value of ``0 ``, the default, disables health checks.
304
+ must be an integer . A value of ``0 ``, the default, disables health checks.
305
305
Any positive integer will enable health checks. Health checks are performed
306
306
just before a command is executed if the underlying connection has been idle
307
307
for more than ``health_check_interval `` seconds. For example,
@@ -310,7 +310,7 @@ connection that has been idle for 30 or more seconds just before a command
310
310
is executed on that connection.
311
311
312
312
If your application is running in an environment that disconnects idle
313
- connections after 30 seconds you should set the ``heatlh_check_interval ``
313
+ connections after 30 seconds you should set the ``health_check_interval ``
314
314
option to a value less than 30.
315
315
316
316
This option also works on any PubSub connection that is created from a
0 commit comments