From 8866a749e0fa764969a088260f7c0e906ddf7e84 Mon Sep 17 00:00:00 2001 From: Dan <14043624+delivrance@users.noreply.github.com> Date: Mon, 20 May 2019 19:19:26 +0200 Subject: [PATCH] Fix spelling: an handler -> a handler Thanks @rastamanjohn for the hint --- docs/source/api/handlers.rst | 2 +- docs/source/start/updates.rst | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/source/api/handlers.rst b/docs/source/api/handlers.rst index 5f80922d..90c8e614 100644 --- a/docs/source/api/handlers.rst +++ b/docs/source/api/handlers.rst @@ -4,7 +4,7 @@ Update Handlers Handlers are used to instruct Pyrogram about which kind of updates you'd like to handle with your callback functions. For a much more convenient way of registering callback functions have a look at `Decorators `_ instead. -In case you decided to manually create an handler, use :meth:`add_handler() ` to register +In case you decided to manually create a handler, use :meth:`add_handler() ` to register it. .. code-block:: python diff --git a/docs/source/start/updates.rst b/docs/source/start/updates.rst index 644cf31c..a0f2ca0c 100644 --- a/docs/source/start/updates.rst +++ b/docs/source/start/updates.rst @@ -15,8 +15,8 @@ using `Handlers <../api/handlers>`_. Each handler deals with a specific event and once a matching update arrives from Telegram, your registered callback function will be called back by the framework and its body executed. -Registering an Handler ----------------------- +Registering a Handler +--------------------- To explain how handlers work let's have a look at the most used one, the :obj:`MessageHandler `, which will be in charge for handling :obj:`Message `