Update content of files

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

@@ -94,7 +94,7 @@ A <code>BOOST_NOT_MODIFIED</code> RPC error will be returned when calling any of
 <p>Everything works exactly the same as when <a href="/api/stories#posting-stories">posting stories as a user</a>, with the only difference that clients should pass the appropriate <a href="/constructor/inputPeerChannel">inputPeerChannel</a> instead of <a href="/constructor/inputPeerSelf">inputPeerSelf</a> to <a href="/method/stories.canSendStory">stories.canSendStory</a>, <a href="/method/stories.sendStory">stories.sendStory</a> and all the other story methods, see the <a href="/api/stories#posting-stories">main documentation »</a> for more info.  </p>
 <p>Use <a href="/method/stories.getChatsToSend">stories.getChatsToSend</a> to obtain a list of channels where the user can post stories; <a href="/method/stories.canSendStory">stories.canSendStory</a> must still be used before uploading a story to make sure no other limit was reached, as described in the <a href="/api/stories#posting-stories">main documentation »</a>.</p>
 <h4><a class="anchor" href="#changing-message-accents" id="changing-message-accents" name="changing-message-accents"><i class="anchor-icon"></i></a>Changing message accents</h4>
-<p>After reaching at least boost level <a href="/api/config#channel-color-level-min">channel_color_level_min »</a>, channels gain the ability to change their <a href="/api/colors">message accent palette »</a>.</p></div>
+<p>After reaching at least boost level <a href="/api/config#channel-color-level-min">channel_color_level_min »</a>, channels gain the ability to change their <a href="/api/colors">message accent and profile palettes »</a>.</p></div>
   
 </div>
           

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

@@ -82,7 +82,7 @@ If the <code>hidden</code> flag is set it should not be displayed as an option t
 <p>Use <a href="/method/account.updateColor">account.updateColor</a> to update the color palette of the current account's message accents and/or profile page; note that the current account must be subscribed to <a href="/api/premium">Telegram Premium</a> in order to call the method.<br>
 Use <a href="/method/channels.updateColor">channels.updateColor</a> to update the color palette of a channel's message accents; note that channels have to be <a href="/api/boost">boosted »</a> at least to level <a href="/api/config#channel-color-level-min">channel_color_level_min »</a> in order to use this method.  </p>
 <p>The chosen message accent palette will be visible to other users in the <a href="/constructor/channel">channel</a>.<code>color</code> and <a href="/constructor/user">user</a>.<code>color</code> fields.  </p>
-<p>User profile palettes will be visible in the <a href="/constructor/user">user</a>.<code>profile_color</code> field.</p></div>
+<p>The chosen user and channel profile palettes will be visible in the <a href="/constructor/user">user</a>.<code>profile_color</code> and <a href="/constructor/channel">channel</a>.<code>profile_color</code> fields.</p></div>
   
 </div>
           

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

@@ -69,7 +69,7 @@ These methods allow reducing the latency for calls which require strict ordering
 </div>
 <p>They may be used, for example, when a client attempts to send messages that accumulated while waiting for the Internet connection to be restored for a long time. In this case, the 32-bit number <code>0xcb9f372d</code> must be added before the method number in each request, followed by a 64-bit message identifier, msg_id, which contains the previous request in the queue. </p>
 <p>The second method is similar, except it takes several messages that must be successfully processed before the current one.</p>
-<p>If the waiting period exceeds 0.5 seconds (this value may change in the future) and no result has appeared, the method will return the 400/500 <code>MSG_WAIT_TIMEOUT</code> error: handle this error by resending the request, still wrapped in the same <code>invokeAfterMsg</code>/<code>invokeAfterMsgs</code> constructor with the same <code>id</code>/<code>ids</code>.  </p>
+<p>If the waiting period exceeds 0.5 seconds (this value may change in the future) and no result has appeared, the method will return the <code>MSG_WAIT_TIMEOUT</code> error: handle this error by resending the request, still wrapped in the same <code>invokeAfterMsg</code>/<code>invokeAfterMsgs</code> constructor with the same <code>id</code>/<code>ids</code>.  </p>
 <p>If any of the previous queries mentioned in <code>msg_ids</code> or <code>msg_id</code> fails (i.e. an RPC error is emitted by a query, including <code>FLOOD_WAIT_</code> errors), a <code>MSG_WAIT_FAILED</code> error will be returned for the current request: the simplest way to handle it is to simply enforce local synchronization, by waiting for a response from all previous <code>msg_ids</code>/<code>msg_id</code> before resending the request.  </p>
 <p>If and only if any of the previous requests also failed with <code>MSG_WAIT_FAILED</code>/<code>MSG_WAIT_TIMEOUT</code> errors and require resending, wrap the current request in another <code>invokeAfterMsg</code>/<code>invokeAfterMsgs</code> constructor with the new IDs of the previous requests, resent along with the current one.  </p>
 <h4><a class="anchor" href="#scenario-1" id="scenario-1" name="scenario-1"><i class="anchor-icon"></i></a>Scenario 1</h4>

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

@@ -80,7 +80,7 @@
 <tr>
 <td><strong>has_settings</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.1?<a href="/constructor/true">true</a></td>
-<td>True, if the bot supports the <a href="/api/bots/webapps#settings-button-pressed">"settings_button_pressed" event »</a></td>
+<td>Deprecated flag, can be ignored.</td>
 </tr>
 <tr>
 <td><strong>request_write_access</strong></td>

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

