Index: openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml,v
diff -u -r1.13.2.2 -r1.13.2.3
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml	5 Jan 2021 17:33:40 -0000	1.13.2.2
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/packages.xml	2 Sep 2021 16:56:01 -0000	1.13.2.3
@@ -406,7 +406,7 @@
       administrator can create as many instances of the package as she
       likes, and map these instances to any URL in the site that she
       wants. If packages are analogous to executable programs in an
-      operating system, then package instances are analgous to multiple
+      operating system, then package instances are analogous to multiple
       running copies of a single program. Each instance can be independently
       administered and each instance maintains its own set of application
       parameters and options.
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.60.2.8 -r1.60.2.9
--- openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml	8 Apr 2021 15:44:06 -0000	1.60.2.8
+++ openacs-4/packages/acs-core-docs/www/xml/developers-guide/tutorial-advanced.xml	2 Sep 2021 16:56:01 -0000	1.60.2.9
@@ -433,7 +433,7 @@
 Now that you have the first admin page it would be nice to have a link to it
 somewhere in the system so that admins don't have to type in the
 <computeroutput>/admin</computeroutput> every time they need to reach it.  You
-could put a static link to the toplevel
+could put a static link to the top-level
 <computeroutput>index.adp</computeroutput> but that might be distracting for
 people who are not admins.  Besides, some people consider it impolite to first
 offer a link and then display a nasty "You don&#39;t have permission to access this
Index: openacs-4/packages/acs-core-docs/www/xml/engineering-standards/filenaming.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/engineering-standards/filenaming.xml,v
diff -u -r1.8.2.1 -r1.8.2.2
--- openacs-4/packages/acs-core-docs/www/xml/engineering-standards/filenaming.xml	16 Dec 2019 17:14:38 -0000	1.8.2.1
+++ openacs-4/packages/acs-core-docs/www/xml/engineering-standards/filenaming.xml	2 Sep 2021 16:56:02 -0000	1.8.2.2
@@ -21,7 +21,7 @@
 <title>File Nomenclature</title>
 
 <para>
-Usually we organize our files so that they mainly serve one of the following three purposes:
+Usually, we organize our files so that they mainly serve one of the following three purposes:
 </para>
 
 <itemizedlist>
Index: openacs-4/packages/acs-core-docs/www/xml/engineering-standards/psgml-mode.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/engineering-standards/psgml-mode.xml,v
diff -u -r1.9 -r1.9.2.1
--- openacs-4/packages/acs-core-docs/www/xml/engineering-standards/psgml-mode.xml	7 Aug 2017 23:47:54 -0000	1.9
+++ openacs-4/packages/acs-core-docs/www/xml/engineering-standards/psgml-mode.xml	2 Sep 2021 16:56:02 -0000	1.9.2.1
@@ -146,7 +146,7 @@
 
 
 <para>All SGML and XML documents that should conform to a DTD have to declare a
-doctype. For the docbook XML, all your <computeroutput>.xml</computeroutput> files whould start with
+doctype. For the docbook XML, all your <computeroutput>.xml</computeroutput> files would start with
 the line</para>
 
 <programlisting>
Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml,v
diff -u -r1.33.2.1 -r1.33.2.2
--- openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml	2 Jul 2020 08:39:25 -0000	1.33.2.1
+++ openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml	2 Sep 2021 16:56:02 -0000	1.33.2.2
@@ -414,7 +414,7 @@
 [$OPENACS_SERVICE_NAME etc]$ <userinput>emacs config.tcl</userinput>
 </screen>
             <para>
-	  You can continue without changing any values in the file.  However, if you don&#39;t change <computeroutput>address</computeroutput> to match the computer&#39;s ip address, you won&#39;t be able to browse to your server from other machines.
+	  You can continue without changing any values in the file.  However, if you don&#39;t change <computeroutput>address</computeroutput> to match the computer&#39;s IP address, you won&#39;t be able to browse to your server from other machines.
 	</para>
             
             <itemizedlist>
Index: openacs-4/packages/acs-core-docs/www/xml/kernel/apm-design.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/apm-design.xml,v
diff -u -r1.14.2.1 -r1.14.2.2
--- openacs-4/packages/acs-core-docs/www/xml/kernel/apm-design.xml	2 Jul 2020 08:39:25 -0000	1.14.2.1
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/apm-design.xml	2 Sep 2021 16:56:02 -0000	1.14.2.2
@@ -57,7 +57,7 @@
 <title>Introduction</title>
 
 <para>
