From 539e2d143cc9a432b0f53774aceb665e026d3880 Mon Sep 17 00:00:00 2001
From: GitHub Action <github-action@users.noreply.github.com>
Date: Tue, 16 May 2023 21:00:35 +0000
Subject: [PATCH] Update content of files

---
 data/web/corefork.telegram.org/api/errors.html           | 2 +-
 data/web/corefork.telegram.org/api/files.html            | 2 +-
 data/web/corefork.telegram.org/api/layers.html           | 4 ++--
 .../corefork.telegram.org/method/messages.sendReaction   | 9 ++++++---
 data/web/corefork.telegram.org/methods.html              | 2 +-
 data/web/corefork.telegram.org/type/Updates.html         | 2 +-
 6 files changed, 12 insertions(+), 9 deletions(-)

diff --git a/data/web/corefork.telegram.org/api/errors.html b/data/web/corefork.telegram.org/api/errors.html
index 8d9c41971e..4805222211 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 human-readable JSON list of RPC errors that can be returned by all methods in the API can be found <a href="/file/464001645/10615/psjxnPVjjgY.96919.json/0ed748f5649b018238">here »</a>, what follows is a description of its fields:  </p>
+<p>A full human-readable JSON list of RPC errors that can be returned by all methods in the API can be found <a href="/file/464001689/1083a/g7RttcHQ5iw.96919.json/5308054e847ddc0301">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/files.html b/data/web/corefork.telegram.org/api/files.html
index 75ae45953c..fd6f705cdb 100644
--- a/data/web/corefork.telegram.org/api/files.html
+++ b/data/web/corefork.telegram.org/api/files.html
@@ -292,7 +292,7 @@ The data for the input parameter of the <a href="/type/InputFileLocation">InputF
 <ul>
 <li><strong>offset</strong> / (1024 * 1024) == (<strong>offset</strong> + <strong>limit</strong> - 1) / (1024 * 1024).</li>
 </ul>
-<p>When downloading multiple files in parallel, limit the parallelism to download at most <code>small_queue_max_active_operations_count</code>/<code>large_queue_max_active_operations_count</code> files in parallel when downloading files smaller/bigger than 20MB (<a href="/api/config#client-configuration">client configuration parameters »</a>).  </p>
+<p>When downloading multiple files in parallel from the same DC, clients should limit the parallelism to download at most <code>small_queue_max_active_operations_count</code>/<code>large_queue_max_active_operations_count</code> files in parallel when downloading files smaller/bigger than 20MB (<a href="/api/config#client-configuration">client configuration parameters »</a>).  </p>
 <p>The file download operation may return a <code>FILE_REFERENCE_EXPIRED</code> error (or another error starting with <code>FILE_REFERENCE_</code>): in this case, the <code>file_reference</code> field of the input location must be <a href="/api/file_reference">refreshed</a>.
 The file download operation may return an <a href="/constructor/upload.fileCdnRedirect">upload.fileCdnRedirect</a> constructor: in this case, <a href="/cdn">these</a> instructions must be followed for downloading CDN files.
 The file download operation may also return one of the following <a href="/api/errors#400-bad-request">data input errors</a>:</p>
diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html
index 3332740a84..e9a7fc9259 100644
--- a/data/web/corefork.telegram.org/api/layers.html
+++ b/data/web/corefork.telegram.org/api/layers.html
@@ -55,7 +55,7 @@ Third-party apps may log in using any of the other code delivery methods (Telegr
 Users may now edit the <a href="/api/bots/info">usernames, name, about text, description and profile picture</a> of bots they own using the API.<br>
 Bots can now directly invoke <a href="/method/photos.updateProfilePhoto">photos.updateProfilePhoto</a> and <a href="/method/photos.uploadProfilePhoto">photos.uploadProfilePhoto</a> to edit their own profile picture.<br>
 Bots may also now specify a custom peer filter when using <a href="/constructor/keyboardButtonSwitchInline">keyboardButtonSwitchInline</a> buttons.</p>
-<p>Added the <a href="/api/config#small-queue-max-active-operations-count"><code>small_queue_max_active_operations_count</code> »</a> and <a href="/api/config#large-queue-max-active-operations-count"><code>large_queue_max_active_operations_count</code> »</a> client configuration parameters, used to limit parallelism when downloading multiple files in parallel as described in the <a href="/api/files#downloading-files">docs »</a>.</p>
+<p>Added the <a href="/api/config#small-queue-max-active-operations-count"><code>small_queue_max_active_operations_count</code> »</a> and <a href="/api/config#large-queue-max-active-operations-count"><code>large_queue_max_active_operations_count</code> »</a> client configuration parameters, used to limit parallelism when downloading multiple files in parallel from the same DC as described in the <a href="/api/files#downloading-files">docs »</a>.</p>
 <p>The <a href="/api/errors#error-database">RPC error database »</a> was also updated, and a small clarification for open-source push notification standards like UnifiedPush was added to the <a href="/api/push-updates">push notifications documentation »</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>
@@ -1327,7 +1327,7 @@ Also, discussion group admins can now <a href="/api/discussion#requiring-users-t
 <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>
-<li>Added <a href="/method/messages.sendReaction">messages.sendReaction</a> - React to message</li>
+<li>Added <a href="/method/messages.sendReaction">messages.sendReaction</a> - React to message.</li>
 <li>Added <a href="/method/messages.getMessagesReactions">messages.getMessagesReactions</a> - Get <a href="/api/reactions">message reactions »</a></li>
 <li>Added <a href="/method/messages.getMessageReactionsList">messages.getMessageReactionsList</a> - Get <a href="/api/reactions">message reaction</a> list, along with the sender of each reaction.</li>
 <li>Added <a href="/method/messages.setChatAvailableReactions">messages.setChatAvailableReactions</a> - Change the set of <a href="/api/reactions">message reactions »</a> that can be used in a certain group, supergroup or channel</li>
diff --git a/data/web/corefork.telegram.org/method/messages.sendReaction b/data/web/corefork.telegram.org/method/messages.sendReaction
index 835ede966f..2fc045a8f7 100644
--- a/data/web/corefork.telegram.org/method/messages.sendReaction
+++ b/data/web/corefork.telegram.org/method/messages.sendReaction
@@ -4,10 +4,10 @@
     <meta charset="utf-8">
     <title>messages.sendReaction</title>
     <meta name="viewport" content="width=device-width, initial-scale=1.0">
-    <meta property="description" content="React to message">
+    <meta property="description" content="React to message.">
     <meta property="og:title" content="messages.sendReaction">
     <meta property="og:image" content="">
-    <meta property="og:description" content="React to message">
+    <meta property="og:description" content="React to message.">
     <link rel="icon" type="image/svg+xml" href="/img/website_icon.svg?4">
 <link rel="apple-touch-icon" sizes="180x180" href="/img/apple-touch-icon.png">
 <link rel="icon" type="image/png" sizes="32x32" href="/img/favicon-32x32.png">
@@ -42,7 +42,8 @@
   <div class="dev_page_bread_crumbs"><ul class="breadcrumb clearfix"><li><a  href="/api" >API</a></li><i class="icon icon-breadcrumb-divider"></i><li><a  href="/methods" >All Methods</a></li><i class="icon icon-breadcrumb-divider"></i><li><a  href="/method/messages.sendReaction" >messages.sendReaction</a></li></ul></div>
   <h1 id="dev_page_title">messages.sendReaction</h1>
   
-  <div id="dev_page_content"><p>React to message</p>
+  <div id="dev_page_content"><p>React to message.</p>
+<p>Starting from layer 159, the reaction will be sent from the peer specified using <a href="/method/messages.saveDefaultSendAs">messages.saveDefaultSendAs</a>.</p>
 <p><div class="clearfix">
   <ul class="dev_layer_select slightly-pull-right nav nav-pills">
     <li class="dropdown">
@@ -183,6 +184,8 @@
 <h3><a class="anchor" href="#related-pages" id="related-pages" name="related-pages"><i class="anchor-icon"></i></a>Related pages</h3>
 <h4><a class="anchor" href="#message-reactions" id="message-reactions" name="message-reactions"><i class="anchor-icon"></i></a><a href="/api/reactions">Message reactions</a></h4>
 <p>Telegram allows users to react on any message using specific emojis, triggering cute lottie animations.</p>
+<h4><a class="anchor" href="#messagessavedefaultsendas" id="messagessavedefaultsendas" name="messagessavedefaultsendas"><i class="anchor-icon"></i></a><a href="/method/messages.saveDefaultSendAs">messages.saveDefaultSendAs</a></h4>
+<p>Change the default peer that should be used when sending messages to a specific group</p>
 <h4><a class="anchor" href="#client-configuration" id="client-configuration" name="client-configuration"><i class="anchor-icon"></i></a><a href="/api/config">Client configuration</a></h4>
 <p>The MTProto API has multiple configuration parameters that can be fetched with the appropriate methods.</p></div>
   
diff --git a/data/web/corefork.telegram.org/methods.html b/data/web/corefork.telegram.org/methods.html
index 5c08a81137..3e5bbaf4d7 100644
--- a/data/web/corefork.telegram.org/methods.html
+++ b/data/web/corefork.telegram.org/methods.html
@@ -1187,7 +1187,7 @@
 </tr>
 <tr>
 <td><a href="/method/messages.sendReaction">messages.sendReaction</a></td>
-<td>React to message</td>
+<td>React to message.<br><br>Starting from layer 159, the reaction will be sent from the peer specified using <a href="/method/messages.saveDefaultSendAs">messages.saveDefaultSendAs</a>.</td>
 </tr>
 <tr>
 <td><a href="/method/messages.getAvailableReactions">messages.getAvailableReactions</a></td>
diff --git a/data/web/corefork.telegram.org/type/Updates.html b/data/web/corefork.telegram.org/type/Updates.html
index 994a42f23d..84cbb975cf 100644
--- a/data/web/corefork.telegram.org/type/Updates.html
+++ b/data/web/corefork.telegram.org/type/Updates.html
@@ -474,7 +474,7 @@
 </tr>
 <tr>
 <td><a href="/method/messages.sendReaction">messages.sendReaction</a></td>
-<td>React to message</td>
+<td>React to message.<br><br>Starting from layer 159, the reaction will be sent from the peer specified using <a href="/method/messages.saveDefaultSendAs">messages.saveDefaultSendAs</a>.</td>
 </tr>
 <tr>
 <td><a href="/method/messages.getMessagesReactions">messages.getMessagesReactions</a></td>