Update content of files

data/web/corefork.telegram.org.html

@@ -223,6 +223,8 @@ This allows the server to filter messages based on a text query, and even on the
 <p>Telegram <a href="/api/channel">channel</a> administrators may launch giveaways to randomly distribute <a href="/api/premium">Telegram Premium</a> subscriptions and other gifts among their followers, in exchange for <a href="/api/boost">boosts</a>.</p>
 <h4><a class="anchor" href="#action-bar" id="action-bar" name="action-bar"><i class="anchor-icon"></i></a><a href="/api/action-bar">Action bar</a></h4>
 <p>Sometimes, when interacting with Telegram users via private or secret chats, an action bar must be shown on top of the chat, offering convenient action buttons or notices regarding the user.</p>
+<h4><a class="anchor" href="#saved-messages" id="saved-messages" name="saved-messages"><i class="anchor-icon"></i></a><a href="/api/saved-messages">Saved messages</a></h4>
+<p>The Saved Messages chat allows users to bookmark messages and media: it's a personal cloud storage for any messages or media you may want to send or forward there.  </p>
 <h3><a class="anchor" href="#contacts" id="contacts" name="contacts"><i class="anchor-icon"></i></a><a href="/api/contacts">Contacts</a></h3>
 <p>Working with contacts in the API.</p>
 <h3><a class="anchor" href="#blocklist" id="blocklist" name="blocklist"><i class="anchor-icon"></i></a><a href="/api/block">Blocklist</a></h3>

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

@@ -223,6 +223,8 @@ This allows the server to filter messages based on a text query, and even on the
 <p>Telegram <a href="/api/channel">channel</a> administrators may launch giveaways to randomly distribute <a href="/api/premium">Telegram Premium</a> subscriptions and other gifts among their followers, in exchange for <a href="/api/boost">boosts</a>.</p>
 <h4><a class="anchor" href="#action-bar" id="action-bar" name="action-bar"><i class="anchor-icon"></i></a><a href="/api/action-bar">Action bar</a></h4>
 <p>Sometimes, when interacting with Telegram users via private or secret chats, an action bar must be shown on top of the chat, offering convenient action buttons or notices regarding the user.</p>
+<h4><a class="anchor" href="#saved-messages" id="saved-messages" name="saved-messages"><i class="anchor-icon"></i></a><a href="/api/saved-messages">Saved messages</a></h4>
+<p>The Saved Messages chat allows users to bookmark messages and media: it's a personal cloud storage for any messages or media you may want to send or forward there.  </p>
 <h3><a class="anchor" href="#contacts" id="contacts" name="contacts"><i class="anchor-icon"></i></a><a href="/api/contacts">Contacts</a></h3>
 <p>Working with contacts in the API.</p>
 <h3><a class="anchor" href="#blocklist" id="blocklist" name="blocklist"><i class="anchor-icon"></i></a><a href="/api/block">Blocklist</a></h3>

data/web/corefork.telegram.org/api/saved-messages.html

@@ -111,9 +111,9 @@ To add new dialogs to the saved dialog list, simply forward messages from any no
 </li>
 </ul>
 <p>Saving messages from private chats with users with forward privacy enabled will add them to a saved dialog entry of a special anonymous user with <code>id=2666000</code>.  </p>
