Index: openacs-4/packages/acs-core-docs/www/openacs.adp
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/openacs.adp,v
diff -u -N -r1.1.2.16 -r1.1.2.17
--- openacs-4/packages/acs-core-docs/www/openacs.adp	6 Jan 2017 09:18:42 -0000	1.1.2.16
+++ openacs-4/packages/acs-core-docs/www/openacs.adp	2 Jun 2017 11:12:57 -0000	1.1.2.17
@@ -304,7 +304,7 @@
 automatically authenticates as the postgres user of the same name,
 if one exists. We currently use postgres "super-users"
 for everything, which means that anyone with access to any of the
-openacs system accounts on a machine has full access to all
+OpenACS system accounts on a machine has full access to all
 postgresql databases on that machine.</p><pre class="screen">
 [root root]# <strong class="userinput"><code>su - postgres</code></strong>
 [postgres pgsql]$ <strong class="userinput"><code>createuser -a -d <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>
@@ -337,7 +337,7 @@
 automate vacuuming is to edit the cron file for the database user.
 Recommended: <code class="computeroutput">VACUUM ANALYZE</code>
 every hour and <code class="computeroutput">VACUUM FULL
-ANALYZE</code> every day.</p><a class="indexterm" name="idp140529124103840" id="idp140529124103840"></a><pre class="screen">
+ANALYZE</code> every day.</p><a class="indexterm" name="idp140186673868376" id="idp140186673868376"></a><pre class="screen">
 [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ <strong class="userinput"><code>export EDITOR=emacs;crontab -e</code></strong>
 </pre><p>Add these lines to the file. The vacuum command cleans up
 temporary structures within a PostGreSQL database, and can improve
@@ -371,7 +371,7 @@
 specific port, e.g. port 80. In order for OpenACS to work, you need
 to configure a virtual server. The Reference Platform uses a
 configuration file included in the OpenACS tarball, <code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/etc/config.tcl</code>.
-Open it in an editor to adjust the parameters.</p><a class="indexterm" name="idp140529124117824" id="idp140529124117824"></a><pre class="screen">
+Open it in an editor to adjust the parameters.</p><a class="indexterm" name="idp140186673882360" id="idp140186673882360"></a><pre class="screen">
 [root root]# <strong class="userinput"><code>su - <span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>
 </code></strong>
 [$OPENACS_SERVICE_NAME $OPENACS_SERVICE_NAME]$ <strong class="userinput"><code>cd /var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/etc</code></strong>
@@ -465,7 +465,7 @@
 (<code class="computeroutput">/var/lib/aolserver/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>/log/<span class="replaceable"><span class="replaceable">$OPENACS_SERVICE_NAME</span></span>-error.log</code>)
 to make sure the service is starting without any problems. The most
 common errors here are trying to start a port 80 server while not
-root, failing to connect because of a firewall, and aolserver
+root, failing to connect because of a firewall, and AOLserver
 failing to start due to permissions errors or missing files. If you
 need to make changes, don&#39;t forget to kill any running servers
 with <strong class="userinput"><code>killall
@@ -611,8 +611,8 @@
 recovery</a> procedure.</p></li><li class="listitem"><p>Set up <a class="xref" href="uptime" title="External uptime validation">the section called
 &ldquo;External uptime
 validation&rdquo;</a>.</p></li>
-</ul></div><div class="cvstag">($&zwnj;Id: openacs.xml,v 1.31.14.2 2016/07/05
-16:42:42 gustafn Exp $)</div>
+</ul></div><div class="cvstag">($&zwnj;Id: openacs.xml,v 1.31.14.3 2017/04/22
+17:18:48 gustafn Exp $)</div>
 </div>
 </div>
 <include src="/packages/acs-core-docs/lib/navfooter"