Index: openacs-4/packages/acs-admin/www/apm/version-files.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-admin/www/apm/version-files.tcl,v diff -u -r1.19.2.1 -r1.19.2.2 --- openacs-4/packages/acs-admin/www/apm/version-files.tcl 3 Jul 2020 07:43:20 -0000 1.19.2.1 +++ openacs-4/packages/acs-admin/www/apm/version-files.tcl 11 Aug 2020 20:44:38 -0000 1.19.2.2 @@ -84,7 +84,7 @@ set server_rel_path "packages/$package_key/$path" if { [apm_file_watchable_p $server_rel_path] } { if { [nsv_exists apm_reload_watch $server_rel_path] } { - # This procs file is already being watched. + # This "-procs" file is already being watched. append body " being watched " } else { if {![parameter::get -package_id [ad_acs_kernel_id] \ Index: openacs-4/packages/acs-admin/www/users/one.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-admin/www/users/one.tcl,v diff -u -r1.20.2.3 -r1.20.2.4 --- openacs-4/packages/acs-admin/www/users/one.tcl 3 Sep 2019 10:56:57 -0000 1.20.2.3 +++ openacs-4/packages/acs-admin/www/users/one.tcl 11 Aug 2020 20:44:38 -0000 1.20.2.4 @@ -75,7 +75,7 @@ } # cro@ncacasi.org 2002-02-20 -# Boy is this query wacked, but I think I am starting to understand +# Boy, is this query wacked, but I think I am starting to understand # how this groups thing works. # Find out which groups this user belongs to where he was added to the group # directly (e.g. his membership is not by virtue of the group being Index: openacs-4/packages/acs-automated-testing/www/admin/record-test.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-automated-testing/www/admin/record-test.tcl,v diff -u -r1.5.2.2 -r1.5.2.3 --- openacs-4/packages/acs-automated-testing/www/admin/record-test.tcl 14 Aug 2019 07:36:04 -0000 1.5.2.2 +++ openacs-4/packages/acs-automated-testing/www/admin/record-test.tcl 11 Aug 2020 20:44:38 -0000 1.5.2.3 @@ -138,7 +138,7 @@ set file [open $full_path a] } - # To be able to use this cases in other server + # To be able to use these cases on other server instances # we need to replace the URL generated by TwtR # with the URL provided by ad_url, we could do # a string map or use the regexp or regsub like Index: openacs-4/packages/acs-tcl/tcl/http-client-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/acs-tcl/tcl/http-client-procs.tcl,v diff -u -r1.30.2.6 -r1.30.2.7 --- openacs-4/packages/acs-tcl/tcl/http-client-procs.tcl 6 Aug 2020 13:09:53 -0000 1.30.2.6 +++ openacs-4/packages/acs-tcl/tcl/http-client-procs.tcl 11 Aug 2020 20:44:38 -0000 1.30.2.7 @@ -554,7 +554,7 @@ states that method should not change when 301 or 302 are returned, and that GET should be used on a 303 response, but most HTTP clients fail in respecting this and switch to a GET request - independently. This options forces this kinds of redirect to + independently. This option forces this kinds of redirect to conserve their original method. @param max_depth is the maximum number of redirects the proc is @@ -970,7 +970,7 @@ states that method should not change when 301 or 302 are returned, and that GET should be used on a 303 response, but most HTTP clients fail in respecting this and switch to a GET request - independently. This options forces this kinds of redirect to + independently. This option forces this kinds of redirect to conserve their original method. @param max_depth is the maximum number of redirects the proc is @@ -1150,7 +1150,7 @@ states that method should not change when 301 or 302 are returned, and that GET should be used on a 303 response, but most HTTP clients fail in respecting this and switch to a GET request - independently. This options forces this kinds of redirect to + independently. This option forces this kinds of redirect to conserve their original method. Notice that, as from RFC, a 303 redirect won't send again any data to the server, as specification says we can assume variables to have been received. @@ -1395,7 +1395,7 @@ states that method should not change when 301 or 302 are returned, and that GET should be used on a 303 response, but most HTTP clients fail in respecting this and switch to a GET request - independently. This options forces this kinds of redirect to + independently. This option forces this kinds of redirect to conserve their original method. Notice that, as from RFC, a 303 redirect won't send again any data to the server, as specification says we can assume variables to have been received. @@ -1683,7 +1683,7 @@ states that method should not change when 301 or 302 are returned, and that GET should be used on a 303 response, but most HTTP clients fail in respecting this and switch to a GET request - independently. This options forces this kinds of redirect to + independently. This option forces this kinds of redirect to conserve their original method. Be aware that curl allows the POSTing of 303 requests only since version 7.26. Versions prior than this will follow 303 redirects Index: openacs-4/packages/xotcl-core/tcl/01-debug-procs.tcl =================================================================== RCS file: /usr/local/cvsroot/openacs-4/packages/xotcl-core/tcl/01-debug-procs.tcl,v diff -u -r1.93.2.25 -r1.93.2.26 --- openacs-4/packages/xotcl-core/tcl/01-debug-procs.tcl 30 Jul 2020 13:54:32 -0000 1.93.2.25 +++ openacs-4/packages/xotcl-core/tcl/01-debug-procs.tcl 11 Aug 2020 20:44:38 -0000 1.93.2.26 @@ -456,7 +456,7 @@ # In case the server has way to many connection threads defined, # broadcast messages might pile up. In these situations, the idle # callback provides a means to keep these idle connection threads - # uptodate. + # up to date. # ns_ictl trace idle { ns_log notice =====IDLE=====START