Update content of files

data/web/corefork.telegram.org/api/bots/attach.html

@@ -77,12 +77,7 @@
 
 <a href='/method/messages.getAttachMenuBots'>messages.getAttachMenuBots</a>#16fcc2cb hash:<a href='/type/long'>long</a> = <a href='/type/AttachMenuBots'>AttachMenuBots</a>;</code></pre>
 <p>Bots that have the <code>bot_attach_menu</code> flag set offer an attachment menu entry that can be added to the attachment menu.  </p>
-<p>Use <a href="/method/messages.getAttachMenuBot">messages.getAttachMenuBot</a> to get info about the attachment menu entry of a given bot, specifically:</p>
+<p>Use <a href="/method/messages.getAttachMenuBot">messages.getAttachMenuBot</a> to get info about the attachment menu entry of a given bot, see the <a href="/constructor/attachMenuBot">attachMenuBot constructor page for more info »</a>.</p>
-<ul>
-<li><a href="/constructor/attachMenuBot">attachMenuBot</a>.<code>short_name</code> contains the short name used for the attachment menu label</li>
-<li><a href="/constructor/attachMenuBot">attachMenuBot</a>.<code>peer_types</code> indicates the dialog types supported by the attachment menu</li>
-<li><a href="/constructor/attachMenuBot">attachMenuBot</a>.<code>icons</code> contains a list of platform-specific static icons and animations to use for the attachment menu button.</li>
-</ul>
 <p>The installed attachment menu list can be fetched using <a href="/method/messages.getAttachMenuBots">messages.getAttachMenuBots</a>.  </p>
 <p>Use <a href="/method/messages.toggleBotInAttachMenu">messages.toggleBotInAttachMenu</a> to enable or disable the attachment menu of a given bot.<br>
 Changes made using this method will trigger an <a href="/constructor/updateAttachMenuBots">updateAttachMenuBots</a> update in other clients, which should trigger a <a href="/method/messages.getAttachMenuBots">messages.getAttachMenuBots</a> call to fetch the full updated list of installed attachment menu entries.<br>

data/web/corefork.telegram.org/api/layers.html

@@ -217,7 +217,7 @@ Also introducing new <a href="https://telegram.org/blog/custom-emoji#privacy-set
 </ul>
 <h5><a class="anchor" href="#new-constructors" id="new-constructors" name="new-constructors"><i class="anchor-icon"></i></a>New Constructors</h5>
 <ul>
-<li>Added <a href="/constructor/messageEntityCustomEmoji">messageEntityCustomEmoji</a> - Represents a custom emoji</li>
+<li>Added <a href="/constructor/messageEntityCustomEmoji">messageEntityCustomEmoji</a> - Represents a custom emoji.  </li>
 <li>Added <a href="/constructor/documentAttributeCustomEmoji">documentAttributeCustomEmoji</a> - Info about a custom emoji</li>
 <li>Added <a href="/constructor/stickerSetFullCovered">stickerSetFullCovered</a> - Stickerset preview with all stickers of the stickerset included.  </li>
 <li>Added <a href="/constructor/inputStorePaymentPremiumSubscription">inputStorePaymentPremiumSubscription</a> - Info about a Telegram Premium purchase</li>
@@ -269,7 +269,7 @@ Also introducing new <a href="https://telegram.org/blog/custom-emoji#privacy-set
 <h5><a class="anchor" href="#new-constructors" id="new-constructors" name="new-constructors"><i class="anchor-icon"></i></a>New Constructors</h5>
 <ul>
 <li>Added <a href="/constructor/messageEntitySpoiler">messageEntitySpoiler</a> - Message entity representing a spoiler</li>
-<li>Added <a href="/constructor/messageEntityCustomEmoji">messageEntityCustomEmoji</a> - Represents a custom emoji</li>
+<li>Added <a href="/constructor/messageEntityCustomEmoji">messageEntityCustomEmoji</a> - Represents a custom emoji.</li>
 </ul>
 <h4><a class="anchor" href="#end-to-end-schema" id="end-to-end-schema" name="end-to-end-schema"><i class="anchor-icon"></i></a>End-to-end schema</h4>
 <div><pre><code>===144===<br>
