Fix retquire

9 files changed, 19 insertions, 19 deletions

diff --git a/doc/classref/tdecore/KCmdLineArgs.html b/doc/classref/tdecore/KCmdLineArgs.html
index 8cb2bbf..005040e 100644
--- a/doc/classref/tdecore/KCmdLineArgs.html
+++ b/doc/classref/tdecore/KCmdLineArgs.html
@@ -54,7 +54,7 @@
 </table>
 </td><td width="50%"><table><tr><td>A Pytbon list of tuples (name, description, default) is the first parameter
 instead of a KCmdLineOptions object (KCmdLineOptions is not used);
-NULL (or None) parameters to mark the end of the list are not retquired
+NULL (or None) parameters to mark the end of the list are not required
 </td></tr></table></td></tr></table></li><hr>
 <li><b>addTempFileOption</b> ()
 <table width = "100%"><tr><td width="50%" valign="top"><table><tr><td>returns <i>nothing</i></td></tr>
diff --git a/doc/dcopext.html b/doc/dcopext.html
index a22fa6f..f2786e9 100644
--- a/doc/dcopext.html
+++ b/doc/dcopext.html
@@ -48,7 +48,7 @@ Python classes, and the method being called looks to the programmer like a Pytho
 <dt>DCOP Enabling (Export) Extensions</dt>
 <dd>
 Another set of extensions makes it trivial to expose an application's methods via DCOP to 
-other applications. All that is retquired is to subclass a pre-written Python class and
+other applications. All that is required is to subclass a pre-written Python class and
 provide a list of the methods to expose, along with a method signature listing the name
 of the method, it's return type, and the the types of its arguments.
 </dd>
@@ -61,14 +61,14 @@ are two Python modules that are included and installed as part of PyKDE.
 
 <h2>Calling DCOP Methods</h2>
 <p>
-Accessing a DCOP method in another application retquires 3 pieces of information: the name of
+Accessing a DCOP method in another application requires 3 pieces of information: the name of
 the application to be accessed, the name of the DCOP object which holds the method to be
 called, and the name of the method itself.
 </p>
 
 <h3>Collection the Information</h3>
 <p>
-The easiest way to collect the retquired information is to use the kdcop application that
+The easiest way to collect the required information is to use the kdcop application that
 comes with PyKDE. kdcop is graphical application that looks like the image shown. 
 </p>
 <IMG src="images/kdcop1.png" align="middle" border="0">
@@ -174,14 +174,14 @@ The DCOP extensions will support any of the following C++ data types:
 <p>
 Data conversion between C++ and Python types is done transparently. The integer types
 map to Python int or Python long, the decimal types to Python double. A Python string
-can be used for any argument that retquires a TQString or TQCString (return types will
+can be used for any argument that requires a TQString or TQCString (return types will
 always be the TQt object type). The TQValueList types take or return a Python list of the
 indicated object. The TQMap types take or return a Python dict with the first type as
 the key and the second type as data. All other types use the same object type in 
 Python and TQt (for instance, TQPoint or TQStringList).
 </p>
 <p>
-It's possible to add support for more types in the future. To be added, a type retquires
+It's possible to add support for more types in the future. To be added, a type requires
 a pair of overloaded TQDataStream operators ("&lt;&lt;" and "&gt;&gt;"). Types must also
 exist in the libs that PyTQt and PyKDE support - types specific to applications (like 
 konqueror) cannot be supported at this time.
diff --git a/doc/examples.html b/doc/examples.html
index 8a02747..8b409a9 100644
--- a/doc/examples.html
+++ b/doc/examples.html
@@ -89,7 +89,7 @@ pyKHTMLPart.py demonstrates importing KHTMLPart as a KPart.
 </p>
 <img src="images/khtmlpart.png" border=0>
 <p>
-The program is hard-coded to display the KDE website's main page, and retquires
+The program is hard-coded to display the KDE website's main page, and requires
 an active internet connection to do the display (it will be blank if no internet
 connection is active).
 </p>
diff --git a/doc/install.html b/doc/install.html
index 71fe7f0..a2dff56 100644
--- a/doc/install.html
+++ b/doc/install.html
@@ -26,7 +26,7 @@ Before reporting bugs, please read the <a href="trouble.html">Troubleshooting</a
 </p>
 <h2>System Retquirements</h2>
 <p>PyKDE only runs on Linux or other Unix-based systems. The usual tools (compiler,
-linker, make, etc) are retquired. In addition you need:
+linker, make, etc) are required. In addition you need:
 </p>
 <dl>
 <dt>sip</dt>
@@ -60,7 +60,7 @@ are in the same location as the PyTQt files (usually python/site-packages). Thes
 files are generated automatically if you build/compile sip and PyTQt from source.
 </p>
 <p>
-PyKDE also retquires the PyTQt sip files to build and compile. If you installed PyTQt from an 
+PyKDE also requires the PyTQt sip files to build and compile. If you installed PyTQt from an 
 RPM, you also need to have installed the corresponding "PyTQt-devel" RPM, which contains the 
 PyTQt sip files.
 </p>
diff --git a/doc/libpythonize.html b/doc/libpythonize.html
index 84a3e22..0aae9a2 100644
--- a/doc/libpythonize.html
+++ b/doc/libpythonize.html
@@ -32,7 +32,7 @@ The method descriptions here apply to both C and C++ versions unless noted.
 </p>
 <p>
 Although libpythonize is used with (and installed with) PyKDE, it has no dependencies itself on
