aboutsummaryrefslogtreecommitdiff
path: root/docs/faq.rst
diff options
context:
space:
mode:
authorRapptz <[email protected]>2016-06-07 20:39:15 -0400
committerRapptz <[email protected]>2016-06-07 20:39:15 -0400
commita0966f59d2315a72a21fce0138d53c3596713a59 (patch)
treede6e56330907d2a5d8ce8dcc1550106c872a61ec /docs/faq.rst
parentAdd FAQ section to the documentation. (diff)
downloaddiscord.py-a0966f59d2315a72a21fce0138d53c3596713a59.tar.xz
discord.py-a0966f59d2315a72a21fce0138d53c3596713a59.zip
Fix some typos in the FAQ page.
Diffstat (limited to 'docs/faq.rst')
-rw-r--r--docs/faq.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/docs/faq.rst b/docs/faq.rst
index ac47564e..94d75b48 100644
--- a/docs/faq.rst
+++ b/docs/faq.rst
@@ -55,7 +55,7 @@ What does "blocking" mean?
~~~~~~~~~~~~~~~~~~~~~~~~~~
In asynchronous programming a blocking call is essentially all the parts of the function that are not ``await``. Do not
-despair however, because not all forms of blocking are bad! Avoiding blocking calls is inevitable, but you must work to make
+despair however, because not all forms of blocking are bad! Using blocking calls is inevitable, but you must work to make
sure that you don't excessively block functions. Remember, if you block for too long then your bot will freeze since it has
not stopped the function's execution at that point to do other things.
@@ -179,7 +179,7 @@ one of the following functions:
- :meth:`Server.get_member`
- :meth:`Server.get_channel`
-If the functions above do not help you, then use of :func:`utils.find` or :func:`utils.get` would server some use in finding
+If the functions above do not help you, then use of :func:`utils.find` or :func:`utils.get` would serve some use in finding
specific entities. The documentation for those functions provide specific examples.
Commands Extension