-In general terms, a <emphasis role="strong">package</emphasis> is a unit of software that
+In general, a <emphasis role="strong">package</emphasis> is a unit of software that
 serves a single well-defined purpose. That purpose may be to provide a
 service directly to one or more classes of end-user, (e.g., discussion forums
 and file storage for community members, user profiling tools for the site
Index: openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml,v
diff -u -r1.11.2.1 -r1.11.2.2
--- openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml	2 Jul 2020 08:39:25 -0000	1.11.2.1
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/apm-requirements.xml	2 Sep 2021 16:56:02 -0000	1.11.2.2
@@ -62,7 +62,7 @@
 and easily distribute their OpenACS components in a standardized manner to other
 OpenACS sites.</para>
 
-<para>In general terms, a package is a unit of software that serves a single
+<para>In general, a package is a unit of software that serves a single
 well-defined purpose. The OpenACS Package Manager (APM) provides a mechanism for
 packaging, installing, and configuring OpenACS software in a consistent,
 user-friendly, and subsite-aware manner.</para>
Index: openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml,v
diff -u -r1.11.2.2 -r1.11.2.3
--- openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml	2 Jul 2020 08:39:25 -0000	1.11.2.2
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/object-system-design.xml	2 Sep 2021 16:56:02 -0000	1.11.2.3
@@ -345,7 +345,7 @@
 <para>Object subtypes provide a way to factor the data model while still keeping
 track of the fact that each member of a subtype (i.e. for each row in the
 subtype&#39;s table), is also a member of the parent type (i.e. there is a
-corresponding row in the parent type table). Therefore, applications an use
+corresponding row in the parent type table). Therefore, applications use
 this mechanism without worrying about this bookkeeping themselves, and we
 avoid having applications pollute the core data model with their specific
 information.</para>
Index: openacs-4/packages/acs-core-docs/www/xml/kernel/security-design.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/security-design.xml,v
diff -u -r1.7.16.2 -r1.7.16.3
--- openacs-4/packages/acs-core-docs/www/xml/kernel/security-design.xml	2 Jul 2020 08:39:25 -0000	1.7.16.2
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/security-design.xml	2 Sep 2021 16:56:03 -0000	1.7.16.3
@@ -95,7 +95,7 @@
 over SSL when performing some action that requires secure authentication.</para>
 
 <para>Although this makes the site less user friendly, this design significantly
-increases the security of the system because this insures that the
+increases the security of the system because this ensures that the
 authentication tokens presented to a secure section of the web site were not
 sniffed. The system is not entirely secure, since the actual authentication
 password can be sniffed from the system, after which the sniffer can apply
@@ -395,7 +395,7 @@
 <computeroutput>sec_setup_session</computeroutput>, which is called either to
 create a new session from <computeroutput>sec_handler</computeroutput> or from
 <computeroutput>ad_user_login</computeroutput> when there is a change in
-authorization level. The session management code must do two things: insure that
+authorization level. The session management code must do two things: ensure that
 session-level data does not float between users, and update the users table
 which has columns for <computeroutput>n_sessions</computeroutput>,
 <computeroutput>last_visit</computeroutput>, and
@@ -809,7 +809,7 @@
 <title>Cookieless Sessions</title>
 
 <para>Two trends drive the requirement for removing cookie dependence. WAP
-browsers that do not have cookies, and publc perceptions of cookies as an
+browsers that do not have cookies, and public perceptions of cookies as an
 invasion of privacy. The rely on the cookies mechanism in HTTP to distinguish
 one request from the next, and we trust it to force requests from the same
 client to carry the same cookie headers. The same thing can be accomplished by
Index: openacs-4/packages/acs-core-docs/www/xml/kernel/security-notes.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/security-notes.xml,v
diff -u -r1.7 -r1.7.4.1
--- openacs-4/packages/acs-core-docs/www/xml/kernel/security-notes.xml	27 Oct 2014 16:39:32 -0000	1.7
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/security-notes.xml	2 Sep 2021 16:56:03 -0000	1.7.4.1
@@ -25,7 +25,7 @@
 <para>
 
 If a user switches to HTTPS after logging into the system via HTTP, the user
-must obtain a secure token. To insure security, the <emphasis>only way</emphasis> to
+must obtain a secure token. To ensure security, the <emphasis>only way</emphasis> to
 obtain a secure token in the security system is to authenticate yourself via
 password over an HTTPS connection. Thus, users may need to log on again to a
 system when switching from HTTP to HTTPS. Note that logging on to a system