From 68b904e4c71aab774f9a15f7ed4299680659682a Mon Sep 17 00:00:00 2001
From: GitHub Action <github-action@users.noreply.github.com>
Date: Wed, 6 Dec 2023 20:26:40 +0000
Subject: [PATCH] Update content of files

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

diff --git a/data/web/corefork.telegram.org/api/invoking.html b/data/web/corefork.telegram.org/api/invoking.html
index 90333bfe65..3305b71887 100644
--- a/data/web/corefork.telegram.org/api/invoking.html
+++ b/data/web/corefork.telegram.org/api/invoking.html
@@ -120,7 +120,7 @@ It may be required to repeat the process if the newly sent <code>invokeAfterMsgs
 <p>Obviously the first option (waiting for replies (errors or successes) for <strong>all</strong> of the queries mentioned before proceeding) is the simplest.</p>
 </li>
 </ul>
-<p>An even simpler option is to always follow <a href="#scenario-1">Scenario 1</a>, never using <code>invokeAfterMsgs</code> and only using chained <code>invokeAfterMsg</code> calls, which avoids the use of this slightly more complicated logic.</p>
+<p>An even simpler option is to always follow <a href="#scenario-1">Scenario 1</a>, never using <code>invokeAfterMsgs</code> and only using chained <code>invokeAfterMsg</code> calls, thus avoiding the use of this slightly more complicated recovery logic.</p>
 <h4><a class="anchor" href="#helper-method-sequence" id="helper-method-sequence" name="helper-method-sequence"><i class="anchor-icon"></i></a>Helper Method Sequence</h4>
 <p><strong>Important:</strong> if the helper methods <strong>invokeAfterMsg</strong> / <strong>invokeAfterMsgs</strong> are used together with <strong>invokeWithLayerN</strong> or other helper methods, <strong>invokeAfterMsg</strong> / <strong>invokeAfterMsgs</strong> must always be the outermost wrapper.</p>
 <h3><a class="anchor" href="#data-compression" id="data-compression" name="data-compression"><i class="anchor-icon"></i></a>Data Compression</h3>