Index: openacs-4/packages/news/www/doc/design.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/news/www/doc/design.adp,v
diff -u -r1.7.2.1 -r1.7.2.2
--- openacs-4/packages/news/www/doc/design.adp	11 Mar 2019 08:43:27 -0000	1.7.2.1
+++ openacs-4/packages/news/www/doc/design.adp	24 Nov 2019 11:23:28 -0000	1.7.2.2
@@ -53,7 +53,7 @@
 </ul>
 
 as input. Publishers may wish to provide their own templates,
-however even more flexibility can be introduced by supplying the
+however, even more flexibility can be introduced by supplying the
 news body in HTML format. If someone submits a news body with
 inconsistent HTML tags, the News application attempts to close
 these tags in the preview page.
Index: openacs-4/packages/news/www/doc/design.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/news/www/doc/design.html,v
diff -u -r1.9.2.1 -r1.9.2.2
--- openacs-4/packages/news/www/doc/design.html	9 Aug 2019 20:19:04 -0000	1.9.2.1
+++ openacs-4/packages/news/www/doc/design.html	24 Nov 2019 11:23:28 -0000	1.9.2.2
@@ -70,7 +70,7 @@
     <li><pre>@creator_link@</pre>
   </ul>
 as input.  Publishers may wish to provide their own templates, 
-however even more flexibility can be introduced by supplying 
+however, even more flexibility can be introduced by supplying 
 the news body in HTML format. 
 If someone submits a news body with inconsistent HTML tags, the News application
 attempts to close these tags in the preview page.
Index: openacs-4/packages/news/www/doc/requirements.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/news/www/doc/requirements.adp,v
diff -u -r1.3.2.1 -r1.3.2.2
--- openacs-4/packages/news/www/doc/requirements.adp	9 Aug 2019 20:19:04 -0000	1.3.2.1
+++ openacs-4/packages/news/www/doc/requirements.adp	24 Nov 2019 11:23:28 -0000	1.3.2.2
@@ -18,7 +18,7 @@
 items to other members is one of the ways in which online
 communities best realize this goal. The News application allows
 community members to do just this. Posted news items can be
-associated with community member comments as in a forum, however
+associated with community member comments as in a forum, however,
 the primary intention of the News application is simply to give
 members access to community related news items. News items are
 listed by date, and when news items are no longer current, they are
Index: openacs-4/packages/news/www/doc/requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/news/www/doc/requirements.html,v
diff -u -r1.2.2.1 -r1.2.2.2
--- openacs-4/packages/news/www/doc/requirements.html	9 Aug 2019 20:19:04 -0000	1.2.2.1
+++ openacs-4/packages/news/www/doc/requirements.html	24 Nov 2019 11:23:28 -0000	1.2.2.2
@@ -22,7 +22,7 @@
 the dissemination of news items to other members is one of the ways in
 which online communities best realize this goal.  The News application
 allows community members to do just this.  Posted news items can be
-associated with community member comments as in a forum, however the
+associated with community member comments as in a forum, however, the
 primary intention of the News application is simply to give members
 access to community related news items.  News items are listed by
 date, and when news items are no longer current, they are automatically
Index: openacs-4/packages/static-portlet/tcl/static-portal-content-procs.tcl
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/static-portlet/tcl/static-portal-content-procs.tcl,v
diff -u -r1.22.2.1 -r1.22.2.2
--- openacs-4/packages/static-portlet/tcl/static-portal-content-procs.tcl	14 Feb 2019 16:15:01 -0000	1.22.2.1
+++ openacs-4/packages/static-portlet/tcl/static-portal-content-procs.tcl	24 Nov 2019 11:26:49 -0000	1.22.2.2
@@ -54,7 +54,7 @@
             # being called from add_applet_to_community. That means that
             # we have a static portlet copied from our template,
             # but the pointer to the _content_ of the portlet still
-            # _template's content_. Therefore we need to clone the
+            # _template's content_. Therefore, we need to clone the
             # _template's content_ and update the pointer
             # (2) that there's only one static portlet on the page.
 
@@ -97,7 +97,7 @@
         db_transaction {
             # Generate the element, don't use add_element_parameters here,
             # since it doesn't do the right thing for multiple elements with
-            # the same datasource on a page. so we just use the more low level
+            # the same datasource on a page. Therefore, we just use the more low-level
             # portal::add_element
             set element_id [portal::add_element \
                     -portal_id $portal_id \