X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/deabda197e63bdf85e3277cea5e6a0782d7213c9..eda9cac17f1c742273b62b039f512bc88ffb37a1:/INSTALL

diff --git a/INSTALL b/INSTALL
index 4c4c43c..33faa6b 100644
--- a/INSTALL
+++ b/INSTALL
@@ -530,9 +530,9 @@ The directories set up by Configure fall into three broad categories.
 
 =item Directories for the perl distribution
 
-By default, Configure will use the following directories for 5.13.6.
+By default, Configure will use the following directories for 5.13.9.
 $version is the full perl version number, including subversion, e.g.
-5.13.6 or 5.9.5, and $archname is a string like sun4-sunos,
+5.13.9 or 5.9.5, and $archname is a string like sun4-sunos,
 determined by Configure.  The full definitions of all Configure
 variables are in the file Porting/Glossary.
 
@@ -984,7 +984,7 @@ Perl comes with interfaces to number of libraries, including threads,
 dbm, ndbm, gdbm, and Berkeley db.  For the *db* extension, if
 Configure can find the appropriate header files and libraries, it will
 automatically include that extension.  The threading extension needs
-to be specified explicitely (see L<Threads>).
+to be specified explicitly (see L<Threads>).
 
 Those libraries are not distributed with perl. If your header (.h) files
 for those libraries are not in a directory normally searched by your C
@@ -2374,9 +2374,9 @@ won't interfere with another version.  (The defaults guarantee this for
 libraries after 5.6.0, but not for executables. TODO?)  One convenient
 way to do this is by using a separate prefix for each version, such as
 
-	sh Configure -Dprefix=/opt/perl5.13.6
+	sh Configure -Dprefix=/opt/perl5.13.9
 
-and adding /opt/perl5.13.6/bin to the shell PATH variable.  Such users
+and adding /opt/perl5.13.9/bin to the shell PATH variable.  Such users
 may also wish to add a symbolic link /usr/local/bin/perl so that
 scripts can still start with #!/usr/local/bin/perl.
 
@@ -2389,13 +2389,13 @@ seriously consider using a separate directory, since development
 subversions may not have all the compatibility wrinkles ironed out
 yet.
 
-=head2 Upgrading from 5.13.4 or earlier
+=head2 Upgrading from 5.13.8 or earlier
 
-B<Perl 5.13.6 is binary incompatible with Perl 5.13.5 and any earlier
+B<Perl 5.13.9 is binary incompatible with Perl 5.13.8 and any earlier
 Perl release.>  Perl modules having binary parts
 (meaning that a C compiler is used) will have to be recompiled to be
-used with 5.13.6.  If you find you do need to rebuild an extension with
-5.13.6, you may safely do so without disturbing the older
+used with 5.13.9.  If you find you do need to rebuild an extension with
+5.13.9, you may safely do so without disturbing the older
 installations.  (See L<"Coexistence with earlier versions of perl 5">
 above.)