Reflow and rephrasing

Author: JJ

doc/Language/5to6-nutshell.pod6

@@ -1541,10 +1541,10 @@ module like so:
 =for code :lang<perl5>
 use ModuleName qw{foo bar baz};
 
-In Perl 6 one specifies the functions which are to be exported by using the
-C<is export> role on the relevant subs and I<all> subs with this role are
-then exported.  Hence, the following module C<Bar> exports the subs C<foo>
-and C<bar> but not C<baz>:
+In Perl 6 one specifies the functions which are to be exported by using
+the C<is export> role on the relevant subs; I<all> subs with this role
+are then exported.  Hence, the following module C<Bar> exports the subs
+C<foo> and C<bar> but not C<baz>:
 
 =begin code :solo
 unit module Bar;
@@ -1566,11 +1566,11 @@ If one tries to use C<baz> an "Undeclared routine" error is raised at
 compile time.
 
 So, how does one recreate the Perl 5 behaviour of being able to
-selectively import functions? For this one needs to define an C<EXPORT>
-sub inside the module which specifies the functions to be exported and
-remove the C<module Bar> statement.
+selectively import functions? By defining an C<EXPORT> sub inside the
+module which specifies the functions to be exported and removing the
+C<module Bar> statement.
 
-The module C<Bar> now is merely a file called C<Bar.pm6> with the
+The former module C<Bar> now is merely a file called C<Bar.pm6> with the
 following contents:
 
 =begin code :preamble<no strict;>
@@ -1594,8 +1594,8 @@ sub baz($z) { say "baz, $z" }
 =end code
 
 Note that the subs are no longer explicitly exported via the C<is
-export> role.  We are defining an C<EXPORT> sub which specifies the subs
-in the module we want to be available for export and then we are
+export> role, but by an C<EXPORT> sub which specifies the subs
+in the module we want to make available for export and then we are
 populating a hash containing the subs which will actually be exported.
 The C<@import-list> is set by the C<use> statement in the calling code
 thus allowing us to selectively import the subs made available by the
@@ -1608,7 +1608,7 @@ calling code:
 use Bar <foo>;
 foo(1);       #=> "foo 1"
 
-Here we see that even though C<bar> is able to be exported, if we don't
+Here we see that even though C<bar> is exportable, if we don't
 explicitly import it, it's not available for use.  Hence this causes an
 "Undeclared routine" error at compile time:
 
@@ -1617,33 +1617,34 @@ use Bar <foo>;
 foo(1);
 bar(5);       #!> "Undeclared routine: bar used at line 3"
 
-however, this will work
+However, this will work
 
 =for code :skip-test
 use Bar <foo bar>;
 foo(1);       #=> "foo 1"
 bar(5);       #=> "bar 5"
 
-Note also that C<baz> remains unimportable even if specified in the C<use>
-statement:
+Note also that C<baz> remains unimportable even if specified in the
+C<use> statement:
 
 =for code :skip-test
 use Bar <foo bar baz>;
 baz(3);       #!> "Undeclared routine: baz used at line 2"
 
-In order to get this to work, one obviously has to jump through many hoops.
-In the standard use-case where one specifies the functions to be exported
-via the C<is export> role, Perl 6 automatically creates the C<EXPORT> sub in
-the correct manner for you, so one should consider very carefully whether or
-not writing one's own C<EXPORT> routine is worthwhile.
+In order to get this to work, one obviously has to jump through many
+hoops. In the standard use-case where one specifies the functions to be
+exported via the C<is export> role, Perl 6 automatically creates the
+C<EXPORT> sub in the correct manner for you, so one should consider very
+carefully whether or not writing one's own C<EXPORT> routine is
+worthwhile.
 
 =head2 Importing groups of specific functions from a module
 
 If you would like to export groups of functions from a module, you just
-need to assign names to the groups, and the rest will work automagically.
-When you specify C<is export> in a sub declaration, you are in fact adding
-this subroutine to the C<:DEFAULT> export group.  But you can add a subroutine
-to another group, or to multiple groups:
+need to assign names to the groups, and the rest will work
+automagically. When you specify C<is export> in a sub declaration, you
+are in fact adding this subroutine to the C<:DEFAULT> export group.  But
+you can add a subroutine to another group, or to multiple groups:
 
 =for code :solo
 unit module Bar;