summaryrefslogtreecommitdiff
path: root/pod/perlvms.pod
diff options
context:
space:
mode:
authorCraig A. Berry <craigberry@mac.com>2009-10-15 11:01:33 -0500
committerCraig A. Berry <craigberry@mac.com>2009-10-15 11:01:33 -0500
commita55b162c2ce28c963bbb5fda32a8aff3855ff15d (patch)
tree03ab98f07f156bbf786f1b9806aff977aafd1899 /pod/perlvms.pod
parent7fa7b0adb97886e2a8e02b65c9e10f9872651150 (diff)
downloadperl-a55b162c2ce28c963bbb5fda32a8aff3855ff15d.tar.gz
Fix 2 pod errors in perlvms.pod.
Diffstat (limited to 'pod/perlvms.pod')
-rw-r--r--pod/perlvms.pod2
1 files changed, 1 insertions, 1 deletions
diff --git a/pod/perlvms.pod b/pod/perlvms.pod
index 9854ff855a..d7ed2bca33 100644
--- a/pod/perlvms.pod
+++ b/pod/perlvms.pod
@@ -772,7 +772,7 @@ true, a warning message is printed, and C<undef> is returned.
=item kill
In most cases, C<kill> is implemented via the undocumented system
-service <$SIGPRC>, which has the same calling sequence as <$FORCEX>, but
+service C<$SIGPRC>, which has the same calling sequence as C<$FORCEX>, but
throws an exception in the target process rather than forcing it to call
C<$EXIT>. Generally speaking, C<kill> follows the behavior of the
CRTL's C<kill()> function, but unlike that function can be called from