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.5 -r1.6
--- openacs-4/packages/acs-core-docs/www/xml/kernel/apm-design.xml	20 Aug 2003 16:20:19 -0000	1.5
+++ openacs-4/packages/acs-core-docs/www/xml/kernel/apm-design.xml	11 Dec 2003 21:39:49 -0000	1.6
@@ -4,12 +4,12 @@
 <!ENTITY % myvars SYSTEM "../variables.ent">
 %myvars;
 ]>
-<sect1 id="apm-design" xreflabel="OpenACS &version; Package Manager Design">
-<title>OpenACS &version; Package Manager Design</title>
+<sect1 id="apm-design" xreflabel="Package Manager Design">
+<title>Package Manager Design</title>
 
 
 <authorblurb>
-by <ulink url="mailto:bquinn@arsdigita.com">Bryan Quinn</ulink> 
+<para>By Bryan Quinn</para>
 </authorblurb>
 
 
@@ -71,7 +71,7 @@
 <listitem><para><emphasis role="strong">OpenACS Applications:</emphasis> a &quot;program or group of programs
 designed for end users&quot; (the <ulink url="http://www.pcwebopaedia.com/TERM/a/application.html">Webopedia
 definition</ulink>); also known as <emphasis>modules</emphasis>, for historical reasons.
-Examples of applications include <ulink url="/doc/bboard">Bboard</ulink> and <ulink url="/doc/news">News</ulink>. 
+Examples of applications include <ulink url="/doc/forums">Forums</ulink> and <ulink url="/doc/news">News</ulink>. 
 
 
 </para></listitem>
@@ -91,11 +91,11 @@
 
 <para>This architecture supports the growth of collaborative commerce. For
 example, Jane User starts a forum focusing on the merits of View Cameras by
-creating an instance of the Bboard application for her personal subsite on an
+creating an instance of the Forum application for her personal subsite on an
 OpenACS Installation. Jack User discovers Jane&#39;s forum and includes a link to
 it in his subsite. As interest in Jane&#39;s forum grows, she creates a
 subsite specializing in providing information about View cameras. This
-subsite now includes several package instances beyond Bboard; it could
+subsite now includes several package instances beyond Forum; it could
 potentially include its own Ecommerce capabilities (ala <ulink url="http://shopping.yahoo.com">Yahoo! Shopping</ulink>). This could include a
 knowledge management application that allows users to spread expertise about
 view cameras and a portal application that links to reliable camera models
@@ -193,9 +193,9 @@
 
 <para>Consistent use of the APM format and tools will go a long way toward
 solving the maintainability problems listed above. Moreover, APM is the
-substrate that will enable us to soon establish a central package repository,
-where both ArsDigita and third-party developers will be able publish their
-packages for other ACS users to download and install.</para>
+substrate that will enable us to establish a central package repository,
+where developers will be able publish their
+packages for other OpenACS users to download and install.</para>
 
 <para>For a simple illustration of the difference between ACS without APM
 (pre-3.3) and ACS with APM (3.3 and beyond), consider a hypothetical ACS
@@ -209,7 +209,7 @@
     <imagedata fileref="images/acs-without-apm-vs-with-apm.png" format="PNG" align="center"/>
   </imageobject>
   <textobject>
-    <emphasis role="strong">OpenACS without APM vs. with APM</emphasis>
+    <para><emphasis role="strong">OpenACS without APM vs. with APM</emphasis></para>
   </textobject>
 </mediaobject>
 
@@ -879,7 +879,7 @@
 <para>The central piece of the data model is the <computeroutput>apm_package_types</computeroutput>
 table where each package is registered. When a new application or service is
 installed on an OpenACS instance, a corresponding row in this table is inserted
-with information about the type of package, e.g. if the <ulink url="/doc/bboard">bboard package</ulink> is installed on your OpenACS server, a row
+with information about the type of package, e.g. if the <ulink url="/doc/forum">forum package</ulink> is installed on your OpenACS server, a row
 in <computeroutput>apm_package_types</computeroutput> will be created, noting that it&#39;s an
 application package type.</para>
 
@@ -1077,7 +1077,7 @@
 
 <row>
 <entry>1.0</entry>
-<entry>Edited for OpenACS &version; Beta release</entry>
+<entry>Edited for OpenACS 4.5 Beta release</entry>
 <entry>03/02/2002</entry>
 <entry>Roberto Mello</entry>
 </row>