Sync with latest script

1 files changed, 3 insertions, 3 deletions

diff --git a/doc/html/porting2.html b/doc/html/porting2.html
index 9f44766e3..723a4e0a0 100644
--- a/doc/html/porting2.html
+++ b/doc/html/porting2.html
@@ -64,7 +64,7 @@ compiler errors (rather than mysterious results), or produce run-time
 messages.  The result is that TQt 2.x includes many additional features,
 discards obsolete functionality that is easily converted to use the new
 features, and that porting an application from TQt 1.x to TQt 2.x is
-a simple task well worth the amount of effort retquired.
+a simple task well worth the amount of effort required.
 <p> To port code using TQt 1.x to use TQt 2.x:
 <p> <ul>
 <li> Briefly read the porting notes below to get an idea of what to expect.
@@ -224,7 +224,7 @@ you use that you will incur a performance penalty since all TQt functions
 that took const char* now take const TQString&.
 <p> <p>
 To take full advantage of the new <a href="i18n.html#internationalization">Internationalization</a>
-functionality in TQt 2.x, the following steps are retquired:
+functionality in TQt 2.x, the following steps are required:
 <p> <ul>
 <li> Start converting all uses of "const char*" in parameters to
 "const TQString&" - this can often be done mechanically, eg.
@@ -784,7 +784,7 @@ use it outside a member function, you'll need to prefix with TQt::.
 <p> <h3><a name="TQPicture">TQPicture</a></h3>
 <p> <p>The binary storage format of <a href="qpicture.html">TQPicture</a> is changed, but the TQt 2.x
 TQPicture class can both read and write TQt 1.x format TQPictures. No
-special handling is retquired for reading; TQPicture will automatically
+special handling is required for reading; TQPicture will automatically
 detect the version number. In order to write a TQt 1.x format TQPicture,
 set the formatVersion parameter to 1 in the TQPicture constructor.
 <p> <p>For writing TQt 1.x format TQPictures, the compatibility issues of <a