information on reporting bugs and submitting patches.
In most cases, patches to modules in F<cpan/> should be sent upstream
-and should not be applied to the Perl core individually. If a patch to
-a file in F<cpan/> absolutely cannot wait for the fix to be made
-upstream, released to CPAN and copied to blead, you must add (or update) a
-C<CUSTOMIZED> entry in the F<Porting/Maintainers.pl> file to flag that a
-local modification has been made. See F<Porting/Maintainers.pl> for
-more details.
+and should not be applied to the Perl core individually. If a patch
+to a file in F<cpan/> absolutely cannot wait for the fix to be made
+upstream, released to CPAN and copied to blead, you must add (or
+update) a C<CUSTOMIZED> entry in the F<"Porting/Maintainers.pl"> file
+to flag that a local modification has been made. See
+F<"Porting/Maintainers.pl"> for more details.
In contrast, modules in the F<dist/> directory are maintained in the
core.
pod/perlguts.pod ? Should you be using F<...> or maybe L<...> instead of 2
pod/perlguts.pod ? Should you be using L<...> instead of 1
pod/perlguts.pod Verbatim line length including indents exceeds 80 by 26
+pod/perlhack.pod ? Should you be using L<...> instead of 1
pod/perlhack.pod Verbatim line length including indents exceeds 80 by 1
pod/perlhacktips.pod Verbatim line length including indents exceeds 80 by 1
pod/perlhist.pod Verbatim line length including indents exceeds 80 by 2