Update content of files

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

@@ -64,18 +64,18 @@
 <ul>
 <li><code>user_id</code> - <a href="/constructor/inputUserEmpty">inputUserEmpty</a></li>
 <li><code>button</code> - one of the following constructors:<ul>
-<li><a href="/constructor/botMenuButton">botMenuButton</a> - Opens a <a href="/api/bots/webapps">bot web app</a> when clicked.</li>
+<li><a href="/constructor/botMenuButton">botMenuButton</a> - Open a <a href="/api/bots/webapps">bot web app</a> when clicked.</li>
 <li><a href="/constructor/botMenuButtonCommands">botMenuButtonCommands</a> - Open the bot's command list when clicked.</li>
-<li><a href="/constructor/botMenuButton">botMenuButtonDefault</a> - No effect, keeps the previous menu button (either <a href="/constructor/botMenuButton">botMenuButton</a> or <a href="/constructor/botMenuButtonCommands">botMenuButtonCommands</a>)</li>
 </ul>
 </li>
 </ul>
+<p><a href="/constructor/botMenuButton">botMenuButtonDefault</a> shouldn't be used as it has no effect, keeping the previously set menu button (either <a href="/constructor/botMenuButton">botMenuButton</a> or <a href="/constructor/botMenuButtonCommands">botMenuButtonCommands</a>).</p>
 <h4><a class="anchor" href="#set-scope-specific-users" id="set-scope-specific-users" name="set-scope-specific-users"><i class="anchor-icon"></i></a>Set scope: specific users</h4>
-<p>To change the menu button for a specific users use the following parameters:</p>
+<p>To change the menu button for a specific user use the following parameters:</p>
 <ul>
 <li><code>user_id</code> - <a href="/constructor/inputUser">inputUser</a> with the user ID/access hash</li>
 <li><code>button</code> - one of the following constructors:<ul>
-<li><a href="/constructor/botMenuButton">botMenuButton</a> - Opens a <a href="/api/bots/webapps">bot web app</a> when clicked.</li>
+<li><a href="/constructor/botMenuButton">botMenuButton</a> - Open a <a href="/api/bots/webapps">bot web app</a> when clicked.</li>
 <li><a href="/constructor/botMenuButtonCommands">botMenuButtonCommands</a> - Open the bot's command list when clicked.</li>
 <li><a href="/constructor/botMenuButton">botMenuButtonDefault</a> - Resets the behavior of the button to the <a href="#set-scope-all-users">default scope (all users)</a>.  </li>
 </ul>
@@ -95,8 +95,8 @@
 <a href='/method/bots.getBotMenuButton'>bots.getBotMenuButton</a>#9c60eb28 user_id:<a href='/type/InputUser'>InputUser</a> = <a href='/type/BotMenuButton'>BotMenuButton</a>;</code></pre>
 <p>Bots might need to know the button type currently used in a given chat or in all chats: <a href="/method/bots.getBotMenuButton">bots.getBotMenuButton</a> can be used for this.</p>
 <p>Users can't use this method, and should use the <a href="#users">user</a> method instead.  </p>
-<h4><a class="anchor" href="#get-scope-all-users" id="get-scope-all-users" name="get-scope-all-users"><i class="anchor-icon"></i></a>Get scope: all users</h4>
-<p>To get the menu button used for for all users use the following parameters:</p>
+<h5><a class="anchor" href="#get-scope-all-users" id="get-scope-all-users" name="get-scope-all-users"><i class="anchor-icon"></i></a>Get scope: all users</h5>
+<p>To get the menu button used for all users use the following parameter:</p>
 <ul>
 <li><code>user_id</code> - <a href="/constructor/inputUserEmpty">inputUserEmpty</a></li>
 </ul>
@@ -106,8 +106,8 @@
 <li><a href="/constructor/botMenuButtonCommands">botMenuButtonCommands</a> - Open the bot's command list when clicked.</li>
 </ul>
 <p><a href="/constructor/botMenuButton">botMenuButtonDefault</a> will never be returned in this case.</p>
-<h4><a class="anchor" href="#get-scope-specific-users" id="get-scope-specific-users" name="get-scope-specific-users"><i class="anchor-icon"></i></a>Get scope: specific users</h4>
-<p>To get the menu button used for for all users use the following parameters:</p>
+<h5><a class="anchor" href="#get-scope-specific-users" id="get-scope-specific-users" name="get-scope-specific-users"><i class="anchor-icon"></i></a>Get scope: specific users</h5>
+<p>To get the menu button used for a specific user use the following parameter:</p>
 <ul>
 <li><code>user_id</code> - <a href="/constructor/inputUser">inputUser</a> with the user ID access/hash</li>
 </ul>

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

