Update to latest tqt3 automated conversion

1 files changed, 1 insertions, 1 deletions

diff --git a/doc/html/designer-manual-5.html b/doc/html/designer-manual-5.html
index 963375215..d2f605fce 100644
--- a/doc/html/designer-manual-5.html
+++ b/doc/html/designer-manual-5.html
@@ -96,7 +96,7 @@ body { background: #ffffff; color: black; }
 <p>The <tt>ui.h</tt> extension approach has one disadvantage compared to subclassing. The <tt>ui.h</tt> file only contains custom slot implementations, but the objects are still entirely constructed and destructed inside the generated <tt>form.cpp</tt> code. This leaves the user without the possibility of doing further form initializations or cleanups that you normally would do within the constructor and destructor functions of a C++ class.</p>
 <p>To work around this limitation, we created the init/destroy convention. If you add a slot <tt>Form::init()</tt> to your form, this slot will be called automatically at the end of the generated form constructor. Similarly, if you add a slot <tt>Form::destroy()</tt> to your form, the slot will automatically be invoked by the destructor before any form controls get deleted. (These slots should return void.) If you prefer to use your own editor you must still create these functions in <em>TQt Designer</em>; once created you can then write your implementation code either using <em>TQt Designer</em>'s C++ editor plugin or using your own editor.</p>
 <h3><a name="4"></a>Loading forms dynamically</h3>
-<p>We extracted the part of <em>TQt Designer</em> that is responsible for loading and previewing a form into a library of its own, <tt>libtqui</tt>. A new class <a href="qwidgetfactory.html">TQWidgetFactory</a> makes it possible to load <tt>.ui</tt> files at runtime and instantiate forms from them.</p>
+<p>We extracted the part of <em>TQt Designer</em> that is responsible for loading and previewing a form into a library of its own, <tt>libtqui</tt>. A new class <a href="ntqwidgetfactory.html">TQWidgetFactory</a> makes it possible to load <tt>.ui</tt> files at runtime and instantiate forms from them.</p>
 <p>This dynamic approach keeps the GUI design and the code separate and is useful in environments where the GUI may have to change more often than the underlying application logic. Ultimately, you can provide users of your application the ability to modify the graphical user interface without the need for a complete C++ development environment.</p>
 <p>Since the .ui file is not compiled it cannot include any C++ code, (e.g. custom slot implementations). We provide a way of adding those implementations via a controlling TQObject subclass that you pass as receiver to the widget factory.</p>
 <p>This concept and its usage is explained in detail in the <a href="designer-manual-6.html">Subclassing and Dynamic Dialogs</a> chapter.</p>