diff --git a/data/web/blogfork.telegram.org/cdn.html b/data/web/blogfork.telegram.org/cdn.html
index f9bdf638ec..79a9e0df57 100644
--- a/data/web/blogfork.telegram.org/cdn.html
+++ b/data/web/blogfork.telegram.org/cdn.html
@@ -136,7 +136,10 @@
 <td>The master DC did not accept the <code>request_token</code> from the CDN DC. Continue downloading the file from the master DC using upload.getFile.</td>
 </tr>
 </tbody>
-</table></div>
+</table>
+<h3><a class="anchor" href="#testing-cdn-redirects" id="testing-cdn-redirects" name="testing-cdn-redirects"><i class="anchor-icon"></i></a>Testing CDN redirects</h3>
+<p>You may test CDN file redirects by logging into the <a href="/api/auth#test-accounts">test DCs</a> with a DC 2 account (phone number <code>999662YYYY</code>, where YYYY are random numbers, login code <code>22222</code>), uploading and then redownloading the uploaded file.  </p>
+<p>Make sure the chosen test account doesn't have a Telegram Premium test subscription, as CDN file downloads are disabled on the test DCs if a Telegram Premium test subscription is enabled (you can check this by making sure the <a href="/constructor/user">user</a> returned by a <a href="/method/users.getUsers">users.getUsers</a> call with <a href="/constructor/inputUserSelf">inputUserSelf</a> does not have the <code>premium</code> flag set).</p></div>
   
 </div>
           
diff --git a/data/web/blogfork.telegram.org/constructor/messageEntityMention.html b/data/web/blogfork.telegram.org/constructor/messageEntityMention.html
index f171b8aa31..dd6d94e1a5 100644
--- a/data/web/blogfork.telegram.org/constructor/messageEntityMention.html
+++ b/data/web/blogfork.telegram.org/constructor/messageEntityMention.html
@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>messageEntityMention</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="Message entity mentioning the current user">
+    <meta property="description" content="Message entity mentioning a user by @username; messageEntityMentionName can also be used to mention users by their ID.">
     <meta property="og:title" content="messageEntityMention">
     <meta property="og:image" content="">
-    <meta property="og:description" content="Message entity mentioning the current user">
+    <meta property="og:description" content="Message entity mentioning a user by @username; messageEntityMentionName can also be used to mention users by their ID.">
     <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,9 @@
 <h4><a class="anchor" href="#styled-text-with-message-entities" id="styled-text-with-message-entities" name="styled-text-with-message-entities"><i class="anchor-icon"></i></a><a href="/api/entities">Styled text with message entities</a></h4>
 <p>How to create styled text with message entities</p>
 <h4><a class="anchor" href="#mentions" id="mentions" name="mentions"><i class="anchor-icon"></i></a><a href="/api/mentions">Mentions</a></h4>
-<p>Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.</p></div>
+<p>Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.</p>
+<h4><a class="anchor" href="#messageentitymentionname" id="messageentitymentionname" name="messageentitymentionname"><i class="anchor-icon"></i></a><a href="/constructor/messageEntityMentionName">messageEntityMentionName</a></h4>
+<p>Message entity representing a <a href="/api/mentions">user mention</a>: for <em>creating</em> a mention use <a href="/constructor/inputMessageEntityMentionName">inputMessageEntityMentionName</a>.</p></div>
   
 </div>
           
diff --git a/data/web/core.telegram.org/cdn.html b/data/web/core.telegram.org/cdn.html
index f9bdf638ec..79a9e0df57 100644
--- a/data/web/core.telegram.org/cdn.html
+++ b/data/web/core.telegram.org/cdn.html
@@ -136,7 +136,10 @@
 <td>The master DC did not accept the <code>request_token</code> from the CDN DC. Continue downloading the file from the master DC using upload.getFile.</td>
 </tr>
 </tbody>
-</table></div>
+</table>
+<h3><a class="anchor" href="#testing-cdn-redirects" id="testing-cdn-redirects" name="testing-cdn-redirects"><i class="anchor-icon"></i></a>Testing CDN redirects</h3>
+<p>You may test CDN file redirects by logging into the <a href="/api/auth#test-accounts">test DCs</a> with a DC 2 account (phone number <code>999662YYYY</code>, where YYYY are random numbers, login code <code>22222</code>), uploading and then redownloading the uploaded file.  </p>
+<p>Make sure the chosen test account doesn't have a Telegram Premium test subscription, as CDN file downloads are disabled on the test DCs if a Telegram Premium test subscription is enabled (you can check this by making sure the <a href="/constructor/user">user</a> returned by a <a href="/method/users.getUsers">users.getUsers</a> call with <a href="/constructor/inputUserSelf">inputUserSelf</a> does not have the <code>premium</code> flag set).</p></div>
   
 </div>
           
diff --git a/data/web/core.telegram.org/constructor/messageEntityMention.html b/data/web/core.telegram.org/constructor/messageEntityMention.html
index f171b8aa31..dd6d94e1a5 100644
--- a/data/web/core.telegram.org/constructor/messageEntityMention.html
+++ b/data/web/core.telegram.org/constructor/messageEntityMention.html
@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>messageEntityMention</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="Message entity mentioning the current user">
+    <meta property="description" content="Message entity mentioning a user by @username; messageEntityMentionName can also be used to mention users by their ID.">
     <meta property="og:title" content="messageEntityMention">
     <meta property="og:image" content="">
-    <meta property="og:description" content="Message entity mentioning the current user">
+    <meta property="og:description" content="Message entity mentioning a user by @username; messageEntityMentionName can also be used to mention users by their ID.">
     <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,9 @@
 <h4><a class="anchor" href="#styled-text-with-message-entities" id="styled-text-with-message-entities" name="styled-text-with-message-entities"><i class="anchor-icon"></i></a><a href="/api/entities">Styled text with message entities</a></h4>
 <p>How to create styled text with message entities</p>
 <h4><a class="anchor" href="#mentions" id="mentions" name="mentions"><i class="anchor-icon"></i></a><a href="/api/mentions">Mentions</a></h4>
-<p>Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.</p></div>
+<p>Telegram allows mentioning other users in case of urgent duckling matters, and quickly navigating to those mentions in order to read them as swiftly as possible.</p>
+<h4><a class="anchor" href="#messageentitymentionname" id="messageentitymentionname" name="messageentitymentionname"><i class="anchor-icon"></i></a><a href="/constructor/messageEntityMentionName">messageEntityMentionName</a></h4>
+<p>Message entity representing a <a href="/api/mentions">user mention</a>: for <em>creating</em> a mention use <a href="/constructor/inputMessageEntityMentionName">inputMessageEntityMentionName</a>.</p></div>
   
 </div>