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

---
 data/web/corefork.telegram.org/api/push-updates.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/data/web/corefork.telegram.org/api/push-updates.html b/data/web/corefork.telegram.org/api/push-updates.html
index af2a59d260..a44d696dc1 100644
--- a/data/web/corefork.telegram.org/api/push-updates.html
+++ b/data/web/corefork.telegram.org/api/push-updates.html
@@ -55,7 +55,7 @@
 <li><code>3</code> - MPNS (channel URI for microsoft push)</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>.<br>
 Simple push works by sending a simple PUT request with a <code>version=number</code> payload to the specified HTTPS endpoint every time a relevant message is received: upon receiving such a notification, clients should connect to the MTProto API and fetch <a href="/api/updates">updates</a>.<br>
-(Note that the <code>number</code> won't necessarily be incremental in Telegram's implementation, just treat each distinct request as a distinct wake-up signal).</li>
+(Note that the <code>number</code> won't necessarily be incremental in Telegram's implementation, just treat each distinct request as a signal that a message is waiting to be fetched via MTProto).</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>