Rename basic widget nt* related files to equivalent tq*

Signed-off-by: Michele Calgaro <michele.calgaro@yahoo.it>

1 files changed, 2 insertions, 2 deletions

diff --git a/doc/html/motif-walkthrough-5.html b/doc/html/motif-walkthrough-5.html
index bf6f75ab0..d6ad1178e 100644
--- a/doc/html/motif-walkthrough-5.html
+++ b/doc/html/motif-walkthrough-5.html
@@ -40,12 +40,12 @@ body { background: #ffffff; color: black; }
 have converted the <em>View</em> widget.  The <em>Print</em> dialog will be
 removed once we have finished our migration, since we will use
 <a href="tqprinter.html">TQPrinter</a> instead.  Based on this information, we decide that it is not
-worth replacing the <em>Print</em> dialog with a custom <a href="ntqdialog.html">TQDialog</a> replacement.
+worth replacing the <em>Print</em> dialog with a custom <a href="tqdialog.html">TQDialog</a> replacement.
 Instead, we will keep the <a href="motif-extension.html#Motif">Motif</a> based dialog and use <a href="qmotifdialog.html">TQMotifDialog</a> to
 integrate the dialog with the application.
 <p> <h2> Modality Requirements
 </h2>
-<a name="1"></a><p> Modality with TQDialog is different from Motif.  The <a href="ntqdialog.html#exec">TQDialog::exec</a>()
+<a name="1"></a><p> Modality with TQDialog is different from Motif.  The <a href="tqdialog.html#exec">TQDialog::exec</a>()
 function does not return until the dialog is finished.  In Motif,
 modality is simply a property of the shell, and the application
 programmer must write TQDialog::exec() style functionality if they