diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html
index 225c1fc013..172dae3db3 100644
--- a/data/web/corefork.telegram.org/api/layers.html
+++ b/data/web/corefork.telegram.org/api/layers.html
@@ -202,6 +202,17 @@
 <a href="/method/auth.reportMissingCode">auth.reportMissingCode</a>#cb9deff6 phone_number:<a href="/type/string">string</a> phone_code_hash:<a href="/type/string">string</a> mnc:<a href="/type/string">string</a> = <a href="/type/Bool">Bool</a>;<br>
 <a href="/method/messages.getEmojiStickerGroups">messages.getEmojiStickerGroups</a>#1dd840f5 hash:<a href="/type/int">int</a> = <a href="/type/messages.EmojiGroups">messages.EmojiGroups</a>;<br></code></pre></div>
 <h3><a class="anchor" href="#layer-178" id="layer-178" name="layer-178"><i class="anchor-icon"></i></a><a href="/schema?layer=178">Layer 178</a></h3>
+<p>This layers introduces the following features:</p>
+<ul>
+<li><a href="/api/business#re-enable-ads">Telegram Business: re-enable ads »</a></li>
+<li><a href="/api/sponsored-messages">Greatly simplify sponsored messages »</a></li>
+<li><a href="/api/stories#pinned-or-archived-stories">Pin stories to the top of the profile »</a></li>
+<li><a href="/api/reactions#notifications-about-reactions">Reaction notification settings »</a></li>
+<li><a href="/method/messages.setChatAvailableReactions">Custom unique reactions limit for groups, supergroups and channels »</a></li>
+<li><a href="/api/search#global-search">Global channel recommendations in the "Channels" global search tab »</a></li>
+<li><a href="/constructor/webPageAttributeStickerSet">Stickerset deep link previews »</a></li>
+<li><a href="/constructor/codeSettings">codeSettings</a>.<code>unknown_number</code>: set this flag if there is a SIM card in the current device, but it is not possible to check whether the specified phone number matches the SIM's phone number.</li>
+</ul>
 <h4><a class="anchor" href="#schema-changes" id="schema-changes" name="schema-changes"><i class="anchor-icon"></i></a>Schema changes</h4>
 <h5><a class="anchor" href="#new-methods" id="new-methods" name="new-methods"><i class="anchor-icon"></i></a>New Methods</h5>
 <ul>
@@ -258,8 +269,8 @@
 <h3><a class="anchor" href="#layer-177" id="layer-177" name="layer-177"><i class="anchor-icon"></i></a><a href="/schema?layer=177">Layer 177</a></h3>
 <p>This layer adds the following features:</p>
 <ul>
-<li><a href="/api/revenue">Channel ad revenue »</a> - Telegram channel owners can now receive 50% of the revenue from ads displayed in their channels, as well as view detailed revenue statistics.  </li>
-<li><a href="/api/business#connected-bots">Telegram Business connected bots »</a> (bot-side constructors)</li>
+<li><a href="/api/revenue">Channel ad revenue »</a>: Telegram channel owners can now receive 50% of the revenue from ads displayed in their channels, as well as view detailed revenue statistics.  </li>
+<li><a href="/api/business#connected-bots">Telegram Business connected bots »</a>: <a href="/api/action-bar#manage-a-connected-business-bot">connected business bot action bar »</a> and bot-side constructors.  </li>
 <li><a href="/api/business#business-introduction">Telegram Business introduction »</a></li>
 <li><a href="/api/business#business-chat-links">Telegram Business chat links »</a></li>
 <li><a href="/api/fragment">Fetch info about Fragment collectibles »</a></li>
