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.37 -r1.38
--- openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl	5 Aug 2018 21:16:25 -0000	1.37
+++ openacs-4/packages/xotcl-core/tcl/http-client-procs.tcl	28 Sep 2018 08:43:01 -0000	1.38
@@ -253,7 +253,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 behaviour of
+    # "binary". This corresponds to the behavior of
     # [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
@@ -759,7 +759,7 @@
   # TLS/SSL support
   #
   # Perform HTTPS requests via TLS (does not require nsopenssl)
-  # - requires tls 1.5.0 to be compiled into <aolsever>/lib/ ...
+  # - requires tls 1.5.0 to be compiled into <AOLserver>/lib/ ...
   # - - - - - - - - - - - - - - - - - - 
   # - see http://www.ietf.org/rfc/rfc2246.txt
   # - http://wp.netscape.com/eng/ssl3/3-SPEC.HTM