Index: openacs-4/packages/acs-core-docs/www/groups-requirements.html
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/groups-requirements.html,v
diff -u -r1.37.2.1 -r1.37.2.2
--- openacs-4/packages/acs-core-docs/www/groups-requirements.html	2 Mar 2019 19:30:04 -0000	1.37.2.1
+++ openacs-4/packages/acs-core-docs/www/groups-requirements.html	3 Sep 2021 09:15:00 -0000	1.37.2.2
@@ -88,7 +88,7 @@
             an associated name.</p></dd><dt><span class="term"><span class="strong"><strong>40.0 Users</strong></span>
 
         </span></dt><dd><p>A <span class="strong"><strong>user</strong></span> is a person who has registered with an OpenACS site. A
-            user may have additional attributes, such as a screen name.</p><p>The data model should enforce these constraints:</p><p><span class="strong"><strong>40.10</strong></span> A user must have a non-empty email address.</p><p><span class="strong"><strong>40.20</strong></span> Two different users may not have the same email
+            user may have additional attributes, such as a screen name.</p><p>The data model should enforce these constraints:</p><p><span class="strong"><strong>40.10</strong></span> A user must have a nonempty email address.</p><p><span class="strong"><strong>40.20</strong></span> Two different users may not have the same email
             address on a single OpenACS installation; i.e., an email address identifies a
             single user on the system.</p><p><span class="strong"><strong>40.30</strong></span> A user may have multiple email addresses; for
             example, two or more email addresses may identify a single user.</p><p><span class="strong"><strong>40.40</strong></span> A user must have password field which can be