summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJoe Gordon <jogo@users.noreply.github.com>2022-08-18 09:25:27 -0700
committerGitHub <noreply@github.com>2022-08-18 09:25:27 -0700
commitf34ac28f892307b3584260707d527a6c09aeb825 (patch)
treef36440a0ccc17ec77351ea8605838c2ab0bc5f1b
parent040b4ecc5d6b9d22799028e0fe8759fd7420a299 (diff)
parent70ff711656ad9640a286e3c754d73b98b5a05c37 (diff)
downloadpymemcache-f34ac28f892307b3584260707d527a6c09aeb825.tar.gz
Merge pull request #414 from 10kartik/Docs-Fix
Fixed Typos in Docs
-rw-r--r--docs/getting_started.rst16
1 files changed, 8 insertions, 8 deletions
diff --git a/docs/getting_started.rst b/docs/getting_started.rst
index a88e1be..c2f7bce 100644
--- a/docs/getting_started.rst
+++ b/docs/getting_started.rst
@@ -90,7 +90,7 @@ follows:
1. A :class:`pymemcache.client.hash.HashClient` is created with 3 nodes,
``node1``, ``node2`` and ``node3``.
-2. A number of values is set in the client using ``set`` and ``set_many``.
+2. A number of values are set in the client using ``set`` and ``set_many``.
Example:
- ``key1`` -> ``node2``
@@ -120,13 +120,13 @@ follows:
Using the built-in retrying mechanism
-------------------------------------
-The library comes with retry mechanisms that can be used to wrap all kind of
-pymemcache clients. The wrapper allow you to define the exceptions that you want
+The library comes with retry mechanisms that can be used to wrap all kinds of
+pymemcache clients. The wrapper allows you to define the exceptions that you want
to handle with retries, which exceptions to exclude, how many attempts to make
and how long to wait between attempts.
The ``RetryingClient`` wraps around any of the other included clients and will
-have the same methods. For this example we're just using the base ``Client``.
+have the same methods. For this example, we're just using the base ``Client``.
.. code-block:: python
@@ -250,7 +250,7 @@ For testing purpose pymemcache can be used in an interactive mode by using
the python interpreter or again ipython and tools like tox.
One main advantage of using `tox` to interact with `pymemcache` is that it
-comes with it's own virtual environments. It will automatically install
+comes with its own virtual environments. It will automatically install
pymemcache and fetch all the needed requirements at run. See the example below:
.. code-block::
@@ -274,8 +274,8 @@ pymemcache and fetch all the needed requirements at run. See the example below:
You can instantiate all the classes and clients offered by pymemcache.
Your client will remain open until you decide to close it or until you decide
-to quit your interpreter. It can allow you to see what's happen if your server
-is abruptly closed. Below is an by example.
+to quit your interpreter. It can allow you to see what happens if your server
+is abruptly closed. Below is an example.
Starting your server:
@@ -299,7 +299,7 @@ Restarting the server:
$ podman restart memcached
-The previous client is still opened, now try to retrieve some keys:
+The previous client is still open, now try to retrieve some keys:
.. code-block:: shell