Update content of files

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

@@ -67,8 +67,8 @@
 <li><code>slug</code> - Invoice identifier (string)</li>
 <li><code>status</code> - One of the following values (string):<ul>
 <li><code>cancelled</code> – The user closed the invoice popup without paying, before the call to <a href="/method/payments.sendPaymentForm">payments.sendPaymentForm</a>.</li>
-<li><code>pending</code> – The payment is still processing: the bot will receive a further service message about a successful or failed payment. <a href="/method/payments.sendPaymentForm">payments.sendPaymentForm</a> was successfully invoked, the user completed all additional verification forms returned by the method, the invoice popup was closed but the client hasn't received a <a href="/constructor/messageActionPaymentSent">messageActionPaymentSent</a> service message yet.</li>
-<li><code>failed</code> – The user tried to pay, but the payment failed: the call to <a href="/method/payments.sendPaymentForm">payments.sendPaymentForm</a> returned an RPC error (via an <a href="/constructor/updateServiceNotification">updateServiceNotification</a>) and the popup was closed.</li>
+<li><code>failed</code> – The user tried to pay, but the payment failed: the call to <a href="/method/payments.sendPaymentForm">payments.sendPaymentForm</a> returned an RPC error and the popup was closed.</li>
+<li><code>pending</code> – The payment is still processing: the bot will receive a further service message about a successful or failed payment. <a href="/method/payments.sendPaymentForm">payments.sendPaymentForm</a> was successfully invoked returning <a href="/constructor/payments.paymentVerificationNeeded">payments.paymentVerificationNeeded</a>, the user completed all additional verification forms returned by the method and the invoice popup was closed, but the client hasn't received a <a href="/constructor/messageActionPaymentSent">messageActionPaymentSent</a> service message yet.</li>
 <li><code>paid</code> – The invoice was paid successfully: the client completed the <a href="/api/payments">payment flow »</a>, the invoice popup was closed and a <a href="/constructor/messageActionPaymentSent">messageActionPaymentSent</a> service message was received by the client.</li>
 </ul>
 </li>
@@ -117,7 +117,8 @@
 <li><code>button_text</code> - Text of the <a href="/constructor/keyboardButtonSimpleWebView">keyboardButtonSimpleWebView</a> that was pressed to open the simple web app</li>
 <li><code>data</code> - Contents of the <code>data</code> field of the JS event.  </li>
 </ul>
-<p>The webview must be closed after invoking the <a href="/method/messages.sendWebViewData">messages.sendWebViewData</a> method.  </p>
+<p>Make sure to ignore all <code>web_app_data_send</code> events sent after the first one, <a href="/method/messages.sendWebViewData">messages.sendWebViewData</a> must be called only once.<br>
+The webview must be closed after invoking the <a href="/method/messages.sendWebViewData">messages.sendWebViewData</a> method.  </p>
 <p>This will generate a <a href="/constructor/messageActionWebViewDataSent">messageActionWebViewDataSent</a> update for the user, and a <a href="/constructor/messageActionWebViewDataSentMe">messageActionWebViewDataSentMe</a> update for the bot, containing the event data.  </p>
 <h3><a class="anchor" href="#normal-web-apps" id="normal-web-apps" name="normal-web-apps"><i class="anchor-icon"></i></a>Normal web apps</h3>
 <p>Schema:</p>

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

@@ -279,7 +279,7 @@ This is only possible on accounts with <a href="/api/srp">2FA</a> enabled.</p>
 <p>The bot then <a href="#41-receiving-pre-checkout-query">replies to the received precheckout query</a>, finally the user <a href="#5-checkout">proceeds to checkout</a>.</p>
 <p>Please note that if the result of the method is a <a href="/constructor/payments.paymentVerificationNeeded">payments.paymentVerificationNeeded</a>, before <a href="#5-checkout">proceeding to checkout</a> the payment provider requires the user to verify their identity by opening the provided <code>url</code> and following instructions.
 Once the user finishes working with the webpage, the client can <a href="#5-checkout">proceed to checkout</a>.</p>
-<p>Eventual errors are returned in the form of RPC errors, with the description of the error by the bot contained in <a href="/constructor/updateServiceNotification">service updates</a>.</p>
+<p>Eventual errors are returned in the form of RPC errors, with the description of the error by the bot contained in additional <a href="/constructor/updateServiceNotification">service updates</a>.</p>
 <h4><a class="anchor" href="#41-receiving-pre-checkout-query" id="41-receiving-pre-checkout-query" name="41-receiving-pre-checkout-query"><i class="anchor-icon"></i></a>4.1 Receiving pre-checkout query</h4>
 <pre><code><a href='/constructor/paymentRequestedInfo'>paymentRequestedInfo</a>#909c3f94 flags:<a href='/type/%23'>#</a> name:flags.0?<a href='/type/string'>string</a> phone:flags.1?<a href='/type/string'>string</a> email:flags.2?<a href='/type/string'>string</a> shipping_address:flags.3?<a href='/type/PostAddress'>PostAddress</a> = <a href='/type/PaymentRequestedInfo'>PaymentRequestedInfo</a>;
 

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

@@ -101,7 +101,7 @@ While handling is enabled, maximum 3 consecutive valid events of this type can b
 <p>Used to set the web app header and upper overscroll color.  </p>
 <h4><a class="anchor" href="#web-app-data-send" id="web-app-data-send" name="web-app-data-send"><i class="anchor-icon"></i></a><code>web_app_data_send</code></h4>
 <p>Event data: a JSON object with a string <code>data</code> field.  </p>
-<p>Used by <a href="/api/bots/webapps#simple-web-apps">simple webapps</a> to send back data to the bot. The Web App will be closed.  </p>
+<p>Used by <a href="/api/bots/webapps#simple-web-apps">simple webapps</a> to send back data to the bot as specified <a href="/api/bots/webapps#simple-web-apps">here »</a>. The Web App will be closed.  </p>
 <h4><a class="anchor" href="#web-app-trigger-haptic-feedback" id="web-app-trigger-haptic-feedback" name="web-app-trigger-haptic-feedback"><i class="anchor-icon"></i></a><code>web_app_trigger_haptic_feedback</code></h4>
 <p>Event data: a JSON object with the following fields:</p>
 <ul>