-<p>Sending (not forwarding) new messages directly to ourselves will add them to a saved dialog entry with ourselves.  </p>
+<p>Sending (not forwarding from another dialog) new messages directly to ourselves will add them to a saved dialog entry with ourselves.  </p>
 <p>A set of methods can then be used to obtain this dialog list, pin/unpin dialogs inside of it, view and remove messages from saved dialogs: <a href="/method/messages.getSavedDialogs">messages.getSavedDialogs</a>, <a href="/method/messages.getSavedHistory">messages.getSavedHistory</a>, <a href="/method/messages.deleteSavedHistory">messages.deleteSavedHistory</a>, <a href="/method/messages.getPinnedSavedDialogs">messages.getPinnedSavedDialogs</a>, <a href="/method/messages.toggleSavedDialogPin">messages.toggleSavedDialogPin</a>, <a href="/method/messages.reorderPinnedSavedDialogs">messages.reorderPinnedSavedDialogs</a> work just like their counterparts <a href="/method/messages.getDialogs">messages.getDialogs</a>, <a href="/method/messages.getHistory">messages.getHistory</a>, <a href="/method/messages.deleteHistory">messages.deleteHistory</a>, <a href="/method/messages.getPinnedDialogs">messages.getPinnedDialogs</a>, <a href="/method/messages.toggleDialogPin">messages.toggleDialogPin</a>, <a href="/method/messages.reorderPinnedDialogs">messages.reorderPinnedDialogs</a>, with the sole difference that they affect the saved dialog list, instead of the main dialog list.  </p>
-<p>To search for messages within a saved dialog, use the usual <a href="/method/messages.search">messages.search</a>, <a href="/method/messages.search">messages.search</a>, <a href="/method/messages.getSearchResultsCalendar">messages.getSearchResultsCalendar</a>, <a href="/method/messages.getSearchResultsPositions">messages.getSearchResultsPositions</a> methods with <code>peer</code>=<a href="/constructor/inputPeerSelf">inputPeerSelf</a> and <code>saved_peer_id=id of the saved dialog</code>.</p></div>
+<p>To search for messages within a saved dialog, use the usual <a href="/method/messages.search">messages.search</a>, <a href="/method/messages.search">messages.search</a>, <a href="/method/messages.getSearchResultsCalendar">messages.getSearchResultsCalendar</a>, <a href="/method/messages.getSearchResultsPositions">messages.getSearchResultsPositions</a> methods with <code>peer</code>=<a href="/constructor/inputPeerSelf">inputPeerSelf</a> and <code>saved_peer_id</code>=id of the saved dialog.</p></div>
   
 </div>
           

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

@@ -79,7 +79,7 @@
 <tr>
 <td><strong>saved_out</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.11?<a href="/constructor/true">true</a></td>
-<td>Only for messages forwarded to <a href="/api/saved-messages">saved messages »</a>, set if the original message was outgoing (though the message may have been originally outgoing even if this flag is not set, for example if <code>from_id</code> points to the current user).</td>
+<td>Only for messages forwarded to <a href="/api/saved-messages">saved messages »</a>, set if the original message was outgoing (though the message may have been originally outgoing even if this flag is not set, if <code>from_id</code> points to the current user).</td>
 </tr>
 <tr>
 <td><strong>from_id</strong></td>
@@ -109,17 +109,17 @@
 <tr>
 <td><strong>saved_from_peer</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.4?<a href="/type/Peer">Peer</a></td>
-<td>Only for messages forwarded to <a href="/api/saved-messages">saved messages »</a>, full info about the user/channel that originally sent the message</td>
+<td>Only for messages forwarded to <a href="/api/saved-messages">saved messages »</a>, contains the dialog where the message was originally sent.</td>
 </tr>
 <tr>
 <td><strong>saved_from_msg_id</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>Only for messages forwarded to <a href="/api/saved-messages">saved messages »</a>, contains the original ID of the forwarded message.</td>
+<td>Only for messages forwarded to <a href="/api/saved-messages">saved messages »</a>, contains the original ID of the message in <code>saved_from_peer</code>.</td>
 </tr>
 <tr>
 <td><strong>saved_from_id</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.8?<a href="/type/Peer">Peer</a></td>
-<td>Only for messages forwarded to <a href="/api/saved-messages">saved messages »</a>, contains the original dialog's peer.</td>
+<td>Only for messages forwarded to <a href="/api/saved-messages">saved messages »</a>, contains the sender of the original message.</td>
 </tr>
 <tr>
 <td><strong>saved_from_name</strong></td>