From f57eed78417fb5ea532cdab1a548a329d07bfe16 Mon Sep 17 00:00:00 2001
From: GitHub Action <github-action@users.noreply.github.com>
Date: Wed, 24 Jul 2024 17:37:50 +0000
Subject: [PATCH] Update content of files

---
 data/web/corefork.telegram.org/api/layers.html | 1 +
 data/web/corefork.telegram.org/api/peers.html  | 5 ++++-
 2 files changed, 5 insertions(+), 1 deletion(-)

diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html
index fdaf8534ad..85216fe4d5 100644
--- a/data/web/corefork.telegram.org/api/layers.html
+++ b/data/web/corefork.telegram.org/api/layers.html
@@ -627,6 +627,7 @@
 <a href="/method/channels.setBoostsToUnblockRestrictions">channels.setBoostsToUnblockRestrictions</a>#ad399cee channel:<a href="/type/InputChannel">InputChannel</a> boosts:<a href="/type/int">int</a> = <a href="/type/Updates">Updates</a>;
 <a href="/method/channels.setEmojiStickers">channels.setEmojiStickers</a>#3cd930b7 channel:<a href="/type/InputChannel">InputChannel</a> stickerset:<a href="/type/InputStickerSet">InputStickerSet</a> = <a href="/type/Bool">Bool</a>;<br></code></pre></div>
 <h3><a class="anchor" href="#layer-171" id="layer-171" name="layer-171"><i class="anchor-icon"></i></a><a href="/schema?layer=171">Layer 171</a></h3>
+<p>This layer introduces <a href="/api/saved-messages#tags">saved message tags »</a> and adds support for the "Channels" tab in the <a href="/api/search#global-search">global search view »</a>.  </p>
 <h4><a class="anchor" href="#schema-changes" id="schema-changes" name="schema-changes"><i class="anchor-icon"></i></a>Schema changes</h4>
 <h5><a class="anchor" href="#new-methods" id="new-methods" name="new-methods"><i class="anchor-icon"></i></a>New Methods</h5>
 <ul>
diff --git a/data/web/corefork.telegram.org/api/peers.html b/data/web/corefork.telegram.org/api/peers.html
index f21d34531b..e03fe01c13 100644
--- a/data/web/corefork.telegram.org/api/peers.html
+++ b/data/web/corefork.telegram.org/api/peers.html
@@ -198,8 +198,11 @@ As specified in the constructor docs, some of the fields must not be overwritten
 <p>Full peer info stored to the database must be refreshed <strong>only in the following conditions</strong> (i.e. <strong>do not</strong> refresh user info when opening the profile page, or every time the entry is accessed, <strong>do not</strong> use TTLs to expire the database entries, and so on...): </p>
 <ul>
 <li>Some event (specified <a href="#peer-info-database">here »</a>) changes the value of a specific subset of fields of an entry in the (non-full!) <a href="#peer-info-database">peer info database »</a>.<br>
-The relative full info entry should only be invalidated when some specific fields of the locally cached <a href="/constructor/user">user</a>/<a href="/constructor/channel">channel</a> are changed, see the documentation in the constructor pages for the full list.  </li>
+The relative full info entry should only be refreshed when some specific fields of the locally cached <a href="/constructor/user">user</a>/<a href="/constructor/channel">channel</a> are changed, see the documentation in the constructor pages for the full list.  </li>
 <li>After invoking <a href="/method/bots.setBotInfo">bots.setBotInfo</a> after changing <code>about</code> or <code>description</code> (but <strong>not</strong> <code>name</code>), for the bot whose info we changed.</li>
+<li>After invoking <a href="/method/messages.setChatWallPaper">messages.setChatWallPaper</a> to <em>remove</em> the wallpaper and receiving an error, for the peer whose wallpapers we tried to change, to fetch the correct and updated wallpaper settings.  </li>
+<li>After invoking <a href="/method/messages.setChatAvailableReactions">messages.setChatAvailableReactions</a> and getting an error different from <code>CHAT_NOT_MODIFIED</code>, for the peer whose reaction settings we tried to change.  </li>
+<li>After receiving a SEND_AS_PEER_INVALID error from any method that interacts with a group/supergroup: refresh info about the destination, to see which channel peers can be used to send messages to the group/supergroup through send_as.</li>
 </ul>
 <p><strong>Do not</strong> refresh full peer information in any other case, to avoid overloading the server by continuously requesting changes for the same unchanged information.</p></div>