From cbd60dfa0a4c32d6045464a3d1e1752ce0a1ad5d Mon Sep 17 00:00:00 2001
From: GitHub Action <github-action@users.noreply.github.com>
Date: Sat, 15 Apr 2023 18:38:58 +0000
Subject: [PATCH] Update content of files

---
 data/web/corefork.telegram.org/api/push-updates.html           | 3 +--
 data/web/corefork.telegram.org/api/translation.html            | 2 +-
 .../constructor/inputStorePaymentPremiumSubscription.html      | 2 +-
 3 files changed, 3 insertions(+), 4 deletions(-)

diff --git a/data/web/corefork.telegram.org/api/push-updates.html b/data/web/corefork.telegram.org/api/push-updates.html
index 29428084d6..0c54557dde 100644
--- a/data/web/corefork.telegram.org/api/push-updates.html
+++ b/data/web/corefork.telegram.org/api/push-updates.html
@@ -53,7 +53,7 @@
 <li><code>1</code> - APNS (device token for apple push)</li>
 <li><code>2</code> - FCM (firebase token for google firebase)</li>
 <li><code>3</code> - MPNS (channel URI for microsoft push)</li>
-<li><code>4</code> - Deprecated: Simple push (endpoint for firefox's simple push API)</li>
+<li><code>4</code> - Simple push (endpoint for firefox's deprecated simple push API): note that this push type can also be used by an open source push notification spec like <a href="https://unifiedpush.org/">UnifiedPush »</a>.</li>
 <li><code>5</code> - Ubuntu phone (token for ubuntu push)</li>
 <li><code>6</code> - Blackberry (token for blackberry push)</li>
 <li><code>7</code> - MTProto separate session</li>
@@ -72,7 +72,6 @@
 </ul>
 </li>
 </ul>
-<p>Web push (<code>10</code>) may also be used to deliver push notifications via <a href="https://unifiedpush.org/">UnifiedPush »</a>.</p>
 <h3><a class="anchor" href="#notification-encryption" id="notification-encryption" name="notification-encryption"><i class="anchor-icon"></i></a>Notification encryption</h3>
 <p>For FCM and APNS VoIP, an optional encryption key used to encrypt push notifications can be passed to <a href="/method/account.registerDevice">account.registerDevice</a> (<code>secret</code>). This key (<code>auth_key</code>) is used to encrypt the payloads using <a href="/mtproto/description">MTProto v2</a>.</p>
 <p>The FCM payload will be a JSON payload, containing a <code>p</code> field with the base64url-encoded encrypted <a href="/mtproto/description">MTProto payload</a>. After decryption, the result will be a JSON object, prefixed by a 32-bit little-endian integer with the length of the JSON payload. As usual, make sure to follow all security checks as described in the <a href="/mtproto/description#important-checks">MTProto docs</a>.</p>
diff --git a/data/web/corefork.telegram.org/api/translation.html b/data/web/corefork.telegram.org/api/translation.html
index 48251ad7e4..7f96da148b 100644
--- a/data/web/corefork.telegram.org/api/translation.html
+++ b/data/web/corefork.telegram.org/api/translation.html
@@ -70,7 +70,7 @@ If the currently logged in account is a Premium account, and the <code>translati
 <ul>
 <li>The language recognition model was ran on at least 8 messages in the chat,</li>
 <li><strong>and</strong> the language of at least 35% of the processed messages was successfully detected,</li>
-<li><strong>and</strong> at least 65% of the messages whose language was successfully detected are in a foreign language (a language that is not the system language or the Telegram in-app language, and a language that was not explicitly excluded from translation by the user),</li>
+<li><strong>and</strong> at least 65% of the messages whose language was successfully detected are in a foreign language (a language that is not the system language nor the Telegram in-app language, and a language that was not explicitly excluded from translation by the user),</li>
 <li><strong>then</strong>, a popup should be displayed to the user, offering to enable real-time chat translation, or to disallow translation of the detected language (the detected language is the language with most occurrences amongst all processed messages).  </li>
 </ul>
 <p>If the user dismisses the autotranslation popup, invoke <a href="/method/messages.togglePeerTranslations">messages.togglePeerTranslations</a> with the <code>disabled</code> flag set: this will set the <code>translations_disabled</code> flag in the corresponding full info constructor, signaling to the other sessions that the autotranslation popup should not be displayed.  </p>
diff --git a/data/web/corefork.telegram.org/constructor/inputStorePaymentPremiumSubscription.html b/data/web/corefork.telegram.org/constructor/inputStorePaymentPremiumSubscription.html
index a57f418b2d..bcdb573a47 100644
--- a/data/web/corefork.telegram.org/constructor/inputStorePaymentPremiumSubscription.html
+++ b/data/web/corefork.telegram.org/constructor/inputStorePaymentPremiumSubscription.html
@@ -79,7 +79,7 @@
 <tr>
 <td><strong>upgrade</strong></td>
 <td style="text-align: center;"><a href="/mtproto/TL-combinators#conditional-fields">flags</a>.1?<a href="/constructor/true">true</a></td>
-<td> </td>
+<td>Pass true if this is an upgrade from a monthly subscription to a yearly subscription; only for App Store</td>
 </tr>
 </tbody>
 </table>