Document configure's --with-maxbackends switch.

Fix a few small typos.

diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml
index 54e3b22619c509e24ed3f743dd8309905582dcc3..0446ad47d644bbf522f3beadfe6bbe1eec56abef 100644 (file)
--- a/doc/src/sgml/config.sgml
+++ b/doc/src/sgml/config.sgml
@@ -39,21 +39,23 @@ Features and packages:
   --enable-recode         enable cyrillic recode support
   --with-mb=encoding    enable multi-byte support
   --with-pgport=portnum change default startup port
-  --with-tcl              use tcl
+  --with-maxbackends=n  set default maximum number of server processes 
+  --with-tcl              build Tcl interfaces and pgtclsh
   --with-tclconfig=tcldir tclConfig.sh and tkConfig.sh are in DIR
-  --with-perl             use perl
+  --with-perl             build Perl interface
   --with-odbc             build ODBC driver package
   --with-odbcinst=odbcdir change default directory for odbcinst.ini
   --enable-cassert        enable assertion checks (debugging)
   --with-CC=compiler      use specific C compiler
   --with-CXX=compiler     use specific C++ compiler
+  --without-CXX           prevent building C++ code 
    
   
   
    Some systems may have trouble building a specific feature of
    Postgres. For example, systems with a damaged
-   C++ compiler may need to specify --without-CXX to encourage
-   the build procedure to ignore the libpq++ construction.
+   C++ compiler may need to specify --without-CXX to instruct
+   the build procedure to skip construction of libpq++.
   
  
  
@@ -64,7 +66,7 @@ Features and packages:
    stage of Postgres installation.
   
   
-   In most cases, these parameters should be place in a file,
+   In most cases, these parameters should be placed in a file,
    Makefile.custom, intended just for that purpose.
    The default distribution does not contain this optional file, so you
    will create it using a text editor of your choice. When upgrading installations,
@@ -348,7 +350,7 @@ PSTYLE= /home/tgl/SGML/db118.d/docbook/print
    What are the Drawbacks?
    
    
-    There is one evident drawback of using locale - it's speed! 
+    There is one evident drawback of using locale - its speed! 
     So, use locale only if you really need it. 
    
   

diff --git a/doc/src/sgml/install.sgml b/doc/src/sgml/install.sgml
index b4db0ad4d8a8fc57a2c1a46c45f384e6e3b31788..aa62649aa5622fa961f2f47d871bae845eb241c4 100644 (file)
--- a/doc/src/sgml/install.sgml
+++ b/doc/src/sgml/install.sgml
@@ -310,7 +310,7 @@ $ ls -l db.out
      your backup.  If necessary, bring down postmaster, edit the permissions
      in file /usr/local/pgsql/data/pg_hba.conf
  to allow only you on, then
-     bring postmaster back up.
+     bring postmaster back up.
 
 
 
@@ -380,7 +380,7 @@ $ exit
 
 
   Make new source and install directories.  The actual paths can be
-     different for your installation but you must be consistant throughout this procedure.
+     different for your installation but you must be consistent throughout this procedure.
 
 
 
@@ -711,7 +711,7 @@ pg_id: can't load library 'libpq.so'
      
      
       
-       Several regression tests could failed if the user's locale collation
+       Several regression tests could fail if the user's locale collation
        scheme is different from that of standard C locale.