Apparentl S<C<< doesn't work with all pod parsers

diff --git a/lib/Moose/Cookbook/Extending/Recipe3.pod b/lib/Moose/Cookbook/Extending/Recipe3.pod
index 39dc0a8..7db8b12 100644 (file)
--- a/lib/Moose/Cookbook/Extending/Recipe3.pod
+++ b/lib/Moose/Cookbook/Extending/Recipe3.pod
@@ -42,13 +42,13 @@ In this particular example, our base class issues some debugging
 output every time a new object is created, but you can think of some
 more interesting things to do with your own base class.
 
-This uses the magic of L<Moose::Exporter>. When we call S<C<<
-Moose::Exporter->setup_import_methods( also => 'Moose' ) >>> it builds
-C<import> and C<unimport> methods for you. The S<C<< also => 'Moose'
->>> bit says that we want to export everything that Moose does.
+This uses the magic of L<Moose::Exporter>. When we call C<<
+Moose::Exporter->setup_import_methods( also => 'Moose' ) >> it builds
+C<import> and C<unimport> methods for you. The C<< also => 'Moose' >>
+bit says that we want to export everything that Moose does.
 
 The C<import> method that gets created will call our C<init_meta>
-method, passing it S<C<< for_caller => $caller >>> as its
+method, passing it C<< for_caller => $caller >> as its
 arguments. The C<$caller> is set to the class that actually imported
 us in the first place.