Fix typos in docs and comments

Found by codespell

Change-Id: Ie3e301a23830c773a2e9aff487c702a223d246eb
Reviewed-by: Nicholas Bennett <nicholas.bennett@qt.io>
Reviewed-by: Edward Welbourne <edward.welbourne@qt.io>
(cherry picked from commit 9d2cc4dd766ca6538e17040b6ac845ed880ab0fe)
Reviewed-by: Qt Cherry-pick Bot <cherrypick_bot@qt-project.org>

7 files changed, 9 insertions, 9 deletions

diff --git a/tests/auto/corelib/thread/qfuture/tst_qfuture.cpp b/tests/auto/corelib/thread/qfuture/tst_qfuture.cpp
index 85239395d5..638dc380f7 100644
--- a/tests/auto/corelib/thread/qfuture/tst_qfuture.cpp
+++ b/tests/auto/corelib/thread/qfuture/tst_qfuture.cpp
@@ -3079,7 +3079,7 @@ void tst_QFuture::cancelContinuations()
 
 #ifndef QT_NO_EXCEPTIONS
     // The chain is cancelled in the middle of execution of continuations,
-    // while there's an exception in the chain, which is handeled inside
+    // while there's an exception in the chain, which is handled inside
     // the continuations.
     {
         QPromise<int> promise;
diff --git a/tests/auto/gui/image/qimagewriter/tst_qimagewriter.cpp b/tests/auto/gui/image/qimagewriter/tst_qimagewriter.cpp
index 88fa0634fb..f64c94bb90 100644
--- a/tests/auto/gui/image/qimagewriter/tst_qimagewriter.cpp
+++ b/tests/auto/gui/image/qimagewriter/tst_qimagewriter.cpp
@@ -102,7 +102,7 @@ void tst_QImageWriter::getSetCheck()
 
     QCOMPARE((QIODevice *) var1, obj1.device());
     // The class should possibly handle a 0-pointer as a device, since
-    // there is a default contructor, so it's "handling" a 0 device by default.
+    // there is a default constructor, so it's "handling" a 0 device by default.
     // For example: QMovie::setDevice(0) works just fine
     obj1.setDevice((QIODevice *)0);
     QCOMPARE((QIODevice *) 0, obj1.device());
diff --git a/tests/auto/gui/text/qtextmarkdownwriter/data/example.md b/tests/auto/gui/text/qtextmarkdownwriter/data/example.md
index a9a157f25a..15b30598e6 100644
--- a/tests/auto/gui/text/qtextmarkdownwriter/data/example.md
+++ b/tests/auto/gui/text/qtextmarkdownwriter/data/example.md
@@ -83,7 +83,7 @@ is used extensively in
 [Qt Assistant](http://doc.qt.io/qt-5/qtassistant-index.html). Hyperlinks are
 automatically created when an HTML file is imported into an editor. Since the
 rich text framework supports hyperlinks natively, they can also be created
-programatically.
+programmatically.
 
 ## Undo and Redo
 
diff --git a/tests/auto/widgets/kernel/qwidget/tst_qwidget.cpp b/tests/auto/widgets/kernel/qwidget/tst_qwidget.cpp
index ce46a45649..06cb89f4d8 100644
--- a/tests/auto/widgets/kernel/qwidget/tst_qwidget.cpp
+++ b/tests/auto/widgets/kernel/qwidget/tst_qwidget.cpp
@@ -10253,7 +10253,7 @@ void tst_QWidget::taskQTBUG_4055_sendSyntheticEnterLeave()
     QTRY_COMPARE(child.numEnterEvents, 1);
     QCOMPARE(child.numMouseMoveEvents, 0);
 
-    // Sending synthetic enter/leave trough the parent's mousePressEvent handler.
+    // Sending synthetic enter/leave through the parent's mousePressEvent handler.
     parent.child = &child;
 
     child.hide();
diff --git a/tests/auto/widgets/widgets/qlineedit/tst_qlineedit.cpp b/tests/auto/widgets/widgets/qlineedit/tst_qlineedit.cpp
index 8722b4602e..9719aefe7b 100644
--- a/tests/auto/widgets/widgets/qlineedit/tst_qlineedit.cpp
+++ b/tests/auto/widgets/widgets/qlineedit/tst_qlineedit.cpp
@@ -4105,7 +4105,7 @@ void tst_QLineEdit::QTBUG13520_textNotVisible()
     QString sometext("01-ST16-01SIL-MPL001wfgsdfgsdgsdfgsdfgsdfgsdfgsdfg");
     le.setText(sometext);
     le.setCursorPosition(0);
-    QTest::qWait(100); //just make sure we get he lineedit correcly painted
+    QTest::qWait(100); //just make sure we get he lineedit correctly painted
 
     auto expectedCursorCoordinate = le.width() - le.fontMetrics().horizontalAdvance(sometext);
     // cursor does not leave widget to the left:
diff --git a/tests/baseline/shared/lookup3.cpp b/tests/baseline/shared/lookup3.cpp
index 33d27bd964..bb91b3ac06 100644
--- a/tests/baseline/shared/lookup3.cpp
+++ b/tests/baseline/shared/lookup3.cpp
@@ -303,7 +303,7 @@ quint32 hashlittle( const void *key, size_t length, quint32 initval)
      * rest of the string.  Every machine with memory protection I've seen
      * does it on word boundaries, so is OK with this.  But VALGRIND will
      * still catch it and complain.  The masking trick does make the hash
-     * noticably faster for short strings (like English words).
+     * noticeably faster for short strings (like English words).
      */
 #ifndef VALGRIND
 
@@ -511,7 +511,7 @@ void hashlittle2(
      * rest of the string.  Every machine with memory protection I've seen
      * does it on word boundaries, so is OK with this.  But VALGRIND will
      * still catch it and complain.  The masking trick does make the hash
-     * noticably faster for short strings (like English words).
+     * noticeably faster for short strings (like English words).
      */
 #ifndef VALGRIND
 
@@ -711,7 +711,7 @@ quint32 hashbig( const void *key, size_t length, quint32 initval)
      * rest of the string.  Every machine with memory protection I've seen
      * does it on word boundaries, so is OK with this.  But VALGRIND will
      * still catch it and complain.  The masking trick does make the hash
-     * noticably faster for short strings (like English words).
+     * noticeably faster for short strings (like English words).
      */
 #ifndef VALGRIND
 
diff --git a/tests/benchmarks/corelib/tools/qhash/tst_bench_qhash.cpp b/tests/benchmarks/corelib/tools/qhash/tst_bench_qhash.cpp
index 7c81802df9..ca48763538 100644
--- a/tests/benchmarks/corelib/tools/qhash/tst_bench_qhash.cpp
+++ b/tests/benchmarks/corelib/tools/qhash/tst_bench_qhash.cpp
@@ -72,7 +72,7 @@ void tst_QHash::initTestCase()
     // lots of strings with alphabetical characters, vaguely reminiscent of
     // a dictionary.
     //
-    // this programatically generates a series like:
+    // this programmatically generates a series like:
     //  AAAAAA
     //  AAAAAB
     //  AAAAAC