Log Message:
-----------
Point to new location of RPMs, apply <file> tag to several filenames...

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        installation.sgml (r1.20 -> r1.21)

-------------- next part --------------
Index: installation.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/installation.sgml,v
retrieving revision 1.20
retrieving revision 1.21
diff -Ldoc/adminguide/installation.sgml -Ldoc/adminguide/installation.sgml -u -w -r1.20 -r1.21
--- doc/adminguide/installation.sgml
+++ doc/adminguide/installation.sgml
@@ -141,15 +141,16 @@
 
 <para> Even though &slony1; can be compiled and run on most Linux 
 distributions, it is also possible to install &slony1; using binary 
-packages. Slony Global Development Team provides official RPMs and SRPMs 
-for many versions or Red Hat ana Fedora Core.</para>
+packages. Slony Global Development Team provides official RPMs and
+SRPMs for many versions or Red Hat ana Fedora Core.</para>
 
-<para>The RPMs are available at 
-http://developer.PostgreSQL.org/~devrim/slony . Please read <command> 
-CURRENT_MAINTAINER</command> file for the details of the RPMs. 
-Please note that the RPMs will look for RPM installation of 
-&postgres;, so if you install &postgres; from source, you should 
-manually ignore the RPM dependencies related to &postgres;.</para>
+<para>The RPMs are available at <ulink
+url="http://pgfoundry.org/projects/slony1/"> &slony1; at pgFoundry.org
+</ulink>. Please read <command> CURRENT_MAINTAINER</command> file for
+the details of the RPMs. Please note that the RPMs will look for RPM
+installation of &postgres;, so if you install &postgres; from source,
+you should manually ignore the RPM dependencies related to
+&postgres;.</para>
 
 <para>Installing &slony1; using these RPMs is as easy as 
 installing any RPM.</para>
@@ -161,20 +162,22 @@
 the usual upgrade procedure, too.</para>
 
 <para>The RPM installs the files into their usual places. The 
-configuration files are installed under /etc, the binary files are 
-installed to /usr/bin, libs are installed to /usr/lib/pgsql, and finally 
-the docs are installed under 
-/usr/share/doc/postgresql-slony1-engine.</para> 
+configuration files are installed under <filename>/etc</filename>, the
+binary files are installed in <filename>/usr/bin</filename>, libraries
+are installed in <filename>/usr/lib/pgsql</filename>, and finally the
+docs are installed in
+<filename>/usr/share/doc/postgresql-slony1-engine</filename>.</para>
 
 </sect2>
 
 <sect2>
 <title> Installing the &slony1; service on &windows;</title>
 
-<para> On &windows; systems, instead of running one slon daemon per
-node, a single slon service is installed which can then be controlled
-through the <command>Services</command> control panel applet, or from
-a command prompt using the <command>net</command> command.</para>
+<para> On &windows; systems, instead of running one <xref
+linkend="slon"> daemon per node, a single slon service is installed
+which can then be controlled through the <command>Services</command>
+control panel applet, or from a command prompt using the
+<command>net</command> command.</para>
 
 <screen>
 C:\Program Files\PostgreSQL\8.0\bin> slon -regservice my_slon