Index: openacs-4/packages/accounts-finance/tcl/pretti-example-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/accounts-finance/tcl/pretti-example-procs.tcl,v
diff -u -r1.1 -r1.2
--- openacs-4/packages/accounts-finance/tcl/pretti-example-procs.tcl	14 Nov 2014 18:20:17 -0000	1.1
+++ openacs-4/packages/accounts-finance/tcl/pretti-example-procs.tcl	3 Apr 2018 21:30:47 -0000	1.2
@@ -540,7 +540,7 @@
             # p2 Task Network
             #      activity_ref           reference for an activity, a unique task id, using "activity" to differentiate between table_id's tid 
             #                             An activity reference is essential a function as in f() with no attributes,
-            #                             However, there is room to grow this by extending a function to include explicitly set paramemters
+            #                             However, there is room to grow this by extending a function to include explicitly set parameters
             #                             within the function, similar to how app-model handles functions aka vectors
             #                             The multiple of an activity is respresented by a whole number followed by an "*" 
             #                             with no spaces between (when spaces are used as an activity delimiter), or
Index: openacs-4/packages/accounts-finance/tcl/pretti-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/accounts-finance/tcl/pretti-procs.tcl,v
diff -u -r1.4 -r1.5
--- openacs-4/packages/accounts-finance/tcl/pretti-procs.tcl	29 Mar 2018 17:28:50 -0000	1.4
+++ openacs-4/packages/accounts-finance/tcl/pretti-procs.tcl	3 Apr 2018 21:30:47 -0000	1.5
@@ -1294,7 +1294,7 @@
             # p2 Task Network
             #      activity_ref           reference for an activity, a unique task id, using "activity" to differentiate between table_id's tid 
             #                             An activity reference is essential a function as in f() with no attributes,
-            #                             However, there is room to grow this by extending a function to include explicitly set paramemters
+            #                             However, there is room to grow this by extending a function to include explicitly set parameters
             #                             within the function, similar to how app-model handles functions aka vectors
             #                             The multiple of an activity is respresented by a whole number followed by an "*" 
             #                             with no spaces between (when spaces are used as an activity delimiter), or
Index: openacs-4/packages/acs-authentication/www/doc/acs-authentication.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-authentication/www/doc/acs-authentication.html,v
diff -u -r1.1 -r1.2
--- openacs-4/packages/acs-authentication/www/doc/acs-authentication.html	29 Dec 2017 10:09:01 -0000	1.1
+++ openacs-4/packages/acs-authentication/www/doc/acs-authentication.html	3 Apr 2018 21:30:47 -0000	1.2
@@ -67,7 +67,7 @@
 </ul>
 <p>Then you can enter your specific values for your server, is likely that the recomemded ones will work fine. </p>
 <p>Hint: nssha (SSHA) doesn't work well with LDAP use ns_passwd or another encryption method (MD5...)</p>
-<p>You can make your users to loging using the email or username, by changing the paramenter at the kernel named: UseEmailForLoginP under Security section. If username is used for loging, it will ask  for the authority to use, since username is unique by authority but not for the entire openacs installation (can exists several identic usernames but each one belongs to a different authority). </p>
+<p>You can make your users to loging using the email or username, by changing the parameter at the kernel named: UseEmailForLoginP under Security section. If username is used for loging, it will ask  for the authority to use, since username is unique by authority but not for the entire openacs installation (can exists several identic usernames but each one belongs to a different authority). </p>
 <p class="style2">&nbsp;</p>
 <p class="style2"><strong>acs-authentication defines a set of SC to interact with the different authentication implementations (LDAP or PAM):</strong></p>
 <ol>
Index: openacs-4/packages/acs-mail-lite/tcl/test/email-inbound-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-mail-lite/tcl/test/email-inbound-procs.tcl,v
diff -u -r1.2 -r1.3
--- openacs-4/packages/acs-mail-lite/tcl/test/email-inbound-procs.tcl	19 Feb 2018 18:32:06 -0000	1.2
+++ openacs-4/packages/acs-mail-lite/tcl/test/email-inbound-procs.tcl	3 Apr 2018 21:30:47 -0000	1.3
@@ -124,7 +124,7 @@
            set p_type_i 0
             foreach p_type $priority_types {
 
-                # reset prameters
+                # reset parameters
                 foreach {n v} $a_list {
                     #set $n $v
                     set p "-"
Index: openacs-4/packages/authorize-gateway/tcl/authorize-gateway-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/authorize-gateway/tcl/authorize-gateway-procs.tcl,v
diff -u -r1.10 -r1.11
--- openacs-4/packages/authorize-gateway/tcl/authorize-gateway-procs.tcl	29 Mar 2018 17:28:50 -0000	1.10
+++ openacs-4/packages/authorize-gateway/tcl/authorize-gateway-procs.tcl	3 Apr 2018 21:30:47 -0000	1.11
@@ -59,7 +59,7 @@
     append full_url "&x_Test_Request=[ns_urlencode $test_request]"
 
     # Set the transaction type to AUTHORIZE ONLY and set the invoice
-    # number to the transaction id paramater. This is a bit confusing
+    # number to the transaction id parameter. This is a bit confusing
     # as the transaction id passed to this procedure should not be
     # mistaken for the transaction id that Authorize.net will generate
     # and return. The Authorize.net transaction id will be store in
@@ -632,7 +632,7 @@
     append full_url "&x_Test_Request=[ns_urlencode $test_request]"
 
     # Set the transaction type to AUTH_CAPTURE and set the invoice
-    # number to the transaction id paramater. This is a bit confusing
+    # number to the transaction id parameter. This is a bit confusing
     # as the transaction id passed to this procedure should not be
     # mistaken for the transaction id that Authorize.net will generate
     # and return. The Authorize.net transaction id will be store in
Index: openacs-4/packages/boomerang/tcl/boomerang-init.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/boomerang/tcl/boomerang-init.tcl,v
diff -u -r1.1 -r1.2
--- openacs-4/packages/boomerang/tcl/boomerang-init.tcl	3 Jan 2018 19:20:58 -0000	1.1
+++ openacs-4/packages/boomerang/tcl/boomerang-init.tcl	3 Apr 2018 21:30:47 -0000	1.2
@@ -1,7 +1,7 @@
 
 
 #
-# We should get the URL from the parmeter and register this for every
+# We should get the URL from the parameter and register this for every
 # toplevel subsite, on which boomerang is enabled
 #
 foreach url {/} {