Index: openacs-4/packages/dotlrn/tcl/community-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrn/tcl/community-procs.tcl,v
diff -u -r1.231 -r1.232
--- openacs-4/packages/dotlrn/tcl/community-procs.tcl	17 Jul 2018 11:42:26 -0000	1.231
+++ openacs-4/packages/dotlrn/tcl/community-procs.tcl	24 Jul 2018 19:04:34 -0000	1.232
@@ -317,7 +317,7 @@
             foreach applet_key $default_applets_list {
                 if {[dotlrn_applet::applet_exists_p -applet_key $applet_key]} {
                     dotlrn_community::add_applet_to_community $community_id $applet_key
-                ns_log Notice "Added applet:::: $applet_key"
+                    ns_log Notice "Added applet: $applet_key"
                 }
             }
         }
@@ -829,7 +829,7 @@
         #
         #     util_memoize_flush_regexp  $user_id
         #
-        # was intended just to flush, just permissons or more. To
+        # was intended just to flush, just permissions or more. To
         # improve latencies, the following flush command should be
         # more precise (or removed)
         #
@@ -964,7 +964,7 @@
         #
         #     util_memoize_flush_regexp  $user_id
         #
-        # was intended just to flush, just permissons or more. To
+        # was intended just to flush, just permissions or more. To
         # improve latencies, the following flush command should be
         # more precise (or removed)
         #
@@ -1568,7 +1568,7 @@
     ad_proc -public needs_approval_p {
         {-community_id:required}
     } {
-        Returns 1 if the community's join policy is 'needs approval' aka "request approval".
+        Returns 1 if the community's join policy is 'needs approval' a.k.a. "request approval".
     } {
         return [db_string check_community_needs_approval {} -default 0]
     }
