From c2f06c8f14da53d68f258415c46efc6414c592de Mon Sep 17 00:00:00 2001
From: GitHub Action <github-action@users.noreply.github.com>
Date: Tue, 13 Sep 2022 15:33:03 +0000
Subject: [PATCH] Update content of files

---
 data/web/corefork.telegram.org/api/errors.html | 4 ++--
 data/web/corefork.telegram.org/api/layers.html | 9 +++++++++
 2 files changed, 11 insertions(+), 2 deletions(-)

diff --git a/data/web/corefork.telegram.org/api/errors.html b/data/web/corefork.telegram.org/api/errors.html
index 129383ad74..60228a2b4c 100644
--- a/data/web/corefork.telegram.org/api/errors.html
+++ b/data/web/corefork.telegram.org/api/errors.html
@@ -49,7 +49,7 @@
 <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/464001266/11d30/8avYQb50xVY.85929.json/b8cdcb96fc82498fe6">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/464001219/106c5/hD5w1XYEfUU.86480.json/66be96977e2052b519">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>
@@ -154,7 +154,7 @@
 <p>An exception to this is the <code>AUTH_KEY_DUPLICATED</code> error, which is only emitted if any of the non-media DC detects that an authorized session is sending requests in parallel from two separate TCP connections, from the same or different IP addresses.<br>
 Note that parallel connections are still allowed and actually recommended for media DCs.
 Also note that by session we mean a logged-in session identified by an <a href="/constructor/authorization">authorization</a> constructor, fetchable using <a href="/method/account.getAuthorizations">account.getAuthorizations</a>, not an MTProto session.  </p>
-<p>If the client receives an <code>AUTH_KEY_DUPLICATED</code> error, the session is already invalidated by the server and the user must log out, generate a new auth key and login again.  </p>
+<p>If the client receives an <code>AUTH_KEY_DUPLICATED</code> error, the session is already invalidated by the server and the user must generate a new auth key and login again.  </p>
 <h3><a class="anchor" href="#420-flood" id="420-flood" name="420-flood"><i class="anchor-icon"></i></a>420 FLOOD</h3>
 <p>The maximum allowed number of attempts to invoke the given method with the given input parameters has been exceeded. For example, in an attempt to request a large number of text messages (SMS) for the same phone number.</p>
 <h4><a class="anchor" href="#error-example" id="error-example" name="error-example"><i class="anchor-icon"></i></a>Error Example:</h4>
diff --git a/data/web/corefork.telegram.org/api/layers.html b/data/web/corefork.telegram.org/api/layers.html
index 58cc1e4206..fa79695bff 100644
--- a/data/web/corefork.telegram.org/api/layers.html
+++ b/data/web/corefork.telegram.org/api/layers.html
@@ -48,7 +48,16 @@
 <h3><a class="anchor" href="#layer-144" id="layer-144" name="layer-144"><i class="anchor-icon"></i></a><a href="/schema?layer=144">Layer 144</a></h3>
 <p>Users can now send <a href="/api/custom-emoji">custom emojis</a>, <a href="/api/premium#gifting-telegram-premium">gift Telegram Premium</a> to other users, and <a href="/constructor/inputWebFileAudioAlbumThumbLocation">download album covers for any music file</a>.<br>
 Also introducing new <a href="https://telegram.org/blog/custom-emoji#privacy-settings-for-voice-messages">voice message privacy settings</a> and support for additional <a href="/api/payments">payment methods</a>.</p>
+<p>Added the following brand new documentation articles:</p>
+<ul>
+<li><a href="/api/links">Deep links</a></li>
+<li><a href="/api/stickers">Stickers</a></li>
+<li><a href="/api/themes">Themes</a></li>
+<li><a href="/api/wallpapers">Wallpapers</a></li>
+</ul>
+<p>Also added more details on <a href="/api/entities#entity-length">entity length calculation</a> and <a href="/api/errors#406-not-acceptable"><code>AUTH_KEY_DUPLICATED</code> errors</a>.</p>
 <p>The <a href="/schema/end-to-end">E2E schema</a> was also updated to account for previous changes in the main schema (<a href="/api/custom-emoji">custom emojis</a>+<a href="/api/entities">spoiler entities</a>).</p>
+<p>The <a href="/api/errors#error-database">RPC error database »</a> was also updated.</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>