Index: openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-requirements.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-requirements.xml,v
diff -u -r1.4 -r1.4.2.1
--- openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-requirements.xml	20 Aug 2003 16:20:19 -0000	1.4
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/permissions-requirements.xml	17 Nov 2003 16:38:10 -0000	1.4.2.1
@@ -8,7 +8,7 @@
 <title>OpenACS 4 Permissions Requirements</title>
 
 <authorblurb>
-by <ulink url="mailto:jmp@arsdigita.com">John McClary Prevost</ulink> 
+by John McClary Prevost
 </authorblurb>
 
 <sect2 id="permissions-requirements-intro">
@@ -104,7 +104,7 @@
 
 
 <para>Examples of the essential question addressed by the Permissions system:
-Can jane@attacker.com delete the web security bboard? Can the Boston office
+Can jane@attacker.com delete the web security forum? Can the Boston office
 (a party) within the VirtuaCorp intranet/website create its own news
 instance?</para>
 
@@ -167,7 +167,7 @@
 <para>Privileges must be designed with appropriate scope for a given OpenACS
 package. Some privileges are of general utility (e.g. &quot;read&quot; and
 &quot;write&quot;). Others are of more limited use (e.g. &quot;moderate&quot;
-- applies mainly to a package like bboard, where many users are contributing
+- applies mainly to a package like forum, where many users are contributing
 content simultaneously). A package defining its own privileges should do so
 with moderation, being careful not to overload a privilege like
 &quot;read&quot; to mean too many things.</para>
@@ -192,8 +192,8 @@
 <blockquote><para><emphasis role="strong">70.10 Context</emphasis></para>
 
 <para>There must be a method for objects to receive default access control from
-some context. For example, if you do not have read access to a bboard, you
-should not have read access to a message in that bboard.</para>
+some context. For example, if you do not have read access to a forum, you
+should not have read access to a message in that forum.</para>
 
 </blockquote><blockquote><para><emphasis role="strong">70.20 Overriding</emphasis></para>
 
@@ -205,7 +205,7 @@
 
 <para>It must be possible to allow a party more access to some target than they
 would get by default. (For example, a user does not have the right to edit
-any message on a bboard. But a user does possibly have the right to edit
+any message on a forum. But a user does possibly have the right to edit
 their own messages.)</para>
 
 </blockquote><blockquote><para><emphasis role="strong">70.20.20 Negative Overriding</emphasis></para>