summaryrefslogtreecommitdiff
path: root/pod/perlipc.pod
diff options
context:
space:
mode:
authorDavid Landgren <david@landgren.net>2007-09-28 22:42:56 +0200
committerRafael Garcia-Suarez <rgarciasuarez@gmail.com>2007-10-04 14:28:34 +0000
commit353c650532037e4006fbdb2176350717f320f7c3 (patch)
treed168025606b4a4daf862755b087c4ba3b29e97b5 /pod/perlipc.pod
parent94fcd414575e04d8b809003ba7bca1216090abff (diff)
downloadperl-353c650532037e4006fbdb2176350717f320f7c3.tar.gz
POD cleanups
Message-ID: <46FD4B30.9070802@landgren.net> p4raw-id: //depot/perl@32026
Diffstat (limited to 'pod/perlipc.pod')
-rw-r--r--pod/perlipc.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlipc.pod b/pod/perlipc.pod
index f027d23839..f0722f72aa 100644
--- a/pod/perlipc.pod
+++ b/pod/perlipc.pod
@@ -119,7 +119,7 @@ handlers:
But that will be problematic for the more complicated handlers that need
to reinstall themselves. Because Perl's signal mechanism is currently
based on the signal(3) function from the C library, you may sometimes be so
-misfortunate as to run on systems where that function is "broken", that
+unfortunate as to run on systems where that function is "broken", that
is, it behaves in the old unreliable SysV way rather than the newer, more
reasonable BSD and POSIX fashion. So you'll see defensive people writing
signal handlers like this: