Index: openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml
===================================================================
RCS file: /usr/local/cvsroot/openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml,v
diff -u -r1.31.14.1 -r1.31.14.2
--- openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml	23 Jun 2016 08:32:46 -0000	1.31.14.1
+++ openacs-4/packages/acs-core-docs/www/xml/install-guide/openacs.xml	5 Jul 2016 16:42:42 -0000	1.31.14.2
@@ -628,7 +628,16 @@
 
   <sect2 id="install-from-cvs">
     <title>Installation Option 3: Install from CVS</title>
-    <para>If you want to track fresh code developments inbetween releases, or you are an OpenACS core developer, you may want to install from CVS.  This is identical to Option 2 except that you get the files from CVS instead of the tarball: <ulink url="http://openacs.org/4/checkout">CVS Checkout Instructions</ulink>.  So, instead of <computeroutput><userinput>tar xzf /var/tmp/&tarballpath;.tgz</userinput></computeroutput>, <computeroutput><userinput>cvs -z3 -d :pserver:anonymous@openacs.org:/cvsroot co acs-core</userinput></computeroutput>.</para>
+    <para>If you want to track fresh code developments between
+    releases, or you are an OpenACS core developer, you may want to
+    install from CVS.  This is identical to Option 2 except that you
+    get the files from CVS instead of the tarball: <ulink
+    url="/xowiki/Get_the_Code">CVS Checkout Instructions</ulink>.  In short,
+    instead of <computeroutput><userinput>tar xzf
+    /var/tmp/&tarballpath;.tgz</userinput></computeroutput>, use
+    <computeroutput><userinput>cvs -z3 -d
+    :pserver:anonymous@openacs.org:/cvsroot co
+    acs-core</userinput></computeroutput> to obtain an ACS core installation.</para>
   </sect2>
   <sect2 id="install-next-steps">
     <title>Next Steps</title>