@@ -89,17 +89,17 @@
 <tr>
 <td><strong>quote_text</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.2?<a href="/type/string">string</a></td>
-<td> </td>
+<td>Used to quote-reply to only a certain section (specified here) of the original message.</td>
 </tr>
 <tr>
 <td><strong>quote_entities</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.3?<a href="/type/Vector%20t">Vector</a>&lt;<a href="/type/MessageEntity">MessageEntity</a>&gt;</td>
-<td><a href="/api/entities">Message entities for styled text</a></td>
+<td><a href="/api/entities">Message entities for styled text</a> from the <code>quote_text</code> field.</td>
 </tr>
 <tr>
 <td><strong>quote_offset</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.4?<a href="/type/int">int</a></td>
-<td> </td>
+<td>Offset of the message <code>quote_text</code> within the original message (in <a href="/api/entities#entity-length">UTF-16 code units</a>).</td>
 </tr>
 </tbody>
 </table>

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

@@ -84,7 +84,7 @@
 <tr>
 <td><strong>quote</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.9?<a href="/constructor/true">true</a></td>
-<td> </td>
+<td>Whether this message is quoting a part of another message.</td>
 </tr>
 <tr>
 <td><strong>reply_to_msg_id</strong></td>
@@ -99,12 +99,12 @@
 <tr>
 <td><strong>reply_from</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.5?<a href="/type/MessageFwdHeader">MessageFwdHeader</a></td>
-<td> </td>
+<td>When replying to a message sent by a certain peer to another chat, contains info about the peer that originally sent the message to that other chat.</td>
 </tr>
 <tr>
 <td><strong>reply_media</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.8?<a href="/type/MessageMedia">MessageMedia</a></td>
-<td> </td>
+<td>When replying to a media sent by a certain peer to another chat, contains the media of the replied-to message.</td>
 </tr>
 <tr>
 <td><strong>reply_to_top_id</strong></td>
@@ -114,17 +114,17 @@
 <tr>
 <td><strong>quote_text</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.6?<a href="/type/string">string</a></td>
-<td> </td>
+<td>Used to quote-reply to only a certain section (specified here) of the original message.</td>
 </tr>
 <tr>
 <td><strong>quote_entities</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.7?<a href="/type/Vector%20t">Vector</a>&lt;<a href="/type/MessageEntity">MessageEntity</a>&gt;</td>
-<td><a href="/api/entities">Message entities for styled text</a></td>
+<td><a href="/api/entities">Message entities for styled text</a> from the <code>quote_text</code> field.</td>
 </tr>
 <tr>
 <td><strong>quote_offset</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.10?<a href="/type/int">int</a></td>
-<td> </td>
+<td>Offset of the message <code>quote_text</code> within the original message (in <a href="/api/entities#entity-length">UTF-16 code units</a>).</td>
 </tr>
 </tbody>
 </table>

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

@@ -128,7 +128,6 @@ MTProto v.1.0 is deprecated and is currently being phased out.</p>
 <li><code>msg_detailed_info</code></li>
 <li><code>msg_new_detailed_info</code></li>
 <li><code>msg_resend_req</code></li>
-<li><code>msg_resend_ans_req</code></li>
 </ul>
 <h4><a class="anchor" href="#message-key-msg-key" id="message-key-msg-key" name="message-key-msg-key"><i class="anchor-icon"></i></a>Message Key (msg_key)</h4>
 <p>In <strong>MTProto 2.0</strong>, the middle 128 bits of the SHA-256 hash of the message to be encrypted (including the internal header and the <em>padding bytes</em> for MTProto 2.0), prepended by a 32-byte fragment of the authorization key.</p>

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

@@ -125,7 +125,16 @@ Clients should group acknowledgments, state requests and message resend requests
 <p>At the same time, the <code>max_delay</code> parameter has higher priority than <code>wait_after</code>, and <code>max_wait</code> has higher priority than <code>max_delay</code>.</p>
 <p>This message does not require a response or an acknowledgement. If the container transmitted over HTTP carries several such messages, the behavior is undefined (in fact, the latest parameter will be used). </p>
 <p>If no <code>http_wait</code> is present in container, default values <code>max_delay=0</code> (milliseconds), <code>wait_after=0</code> (milliseconds), and <code>max_wait=25000</code> (milliseconds) are used. </p>
-<p>If the client's ping of the server takes a long time, it may make sense to set <code>max_delay</code> to a value that is comparable in magnitude to ping time.</p></div>
+<p>If the client's ping of the server takes a long time, it may make sense to set <code>max_delay</code> to a value that is comparable in magnitude to ping time.</p>
+<h2><a class="anchor" href="#destruction-of-a-permanent-auth-key" id="destruction-of-a-permanent-auth-key" name="destruction-of-a-permanent-auth-key"><i class="anchor-icon"></i></a>Destruction of a permanent auth key</h2>
+<pre><code>destroy_auth_key_ok#f660e1d4 = DestroyAuthKeyRes;
+destroy_auth_key_none#0a9f2259 = DestroyAuthKeyRes;
+destroy_auth_key_fail#ea109b13 = DestroyAuthKeyRes;
+
+---functions---
+
+destroy_auth_key#d1435160 = DestroyAuthKeyRes;</code></pre>
+<p><code>destroy_auth_key</code> should be called whenever a permanent auth key isn't needed anymore, such as after the user was logged out.</p></div>
   
 </div>