aboutsummaryrefslogtreecommitdiff
path: root/docs
diff options
context:
space:
mode:
authorNCPlayz <[email protected]>2019-03-16 21:43:55 +0000
committerRapptz <[email protected]>2019-03-19 08:24:42 -0400
commitfb02191b80972a9cf7c3baa765cb3aa84c6f1cfa (patch)
tree7a0a5c9aaa5cc5bac26fc51caf4fdffbaee64c26 /docs
parentTake back ownership of files from aiohttp for retrying requests. (diff)
downloaddiscord.py-fb02191b80972a9cf7c3baa765cb3aa84c6f1cfa.tar.xz
discord.py-fb02191b80972a9cf7c3baa765cb3aa84c6f1cfa.zip
Organise documentation
Diffstat (limited to 'docs')
-rw-r--r--docs/api.rst10
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/api.rst b/docs/api.rst
index db7b8d96..8230cef2 100644
--- a/docs/api.rst
+++ b/docs/api.rst
@@ -140,12 +140,12 @@ to handle it, which defaults to print a traceback and ignoring the exception.
printed to stderr and the exception is ignored. If you want to
change this behaviour and handle the exception for whatever reason
yourself, this event can be overridden. Which, when done, will
- supress the default action of printing the traceback.
+ suppress the default action of printing the traceback.
- The information of the exception rasied and the exception itself can
- be retreived with a standard call to ``sys.exc_info()``.
+ The information of the exception raised and the exception itself can
+ be retrieved with a standard call to ``sys.exc_info()``.
- If you want exception to propogate out of the :class:`Client` class
+ If you want exception to propagate out of the :class:`Client` class
you can define an ``on_error`` handler consisting of a single empty
``raise`` statement. Exceptions raised by ``on_error`` will not be
handled in any way by :class:`Client`.
@@ -154,7 +154,7 @@ to handle it, which defaults to print a traceback and ignoring the exception.
:param args: The positional arguments for the event that raised the
exception.
:param kwargs: The keyword arguments for the event that raised the
- execption.
+ exception.
.. function:: on_socket_raw_receive(msg)