Rename threading nt* related files to equivalent tq*

Signed-off-by: Michele Calgaro <[email protected]>

1 files changed, 1 insertions, 1 deletions

diff --git a/doc/man/man3/tqmap.3qt b/doc/man/man3/tqmap.3qt
index 6630c43a5..169d558d6 100644
--- a/doc/man/man3/tqmap.3qt
+++ b/doc/man/man3/tqmap.3qt
@@ -324,7 +324,7 @@ It is safe to have multiple iterators at the same time. If some member of the ma
 .PP
 Since TQMap is value-based, there is no need to be concerned about deleting items in the map. The map holds its own copies and will free them if the corresponding member or the map itself is deleted.
 .PP
-TQMap is implicitly shared. This means you can just make copies of the map in time O(1). If multiple TQMap instances share the same data and one is modifying the map's data, this modifying instance makes a copy and modifies its private copy: so it does not affect other instances. If a TQMap is being used in a multi-threaded program, you must protect all access to the map. See QMutex.
+TQMap is implicitly shared. This means you can just make copies of the map in time O(1). If multiple TQMap instances share the same data and one is modifying the map's data, this modifying instance makes a copy and modifies its private copy: so it does not affect other instances. If a TQMap is being used in a multi-threaded program, you must protect all access to the map. See TQMutex.
 .PP
 There are a couple of ways of inserting new items into the map. One uses the insert() method; the other uses operator[]:
 .PP