Some corrections and reflow

Author: JJ

doc/Language/modules.pod6

@@ -6,22 +6,28 @@
 
 =head1 Creating and using modules
 
-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
-expose Perl 6 constructs. These are typically packages
-(L<classes|/language/objects#Classes>,
+A module is usually a source file or set of source files that expose Perl 6
+constructs.
+
+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>.>
+
+Modules are typically packages (L<classes|/language/objects#Classes>,
 L<roles|/language/objects#Roles>, L<grammars|Grammar>),
 L<subroutines|/language/functions>, and sometimes
-L<variables|/language/variables>. In Perl 6 I<module> can also refer
-to a type of package declared with the C<module> keyword (see
-L<Module Packages|/language/module-packages> and the examples
-below) but here we mostly mean "module" as a set of source
-files in a namespace.
+L<variables|/language/variables>. In Perl 6 I<module> can also refer to a type
+of package declared with the C<module> keyword (see L<Module
+Packages|/language/module-packages> and the examples below) but here we mostly
+mean "module" as a set of source files in a namespace.
 
 =head2 Looking for and installing modules.
 
-L<C<zef>|https://github.com/ugexe/zef> is the application using for installing modules in Perl 6. Modules are listed in L<the Perl 6 ecosystem|https://modules.perl6.org> and can be searched there or from the command line using C<zef search>
+L<C<zef>|https://github.com/ugexe/zef> is the application using for installing
+modules in Perl 6. Modules are listed in L<the Perl 6
+ecosystem|https://modules.perl6.org> and can be searched there or from the
+command line using C<zef search>
 
 =for code :lang<shell>
     zef search WWW
@@ -258,7 +264,8 @@ tags: C<ALL>, C<DEFAULT> and C<MANDATORY>.
     # lib/MyModule.pm6
     unit module MyModule;
     sub bag        is export             { ... }
-    sub pants      is export(:MANDATORY) { ... } # objects with tag ':MANDATORY' are always exported
+    # objects with tag ':MANDATORY' are always exported
+    sub pants      is export(:MANDATORY) { ... }
     sub sunglasses is export(:day)       { ... }
     sub torch      is export(:night)     { ... }
     sub underpants is export(:ALL)       { ... }
@@ -608,7 +615,12 @@ C<Test>.
 
 =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 as HTML for easy browsing. If you have extra docs (in addition to the  Pod docs in your module(s)), create a C<doc> directory for them. Follow  the same folder structure as the C<lib> directory like so:
+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 as HTML for easy browsing. If you have extra docs (in
+addition to the  Pod docs in your module(s)), create a C<doc> directory for
+them. Follow  the same folder structure as the C<lib> directory like so:
 
 =begin code :lang<text>
 doc

doc/Language/packages.pod6

@@ -6,6 +6,7 @@
 
 =begin comment
 
+TODO
 * Take a lot of stuff from S02 for this
 * Document 'import'
 
@@ -32,13 +33,13 @@ class Foo {
     }
 }
 
-my $foo;                # simple identifiers
-say Foo::Bar.baz;       # Calling a method; OUTPUT: «Þor is mighty␤»
+my $foo;               # simple identifiers
+say Foo::Bar.baz;      # Calling a method; OUTPUT: «Þor is mighty␤»
 say Foo::Bar::zape;    # compound identifiers separated by ::; OUTPUT: «zipi␤»
 my $bar = 'Bar';
-say $Foo::($bar)::quux; # compound identifiers with interpolations; OUTPUT: «42␤»
-$42;                    # numeric names
-$!;                     # certain punctuation variables
+say $Foo::($bar)::quux;# compound identifiers with interpolations; OUTPUT: «42␤»
+$42;                   # numeric names
+$!;                    # certain punctuation variables
 =end code
 
 X<|::,package>
@@ -73,13 +74,12 @@ X«|MY (package)»X«|OUR (package)»X«|CORE (package)»X«|GLOBAL (package)»X
 The following pseudo-package names are reserved at the front of a name:
 
 =begin table
-    MY          Symbols in the current lexical scope (aka $?SCOPE)
-    OUR         Symbols in the current package (aka $?PACKAGE)
-    CORE        Outermost lexical scope, definition of standard Perl
-    GLOBAL      Interpreter-wide package symbols, really UNIT::GLOBAL
-    PROCESS     Process-related globals (superglobals). The last place dynamic variable
-                lookup will look.
-    COMPILING   Lexical symbols in the scope being compiled
+MY          Symbols in the current lexical scope (aka $?SCOPE)
+OUR         Symbols in the current package (aka $?PACKAGE)
+CORE        Outermost lexical scope, definition of standard Perl
+GLOBAL      Interpreter-wide package symbols, really UNIT::GLOBAL
+PROCESS     Process-related globals (superglobals). The last place dynamic variable lookup will look.
+COMPILING   Lexical symbols in the scope being compiled
 =end table
 
 X«|CALLER (package)»X«|CALLERS (package)»X«|DYNAMIC (package)»X«|OUTER (package)»X«|OUTERS (package)»X«|LEXICAL (package)»X«|UNIT (package)»X«|SETTING (package)»X«|PARENT (package)»X«|CLIENT (package)»
@@ -225,8 +225,9 @@ MyType::<$foo>
 
 =head2 Class member lookup
 
-Methods—including auto-generated methods, such as public attributes' accessors—are stored
-in the class meta object and can be looked up through by the L<lookup|/routine/lookup> method.
+Methods—including auto-generated methods, such as public attributes'
+accessors—are stored in the class meta object and can be looked up through by
+the L<lookup|/routine/lookup> method.
 
 =for code :skip-test
 Str.^lookup('chars')