summaryrefslogtreecommitdiff
path: root/pod/perllexwarn.pod
diff options
context:
space:
mode:
authorFather Chrysostomos <sprout@cpan.org>2013-10-31 05:46:39 -0700
committerFather Chrysostomos <sprout@cpan.org>2013-10-31 05:46:39 -0700
commite9158b84fe735f37141c35ffabc02ac81dd2ea4b (patch)
tree621fb0333bc0b536f3e0a4f84dae45e7e187d511 /pod/perllexwarn.pod
parent5e0ced9c71eb5288cc7d3c653e747b26ea6ec7b6 (diff)
downloadperl-e9158b84fe735f37141c35ffabc02ac81dd2ea4b.tar.gz
perllexwarn: typo, pod syntax
Diffstat (limited to 'pod/perllexwarn.pod')
-rw-r--r--pod/perllexwarn.pod5
1 files changed, 3 insertions, 2 deletions
diff --git a/pod/perllexwarn.pod b/pod/perllexwarn.pod
index 733df81432..d63292000a 100644
--- a/pod/perllexwarn.pod
+++ b/pod/perllexwarn.pod
@@ -402,7 +402,8 @@ except for those in the "syntax" category.
use warnings FATAL => 'all', NONFATAL => 'syntax';
-B<NOTE:> Users of FATAL warnings, especially those using C<FATAL => 'all'>
+B<NOTE:> Users of FATAL warnings, especially
+those using C<< FATAL => 'all' >>
should be fully aware that they are risking future portability of their
programs by doing so. Perl makes absolutely no commitments to not
introduce new warnings, or warnings categories in the future, and indeed
@@ -417,7 +418,7 @@ the documentation of the features they use to ensure they do not exploit
features that are documented as risky, deprecated, or unspecified, or where
the documentation says "so don't do that", or anything with the same sense
and spirit. Use of such features in combination with FATAL warnings is
-ENTIRELY AT THE USERS RISK.
+ENTIRELY AT THE USER'S RISK.
=head2 Reporting Warnings from a Module
X<warning, reporting> X<warning, registering>