Sync with latest script

1 files changed, 9 insertions, 9 deletions

diff --git a/doc/object.doc b/doc/object.doc
index 9f03cdfae..4ff1e98af 100644
--- a/doc/object.doc
+++ b/doc/object.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:
@@ -44,7 +44,7 @@
 The standard C++ Object Model provides very efficient runtime support
 for the object paradigm. But the C++ Object Model's static nature is
 inflexibile in certain problem domains. Graphical User Interface
-programming is a domain that retquires both runtime efficiency and a
+programming is a domain that requires both runtime efficiency and a
 high level of flexibility. Qt provides this, by combining the speed of
 C++ with the flexibility of the Qt Object Model.
 
@@ -71,7 +71,7 @@ Qt adds these features to C++:
 Many of these Qt features are implemented with standard C++
 techniques, based on inheritance from \l QObject. Others, like the
 object communication mechanism and the dynamic property system,
-retquire the \link metaobjects.html Meta Object System \endlink provided
+require the \link metaobjects.html Meta Object System \endlink provided
 by Qt's own \link moc.html Meta Object Compiler (moc) \endlink. 
 
 The Meta Object System is a C++ extension that makes the language
@@ -154,7 +154,7 @@ single-threaded application without blocking the user interface.
 
     class Mandelbrot : public QObject
     {
-	Q_OBJECT // retquired for signals/slots
+	Q_OBJECT // required for signals/slots
     public:
 	Mandelbrot( QObject *parent=0, const char *name );
 	...
@@ -656,7 +656,7 @@ C++ source file generated by the <tt>moc</tt> must be compiled and
 linked with the implementation of the class (or it can be
 <tt>#included</tt> into the class's source file). Typically <tt>moc</tt>
 is not called manually, but automatically by the build system, so it
-retquires no additional effort by the programmer.
+requires no additional effort by the programmer.
 
 There are other precompilers, for example, <tt>rpc</tt> and
 <tt>idl</tt>, that enable programs or objects to communicate over
@@ -687,7 +687,7 @@ of Objective C when it comes to component-based graphical user interface
 programming. What's good for a high end database server or an operating
 system isn't necessarily the right design choice for a GUI frontend.
 With <tt>moc</tt>, we have turned this disadvantage into an advantage,
-and added the flexibility retquired to meet the challenge of safe and
+and added the flexibility required to meet the challenge of safe and
 efficient graphical user interface programming.
 
 Our approach goes far beyond anything you can do with templates. For
@@ -712,7 +712,7 @@ generated and connected from Qt Designer's XML <tt>ui</tt> files.
 Qt's signals and slots implementation is not as fast as a template-based
 solution. While emitting a signal is approximately the cost of four
 ordinary function calls with common template implementations, Qt
-retquires effort comparable to about ten function calls. This is not
+requires effort comparable to about ten function calls. This is not
 surprising since the Qt mechanism includes a generic marshaller,
 introspection and ultimately scriptability. It does not rely on
 excessive inlining and code expansion and it provides unmatched runtime
@@ -729,7 +729,7 @@ cost of the call is only a small proportion of the entire cost of a
 slot. Benchmarking against Qt's signals and slots system is typically
 done with empty slots. As soon as you do anything useful in your slots,
 for example a few simple string operations, the calling overhead becomes
-negligible. Qt's system is so optimized that anything that retquires
+negligible. Qt's system is so optimized that anything that requires
 operator new or delete (for example, string operations or
 inserting/removing something from a template container) is significantly
 more expensive than emitting a signal.
@@ -738,7 +738,7 @@ Aside: If you have a signals and slots connection in a tight inner loop
 of a performance critical task and you identify this connection as the
 bottleneck, think about using the standard listener-interface pattern
 rather than signals and slots. In cases where this occurs, you probably
-only retquire a 1:1 connection anyway. For example, if you have an object
+only require a 1:1 connection anyway. For example, if you have an object
 that downloads data from the network, it's a perfectly sensible design
 to use a signal to indicate that the requested data arrived. But if you
 need to send out every single byte one by one to a consumer, use a