returns nothing |
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
DCOP Enabling (Export) Extensions
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.
@@ -61,14 +61,14 @@ are two Python modules that are included and installed as part of PyKDE.
Calling DCOP Methods
-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.
Collection the Information
-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.
@@ -174,14 +174,14 @@ The DCOP extensions will support any of the following C++ data types:
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).
-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 ("<<" and ">>"). 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.
-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).
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 Troubleshooting
System Retquirements
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:
- sip
@@ -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.
-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.
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.
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.
Initialization and Finalization
@@ -153,7 +153,7 @@ Runs an arbitrary script in the interpreter and returns Python's result.
bool runString (char *str);
-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.
@@ -186,7 +186,7 @@ not affect the global interpreter lock.
Using libpythonize in an application
-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).
@@ -197,7 +197,7 @@ At present only the C++/C wrapper versions are available, and they're distribute
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.
You can contact me at this address: Jim Bublitz <jbublitz@nwinternet.com>
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
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)
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"))
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.