Update content of files

data/web/core.telegram.org/stickers/webm-vp9-encoding.html

@@ -77,7 +77,7 @@
 <li>Make sure to check that <strong>VP9</strong> is selected in the codec settings – some apps may default to VP8.</li>
 <li>Make sure to <strong>remove</strong> any audio streams (uncheck ‘Export Audio’ in Adobe programs).</li>
 <li>Make sure the frame rate is a <strong>constant 30 FPS</strong>.</li>
-<li>Use <strong>Constant Quality</strong> and a lower (or lowest) quality setting – size dramatically decreases without affecting fidelity.</li>
+<li>Use <strong>Constant Quality</strong> and a lower (or lowest) quality setting – otherwise size dramatically decreases without affecting fidelity.</li>
 <li>In <strong>Media Encoder</strong>, make sure your Renderer is set to ‘Software Only’.</li>
 <li>If your file fails to render, try importing it as a <strong>PNG Sequence</strong>.</li>
 </ul>

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

@@ -46,6 +46,9 @@
 
 <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-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">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>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>
 <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>
@@ -127,6 +130,8 @@
 <a href="/constructor/messageEntitySpoiler">messageEntitySpoiler</a>#32ca960f offset:<a href="/type/int">int</a> length:<a href="/type/int">int</a> = <a href="/type/MessageEntity">MessageEntity</a>;
 <a href="/constructor/messageEntityCustomEmoji">messageEntityCustomEmoji</a>#c8cf05f8 offset:<a href="/type/int">int</a> length:<a href="/type/int">int</a> document_id:<a href="/type/long">long</a> = <a href="/type/MessageEntity">MessageEntity</a>;<br></code></pre></div>
 <h3><a class="anchor" href="#layer-143" id="layer-143" name="layer-143"><i class="anchor-icon"></i></a><a href="/schema?layer=143">Layer 143</a></h3>
+<p><a href="/api/premium">Telegram Premium</a>, <a href="/api/transcribe">voice message transcription</a>, <a href="/api/links#invoice-links">invoices</a>, bot description photos/animations, and <a href="/api/bots/attach">attachment menu</a> improvements.<br>
+Also, discussion group admins can now <a href="/api/discussion#requiring-users-to-join-the-group">require users to join</a> before commenting.</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>
@@ -260,7 +265,7 @@
 <h4><a class="anchor" href="#schema" id="schema" name="schema"><i class="anchor-icon"></i></a>Schema</h4>
 <div><pre><code><a href="/constructor/phoneConnection">phoneConnection</a>#9cc123c7 flags:<a href="/type/%23">#</a> tcp:flags.0?<a href="/constructor/true">true</a> id:<a href="/type/long">long</a> ip:<a href="/type/string">string</a> ipv6:<a href="/type/string">string</a> port:<a href="/type/int">int</a> peer_tag:<a href="/type/bytes">bytes</a> = <a href="/type/PhoneConnection">PhoneConnection</a>;<br></code></pre></div>
 <h3><a class="anchor" href="#layer-140" id="layer-140" name="layer-140"><i class="anchor-icon"></i></a><a href="/schema?layer=140">Layer 140</a></h3>
-<p>Introducing <a href="/api/bots/attach">attachment menus</a>, <a href="/api/bots/webapps">bot web apps</a>, <a href="/api/bots/menu">custom bot menu buttons</a>, <a href="/api/rights#suggested-bot-rights">suggested bot admin rights</a> and <a href="/api/ringtones">ringtones</a>.  </p>
+<p>Introducing <a href="/api/bots/attach">attachment menus</a>, <a href="/api/bots/webapps">bot web apps</a>, <a href="/api/bots/menu">custom bot menu buttons</a>, <a href="/api/rights#suggested-bot-rights">suggested bot admin rights</a> and <a href="/api/ringtones">ringtones</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>

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

@@ -61,7 +61,7 @@ The method call generates the following updates:</p>
 <li>At <code>schedule_date</code>, an <a href="/constructor/updateNewMessage">updateNewMessage</a> or <a href="/constructor/updateNewChannelMessage">updateNewChannelMessage</a> with the <code>from_scheduled</code> flag set, indicating to the sender that the specified scheduled message was sent.  </li>
 <li>At <code>schedule_date</code>, an <a href="/constructor/updateDeleteScheduledMessages">updateDeleteScheduledMessages</a>, indicating that the message was flushed from the schedule queue.</li>
 </ul>
-<p>If the <code>schedule_date</code> is less than 10 seconds in the future, the message will be sent immediately, generating a normal <a href="/constructor/updateNewMessage">updateNewMessage</a>/<a href="/constructor/updateNewChannelMessage">updateNewChannelMessage</a> .  </p>
+<p>If the <code>schedule_date</code> is less than 10 seconds in the future, the message will be sent immediately, generating a normal <a href="/constructor/updateNewMessage">updateNewMessage</a>/<a href="/constructor/updateNewChannelMessage">updateNewChannelMessage</a>.  </p>
 <h3><a class="anchor" href="#manipulating-the-schedule-queue" id="manipulating-the-schedule-queue" name="manipulating-the-schedule-queue"><i class="anchor-icon"></i></a>Manipulating the schedule queue</h3>
 <pre><code><a href='/constructor/updateNewScheduledMessage'>updateNewScheduledMessage</a>#39a51dfb message:<a href='/type/Message'>Message</a> = <a href='/type/Update'>Update</a>;
 <a href='/constructor/updateDeleteScheduledMessages'>updateDeleteScheduledMessages</a>#90866cee peer:<a href='/type/Peer'>Peer</a> messages:<a href='/type/Vector%20t'>Vector</a>&lt;<a href='/type/int'>int</a>&gt; = <a href='/type/Update'>Update</a>;

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

@@ -74,12 +74,12 @@
 <tr>
 <td><strong>show_previews</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.0?<a href="/type/Bool">Bool</a></td>
-<td>Display text in notifications</td>
+<td>(Ternary value) If set, indicates whether or not to display previews of messages in notifications; otherwise the default behavior should be used.</td>
 </tr>
 <tr>
 <td><strong>silent</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.1?<a href="/type/Bool">Bool</a></td>
-<td>Mute peer?</td>
+<td>(Ternary value) If set, indicates whether to mute or unmute the peer; otherwise the default behavior should be used.</td>
 </tr>
 <tr>
 <td><strong>mute_until</strong></td>