@@ -310,8 +310,8 @@ Also, discussion group admins can now <a href="/api/discussion#requiring-users-t
 <h5><a class="anchor" href="#new-constructors" id="new-constructors" name="new-constructors"><i class="anchor-icon"></i></a>New Constructors</h5>
 <ul>
 <li>Added <a href="/constructor/attachMenuPeerTypeSameBotPM">attachMenuPeerTypeSameBotPM</a> - The bot attachment menu entry is available in the chat with the bot that offers it</li>
-<li>Added <a href="/constructor/attachMenuPeerTypeBotPM">attachMenuPeerTypeBotPM</a> - The bot attachment menu entry is available in private chats with other bots</li>
+<li>Added <a href="/constructor/attachMenuPeerTypeBotPM">attachMenuPeerTypeBotPM</a> - The bot attachment menu entry is available in private chats with other bots (excluding the bot that offers the current attachment menu)</li>
-<li>Added <a href="/constructor/attachMenuPeerTypePM">attachMenuPeerTypePM</a> - The bot attachment menu entry is available in private chats with other users</li>
+<li>Added <a href="/constructor/attachMenuPeerTypePM">attachMenuPeerTypePM</a> - The bot attachment menu entry is available in private chats with other users (not bots)</li>
 <li>Added <a href="/constructor/attachMenuPeerTypeChat">attachMenuPeerTypeChat</a> - The bot attachment menu entry is available in <a href="/api/channel">groups and supergroups</a></li>
 <li>Added <a href="/constructor/attachMenuPeerTypeBroadcast">attachMenuPeerTypeBroadcast</a> - The bot attachment menu entry is available in channels</li>
 <li>Added <a href="/constructor/chatInvitePublicJoinRequests">chatInvitePublicJoinRequests</a> - Used in updates and in the channel log to indicate when a user is requesting to join or has joined a <a href="/api/discussion#requiring-users-to-join-the-group">discussion group</a></li>

data/web/corefork.telegram.org/api/web-events.html

@@ -166,7 +166,7 @@ The web app must also be expanded when the user swipes up on the webview.  </p>
 <li><code>is_progress_visible</code> - Indicates whether the button should display a loading indicator (boolean, false by default)</li>
 </ul>
 <p>Configures the main button, located immediately below the webview: when the user presses it a <a href="/api/bots/webapps#main-button-pressed"><code>main_button_pressed</code> event should be emitted by the client</a>.  </p>
-<p>Note that if <code>is_visible</code> is true, <em>only when opening web apps from the <a href="/api/bots/attach">attachment menu</a></em> and <em>only on clients with tab bars</em>, the main button should be displayed only after the first user tap inside of the webview (to prevent bots from immediately blocking the media type tab bar).<br>
+<p>Note that if <code>is_visible</code> is true, <em>only when opening web apps from the <a href="/api/bots/attach">attachment menu</a></em> and <em>only on clients with media type tab bars</em>, the main button should be displayed (replacing the tab bar) only after the first user tap inside of the webview (to prevent bots from immediately blocking the tab bar).<br>
 Otherwise, the main button can be displayed right away if <code>is_visible</code> is true.  </p>
 <h4><a class="anchor" href="#web-app-setup-back-button" id="web-app-setup-back-button" name="web-app-setup-back-button"><i class="anchor-icon"></i></a><code>web_app_setup_back_button</code></h4>
 <p>Event data: a JSON object with an <code>is_visible</code> boolean field.</p>

data/web/corefork.telegram.org/constructor/attachMenuBot.html

@@ -94,12 +94,12 @@
 <tr>
 <td><strong>peer_types</strong></td>
 <td style="text-align: center;"><a href="/type/Vector%20t">Vector</a>&lt;<a href="/type/AttachMenuPeerType">AttachMenuPeerType</a>&gt;</td>
