summaryrefslogtreecommitdiffstats
path: root/doc/src/timers.qdoc
diff options
context:
space:
mode:
authorFrederik Schwarzer <schwarzerf@gmail.com>2009-05-11 13:55:59 (GMT)
committerFrederik Schwarzer <schwarzerf@gmail.com>2009-05-11 13:55:59 (GMT)
commite9c8a4cf013906a54b1b05796d6007d878e85398 (patch)
treeaaffd3af0d5198e3fd489c6b6aa0305bbcdfda73 /doc/src/timers.qdoc
parent38809e24a48f6c4b148cd730a8d5d52a7525e5bd (diff)
downloadQt-e9c8a4cf013906a54b1b05796d6007d878e85398.zip
Qt-e9c8a4cf013906a54b1b05796d6007d878e85398.tar.gz
Qt-e9c8a4cf013906a54b1b05796d6007d878e85398.tar.bz2
typos in docs: double "the"
Diffstat (limited to 'doc/src/timers.qdoc')
-rw-r--r--doc/src/timers.qdoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/src/timers.qdoc b/doc/src/timers.qdoc
index 4f54343..1b48d7d 100644
--- a/doc/src/timers.qdoc
+++ b/doc/src/timers.qdoc
@@ -62,7 +62,7 @@
In multithreaded applications, you can use the timer mechanism in
any thread that has an event loop. To start an event loop from a
- non-GUI thread, use QThread::exec(). Qt uses the the object's
+ non-GUI thread, use QThread::exec(). Qt uses the object's
\l{QObject::thread()}{thread affinity} to determine which thread
will deliver the QTimerEvent. Because of this, you must start and
stop all timers in the object's thread; it is not possible to
@@ -105,7 +105,7 @@
In multithreaded applications, you can use QTimer in any thread
that has an event loop. To start an event loop from a non-GUI
- thread, use QThread::exec(). Qt uses the the timer's
+ thread, use QThread::exec(). Qt uses the timer's
\l{QObject::thread()}{thread affinity} to determine which thread
will emit the \l{QTimer::}{timeout()} signal. Because of this, you
must start and stop the timer in its thread; it is not possible to