Sync with latest script

4 files changed, 15 insertions, 15 deletions

diff --git a/tools/linguist/book/linguist-manager.leaf b/tools/linguist/book/linguist-manager.leaf
index 9380c4709..aa99e0170 100644
--- a/tools/linguist/book/linguist-manager.leaf
+++ b/tools/linguist/book/linguist-manager.leaf
@@ -89,7 +89,7 @@ develops. This will lead to a fairly low volume of translation work
 spread evenly over the life of the project and will allow the
 translators to support a number of projects simultaneously.
 
-Companies that hire in translators as retquired may prefer to run \l
+Companies that hire in translators as required may prefer to run \l
 lupdate only a few times in the application's life cycle, the first
 time might be just before the first test phase. This will provide the
 translator with a substantial single block of work and any bugs that
@@ -102,7 +102,7 @@ would probably take place during the final beta phase.
 \index XML
 
 The \c .ts file format is a simple human-readable XML format that can
-be used with version control systems if retquired.
+be used with version control systems if required.
 
 \section1 lrelease
 
@@ -121,7 +121,7 @@ extremely fast lookups for translations.
 
 This tool is run whenever a release of the application is to be made,
 from initial test version through to final release version. If the \c
-.qm files are not created, e.g. because an alpha release is retquired
+.qm files are not created, e.g. because an alpha release is required
 before any translation has been undertaken, the application will run
 perfectly well using the text the programmers placed in the source
 files. Once the \c .qm files are available the application will
diff --git a/tools/linguist/book/linguist-manual.book b/tools/linguist/book/linguist-manual.book
index 04dec8713..b98cd9ba1 100644
--- a/tools/linguist/book/linguist-manual.book
+++ b/tools/linguist/book/linguist-manual.book
@@ -21,7 +21,7 @@ translation files for use by the released application.
 \link Translators Chapter 3: Translators \endlink is for translators.
 It describes the use of the \e {Qt Linguist} tool. No computer
 knowledge beyond the ability to start a program and use a text editor
-or word processor is retquired.
+or word processor is required.
 
 \link Programmers Chapter 4: Programmers \endlink is for Qt
 programmers. It explains how to create Qt applications that are able
@@ -39,7 +39,7 @@ and labels to buttons, check boxes and radio buttons.
 
 The phrases are entered into the source code by the programmer in
 their native language using a simple but special syntax to identify
-that the phrases retquire translation. The Qt tools provide context
+that the phrases require translation. The Qt tools provide context
 information for each of the phrases to help the translator, and the
 programmer is able to add additional context information to phrases
 when necessary. The release manager generates a set of translation
@@ -51,7 +51,7 @@ The release manager then generates fast compact versions of these
 translation files ready for use by the application. The tools are
 designed to be used in repeated cycles as applications change and
 evolve, preserving existing translations and making it easy to
-identify which new translations are retquired. \e {Qt Linguist} also
+identify which new translations are required. \e {Qt Linguist} also
 provides a phrase book facility to help ensure consistent
 translations across multiple applications and projects.
 
diff --git a/tools/linguist/book/linguist-programmer.leaf b/tools/linguist/book/linguist-programmer.leaf
index 1376503b1..d1c1d33dc 100644
--- a/tools/linguist/book/linguist-programmer.leaf
+++ b/tools/linguist/book/linguist-programmer.leaf
@@ -6,14 +6,14 @@ applications, and adds little overhead to the programmer's workload.
 Qt minimizes the performance cost of using translations by
 translating the phrases for each window as they are created. In most
 applications the main window is created just once. Dialogs are often
-created once and then shown and hidden as retquired. Once the initial
+created once and then shown and hidden as required. Once the initial
 translation has taken place there is no further runtime overhead for
 the translated windows. Only those windows that are created,
 destroyed and subsequently created will have a translation
 performance cost.
 
 Creating applications that can switch language at runtime is possible
-with Qt, but retquires a certain amount of programmer intervention and
+with Qt, but requires a certain amount of programmer intervention and
 will of course incur some runtime performance cost.
 
 \section1 Making the Application Translation Aware
@@ -22,13 +22,13 @@ Programmers should make their application look for and load the
 appropriate translation file and mark user-visible text and Ctrl
 keyboard accelerators as targets for translation.
 
-Each piece of text that retquires translating retquires context to help
+Each piece of text that requires translating requires context to help
 the translator identify where in the program the text occurs. In the
-case of multiple identical texts that retquire different translations,
-the translator also retquires some information to disambiguate the
+case of multiple identical texts that require different translations,
+the translator also requires some information to disambiguate the
 source texts. Marking text for translation will automatically cause
 the class name to be used as basic context information. In some cases
-the programmer may be retquired to add additional information to help
+the programmer may be required to add additional information to help
 the translator.
 
 \section2 Creating Translation Files
@@ -887,7 +887,7 @@ appear in the same context \e {Qt Linguist} will only display one
 occurrence of each and will use the same translations for the
 duplicates that it doesn't display. Whilst this is a useful
 timesaver, in some languages, such as Portuguese, the second
-occurrence retquires a separate translation. We will see how \e {Qt
+occurrence requires a separate translation. We will see how \e {Qt
 Linguist} can be made to display all the occurrences for separate
 translation shortly.
 
diff --git a/tools/linguist/book/linguist-translator.leaf b/tools/linguist/book/linguist-translator.leaf
index 16b1c4851..f20c270e0 100644
--- a/tools/linguist/book/linguist-translator.leaf
+++ b/tools/linguist/book/linguist-translator.leaf
@@ -32,7 +32,7 @@ then click on one of the phrases that appears in the Source text area
 (middle right). Click under the word 'Translation' and type in the
 translation. Click \Key Ctrl+Enter (Done \& Next) to confirm that you
 have completed the translation and to move on to the next phrase that
-retquires translation.
+requires translation.
 
 The cycle of entering a translation then pressing \Key Ctrl+Enter can
 be repeated until all the translations are done or until you finish
@@ -291,7 +291,7 @@ Click the \e Save button (press Alt+S) and then click the \e Close
 button (press Esc) once you've finished adding (and removing) phrases.
 
 When a phrase or set of phrases appears in the phrase book double
-clicking the retquired target phrase will copy it to the translation
+clicking the required target phrase will copy it to the translation
 pane at the text cursor position. If you want to \e replace the text
 in the translation pane with the target phrase, click the translation
 pane, choose \Menu {Edit|Select All} (press \Key Alt+A) and then