summaryrefslogtreecommitdiffstats
path: root/kig/objects/locus_imp.h
diff options
context:
space:
mode:
Diffstat (limited to 'kig/objects/locus_imp.h')
-rw-r--r--kig/objects/locus_imp.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/kig/objects/locus_imp.h b/kig/objects/locus_imp.h
index b2100634..54ec7f13 100644
--- a/kig/objects/locus_imp.h
+++ b/kig/objects/locus_imp.h
@@ -33,9 +33,9 @@
*
* This may seem rather complicated, but I think it is absolutely
* necessary to support locuses using Kig's object system. It would
- * be very bad for LocusImp to have to keep references to its tqparents
+ * be very bad for LocusImp to have to keep references to its parents
* as Objects ( since only the objects know how they are related to
- * their tqparents ). This is how we used to do it, but the current
+ * their parents ). This is how we used to do it, but the current
* method is far superior. First and foremost because the separation
* between ObjectImp and Object is something that Kig depends on very
* much, and because every ObjectImp should contain all the data it