From ac699c9b0abe55eac2e72654d49efa900a59e061 Mon Sep 17 00:00:00 2001
From: GitHub Action <github-action@users.noreply.github.com>
Date: Wed, 28 Sep 2022 20:14:27 +0000
Subject: [PATCH] Update content of files

---
 data/web/corefork.telegram.org/api/config.html    | 4 ++--
 data/web/corefork.telegram.org/api/errors.html    | 2 +-
 data/web/corefork.telegram.org/api/layers.html    | 2 +-
 data/web/corefork.telegram.org/api/premium.html   | 2 +-
 data/web/corefork.telegram.org/api/reactions.html | 5 +++--
 5 files changed, 8 insertions(+), 7 deletions(-)

diff --git a/data/web/corefork.telegram.org/api/config.html b/data/web/corefork.telegram.org/api/config.html
index f2119c9c28..06b7415866 100644
--- a/data/web/corefork.telegram.org/api/config.html
+++ b/data/web/corefork.telegram.org/api/config.html
@@ -302,9 +302,9 @@ While <a href="/method/help.getConfig">help.getConfig</a> returns MTProto-specif
 <h4><a class="anchor" href="#groupcall-video-participants-max" id="groupcall-video-participants-max" name="groupcall-video-participants-max"><i class="anchor-icon"></i></a><code>groupcall_video_participants_max</code></h4>
 <p>Maximum number of participants in a group call (livestreams allow ∞ participants) (integer)</p>
 <h4><a class="anchor" href="#reactions-uniq-max" id="reactions-uniq-max" name="reactions-uniq-max"><i class="anchor-icon"></i></a><code>reactions_uniq_max</code></h4>
-<p>Maximum number of unique reaction (non-custom) emojis for any given message: for example, if there are 2000 <img class="emoji" src="//telegram.org/img/emoji/40/F09F918D.png" width="20" height="20" alt="👍" /> and 1000 <img class="emoji" src="//telegram.org/img/emoji/40/F09F9881.png" width="20" height="20" alt="😁" /> reactions and reactions_uniq_max = 2, you can't add a <img class="emoji" src="//telegram.org/img/emoji/40/F09F918E.png" width="20" height="20" alt="👎" /> reaction, because that would raise the number of unique reaction-emojis to 3 &gt; 2. (integer)</p>
+<p>Maximum number of unique reactions for any given message: for example, if there are 2000 <img class="emoji" src="//telegram.org/img/emoji/40/F09F918D.png" width="20" height="20" alt="👍" /> and 1000 <img class="emoji" src="//telegram.org/img/emoji/40/F09F9881.png" width="20" height="20" alt="😁" /> reactions and reactions_uniq_max = 2, you can't add a <img class="emoji" src="//telegram.org/img/emoji/40/F09F918E.png" width="20" height="20" alt="👎" /> reaction, because that would raise the number of unique reaction-emojis to 3 &gt; 2. (integer)</p>
 <h4><a class="anchor" href="#reactions-in-chat-max" id="reactions-in-chat-max" name="reactions-in-chat-max"><i class="anchor-icon"></i></a><code>reactions_in_chat_max</code></h4>
-<p>Total number of reactions that should be shown under a message. (integer)</p>
+<p>(integer)</p>
 <h4><a class="anchor" href="#reactions-user-max-default" id="reactions-user-max-default" name="reactions-user-max-default"><i class="anchor-icon"></i></a><code>reactions_user_max_default</code></h4>
 <p>Maximum number of reactions that can be added to a single message by a non-Premium user. (integer)</p>
 <h4><a class="anchor" href="#reactions-user-max-premium" id="reactions-user-max-premium" name="reactions-user-max-premium"><i class="anchor-icon"></i></a><code>reactions_user_max_premium</code></h4>
diff --git a/data/web/corefork.telegram.org/api/errors.html b/data/web/corefork.telegram.org/api/errors.html
index f3beb0b2bb..df67c7f006 100644
--- a/data/web/corefork.telegram.org/api/errors.html
+++ b/data/web/corefork.telegram.org/api/errors.html
@@ -49,7 +49,7 @@ An error is characterized by several parameters:</p>
 <h4><a class="anchor" href="#error-type" id="error-type" name="error-type"><i class="anchor-icon"></i></a>Error Type</h4>
 <p>A string literal in the form of <code>/[A-Z_0-9]+/</code>, which summarizes the problem. For example, <code>AUTH_KEY_UNREGISTERED</code>. This is an optional parameter.</p>
 <h4><a class="anchor" href="#error-database" id="error-database" name="error-database"><i class="anchor-icon"></i></a>Error Database</h4>
-<p>A full machine-readable JSON list of RPC errors that can be returned by all methods in the API can be found <a href="/file/464001715/11004/r6e3zdhWVxU.87351.json/9b4183f1f997136734">here »</a>, what follows is a description of its fields:  </p>
+<p>A full machine-readable JSON list of RPC errors that can be returned by all methods in the API can be found <a href="/file/464001530/11880/Trl4csyCMqI.87735.json/a913651b756424f1e4">here »</a>, what follows is a description of its fields:  </p>
 <ul>
 <li><code>errors</code> - All error messages and codes for each method (object).<ul>
 <li>Keys: Error codes as strings (numeric strings)</li>
diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html
index 9637cf5733..1aa938b304 100644
--- a/data/web/corefork.telegram.org/api/layers.html
+++ b/data/web/corefork.telegram.org/api/layers.html
@@ -46,7 +46,7 @@
 
 <p>Below you will find information on schema changes. For more details on the use of layers, see <a href="/api/invoking#layers">Invoking API methods</a>.</p>
 <h3><a class="anchor" href="#layer-145" id="layer-145" name="layer-145"><i class="anchor-icon"></i></a><a href="/schema?layer=145">Layer 145</a></h3>
-<p><a href="/api/emoji-status">Custom emoji statuses</a>, <a href="/api/reactions">custom emoji message reactions</a>, <a href="/api/auth#email-verification">login via email</a>, <a href="/api/premium">Telegram Premium</a> improvements.</p>
+<p><a href="/api/emoji-status">Custom emoji statuses</a>, <a href="/api/reactions">custom emoji &amp; multiple message reactions</a>, <a href="/api/auth#email-verification">login via email</a>, <a href="/api/stickers#recent-stickersets">recent stickersets</a>, <a href="/api/premium">Telegram Premium</a> and <a href="/api/bots/webapps">bot web app</a> improvements.</p>
 <p>Added the following brand new documentation articles:</p>
 <ul>
 <li><a href="/api/links">Deep links</a></li>
diff --git a/data/web/corefork.telegram.org/api/premium.html b/data/web/corefork.telegram.org/api/premium.html
index 123edd278f..efce5af82e 100644
--- a/data/web/corefork.telegram.org/api/premium.html
+++ b/data/web/corefork.telegram.org/api/premium.html
@@ -97,7 +97,7 @@ Clicking on this button in the settings, clicking on the <a href="#badge">badge<
 <p>What follows is a list of <a href="/api/config#client-configuration">appConfig integer config parameters</a>.  </p>
 <p>Note that whenever config keys end with a <code>*</code> in the following list, the <code>*</code> should be replaced with <code>premium</code> or <code>default</code>, to fetch the appropriate limit value for Premium and non-Premium users.</p>
 <ul>
-<li><code>reactions_user_max_*</code> - The maximum number of reactions that can be added to a single message by the user.</li>
+<li><code>reactions_user_max_*</code> - The maximum number of <a href="/api/reactions">reactions</a> that can be added to a single message by the user.</li>
 <li><code>channels_limit_*</code> - The maximum number of <a href="/api/channel">channels and supergroups</a> a user may join.</li>
 <li><code>saved_gifs_limit_*</code> - The maximum number of GIFs a user may save.</li>
 <li><code>stickers_faved_limit_*</code> - The maximum number of stickers a user may <a href="/api/stickers#favorite-stickersets">add to favorites</a>.</li>
diff --git a/data/web/corefork.telegram.org/api/reactions.html b/data/web/corefork.telegram.org/api/reactions.html
index c6f1e3909e..5e944d1a72 100644
--- a/data/web/corefork.telegram.org/api/reactions.html
+++ b/data/web/corefork.telegram.org/api/reactions.html
@@ -72,8 +72,9 @@
 
 <a href='/method/messages.reportReaction'>messages.reportReaction</a>#3f64c076 peer:<a href='/type/InputPeer'>InputPeer</a> id:<a href='/type/int'>int</a> reaction_peer:<a href='/type/InputPeer'>InputPeer</a> = <a href='/type/Bool'>Bool</a>;</code></pre>
 <p>Users can react to a message with one or more reactions using <a href="/method/messages.sendReaction">messages.sendReaction</a>.<br>
-After sending the reaction, the <code>chosen_order</code> field of <a href="/constructor/reactionCount">reactionCount</a> will be set for the reaction, the integer value indicates when was the reaction added: the bigger the value, the newer the reaction: use this value to appropriately sort the <code>messages.sendReaction:reaction</code> vector when adding new reactions.<br>
-Reactions should be sent in <strong>ascending order</strong> (new reactions at the end in the <code>messages.sendReaction:reaction</code> vector), and when adding more reactions to the same message, older reactions should be removed to keep the total number of sent/modified reactions within by the <a href="/api/config#reactions-user-max-default">reactions_user_max_default</a>/<a href="/api/config#reactions-user-max-premium">reactions_user_max_premium</a> reactions.  </p>
+After sending the reaction, the <code>chosen_order</code> field of <a href="/constructor/reactionCount">reactionCount</a> will be set for the reaction. The integer value indicates when was the reaction added: the bigger the value, the newer the reaction, use this value to appropriately sort the <code>messages.sendReaction:reaction</code> vector when adding new reactions.<br>
+Reactions should be sent in <strong>ascending order</strong> (new reactions at the end in the <code>messages.sendReaction:reaction</code> vector), and when adding more reactions to the same message, older reactions should be removed to keep the total number of sent/modified reactions within <a href="/api/config#reactions-user-max-default">reactions_user_max_default</a>/<a href="/api/config#reactions-user-max-premium">reactions_user_max_premium</a> reactions.<br>
+The <a href="/api/config#reactions-uniq-max">reactions_uniq_max</a> configuration field also indicates the maximum number of reactions that can be added to a message.  </p>
 <p>The <code>big</code> flag can be optionally set to elicit a bigger reaction.<br>
 Send a <a href="/constructor/reactionEmoji">reactionEmoji</a> to react using a normal emoji, and a <a href="/constructor/reactionCustomEmoji">reactionCustomEmoji</a> to react using a <a href="/api/custom-emoji">custom emoji</a>.<br>
 Message authors will receive an <a href="/constructor/updateMessageReactions">updateMessageReactions</a> update when a user reacts to their message.  </p>