@@ -121,8 +121,8 @@ While <a href="/method/help.getConfig">help.getConfig</a> returns MTProto-specif
 <li><code>caption_length_limit_premium</code> - The maximum UTF-8 length of media captions sendable by non-Premium users (integer)</li>
 <li><code>upload_max_fileparts_default</code> - The maximum size of files uploadable by non-Premium users (integer, indicates the number of 512kb file parts, so the size in bytes is determined by multiplying by <code>524288</code>)</li>
 <li><code>upload_max_fileparts_premium</code> - The maximum size of files uploadable by Premium users (integer, indicates the number of 512kb file parts, so the size in bytes is determined by multiplying by <code>524288</code>)</li>
-<li><code>about_length_limit_default</code> - The maximum UTF-8 length of bios of non-Premium users</li>
-<li><code>about_length_limit_premium</code> - The maximum UTF-8 length of bios of Premium users</li>
+<li><code>about_length_limit_default</code> - The maximum UTF-8 length of bios of non-Premium users (integer)</li>
+<li><code>about_length_limit_premium</code> - The maximum UTF-8 length of bios of Premium users (integer)</li>
 <li><code>premium_promo_order</code> - Array of string identifiers, indicating the order of Telegram Premium features in the Telegram Premimum promotion popup, possible values:<ul>
 <li><code>double_limits</code> - Should open a secondary popup with a list of the default/premium limits mentioned above</li>
 <li><code>more_upload</code> - Premium users can upload bigger files, as specified by the <code>upload_max_fileparts_*</code> config keys</li>
@@ -132,7 +132,7 @@ While <a href="/method/help.getConfig">help.getConfig</a> returns MTProto-specif
 <li><code>unique_reactions</code> - Premium users have access to more <a href="/api/reactions">message reactions</a></li>
 <li><code>premimum_stickers</code> - Premium users have access to premium stickersets</li>
 <li><code>animated_emoji</code> - Premium users can send custom animated emojis</li>
-<li><code>advanced_chat_management</code> -</li>
+<li><code>advanced_chat_management</code> - Premium users can <a href="/api/folders">reorder the default folder</a>, auto-archive and hide new chats from non-contacts.</li>
 <li><code>profile_badge</code> - Premium users have a badge next to their name, showing that they are helping support Telegram</li>
 <li><code>animated_userpics</code> - <a href="/api/files#animated-profile-pictures">Animated profile pictures</a> of Premium users will play in-chat and when browsing the dialog list</li>
 <li><code>app_icons</code> - Premium users can change the default icon of the Telegram app</li>

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

@@ -78,7 +78,7 @@ The GamingCommunication and bot web app libraries by default will use <code>'*'<
 <tr>
 <td><code>web_app_phone_requested</code></td>
 <td>null</td>
-<td>Emitted by bot web apps when they request the user's phone number: Telegram clients should show a prompt to the user, which calls `window.Telegram.WebView.receiveEvent({})</td>
+<td>Emitted by bot web apps when they request the user's phone number: Telegram clients should show a prompt to the user, which should call <code>window.Telegram.WebView.receiveEvent({})</code> upon completion</td>
 </tr>
 <tr>
 <td><code>web_app_open_popup</code></td>
@@ -97,7 +97,7 @@ The GamingCommunication and bot web app libraries by default will use <code>'*'<
 <tr>
 <td><code>share_game</code></td>
 <td>null</td>
-<td>Will be called by games when the user explicitly clicks on the <strong>share game</strong> button to share the game, without sharing his score.<br>Typically done by using <a href="/method/messages.forwardMessages">messages.forwardMessages</a> on the game message without the <code>with_my_score</code> flag, or by sharing the game's short URL.</td>
+<td>Will be called by games when the user explicitly clicks on the <strong>share game</strong> button to share the game, without sharing his score.<br>Typically done by using <a href="/method/messages.forwardMessages">messages.forwardMessages</a> on the game message without the <code>with_my_score</code> flag, or by sharing the game's <a href="/api/links#game-links">deep link</a>.</td>
 </tr>
 <tr>
 <td><code>game_over</code></td>

data/web/corefork.telegram.org/constructor/messages.requestSimpleWebView

