Skip to content

Commit 29a5259

Browse files
shassardandymccurdy
authored andcommitted
spelling fixes (redis#1218)
1 parent d811ae7 commit 29a5259

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

README.rst

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -148,7 +148,7 @@ keys and values as a dict to these commands.
148148
ZINCRBY
149149
^^^^^^^
150150

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
152152
order of value and amount. ZINCRBY now looks like:
153153

154154
.. code-block:: pycon
@@ -231,7 +231,7 @@ to the official command syntax. There are a few exceptions:
231231
<https://github.com/andymccurdy/redis-py/issues/151#issuecomment-1545015>`_
232232
for details).
233233
* **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
235235
iterator method. These are purely for convenience so the user doesn't have
236236
to keep track of the cursor while iterating. Use the
237237
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
301301
liveliness of a connection just before issuing a command. Users can pass
302302
``health_check_interval=N`` to the Redis or ConnectionPool classes or
303303
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.
305305
Any positive integer will enable health checks. Health checks are performed
306306
just before a command is executed if the underlying connection has been idle
307307
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
310310
is executed on that connection.
311311

312312
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``
314314
option to a value less than 30.
315315

316316
This option also works on any PubSub connection that is created from a

0 commit comments

Comments
 (0)