Fixes other occurrences, refs #3024

doc/Language/modules-extra.pod6

@@ -16,7 +16,8 @@ of a module distribution.
 
 =item L<App::Assixt|https://modules.perl6.org/dist/App::Assixt> The module developer's assistant
 =item L<App::Mi6|https://modules.perl6.org/dist/App::Mi6>     Minimal authoring tool for Perl 6
-=item L<META6|https://modules.perl6.org/dist/META6>        Do things with Perl 6 META files
+=item L<META6|https://modules.perl6.org/dist/META6>        Do things with
+Perl 6 C<META> files
 =item L<Module::Skeleton|https://bitbucket.org/rightfold/module-skeleton>        Generate a skeleton module
 =item L<p6doc|https://modules.perl6.org/dist/p6doc>        Generate documentation end-products
 

doc/Language/modules.pod6

@@ -801,12 +801,13 @@ which was used to indicate the kind of source control system, generally C<git>,
 which can be used to download the module. However, this field is nowadays
 ignored by C<zef> and the rest of the tools.>
 
-The L<Test::META module | https://github.com/jonathanstowe/Test-META/> can help
+The L<C<Test::META>> module | https://github.com/jonathanstowe/Test-META/> can
+help
 you check the correctness of the META6.json file; this module will check for all
 the mandatory fields and that the type used for all of them is correct.
 
 There are more fields described in the
-L<META design documents |https://design.perl6.org/S22.html#META6.json>,
+L<C<META> design documents |https://design.perl6.org/S22.html#META6.json>,
 but not all of these are
 implemented by existing package managers. Hence you should stick to the fields
 described in the above example block to ensure compatibility with existing