Index: openacs-4/packages/workflow/tcl/case-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/workflow/tcl/case-procs.tcl,v
diff -u -r1.53 -r1.54
--- openacs-4/packages/workflow/tcl/case-procs.tcl	9 May 2018 15:33:33 -0000	1.53
+++ openacs-4/packages/workflow/tcl/case-procs.tcl	22 Mar 2019 22:28:00 -0000	1.54
@@ -321,7 +321,7 @@
 } {
     Get the currently enabled_action_id's of enabled user actions in the case.
 
-    Note, that this is different from get_enabled_actions, which only returns 
+    Note that this is different from get_enabled_actions, which only returns 
     the action_id, which will not work for dynamic actions.
 
     @param case_id       The ID of the case.
@@ -2541,7 +2541,7 @@
 
         if { $enabled_action_id ne "" } {
             workflow::case::enabled_action_get -enabled_action_id $enabled_action_id -array enabled_action
-            # Even if these are provided, we overide them with the DB call
+            # Even if these are provided, we override them with the DB call
             set case_id $enabled_action(case_id)
             set action_id $enabled_action(action_id)
             set parent_enabled_action_id $enabled_action(parent_enabled_action_id)
Index: openacs-4/packages/workflow/www/doc/developer-guide.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/workflow/www/doc/developer-guide.adp,v
diff -u -r1.7 -r1.8
--- openacs-4/packages/workflow/www/doc/developer-guide.adp	28 Mar 2018 23:50:36 -0000	1.7
+++ openacs-4/packages/workflow/www/doc/developer-guide.adp	22 Mar 2019 22:28:00 -0000	1.8
@@ -73,7 +73,7 @@
 <p>As mentioned, workflow is designed to support workflows based on
 any model, however the only model currently implemented is the
 finite state machine.</p>
-<p>The workflow API is designed so that whenver you&#39;re using
+<p>The workflow API is designed so that whenever you&#39;re using
 features that are specific to finite state machines, the procedure
 name will include the letters "fsm" in the name, as in
 <code><a href="/api-doc/proc-view?proc=workflow::case::fsm::get">workflow::case::fsm::get</a></code>.
Index: openacs-4/packages/workflow/www/doc/developer-guide.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/workflow/www/doc/developer-guide.html,v
diff -u -r1.7 -r1.8
--- openacs-4/packages/workflow/www/doc/developer-guide.html	28 Mar 2018 23:50:36 -0000	1.7
+++ openacs-4/packages/workflow/www/doc/developer-guide.html	22 Mar 2019 22:28:00 -0000	1.8
@@ -150,7 +150,7 @@
 </p>
 
 <p>
-  The workflow API is designed so that whenver you're using features
+  The workflow API is designed so that whenever you're using features
   that are specific to finite state machines, the procedure name will
   include the letters "fsm" in the name, as in <code><a
   href="/api-doc/proc-view?proc=workflow::case::fsm::get">workflow::case::fsm::get</a></code>. That