minor edits and cleanup

Author: tbrowder

doc/Language/modules.pod6

@@ -214,7 +214,7 @@ my $bar = Bar.new;
 
 =head3 is export
 
-Packages, subroutines, variables, constants and enums are exported by marking
+Packages, subroutines, variables, constants, and enums are exported by marking
 them with the L<is export|/routine/is export> trait (also note the tags available for indicating
 authors and versions).
 
@@ -621,20 +621,19 @@ copy/paste the raw form of L<its license|https://github.com/rakudo/rakudo/blob/m
 into your own C<LICENSE> file.
 
 =item The license field in META6.json
-The license field should be one of the standardized names listed here:
+should be one of the standardized names listed here:
 L<https://spdx.org/licenses/>. In the case of the B<Artistic 2.0> license, which
     is what many of our ecosystem modules use, its identifier is
     C<Artistic-2.0>. Having standardized identifiers make it easy for humans
     and computers alike to know which license was actually used by looking at
     the metadata!
 
-=item I<Your license is not on spdx.org or you have your own license>:
-If you can't find your license on C<spdx.org> or you use your own license,
-you should put the license's name in the license field, and under
-more details here L<https://design.perl6.org/S22.html#license>.
+=item If you can't find your license on C<spdx.org> or you use your own license,
+you should put the license's name in the license field. For more details see
+L<https://design.perl6.org/S22.html#license>.
 
 =item If you don't yet have any tests, you can leave out the C<t>
-directory and C<basic.t> file for now. For more info on how to write
+directory and C<basic.t> file for now. For more information on how to write
 tests (for now), you might have a look at how other modules use
 C<Test>.
 
@@ -662,8 +661,8 @@ C<TODO>, or other files.>
 
 If your module requires extra processing during installation to fully
 integrate with and use non-Perl operating system resources, you may
-need to add a C<Build.pm6> file (a "build hook") to the top-level directory. It will
-bu used by the C<zef> installer as the first step in the installation process.
+need to add a X<C<Build.pm6>|Build.pm6> file (a "build hook") to the top-level directory. It will
+be used by the C<zef> installer as the first step in the installation process.
 See the README for C<zef> for a brief example. Also see various usage scenarios in existing
 ecosystem modules such as C<zef> itself.
 =end item
@@ -747,7 +746,7 @@ Their installed location can be determined through the C<%?RESOURCES> C<Hash>
 indexed on the name provided. The C<tags> section is also optional. It is used to describe
 the module in the Perl 6 ecosystem.
 
-The C<depends>, C<build-depends> and C<test-depends> sections include different modules that
+The C<depends>, C<build-depends>, and C<test-depends> sections include different modules that
 are used in those phases of the of installation. All are optional, but
 they must obviously contain the modules that are going to be needed in those
 particular phases. These dependencies might optionally use