Index: openacs-4/packages/acs-templating/acs-templating.info
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/acs-templating.info,v
diff -u -r1.56.2.21 -r1.56.2.22
--- openacs-4/packages/acs-templating/acs-templating.info	27 Feb 2017 07:42:03 -0000	1.56.2.21
+++ openacs-4/packages/acs-templating/acs-templating.info	21 Apr 2017 16:50:29 -0000	1.56.2.22
@@ -16,7 +16,7 @@
         <vendor url="http://openacs.org">OpenACS</vendor>
         <description format="text/html">The templating system provides the tag library and support routines
 that allow developers and graphic designers to work
-independently. Templates specify the layout of the page seperately
+independently. Templates specify the layout of the page separately
 from the contents of the page. Graphic designers work primarily on the
 layout part of the template (the template), while programmers work
 primarily a script that generates the the content part of the template
Index: openacs-4/packages/acs-templating/resources/lists/select-menu.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/resources/lists/select-menu.adp,v
diff -u -r1.5.2.2 -r1.5.2.3
--- openacs-4/packages/acs-templating/resources/lists/select-menu.adp	18 Jan 2017 08:20:57 -0000	1.5.2.2
+++ openacs-4/packages/acs-templating/resources/lists/select-menu.adp	21 Apr 2017 16:50:29 -0000	1.5.2.3
@@ -22,7 +22,7 @@
 #	   where_clause { filter_where_cluse }
 #     }
 #  }
-#  - The recieving page variable must be of the type :multiple
+#  - The receiving page variable must be of the type :multiple
 #    since the filter sends the values in the following way:
 #    filter_name=filter_value&amp;filter_name=filter_value&....&amp;extra_variables=extra_values
 %>
@@ -58,7 +58,7 @@
       }	
 
   if (extra_vars.length > 0 ) {
-      // There are extra variables, so we send then using along wiht the filter value
+      // There are extra variables, so we send then using along with the filter value
       return (url+'?'+filter_name+'='+r.join('&'+filter_name+'=')+'&'+extra_vars);
   } 
   else 
Index: openacs-4/packages/acs-templating/tcl/doc-tcl-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/doc-tcl-procs.tcl,v
diff -u -r1.11.2.3 -r1.11.2.4
--- openacs-4/packages/acs-templating/tcl/doc-tcl-procs.tcl	3 Oct 2016 18:52:07 -0000	1.11.2.3
+++ openacs-4/packages/acs-templating/tcl/doc-tcl-procs.tcl	21 Apr 2017 16:50:29 -0000	1.11.2.4
@@ -460,7 +460,7 @@
     # as would be expected if the namespace were being described 
     # for the first time; otherwise
     # it is set to 0;  the problem i'm trying to resolve here is multiple uses 
-    # of the @namespace directive and determining which occurance of the 
+    # of the @namespace directive and determining which occurrence of the 
     # directive is followed by comments
     # by comments we want to parse into our static files
 
@@ -489,7 +489,7 @@
     if { $has_comments } {
 	
 	# this check determines whether or not we want the comments
-	# following this occurrance of the @namespace directive for 
+	# following this occurrence of the @namespace directive for 
 	# this namespace to be included in our static files
 
         set namespace_info [list name "$namespace_name" overview "$namespace_description" author "$namespace_author" see "$namespace_see"]
Index: openacs-4/packages/acs-templating/tcl/element-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/element-procs.tcl,v
diff -u -r1.33.2.3 -r1.33.2.4
--- openacs-4/packages/acs-templating/tcl/element-procs.tcl	4 Oct 2016 07:17:27 -0000	1.33.2.3
+++ openacs-4/packages/acs-templating/tcl/element-procs.tcl	21 Apr 2017 16:50:29 -0000	1.33.2.4
@@ -388,7 +388,7 @@
 
     @param form_id     The identifier of the form containing the element.
     @param element_id  The unique identifier of the element.
-    @param property    The property to be retreived
+    @param property    The property to be retrieved
 
     @return The value of the property, or "" if the property does not exist
 
Index: openacs-4/packages/acs-templating/tcl/head-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/head-procs.tcl,v
diff -u -r1.20.2.17 -r1.20.2.18
--- openacs-4/packages/acs-templating/tcl/head-procs.tcl	7 Dec 2016 11:11:26 -0000	1.20.2.17
+++ openacs-4/packages/acs-templating/tcl/head-procs.tcl	21 Apr 2017 16:50:29 -0000	1.20.2.18
@@ -89,7 +89,7 @@
     users client.  A script library in an external file may only be included
     once; subsequent calls to add_script will replace the existing entry.
     Anonymous script blocks will be added without checking for duplicates; the
-    caller must ensure that anonymous script blocks are not inadvertantly added
+    caller must ensure that anonymous script blocks are not inadvertently added
     multiple times.  You <strong>must</strong> supply either src or script.
 
     @param async   whether execution of the script should be executed asynchronously
@@ -128,7 +128,7 @@
 
         #
         # For the time being, not all browsers support
-        # nonces. According to the spects the added 'unsafe-inline',
+        # nonces. According to the specs the added 'unsafe-inline',
         # is ignored on browsers supporting nonces.
         #
         # We could restrict setting of unsafe-inline to certain
@@ -442,7 +442,7 @@
     if {$script ne ""} {
         #
         # For the time being, not all browsers support
-        # nonces. According to the spects the added 'unsafe-inline',
+        # nonces. According to the specs the added 'unsafe-inline',
         # is ignored on browsers supporting nonces.
         #
         # We could restrict setting of unsafe-inline to certain
Index: openacs-4/packages/acs-templating/tcl/list-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/list-procs.tcl,v
diff -u -r1.60.2.15 -r1.60.2.16
--- openacs-4/packages/acs-templating/tcl/list-procs.tcl	8 Nov 2016 10:35:41 -0000	1.60.2.15
+++ openacs-4/packages/acs-templating/tcl/list-procs.tcl	21 Apr 2017 16:50:29 -0000	1.60.2.16
@@ -127,7 +127,7 @@
     This switch is required to have bulk actions.
 
     @param  pass_properties
-    A list of variables in the caller's namespace, which should be avilable to the display_template
+    A list of variables in the caller's namespace, which should be available to the display_template
     of elements.
 
     @param  actions        A list of action buttons to display at the top of
@@ -146,7 +146,7 @@
     @param  bulk_action_method should a bulk action be a "get" or "post"
 
     @param  bulk_action_export_vars
-    A list of additional variables to pass to the receving page, along with the other variables for
+    A list of additional variables to pass to the receiving page, along with the other variables for
     the selected keys. This is typically useful if the rows in this list are all hanging off of
     one row in a parent table. For example, if this list contains the order lines of one particular
     order, and the primary key of the order lines table is 'order_id, item_id', the key would be
@@ -612,7 +612,7 @@
         # We need this uplevel so that the bind variables in the query
         # will get bound at the caller's level
         # we pass in a dummy query name because the query text was
-        # already retreived previously with db_map so this call
+        # already retrieved previously with db_map so this call
         # always passes the full query text and not the query name
         # this was failing if the template::list call contained a
         # page_query with an empty page_query_name
@@ -3226,7 +3226,7 @@
             lappend filter_names_options [list $option_label $option_name]
         }
     }