@@ -0,0 +1,118 @@
+<!DOCTYPE html>
+<html class="">
+  <head>
+    <meta charset="utf-8">
+    <title>Page not found</title>
+    <meta name="viewport" content="width=device-width, initial-scale=1.0">
+    <meta property="description" content="">
+    <meta property="og:title" content="Page not found">
+    <meta property="og:image" content="">
+    <meta property="og:description" content="">
+    <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">
+<link rel="icon" type="image/png" sizes="16x16" href="/img/favicon-16x16.png">
+<link rel="alternate icon" href="/img/favicon.ico" type="image/x-icon" />
+    <link href="/css/bootstrap.min.css?3" rel="stylesheet">
+    
+    <link href="/css/telegram.css?231" rel="stylesheet" media="screen">
+    <style>
+    </style>
+  </head>
+  <body class="preload">
+    <div class="dev_page_wrap">
+      <div class="dev_page_head navbar navbar-static-top navbar-tg">
+        <div class="navbar-inner">
+          <div class="container clearfix">
+            <ul class="nav navbar-nav navbar-right hidden-xs"><li class="navbar-twitter"><a href="https://twitter.com/telegram" target="_blank" data-track="Follow/Twitter" onclick="trackDlClick(this, event)"><i class="icon icon-twitter"></i><span> Twitter</span></a></li></ul>
+            <ul class="nav navbar-nav">
+              <li><a href="//telegram.org/">Home</a></li>
+<li class="hidden-xs"><a href="//telegram.org/faq">FAQ</a></li>
+<li class="hidden-xs"><a href="//telegram.org/apps">Apps</a></li>
+<li class=""><a href="/api">API</a></li>
+<li class=""><a href="/mtproto">Protocol</a></li>
+<li class="active"><a href="/schema">Schema</a></li>
+            </ul>
+          </div>
+        </div>
+      </div>
+      <div class="container clearfix">
+        <div class="dev_page">
+          <div id="dev_page_content_wrap" class=" ">
+  <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="/schema" >TL-schema</a></li><i class="icon icon-breadcrumb-divider"></i><li></li></ul></div>
+  <h1 id="dev_page_title">Page not found</h1>
+  
+  <div id="dev_page_content">The page has not been saved</div>
+  
+</div>
+          
+        </div>
+      </div>
+      <div class="footer_wrap">
+  <div class="footer_columns_wrap footer_desktop">
+    <div class="footer_column footer_column_telegram">
+      <h5>Telegram</h5>
+      <div class="footer_telegram_description"></div>
+      Telegram is a cloud-based mobile and desktop messaging app with a focus on security and speed.
+    </div>
+
+    <div class="footer_column">
+      <h5><a href="//telegram.org/faq">About</a></h5>
+      <ul>
+        <li><a href="//telegram.org/faq">FAQ</a></li>
+        <li><a href="//telegram.org/blog">Blog</a></li>
+        <li><a href="//telegram.org/jobs">Jobs</a></li>
+      </ul>
+    </div>
+    <div class="footer_column">
+      <h5><a href="//telegram.org/apps#mobile-apps">Mobile Apps</a></h5>
+      <ul>
+        <li><a href="//telegram.org/dl/ios">iPhone/iPad</a></li>
+        <li><a href="//telegram.org/dl/android">Android</a></li>
+        <li><a href="//telegram.org/dl/wp">Windows Phone</a></li>
+      </ul>
+    </div>
+    <div class="footer_column">
+      <h5><a href="//telegram.org/apps#desktop-apps">Desktop Apps</a></h5>
+      <ul>
+        <li><a href="//desktop.telegram.org/">PC/Mac/Linux</a></li>
+        <li><a href="//macos.telegram.org/">macOS</a></li>
+        <li><a href="//telegram.org/dl/web">Web-browser</a></li>
+      </ul>
+    </div>
+    <div class="footer_column footer_column_platform">
+      <h5><a href="//core.telegram.org/">Platform</a></h5>
+      <ul>
+        <li><a href="//core.telegram.org/api">API</a></li>
+        <li><a href="//translations.telegram.org/">Translations</a></li>
+        <li><a href="//instantview.telegram.org/">Instant View</a></li>
+      </ul>
+    </div>
+  </div>
+  <div class="footer_columns_wrap footer_mobile">
+    <div class="footer_column">
+      <h5><a href="//telegram.org/faq">About</a></h5>
+    </div>
+    <div class="footer_column">
+      <h5><a href="//telegram.org/blog">Blog</a></h5>
+    </div>
+    <div class="footer_column">
+      <h5><a href="//telegram.org/apps">Apps</a></h5>
+    </div>
+    <div class="footer_column">
+      <h5><a href="//core.telegram.org/">Platform</a></h5>
+    </div>
+    <div class="footer_column">
+      <h5><a href="https://twitter.com/telegram" target="_blank" data-track="Follow/Twitter" onclick="trackDlClick(this, event)">Twitter</a></h5>
+    </div>
+  </div>
+</div>
+    </div>
+    <script src="/js/main.js?46"></script>
+    
+    <script>backToTopInit("Go up");
+removePreloadInit();
+</script>
+  </body>
+</html>
+