1 files changed, 21 insertions, 21 deletions
diff --git a/experimental/tqtinterface/qt4/tools/linguist/book/linguist-programmer.leaf b/experimental/tqtinterface/qt4/tools/linguist/book/linguist-programmer.leaf
index a4dfa6405..7cec63194 100644
--- a/experimental/tqtinterface/qt4/tools/linguist/book/linguist-programmer.leaf
+++ b/experimental/tqtinterface/qt4/tools/linguist/book/linguist-programmer.leaf
@@ -157,7 +157,7 @@ Translations
 \index lupdate
 
 The \l lupdate program automatically provides a \e context for every
-source text. This context is the class name of the class that tqcontains
+source text. This context is the class name of the class that contains
 the \c tr() call. This is sufficient in the vast majority of cases.
 Sometimes however, the translator will need further information to
 uniquely identify a source text; for example, a dialog that contained
@@ -350,7 +350,7 @@ Creates a \l QTranslator object without a tqparent.
 \index tt1_la.qm
 
 Tries to load a file called \c tt1_la.qm (the \c .qm file extension is
-implicit) that tqcontains Latin translations for the source texts used in
+implicit) that contains Latin translations for the source texts used in
 the program. No error will occur if the file is not found.
 
 \index QApplication!installTranslator()
@@ -366,7 +366,7 @@ by the program.
 \printline hello
 
 Creates a push button that displays "Hello world!". If \c tt1_la.qm
-was found and tqcontains a translation for "Hello world!", the
+was found and contains a translation for "Hello world!", the
 translation appears; if not, the source text appears.
 
 \index tr()
@@ -394,7 +394,7 @@ is shown when we run the application:
 
 The first step is to create a project file, \c tt1.pro, that lists
 all the source files for the project. The project file can be a qmake
-project file, or even an ordinary makefile. Any file that tqcontains
+project file, or even an ordinary makefile. Any file that contains
 
 \index SOURCES!in Project Files
 \index TRANSLATIONS!in Project Files
@@ -539,12 +539,12 @@ This example is a slightly more involved and introduces a key
 \e {Qt Linguist} concept: "contexts".
 
 \list
-\i \c arrowpad.h tqcontains the definition of \c ArrowPad, a custom widget;
-\i \c arrowpad.cpp tqcontains the implementation of \c ArrowPad;
-\i \c mainwindow.h tqcontains the definition of \c MainWindow, a subclass of
+\i \c arrowpad.h contains the definition of \c ArrowPad, a custom widget;
+\i \c arrowpad.cpp contains the implementation of \c ArrowPad;
+\i \c mainwindow.h contains the definition of \c MainWindow, a subclass of
    \l QMainWindow
-\i \c mainwindow.cpp tqcontains the implementation of \c MainWindow;
-\i \c main.cpp tqcontains main().
+\i \c mainwindow.cpp contains the implementation of \c MainWindow;
+\i \c main.cpp contains main().
 \endlist
 
 \index tt2.pro
@@ -814,7 +814,7 @@ conflict between \e \&Bestand and \e \&Boven.
 \index Portuguese Language
 \index Brazilian Language
 
-We've included a translation file, \c tt3_pt.ts, which tqcontains some
+We've included a translation file, \c tt3_pt.ts, which contains some
 Portuguese translations for this example.
 
 \index Troll Print
@@ -834,11 +834,11 @@ Version 1.0 consists of these files:
 \index tt3_pt.ts
 
 \list
-\i \c printpanel.h tqcontains the definition of PrintPanel;
-\i \c printpanel.cpp tqcontains the implementation of PrintPanel;
-\i \c mainwindow.h tqcontains the definition of \c MainWindow;
-\i \c mainwindow.cpp tqcontains the implementation of \c MainWindow;
-\i \c main.cpp tqcontains main();
+\i \c printpanel.h contains the definition of PrintPanel;
+\i \c printpanel.cpp contains the implementation of PrintPanel;
+\i \c mainwindow.h contains the definition of \c MainWindow;
+\i \c mainwindow.cpp contains the implementation of \c MainWindow;
+\i \c main.cpp contains main();
 \i \c tt3.pro is the \e qmake project file.
 \i \c tt3_pt.ts is the Portuguese message file.
 \endlist
@@ -893,7 +893,7 @@ translation shortly.
 
 \index MainWindow!in Translation Tutorial
 
-The header file for \c MainWindow, \c mainwindow.h, tqcontains no
+The header file for \c MainWindow, \c mainwindow.h, contains no
 surprises. In the implementation, \c mainwindow.cpp, we have some
 user-visible source texts that must be marked for translation.
 
@@ -976,10 +976,10 @@ for the second pair of radio buttons:
 Now run \l lupdate and open \c tt3_pt.ts with \e {Qt Linguist}. You
 should now see two changes.
 
-First, the translation source file now tqcontains \e three "Enabled",
+First, the translation source file now contains \e three "Enabled",
 "Disabled" pairs. The first pair is marked "(obs.)" signifying that they
 are obsolete. This is because these texts appeared in \c tr() calls that
-have been tqreplaced by new calls with two arguments. The second pair has
+have been replaced by new calls with two arguments. The second pair has
 "two-sided" as their comment, and the third pair has "colors" as their
 comment. The comments are shown in the \e {Source text and comments}
 area in \e {Qt Linguist}.
@@ -1013,9 +1013,9 @@ the translator.
 \index Comments!for Translators
 
 An additional way of helping the translator is to provide information on
-how to navigate to the particular part of the application that tqcontains
+how to navigate to the particular part of the application that contains
 the source texts they must translate. This helps them see the context
-in which the translation appears and also helps them to tqfind and test
+in which the translation appears and also helps them to find and test
 the translations. This can be achieved by using a \e TRANSLATOR comment
 in the source code:
 \code
@@ -1036,7 +1036,7 @@ You should see the comments in the \e {Source text and comments} area
 as you browse through the list of source texts.
 
 Sometimes, particularly with large programs, it can be difficult for
-the translator to tqfind their translations and check that they're
+the translator to find their translations and check that they're
 correct. Comments that provide good navigation information can save
 them time: