Index: openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl,v
diff -u -N -r1.39 -r1.40
--- openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl	30 Sep 2018 15:56:17 -0000	1.39
+++ openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl	3 Nov 2018 18:58:49 -0000	1.40
@@ -254,7 +254,7 @@
     # (C) If neither A or B apply (e.g., because an invalid charset
     # name was given to the charset parameter), we default to
     # "binary". This corresponds to the behavior of
-    # [ns_encodingfortype].  Also note, that the RFCs 3023 and 2616 do
+    # [ns_encodingfortype].  Also note that the RFCs 3023 and 2616 do
     # not state any procedure when "invalid" charsets etc. are
     # identified. I assume, RFC-compliant clients have to ignore them
     # which means keep the channel in- and output unfiltered (encoding