1 files changed, 3 insertions, 3 deletions
diff --git a/doc/man/man3/qwidget.3qt b/doc/man/man3/qwidget.3qt
index 007f06f2f..2da51743d 100644
--- a/doc/man/man3/qwidget.3qt
+++ b/doc/man/man3/qwidget.3qt
@@ -1028,7 +1028,7 @@ Every widget's constructor accepts two or three standard arguments: <ol type=1>
 .IP 1
 \fCQWidget *parent = 0\fR is the parent of the new widget. If it is 0 (the default), the new widget will be a top-level window. If not, it will be a child of \fIparent\fR, and be constrained by \fIparent\fR's geometry (unless you specify WType_TopLevel as widget flag).
 .IP 2
-\fCconst char *name = 0\fR is the widget name of the new widget. You can access it using name(). The widget name is little used by programmers but is tquite useful with GUI builders such as \fIQt Designer\fR (you can name a widget in \fIQt Designer\fR, and connect() to it using the name in your code). The dumpObjectTree() debugging function also uses it.
+\fCconst char *name = 0\fR is the widget name of the new widget. You can access it using name(). The widget name is little used by programmers but is quite useful with GUI builders such as \fIQt Designer\fR (you can name a widget in \fIQt Designer\fR, and connect() to it using the name in your code). The dumpObjectTree() debugging function also uses it.
 .IP 3
 \fCWFlags f = 0\fR (where available) sets the widget flags; the default is suitable for almost all widgets, but to get, for example, a top-level widget without a window system frame, you must use special flags.
 .PP
@@ -1049,7 +1049,7 @@ mousePressEvent() - called when a mouse button is pressed. There are six mouse-r
 mouseReleaseEvent() - called when a mouse button is released. A widget receives mouse release events when it has received the corresponding mouse press event. This means that if the user presses the mouse inside \fIyour\fR widget, then drags the mouse to somewhere else, then releases, \fIyour\fR widget receives the release event. There is one exception: if a popup menu appears while the mouse button is held down, this popup immediately steals the mouse events.
 .IP
 .TP
-mouseDoubleClickEvent() - not tquite as obvious as it might seem. If the user double-clicks, the widget receives a mouse press event (perhaps a mouse move event or two if they don't hold the mouse tquite steady), a mouse release event and finally this event. It is \fInot possible\fR to distinguish a click from a double click until you've seen whether the second click arrives. (This is one reason why most GUI books recommend that double clicks be an extension of single clicks, rather than trigger a different action.)
+mouseDoubleClickEvent() - not quite as obvious as it might seem. If the user double-clicks, the widget receives a mouse press event (perhaps a mouse move event or two if they don't hold the mouse quite steady), a mouse release event and finally this event. It is \fInot possible\fR to distinguish a click from a double click until you've seen whether the second click arrives. (This is one reason why most GUI books recommend that double clicks be an extension of single clicks, rather than trigger a different action.)
 .IP
 .PP
 If your widget only contains child widgets, you probably do not need to implement any event handlers. If you want to detect a mouse click in a child widget call the child's hasMouse() function inside the parent widget's mousePressEvent().
@@ -1247,7 +1247,7 @@ The QApplication::lastWindowClosed() signal is emitted when the last visible top
 .PP
 Note that closing the QApplication::mainWidget() terminates the application.
 .PP
-See also closeEvent(), QCloseEvent, hide(), QApplication::tquit(), QApplication::setMainWidget(), and QApplication::lastWindowClosed().
+See also closeEvent(), QCloseEvent, hide(), QApplication::quit(), QApplication::setMainWidget(), and QApplication::lastWindowClosed().
 .SH "void QWidget::closeEvent ( QCloseEvent * e )\fC [virtual protected]\fR"
 This event handler, for event \fIe\fR, can be reimplemented in a subclass to receive widget close events.
 .PP