Merge pull request #1654 from patzim/master

Some markup fixes for Language/Modules.

Author: PatZim

doc/Language/modules.pod6

@@ -507,7 +507,8 @@ lib
     tests (for now), you might have a look at how other modules use
     C<Test>. It's quite similar to Perl 5's C<Test::More>.
 
-    =item To document your modules, use L<Perl 6 Pod |
+    =begin item
+    To document your modules, use L<Perl 6 Pod |
     https://design.perl6.org/S26.html> markup inside your modules. Module
     documentation is most appreciated and will be especially important once
     the Perl 6 module directory (or some other site) begins rendering Pod docs
@@ -521,15 +522,16 @@ lib
         `-- TotalPerspective.pod6
     =end code
 
-    N«
-        Note, described above is a minimal project directory. If your project
-        contains scripts that you'd like distributed along with your module(s),
-        put them in a C<bin> directory. If you'd like a graphical logo to
-        appear next to your module at the module directory, create a
-        C<logotype> directory and put into it a C<logo_32x32.png> file. At some
-        point, you might also consider adding C<CONTRIBUTORS>, C<NEWS>,
-        C<TODO>, or other files.
-    »
+    =end item
+
+    =item
+    Note, described above is a minimal project directory. If your project
+    contains scripts that you'd like distributed along with your module(s),
+    put them in a C<bin> directory. If you'd like a graphical logo to
+    appear next to your module at the module directory, create a
+    C<logotype> directory and put into it a C<logo_32x32.png> file. At some
+    point, you might also consider adding C<CONTRIBUTORS>, C<NEWS>,
+    C<TODO>, or other files.
 
     =begin item
     Make your X<C<META6.json>|META6.json> file look something like this:
@@ -589,8 +591,9 @@ lib
     To test your module you can use the following command to install the
     module directly from the module folder you just created.
 
-    =for code :lang<shell>
+    =begin code :lang<shell>
     zef install ./your-module-folder
+    =end code
 
     =end item
 
@@ -610,8 +613,9 @@ account. The process takes about 5 minutes and some e-mail back and forth.
 
     If you use git you can also use the following command to create a package directly for a given commit.
 
-    =for code :lang<shell>
+    =begin code :lang<shell>
     git archive --prefix=Vortex-TotalPerspective-0.0.1/ -o ../Vortex-TotalPerspective-0.0.1.tar.gz HEAD
+    =end code
 
     =end item
 
@@ -623,20 +627,16 @@ account. The process takes about 5 minutes and some e-mail back and forth.
     =begin item
     Select your file and click I<Upload>!
 
-    N«
-        Make sure you have a META6.json file in your dist and that the dist
-        version you're uploading is higher than the currently uploaded version.
-        Those are the most common upload errors.
-    »
+    I<Make sure you have a META6.json file in your dist and that the dist
+    version you're uploading is higher than the currently uploaded version.
+    Those are the most common upload errors.>
 
     =end item
 
 =head2 Upload your Module to p6c
 
-N«
-    The I<p6c> ecosystem is soon to be deprecated, so you should consider
-    using the I<CPAN> ecosystem instead.
-»
+I<The p6c ecosystem is soon to be deprecated, so you should consider
+using the CPAN ecosystem instead.>
 
 If you want to use the I<p6c> ecosystem you need to use git for your module's
 version control. The instructions herein assume that you have a
@@ -672,8 +672,9 @@ B<That's it! Thanks for contributing to the Perl 6 community!>
 If you'd like to try out installing your module, use the X<zef> module
 installer tool which is included with Rakudo Star Perl 6:
 
-=for code :lang<shell>
-$ zef install Vortex::TotalPerspective
+=begin code :lang<shell>
+zef install Vortex::TotalPerspective
+=end code
 
 This will download your module to its own working directory (C<~/.zef>),
 build it there, and install the module into your local Perl 6 installation directory.