diff --git a/data/web/corefork.telegram.org/api/bots/webapps.html b/data/web/corefork.telegram.org/api/bots/webapps.html
index 188acb0281..10ceed3c19 100644
--- a/data/web/corefork.telegram.org/api/bots/webapps.html
+++ b/data/web/corefork.telegram.org/api/bots/webapps.html
@@ -182,7 +182,7 @@ If the client has already encountered an app with this short name from the same
If the user agrees, set the write_allowed flag when invoking messages.requestAppWebView in the next step.
If a messages.botApp constructor is returned, open the web app by invoking messages.requestAppWebView, generating an inputBotAppID constructor from id and access_hash of the returned botApp, or from previously cached information if we already met the bot app and botAppNotModified was returned.
- If the client has clicked on the link in a Telegram chat, pass the chat's peer information into
peer; otherwise pass the bot's peer information, instead.
-- If the messages.botApp.
inactive flag is set, ask confirmation from the user before opening the web app.
+- If the messages.botApp.
inactive flag is set, ask confirmation from the user before opening the web app; the request_write_access checkbox should be shown in this prompt, if needed.
- If the
startapp query string parameter is present, pass it to start_param when invoking messages.requestAppWebView.
- If the messages.botApp.
request_write_access flag is set, the bot is asking permission to send messages to the user: if the user agrees, set the write_allowed flag when invoking messages.requestAppWebView.