Update content of files

data/web/corefork.telegram.org/api/layers.html

@@ -62,7 +62,7 @@
 <li><a href="/api/takeout">Working with the takeout API »</a></li>
 <li><a href="/api/saved-messages">Working with saved messages »</a></li>
 </ul>
-<p>Also added documentation for <a href="/api/files#streamed-uploads">streamed uploads</a> and improved the <a href="/api/invoking#sequential-requests">method queue</a> documentation.</p>
+<p>Also added documentation for <a href="/api/files#streamed-uploads">streamed uploads</a> and improved the docs for <a href="/api/invoking#sequential-requests">method queue</a>, <a href="/mtproto/mtproto-transports">quick ACKs</a> and <a href="/mtproto/description#message-sequence-number-msg-seqno">content-related messages</a>.</p>
 <p>The <a href="/api/errors#error-database">RPC error database »</a> was also updated.</p>
 <p>The following new deep links were added:</p>
 <ul>

data/web/corefork.telegram.org/constructor/userFull.html

@@ -124,7 +124,7 @@
 <tr>
 <td><strong>wallpaper_overridden</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.28?<a href="/constructor/true">true</a></td>
-<td>Whether the other user has chosen a custom wallpaper for us using <a href="/method/messages.setChatWallPaper">messages.setChatWallPaper</a> and the <code>for_both</code> flag, see <a href="/api/wallpapers#installing-wallpapers-in-a-specific-chator-channel">here »</a> for more info.</td>
+<td>Whether the other user has chosen a custom wallpaper for us using <a href="/method/messages.setChatWallPaper">messages.setChatWallPaper</a> and the <code>for_both</code> flag, see <a href="/api/wallpapers#installing-wallpapers-in-a-specific-chat-or-channel">here »</a> for more info.</td>
 </tr>
 <tr>
 <td><strong>id</strong></td>

data/web/corefork.telegram.org/method/messages.sendMessage.html

@@ -171,7 +171,7 @@
 <tr>
 <td>400</td>
 <td>ADMIN_RIGHTS_EMPTY</td>
-<td> </td>
+<td>The chatAdminRights constructor passed in keyboardButtonRequestPeer.peer_type.user_admin_rights has no rights set (i.e. flags is 0).</td>
 </tr>
 <tr>
 <td>400</td>
@@ -319,6 +319,11 @@
 <td>Invalid poll option provided.</td>
 </tr>
 <tr>
+<td>406</td>
+<td>PRIVACY_PREMIUM_REQUIRED</td>
+<td>You need a <a href="/api/premium">Telegram Premium subscription</a> to send a message to this user.</td>
+</tr>
+<tr>
 <td>500</td>
 <td>RANDOM_ID_DUPLICATE</td>
 <td>You provided a random ID that was already used.</td>
@@ -428,7 +433,9 @@
 <h4><a class="anchor" href="#discussion-groups" id="discussion-groups" name="discussion-groups"><i class="anchor-icon"></i></a><a href="/api/discussion">Discussion groups</a></h4>
 <p>Groups can be associated to a channel as a discussion group, to allow users to discuss about posts.</p>
 <h4><a class="anchor" href="#error-handling" id="error-handling" name="error-handling"><i class="anchor-icon"></i></a><a href="/api/errors">Error handling </a></h4>
-<p>How to handle API return errors correctly.</p></div>
+<p>How to handle API return errors correctly.</p>
+<h4><a class="anchor" href="#telegram-premium" id="telegram-premium" name="telegram-premium"><i class="anchor-icon"></i></a><a href="/api/premium">Telegram Premium</a></h4>
+<p>Telegram Premium is an optional subscription service that unlocks additional exclusive client-side and API-side features, while helping support the development of the app.</p></div>
   
 </div>
           

data/web/corefork.telegram.org/mtproto/description.html

@@ -102,7 +102,7 @@ MTProto v.1.0 is deprecated and is currently being phased out.</p>
 <p>Thus, the content-relatedness of an incoming MTProto message can simply be determined by checking the value of the least-significant bit of the seqno of the message (<code>message.isContentRelated = (message.seqNo &amp; 1) == 1</code>).  </p>
 <p>A container is always generated after its entire contents; therefore, its sequence number is greater than or equal to the sequence numbers of the messages contained in it.  </p>
 <h5><a class="anchor" href="#content-related-message" id="content-related-message" name="content-related-message"><i class="anchor-icon"></i></a>Content-related Message</h5>
-<p>When receiving an MTProto message that is marked as content-related by setting the least-significant bit of the <a href="#message-sequence-number-msg_seqno">seqno</a>, the receiving party <strong>must</strong> acknowledge it in some way.  </p>
+<p>When receiving an MTProto message that is marked as content-related by setting the least-significant bit of the <a href="#message-sequence-number-msg-seqno">seqno</a>, the receiving party <strong>must</strong> acknowledge it in some way.  </p>
 <p>When the receiving party is the client, this must be done through <code>msgs_ack</code> constructors.  </p>
 <p>When the receiving party is the server, this is usually done through <code>msgs_ack</code> constructors, but may also be done using the reply of a method, or an error, or some other way, as specified by the documentation of each method or constructor.  </p>
 <p>When a TCP transport is used, the content-relatedness of constructors affects the server's behavior: the server will resend not-yet acknowledged content-related messages to a new connection if the current connection is closed and then re-opened.  </p>