diff --git a/data/core.telegram.org/bots/api.html b/data/core.telegram.org/bots/api.html
index 05433e128a..099d575d05 100644
--- a/data/core.telegram.org/bots/api.html
+++ b/data/core.telegram.org/bots/api.html
@@ -114,18 +114,6 @@ To learn how to create…">
 <p><strong><img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /> WARNING! <img class="emoji" src="//telegram.org/img/emoji/40/E29AA0.png" width="20" height="20" alt="⚠️" /></strong><br>User identifiers can now be bigger than <code>2^31 - 1</code> and it is no longer possible to store them in a signed 32-bit integer type. User identifiers have up to 52 significant bits, so a 64-bit integer or double-precision float type is safe for storing them. Please make sure that your code can correctly handle such user identifiers.</p>
 </blockquote>
 <hr>
-<h4><a class="anchor" name="april-26-2021" href="#april-26-2021"><i class="anchor-icon"></i></a>April 26, 2021</h4>
-<p><strong>Bot API 5.2</strong></p>
-<ul>
-<li>Support for <a href="https://telegram.org/blog/payments-2-0-scheduled-voice-chats">Payments 2.0</a>, see <a href="https://core.telegram.org/bots/payments">this manual</a> for more details about the <strong>Bot Payments API</strong>.</li>
-<li>Added the type <a href="#inputinvoicemessagecontent">InputInvoiceMessageContent</a> to support sending invoices as inline query results.</li>
-<li>Allowed sending invoices to group, supergroup and channel chats.</li>
-<li>Added the fields <em>max_tip_amount</em> and <em>suggested_tip_amounts</em> to the method <a href="#sendinvoice">sendInvoice</a> to allow adding optional tips to the payment.</li>
-<li>The parameter <em>start_parameter</em> of the method <a href="#sendinvoice">sendInvoice</a> became optional. If the parameter isn&#39;t specified, the invoice can be paid directly from forwarded messages.</li>
-<li>Added the field <em>chat_type</em> to the class <a href="#inlinequery">InlineQuery</a>, containing the type of the chat, from which the inline request was sent.</li>
-<li>Added the type <a href="#voicechatscheduled">VoiceChatScheduled</a> and the field <em>voice_chat_scheduled</em> to the class <a href="#message">Message</a>.</li>
-<li>Fixed an error in <a href="#sendchataction">sendChatAction</a> documentation to correctly mention “record_voice” and “upload_voice” instead of “record_audio” and “upload_audio” for related to voice note actions. Old action names will still work for backward compatibility.</li>
-</ul>
 <p><strong><a href="/bots/api-changelog">See earlier changes »</a></strong></p>
 <h3><a class="anchor" name="authorizing-your-bot" href="#authorizing-your-bot"><i class="anchor-icon"></i></a>Authorizing your bot</h3>
 <p>Each bot is given a unique authentication token <a href="/bots#6-botfather">when it is created</a>. The token looks something like <code>123456:ABC-DEF1234ghIkl-zyx57W2v1u123ew11</code>, but we&#39;ll use simply <strong>&lt;token&gt;</strong> in this document instead. You can learn about obtaining tokens and generating new ones in <a href="https://core.telegram.org/bots#6-botfather">this document</a>.</p>
@@ -3174,7 +3162,7 @@ To learn how to create…">
 <td>protect_content</td>
 <td>Boolean</td>
 <td>Optional</td>
-<td>Protects the contents of sent message from forwarding and saving</td>
+<td>Protects the contents of sent messages from forwarding and saving</td>
 </tr>
 <tr>
 <td>reply_to_message_id</td>