Skip to content

Commit b4467e8

Browse files
committed
Update Bot API diagram in docs
1 parent e30b9c5 commit b4467e8

File tree

2 files changed

+2
-2
lines changed

2 files changed

+2
-2
lines changed

docs/source/faq.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ Requests against the official bot API endpoint are made via JSON/HTTP, but are h
8585
application that implements the MTProto protocol -- just like Pyrogram -- and uses its own API key, which is always
8686
required, but hidden to the public.
8787

88-
.. figure:: https://i.imgur.com/C108qkX.png
88+
.. figure:: https://i.imgur.com/WvwBoZo.png
8989
:align: center
9090

9191
Using MTProto is the only way to communicate with the actual Telegram servers, and the main API requires developers to

docs/source/topics/mtproto-vs-botapi.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -35,7 +35,7 @@ accounts that are authorized via tokens instead of phone numbers. The Bot API is
3535
Telegram API, but runs on an intermediate server application that in turn communicates with the actual Telegram servers
3636
using MTProto.
3737

38-
.. figure:: https://i.imgur.com/C108qkX.png
38+
.. figure:: https://i.imgur.com/WvwBoZo.png
3939
:align: center
4040

4141
.. _Bot API: https://core.telegram.org/bots/api

0 commit comments

Comments
 (0)