Re: [PATCH] POD fixes

Message-ID: <47BFFDCB.60107@profvince.com>

p4raw-id: //depot/perl@33366

3 files changed, 3 insertions, 3 deletions

diff --git a/pod/perlreapi.pod b/pod/perlreapi.pod
index f8e9984341..b0d6275810 100644
--- a/pod/perlreapi.pod
+++ b/pod/perlreapi.pod
@@ -334,7 +334,7 @@ just die when assigned to in the default engine.
 Get the C<length> of a capture variable. There's a special callback
 for this so that perl doesn't have to do a FETCH and run C<length> on
 the result, since the length is (in perl's case) known from an offset
-stored in C<<rx->offs> this is much more efficient:
+stored in C<< rx->offs >> this is much more efficient:
 
     I32 s1  = rx->offs[paren].start;
     I32 s2  = rx->offs[paren].end;
diff --git a/pod/perlreguts.pod b/pod/perlreguts.pod
index 125a9f9f41..204993165c 100644
--- a/pod/perlreguts.pod
+++ b/pod/perlreguts.pod
@@ -385,7 +385,7 @@ A grammar form might be something like this:
 
 =head3 Debug Output
 
-In the 5.9.x development version of perl you can C<<use re Debug => 'PARSE'>>
+In the 5.9.x development version of perl you can C<< use re Debug => 'PARSE' >>
 to see some trace information about the parse process. We will start with some
 simple patterns and build up to more complex patterns.
 
diff --git a/pod/perlxs.pod b/pod/perlxs.pod
index c045564a6d..f88565bf17 100644
--- a/pod/perlxs.pod
+++ b/pod/perlxs.pod
@@ -2007,7 +2007,7 @@ comma, i.e.  C<_aMY_CXT>, C<aMY_CXT_>, C<_pMY_CXT> and C<pMY_CXT_>.
 =item MY_CXT_CLONE
 
 By default, when a new interpreter is created as a copy of an existing one
-(eg via C<<threads->create()>>), both interpreters share the same physical
+(eg via C<< threads->create() >>), both interpreters share the same physical
 my_cxt_t structure. Calling C<MY_CXT_CLONE> (typically via the package's
 C<CLONE()> function), causes a byte-for-byte copy of the structure to be
 taken, and any future dMY_CXT will cause the copy to be accessed instead.