summaryrefslogtreecommitdiff
path: root/pod/perlport.pod
diff options
context:
space:
mode:
authorJeffrey Friedl <jfriedl@regex.info>2001-11-11 13:15:18 -0800
committerJarkko Hietaniemi <jhi@iki.fi>2001-11-12 14:50:44 +0000
commitd1be9408a3c14848d30728674452e191ba5fffaa (patch)
treed3171518bc3a517cf0c9ce65b5d8382c995f2fb6 /pod/perlport.pod
parentbf0fa0b28861f64af680a3c19765ac8a24e4f2bd (diff)
downloadperl-d1be9408a3c14848d30728674452e191ba5fffaa.tar.gz
a few typo fixes
Message-Id: <200111120515.fAC5FIc74795@ventrue.corp.yahoo.com> Patching README.foo instead of pod/perlfoo.pod, not patching Math::BigInt (Tels will take care of that), dropping broken hv.c and sv.h patches, patching libnetcfg.PL and perldoc.PL instead of libnetcfg and perldoc, patching ext/Digest/MD5/t/files.t since MD5.pm was changed. p4raw-id: //depot/perl@12954
Diffstat (limited to 'pod/perlport.pod')
-rw-r--r--pod/perlport.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlport.pod b/pod/perlport.pod
index 4edf7108a6..5869135020 100644
--- a/pod/perlport.pod
+++ b/pod/perlport.pod
@@ -559,7 +559,7 @@ often happens when tests spawn off other processes or call external
programs to aid in the testing, or when (as noted above) the tests
assume certain things about the filesystem and paths. Be careful
not to depend on a specific output style for errors, such as when
-checking C<$!> after an system call. Some platforms expect a certain
+checking C<$!> after a system call. Some platforms expect a certain
output format, and perl on those platforms may have been adjusted
accordingly. Most specifically, don't anchor a regex when testing
an error value.