diff --git a/data/web/corefork.telegram.org/api/dice.html b/data/web/corefork.telegram.org/api/dice.html
index 1e7e7f1933..d1c56ec40c 100644
--- a/data/web/corefork.telegram.org/api/dice.html
+++ b/data/web/corefork.telegram.org/api/dice.html
@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>Dice</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="Telegram supports sending [animated dice](https://telegram.org/blog/folders#and-one-more-thing) emojis.">
+    <meta property="description" content="Telegram supports sending animated dice emojis.">
     <meta property="og:title" content="Dice">
     <meta property="og:image" content="">
-    <meta property="og:description" content="Telegram supports sending [animated dice](https://telegram.org/blog/folders#and-one-more-thing) emojis.">
+    <meta property="og:description" content="Telegram supports sending animated dice emojis.">
     <link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
 <link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
diff --git a/data/web/corefork.telegram.org/api/discussion.html b/data/web/corefork.telegram.org/api/discussion.html
index 36f5c3c089..c487931b18 100644
--- a/data/web/corefork.telegram.org/api/discussion.html
+++ b/data/web/corefork.telegram.org/api/discussion.html
@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>Discussion groups</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="[Groups](/api/channel) can be associated to a [channel](/api/channel) as a [discussion group](https://telegram.org/blog/privacy-discussions-web-bots), to allow users to discuss about posts.">
+    <meta property="description" content="Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.">
     <meta property="og:title" content="Discussion groups">
     <meta property="og:image" content="">
-    <meta property="og:description" content="[Groups](/api/channel) can be associated to a [channel](/api/channel) as a [discussion group](https://telegram.org/blog/privacy-discussions-web-bots), to allow users to discuss about posts.">
+    <meta property="og:description" content="Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.">
     <link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
 <link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
@@ -84,7 +84,7 @@ Before linking a supergroup to a channel, access to the supergroup's old message
 
 <a href='/method/channels.toggleJoinToSend'>channels.toggleJoinToSend</a>#e4cb9580 channel:<a href='/type/InputChannel'>InputChannel</a> enabled:<a href='/type/Bool'>Bool</a> = <a href='/type/Updates'>Updates</a>;</code></pre>
 <p>Admins may use <a href="/method/channels.toggleJoinToSend">channels.toggleJoinToSend</a> to force users to join a discussion group before commenting.<br>
-The <a href="/constructor/channel"><code>channel.join_to_send</code></a> flag will be set accordingly, and all attempts by non-members to send a message to the group will return a <code>CHAT_GUEST_SEND_FORBIDDEN</code> RPC error.  </p></div>
+The <a href="/constructor/channel"><code>channel.join_to_send</code></a> flag will be set accordingly, and all attempts by non-members to send a message to the group will return a <code>CHAT_GUEST_SEND_FORBIDDEN</code> RPC error.</p></div>
   
 </div>
           
diff --git a/data/web/corefork.telegram.org/api/emoji-status.html b/data/web/corefork.telegram.org/api/emoji-status.html
index 779fb40dce..ecb1f36c67 100644
--- a/data/web/corefork.telegram.org/api/emoji-status.html
+++ b/data/web/corefork.telegram.org/api/emoji-status.html
@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>Emoji status</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="Telegram allows users to set an emoticon or a [custom emoji](/api/custom-emoji) as status, to show next to their name in chats and profiles.">
+    <meta property="description" content="Telegram allows users to set an emoticon or a custom emoji as status, to show next to their name in chats and profiles.">
     <meta property="og:title" content="Emoji status">
     <meta property="og:image" content="">
-    <meta property="og:description" content="Telegram allows users to set an emoticon or a [custom emoji](/api/custom-emoji) as status, to show next to their name in chats and profiles.">
+    <meta property="og:description" content="Telegram allows users to set an emoticon or a custom emoji as status, to show next to their name in chats and profiles.">
     <link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
 <link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
@@ -85,7 +85,7 @@
 
 <a href='/method/account.getDefaultEmojiStatuses'>account.getDefaultEmojiStatuses</a>#d6753386 hash:<a href='/type/long'>long</a> = <a href='/type/account.EmojiStatuses'>account.EmojiStatuses</a>;</code></pre>
 <p>A set of standard statuses can be fetched by passing <a href="/constructor/inputStickerSetEmojiDefaultStatuses">inputStickerSetEmojiDefaultStatuses</a> to <a href="/method/messages.getStickerSet">messages.getStickerSet</a>, as specified in the <a href="/api/stickers">stickerset documentation »</a>.  </p>