-    # build an ad_form form based on the choosen filters
+    # build an ad_form form based on the chosen filters
     set filters_form_name list-filters-$name
     set add_filter_form_name list-filter-add-$name
     ad_form -name $add_filter_form_name -form {
Index: openacs-4/packages/acs-templating/tcl/paginator-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/paginator-procs.tcl,v
diff -u -r1.22.2.6 -r1.22.2.7
--- openacs-4/packages/acs-templating/tcl/paginator-procs.tcl	3 Oct 2016 18:52:07 -0000	1.22.2.6
+++ openacs-4/packages/acs-templating/tcl/paginator-procs.tcl	21 Apr 2017 16:50:29 -0000	1.22.2.7
@@ -157,7 +157,7 @@
 	  }
 	  set return_url [lindex $opts(printing_prefs) 5]
 	  if { $return_url ne "" } {
-	      # Not sure, what the intented semantics of this command was...
+	      # Not sure, what the intended semantics of this command was...
 	      #if { [llength $opts(row_ids)]==0 } {
 	      #	  nsv_set __template_cache_timeout $cache_key $opts(timeout)
 	      #}
@@ -645,7 +645,7 @@
     </tr>
     <tr>
       <td>previous_page:</td>
-                 <td>preceeding page or empty string if at beginning</td>
+                 <td>preceding page or empty string if at beginning</td>
     </tr>
     <tr>
       <td>next_group:</td>
Index: openacs-4/packages/acs-templating/tcl/parse-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/parse-procs.tcl,v
diff -u -r1.55.2.5 -r1.55.2.6
--- openacs-4/packages/acs-templating/tcl/parse-procs.tcl	27 Nov 2016 12:19:35 -0000	1.55.2.5
+++ openacs-4/packages/acs-templating/tcl/parse-procs.tcl	21 Apr 2017 16:50:29 -0000	1.55.2.6
@@ -35,7 +35,7 @@
     </pre>
 
     The [list &book "bookdata" ...] tells adp_include to pass the book array by reference to the adp include, where it is
-    refered to via @book.field@.
+    referred to via @book.field@.
 
     @param uplevel how far up the stack should the adp_level be set to
     (default is the calling procedures level)
@@ -576,7 +576,7 @@
 
 ad_proc -public template::adp_array_variable_regexp {} {
     The regexp pattern used to find adp array variables in 
-    a piece of text (i.e. @array_name.variable_name@). Captures the character preceeding
+    a piece of text (i.e. @array_name.variable_name@). Captures the character preceding
     the first @ in \1, the array_name in \2, and variable_name in \3
     
     @author Peter Marklund (peter@collaboraid.biz)
@@ -615,7 +615,7 @@
 ad_proc -public template::adp_variable_regexp {} {
     The regexp pattern used to find adp variables in
     a piece of text, i.e. occurenceis of @variable_name@. 
-    Captures the character preceeding the first @ in \1 and
+    Captures the character preceding the first @ in \1 and
     the variable_name in \2.
 
     @author Peter Marklund (peter@collaboraid.biz)
Index: openacs-4/packages/acs-templating/tcl/query-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/query-procs.tcl,v
diff -u -r1.34.2.4 -r1.34.2.5
--- openacs-4/packages/acs-templating/tcl/query-procs.tcl	3 Oct 2016 18:52:07 -0000	1.34.2.4
+++ openacs-4/packages/acs-templating/tcl/query-procs.tcl	21 Apr 2017 16:50:29 -0000	1.34.2.5
@@ -29,8 +29,8 @@
 
 
 ad_proc -public template::query { statement_name result_name type sql args } {
-    Public interface to template query api.  This routine parses the arguements and
-    dispatches to the query command specified by the type arguement.
+    Public interface to template query api.  This routine parses the arguments and
+    dispatches to the query command specified by the type argument.
 
     @option maxrows    Limits the query results of a multirow query
                        to a fixed number of rows.
@@ -422,7 +422,7 @@
 
     @param type Type of query
 
-    @return 1 if result was successfully retrieved, 0 if failed
+    @return 1 if result was successfuly retrieved, 0 if failed
 } {
 
   upvar opts opts
@@ -610,7 +610,7 @@
     multirow is really template::multirow or possibly 
     template::query::multirow depending on context.
     the "template::" or "template::query::"
-    may be ommitted depending on what the namespace 
+    may be omitted depending on what the namespace 
     is.  .tcl pages are evaluated in the template:: 
     namespace.
 
Index: openacs-4/packages/acs-templating/tcl/spellcheck-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/spellcheck-procs.tcl,v
diff -u -r1.22.2.4 -r1.22.2.5
--- openacs-4/packages/acs-templating/tcl/spellcheck-procs.tcl	27 Mar 2017 10:47:03 -0000	1.22.2.4
+++ openacs-4/packages/acs-templating/tcl/spellcheck-procs.tcl	21 Apr 2017 16:50:29 -0000	1.22.2.5
@@ -49,7 +49,7 @@
     -element_ref:required
     -values:required
 } {
-    Tranform submitted and previously validated input into a spellcheck datastructure.
+    Transform submitted and previously validated input into a spellcheck datastructure.
 
     @param element_ref Reference variable to the form element.
     @param values The set of values for that element.
Index: openacs-4/packages/acs-templating/tcl/table-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/table-procs.tcl,v
diff -u -r1.9.2.2 -r1.9.2.3
--- openacs-4/packages/acs-templating/tcl/table-procs.tcl	3 Oct 2016 18:52:07 -0000	1.9.2.2
+++ openacs-4/packages/acs-templating/tcl/table-procs.tcl	21 Apr 2017 16:50:30 -0000	1.9.2.3
@@ -24,12 +24,12 @@
 #       presentation is the html code that will be shown in the table cell
 #         (defaults to "@row.value@", see below)
 #     The column definition will be extracted from the query results
-#     if it is ommitted. 
+#     if it is omitted. 
 #
 # 2). The SQL query that will be executed to get the rows. The orderby
 #      clause will be appended to the query (-query, required).
 #
-# 3). The template to render the table (-style, optional). If ommitted, 
+# 3). The template to render the table (-style, optional). If omitted, 
 #     the code inside the
 #       <tablewidget> tag will be used
 #
@@ -66,7 +66,7 @@
   set widget(name) $name
    
   template::widget::table::get_params $name 2
-  template::widget::table::prepare $statment_name $name 2
+  template::widget::table::prepare $statement_name $name 2
 }
 
 ad_proc -public template::widget::table::get_params {
@@ -110,7 +110,7 @@
   name
   {level 1}
 } {
-  Compose the query, if neccessary, and define the datasources
+  Compose the query, if necessary, and define the datasources
 } {
   
   upvar $level "tablewidget:${name}" widget
Index: openacs-4/packages/acs-templating/tcl/util-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/util-procs.tcl,v
diff -u -r1.28.2.14 -r1.28.2.15
--- openacs-4/packages/acs-templating/tcl/util-procs.tcl	27 Nov 2016 12:19:35 -0000	1.28.2.14
+++ openacs-4/packages/acs-templating/tcl/util-procs.tcl	21 Apr 2017 16:50:30 -0000	1.28.2.15
@@ -705,7 +705,7 @@
     {section ""} 
     {key ""} 
 } {
-    Retreive a stored parameter, or "" if no such parameter
+    Retrieve a stored parameter, or "" if no such parameter
     If section/key are present, read the parameter from the specified
     section.key in the INI file, and cache them under the given name
 } {
Index: openacs-4/packages/acs-templating/tcl/wizard-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/wizard-procs.tcl,v
diff -u -r1.11.2.3 -r1.11.2.4
--- openacs-4/packages/acs-templating/tcl/wizard-procs.tcl	27 Nov 2016 12:19:35 -0000	1.11.2.3
+++ openacs-4/packages/acs-templating/tcl/wizard-procs.tcl	21 Apr 2017 16:50:30 -0000	1.11.2.4
@@ -660,7 +660,7 @@
 }
 
 ad_proc -public template::wizard::get_action_url {} {
-    Retreive the URL to the action
+    Retrieve the URL to the action
 
     @see template::wizard
 } {
Index: openacs-4/packages/acs-templating/tcl/test/spell-checker-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/tcl/test/spell-checker-procs.tcl,v
diff -u -r1.8.2.1 -r1.8.2.2
--- openacs-4/packages/acs-templating/tcl/test/spell-checker-procs.tcl	10 Sep 2015 08:22:08 -0000	1.8.2.1
+++ openacs-4/packages/acs-templating/tcl/test/spell-checker-procs.tcl	21 Apr 2017 16:50:30 -0000	1.8.2.2
@@ -147,9 +147,9 @@
     #####
 
     set command $base_command
-    lappend command -text "This <i>sentence</i> <b>does</b> contain mispelled worrds. What we have here is <a href=\"\#\">HTML</a>."
+    lappend command -text "This <i>sentence</i> <b>does</b> contain misspelled worrds. What we have here is <a href=\"\#\">HTML</a>."
     lappend command -html
-    set errwords {mispelled worrds}
+    set errwords {misspelled worrds}
     
     aa_log "--- Incorrectly spelled HTML fragment --- $command"
 
Index: openacs-4/packages/acs-templating/www/doc/design.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/design.adp,v
diff -u -r1.2.2.6 -r1.2.2.7
--- openacs-4/packages/acs-templating/www/doc/design.adp	7 Nov 2016 19:23:16 -0000	1.2.2.6
+++ openacs-4/packages/acs-templating/www/doc/design.adp	21 Apr 2017 16:50:30 -0000	1.2.2.7
@@ -100,7 +100,7 @@
 "Styles" by Philip Greenspun. An extended and improved
 version was named "Dynamic Publishing System". It
 wasn&#39;t part of the ACS yet, but client projects like iluvCAMP
-used it successfully. Newcomers were consistently puzzled by the
+used it successfuly. Newcomers were consistently puzzled by the
 <code>.data</code> files, which specified the datasources in an
 apparently unfamiliar XML syntax. (The <code>.form</code> files
 specified elements in an HTML form similarly.) To mitigate this
Index: openacs-4/packages/acs-templating/www/doc/design.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/design.html,v
diff -u -r1.4.2.1 -r1.4.2.2
--- openacs-4/packages/acs-templating/www/doc/design.html	22 Jun 2016 07:48:43 -0000	1.4.2.1
+++ openacs-4/packages/acs-templating/www/doc/design.html	21 Apr 2017 16:50:30 -0000	1.4.2.2
@@ -185,7 +185,7 @@
       distinguish it from the obsolescent templates or "Styles" by
       Philip Greenspun.  An extended and improved version was named
       "Dynamic Publishing System".  It wasn't part of the ACS yet, but 
-      client projects like iluvCAMP used it successfully.  Newcomers
+      client projects like iluvCAMP used it successfuly.  Newcomers
       were consistently puzzled by the <code>.data</code> files, which
       specified the datasources in an apparently unfamiliar XML
       syntax.  (The <code>.form</code> files specified elements in an
Index: openacs-4/packages/acs-templating/www/doc/designer-guide.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/designer-guide.adp,v
diff -u -r1.2.2.5 -r1.2.2.6
--- openacs-4/packages/acs-templating/www/doc/designer-guide.adp	7 Nov 2016 19:23:16 -0000	1.2.2.5
+++ openacs-4/packages/acs-templating/www/doc/designer-guide.adp	21 Apr 2017 16:50:30 -0000	1.2.2.6
@@ -86,7 +86,7 @@
 designer may want to have alternate between white and gray bands in
 a table.</p></li>
 </ol>
-<p>To accomodate these type of scenarios, the template parser sets
+<p>To accommodate these type of scenarios, the template parser sets
 some additional variables that the designer can reference to vary
 the layout from item to item.</p>
 <p>See <a href="tagref/multiple"><kbd>multiple</kbd></a>,
Index: openacs-4/packages/acs-templating/www/doc/designer-guide.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/designer-guide.html,v
diff -u -r1.1.1.1.30.1 -r1.1.1.1.30.2
--- openacs-4/packages/acs-templating/www/doc/designer-guide.html	22 Jun 2016 07:48:43 -0000	1.1.1.1.30.1
+++ openacs-4/packages/acs-templating/www/doc/designer-guide.html	21 Apr 2017 16:50:30 -0000	1.1.1.1.30.2
@@ -127,7 +127,7 @@
       in a table.</p>
 </ol>
 
-<p>To accomodate these type of scenarios, the template parser sets
+<p>To accommodate these type of scenarios, the template parser sets
 some additional variables that the designer can reference to vary
 the layout from item to item.</p>
 
Index: openacs-4/packages/acs-templating/www/doc/noquote.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/noquote.adp,v
diff -u -r1.3.2.5 -r1.3.2.6
--- openacs-4/packages/acs-templating/www/doc/noquote.adp	7 Nov 2016 19:23:16 -0000	1.3.2.5
+++ openacs-4/packages/acs-templating/www/doc/noquote.adp	21 Apr 2017 16:50:30 -0000	1.3.2.6
@@ -181,7 +181,7 @@
 a broken page from time to time, typically by spotting the
 obviously visible HTML markup. Such a page would get fixed it in a
 matter of seconds by appending ;noquote to the name of the
-offending variable.</p><p>We launched successfully within schedule.</p>
+offending variable.</p><p>We launched successfuly within schedule.</p>
 </div><div class="sect2" lang="en">
 <div class="titlepage"><div><h3 class="title">
 <a name="Porting_the_quoting_changes_to_the_ACS" id="Porting_the_quoting_changes_to_the_ACS"></a>Porting the quoting
Index: openacs-4/packages/acs-templating/www/doc/noquote.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/noquote.html,v
diff -u -r1.1.24.2 -r1.1.24.3
--- openacs-4/packages/acs-templating/www/doc/noquote.html	7 Nov 2016 19:16:25 -0000	1.1.24.2
+++ openacs-4/packages/acs-templating/www/doc/noquote.html	21 Apr 2017 16:50:30 -0000	1.1.24.3
@@ -134,7 +134,7 @@
 templating still supports all the ADP features, including embedding
 Tcl code in the template. Thus instead of referring to the multirow
 variable with the @forums.name@ variable substitutions, we use
-&lt;%=�[ns_quotehtml�@forums.name@]�%&gt;. This works
+&lt;%= [ns_quotehtml @forums.name@] %&gt;. This works
 correctly, but obviously breaks the abstraction barrier between ADP
 and Tcl syntaxes. The practical result of breaking the abstraction is
 that every occurrence of Tcl code in an ADP template will have to be
@@ -198,7 +198,7 @@
 broken page from time to time, typically by spotting the obviously
 visible HTML markup. Such a page would get fixed it in a matter of
 seconds by appending ;noquote to the name of the offending variable.
-</p><p>We launched successfully within schedule.
+</p><p>We launched successfuly within schedule.
 </p></div><div class="sect2" lang="en"><div class="titlepage"><div><h3 class="title"><a name="Porting_the_quoting_changes_to_the_ACS"></a>Porting the quoting changes to the ACS.
 </h3></div></div><p>
 After some discussion, it was decided that these changes will be
Index: openacs-4/packages/acs-templating/www/doc/requirements.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/requirements.adp,v
diff -u -r1.2.2.6 -r1.2.2.7
--- openacs-4/packages/acs-templating/www/doc/requirements.adp	7 Nov 2016 19:23:16 -0000	1.2.2.6
+++ openacs-4/packages/acs-templating/www/doc/requirements.adp	21 Apr 2017 16:50:30 -0000	1.2.2.7
@@ -59,7 +59,7 @@
 the application logic generates data for the presentation to
 display to the user. The template system must provide mechanisms
 that supports both of these tasks and allows the designer and
-programmer to work seperately, but for their work to be combined at
+programmer to work separately, but for their work to be combined at
 runtime into something that the user sees as a single page.</p>
 <p>Thus, pages are naturally split into two parts. The <em>logic
 part</em> executes application logic and generates data, and the
Index: openacs-4/packages/acs-templating/www/doc/requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/requirements.html,v
diff -u -r1.2.2.1 -r1.2.2.2
--- openacs-4/packages/acs-templating/www/doc/requirements.html	22 Jun 2016 07:48:43 -0000	1.2.2.1
+++ openacs-4/packages/acs-templating/www/doc/requirements.html	21 Apr 2017 16:50:30 -0000	1.2.2.2
@@ -86,7 +86,7 @@
       generates data for the presentation to display to the user. The
       template system must provide mechanisms that supports both of
       these tasks and allows the designer and programmer to work
-      seperately, but for their work to be combined at runtime into
+      separately, but for their work to be combined at runtime into
       something that the user sees as a single page.
     </p>
     <p>
Index: openacs-4/packages/acs-templating/www/doc/TclDocs/item.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/TclDocs/item.adp,v
diff -u -r1.2.2.5 -r1.2.2.6
--- openacs-4/packages/acs-templating/www/doc/TclDocs/item.adp	7 Nov 2016 19:23:16 -0000	1.2.2.5
+++ openacs-4/packages/acs-templating/www/doc/TclDocs/item.adp	21 Apr 2017 16:50:30 -0000	1.2.2.6
@@ -76,7 +76,7 @@
 </table>
 <table width="100%">
 <tr><td width="100%" bgcolor="#CCCCFF"><a name="item::get_content_type" id="item::get_content_type"><font size="+1" weight="bold">item::get_content_type</font></a></td></tr><tr><td>
-<blockquote>Retrieves the content type of tyhe item. If the item
+<blockquote>Retrieves the content type of the item. If the item
 does not exist, returns an empty string.</blockquote><dl>
 <dd>
 <strong>Parameters:</strong><table><tr>
Index: openacs-4/packages/acs-templating/www/doc/TclDocs/item.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/TclDocs/item.html,v
diff -u -r1.2.2.1 -r1.2.2.2
--- openacs-4/packages/acs-templating/www/doc/TclDocs/item.html	22 Jun 2016 07:48:44 -0000	1.2.2.1
+++ openacs-4/packages/acs-templating/www/doc/TclDocs/item.html	21 Apr 2017 16:50:30 -0000	1.2.2.2
@@ -187,7 +187,7 @@
 </tr>
 <tr><td>
 <blockquote>
-Retrieves the content type of tyhe item. If the item does not exist, returns an empty string.
+Retrieves the content type of the item. If the item does not exist, returns an empty string.
 </blockquote>
 <dl>
 
Index: openacs-4/packages/acs-templating/www/doc/TclDocs/publish.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/TclDocs/publish.adp,v
diff -u -r1.2.2.5 -r1.2.2.6
--- openacs-4/packages/acs-templating/www/doc/TclDocs/publish.adp	7 Nov 2016 19:23:16 -0000	1.2.2.5
+++ openacs-4/packages/acs-templating/www/doc/TclDocs/publish.adp	21 Apr 2017 16:50:30 -0000	1.2.2.6
@@ -123,19 +123,19 @@
 <code>revision_id_ref</code><font color="red">*</font>
 </td><td align="left">
 <em>required</em> The name of the variable in the
-calling frame that will recieve the revision_id whose content blob
+calling frame that will receive the revision_id whose content blob
 was written to the filesystem.</td>
 </tr><tr>
 <td align="right">
 <code>url_ref</code><font color="red">*</font>
 </td><td align="left">The name of the variable in the calling frame that
-will recieve the relative URL of the file in the file system which
+will receive the relative URL of the file in the file system which
 contains the content blob</td>
 </tr><tr>
 <td align="right">
 <code>error_ref</code><font color="red">*</font>
 </td><td align="left">The name of the variable in the calling frame that
-will recieve an error message. If no error has ocurred, this
+will receive an error message. If no error has occurred, this
 variable will be set to the empty string { }</td>
 </tr>
 </table>
@@ -187,7 +187,7 @@
 </table>
 <table width="100%">
 <tr><td width="100%" bgcolor="#CCCCFF"><a name="publish::mkdirs" id="publish::mkdirs"><font size="+1" weight="bold">publish::mkdirs</font></a></td></tr><tr><td>
-<blockquote>Create all the directories neccessary to save the
+<blockquote>Create all the directories necessary to save the
 specified file</blockquote><dl><dd>
 <strong>Parameters:</strong><table><tr>
 <td align="right">
Index: openacs-4/packages/acs-templating/www/doc/TclDocs/publish.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/TclDocs/publish.html,v
diff -u -r1.2.2.1 -r1.2.2.2
--- openacs-4/packages/acs-templating/www/doc/TclDocs/publish.html	22 Jun 2016 07:48:44 -0000	1.2.2.1
+++ openacs-4/packages/acs-templating/www/doc/TclDocs/publish.html	21 Apr 2017 16:50:30 -0000	1.2.2.2
@@ -235,21 +235,21 @@
   <font color=red>*</font></td>
        <td align="left">
     
-  <em>required</em> The name of the variable in the calling frame that will recieve the revision_id whose content blob was written to the filesystem.</td></tr>
+  <em>required</em> The name of the variable in the calling frame that will receive the revision_id whose content blob was written to the filesystem.</td></tr>
   
   <tr>
   <td align="right"><code>url_ref</code>
   <font color=red>*</font></td>
        <td align="left">
     
-  The name of the variable in the calling frame that will recieve the relative URL of the file in the file system which contains the content blob</td></tr>
+  The name of the variable in the calling frame that will receive the relative URL of the file in the file system which contains the content blob</td></tr>
   
   <tr>
   <td align="right"><code>error_ref</code>
   <font color=red>*</font></td>
        <td align="left">
     
-  The name of the variable in the calling frame that will recieve an error message. If no error has ocurred, this variable will be set to the empty string { }</td></tr>
+  The name of the variable in the calling frame that will receive an error message. If no error has occurred, this variable will be set to the empty string { }</td></tr>
   
    </table>
 
@@ -338,7 +338,7 @@
 </tr>
 <tr><td>
 <blockquote>
-Create all the directories neccessary to save the specified file
+Create all the directories necessary to save the specified file
 </blockquote>
 <dl>
 
Index: openacs-4/packages/acs-templating/www/doc/demo/list5/add-edit.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/demo/list5/add-edit.tcl,v
diff -u -r1.3.2.2 -r1.3.2.3
--- openacs-4/packages/acs-templating/www/doc/demo/list5/add-edit.tcl	22 May 2016 19:25:48 -0000	1.3.2.2
+++ openacs-4/packages/acs-templating/www/doc/demo/list5/add-edit.tcl	21 Apr 2017 16:50:30 -0000	1.3.2.3
@@ -117,7 +117,7 @@
 
 } -after_submit {
 
-    # We've successfully processed the submission, send the user back to the index page.
+    # We've successfuly processed the submission, send the user back to the index page.
 
     ad_returnredirect "./"
 
Index: openacs-4/packages/acs-templating/www/doc/demo/list5/delete.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/demo/list5/delete.tcl,v
diff -u -r1.2.2.1 -r1.2.2.2
--- openacs-4/packages/acs-templating/www/doc/demo/list5/delete.tcl	10 Sep 2015 08:22:14 -0000	1.2.2.1
+++ openacs-4/packages/acs-templating/www/doc/demo/list5/delete.tcl	21 Apr 2017 16:50:30 -0000	1.2.2.2
@@ -15,7 +15,7 @@
 # is there are a bunch of template_demo_note_id values coming in 
 # through the url. So, this list is sorta becoming a form too :)
 #
-# so this loop runs thru all passed-in values of template_demo_note_id
+# so this loop runs through all passed-in values of template_demo_note_id
 # and for each, deletes that note.
 
 foreach template_demo_note_id $template_demo_note_id {
Index: openacs-4/packages/acs-templating/www/doc/demo/list6/add-edit.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/demo/list6/add-edit.tcl,v
diff -u -r1.4.2.1 -r1.4.2.2
--- openacs-4/packages/acs-templating/www/doc/demo/list6/add-edit.tcl	10 Sep 2015 08:22:14 -0000	1.4.2.1
+++ openacs-4/packages/acs-templating/www/doc/demo/list6/add-edit.tcl	21 Apr 2017 16:50:30 -0000	1.4.2.2
@@ -106,7 +106,7 @@
 
 } -after_submit {
 
-    # We've successfully processed the submission, send the user back to the index page.
+    # We've successfuly processed the submission, send the user back to the index page.
 
     ad_returnredirect "./"
 
Index: openacs-4/packages/acs-templating/www/doc/demo/list7/add-edit.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/demo/list7/add-edit.tcl,v
diff -u -r1.3.2.3 -r1.3.2.4
--- openacs-4/packages/acs-templating/www/doc/demo/list7/add-edit.tcl	6 Feb 2017 12:46:04 -0000	1.3.2.3
+++ openacs-4/packages/acs-templating/www/doc/demo/list7/add-edit.tcl	21 Apr 2017 16:50:30 -0000	1.3.2.4
@@ -100,7 +100,7 @@
 
 } -after_submit {
 
-    # We've successfully processed the submission, send the user back to the index page.
+    # We've successfuly processed the submission, send the user back to the index page.
 
     ad_returnredirect "./"
 
Index: openacs-4/packages/acs-templating/www/doc/demo/list8/add-edit.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/demo/list8/add-edit.tcl,v
diff -u -r1.5.2.1 -r1.5.2.2
--- openacs-4/packages/acs-templating/www/doc/demo/list8/add-edit.tcl	10 Sep 2015 08:22:15 -0000	1.5.2.1
+++ openacs-4/packages/acs-templating/www/doc/demo/list8/add-edit.tcl	21 Apr 2017 16:50:30 -0000	1.5.2.2
@@ -106,7 +106,7 @@
 
 } -after_submit {
 
-    # We've successfully processed the submission, send the user back to the index page.
+    # We've successfuly processed the submission, send the user back to the index page.
 
     ad_returnredirect "./"
 
Index: openacs-4/packages/acs-templating/www/doc/demo/list9/add-edit.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/demo/list9/add-edit.tcl,v
diff -u -r1.3.2.1 -r1.3.2.2
--- openacs-4/packages/acs-templating/www/doc/demo/list9/add-edit.tcl	10 Sep 2015 08:22:15 -0000	1.3.2.1
+++ openacs-4/packages/acs-templating/www/doc/demo/list9/add-edit.tcl	21 Apr 2017 16:50:30 -0000	1.3.2.2
@@ -106,7 +106,7 @@
 
 } -after_submit {
 
-    # We've successfully processed the submission.
+    # We've successfuly processed the submission.
     # Clear the pagination cache.
 
     cache flush notes*
Index: openacs-4/packages/acs-templating/www/doc/demo/list9/delete.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/demo/list9/delete.tcl,v
diff -u -r1.2.2.3 -r1.2.2.4
--- openacs-4/packages/acs-templating/www/doc/demo/list9/delete.tcl	6 Feb 2017 12:46:04 -0000	1.2.2.3
+++ openacs-4/packages/acs-templating/www/doc/demo/list9/delete.tcl	21 Apr 2017 16:50:30 -0000	1.2.2.4
@@ -20,7 +20,7 @@
 	del
 }
 
-# We've successfully processed the submission.
+# We've successfuly processed the submission.
 # Clear the pagination cache.
 
 cache flush notes*
Index: openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.adp,v
diff -u -r1.2.2.6 -r1.2.2.7
--- openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.adp	7 Nov 2016 19:23:16 -0000	1.2.2.6
+++ openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.adp	21 Apr 2017 16:50:30 -0000	1.2.2.7
@@ -28,7 +28,7 @@
 as a reusable, unchanging framework that delivers dynamic data. The
 advantage to this is something you probably already realize: you
 need only build and edit a few pages to maintain a consistent
-presentation style while accomodating numerous permutaions of
+presentation style while accommodating numerous permutaions of
 changing data.</p>
 <p>This training module will teach largely by exercise and example,
 but you should also refer regularly to the <a href="../index">ATS documents</a> provided and more specific
@@ -120,7 +120,7 @@
 <p>Dynamic data implies a changing page, and also changing
 presentation. The <a href="../tags/if">&lt;if&gt;</a> and
 &lt;else&gt; tags allow you to alter the format of your page to
-accomodate data changes. The function of &lt;if&gt; is
+accommodate data changes. The function of &lt;if&gt; is
 straightforward enough: given a condition -- such as \@x\@ equals 5
 -- all the text/html/dynamic data between the the opening and
 closing &lt;if&gt; tags will be displayed if and only if \@x\@ does
Index: openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.html,v
diff -u -r1.1.1.1.30.1 -r1.1.1.1.30.2
--- openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.html	22 Jun 2016 07:48:44 -0000	1.1.1.1.30.1
+++ openacs-4/packages/acs-templating/www/doc/exercise/ats-for-designers.html	21 Apr 2017 16:50:30 -0000	1.1.1.1.30.2
@@ -33,7 +33,7 @@
 <p>First, perhaps an explanation of what the templating system does will help us understand
 how it works.  An ATS template itself serves as a reusable, unchanging framework that delivers
 dynamic data.  The advantage to this is something you probably already realize: you need only build 
-and edit a few pages to maintain a consistent presentation style while accomodating numerous permutaions of changing data.
+and edit a few pages to maintain a consistent presentation style while accommodating numerous permutaions of changing data.
 
 <p>This training module will teach largely by exercise and example, but you should also
 refer regularly to the <a href="../index.html">ATS documents</a> provided and more specific pointers will be given to help you out along the way.
@@ -136,7 +136,7 @@
 <p>
 Dynamic data implies a changing page, and also changing presentation.  
 The <a href="../tags/if.html">&lt;if&gt;</a> and &lt;else&gt; tags allow 
-you to alter the format of your page to accomodate data changes.  The 
+you to alter the format of your page to accommodate data changes.  The 
 function of &lt;if&gt;
 is straightforward enough: given a condition -- such as @x@ equals 5 -- 
 all the text/html/dynamic data between the the opening 
Index: openacs-4/packages/acs-templating/www/doc/guide/search.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/search.adp,v
diff -u -r1.2.2.5 -r1.2.2.6
--- openacs-4/packages/acs-templating/www/doc/guide/search.adp	1 Dec 2016 20:43:45 -0000	1.2.2.5
+++ openacs-4/packages/acs-templating/www/doc/guide/search.adp	21 Apr 2017 16:50:30 -0000	1.2.2.6
@@ -25,8 +25,8 @@
 the search criteria and search again.</p><p>To continue the travel site example, if an exact match is found
 for the cities entered by the user, the system immediately returns
 a list of flights. If several possible matches are found, the
-system prompts the user to choose a city before proceding. If no
-matches are found, the sytem prompts the user to search again.</p>
+system prompts the user to choose a city before proceeding. If no
+matches are found, the system prompts the user to search again.</p>
 </li>
 </ol>
 <p>To illustrate how to implement this type of page flow using the
Index: openacs-4/packages/acs-templating/www/doc/guide/search.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/search.html,v
diff -u -r1.1.1.1.30.2 -r1.1.1.1.30.3
--- openacs-4/packages/acs-templating/www/doc/guide/search.html	1 Dec 2016 20:43:45 -0000	1.1.1.1.30.2
+++ openacs-4/packages/acs-templating/www/doc/guide/search.html	21 Apr 2017 16:50:30 -0000	1.1.1.1.30.3
@@ -27,8 +27,8 @@
   <p>To continue the travel site example, if an exact match is
   found for the cities entered by the user, the system immediately
   returns a list of flights.  If several possible matches are found,
-  the system prompts the user to choose a city before proceding.  If
-  no matches are found, the sytem prompts the user to search again.</p>
+  the system prompts the user to choose a city before proceeding.  If
+  no matches are found, the system prompts the user to search again.</p>
 </ol>
 
 <p>To illustrate how to implement this type of page flow using the
Index: openacs-4/packages/acs-templating/www/doc/guide/templates.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/templates.adp,v
diff -u -r1.3.2.7 -r1.3.2.8
--- openacs-4/packages/acs-templating/www/doc/guide/templates.adp	1 Dec 2016 20:43:45 -0000	1.3.2.7
+++ openacs-4/packages/acs-templating/www/doc/guide/templates.adp	21 Apr 2017 16:50:30 -0000	1.3.2.8
@@ -73,7 +73,7 @@
 designer may want to have alternate between white and gray bands in
 a table.</p></li>
 </ol>
-<p>To accomodate these type of scenarios, the template parser sets
+<p>To accommodate these type of scenarios, the template parser sets
 some additional variables that the designer can reference to vary
 the layout from item to item.</p>
 <p>See <a href="../tagref/multiple"><kbd>multiple</kbd></a>,
Index: openacs-4/packages/acs-templating/www/doc/guide/templates.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/guide/templates.html,v
diff -u -r1.1.1.1.30.2 -r1.1.1.1.30.3
--- openacs-4/packages/acs-templating/www/doc/guide/templates.html	1 Dec 2016 20:43:45 -0000	1.1.1.1.30.2
+++ openacs-4/packages/acs-templating/www/doc/guide/templates.html	21 Apr 2017 16:50:30 -0000	1.1.1.1.30.3
@@ -93,7 +93,7 @@
       in a table.</p>
 </ol>
 
-<p>To accomodate these type of scenarios, the template parser sets
+<p>To accommodate these type of scenarios, the template parser sets
 some additional variables that the designer can reference to vary
 the layout from item to item.</p>
 
Index: openacs-4/packages/acs-templating/www/doc/tagref/if.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/tagref/if.adp,v
diff -u -r1.3.2.8 -r1.3.2.9
--- openacs-4/packages/acs-templating/www/doc/tagref/if.adp	1 Dec 2016 17:14:38 -0000	1.3.2.8
+++ openacs-4/packages/acs-templating/www/doc/tagref/if.adp	21 Apr 2017 16:50:30 -0000	1.3.2.9
@@ -112,7 +112,7 @@
 <ul>
 <li><p>Any legal variables that may be referenced in the template may
 also be used in <kbd>if</kbd> statements. Words not surrounded with
-the commerical at sign (<kbd>\@</kbd>) are interpreted
+the commercial at sign (<kbd>\@</kbd>) are interpreted
 literally.</p></li><li>
 <p>Phrases with spaces in them must be enclosed in quotes to be
 grouped correctly:</p><pre>
Index: openacs-4/packages/acs-templating/www/doc/tagref/if.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/doc/tagref/if.html,v
diff -u -r1.3.22.2 -r1.3.22.3
--- openacs-4/packages/acs-templating/www/doc/tagref/if.html	1 Dec 2016 20:43:45 -0000	1.3.22.2
+++ openacs-4/packages/acs-templating/www/doc/tagref/if.html	21 Apr 2017 16:50:30 -0000	1.3.22.3
@@ -133,7 +133,7 @@
 
 <li><p>Any legal variables that may be referenced in the template may
 also be used in <kbd>if</kbd> statements.  Words not surrounded with
-the commerical at sign (<kbd>@</kbd>) are interpreted literally.</p>
+the commercial at sign (<kbd>@</kbd>) are interpreted literally.</p>
 
 <li><p>Phrases with spaces in them must be enclosed in quotes to
 be grouped correctly:
Index: openacs-4/packages/acs-templating/www/resources/htmlarea/release-notes.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/resources/htmlarea/release-notes.html,v
diff -u -r1.2.18.1 -r1.2.18.2
--- openacs-4/packages/acs-templating/www/resources/htmlarea/release-notes.html	22 Jun 2016 07:48:44 -0000	1.2.18.1
+++ openacs-4/packages/acs-templating/www/resources/htmlarea/release-notes.html	21 Apr 2017 16:50:30 -0000	1.2.18.2
@@ -59,7 +59,7 @@
           </li>
           <li>
             Speed and bandwidth optimization: reports the list of
-            suggestions only once for each mispelled word; this helps
+            suggestions only once for each misspelled word; this helps
             in cases where you have, for instance, the word “HTMLArea”
             in 10 places all over the document; the list of
             suggestions for it--which is kind of huge--will only be
@@ -76,7 +76,7 @@
           <li>
             Added a "Info" button which reports information about the
             document, retrieved by the server-side spell checker:
-            total number of words, total number of mispelled words,
+            total number of words, total number of misspelled words,
             number of suggestions made, spell check time, etc.  More
             can be easily added.  <span class="fixme">FIXME: this part
             is not yet internationalized.</span>
Index: openacs-4/packages/acs-templating/www/resources/htmlarea/examples/fully-loaded.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/resources/htmlarea/examples/fully-loaded.html,v
diff -u -r1.1 -r1.1.18.1
--- openacs-4/packages/acs-templating/www/resources/htmlarea/examples/fully-loaded.html	30 Jan 2005 16:13:26 -0000	1.1
+++ openacs-4/packages/acs-templating/www/resources/htmlarea/examples/fully-loaded.html	21 Apr 2017 16:50:30 -0000	1.1.18.1
@@ -1,262 +1,262 @@
-<html>
-<head>
-<title>Example of HTMLArea 3.0</title>
-
-<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
-
-<!-- Configure the path to the editor.  We make it relative now, so that the
-    example ZIP file will work anywhere, but please NOTE THAT it's better to
-    have it an absolute path, such as '/htmlarea/'. -->
-<script type="text/javascript">
-  _editor_url = "../";
-  _editor_lang = "en";
-</script>
-
-<!-- load the main HTMLArea file, this will take care of loading the CSS and
-    other required core scripts. -->
-<script type="text/javascript" src="../htmlarea.js"></script>
-
-<!-- load the plugins -->
-<script type="text/javascript">
-      // WARNING: using this interface to load plugin
-      // will _NOT_ work if plugins do not have the language
-      // loaded by HTMLArea.
-
-      // In other words, this function generates SCRIPT tags
-      // that load the plugin and the language file, based on the
-      // global variable HTMLArea.I18N.lang (defined in the lang file,
-      // in our case "lang/en.js" loaded above).
-
-      // If this lang file is not found the plugin will fail to
-      // load correctly and NOTHING WILL WORK.
-
-      HTMLArea.loadPlugin("TableOperations");
-      HTMLArea.loadPlugin("SpellChecker");
-      HTMLArea.loadPlugin("FullPage");
-      HTMLArea.loadPlugin("CSS");
-      HTMLArea.loadPlugin("ContextMenu");
-      //HTMLArea.loadPlugin("HtmlTidy");
-      HTMLArea.loadPlugin("ListType");
-      HTMLArea.loadPlugin("CharacterMap");
-HTMLArea.loadPlugin("DynamicCSS");
-</script>
-
-<style type="text/css">
-html, body {
-  font-family: Verdana,sans-serif;
-  background-color: #fea;
-  color: #000;
-}
-a:link, a:visited { color: #00f; }
-a:hover { color: #048; }
-a:active { color: #f00; }
-
-textarea { background-color: #fff; border: 1px solid 00f; }
-</style>
-
-<script type="text/javascript">
-var editor = null;
-
-function initEditor() {
-
-  // create an editor for the "ta" textbox
-  editor = new HTMLArea("ta");
-
-  // register the FullPage plugin
-  editor.registerPlugin(FullPage);
-
-  // register the SpellChecker plugin
-  editor.registerPlugin(TableOperations);
-
-  // register the SpellChecker plugin
-  editor.registerPlugin(SpellChecker);
-
-  // register the HtmlTidy plugin
-  //editor.registerPlugin(HtmlTidy);
-
-  // register the ListType plugin
-  editor.registerPlugin(ListType);
-
-//  editor.registerPlugin(CharacterMap);
-editor.registerPlugin(DynamicCSS);
-
-  // register the CSS plugin
-  editor.registerPlugin(CSS, {
-    combos : [
-      { label: "Syntax:",
-                   // menu text       // CSS class
-        options: { "None"           : "",
-                   "Code" : "code",
-                   "String" : "string",
-                   "Comment" : "comment",
-                   "Variable name" : "variable-name",
-                   "Type" : "type",
-                   "Reference" : "reference",
-                   "Preprocessor" : "preprocessor",
-                   "Keyword" : "keyword",
-                   "Function name" : "function-name",
-                   "Html tag" : "html-tag",
-                   "Html italic" : "html-helper-italic",
-                   "Warning" : "warning",
-                   "Html bold" : "html-helper-bold"
-                 },
-        context: "pre"
-      },
-      { label: "Info:",
-        options: { "None"           : "",
-                   "Quote"          : "quote",
-                   "Highlight"      : "highlight",
-                   "Deprecated"     : "deprecated"
-                 }
-      }
-    ]
-  });
-
-  // add a contextual menu
-  editor.registerPlugin("ContextMenu");
-
-  // load the stylesheet used by our CSS plugin configuration
-  editor.config.pageStyle = "@import url(custom.css);";
-
-  editor.generate();
-  return false;
-}
-
-HTMLArea.onload = initEditor;
-
-function insertHTML() {
-  var html = prompt("Enter some HTML code here");
-  if (html) {
-    editor.insertHTML(html);
-  }
-}
-function highlight() {
-  editor.surroundHTML('<span style="background-color: yellow">', '</span>');
-}
-</script>
-
-</head>
-
-<!-- use <body onload="HTMLArea.replaceAll()" if you don't care about
-     customizing the editor.  It's the easiest way! :) -->
-<body onload="HTMLArea.init();">
-
-<h1>HTMLArea 3.0</h1>
-
-<p>A replacement for <code>TEXTAREA</code> elements.  &copy; <a
-href="http://interactivetools.com">InteractiveTools.com</a>, 2003-2004.</p>
-
-<form action="test.cgi" method="post" id="edit" name="edit">
-
-<textarea id="ta" name="ta" style="width:100%" rows="24" cols="80">
-&lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 3.2//EN"&gt;
-&lt;html&gt;
-
-&lt;head&gt;
-&lt;title&gt;Passing parameters to JavaScript code&lt;/title&gt;
-&lt;link rel="stylesheet" href="custom.css" /&gt;
-&lt;/head&gt;
-
-&lt;body&gt;
-&lt;h1&gt;Passing parameters to JavaScript code&lt;/h1&gt;
-
-&lt;p&gt;Sometimes we need to pass parameters to some JavaScript function that we
-wrote ourselves.  But sometimes it's simply more convenient to include the
-parameter not in the function call, but in the affected HTML elements.
-Usually, all JavaScript calls affect some element, right? ;-)&lt;/p&gt;
-
-&lt;p&gt;Well, here's an original way to do it.  Or at least, I think it's
-original.&lt;/p&gt;
-
-&lt;h2&gt;But first...&lt;/h2&gt;
-
-&lt;p&gt;... an example.  Why would I need such thing?  I have a JS function that
-is called on &lt;code&gt;BODY&lt;/code&gt; &lt;code&gt;onload&lt;/code&gt; handler.  This function
-tries to retrieve the element with the ID "conttoc" and, if present, it will
-&lt;a href="toc.epl" title="Automatic TOC generation"&gt;generate an index&lt;/a&gt;.
-The problem is, this function exists in some external JavaScript library
-that it's loaded in page.  I only needed to pass the parameter from
-&lt;em&gt;one&lt;/em&gt; page.  Thus, it makes sense to pass the parameter from the HTML
-code on &lt;em&gt;that&lt;/em&gt; page, not to affect the others.&lt;/p&gt;
-
-&lt;p&gt;The first idea that came to me was to use some attribute, like "id" or
-"class".  But "id" was locked already, it &lt;em&gt;had&lt;/em&gt; to be "conttoc".  Use
-"class"?  It's not elegant.. what if I really wanted to give it a class, at
-some point?&lt;/p&gt;
-
-&lt;h2&gt;The idea&lt;/h2&gt;
-
-&lt;p&gt;So I thought: what are the HTML elements that do not affect the page
-rendering in any way?  Well, comments.  I mean, &lt;em&gt;comments&lt;/em&gt;, HTML
-comments.  You know, like &lt;code&gt;&amp;lt;!-- this is a comment --&amp;gt;&lt;/code&gt;.&lt;/p&gt;
-
-&lt;p&gt;Though comments do not normally affect the way browser renders the page,
-they are still parsed and are part of the DOM, as well as any other node.
-But this mean that we can access comments from JavaScript code, just like we
-access any other element, right?  Which means that they &lt;em&gt;can&lt;/em&gt; affect
-the way that page finally appears ;-)&lt;/p&gt;
-
-&lt;h2&gt;The code&lt;/h2&gt;
-
-&lt;p&gt;The main part was the idea.  The code is simple ;-)  Suppose we have the
-following HTML code:&lt;/p&gt;
-
-&lt;pre class="code"&gt;&lt;span class="function-name"&gt;&amp;lt;&lt;/span&gt;&lt;span class="html-tag"&gt;div&lt;/span&gt; &lt;span class="variable-name"&gt;id=&lt;/span&gt;&lt;span class="string"&gt;&amp;quot;conttoc&amp;quot;&lt;/span&gt;&lt;span class="paren-face-match"&gt;&amp;gt;&lt;/span&gt;&lt;span class="function-name"&gt;&amp;lt;&lt;/span&gt;&lt;span class="html-tag"&gt;/div&lt;/span&gt;&lt;span class="function-name"&gt;&amp;gt;&lt;/span&gt;&lt;/pre&gt;
-
-&lt;p&gt;and our function checks for the presence an element having the ID
-"conttoc", and generates a table of contents into it.  Our code will also
-check if the "conttoc" element's first child is a comment node, and if so
-will parse additional parameters from there, for instance, a desired prefix
-for the links that are to be generated into it.  Why did I need it?  Because
-if the page uses a &lt;code&gt;&amp;lt;base&amp;gt;&lt;/code&gt; element to specify the default
-link prefix, then links like "#gen1" generated by the &lt;a href="toc.epl"&gt;toc
-generator&lt;/a&gt; will not point to that same page as they should, but to the
-page reffered from &lt;code&gt;&amp;lt;base&amp;gt;&lt;/code&gt;.&lt;/p&gt;
-
-&lt;p&gt;So the HTML would now look like this:&lt;/p&gt;
-
-&lt;pre class="code"&gt;&lt;span class="function-name"&gt;&amp;lt;&lt;/span&gt;&lt;span class="html-tag"&gt;div&lt;/span&gt; &lt;span class="variable-name"&gt;id=&lt;/span&gt;&lt;span class="string"&gt;&amp;quot;conttoc&amp;quot;&lt;/span&gt;&lt;span class="function-name"&gt;&amp;gt;&lt;/span&gt;&lt;span class="comment"&gt;&amp;lt;!-- base:link/prefix.html --&amp;gt;&lt;/span&gt;&lt;span class="paren-face-match"&gt;&amp;lt;&lt;/span&gt;&lt;span class="html-tag"&gt;/div&lt;/span&gt;&lt;span class="paren-face-match"&gt;&amp;gt;&lt;/span&gt;&lt;/pre&gt;
-
-&lt;p&gt;And our TOC generation function does something like this:&lt;/p&gt;
-
-&lt;pre class="code"&gt;&lt;span class="keyword"&gt;var&lt;/span&gt; &lt;span class="variable-name"&gt;element&lt;/span&gt; = getElementById(&amp;quot;&lt;span class="string"&gt;conttoc&lt;/span&gt;&amp;quot;);
-&lt;span class="keyword"&gt;if&lt;/span&gt; (element.firstChild &amp;amp;&amp;amp; element.firstChild.nodeType == 8) {
-  &lt;span class="comment"&gt;// 8 means Node.COMMENT_NODE.  We're using numeric values
-&lt;/span&gt;  &lt;span class="comment"&gt;// because IE6 does not support constant names.
-&lt;/span&gt;  &lt;span class="keyword"&gt;var&lt;/span&gt; &lt;span class="variable-name"&gt;parameters&lt;/span&gt; = element.firstChild.data;
-  &lt;span class="comment"&gt;// at this point &amp;quot;parameters&amp;quot; contains base:link/prefix.html
-&lt;/span&gt;  &lt;span class="comment"&gt;// ...
-&lt;/span&gt;}&lt;/pre&gt;
-
-&lt;p&gt;So we retrieved the value passed to the script from the HTML code.  This
-was the goal of this article.&lt;/p&gt;
-
-&lt;hr /&gt;
-&lt;address&gt;&lt;a href="http://students.infoiasi.ro/~mishoo/"&gt;Mihai Bazon&lt;/a&gt;&lt;/address&gt;
-&lt;!-- hhmts start --&gt; Last modified on Thu Apr  3 20:34:17 2003
-&lt;!-- hhmts end --&gt;
-&lt;!-- doc-lang: English --&gt;
-&lt;/body&gt;
-&lt;/html&gt;
-</textarea>
-
-<p />
-
-<input type="submit" name="ok" value="  submit  " />
-<input type="button" name="ins" value="  insert html  " onclick="return insertHTML();" />
-<input type="button" name="hil" value="  highlight text  " onclick="return highlight();" />
-
-<a href="javascript:mySubmit()">submit</a>
-
-<script type="text/javascript">
-function mySubmit() {
-// document.edit.save.value = "yes";
-document.edit.onsubmit(); // workaround browser bugs.
-document.edit.submit();
-};
-</script>
-
-</form>
-
-</body>
-</html>
+<html>
+<head>
+<title>Example of HTMLArea 3.0</title>
+
+<meta http-equiv="Content-Type" content="text/html; charset=utf-8" />
+
+<!-- Configure the path to the editor.  We make it relative now, so that the
+    example ZIP file will work anywhere, but please NOTE THAT it's better to
+    have it an absolute path, such as '/htmlarea/'. -->
+<script type="text/javascript">
+  _editor_url = "../";
+  _editor_lang = "en";
+</script>
+
+<!-- load the main HTMLArea file, this will take care of loading the CSS and
+    other required core scripts. -->
+<script type="text/javascript" src="../htmlarea.js"></script>
+
+<!-- load the plugins -->
+<script type="text/javascript">
+      // WARNING: using this interface to load plugin
+      // will _NOT_ work if plugins do not have the language
+      // loaded by HTMLArea.
+
+      // In other words, this function generates SCRIPT tags
+      // that load the plugin and the language file, based on the
+      // global variable HTMLArea.I18N.lang (defined in the lang file,
+      // in our case "lang/en.js" loaded above).
+
+      // If this lang file is not found the plugin will fail to
+      // load correctly and NOTHING WILL WORK.
+
+      HTMLArea.loadPlugin("TableOperations");
+      HTMLArea.loadPlugin("SpellChecker");
+      HTMLArea.loadPlugin("FullPage");
+      HTMLArea.loadPlugin("CSS");
+      HTMLArea.loadPlugin("ContextMenu");
+      //HTMLArea.loadPlugin("HtmlTidy");
+      HTMLArea.loadPlugin("ListType");
+      HTMLArea.loadPlugin("CharacterMap");
+HTMLArea.loadPlugin("DynamicCSS");
+</script>
+
+<style type="text/css">
+html, body {
+  font-family: Verdana,sans-serif;
+  background-color: #fea;
+  color: #000;
+}
+a:link, a:visited { color: #00f; }
+a:hover { color: #048; }
+a:active { color: #f00; }
+
+textarea { background-color: #fff; border: 1px solid 00f; }
+</style>
+
+<script type="text/javascript">
+var editor = null;
+
+function initEditor() {
+
+  // create an editor for the "ta" textbox
+  editor = new HTMLArea("ta");
+
+  // register the FullPage plugin
+  editor.registerPlugin(FullPage);
+
+  // register the SpellChecker plugin
+  editor.registerPlugin(TableOperations);
+
+  // register the SpellChecker plugin
+  editor.registerPlugin(SpellChecker);
+
+  // register the HtmlTidy plugin
+  //editor.registerPlugin(HtmlTidy);
+
+  // register the ListType plugin
+  editor.registerPlugin(ListType);
+
+//  editor.registerPlugin(CharacterMap);
+editor.registerPlugin(DynamicCSS);
+
+  // register the CSS plugin
+  editor.registerPlugin(CSS, {
+    combos : [
+      { label: "Syntax:",
+                   // menu text       // CSS class
+        options: { "None"           : "",
+                   "Code" : "code",
+                   "String" : "string",
+                   "Comment" : "comment",
+                   "Variable name" : "variable-name",
+                   "Type" : "type",
+                   "Reference" : "reference",
+                   "Preprocessor" : "preprocessor",
+                   "Keyword" : "keyword",
+                   "Function name" : "function-name",
+                   "Html tag" : "html-tag",
+                   "Html italic" : "html-helper-italic",
+                   "Warning" : "warning",
+                   "Html bold" : "html-helper-bold"
+                 },
+        context: "pre"
+      },
+      { label: "Info:",
+        options: { "None"           : "",
+                   "Quote"          : "quote",
+                   "Highlight"      : "highlight",
+                   "Deprecated"     : "deprecated"
+                 }
+      }
+    ]
+  });
+
+  // add a contextual menu
+  editor.registerPlugin("ContextMenu");
+
+  // load the stylesheet used by our CSS plugin configuration
+  editor.config.pageStyle = "@import url(custom.css);";
+
+  editor.generate();
+  return false;
+}
+
+HTMLArea.onload = initEditor;
+
+function insertHTML() {
+  var html = prompt("Enter some HTML code here");
+  if (html) {
+    editor.insertHTML(html);
+  }
+}
+function highlight() {
+  editor.surroundHTML('<span style="background-color: yellow">', '</span>');
+}
+</script>
+
+</head>
+
+<!-- use <body onload="HTMLArea.replaceAll()" if you don't care about
+     customizing the editor.  It's the easiest way! :) -->
+<body onload="HTMLArea.init();">
+
+<h1>HTMLArea 3.0</h1>
+
+<p>A replacement for <code>TEXTAREA</code> elements.  &copy; <a
+href="http://interactivetools.com">InteractiveTools.com</a>, 2003-2004.</p>
+
+<form action="test.cgi" method="post" id="edit" name="edit">
+
+<textarea id="ta" name="ta" style="width:100%" rows="24" cols="80">
+&lt;!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 3.2//EN"&gt;
+&lt;html&gt;
+
+&lt;head&gt;
+&lt;title&gt;Passing parameters to JavaScript code&lt;/title&gt;
+&lt;link rel="stylesheet" href="custom.css" /&gt;
+&lt;/head&gt;
+
+&lt;body&gt;
+&lt;h1&gt;Passing parameters to JavaScript code&lt;/h1&gt;
+
+&lt;p&gt;Sometimes we need to pass parameters to some JavaScript function that we
+wrote ourselves.  But sometimes it's simply more convenient to include the
+parameter not in the function call, but in the affected HTML elements.
+Usually, all JavaScript calls affect some element, right? ;-)&lt;/p&gt;
+
+&lt;p&gt;Well, here's an original way to do it.  Or at least, I think it's
+original.&lt;/p&gt;
+
+&lt;h2&gt;But first...&lt;/h2&gt;
+
+&lt;p&gt;... an example.  Why would I need such thing?  I have a JS function that
+is called on &lt;code&gt;BODY&lt;/code&gt; &lt;code&gt;onload&lt;/code&gt; handler.  This function
+tries to retrieve the element with the ID "conttoc" and, if present, it will
+&lt;a href="toc.epl" title="Automatic TOC generation"&gt;generate an index&lt;/a&gt;.
+The problem is, this function exists in some external JavaScript library
+that it's loaded in page.  I only needed to pass the parameter from
+&lt;em&gt;one&lt;/em&gt; page.  Thus, it makes sense to pass the parameter from the HTML
+code on &lt;em&gt;that&lt;/em&gt; page, not to affect the others.&lt;/p&gt;
+
+&lt;p&gt;The first idea that came to me was to use some attribute, like "id" or
+"class".  But "id" was locked already, it &lt;em&gt;had&lt;/em&gt; to be "conttoc".  Use
+"class"?  It's not elegant.. what if I really wanted to give it a class, at
+some point?&lt;/p&gt;
+
+&lt;h2&gt;The idea&lt;/h2&gt;
+
+&lt;p&gt;So I thought: what are the HTML elements that do not affect the page
+rendering in any way?  Well, comments.  I mean, &lt;em&gt;comments&lt;/em&gt;, HTML
+comments.  You know, like &lt;code&gt;&amp;lt;!-- this is a comment --&amp;gt;&lt;/code&gt;.&lt;/p&gt;
+
+&lt;p&gt;Though comments do not normally affect the way browser renders the page,
+they are still parsed and are part of the DOM, as well as any other node.
+But this mean that we can access comments from JavaScript code, just like we
+access any other element, right?  Which means that they &lt;em&gt;can&lt;/em&gt; affect
+the way that page finally appears ;-)&lt;/p&gt;
+
+&lt;h2&gt;The code&lt;/h2&gt;
+
+&lt;p&gt;The main part was the idea.  The code is simple ;-)  Suppose we have the
+following HTML code:&lt;/p&gt;
+
+&lt;pre class="code"&gt;&lt;span class="function-name"&gt;&amp;lt;&lt;/span&gt;&lt;span class="html-tag"&gt;div&lt;/span&gt; &lt;span class="variable-name"&gt;id=&lt;/span&gt;&lt;span class="string"&gt;&amp;quot;conttoc&amp;quot;&lt;/span&gt;&lt;span class="paren-face-match"&gt;&amp;gt;&lt;/span&gt;&lt;span class="function-name"&gt;&amp;lt;&lt;/span&gt;&lt;span class="html-tag"&gt;/div&lt;/span&gt;&lt;span class="function-name"&gt;&amp;gt;&lt;/span&gt;&lt;/pre&gt;
+
+&lt;p&gt;and our function checks for the presence an element having the ID
+"conttoc", and generates a table of contents into it.  Our code will also
+check if the "conttoc" element's first child is a comment node, and if so
+will parse additional parameters from there, for instance, a desired prefix
+for the links that are to be generated into it.  Why did I need it?  Because
+if the page uses a &lt;code&gt;&amp;lt;base&amp;gt;&lt;/code&gt; element to specify the default
+link prefix, then links like "#gen1" generated by the &lt;a href="toc.epl"&gt;toc
+generator&lt;/a&gt; will not point to that same page as they should, but to the
+page referred from &lt;code&gt;&amp;lt;base&amp;gt;&lt;/code&gt;.&lt;/p&gt;
+
+&lt;p&gt;So the HTML would now look like this:&lt;/p&gt;
+
+&lt;pre class="code"&gt;&lt;span class="function-name"&gt;&amp;lt;&lt;/span&gt;&lt;span class="html-tag"&gt;div&lt;/span&gt; &lt;span class="variable-name"&gt;id=&lt;/span&gt;&lt;span class="string"&gt;&amp;quot;conttoc&amp;quot;&lt;/span&gt;&lt;span class="function-name"&gt;&amp;gt;&lt;/span&gt;&lt;span class="comment"&gt;&amp;lt;!-- base:link/prefix.html --&amp;gt;&lt;/span&gt;&lt;span class="paren-face-match"&gt;&amp;lt;&lt;/span&gt;&lt;span class="html-tag"&gt;/div&lt;/span&gt;&lt;span class="paren-face-match"&gt;&amp;gt;&lt;/span&gt;&lt;/pre&gt;
+
+&lt;p&gt;And our TOC generation function does something like this:&lt;/p&gt;
+
+&lt;pre class="code"&gt;&lt;span class="keyword"&gt;var&lt;/span&gt; &lt;span class="variable-name"&gt;element&lt;/span&gt; = getElementById(&amp;quot;&lt;span class="string"&gt;conttoc&lt;/span&gt;&amp;quot;);
+&lt;span class="keyword"&gt;if&lt;/span&gt; (element.firstChild &amp;amp;&amp;amp; element.firstChild.nodeType == 8) {
+  &lt;span class="comment"&gt;// 8 means Node.COMMENT_NODE.  We're using numeric values
+&lt;/span&gt;  &lt;span class="comment"&gt;// because IE6 does not support constant names.
+&lt;/span&gt;  &lt;span class="keyword"&gt;var&lt;/span&gt; &lt;span class="variable-name"&gt;parameters&lt;/span&gt; = element.firstChild.data;
+  &lt;span class="comment"&gt;// at this point &amp;quot;parameters&amp;quot; contains base:link/prefix.html
+&lt;/span&gt;  &lt;span class="comment"&gt;// ...
+&lt;/span&gt;}&lt;/pre&gt;
+
+&lt;p&gt;So we retrieved the value passed to the script from the HTML code.  This
+was the goal of this article.&lt;/p&gt;
+
+&lt;hr /&gt;
+&lt;address&gt;&lt;a href="http://students.infoiasi.ro/~mishoo/"&gt;Mihai Bazon&lt;/a&gt;&lt;/address&gt;
+&lt;!-- hhmts start --&gt; Last modified on Thu Apr  3 20:34:17 2003
+&lt;!-- hhmts end --&gt;
+&lt;!-- doc-lang: English --&gt;
+&lt;/body&gt;
+&lt;/html&gt;
+</textarea>
+
+<p />
+
+<input type="submit" name="ok" value="  submit  " />
+<input type="button" name="ins" value="  insert html  " onclick="return insertHTML();" />
+<input type="button" name="hil" value="  highlight text  " onclick="return highlight();" />
+
+<a href="javascript:mySubmit()">submit</a>
+
+<script type="text/javascript">
+function mySubmit() {
+// document.edit.save.value = "yes";
+document.edit.onsubmit(); // workaround browser bugs.
+document.edit.submit();
+};
+</script>
+
+</form>
+
+</body>
+</html>
Index: openacs-4/packages/acs-templating/www/resources/htmlarea/examples/spell-checker.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/resources/htmlarea/examples/spell-checker.html,v
diff -u -r1.1.18.1 -r1.1.18.2
--- openacs-4/packages/acs-templating/www/resources/htmlarea/examples/spell-checker.html	22 Jun 2016 07:48:44 -0000	1.1.18.1
+++ openacs-4/packages/acs-templating/www/resources/htmlarea/examples/spell-checker.html	21 Apr 2017 16:50:30 -0000	1.1.18.2
@@ -83,7 +83,7 @@
         word in the text and reports wordz that aren't found in the
         dyctionari.</p>
 
-      <p>The document that yu are reading now <strong>intentionaly</strong> containes
+      <p>The document that yu are reading now <strong>intentionaly</strong> contains
         some errorz, so that you have something to corect ;-)</p>
 
       <p>Credits for the <kbd>SpellChecker</kbd> plugin go to:</p>
Index: openacs-4/packages/acs-templating/www/resources/htmlarea/plugins/SpellChecker/readme-tech.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-templating/www/resources/htmlarea/plugins/SpellChecker/readme-tech.html,v
diff -u -r1.2.18.1 -r1.2.18.2
--- openacs-4/packages/acs-templating/www/resources/htmlarea/plugins/SpellChecker/readme-tech.html	22 Jun 2016 07:48:44 -0000	1.2.18.1
+++ openacs-4/packages/acs-templating/www/resources/htmlarea/plugins/SpellChecker/readme-tech.html	21 Apr 2017 16:50:30 -0000	1.2.18.2
@@ -24,7 +24,7 @@
       <li>spell-checker-logic.cgi &mdash; Perl CGI script that checks a text
         given through POST for spelling errors</li>
 
-      <li>spell-checker-style.css &mdash; style for mispelled words</li>
+      <li>spell-checker-style.css &mdash; style for misspelled words</li>
 
       <li>lang/en.js &mdash; main language file (English).</li>
 
@@ -48,7 +48,7 @@
       clear marks of which words are incorrect, along with suggestions for
       each of them.  This file is then loaded in the inline frame.  Upon
       loading, a JavaScript function from "spell-check-ui.js" is called.
-      This function will retrieve all mispelled words from the HTML of the
+      This function will retrieve all misspelled words from the HTML of the
       iframe and will setup the user interface so that it allows correction.
     </p>
 
@@ -63,7 +63,7 @@
       yet (<a
         href="http://mail.gnu.org/archive/html/aspell-user/2000-11/msg00007.html">thread concerning Aspell and Unicode</a>).
       This mean that words containing Unicode
-      characters that are not in 0..255 are likely to be reported as "mispelled" by Aspell.</strike>
+      characters that are not in 0..255 are likely to be reported as "misspelled" by Aspell.</strike>
     </p>
 
     <p>