diff --git a/data/web/corefork.telegram.org/api/bots/attach.html b/data/web/corefork.telegram.org/api/bots/attach.html
index 3fbd449b00..46fa431902 100644
--- a/data/web/corefork.telegram.org/api/bots/attach.html
+++ b/data/web/corefork.telegram.org/api/bots/attach.html
@@ -92,11 +92,12 @@ The attachment/side menu list should also be refreshed if the user changes the a
Thus, before launching the mini app when clicking on a attachment/side menu deep link, the client should show a prompt to the user, asking to add the mini app to the attachment/side menu.
Note that if the attachMenuBot.side_menu_disclaimer_needed flag is set, an additional mandatory checkbox to accept the mini apps TOS and a disclaimer indicating that this Mini App is not affiliated to Telegram should be shown in the installation prompt.
If the user accepts, invoke messages.toggleBotInAttachMenu with the write_allowed flag set and proceed to the next step, otherwise abort the process.
-...is not set, proceed to the next step unconditionally.
+...is not set, and the attachMenuBot.side_menu_disclaimer_needed flag is still set, an additional mandatory checkbox to accept the mini apps TOS and a disclaimer indicating that this Mini App is not affiliated to Telegram should be shown.
+If the user accepts, proceed to the next step, otherwise abort the process.
Open the Mini App:
-- If the link is a direct mini app link, open the Mini App regardless of the currently open Telegram chat (in fact, the Mini App should opened even if the client itself is minimized), as specified here ».
+- If the link is a direct mini app link, open the Mini App regardless of the currently open Telegram chat (in fact, the Mini App should opened even if the client itself is minimized), as specified here ».
- For attachment/side menu links, check that the attachment menu can be opened in the chosen chat type by checking the attachMenuBot.
peer_types field.