Index: openacs-4/packages/acs-ldap-authentication/sql/oracle/LdapLogin.sqlj
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-ldap-authentication/sql/oracle/LdapLogin.sqlj,v
diff -u -N -r1.1 -r1.2
--- openacs-4/packages/acs-ldap-authentication/sql/oracle/LdapLogin.sqlj	20 Apr 2001 20:51:09 -0000	1.1
+++ openacs-4/packages/acs-ldap-authentication/sql/oracle/LdapLogin.sqlj	31 Jan 2018 20:54:06 -0000	1.2
@@ -7,7 +7,7 @@
   private static final String ERROR_PREFIX = "__LDAP_ERROR";
 
   private static String pretty_error (Exception e) {
-    // Return a nicely formatted error message from the given execption.
+    // Return a nicely formatted error message from the given exception.
     if (e instanceof IllegalArgumentException) {
       return ERROR_PREFIX + ": Illegal Argument {"+e.getMessage()+"} {"+e.toString()+"}";
     } 
Index: openacs-4/packages/acs-ldap-authentication/tcl/ldap-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-ldap-authentication/tcl/ldap-procs.tcl,v
diff -u -N -r1.2 -r1.3
--- openacs-4/packages/acs-ldap-authentication/tcl/ldap-procs.tcl	1 Nov 2003 08:45:37 -0000	1.2
+++ openacs-4/packages/acs-ldap-authentication/tcl/ldap-procs.tcl	31 Jan 2018 20:54:06 -0000	1.3
@@ -334,7 +334,7 @@
 }
         
 ad_proc -private ldap_set_environment {} {
-    A convenience function for setting up common local variables from LDAP Package paramter
+    A convenience function for setting up common local variables from LDAP Package parameter
     values.
 } {
     set url             [default_parameter_value LdapUrl acs-ldap-authentication]
Index: openacs-4/packages/acs-ldap-authentication/www/doc/design.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-ldap-authentication/www/doc/design.html,v
diff -u -N -r1.3 -r1.4
--- openacs-4/packages/acs-ldap-authentication/www/doc/design.html	20 Apr 2005 11:48:56 -0000	1.3
+++ openacs-4/packages/acs-ldap-authentication/www/doc/design.html	31 Jan 2018 20:54:06 -0000	1.4
@@ -37,8 +37,8 @@
 <p>
 
 ArsDigita, as the administrator of these two sites can use the LDAP
-authentication package to create "cannonical accounts" that are shared between
-the sites.  The cannonical accounts are the authoritative source for a user's
+authentication package to create "canonical accounts" that are shared between
+the sites.  The canonical accounts are the authoritative source for a user's
 primary information such as e-mail address, password, first names, and last
 name.  Each ACS installation (www.arsdigita.com and acs.arsdigita.com in this
 example) still have their own users table, but they use the LDAP authentication
@@ -230,7 +230,7 @@
 The user interface currently provides a list of all granted
 permissions on the object.  If the user wishes to revoke privileges,
 she may select a set of grants, choose revoke, confirm their deletion,
-and be returned to the same page after those priviliges have been
+and be returned to the same page after those privileges have been
 revoked.
 </p>
 
Index: openacs-4/packages/acs-ldap-authentication/www/doc/ldap-authentication.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-ldap-authentication/www/doc/ldap-authentication.html,v
diff -u -N -r1.1 -r1.2
--- openacs-4/packages/acs-ldap-authentication/www/doc/ldap-authentication.html	13 Sep 2002 15:16:27 -0000	1.1
+++ openacs-4/packages/acs-ldap-authentication/www/doc/ldap-authentication.html	31 Jan 2018 20:54:06 -0000	1.2
@@ -182,7 +182,7 @@
 parameter file.
 
 
-Returns <code>ok</code> if the bind was successfull. If not, it
+Returns <code>ok</code> if the bind was successful. If not, it
 returns <code>Error: <i>explanation</i></code>
 
 <p>
@@ -222,7 +222,7 @@
 <b>ServerURL=<i>ldap://ldap.yourdomain.com</i></b>
 ; The base DN under which all the users of this website resides
 <b>BaseDN=<i>ou=people,dc=yourdomain,dc=com</i></b>
-; Preferred security mechanisms seperated by space, e.g.
+; Preferred security mechanisms separated by space, e.g.
 ; simple, CRAM-MD5, DIGEST-MD5
 <b>SecurityMechanism=<i>simple</i></b>
 </pre></blockquote>
@@ -250,8 +250,8 @@
 
 <h4>Patched /www/register Pages</h4>
 
-The login process has been modified to accomodate LDAP
-authenticaion. The following pages are affected: user-login,
+The login process has been modified to accommodate LDAP
+authentication. The following pages are affected: user-login,
 user-login-2, deleted-user, restore-user.
 
 
Index: openacs-4/packages/acs-service-contract/tcl/contract-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-service-contract/tcl/contract-procs.tcl,v
diff -u -N -r1.7 -r1.8
--- openacs-4/packages/acs-service-contract/tcl/contract-procs.tcl	7 Aug 2017 23:47:57 -0000	1.7
+++ openacs-4/packages/acs-service-contract/tcl/contract-procs.tcl	31 Jan 2018 20:57:02 -0000	1.8
@@ -83,7 +83,7 @@
 
     <ul>
       <li>name: The name of the service contract. 
-      <li>description: A human-readable descirption.
+      <li>description: A human-readable descriptions.
       <li>operations: An array-list of operations in this service contract.
     </ul>
   
Index: openacs-4/packages/acs-service-contract/www/doc/index.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-service-contract/www/doc/index.adp,v
diff -u -N -r1.3 -r1.4
--- openacs-4/packages/acs-service-contract/www/doc/index.adp	7 Aug 2017 23:47:57 -0000	1.3
+++ openacs-4/packages/acs-service-contract/www/doc/index.adp	31 Jan 2018 20:57:02 -0000	1.4
@@ -29,7 +29,7 @@
 <p>Interface Discovery is available programmatically as well as via
 documentation through ad_proc.</p>
 <p>The Service Contract interface specification was inspired by
-WDSL, the interface specfication for web services.</p>
+WDSL, the interface specification for web services.</p>
 <h2>Hitchiker&#39;s Guide to Service Contract Definitions</h2>
 <ul>
 <li>contract - analogous to interface, contracts serve as logical
@@ -68,7 +68,7 @@
 <h3>Creating Message Types</h3>
 <ul><li>(sql):: acs_sc_msg_type__new (name, spec):
 <p>defines a type based on spec. Spec should be a string (possibly
-emtpy) that defines the names and types that compose this type.
+empty) that defines the names and types that compose this type.
 example <code>ObjectDisplay.Name.InputType</code> as name
 <code>object_id:integer</code> as spec.</p>
 </li></ul>
Index: openacs-4/packages/acs-service-contract/www/doc/index.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-service-contract/www/doc/index.html,v
diff -u -N -r1.4 -r1.5
--- openacs-4/packages/acs-service-contract/www/doc/index.html	7 Aug 2017 23:47:57 -0000	1.4
+++ openacs-4/packages/acs-service-contract/www/doc/index.html	31 Jan 2018 20:57:02 -0000	1.5
@@ -22,7 +22,7 @@
     calls on an interface implementation. The dispatch means
     is only available through tcl. </p><p>    Interface Discovery is available programmatically as well as via
     documentation through ad_proc.</p><p>    The Service Contract interface specification was inspired by
-    WDSL, the interface specfication for web services.</p><h2>  Hitchiker's Guide to Service Contract Definitions</h2>
+    WDSL, the interface specification for web services.</p><h2>  Hitchiker's Guide to Service Contract Definitions</h2>
 <ul>
 <li>contract - analogous to interface, contracts serve as logical 
                   containers for operations.</li>
@@ -57,7 +57,7 @@
 <ul>
 <li>(sql)::
                  acs_sc_msg_type__new (name, spec):<p>           defines a type based on spec. Spec should
-           be a string (possibly emtpy) that defines the
+           be a string (possibly empty) that defines the
            names and types that compose this type.
            example <code>ObjectDisplay.Name.InputType</code> as name
            <code>object_id:integer</code> as spec.</p></li>
