Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/overview.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/overview.xml,v
diff -u -N -r1.29 -r1.30
--- openacs-4/packages/acs-core-docs/www/xml/install-guide/overview.xml	27 Oct 2014 16:39:31 -0000	1.29
+++ openacs-4/packages/acs-core-docs/www/xml/install-guide/overview.xml	7 Aug 2017 23:47:55 -0000	1.30
@@ -8,6 +8,13 @@
 <sect1 id="install-steps">
   <title>Basic Steps</title>
 
+  <para>Most of the documentation in this section is kept as a
+    reference. More up-to-date documentation is in the <ulink
+    url="http://openacs.org/xowiki/openacs-system-install">install
+    sections in the Wiki</ulink>.
+  </para>
+
+  
   <para>
     The basic steps for installing OpenACS are:
   </para>
@@ -200,8 +207,8 @@
     </table>
 
     <para>
-      None of these locations are set in stone - they're simply
-      the values that we've chosen.  The values that you'll
+      None of these locations are set in stone - they&#39;re simply
+      the values that we&#39;ve chosen.  The values that you&#39;ll
       probably want to change, such as service name, are
       <replaceable>marked like this</replaceable>.  The other
       values we recommend you leave unchanged unless you have a
@@ -223,8 +230,8 @@
     <title>Getting Help during installation</title>
 
     <para>
-      We'll do our best to assure that following our instructions will get
-      you to the promised land. If something goes wrong, don't
+      We&#39;ll do our best to assure that following our instructions will get
+      you to the promised land. If something goes wrong, don&#39;t
       panic. There are plenty of ways to get help. Here are some tips:
     </para>
 
@@ -241,20 +248,20 @@
 
       <listitem>
         <para>
-          We'll point out where the error logs for the various pieces of
-          software are. Output from those logs will help us help you. Don't
+          We&#39;ll point out where the error logs for the various pieces of
+          software are. Output from those logs will help us help you. Don&#39;t
           worry if you feel overwhelmed by all the information in the error
-          logs. Over time, you'll find that they make more and more
-          sense. Soon, you'll actually look forward to errors so that you
+          logs. Over time, you&#39;ll find that they make more and more
+          sense. Soon, you&#39;ll actually look forward to errors so that you
           can run to the log and diagnose the problem. 
         </para>
       </listitem>
 
       <listitem>
         <para>
           Search the <ulink url="http://openacs.org/forums/">forums at
-            openacs.org</ulink> - you'll often find many people who have
-          struggled through the same spot that you're in.
+            openacs.org</ulink> - you&#39;ll often find many people who have
+          struggled through the same spot that you&#39;re in.
         </para>
       </listitem>
 
@@ -269,7 +276,7 @@
       <listitem>
         <para>
           Ask questions at the irc channel on <ulink url="http://freenode.net">freenode.net</ulink>
-          (#openacs). They're knowledgeable and quite friendly
+          (#openacs). They&#39;re knowledgeable and quite friendly
           if you can keep them on topic.
         </para>
       </listitem>
@@ -278,10 +285,10 @@
         <para>
           Post a question on the <ulink
             url="http://openacs.org/forums/">forums</ulink>. Make sure
-          you've done a search first. When you do post, be sure to include
+          you&#39;ve done a search first. When you do post, be sure to include
           your setup information (OS, etc) as well as the exact commands
           that are failing with the accompanying error.  If
-          there's a SQL error in the Tcl error or in the log,
+          there&#39;s a SQL error in the Tcl error or in the log,
           post that too.
         </para>
       </listitem>