From b4467e82af1df67a025732a6b6c7f05a16d7ce9a Mon Sep 17 00:00:00 2001
From: Dan <14043624+delivrance@users.noreply.github.com>
Date: Mon, 25 May 2020 14:31:31 +0200
Subject: [PATCH] Update Bot API diagram in docs

---
 docs/source/faq.rst                      | 2 +-
 docs/source/topics/mtproto-vs-botapi.rst | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/source/faq.rst b/docs/source/faq.rst
index b064e10b..e56736d8 100644
--- a/docs/source/faq.rst
+++ b/docs/source/faq.rst
@@ -85,7 +85,7 @@ Requests against the official bot API endpoint are made via JSON/HTTP, but are h
 application that implements the MTProto protocol -- just like Pyrogram -- and uses its own API key, which is always
 required, but hidden to the public.
 
-.. figure:: https://i.imgur.com/C108qkX.png
+.. figure:: https://i.imgur.com/WvwBoZo.png
     :align: center
 
 Using MTProto is the only way to communicate with the actual Telegram servers, and the main API requires developers to
diff --git a/docs/source/topics/mtproto-vs-botapi.rst b/docs/source/topics/mtproto-vs-botapi.rst
index 3668d0da..12b73b53 100644
--- a/docs/source/topics/mtproto-vs-botapi.rst
+++ b/docs/source/topics/mtproto-vs-botapi.rst
@@ -35,7 +35,7 @@ accounts that are authorized via tokens instead of phone numbers. The Bot API is
 Telegram API, but runs on an intermediate server application that in turn communicates with the actual Telegram servers
 using MTProto.
 
-.. figure:: https://i.imgur.com/C108qkX.png
+.. figure:: https://i.imgur.com/WvwBoZo.png
     :align: center
 
 .. _Bot API: https://core.telegram.org/bots/api