Log Message:
-----------

Fix some typos, add doc about RPM installations and fix some formatting.

Modified Files:
--------------
    slony1-engine/doc/adminguide:
        prerequisites.sgml (r1.20 -> r1.21)
        intro.sgml (r1.18 -> r1.19)
        installation.sgml (r1.14 -> r1.15)

-------------- next part --------------
Index: installation.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/installation.sgml,v
retrieving revision 1.14
retrieving revision 1.15
diff -Ldoc/adminguide/installation.sgml -Ldoc/adminguide/installation.sgml -u -w -r1.14 -r1.15
--- doc/adminguide/installation.sgml
+++ doc/adminguide/installation.sgml
@@ -129,6 +129,39 @@
 Commonly you need to do this either as root or as the postgres user.
 </para>
 </sect2>
+
+<sect2>
+<title> Installing &slony1; from RPMs</title>
+
+<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>
+
+<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 
+PostgreSQL, so if you install PosgtgreSQL from source, you should 
+manually ignore the RPM dependencies related to PostgreSQL.</para>
+
+<para>Installing &slony1; using these RPMs is as easy as 
+installing any RPM.</para>
+
+<screen>rpm -ivh postgresql-slony1-engine-....rpm</screen>
+
+<para>If you want to upgrade the previous version, just use 
+<command>rpm -Uvh</command> to upgrade it. But please remember to follow 
+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> 
+
+</sect2>
+
 </sect1>
 
 <!-- Keep this comment at the end of the file
Index: intro.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/intro.sgml,v
retrieving revision 1.18
retrieving revision 1.19
diff -Ldoc/adminguide/intro.sgml -Ldoc/adminguide/intro.sgml -u -w -r1.18 -r1.19
--- doc/adminguide/intro.sgml
+++ doc/adminguide/intro.sgml
@@ -29,15 +29,15 @@
 <itemizedlist>
 <listitem><para> Sites where connectivity is really <quote>flakey</quote>
 </para></listitem>
-<listitem><para> Replication to nodes that are unpredictably connected.</para>
+<listitem><para> Replication to nodes that are unpredictably connected.</para></listitem>
 
-<para> Replicating a pricing database from a central server to sales
+<listitem><para> Replicating a pricing database from a central server to sales
 staff who connect periodically to grab updates.  </para></listitem>
 
 <listitem><para> Sites where configuration changes are made in a
-haphazard way.</para>
+haphazard way.</para></listitem>
 
-<para> A <quote>web hosting</quote> situation where customers can
+<listitem><para> A <quote>web hosting</quote> situation where customers can
 independently make arbitrary changes to database schemas is not a good
 candidate for &slony1; usage. </para></listitem>
 
@@ -148,7 +148,7 @@
 linkend="ddlchanges"> caveats.</link></para>
 
 <para>If you have those sorts of requirements, it may be worth
-exploring the use of &postgres; 8.0 <acronym>PITR</acronym> (Point In
+exploring the use of &postgres; 8.X <acronym>PITR</acronym> (Point In
 Time Recovery), where <acronym>WAL</acronym> logs are replicated to
 remote nodes.  Unfortunately, that has two attendant limitations:
 
Index: prerequisites.sgml
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/doc/adminguide/prerequisites.sgml,v
retrieving revision 1.20
retrieving revision 1.21
diff -Ldoc/adminguide/prerequisites.sgml -Ldoc/adminguide/prerequisites.sgml -u -w -r1.20 -r1.21
--- doc/adminguide/prerequisites.sgml
+++ doc/adminguide/prerequisites.sgml
@@ -39,7 +39,7 @@
 need to be able to be compiled from source at your site.</para>
 
 <para> In order to compile &slony1;, you need to have the following
-tools.
+tools:
 
 <itemizedlist>
 <listitem><para> GNU make.  Other make programs will not work.  GNU