From @Abigail

[Please enter your report here]

This fixes a few pod glitches in 5.005_63.

Only in pod.orig​: errors
diff -c pod.orig/perllexwarn.pod pod/perllexwarn.pod
*** pod.orig/perllexwarn.pod Sun Sep 12 23​:00​:00 1999
--- pod/perllexwarn.pod Sun Jan 9 03​:20​:19 2000
***************
*** 3,9 ****
  perllexwarn - Perl Lexical Warnings
 
  =head1 DESCRIPTION
!
  The C<use warnings> pragma is a replacement for both the command line
  flag B<-w> and the equivalent Perl variable, C<$^W>.
 
--- 3,9 ----
  perllexwarn - Perl Lexical Warnings
 
  =head1 DESCRIPTION
!
  The C<use warnings> pragma is a replacement for both the command line
  flag B<-w> and the equivalent Perl variable, C<$^W>.
 
***************
*** 160,166 ****
  lexical warnings and C<$^W>, this section will describe how they interact.
 
  How Lexical Warnings interact with B<-w>/C<$^W>​:
!
  =over 5
 
  =item 1.
--- 160,166 ----
  lexical warnings and C<$^W>, this section will describe how they interact.
 
  How Lexical Warnings interact with B<-w>/C<$^W>​:
!
  =over 5
 
  =item 1.
diff -c pod.orig/perlxstut.pod pod/perlxstut.pod
*** pod.orig/perlxstut.pod Wed Dec 8 01​:23​:13 1999
--- pod/perlxstut.pod Sun Jan 9 03​:22​:40 2000
***************
*** 24,30 ****
  This tutorial assumes that the make program that Perl is configured to
  use is called C<make>. Instead of running "make" in the examples that
  follow, you may have to substitute whatever make program Perl has been
! configured to use. Running "perl -V​:make" should tell you what it is.
 
  =head2 Version caveat
 
--- 24,30 ----
  This tutorial assumes that the make program that Perl is configured to
  use is called C<make>. Instead of running "make" in the examples that
  follow, you may have to substitute whatever make program Perl has been
! configured to use. Running B<perl -V​:make> should tell you what it is.
 
  =head2 Version caveat
 
***************
*** 190,196 ****
 
  If you are on a Win32 system, and the build process fails with linker
  errors for functions in the C library, check if your Perl is configured
! to use PerlCRT (running "perl -V​:libc" should show you if this is the
  case). If Perl is configured to use PerlCRT, you have to make sure
  PerlCRT.lib is copied to the same location that msvcrt.lib lives in,
  so that the compiler can find it on its own. msvcrt.lib is usually
--- 190,196 ----
 
  If you are on a Win32 system, and the build process fails with linker
  errors for functions in the C library, check if your Perl is configured
! to use PerlCRT (running B<perl -V​:libc> should show you if this is the
  case). If Perl is configured to use PerlCRT, you have to make sure
  PerlCRT.lib is copied to the same location that msvcrt.lib lives in,
  so that the compiler can find it on its own. msvcrt.lib is usually