Small SGML cleanup from Jeroen Ruigrok/asmodai

diff --git a/doc/src/sgml/installation.sgml b/doc/src/sgml/installation.sgml
index ea445bed664159810d3d3e495a6dc1da9f4ee5de..92eb827547b01d7e58c549663946f871b86fbfa1 100644 (file)
--- a/doc/src/sgml/installation.sgml
+++ b/doc/src/sgml/installation.sgml
@@ -1,4 +1,4 @@
-<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.144 2003/09/26 17:47:44 momjian Exp $ -->
+<!-- $Header: /cvsroot/pgsql/doc/src/sgml/installation.sgml,v 1.145 2003/09/27 14:06:21 momjian Exp $ -->
 
 <chapter id="installation">
  <title><![%standalone-include[<productname>PostgreSQL</>]]>
@@ -1167,10 +1167,10 @@ All of PostgreSQL is successfully made. Ready to install.
     hardware.  This allows it to start up with almost any hardware
     configuration. However, the default configuration is not designed for
     optimum performance. To achieve optimum performance, several server
-    variables must be adjusted,  the two most common being
+    variables must be adjusted, the two most common being
     <varname>shared_buffers</varname> and <varname> sort_mem</varname>
     mentioned in <xref linkend="runtime-config-resource-memory">. Other
-    paramters in <xref linkend="runtime-config-resource"> also affect 
+    parameters in <xref linkend="runtime-config-resource"> also affect 
     performance.
    </para>
   </sect2>