Add content lists on relevant pages

docs/source/start/auth.rst

@@ -4,6 +4,12 @@ Authorization
 Once a :doc:`project is set up <../intro/setup>`, you will still have to follow a few steps before you can actually use Pyrogram to make
 API calls. This section provides all the information you need in order to authorize yourself as user or bot.
 
+.. contents:: Contents
+    :backlinks: none
+    :local:
+
+-----
+
 User Authorization
 ------------------
 

docs/source/start/errors.rst

@@ -8,6 +8,12 @@ to control the behaviour of your application. Pyrogram errors all live inside th
 
     from pyrogram import errors
 
+.. contents:: Contents
+    :backlinks: none
+    :local:
+
+-----
+
 RPCError
 --------
 
@@ -94,6 +100,6 @@ The value is stored in the ``x`` attribute of the exception object:
     from pyrogram.errors import FloodWait
 
     try:
-        ...
+        ...  # Your code
     except FloodWait as e:
         time.sleep(e.x)  # Wait "x" seconds before continuing

docs/source/start/invoking.rst

@@ -4,6 +4,12 @@ Calling Methods
 At this point, we have successfully :doc:`installed Pyrogram <../intro/install>` and :doc:`authorized <auth>` our
 account; we are now aiming towards the core of the library. It's time to start playing with the API!
 
+.. contents:: Contents
+    :backlinks: none
+    :local:
+
+-----
+
 Basic Usage
 -----------
 

docs/source/start/updates.rst

@@ -4,6 +4,12 @@ Handling Updates
 Calling :doc:`API methods <invoking>` sequentially is cool, but how to react when, for example, a new message arrives?
 This page deals with updates and how to handle such events in Pyrogram. Let's have a look at how they work.
 
+.. contents:: Contents
+    :backlinks: none
+    :local:
+
+-----
+
 Defining Updates
 ----------------