Index: openacs-4/packages/dotlrn/www/subcommunity-new.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/dotlrn/www/subcommunity-new.tcl,v
diff -u -r1.28 -r1.29
--- openacs-4/packages/dotlrn/www/subcommunity-new.tcl	29 Jun 2018 17:27:19 -0000	1.28
+++ openacs-4/packages/dotlrn/www/subcommunity-new.tcl	24 Jul 2018 19:04:34 -0000	1.29
@@ -15,7 +15,7 @@
 #
 
 ad_page_contract {
-    create a new subcommunity (aka subgroup)
+    create a new subcommunity (a.k.a. subgroup)
 
     @author arjun (arjun@openforce.net)
     @creation-date 2001-02-12
Index: openacs-4/packages/categories/tcl/category-xml-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/categories/tcl/category-xml-procs.tcl,v
diff -u -r1.4 -r1.5
--- openacs-4/packages/categories/tcl/category-xml-procs.tcl	7 Aug 2017 23:48:05 -0000	1.4
+++ openacs-4/packages/categories/tcl/category-xml-procs.tcl	24 Jul 2018 19:07:28 -0000	1.5
@@ -53,7 +53,7 @@
                 set description {}
             }
             if {$tree_id} {
-                # tree initialised, add translation
+                # tree initialized, add translation
                 category_tree::update \
                     -tree_id $tree_id \
                     -name $name \
Index: openacs-4/packages/categories/www/doc/o.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/categories/www/doc/o.adp,v
diff -u -r1.2 -r1.3
--- openacs-4/packages/categories/www/doc/o.adp	7 Aug 2017 23:48:05 -0000	1.2
+++ openacs-4/packages/categories/www/doc/o.adp	24 Jul 2018 19:07:28 -0000	1.3
@@ -161,14 +161,14 @@
 The appropriate tcl-procs look like the following:
 <pre>
 ad_proc -public apm_pageurl { object_id } {
-    Service Contract Proc to resolve a url for a package_id
+    Service Contract Proc to resolve a URL for a package_id
 } {
     return
 }
 
 namespace eval acs_user {
     ad_proc -public pageurl { object_id } {
-        Service Contract Proc to resolve a url for a user_id
+        Service Contract Proc to resolve a URL for a user_id
     } {
         return "shared/community-member?user_id=$object_id"
     }
Index: openacs-4/packages/general-comments/www/doc/design.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/general-comments/www/doc/design.adp,v
diff -u -r1.3 -r1.4
--- openacs-4/packages/general-comments/www/doc/design.adp	1 May 2018 08:49:04 -0000	1.3
+++ openacs-4/packages/general-comments/www/doc/design.adp	24 Jul 2018 19:07:28 -0000	1.4
@@ -91,7 +91,7 @@
 <span class="phrase">Note:</span> In the alpha release of
 <tt class="computeroutput">general-comments</tt>, the tcl
 procedures were defined within a namespace and encountered problems
-with the api browser not being able to display them properly. These
+with the API browser not being able to display them properly. These
 procedures have now been moved out of the namespace and the old
 ones are marked as deprecated. The final version will completely
 remove all traces of the namespace procedures.</p><p><span class="phrase">PL/SQL API</span></p><p>None. Uses PL/SQL functions provided by ACS Messaging.</p>
Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml,v
diff -u -r1.15 -r1.16
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml	17 May 2018 14:42:03 -0000	1.15
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/db-api.xml	24 Jul 2018 19:13:55 -0000	1.16
@@ -76,7 +76,7 @@
 	    transaction.  If you use something like db_foreach though, you need to 
             make sure that there are no calls in the code block which would take
             a second db handle since the transaction is only valid for 
-            one handle (thats why we build up a list of returned values and call 
+            one handle (that's why we build up a list of returned values and call 
             a second proc outside the db_foreach loop).
 	  </para>
 	</listitem>
Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml,v
diff -u -r1.58 -r1.59
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml	4 Jul 2018 10:20:41 -0000	1.58
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml	24 Jul 2018 19:13:55 -0000	1.59
@@ -715,10 +715,10 @@
 
 		if { $use_categories_p == 1 &amp;&amp; $category_id ne "" } {
 
-			set from_clause "category_object_map com, acs_named_objects nam"
+			set from_clause "category_object_map com, acs_named_objects ano"
 			set_where_clause "com.object_id = qa.entry_id and
-								nam.package_id = :package_id and
-								com.object_id = nam.object_id and
+								ano.package_id = :package_id and
+								com.object_id = ano.object_id and
 								com.category_id = :category_id"
 			
 			...
@@ -1573,7 +1573,7 @@
     file so that new installation will have the new data model.</para>
 
     <para>Next, check what version your package is currently at. For
-    example, it may be at version 1.0b1. Create a file in 
+    example, it may be at version 1.0b1. Create a file in
     sql/postgres/upgrade called packagename-1.0b1-1.0b2.sql and put
     the SQL code that will update the data model. For example, if you
     add in a column, you would have an alter table add column
Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml,v
diff -u -r1.35 -r1.36
--- openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml	25 Apr 2018 08:38:28 -0000	1.35
+++ openacs-4/packages/acs-core-docs/www/xml/install-guide/other-software.xml	24 Jul 2018 19:13:55 -0000	1.36
@@ -695,7 +695,7 @@
         <listitem id="configure-ns_ldap-bind">
           <formalpara>
             <title>Configure ns_ldap for use with LDAP bind</title>
-          <para>LDAP authentication usually is done by trying to bind (aka. login) a user with the LDAP server. The password of the user is not stored in any field of the LDAP server, but kept internally. The latest version of ns_ldap supports this method with the <emphasis>ns_ldap bind</emphasis> command. All you have to do to enable this is to configure auth_ldap to make use of the BIND authentication instead. Alternatively you can write a small script on how to calculate the username out of the given input (e.g. if the OpenACS username is malte.fb03.tu, the LDAP request can be translated into "ou=malte,ou=fb03,o=tu" (this example is encoded in auth_ldap and you just have to comment it out to make use of it).</para>
+          <para>LDAP authentication usually is done by trying to bind (a.k.a. login) a user with the LDAP server. The password of the user is not stored in any field of the LDAP server, but kept internally. The latest version of ns_ldap supports this method with the <emphasis>ns_ldap bind</emphasis> command. All you have to do to enable this is to configure auth_ldap to make use of the BIND authentication instead. Alternatively you can write a small script on how to calculate the username out of the given input (e.g. if the OpenACS username is malte.fb03.tu, the LDAP request can be translated into "ou=malte,ou=fb03,o=tu" (this example is encoded in auth_ldap and you just have to comment it out to make use of it).</para>
           </formalpara>
         </listitem>
       </orderedlist>