diff --git a/data/web/corefork.telegram.org/api/sponsored-messages.html b/data/web/corefork.telegram.org/api/sponsored-messages.html
index 6224af40c4..6dca821442 100644
--- a/data/web/corefork.telegram.org/api/sponsored-messages.html
+++ b/data/web/corefork.telegram.org/api/sponsored-messages.html
@@ -62,27 +62,18 @@ sponsoredMessage#bdedf566 flags:# recommended:flags.5?true can_report:flags.12?t
 <p><a href="https://t.me/durov/172">More about sponsored messages on Telegram</a></p>
 </blockquote>
 <h4><a class="anchor" href="#displaying-sponsored-messages" id="displaying-sponsored-messages" name="displaying-sponsored-messages"><i class="anchor-icon"></i></a>Displaying sponsored messages</h4>
-<p>Sponsored messages must be displayed below all other posts in the channel, after the user scrolls further down, past the last message. The promoted channel or bot specified in the <code>from_id</code> or <code>chat_invite</code> mutually exclusive fields must be displayed as the author of the message. The message should also contain a button at the bottom with one of the following labels:</p>
+<p>Sponsored messages must be displayed below all other posts in the channel, after the user scrolls further down, past the last message. The message should contain a button at the bottom with one of the following labels:</p>
 <ul>
 <li><mark><strong>View Bot</strong></mark> — if a bot is being promoted. Tapping the button must open the chat with the bot. If <code>start_param</code> is specified, the app must use the <a href="/api/links#bot-links">deep linking mechanism</a> to open the bot.</li>
-<li><mark><strong>View Channel</strong></mark> — if a channel is being promoted. Tapping the button must open the channel using the <code>from_id</code> or by <a href="/api/invites#invite-links">importing</a> the <code>chat_invite_hash</code> <a href="/api/invites#invite-links">invitation link hash »</a>.</li>
+<li><mark><strong>View Channel</strong></mark> — if a channel is being promoted. Tapping the button must open the channel in <code>from_id</code>.</li>
 <li><mark><strong>View Post</strong></mark> — if a channel is being promoted and <code>channel_post</code> is specified. Tapping the button must open the particular channel post.</li>
 <li><mark><strong>Launch App</strong></mark> — if the <code>app</code> flag is set, the specified <a href="/api/bots/webapps">Mini App</a> should be opened when clicking on the button.  </li>
 <li><mark><strong>Open Website</strong></mark> — If the <code>url</code> flag is set, clicking on the button should open the external website specified in <code>url</code>.  </li>
 <li>The contents of the <code>button_text</code> field — if the <code>button_text</code> field is set.</li>
 </ul>
 <p>The message should be marked as "Recommended" instead of "Sponsored" if the <code>recommended</code> flag is set.  </p>
-<p>A profile photo bubble should be displayed for the sponsored message, like for messages sent in groups, using:</p>
-<ul>
-<li><code>photo</code>, if the <code>photo</code> flag is set, otherwise</li>
-<li>The profile picture of the chat in <code>chat_invite</code>, if the <code>chat_invite</code> flag is set, otherwise</li>
-<li>The profile picture of the peer in <code>from_id</code>, if the <code>show_peer_photo</code> flag is set.</li>
-</ul>
-<p>A sender name should be displayed for the sponsored message, like for messages sent in groups, using:</p>
-<ul>
-<li><code>title</code>, if the <code>title</code> flag is set, otherwise</li>
-<li>The title of the chat in <code>chat_invite</code>, if the <code>chat_invite</code> flag is set.</li>
-</ul>
+<p>If the <code>photo</code> flag is set, it should be used to display a profile photo bubble for the sponsored message, like for messages sent in groups.  </p>
+<p>If the <code>title</code> flag is set, it should be used as <em>sender name</em> for the sponsored message, like for messages sent in groups.</p>
 <p>If the <code>sponsor_info</code> or <code>additional_info</code> flags are set, an additional "Sponsor info" menu item must be present in the message context menu (the menu that pops up when clicking on a button), that when clicked, displays the contents of the flags.  </p>
 <p>If set, the sponsored message should use the <a href="/api/colors">message accent color »</a> specified in <code>color</code>.</p>
 <h4><a class="anchor" href="#counting-sponsored-message-views" id="counting-sponsored-message-views" name="counting-sponsored-message-views"><i class="anchor-icon"></i></a>Counting sponsored message views</h4>