Index: openacs-4/packages/dotlrn/tcl/dotlrn-security-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrn/tcl/dotlrn-security-procs.tcl,v
diff -u -N -r1.62 -r1.63
--- openacs-4/packages/dotlrn/tcl/dotlrn-security-procs.tcl	7 Aug 2017 23:48:09 -0000	1.62
+++ openacs-4/packages/dotlrn/tcl/dotlrn-security-procs.tcl	27 Mar 2018 14:32:16 -0000	1.63
@@ -133,7 +133,7 @@
             # if the user is a member of communities (from some previous
             # dotlrn relation) then we must remove them from the community and
             # re-add them so that all the portals will work properly.
-            # NOTE: we cannot do this in a db_foreach beacause of the table we
+            # NOTE: we cannot do this in a db_foreach because of the table we
             # are selecting from changes inside the loop causing all kinds of
             # dead lock issues.
             set current_memberships [db_list_of_ns_sets select_current_memberships {
@@ -200,7 +200,7 @@
         Remove the user from ACS as well.  Chances are pretty good that
         this will fail because it's hard to chase down every piece
         of content the user has ever put into the system.  The net result is
-        that there may be stray referential integrity contraints that
+        that there may be stray referential integrity constraints that
         will throw errors when we try to remove the user record permanently.
 
         @param on_fail indicates what we do if the permanent removal fails. Setting to