Index: openacs-4/packages/xotcl-core/tcl/html-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/html-procs.tcl,v
diff -u -r1.3.2.2 -r1.3.2.3
--- openacs-4/packages/xotcl-core/tcl/html-procs.tcl	22 Apr 2017 16:59:39 -0000	1.3.2.2
+++ openacs-4/packages/xotcl-core/tcl/html-procs.tcl	22 Apr 2017 17:34:03 -0000	1.3.2.3
@@ -8,21 +8,21 @@
       # set taken from W3C on http://www.w3.org/TR/html4/index/elements.html
       #
 
-      # If the following flag is set to false, tdom makes no checks
+      # If the following flag is set to false, tDOM makes no checks
       # for valid XML character encodings. In particular, XML does not
       # allow characters below 0x20 besides #x9 | #xA | #xD (see XML
       # 1.0 fourth edition http://www.w3.org/TR/REC-xml/) although
       # these are valid UTF-8 characters (see rfc3629 or rfc2279). In
       # other words, XML does not accept all valid UTF-8 strings. HTML
       # does not seem to have this limitation.
       #
-      # CAUTION: Notice that when this flag is set, tdom accepts
-      # invalid XML characters even in XML documents.  If the tdom
+      # CAUTION: Notice that when this flag is set, tDOM accepts
+      # invalid XML characters even in XML documents.  If the tDOM
       # tree is generated in XML and send to a different parser, a
       # thorough XML parser will reject the document. So, this flag
       # has to be used with caution.
       #
-      # However, when the flag is not set, tdom complains about
+      # However, when the flag is not set, tDOM complains about
       # invalid input, so it would be necessary to strip all invalid
       # XML characters via string map etc., which is not nice
       # in the code and bad performance wise.