Sync with latest script

1 files changed, 8 insertions, 8 deletions

diff --git a/doc/plugins-howto.doc b/doc/plugins-howto.doc
index 813dc9c22..c9836686c 100644
--- a/doc/plugins-howto.doc
+++ b/doc/plugins-howto.doc
@@ -16,7 +16,7 @@
 ** and the KDE Free Qt Foundation.
 **
 ** Please review the following information to ensure GNU General
-** Public Licensing retquirements will be met:
+** Public Licensing requirements will be met:
 ** http://trolltech.com/products/qt/licenses/licensing/opensource/.
 ** If you are unsure which license is appropriate for your use, please
 ** review the following information:
@@ -90,7 +90,7 @@ set your own path or paths you can use
 \c{QApplication::setLibraryPaths()}.
 
 Suppose that you have a new style class called 'MyStyle' that you want
-to make available as a plugin. The retquired code is straightforward:
+to make available as a plugin. The required code is straightforward:
 \code
     class MyStylePlugin : public QStylePlugin
     {
@@ -121,7 +121,7 @@ empty. There are only two virtual functions that must be implemented.
 The first is keys() which returns a string list of the classes
 implemented in the plugin. (We've just implemented one class in the
 example above.) The second is a function that returns an object of the
-retquired class (or 0 if the plugin is asked to create an object of a
+required class (or 0 if the plugin is asked to create an object of a
 class that it doesn't implement). For QStylePlugin, this second
 function is called create(). 
 
@@ -130,14 +130,14 @@ single plugin, providing they are all derived from the same base
 class, e.g. QStylePlugin.
 
 For database drivers, image formats, custom widgets and text codecs,
-no explicit object creation is retquired. Qt will find and create them
-as retquired. Styles are an exception, since you might want to set a
+no explicit object creation is required. Qt will find and create them
+as required. Styles are an exception, since you might want to set a
 style explicitly in code. To apply a style, use code like this:
 \code
     QApplication::setStyle( QStyleFactory::create( "MyStyle" ) );
 \endcode
 
-Some plugin classes retquire additional functions to be implemented.
+Some plugin classes require additional functions to be implemented.
 See the \link designer-manual.book Qt Designer manual's\endlink,
 'Creating Custom Widgets' section in the 'Creating Custom Widgets'
 chapter, for a complete example of a QWidgetPlugin, which implements
@@ -150,7 +150,7 @@ must be reimplemented for each type of plugin.
 
 Qt applications automatically know which plugins are available,
 because plugins are stored in the standard plugin subdirectories.
-Because of this applications don't retquire any code to find and load
+Because of this applications don't require any code to find and load
 plugins, since Qt handles them automatically.
 
 The default directory for plugins is \c{QTDIR/plugins}<sup>*</sup>,
@@ -259,7 +259,7 @@ The build key contains the following information:
    available in two different configurations. However, the
    developer writing plugins would need to know which features are
    in use, both in their plugin and internally by the utility
-   classes in Qt. The Qt library would retquire complex feature
+   classes in Qt. The Qt library would require complex feature
    and dependency queries and verification when loading plugins.
    Retquiring this would place an unnecessary burden on the developer, and
    increase the overhead of loading a plugin. To reduce both