-<p><a href="/method/account.getDefaultEmojiStatuses">account.getDefaultEmojiStatuses</a> can also be used to get a list of featured emoji statuses, from multiple featured custom emoji stickersets.  </p></div>
+<p><a href="/method/account.getDefaultEmojiStatuses">account.getDefaultEmojiStatuses</a> can also be used to get a list of featured emoji statuses, from multiple featured custom emoji stickersets.</p></div>
   
 </div>
           
diff --git a/data/web/corefork.telegram.org/api/recent-actions.html b/data/web/corefork.telegram.org/api/recent-actions.html
index f9616aff62..6f78a7bfae 100644
--- a/data/web/corefork.telegram.org/api/recent-actions.html
+++ b/data/web/corefork.telegram.org/api/recent-actions.html
@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>Admin log</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="Both supergroups and channels offer a so-called [admin log](https://telegram.org/blog/admin-revolution), a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.">
+    <meta property="description" content="Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.">
     <meta property="og:title" content="Admin log">
     <meta property="og:image" content="">
-    <meta property="og:description" content="Both supergroups and channels offer a so-called [admin log](https://telegram.org/blog/admin-revolution), a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.">
+    <meta property="og:description" content="Both supergroups and channels offer a so-called admin log, a log of recent relevant supergroup and channel actions, like the modification of group/channel settings or information on behalf of an admin, user kicks and bans, and more.">
     <link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
 <link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
@@ -93,7 +93,7 @@
 <a href='/method/channels.getAdminLog'>channels.getAdminLog</a>#33ddf480 flags:<a href='/type/%23'>#</a> channel:<a href='/type/InputChannel'>InputChannel</a> q:<a href='/type/string'>string</a> events_filter:flags.0?<a href='/type/ChannelAdminLogEventsFilter'>ChannelAdminLogEventsFilter</a> admins:flags.1?<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/InputUser'>InputUser</a>&gt; max_id:<a href='/type/long'>long</a> min_id:<a href='/type/long'>long</a> limit:<a href='/type/int'>int</a> = <a href='/type/channels.AdminLogResults'>channels.AdminLogResults</a>;</code></pre>
 <p><a href="/method/channels.getAdminLog">channels.getAdminLog</a> can be used to list recent admin activity.<br>
 A <a href="/constructor/channelAdminLogEventsFilter">channelAdminLogEventsFilter</a> can be used to filter out actions of a certain type, and the <code>admins</code> field can be used to show only actions by certain admins.<br>
-<code>q</code> can also be used to filter only logs matching a query string.  </p></div>
+<code>q</code> can also be used to filter only logs matching a query string.</p></div>
   
 </div>
           
diff --git a/data/web/corefork.telegram.org/api/threads.html b/data/web/corefork.telegram.org/api/threads.html
index 705c41e117..383cd0d12a 100644
--- a/data/web/corefork.telegram.org/api/threads.html
+++ b/data/web/corefork.telegram.org/api/threads.html
@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>Threads</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="Telegram allows commenting on a [channel post](/api/channel) or on a generic [supergroup message](/api/channel), thanks to message threads.">
+    <meta property="description" content="Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.">
     <meta property="og:title" content="Threads">
     <meta property="og:image" content="">
-    <meta property="og:description" content="Telegram allows commenting on a [channel post](/api/channel) or on a generic [supergroup message](/api/channel), thanks to message threads.">
+    <meta property="og:description" content="Telegram allows commenting on a channel post or on a generic supergroup message, thanks to message threads.">
     <link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
 <link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
@@ -106,7 +106,7 @@ Its ID for main and testing endpoints can be seen in the <a href="https://github
 </ul>
 </li>
 </ul>
-<p>Clients should display messages coming from <code>@replies</code> as a read-only supergroup, with each reply displayed as a separate message from the author of the reply, with a "View in chat" button like for channel comments.  </p></div>
+<p>Clients should display messages coming from <code>@replies</code> as a read-only supergroup, with each reply displayed as a separate message from the author of the reply, with a "View in chat" button like for channel comments.</p></div>
   
 </div>