From 113cf22885b901b2ab697d101cdfdd031f910266 Mon Sep 17 00:00:00 2001
From: Sona Kurazyan <sona.kurazyan@qt.io>
Date: Fri, 4 Feb 2022 13:53:39 +0100
Subject: [PATCH] Fix a typo in QFutureWatcher docs

Change-Id: I431d21e6161d117a7b2ee28ee9db955726d50f79
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
(cherry picked from commit 013d0fcf5f5e59d26bc7f1265af5d955b2be22f6)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>
---
 src/corelib/thread/qfuturewatcher.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/corelib/thread/qfuturewatcher.cpp b/src/corelib/thread/qfuturewatcher.cpp
index d3a904ab000..9ad176b1d88 100644
--- a/src/corelib/thread/qfuturewatcher.cpp
+++ b/src/corelib/thread/qfuturewatcher.cpp
@@ -615,7 +615,7 @@ QT_WARNING_POP
     following signals will, if applicable, be emitted in the given order:
     started(), progressRangeChanged(), progressValueChanged(),
     progressTextChanged(), resultsReadyAt(), resultReadyAt(), suspending(),
-    suspended(), canceled() finished(). Of these, resultsReadyAt() and
+    suspended(), canceled(), and finished(). Of these, resultsReadyAt() and
     resultReadyAt() may be emitted several times to cover all available
     results. progressValueChanged() and progressTextChanged() will only be
     emitted once for the latest available progress value and text.