typo

[perl5.git] / INSTALL

diff --git a/INSTALL b/INSTALL
index 01b22e1..525f5e4 100644 (file)
--- 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.8.
+By default, Configure will use the following directories for 5.14.0.
 $version is the full perl version number, including subversion, e.g.
-5.13.8 or 5.9.5, and $archname is a string like sun4-sunos,
+5.14.0 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.
 
@@ -841,7 +841,7 @@ must contain a space separated list of directories under the site_perl
 directory, and has to include architecture-dependent directories separately,
 eg.
 
-       sh Configure -Dinc_version_list="5.12.0/x86_64-linux 5.12.0" ...
+       sh Configure -Dinc_version_list="5.14.0/x86_64-linux 5.14.0" ...
 
 When using the newer perl, you can add these paths again in the
 $PERL5LIB environment variable or with perl's -I runtime option.
@@ -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
@@ -1300,7 +1300,7 @@ various other operating systems.
 
 If you plan to port Perl to a new architecture, study carefully the
 section titled "Philosophical Issues in Patching and Porting Perl"
-in the file Porting/pumpkin.pod and the file pod/perlrepository.pod.
+in the file Porting/pumpkin.pod and the file pod/perlgit.pod.
 Study also how other non-UNIX ports have solved problems.
 
 =back
@@ -2300,7 +2300,7 @@ http://www.chiark.greenend.org.uk/~sgtatham/bugs.html
 
 =head1 Coexistence with earlier versions of perl 5
 
-Perl 5.12 is not binary compatible with earlier versions of Perl.
+Perl 5.14 is not binary compatible with earlier versions of Perl.
 In other words, you will have to recompile your XS modules.
 
 In general, you can usually safely upgrade from one version of Perl (e.g.
@@ -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.8
+       sh Configure -Dprefix=/opt/perl5.14.0
 
-and adding /opt/perl5.13.8/bin to the shell PATH variable.  Such users
+and adding /opt/perl5.14.0/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.7 or earlier
+=head2 Upgrading from 5.13.11 or earlier
 
-B<Perl 5.13.8 is binary incompatible with Perl 5.13.7 and any earlier
+B<Perl 5.14.0 is binary incompatible with Perl 5.13.11 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.8.  If you find you do need to rebuild an extension with
-5.13.8, you may safely do so without disturbing the older
+used with 5.14.0.  If you find you do need to rebuild an extension with
+5.14.0, you may safely do so without disturbing the older
 installations.  (See L<"Coexistence with earlier versions of perl 5">
 above.)