Update content of files

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

@@ -61,6 +61,9 @@
 <h4><a class="anchor" href="#back-button-pressed" id="back-button-pressed" name="back-button-pressed"><i class="anchor-icon"></i></a><code>back_button_pressed</code></h4>
 <p>Params: <code>null</code></p>
 <p>Sent by the client when the user presses the (OS or UI) back button, if it was <a href="/api/web-events#web-app-setup-back-button">previously enabled by a <code>web_app_setup_back_button</code> event »</a>.</p>
+<h4><a class="anchor" href="#settings-button-pressed" id="settings-button-pressed" name="settings-button-pressed"><i class="anchor-icon"></i></a><code>settings_button_pressed</code></h4>
+<p>Params: <code>null</code></p>
+<p>Sent by the client when the user presses the settings button, if it was <a href="/api/web-events#web-app-setup-settings-button">previously enabled by a <code>web_app_setup_settings_button</code> event »</a>.</p>
 <h4><a class="anchor" href="#invoice-closed" id="invoice-closed" name="invoice-closed"><i class="anchor-icon"></i></a><code>invoice_closed</code></h4>
 <p>Params: JSON object with the following fields:</p>
 <ul>
@@ -250,8 +253,7 @@ Confirmation should <strong>always</strong> be asked, even if the <code>inactive
 </li>
 </ul>
 <p>Finally, open the webview using the <code>url</code> contained in the returned <a href="/constructor/appWebViewResultUrl">appWebViewResultUrl</a>.  </p>
-<p>Since there is no linked inline query, <code>web_app_data_send</code> events must be ignored.<br>
-The bot can, however, write to the user directly if it already has a chat with the user or if it requested permission via <code>request_write_access</code> and the user granted it with <code>write_allowed</code>.  </p>
+<p>The bot can write to the user directly if it already has a chat with the user or if it requested permission via <code>request_write_access</code> and the user granted it with <code>write_allowed</code>.  </p>
 <h3><a class="anchor" href="#theme-parameters" id="theme-parameters" name="theme-parameters"><i class="anchor-icon"></i></a>Theme parameters</h3>
 <p>Bot Mini Apps can be themed according to the following theme parameters, passed as a JSON object to the <code>theme_params</code> parameter of the <a href="/method/messages.requestSimpleWebView">messages.requestSimpleWebView</a> and <a href="/method/messages.requestWebView">messages.requestWebView</a> methods.  </p>
 <p>This JSON object has the following keys, containing color theme information (hex string, RGB, no alpha) to pass to the Mini App:</p>
@@ -263,6 +265,12 @@ The bot can, however, write to the user directly if it already has a chat with t
 <li><code>link_color</code> - Link color</li>
 <li><code>button_color</code> - Button color</li>
 <li><code>button_text_color</code> - Button text color</li>
+<li><code>header_bg_color</code> - Header background color</li>
+<li><code>accent_text_color</code> - Accent text color</li>
+<li><code>section_bg_color</code> - Section background color</li>
+<li><code>section_header_text_color</code> - Section header text color</li>
+<li><code>subtitle_text_color</code> - Sub title text color</li>
+<li><code>destructive_text_color</code> - Text color for destructive action buttons in prompts</li>
 </ul></div>
   
 </div>

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

@@ -184,6 +184,9 @@ In clients that implements a tab bar, iff the user opens a mini app through a ta
 <p>Event data: a JSON object with an <code>is_visible</code> boolean field.</p>
 <p>Determines whether to show or hide the back button: when the user presses it a <a href="/api/bots/webapps#back-button-pressed"><code>back_button_pressed</code> event should be emitted by the client</a>.<br>
 Note that on supported platforms, the OS back button can be used instead of a custom back button: in this case, if <code>is_visible</code> is true pressing the OS back button should emit a <a href="/api/bots/webapps#back-button-pressed"><code>back_button_pressed</code> event</a>, otherwise the webview should be closed.</p>
+<h4><a class="anchor" href="#web-app-setup-settings-button" id="web-app-setup-settings-button" name="web-app-setup-settings-button"><i class="anchor-icon"></i></a><code>web_app_setup_settings_button</code></h4>
+<p>Event data: a JSON object with an <code>is_visible</code> boolean field.</p>
+<p>Determines whether to show or hide the settings button: when the user presses it a <a href="/api/bots/webapps#settings-button-pressed"><code>settings_button_pressed</code> event should be emitted by the client</a>.  </p>
 <h4><a class="anchor" href="#payment-form-submit" id="payment-form-submit" name="payment-form-submit"><i class="anchor-icon"></i></a><code>payment_form_submit</code></h4>
 <p>Event payload: JSON object with <code>credentials</code> and <code>title</code> fields.</p>
 <ul>