Change v6.5.2 to 6.5.2.

diff --git a/doc/src/sgml/install.sgml b/doc/src/sgml/install.sgml
index 39440b5f4785bd35f67c2e67050912c4cbe0581f..6a90c212940308c7556bf01d48c533b7f9c5403e 100644 (file)
--- a/doc/src/sgml/install.sgml
+++ b/doc/src/sgml/install.sgml
@@ -4,7 +4,7 @@
   <Abstract>
    <Para>
     Complete installation instructions for 
-    <ProductName>Postgres</ProductName> v6.5.3.
+    <ProductName>Postgres</ProductName> 6.5.3.
    </Para>
   </Abstract>
 
@@ -170,8 +170,8 @@ remaining steps in the installation will happen in this account.
 <Step Performance="required">
 <Para>
 Ftp file 
-<ulink url="ftp://ftp.postgresql.org/pub/postgresql-v6.5.3.tar.gz">
- <filename>ftp://ftp.postgresql.org/pub/postgresql-v6.5.3.tar.gz</filename></ulink>
+<ulink url="ftp://ftp.postgresql.org/pub/postgresql-6.5.3.tar.gz">
+ <filename>ftp://ftp.postgresql.org/pub/postgresql-6.5.3.tar.gz</filename></ulink>
  from the Internet.  Store it in your home directory.
 </Para>
 </Step>
@@ -255,13 +255,13 @@ If you are upgrading from 6.4.* or earlier,  back up your database.
 <tip>
 <para>
 Do not use the <application>pg_dumpall</application> 
-script from v6.0 or everything
+script from 6.0 or everything
      will be owned by the <ProductName>Postgres</ProductName> super user.
 </para>
 </tip>
 
 <para>
-To dump your fairly recent post-v6.0 database installation, type
+To dump your fairly recent post-6.0 database installation, type
 
 <programlisting>
 $ pg_dumpall > db.out
@@ -275,7 +275,7 @@ from the new distribution:
 
 <ProgramListing>
 $ cd
-$ gunzip -c postgresql-v6.5.3.tar.gz \
+$ gunzip -c postgresql-6.5.3.tar.gz \
     | tar xvf - src/bin/pg_dump/pg_dumpall
 $ chmod a+x src/bin/pg_dump/pg_dumpall
 $ src/bin/pg_dump/pg_dumpall > db.out
@@ -418,7 +418,7 @@ $ exit
  Unzip and untar the new source file.  Type
 <ProgramListing>
 $ cd /usr/src/pgsql
-$ gunzip -c ~/postgresql-v6.5.3.tar.gz | tar xvf -
+$ gunzip -c ~/postgresql-6.5.3.tar.gz | tar xvf -
 </ProgramListing>
 </Para>
 </Step>
@@ -780,7 +780,7 @@ $ initdb
      location of this file will change accordingly.)  This file should be
      made read only again once you are finished.
 
-     If you are upgrading from v6.0 or later you can copy file <filename>pg_hba.conf</filename> from
+     If you are upgrading from 6.0 or later you can copy file <filename>pg_hba.conf</filename> from
      your old database on top of the one in your new database, rather than
      redoing the file from scratch.
 </Para>
@@ -1001,7 +1001,7 @@ For example,
 <listitem>
 <Para>
      For a i686/Linux-ELF platform, no tests failed since this is the
-     v6.5.3 regression testing reference platform.
+     6.5.3 regression testing reference platform.
 </Para>
 </listitem>
 
@@ -1082,7 +1082,7 @@ $ cd
 $ psql -e template1 < db.out
 </ProgramListing>
 
-     If your pre-v6.2 database uses either path or polygon geometric data types,
+     If your pre-6.2 database uses either path or polygon geometric data types,
      then you will need to upgrade any columns containing those types. To
      do so, type (from within psql)
 <ProgramListing>
@@ -1115,7 +1115,7 @@ $ rm -rf /usr/src/pgsql_6_5
 $ rm -rf /usr/local/pgsql_6_5
 # Also delete old database directory tree if it is not in
 #  /usr/local/pgsql_6_5/data
-$ rm ~/postgresql-v6.5.3.tar.gz
+$ rm ~/postgresql-6.5.3.tar.gz
 </ProgramListing>
 </Para>
 </Step>
@@ -1162,7 +1162,7 @@ $ lpr -l -s -r manpage.hp
 <itemizedlist>
 <listitem>
 <para>
-The version of <ProductName>Postgres</ProductName> (v6.5.3, 6.5, beta 990318, etc.).
+The version of <ProductName>Postgres</ProductName> (6.5.3, 6.5, beta 990318, etc.).
 </para>
 </listitem>