Index: openacs-4/packages/acs-service-contract/www/doc/index.stx
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-service-contract/www/doc/index.stx,v
diff -u -N -r1.3 -r1.4
--- openacs-4/packages/acs-service-contract/www/doc/index.stx	7 Aug 2017 23:47:57 -0000	1.3
+++ openacs-4/packages/acs-service-contract/www/doc/index.stx	31 Jan 2018 20:57:02 -0000	1.4
@@ -34,7 +34,7 @@
     documentation through ad_proc.
 
     The Service Contract interface specification was inspired by
-    WDSL, the interface specfication for web services.
+    WDSL, the interface specification for web services.
 
   Hitchiker's Guide to Service Contract Definitions
 
@@ -97,7 +97,7 @@
 		 acs_sc_msg_type__new (name, spec):
 
 	   defines a type based on spec. Spec should
-	   be a string (possibly emtpy) that defines the
+	   be a string (possibly empty) that defines the
 	   names and types that compose this type.
 	   example 'ObjectDisplay.Name.InputType' as name
            'object_id:integer' as spec.
Index: openacs-4/packages/acs-service-contract/www/doc/index.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-service-contract/www/doc/index.xml,v
diff -u -N -r1.3 -r1.4
--- openacs-4/packages/acs-service-contract/www/doc/index.xml	7 Aug 2017 23:47:57 -0000	1.3
+++ openacs-4/packages/acs-service-contract/www/doc/index.xml	31 Jan 2018 20:57:02 -0000	1.4
@@ -61,7 +61,7 @@
 <para>
 
 The Service Contract interface specification was inspired by
-    WDSL, the interface specfication for web services.</para>
+    WDSL, the interface specification for web services.</para>
 
 
 </section>
@@ -165,7 +165,7 @@
                  acs_sc_msg_type__new (name, spec):<para>
 
 defines a type based on spec. Spec should
-           be a string (possibly emtpy) that defines the
+           be a string (possibly empty) that defines the
            names and types that compose this type.
            example <literal>ObjectDisplay.Name.InputType</literal>as name
            <literal>object_id:integer</literal>as spec.</para>
Index: openacs-4/packages/xolp/tcl/xolp-activity-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xolp/tcl/xolp-activity-procs.tcl,v
diff -u -N -r1.1 -r1.2
--- openacs-4/packages/xolp/tcl/xolp-activity-procs.tcl	26 Jan 2017 10:00:51 -0000	1.1
+++ openacs-4/packages/xolp/tcl/xolp-activity-procs.tcl	31 Jan 2018 21:01:11 -0000	1.2
@@ -325,7 +325,7 @@
        ::xo::db::Attribute create title
        ::xo::db::Attribute create description
     } -ad_doc {
-      An activity verb may be refered to as "type of usage" of an activity object.
+      An activity verb may be referred to as "type of usage" of an activity object.
       For example, a client application may want to differentiate between
       "practicing" and "competing in" an exam.
     }
Index: openacs-4/packages/xolp/www/doc/design-decisions.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xolp/www/doc/design-decisions.adp,v
diff -u -N -r1.1 -r1.2
--- openacs-4/packages/xolp/www/doc/design-decisions.adp	26 Jan 2017 10:00:51 -0000	1.1
+++ openacs-4/packages/xolp/www/doc/design-decisions.adp	31 Jan 2018 21:01:11 -0000	1.2
@@ -10,7 +10,7 @@
     <dl>
       <dt>(Durable) Storage of Indicators and Activities</dt>
       <dd>
-        The persistance of indicators and activities.
+        The persistence of indicators and activities.
         Although it is possible to update and delete all data via the API,
         indicators are typically simply imported/pushed into the
         data base without the need for further modification.
@@ -72,7 +72,7 @@
         There are several entities in <code>xolp</code> for which we expect only a few instances.
         For example, we will only need a handful of ActivityVerbs and EvaluationSchemas, and in practice
         probably even not too many EvalutionScales (if the client application cares about deduplication).
-        By refering to these resources via human-readable identifiers, we are able to write nice readable
+        By referring to these resources via human-readable identifiers, we are able to write nice readable
         code such as
         <code>::xolp::EvaluationSchema require -iri "https://dotlrn.org/xolp/evaluation-schemas/at-five-to-one"</code>
         or
@@ -121,7 +121,7 @@
     <a href="http://www.kimballgroup.com/2008/09/slowly-changing-dimensions-part-2/">
     Slowly Changing Dimension (of Type 2)</a>.
   </dd>
