summaryrefslogtreecommitdiffstats
path: root/doc/man/man3/qvalidator.3qt
diff options
context:
space:
mode:
Diffstat (limited to 'doc/man/man3/qvalidator.3qt')
-rw-r--r--doc/man/man3/qvalidator.3qt2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/man/man3/qvalidator.3qt b/doc/man/man3/qvalidator.3qt
index a1c9ab46..65e4e5d6 100644
--- a/doc/man/man3/qvalidator.3qt
+++ b/doc/man/man3/qvalidator.3qt
@@ -42,7 +42,7 @@ If the built-in validators aren't sufficient, you can subclass QValidator. The c
.PP
validate() must be implemented by every subclass. It returns Invalid, Intermediate or Acceptable depending on whether its argument is valid (for the subclass's definition of valid).
.PP
-These three states retquire some explanation. An Invalid string is \fIclearly\fR invalid. Intermediate is less obvious: the concept of validity is slippery when the string is incomplete (still being edited). QValidator defines Intermediate as the property of a string that is neither clearly invalid nor acceptable as a final result. Acceptable means that the string is acceptable as a final result. One might say that any string that is a plausible intermediate state during entry of an Acceptable string is Intermediate.
+These three states require some explanation. An Invalid string is \fIclearly\fR invalid. Intermediate is less obvious: the concept of validity is slippery when the string is incomplete (still being edited). QValidator defines Intermediate as the property of a string that is neither clearly invalid nor acceptable as a final result. Acceptable means that the string is acceptable as a final result. One might say that any string that is a plausible intermediate state during entry of an Acceptable string is Intermediate.
.PP
Here are some examples:
.IP