From: Craig A. Berry <craigberry@mac.com>
Date: Thu, 15 Oct 2009 16:01:33 +0000 (-0500)
Subject: Fix 2 pod errors in perlvms.pod.
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=a55b162c2ce28c963bbb5fda32a8aff3855ff15d;p=p5sagit%2Fp5-mst-13.2.git

Fix 2 pod errors in perlvms.pod.
---

diff --git a/pod/perlvms.pod b/pod/perlvms.pod
index 9854ff8..d7ed2bc 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