Update to latest tqt3 automated conversion

1 files changed, 3 insertions, 3 deletions

diff --git a/doc/html/emb-performance.html b/doc/html/emb-performance.html
index 3311941c..7906bba6 100644
--- a/doc/html/emb-performance.html
+++ b/doc/html/emb-performance.html
@@ -47,8 +47,8 @@ requirements at the cost of other factors.
 </h2>
 <a name="1"></a><p> The following guidelines will improve CPU performance:
 <ul>
-<li> Create dialogs and widgets once, then <a href="qwidget.html#hide">TQWidget::hide</a>() and
-<a href="qwidget.html#show">TQWidget::show</a>() them, rather than creating them and deleting
+<li> Create dialogs and widgets once, then <a href="ntqwidget.html#hide">TQWidget::hide</a>() and
+<a href="ntqwidget.html#show">TQWidget::show</a>() them, rather than creating them and deleting
 them every time they are needed.
 This will use a little more memory, but will be much faster.
 Try to create them the first time "lazily" to avoid slow
@@ -75,7 +75,7 @@ you run configure.
 <p> To build your application suite as an all-in-one application, design each
 application as a stand-alone widget or set of widgets, with only minimal
 code in the main() function. Then, write an application that gives
-some way to switch between the applications (e.g. a <a href="qiconview.html">TQIconView</a>).
+some way to switch between the applications (e.g. a <a href="ntqiconview.html">TQIconView</a>).
 <a href="http://www.trolltech.com/products/qtopia/index.html">TQtopia</a> is an example of this. It can be built either as a set of
 dynamically linked executables, or as a single static application.
 <p> Note that you should generally still link dynamically against the