-PyKDE/KDE, PyTQt/TQt or sip. It does retquire qmake from TrollTech (part of TQt) to build.
+PyKDE/KDE, PyTQt/TQt or sip. It does require qmake from TrollTech (part of TQt) to build.
 </p>
 
 <h2>Initialization and Finalization</h2>
@@ -153,7 +153,7 @@ Runs an arbitrary script in the interpreter and returns Python's result.
 <hr>
 <h3>bool  runString (char *str);</h3>
 <p>
-Runs an arbitrary string in the interpreter (indentation retquired for mulit-line
+Runs an arbitrary string in the interpreter (indentation required for mulit-line
 strings) and returns Python's result.
 </p>
 <hr>
@@ -186,7 +186,7 @@ not affect the global interpreter lock.
 <hr>
 <h2>Using libpythonize in an application</h2>
 <p>
-Include the pythonize.h header file (retquires Python.h) and link to libpythonize.so - that's pretty much it. There are unit tests
+Include the pythonize.h header file (requires Python.h) and link to libpythonize.so - that's pretty much it. There are unit tests
 in both C and C++ in the pythonize/tests/ subdirectory. An example of libpythonize usage is in pykpanelapplet.cpp in the
 PyKDE distribution (pykpanelapplet/ directory).
 </p>
@@ -197,7 +197,7 @@ At present only the C++/C wrapper versions are available, and they're distribute
 <p>
 The build process for libpythonize uses TrollTech's qmake (available as part of TQt), but is simple enough
 to be included in most make files. See the pythonize.pro file for more information - most of the additional
-libs retquired are retquired by libpython, and may vary by platform.
+libs required are required by libpython, and may vary by platform.
 </p>
 <p>
 You can contact me at  this address: <a href="mailto:jbublitz@nwinternet.com">Jim Bublitz &lt;jbublitz@nwinternet.com&gt;</a>
diff --git a/doc/limits.html b/doc/limits.html
index 9fb6107..71aef72 100644
--- a/doc/limits.html
+++ b/doc/limits.html
@@ -360,7 +360,7 @@ KSocks
 <P>
 Most of their functionality already exists in the Python socket class or in the
 KSocket class (tdecore module). These classes may be implemented at a future date
-(they retquire support for C socket structures and careful handling to avoid buffer
+(they require support for C socket structures and careful handling to avoid buffer
 overflow problems/exploits)
 </P>
 
diff --git a/doc/signal.html b/doc/signal.html
index 76599e6..51fa7b6 100644
--- a/doc/signal.html
+++ b/doc/signal.html
@@ -171,7 +171,7 @@ a.emit(PYSIGNAL("pySig"),("Hello","World"))</PRE
 ></TR
 ></TABLE
 ><P
->TQt allows a signal to be connected to a slot that retquires fewer arguments than
+>TQt allows a signal to be connected to a slot that requires fewer arguments than
 the signal passes.  The extra arguments are tquietly discarded.  Python slots
 can be used in the same way.</P
 ></DIV
diff --git a/doc/static.html b/doc/static.html
index a106dee..df876f4 100644
--- a/doc/static.html
+++ b/doc/static.html
@@ -160,7 +160,7 @@ to overload each of the pure virtual methods. Following a suggestion on the mail
 list, the docs attempt to flag all abstract classes and identify the pure virtual
 methods which must be overloaded in the derived class. Derived classes can be created
 in Python by writing Python methods to overload the pure virtual methods - no C++ code
-is retquired.
+is required.
 </P>
 
 <DIV CLASS="NAVFOOTER">
diff --git a/doc/switches.html b/doc/switches.html
index 1bc4018..21e5a6a 100644
--- a/doc/switches.html
+++ b/doc/switches.html
@@ -94,7 +94,7 @@ the compile has 128MB or less RAM.
 <td width = "40%"><u>configure.py Default:</u> python/site-packages/</td>
 <td width = "20%"> </td>
 </tr></table>
-Normally, the PyKDE modules are installed in python/site-packages. Writing to this directory retquires
+Normally, the PyKDE modules are installed in python/site-packages. Writing to this directory requires
 root access. RPM builders sometimes need to build the modules to a different directory, or you may want
 to install the modules in a different location (for example, in a subdirectory of site-packages/). For this
 option to be useful, you need to ensure that Python can still locate and import the PyKDE modules from
@@ -162,7 +162,7 @@ The path to KDE's library files (libtdecore.so, etc).
 <td width = "40%"><u>configure.py Default:</u> trinity/include</td>
 <td width = "20%"> </td>
 </tr></table>
-The path to KDE's h files. (May retquire installation of tdelibs3-devel rpm package)
+The path to KDE's h files. (May require installation of tdelibs3-devel rpm package)
 configure.py. PyKDE will locate h files in subdirectories of this path automatically (eg trinity/include/kio/*.h)
 </dd>
 <hr>
@@ -203,7 +203,7 @@ them on.
 <td width = "40%"><u>configure.py Default:</u> none</td>
 <td width = "20%"> </td>
 </tr></table>
-If your site retquires the use of more than one or two option switches, you can place all of the options
+If your site requires the use of more than one or two option switches, you can place all of the options
 in a text file and then reference only the text file's path and name on the command line. The options
 are placed in the text file just as they would be on the command line, with one option per line.
 For example, the options file for the command "python configure.py -c- -v /usr/local/PyTQt/sip" would look