-<td>List of peer types where this attachment should be shown</td>
+<td>List of dialog types where this attachment menu entry should be shown</td>
 </tr>
 <tr>
 <td><strong>icons</strong></td>
 <td style="text-align: center;"><a href="/type/Vector%20t">Vector</a>&lt;<a href="/type/AttachMenuBotIcon">AttachMenuBotIcon</a>&gt;</td>
-<td>Attachment menu icon</td>
+<td>List of platform-specific static icons and animations to use for the attachment menu button</td>
 </tr>
 </tbody>
 </table>

data/web/corefork.telegram.org/constructor/attachMenuPeerTypeBotPM.html

@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>attachMenuPeerTypeBotPM</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="The bot attachment menu entry is available in private chats with other bots">
+    <meta property="description" content="The bot attachment menu entry is available in private chats with other bots (excluding the bot that offers the current attachment menu)">
     <meta property="og:title" content="attachMenuPeerTypeBotPM">
     <meta property="og:image" content="">
-    <meta property="og:description" content="The bot attachment menu entry is available in private chats with other bots">
+    <meta property="og:description" content="The bot attachment menu entry is available in private chats with other bots (excluding the bot that offers the current attachment menu)">
     <link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
 <link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">

data/web/corefork.telegram.org/constructor/attachMenuPeerTypePM.html

@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>attachMenuPeerTypePM</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="The bot attachment menu entry is available in private chats with other users">
+    <meta property="description" content="The bot attachment menu entry is available in private chats with other users (not bots)">
     <meta property="og:title" content="attachMenuPeerTypePM">
     <meta property="og:image" content="">
-    <meta property="og:description" content="The bot attachment menu entry is available in private chats with other users">
+    <meta property="og:description" content="The bot attachment menu entry is available in private chats with other users (not bots)">
     <link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
 <link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">

data/web/corefork.telegram.org/constructor/messageEntityCustomEmoji.html

@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>messageEntityCustomEmoji</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="Represents a custom emoji">
+    <meta property="description" content="Represents a custom emoji. Note that this entity must wrap exactly one regular emoji (the one contained in documentAttributeCustomEmoji.alt) in the related text, otherwise the server will ignore it.">
     <meta property="og:title" content="messageEntityCustomEmoji">
     <meta property="og:image" content="">
-    <meta property="og:description" content="Represents a custom emoji">
+    <meta property="og:description" content="Represents a custom emoji. Note that this entity must wrap exactly one regular emoji (the one contained in documentAttributeCustomEmoji.alt) in the related text, otherwise the server will ignore it.">
     <link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
 <link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
