summaryrefslogtreecommitdiffstats
path: root/doc/html/tqpair.html
diff options
context:
space:
mode:
Diffstat (limited to 'doc/html/tqpair.html')
-rw-r--r--doc/html/tqpair.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/html/tqpair.html b/doc/html/tqpair.html
index 23a14401..06358d91 100644
--- a/doc/html/tqpair.html
+++ b/doc/html/tqpair.html
@@ -62,12 +62,12 @@ values that contains two values of type T1 and T2. Please note
that TQPair does not store pointers to the two elements; it holds a
copy of every member. This is why these kinds of classes are
called <em>value based</em>. If you're interested in <em>pointer based</em>
-classes see, for example, <a href="ntqptrlist.html">TQPtrList</a> and <a href="ntqdict.html">TQDict</a>.
+classes see, for example, <a href="tqptrlist.html">TQPtrList</a> and <a href="ntqdict.html">TQDict</a>.
<p> TQPair holds one copy of type T1 and one copy of type T2, but does
not provide iterators to access these elements. Instead, the two
elements (<tt>first</tt> and <tt>second</tt>) are public member variables of
the pair. TQPair owns the contained elements. For more relaxed
-ownership semantics, see <a href="ntqptrcollection.html">TQPtrCollection</a> and friends which are
+ownership semantics, see <a href="tqptrcollection.html">TQPtrCollection</a> and friends which are
pointer-based containers.
<p> Some classes cannot be used within a TQPair: for example, all
classes derived from <a href="tqobject.html">TQObject</a> and thus all classes that implement