Sync with latest script

1 files changed, 7 insertions, 7 deletions

diff --git a/doc/html/plugins-howto.html b/doc/html/plugins-howto.html
index 97ecd683e..6ab263e87 100644
--- a/doc/html/plugins-howto.html
+++ b/doc/html/plugins-howto.html
@@ -71,7 +71,7 @@ with calls to <a href="qapplication.html#addLibraryPath">TQApplication::addLibra
 set your own path or paths you can use
 <a href="qapplication.html#setLibraryPaths">TQApplication::setLibraryPaths</a>().
 <p> 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:
 <pre>
     class MyStylePlugin : public <a href="qstyleplugin.html">TQStylePlugin</a>
     {
@@ -101,21 +101,21 @@ 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 <a href="qstyleplugin.html">TQStylePlugin</a>, this second
 function is called create(). 
 <p> It is possible to implement any number of plugin subclasses in a
 single plugin, providing they are all derived from the same base
 class, e.g. TQStylePlugin.
 <p> For database drivers, image formats, custom widgets and text codecs,
-no explicit object creation is retquired. TQt will find and create them
-as retquired. Styles are an exception, since you might want to set a
+no explicit object creation is required. TQt 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:
 <pre>
     TQApplication::<a href="qapplication.html#setStyle">setStyle</a>( TQStyleFactory::<a href="qstylefactory.html#create">create</a>( "MyStyle" ) );
 </pre>
  
-<p> Some plugin classes retquire additional functions to be implemented.
+<p> Some plugin classes require additional functions to be implemented.
 See the <a href="designer-manual.html">TQt Designer manual's</a>,
 'Creating Custom Widgets' section in the 'Creating Custom Widgets'
 chapter, for a complete example of a <a href="qwidgetplugin.html">TQWidgetPlugin</a>, which implements
@@ -126,7 +126,7 @@ TQWidgetPlugins.
 must be reimplemented for each type of plugin.
 <p> TQt 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 TQt handles them automatically.
 <p> The default directory for plugins is <tt>QTDIR/plugins</tt><sup>*</sup>,
 with each type of plugin in a subdirectory for that type, e.g. <tt>styles</tt>. If you want your applications to use plugins and you don't
@@ -210,7 +210,7 @@ determine if the plugin is binary compatible.
 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 TQt. The TQt library would retquire complex feature
+classes in TQt. The TQt 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