Reflow and eliminate index, refs #2304

Author: JJ

doc/Language/5to6-nutshell.pod6

@@ -5,36 +5,36 @@
 =SUBTITLE How do I do what I used to do? (Perl 6 in a nutshell)
 
 This page attempts to provide a fast-path to the changes in syntax and
-semantics from Perl 5 to Perl 6. Whatever worked in Perl 5 and must be written
-differently in Perl 6, should be listed here (whereas many I<new> Perl 6
-features and idioms are not).
+semantics from Perl 5 to Perl 6. Whatever worked in Perl 5 and must be
+written differently in Perl 6, should be listed here (whereas many
+I<new> Perl 6 features and idioms are not).
 
-Hence this should not be mistaken for a beginner tutorial or a promotional
-overview of Perl 6; it is intended as a technical reference for Perl 6
-learners with a strong Perl 5 background and for anyone porting Perl 5 code
-to Perl 6 (though note that L<#Automated translation> might be more
-convenient).
+Hence this should not be mistaken for a beginner tutorial or a
+promotional overview of Perl 6; it is intended as a technical reference
+for Perl 6 learners with a strong Perl 5 background and for anyone
+porting Perl 5 code to Perl 6 (though note that L<#Automated
+translation> might be more convenient).
 
 A note on semantics; when we say "now" in this document, we mostly just
 mean "now that you are trying out Perl 6."  We don't mean to imply that
 Perl 5 is now suddenly obsolete.  Quite the contrary, most of us love
 Perl 5, and we expect Perl 5 to continue in use for a good many years.
-Indeed, one of our more important goals has been to make interaction between
-Perl 5 and Perl 6 run smoothly.  However, we do also like the design
-decisions in Perl 6, which are certainly newer and arguably better
-integrated than many of the historical design decisions in Perl 5.
-So many of us do hope that over the next decade or two, Perl 6 will
+Indeed, one of our more important goals has been to make interaction
+between Perl 5 and Perl 6 run smoothly.  However, we do also like the
+design decisions in Perl 6, which are certainly newer and arguably
+better integrated than many of the historical design decisions in Perl
+5. So many of us do hope that over the next decade or two, Perl 6 will
 become the more dominant language.  If you want to take "now" in that
 future sense, that's okay too.  But we're not at all interested in the
 either/or thinking that leads to fights.
 
 =head1 CPAN
 
-See L<https://modules.perl6.org/> .
+See L<https://modules.perl6.org/>.
 
-If the module that you were using has not been converted to Perl 6, and no
-alternative is listed in this document, then its use under Perl 6 may not
-have been addressed yet.
+If the module that you were using has not been converted to Perl 6, and
+no alternative is listed in this document, then its use under Perl 6 may
+not have been addressed yet.
 
 The L<Inline::Perl5|https://github.com/niner/Inline-Perl5/> project makes
 it possible to C<use> Perl 5 modules directly from Perl 6 code by using
@@ -1477,10 +1477,9 @@ The L«C<FALLBACK> method|/language/typesystem#index-entry-FALLBACK_(method)»
 provides similar functionality.
 
 =head2 Importing specific functions from a module
-X<|import>
 
-In Perl 5 it is possible to selectively import functions from a given module
-like so:
+In Perl 5 it is possible to selectively import functions from a given
+module like so:
 
 =for code :lang<perl5>
 use ModuleName qw{foo bar baz};
@@ -1498,23 +1497,24 @@ sub bar($b) is export { say "bar $b" }
 sub baz($z) { say "baz $z" }
 =end code
 
-To use this module, simply C<use Bar> and the functions C<foo> and C<bar>
-will be available
+To use this module, simply C<use Bar> and the functions C<foo> and
+C<bar> will be available
 
 =for code :skip-test
 use Bar;
 foo(1);    #=> "foo 1"
 bar(2);    #=> "bar 2"
 
-If one tries to use C<baz> an "Undeclared routine" error is raised at compile time.
+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.
+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.
 
-The module C<Bar> now is merely a file called C<Bar.pm> with the following
-contents:
+The module C<Bar> now is merely a file called C<Bar.pm> with the
+following contents:
 
 =begin code :preamble<no strict;>
 use v6.c;
@@ -1538,14 +1538,16 @@ sub bar($a) { say "bar, $a" }
 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 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 module.
+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
+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
+module.
 
-So, to import only the C<foo> routine, we do the following in the calling code:
+So, to import only the C<foo> routine, we do the following in the
+calling code:
 
 =for code :skip-test
 use Bar <foo>;