diff --git a/data/web/corefork.telegram.org/api/web-events.html b/data/web/corefork.telegram.org/api/web-events.html
index 573241558c..cd257bbd08 100644
--- a/data/web/corefork.telegram.org/api/web-events.html
+++ b/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 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 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>
 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>