space out N<> - problematic with perl6 --doc

Author: coke

doc/Language/classtut.pod6

@@ -624,11 +624,11 @@ C<$o>, which tells us the exact type of C<$o>: in this case C<Programmer>.
 
 C<$o.perl> returns a string that can be executed as Perl code, and
 reproduces the original object C<$o>. While this does not work perfectly in
-all casesN<For example closures cannot easily be reproduced this way; if you
+all cases, it is very useful for debugging simple objects. 
+N<For example closures cannot easily be reproduced this way; if you
 don't know what a closure is don't worry. Also current implementations have
 problems with dumping cyclic data structures this way, but they are expected
-to be handled correctly by C<.perl> at some point.>, it is very useful for
-debugging simple objects.
+to be handled correctly by C<.perl> at some point.>
 
 C<$o.^methods(:local)> produces a list of L<Method|/type/Method>s that can be
 called on C<$o>. The C<:local> named argument limits the returned methods to

doc/Language/grammars.pod6

@@ -23,7 +23,7 @@ methods of regular code.
 The main ingredient of grammars is named L<regexes|/language/regexes>.
 While the syntax of L<Perl 6 Regexes|/language/regexes> is outside the scope
 of this document, I<named> regexes have a special syntax, similar to
-subroutine definitions:N<In fact, named regexes can even take extra
+subroutine definitions: N<In fact, named regexes can even take extra
 arguments, using the same syntax as subroutine parameter lists>
 
     =begin code :allow<B>

doc/Language/modules.pod6

@@ -6,7 +6,7 @@
 
 =head1 Creating and Using Modules
 
-A module is usually a source file or set of source filesN<Technically
+A module is usually a source file or set of source files N<Technically
 a module is a set of I<compunits> which are usually files but could
 come from anywhere as long as there is a I<compunit repository> that
 can provide it. See L<S11|https://design.perl6.org/S11.html>.> that
@@ -26,7 +26,7 @@ have the same structure as any distribution in the Perl family of languages:
 there is a main project directory containing a C<README> and a C<LICENSE> file,
 a C<lib> directory for the source filesE<mdash>which may be individually
 referred to as modules and/or may themselves define modules with the C<module>
-keywordN<As L<synopsis S11|https://design.perl6.org/S11.html#Units> says:
+keyword N<As L<synopsis S11|https://design.perl6.org/S11.html#Units> says:
 Confusing? Yes it is.>, a C<t> directory for tests, and possibly a C<bin>
 directory for executable programs and scripts.