change t.me/Pyrogram links to point to our fork, in some of the places

Author: SpEcHiDe

.github/ISSUE_TEMPLATE/config.yml

@@ -4,5 +4,5 @@ contact_links:
     url: https://stackoverflow.com/questions/tagged/pyrogram
     about: This place is only for reporting issues about Pyrogram. You can ask questions on StackOverflow.
   - name: Join the Telegram channel
-    url: https://t.me/PyroTGFork
+    url: https://PyroTGFork.t.me/2
     about: Join the official channel and stay tuned for news, updates and announcements.

README.md

@@ -13,7 +13,7 @@
         Releases
     </a>
     •
-    <a href="https://t.me/PyroTGFork">
+    <a href="https://PyroTGFork.t.me/2">
         News
     </a>
 </p>
@@ -60,4 +60,4 @@ pip3 install pyrotgfork
 
 - Check out [the docs](https://telegramplayground.github.io/pyrogram) to learn more about Pyrogram, get started right
 away and discover more in-depth material for building your client applications.
-- Join the official channel at [PyroTGFork](https://t.me/PyroTGFork) and stay tuned for news, updates and announcements.
+- Join the official channel at [PyroTGFork](https://PyroTGFork.t.me/2) and stay tuned for news, updates and announcements.

docs/source/index.rst

@@ -1,5 +1,5 @@
-Welcome to ``PyroTGFork``
-==========================
+Welcome to PyroTGFork Pyrogram Fork
+=====================================
 
 .. admonition :: A Word of Warning
     :class: tip
@@ -34,7 +34,7 @@ Welcome to ``PyroTGFork``
             Releases
         </a>
         •
-        <a href="https://t.me/pyrogram">
+        <a href="https://PyroTGFork.t.me/2">
             News
         </a>
     </p>
@@ -64,11 +64,8 @@ It enables you to easily interact with the main Telegram API through a user acco
 Support
 -------
 
-If you'd like to support Pyrogram, you can consider:
+If you'd like to support this fork, you can consider reading `this message <https://PyroTGFork.t.me/2>`__.
 
-- `Become a GitHub sponsor <https://github.com/sponsors/delivrance>`_.
-- `Become a LiberaPay patron <https://liberapay.com/delivrance>`_.
-- `Become an OpenCollective backer <https://opencollective.com/pyrogram>`_.
 
 How the Documentation is Organized
 ----------------------------------
@@ -111,7 +108,7 @@ Meta
 
     - :doc:`Pyrogram FAQ <faq/index>`: Answers to common Pyrogram questions.
     - :doc:`Support Pyrogram <support>`: Ways to show your appreciation.
-    - :doc:`Release Notes <releases/index>`: Changes in this Fork.
+    - :doc:`Release Notes <releases/changes-in-this-fork>`: Changes in this Fork.
 
 .. toctree::
     :hidden:
@@ -173,15 +170,20 @@ Meta
     :caption: Meta
 
     faq/index
-    support
     releases/index
 
 .. toctree::
     :hidden:
     :caption: Telegram Raw API
 
-    TL Schema Explorer <https://telegramplayground.github.io/schema.tl/>
-    TL Diff <https://telegramplayground.github.io/TG-APIs/TL/diff/tdesktop.html>
     telegram/functions/index
     telegram/types/index
     telegram/base/index
+
+.. toctree::
+    :hidden:
+    :caption: External Links
+
+    version
+    TL Schema Explorer <https://telegramplayground.github.io/schema.tl/>
+    TL Diff <https://telegramplayground.github.io/TG-APIs/TL/diff/tdesktop.html>

docs/source/intro/quickstart.rst

@@ -57,4 +57,4 @@ we have just done above.
 If you are feeling eager to continue you can take a shortcut to :doc:`../start/invoking` and come back
 later to learn some more details.
 
-.. _community: https://t.me/Pyrogram
+.. _community: https://PyroTGFork.t.me/2

docs/source/releases/changes-in-this-fork.rst

@@ -7,7 +7,7 @@ in reverse chronological order. You should read this when upgrading
 to this fork to know where your code can break, and where
 it can take advantage of new goodies!
 
-`For a more detailed description, please check the commits. <https://github.com/TelegramPlayGround/pyrogram/commits/unknown_errors/>`_
+`For a more detailed description, please check the commits. <https://github.com/TelegramPlayGround/pyrogram/commits/dev/>`_
 
 If you found any issue or have any suggestions, feel free to make `an issue <https://github.com/TelegramPlayGround/pyrogram/issues>`_ on github.
 
@@ -26,7 +26,7 @@ Changes in this Fork
 | Scheme layer used: 198 |
 +------------------------+
 
-- Updated :doc:`Message Identifiers <../../topics/text-formatting>`.
+- Updated :doc:`Text Formatting <../../topics/text-formatting>` documentation.
 - Added ``message.content`` property.
 - Added the parameter ``pinned`` and made the parameter ``chat_id`` optional in :meth:`~pyrogram.Client.get_messages`. **NOTE**: Please be aware about using the correct :doc:`Message Identifiers <../../topics/message-identifiers>`, when using this method.
 - Added the ``cover`` and ``start_timestamp`` parameters in :meth:`~pyrogram.Client.send_video` and :obj:`~pyrogram.types.InputPaidMediaVideo`.

docs/source/topics/advanced-usage.rst

@@ -117,4 +117,4 @@ For example, given the ID *123456789*, here's how Pyrogram can tell entities apa
 So, every time you take a raw ID, make sure to translate it into the correct ID when you want to use it with an
 high-level method.
 
-.. _Community: https://t.me/Pyrogram
+.. _Community: https://PyroTGFork.t.me/2

pyproject.toml

@@ -41,7 +41,7 @@ path = "pyrogram/__init__.py"
 [project.urls]
 Homepage = "https://telegramplayground.github.io/pyrogram/"
 Tracker = "https://github.com/TelegramPlayGround/Pyrogram/issues"
-community = "https://t.me/PyroTGFork"
+community = "https://PyroTGFork.t.me/2"
 Source = "https://github.com/TelegramPlayGround/Pyrogram"
 Documentation = "https://telegramplayground.github.io/pyrogram/releases/changes-in-this-fork.html"