Clarify some aspects of the documentation

readthedocs/quick-references/events-reference.rst

@@ -10,34 +10,15 @@ You can access the client that creates this event by doing
 events to find out what arguments it allows on creation and
 its **attributes** (the properties will be shown here).
 
-It is important to remember that **all events subclass**
-`ChatGetter <telethon.tl.custom.chatgetter.ChatGetter>`!
+.. important::
+
+    Remember that **all events base** `ChatGetter
+    <telethon.tl.custom.chatgetter.ChatGetter>`! Please see :ref:`faq`
+    if you don't know what this means or the implications of it.
 
 .. contents::
 
 
-ChatGetter
-==========
-
-All events subclass `ChatGetter <telethon.tl.custom.chatgetter.ChatGetter>`,
-which means all events have (and you can access to):
-
-.. currentmodule:: telethon.tl.custom.chatgetter.ChatGetter
-
-.. autosummary::
-    :nosignatures:
-
-    chat
-    input_chat
-    chat_id
-    is_private
-    is_group
-    is_channel
-
-    get_chat
-    get_input_chat
-
-
 CallbackQuery
 =============
 

readthedocs/quick-references/faq.rst

@@ -1,3 +1,5 @@
+.. _faq:
+
 ===
 FAQ
 ===
@@ -177,6 +179,32 @@ won't do unnecessary work unless you need to:
         sender = await event.get_sender()
 
 
+What does "bases ChatGetter" mean?
+==================================
+
+In Python, classes can base others. This is called `inheritance
+<https://ddg.gg/python%20inheritance>`_. What it means is that
+"if a class bases another, you can use the other's methods too".
+
+For example, `Message <telethon.tl.custom.message.Message>` *bases*
+`ChatGetter <telethon.tl.custom.chatgetter.ChatGetter>`. In turn,
+`ChatGetter <telethon.tl.custom.chatgetter.ChatGetter>` defines
+things like `obj.chat_id <telethon.tl.custom.chatgetter.ChatGetter>`.
+
+So if you have a message, you can access that too:
+
+.. code-block:: python
+
+    # ChatGetter has a chat_id property, and Message bases ChatGetter.
+    # Thus you can use ChatGetter properties and methods from Message
+    print(message.chat_id)
+
+
+Telegram has a lot to offer, and inheritance helps the library reduce
+boilerplate, so it's important to know this concept. For newcomers,
+this may be a problem, so we explain what it means here in the FAQ.
+
+
 Can I use Flask with the library?
 =================================
 

readthedocs/quick-references/objects-reference.rst

@@ -13,6 +13,48 @@ to find out about the attributes.
 .. contents::
 
 
+ChatGetter
+==========
+
+All events base `ChatGetter <telethon.tl.custom.chatgetter.ChatGetter>`,
+and some of the objects below do too, so it's important to know its methods.
+
+.. currentmodule:: telethon.tl.custom.chatgetter.ChatGetter
+
+.. autosummary::
+    :nosignatures:
+
+    chat
+    input_chat
+    chat_id
+    is_private
+    is_group
+    is_channel
+
+    get_chat
+    get_input_chat
+
+
+SenderGetter
+============
+
+Similar to `ChatGetter <telethon.tl.custom.chatgetter.ChatGetter>`, a
+`SenderGetter <telethon.tl.custom.sendergetter.SenderGetter>` is the same,
+but it works for senders instead.
+
+.. currentmodule:: telethon.tl.custom.sendergetter.SenderGetter
+
+.. autosummary::
+    :nosignatures:
+
+    sender
+    input_sender
+    sender_id
+
+    get_sender
+    get_input_sender
+
+
 Message
 =======
 
@@ -22,6 +64,9 @@ The `Message` type is very important, mostly because we are working
 with a library for a *messaging* platform, so messages are widely used:
 in events, when fetching history, replies, etc.
 
+It bases `ChatGetter <telethon.tl.custom.chatgetter.ChatGetter>` and
+`SenderGetter <telethon.tl.custom.sendergetter.SenderGetter>`.
+
 Properties
 ----------
 
@@ -115,6 +160,8 @@ is returned by the `client.conversation()
 <telethon.client.dialogs.DialogMethods.conversation>` method to easily
 send and receive responses like a normal conversation.
 
+It bases `ChatGetter <telethon.tl.custom.chatgetter.ChatGetter>`.
+
 .. currentmodule:: telethon.tl.custom.conversation.Conversation
 
 .. autosummary::