-  <dt>Activity Hierachy</dt>
+  <dt>Activity Hierarchy</dt>
   <dd>
     It is natural to think of activities at different granularity levels, or that
     an activity can comprise several sub-activities.
Index: openacs-4/packages/xolp/www/doc/terminology.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xolp/www/doc/terminology.adp,v
diff -u -N -r1.1 -r1.2
--- openacs-4/packages/xolp/www/doc/terminology.adp	26 Jan 2017 10:00:51 -0000	1.1
+++ openacs-4/packages/xolp/www/doc/terminology.adp	31 Jan 2018 21:01:11 -0000	1.2
@@ -12,7 +12,7 @@
     Within the xolp system, these processes (activities) are considered to be
     referred to/identified by IRIs.
     <br>
-    Note: The detailled semantics of how to represent activities (processes)
+    Note: The detailed semantics of how to represent activities (processes)
     and/or their instances is up to the context and domain of the client of
     the xolp package.
     In other words, whether or not the fact that "three people answered a personalized
Index: openacs-4/packages/xml-rpc/tcl/xml-rpc-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xml-rpc/tcl/xml-rpc-procs.tcl,v
diff -u -N -r1.11 -r1.12
--- openacs-4/packages/xml-rpc/tcl/xml-rpc-procs.tcl	17 Apr 2017 17:10:49 -0000	1.11
+++ openacs-4/packages/xml-rpc/tcl/xml-rpc-procs.tcl	31 Jan 2018 21:03:19 -0000	1.12
@@ -56,7 +56,7 @@
     if {[ns_info name] eq "NaviServer"} {
         #
         # NaviServer provides a generic means to access the content,
-        # indepenent from the spooling configuration
+        # independent from the spooling configuration
         #
         set text [ns_getcontent -as_file false -binary false]
     } else {
@@ -543,7 +543,7 @@
     }
     set req_hdrs [ns_set create]
 
-    # headers necesary for a post and the form variables
+    # headers necessary for a post and the form variables
     ns_set put $req_hdrs Accept "*/*"
     ns_set put $req_hdrs User-Agent "[ns_info name]-Tcl/[ns_info version]"
     ns_set put $req_hdrs "Content-type" "text/xml"
@@ -606,7 +606,7 @@
     if { [xml_node_get_name $root] ne "methodResponse" } {
         set root_name [xml_node_get_name $root]
         xml_doc_free $doc
-        return -code error "xmlrpc::parse_response: invalid server reponse - root node is not methodResponse. it's $root_name"
+        return -code error "xmlrpc::parse_response: invalid server response - root node is not methodResponse. it's $root_name"
     }
     
     set node [xml_node_get_first_child $root]
Index: openacs-4/packages/xml-rpc/tcl/test/xml-rpc-test-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xml-rpc/tcl/test/xml-rpc-test-procs.tcl,v
diff -u -N -r1.2 -r1.3
--- openacs-4/packages/xml-rpc/tcl/test/xml-rpc-test-procs.tcl	24 Feb 2005 22:00:50 -0000	1.2
+++ openacs-4/packages/xml-rpc/tcl/test/xml-rpc-test-procs.tcl	31 Jan 2018 21:03:19 -0000	1.3
@@ -121,7 +121,7 @@
         # int test
         set arglist {-int 33} 
         set result [xmlrpc::construct {} $arglist]
-        aa_equals "int contruction" $result "<i4>33</i4>"
+        aa_equals "int construction" $result "<i4>33</i4>"
 
         # array test
         set arglist {-array {
Index: openacs-4/packages/xml-rpc/www/admin/index.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/xml-rpc/www/admin/index.adp,v
diff -u -N -r1.2 -r1.3
--- openacs-4/packages/xml-rpc/www/admin/index.adp	12 Sep 2013 20:48:32 -0000	1.2
+++ openacs-4/packages/xml-rpc/www/admin/index.adp	31 Jan 2018 21:03:19 -0000	1.3
@@ -10,7 +10,7 @@
 <tr>
   <th>Status: </th> 
   <td>
-    <a href="toggle"><if @server_enabled_p@>Enabled</if><else>Disabled</else></a>
+    <a href="toggle"><if @server_enabled_p;literal@ true>Enabled</if><else>Disabled</else></a>
   </td>
 </tr>