@@ -93,7 +93,9 @@ Note that this entity must wrap exactly one regular emoji (the one contained in
 <p>Telegram allows including animated and static custom emojis inside of messages.</p>
 <h4><a class="anchor" href="#messagesgetcustomemojidocuments" id="messagesgetcustomemojidocuments" name="messagesgetcustomemojidocuments"><i class="anchor-icon"></i></a><a href="/method/messages.getCustomEmojiDocuments">messages.getCustomEmojiDocuments</a></h4>
 <p>Fetch <a href="/api/custom-emoji">custom emoji stickers »</a>.</p>
-<p>Returns a list of <a href="/constructor/document">documents</a> with the animated custom emoji in TGS format, and a <a href="/constructor/documentAttributeCustomEmoji">documentAttributeCustomEmoji</a> attribute with the original emoji and info about the emoji stickerset this custom emoji belongs to.</p></div>
+<p>Returns a list of <a href="/constructor/document">documents</a> with the animated custom emoji in TGS format, and a <a href="/constructor/documentAttributeCustomEmoji">documentAttributeCustomEmoji</a> attribute with the original emoji and info about the emoji stickerset this custom emoji belongs to.</p>
+<h4><a class="anchor" href="#documentattributecustomemoji" id="documentattributecustomemoji" name="documentattributecustomemoji"><i class="anchor-icon"></i></a><a href="/constructor/documentAttributeCustomEmoji">documentAttributeCustomEmoji</a></h4>
+<p>Info about a custom emoji</p></div>
   
 </div>
           

data/web/corefork.telegram.org/method/messages.getCustomEmojiDocuments

@@ -82,7 +82,8 @@
 <h4><a class="anchor" href="#custom-emojis" id="custom-emojis" name="custom-emojis"><i class="anchor-icon"></i></a><a href="/api/custom-emoji">Custom emojis</a></h4>
 <p>Telegram allows including animated and static custom emojis inside of messages.</p>
 <h4><a class="anchor" href="#messageentitycustomemoji" id="messageentitycustomemoji" name="messageentitycustomemoji"><i class="anchor-icon"></i></a><a href="/constructor/messageEntityCustomEmoji">messageEntityCustomEmoji</a></h4>
-<p>Represents a custom emoji</p>
+<p>Represents a custom emoji.<br>
+Note that this entity must wrap exactly one regular emoji (the one contained in <a href="/constructor/documentAttributeCustomEmoji">documentAttributeCustomEmoji</a>.<code>alt</code>) in the related text, otherwise the server will ignore it.</p>
 <h4><a class="anchor" href="#document" id="document" name="document"><i class="anchor-icon"></i></a><a href="/constructor/document">document</a></h4>
 <p>Document</p>
 <h4><a class="anchor" href="#documentattributecustomemoji" id="documentattributecustomemoji" name="documentattributecustomemoji"><i class="anchor-icon"></i></a><a href="/constructor/documentAttributeCustomEmoji">documentAttributeCustomEmoji</a></h4>

data/web/corefork.telegram.org/method/messages.prolongWebView

@@ -42,7 +42,7 @@
   <div class="dev_page_bread_crumbs"><ul class="breadcrumb clearfix"><li><a  href="/api" >API</a></li><i class="icon icon-breadcrumb-divider"></i><li><a  href="/methods" >All Methods</a></li><i class="icon icon-breadcrumb-divider"></i><li><a  href="/method/messages.prolongWebView" >messages.prolongWebView</a></li></ul></div>
   <h1 id="dev_page_title">messages.prolongWebView</h1>
   
-  <div id="dev_page_content"><p>Indicate to the server (from the user side) that the user is still using a web app.  </p>
+  <div id="dev_page_content"><p>Indicate to the server (from the user side) that the user is still using a web app.</p>
 <p>If the method returns a <code>QUERY_ID_INVALID</code> error, the webview must be closed.</p>
 <p><div class="clearfix">
   <ul class="dev_layer_select slightly-pull-right nav nav-pills">

data/web/corefork.telegram.org/method/messages.requestWebView

@@ -139,7 +139,8 @@
 <p>Telegram clients must handle special tg:// and t.me deep links encountered in messages, link entities and in other apps by registering OS handlers.</p>
 <h4><a class="anchor" href="#web-apps-for-bots" id="web-apps-for-bots" name="web-apps-for-bots"><i class="anchor-icon"></i></a><a href="/bots/webapps">Web Apps for Bots</a></h4>
 <h4><a class="anchor" href="#messagesprolongwebview" id="messagesprolongwebview" name="messagesprolongwebview"><i class="anchor-icon"></i></a><a href="/method/messages.prolongWebView">messages.prolongWebView</a></h4>
-<p>Indicate to the server (from the user side) that the user is still using a web app.</p></div>
+<p>Indicate to the server (from the user side) that the user is still using a web app.</p>
+<p>If the method returns a <code>QUERY_ID_INVALID</code> error, the webview must be closed.</p></div>
   
 </div>
           

data/web/corefork.telegram.org/method/messages.sendReaction

@@ -181,6 +181,8 @@
 </tbody>
 </table>
 <h3><a class="anchor" href="#related-pages" id="related-pages" name="related-pages"><i class="anchor-icon"></i></a>Related pages</h3>
+<h4><a class="anchor" href="#message-reactions" id="message-reactions" name="message-reactions"><i class="anchor-icon"></i></a><a href="/api/reactions">Message reactions</a></h4>
+<p>Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.</p>
 <h4><a class="anchor" href="#client-configuration" id="client-configuration" name="client-configuration"><i class="anchor-icon"></i></a><a href="/api/config">Client configuration</a></h4>
 <p>The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.</p></div>
   

data/web/corefork.telegram.org/methods.html

@@ -1372,7 +1372,7 @@
 </tr>
 <tr>
 <td><a href="/method/messages.prolongWebView">messages.prolongWebView</a></td>
-<td>Indicate to the server (from the user side) that the user is still using a web app.</td>
+<td>Indicate to the server (from the user side) that the user is still using a web app.<br><br>If the method returns a <code>QUERY_ID_INVALID</code> error, the webview must be closed.</td>
 </tr>
 <tr>
 <td><a href="/method/messages.requestSimpleWebView">messages.requestSimpleWebView</a></td>

data/web/corefork.telegram.org/type/AttachMenuPeerType.html

@@ -75,11 +75,11 @@
 </tr>
 <tr>
 <td><a href="/constructor/attachMenuPeerTypeBotPM">attachMenuPeerTypeBotPM</a></td>
-<td>The bot attachment menu entry is available in private chats with other bots</td>
+<td>The bot attachment menu entry is available in private chats with other bots (excluding the bot that offers the current attachment menu)</td>
 </tr>
 <tr>
 <td><a href="/constructor/attachMenuPeerTypePM">attachMenuPeerTypePM</a></td>
-<td>The bot attachment menu entry is available in private chats with other users</td>
+<td>The bot attachment menu entry is available in private chats with other users (not bots)</td>
 </tr>
 <tr>
 <td><a href="/constructor/attachMenuPeerTypeChat">attachMenuPeerTypeChat</a></td>

data/web/corefork.telegram.org/type/Bool.html

@@ -667,7 +667,7 @@
 </tr>
 <tr>
 <td><a href="/method/messages.prolongWebView">messages.prolongWebView</a></td>
-<td>Indicate to the server (from the user side) that the user is still using a web app.</td>
+<td>Indicate to the server (from the user side) that the user is still using a web app.<br><br>If the method returns a <code>QUERY_ID_INVALID</code> error, the webview must be closed.</td>
 </tr>
 <tr>
 <td><a href="/method/bots.setBotMenuButton">bots.setBotMenuButton</a></td>

data/web/corefork.telegram.org/type/MessageAction.html

@@ -223,7 +223,7 @@
 </tr>
 <tr>
 <td><a href="/constructor/messageActionWebViewDataSent">messageActionWebViewDataSent</a></td>
-<td>Data from an opened <a href="/api/bots/webapps">reply keyboard bot web app</a> was relayed to the bot that owns it (user side service message).</td>
+<td>Data from an opened <a href="/api/bots/webapps">reply keyboard bot web app</a> was relayed to the bot that owns it (user side service message).<br><br>Clients should display a service message with the text <code>Data from the «$text» button was transferred to the bot.</code></td>
 </tr>
 <tr>
 <td><a href="/constructor/messageActionGiftPremium">messageActionGiftPremium</a></td>

data/web/corefork.telegram.org/type/MessageEntity.html

@@ -167,7 +167,7 @@
 </tr>
 <tr>
 <td><a href="/constructor/messageEntityCustomEmoji">messageEntityCustomEmoji</a></td>
-<td>Represents a custom emoji</td>
+<td>Represents a custom emoji.  <br>Note that this entity must wrap exactly one regular emoji (the one contained in <a href="/constructor/documentAttributeCustomEmoji">documentAttributeCustomEmoji</a>.<code>alt</code>) in the related text, otherwise the server will ignore it.</td>
 </tr>
 </tbody>
 </table></div>