Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml,v
diff -u -N -r1.17 -r1.18
--- openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml	11 Dec 2010 23:36:32 -0000	1.17
+++ openacs-4/packages/acs-core-docs/www/xml/install-guide/recovery.xml	7 Aug 2017 23:47:55 -0000	1.18
@@ -164,11 +164,11 @@
   . exporting pre-schema procedural objects and actions
   . exporting foreign function library names for user SERVICE_NAME 
   . exporting object type definitions for user SERVICE_NAME 
-  About to export SERVICE_NAME's objects ...
+  About to export SERVICE_NAME's objects ...
   . exporting database links
   . exporting sequence numbers
   . exporting cluster definitions
-  . about to export SERVICE_NAME's tables via Conventional Path ...
+  . about to export SERVICE_NAME's tables via Conventional Path ...
   . exporting synonyms
   . exporting views
   . exporting stored procedures
@@ -214,7 +214,7 @@
           <para>Back up all of the files in the service, including the
           database backup file but excluding the auto-generated
           <filename>supervise</filename> directory, which is
-          unneccesary and has complicated permissions.  </para>
+          unnecessary and has complicated permissions.  </para>
         </formalpara>
         <para>In the tar command,</para>
         <itemizedlist>
@@ -234,7 +234,7 @@
           <listitem>
             <para>The <computeroutput>--exclude</computeroutput> clauses skips some daemontools files that
             are owned by root and thus cannot be backed up by the
-            service owner.  These files are autogenerated and we don't
+            service owner.  These files are autogenerated and we don&#39;t
             break anything by omitting them.</para>
           </listitem>
           <listitem>
@@ -258,7 +258,7 @@
       <listitem>
         <formalpara>
           <title>Suffer a catastrophic failure on your production system</title>
-          <para>(We'll simulate this step)</para>
+          <para>(We&#39;ll simulate this step)</para>
         </formalpara>
         <screen>[root root]# <userinput>svc -d /service/$OPENACS_SERVICE_NAME</userinput>
 [root root]# <userinput>mv /var/lib/aolserver/$OPENACS_SERVICE_NAME/ /var/lib/aolserver/$OPENACS_SERVICE_NAME.lost</userinput>
@@ -373,15 +373,15 @@
       </listitem>
       <listitem>
         <para>
-        Set this file to run automatically by adding a line to root's crontab. (Typically, with <computeroutput>export EDITOR=emacs; crontab -e</computeroutput>.)  This example runs the backup script at 1:30 am every day.</para>
+        Set this file to run automatically by adding a line to root&#39;s crontab. (Typically, with <computeroutput>export EDITOR=emacs; crontab -e</computeroutput>.)  This example runs the backup script at 1:30 am every day.</para>
         <programlisting>30 1 * * *        sh /var/lib/aolserver/<replaceable>$OPENACS_SERVICE_NAME</replaceable>/etc/backup.sh</programlisting>
       </listitem>
     </orderedlist>
 
   </sect1>
   <sect1 id="backups-with-cvs">
     <title>Using CVS for backup-recovery</title>
-    <para>CVS-only backup is often appropriate for development sites.  If you are already using CVS and your data is not important, you probably don't
+    <para>CVS-only backup is often appropriate for development sites.  If you are already using CVS and your data is not important, you probably don&#39;t
       need to do anything to back up your files.  Just make
       sure that your current work is checked into the system.
       You can then roll back based on date - note the