Rename graphics class nt* related files to equivalent tq* (part 2)

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

1 files changed, 1 insertions, 1 deletions

diff --git a/doc/man/man3/tqnpinstance.3qt b/doc/man/man3/tqnpinstance.3qt
index d487239cd..1c2e2dabf 100644
--- a/doc/man/man3/tqnpinstance.3qt
+++ b/doc/man/man3/tqnpinstance.3qt
@@ -113,7 +113,7 @@ The QNPInstance is responsible for creating an appropriate QNPWidget window if r
 .PP
 Note that there is \fIabsolutely no guarantee\fR regarding the order in which functions are called. Sometimes the browser will call newWindow() first, at other times, newStreamCreated() will be called first (assuming the \fC<EMBED>\fR tag has a SRC parameter).
 .PP
-\fINone of Qt's GUI functionality\fR may be used until after the first call to newWindow(). This includes any use of TQPaintDevice (i.e. QPixmap, TQWidget, and all subclasses), QApplication, anything related to TQPainter (TQBrush, etc.), fonts, TQMovie, TQToolTip, etc. Useful classes which specifically \fIcan\fR be used are TQImage, TQFile, and TQBuffer.
+\fINone of Qt's GUI functionality\fR may be used until after the first call to newWindow(). This includes any use of TQPaintDevice (i.e. TQPixmap, TQWidget, and all subclasses), QApplication, anything related to TQPainter (TQBrush, etc.), fonts, TQMovie, TQToolTip, etc. Useful classes which specifically \fIcan\fR be used are TQImage, TQFile, and TQBuffer.
 .PP
 This restriction can easily be accommodated by structuring your plugin so that the task of the QNPInstance is to gather data, while the task of the QNPWidget is to provide a graphical interface to that data.
 .SS "Member Type Documentation"