--- doc/build/sles9_install.frag	2008/12/10 19:57:29	1.3
+++ doc/build/sles9_install.frag	2013/12/13 18:28:42	1.6
@@ -36,7 +36,7 @@ The installation process takes the follo
 
 <h2>Obtain SuSE Linux Enterprise Server 9</h2>
 <p>
-SuSE ISO files can be obtained from the Novell site: <a href="http://www.novell.com/products/linuxenterpriseserver/">http://www.novell.com/products/linuxenterpriseserver/</a>.  
+SuSE ISO files can be obtained from the Novell site: <a href="http://www.suse.com/products/server/">http://www.suse.com/products/server/</a>.  
 </p> 
 
 <h2>Determine Network Settings</h2>
@@ -58,8 +58,8 @@ DHCP is <em>not</em> supported.
 Installing SuSE Linux Enterprise Server is quite easy if you've installed Linux products
 before.  Some documentation is available from 
 <a href="http://www.novell.com/documentation/sles9/">
-http://www.novell.com/documentation/sles9/</a>.<br /><br />
-Most of the subsequent installation screens are self explanatory.
+http://www.novell.com/documentation/sles9/</a>.<br><br>
+Most of the installation screens are self explanatory.
 There are a few steps that require comment and are dealt with below.
 </p>
 <dl style="list-style:square outside none">
@@ -92,17 +92,18 @@ There are a few steps that require comme
    </dd>
    <dt>Online update</dt>
    <dd>Indicate "Yes" when prompted to "run online update now?"</dd>
-   </dt>
 </dl>
 <p>
 Finish installing your server, read the "readme", reboot and log in as root.
 </p>
+
 <h2>Configure Firewall Settings</h2>
-<p>After reboot you should start yast, and select Security and Users -> Firewall. At step 2 include the following services: HTTP, HTTP with SSL, and Secure Shell.  Use the "Expert..." option to add additional TCP services on ports 5663 and 8080.    
+<p>After reboot you should start yast, and select Security and Users -> Firewall. At step 2 include the following services: HTTP, HTTP with SSL, and Secure Shell.  
 </p>
+
 <h2>Change software sources for your system</h2>
 <p>
-You will use yast to import packages required for LON-CAPA.<br />
+You will use yast to import packages required for LON-CAPA.<br>
 Execute:
 </p>
 <pre>
@@ -113,6 +114,7 @@ Select "Change Source of Installation".
 </p>
 <h3>Add an additional installation source</h3>
 <p>Add the LON-CAPA SLES 9 repository as an additional installation source, so software installation in yast will have access to two repositories - a SuSE/Novell source (for packages included for the standard distribution) and the LON-CAPA repository (for extra packages needed to run LON-CAPA). For the LON-CAPA source you will use:
+</p>
 <dl style="list-style:square outside none">
 <dd>Protocol</dd>
 <dt>HTTP</dt>
@@ -123,11 +125,14 @@ Select "Change Source of Installation".
 <dd>Authentication</dd>
 <dt>Anonymous</dt>
 </dl>
+<p>
 After saving this configuration information for the LON-CAPA repository, choose "Edit", then "Refresh" the quit yast.  
 </p>
+
 <h2>Update pwdutils package</h2>
 <p>
 Start yast, and choose the "Install and Remove software" option, and use "Search" to find pwdutils. Indicate that you wish to update to version 3.0.2.</p>    
+
 <h2>Installing LON-CAPA</h2>
 <h3>Install prerequisites</h3>
 <p> Execute: </p>
@@ -144,7 +149,7 @@ Retrieve the LON-CAPA setup with one of
 <pre>
 wget http://install.loncapa.org/versions/suse/sles9/i386/suse_install.tar
 </pre>
-<br />
+<br>
 <i>64 bit architecture</i>
 <pre>
 wget http://install.loncapa.org/versions/suse/sles9/x86_64/suse_install.tar
@@ -202,7 +207,7 @@ for it to function at all.  Below is a l
 To configure and install LON-CAPA, execute the following commands:
 </p>
 <pre>
-cd /root/loncapa-N.N.N     (N.N.N should correspond to a version number like '2.0.2')
+cd /root/loncapa-X.Y.Z     (X.Y.Z should correspond to a version number like '2.10.0')
 ./UPDATE
 </pre>
 <p>
@@ -215,21 +220,21 @@ in the previous section.
 </pre>
 <h3>Updating packages</h3>
 <p>Start yast and use "Online Update" to check for updates to installed packages. When prompted for the username and password for your account with Novell, you should check the box to retain your log-in information, otherwise the nightly update check, installed as part of the LON-CAPA install, will fail and send you a message "ERROR(Media:login failed)" each time it runs.</p>
+
 <h2>Creating a Domain Coordinator</h2>
 <p>
 You will need at least one user at your site who has the role of
 'domain coordinator'.  This user creates accounts for other users and
 grants them additional privileges.  The make_domain_coordinator.pl script
-invoked below requires that you enter the users password.  The password will
-show in plaintext as you type it.  Feel free to use the "passwd username"
-command to change it later.  Replace USERNAME and DOMAIN with an 
-appropriate user name and your domain.
+invoked below requires that you enter the user's password. 
+Feel free to use the "passwd username" command to change it later.
+Replace USERNAME and DOMAIN with an appropriate user name and your domain.
 </p>
 <pre>
-cd /root/loncapa-N.N/loncom/build
+cd /root/loncapa-X.Y.Z/loncom/build
 perl make_domain_coordinator.pl USERNAME DOMAIN
-(WILL PROMPT FOR PASSWORD HERE)
 </pre>
+
 <h2>Start/Restart Services</h2>
 <p>
 The LON-CAPA network services take a moment to start.  Most misconfigurations
@@ -245,17 +250,19 @@ please make sure you followed the instru
 <b>Installing LON-CAPA Dependencies</b>.  If you still have errors, please
 contact the MSU LON-CAPA group.
 </p>
+
 <h2>Log in to your LON-CAPA Machine</h2>
 <p>
 Point a web browser at your new machine and log in as the domain
 coordinator.  Congratulations!
 </p>
+
 <h2>If things aren't working right</h2>
 <p>
 If you've followed the steps above and the server doesn't start or you think
 there's something wrong, please get in touch with the MSU LON-CAPA group.
-You can submit a help request using our web form:<br />
-<a href="http://help.loncapa.org/help/">http://help.loncapa.org/help/</a><br />
+You can submit a help request using our web form:<br>
+<a href="http://help.loncapa.org/help/">http://help.loncapa.org/help/</a><br>
 If there were errors in installation of the dependency RPMs or during the
 automatic setup, please send us as much information as possible.
 If some part of this document is unclear please let us know.