Revision, grammar and reflow

Author: JJ

doc/Language/5to6-nutshell.pod6

@@ -1119,7 +1119,8 @@ a better choice for grammar reuse.
 
 =head2 Named captures
 
-These work in a slightly different way; also they only work in the latest versions of Perl 5.
+These work in a slightly different way; also they only work in the latest
+versions of Perl 5.
 
 =for code :lang<perl5>
 use v5.22;
@@ -1154,15 +1155,14 @@ differences!
 
 =head2 UNITCHECK becomes CHECK
 
-There is currently B<no> direct equivalent of C<CHECK> blocks in Perl 6.
-The C<CHECK> phaser in Perl 6 has the same semantics as the C<UNITCHECK>
-block in Perl 5: it gets run whenever the compilation unit in which it
-occurs, has finished parsing.  This is considered a much saner semantic
-than the current semantics of C<CHECK> blocks in Perl 5.  But for
-compatibility reasons, it was impossible to change the semantics of C<CHECK>
-blocks in Perl 5, so a C<UNITCHECK> block was introduced in 5.10.  So it
-was decided that the Perl 6 C<CHECK> phaser would follow the saner Perl 5
-C<UNITCHECK> semantics.
+There is currently B<no> direct equivalent of C<CHECK> blocks in Perl 6. The
+C<CHECK> phaser in Perl 6 has the same semantics as the C<UNITCHECK> block in
+Perl 5: it gets run whenever the compilation unit in which it occurs has
+finished parsing.  This is considered a much saner semantic than the current
+semantics of C<CHECK> blocks in Perl 5.  But for compatibility reasons, it was
+impossible to change the semantics of C<CHECK> blocks in Perl 5, so a
+C<UNITCHECK> block was introduced in 5.10.  Consequently, it was decided that
+the Perl 6 C<CHECK> phaser would follow the saner Perl 5 C<UNITCHECK> semantics.
 
 =head2 No block necessary
 
@@ -1178,11 +1178,11 @@ BEGIN my $foo = 42;  # Perl 6
 
 =head2 Changed semantics with regards to precompilation
 
-If you put C<BEGIN> and C<CHECK> phasers in a module that is being
-precompiled, then these phasers will B<only> be executed during precompilation
-and B<not> when a precompiled module is being loaded.  So when porting module
-code from Perl 5, you may need to change C<BEGIN> and C<CHECK> blocks to
-C<INIT> blocks to ensure that they're run when loading that module.
+If you put C<BEGIN> and C<CHECK> phasers in a module that is being precompiled,
+then these phasers will B<only> be executed during precompilation and B<not>
+when a precompiled module is being loaded.  So when porting module code from
+Perl 5, you may need to change C<BEGIN> and C<CHECK> blocks to C<INIT> blocks to
+ensure that they're run when loading that module.
 
 =head1 Pragmas
 
@@ -1195,7 +1195,7 @@ Strict mode is now on by default.
 Warnings are now on by default.
 
 C<no warnings> is currently L<NYI|/language/glossary#NYI>,
-but putting things in a quietly {} block will silence.
+but putting things in a C<quietly> {} block will silence.
 
 =head3 C<autodie>
 
@@ -1281,10 +1281,11 @@ time being, only utf8 for its scripts.
 =head3 C<integer>
 
 Perl pragma to use integer arithmetic instead of floating point.  There is
-no such equivalent in Perl 6.  If you use native integers in your calculations,
+no such thing in Perl 6.  If you use native integers in your calculations,
 then this will be the closest thing.
 
 =for code
+#Perl 6
 my int $foo = 42;
 my int $bar = 666;
 say $foo * $bar;    # uses native integer multiplication
@@ -1382,7 +1383,8 @@ Removed.
 
 =item C<-P> C<-u> C<-U> C<-W> C<-X>
 
-Removed. See L<S19#Removed Syntactic Features|https://design.perl6.org/S19.html#Removed_Syntactic_Features>.
+Removed. See
+L<Removed Syntactic Features|https://design.perl6.org/S19.html#Removed_Syntactic_Features>.
 
 =item C<-w>
 
@@ -1429,16 +1431,18 @@ the C<lines> method on the result of C<slurp> instead:
 
     my @lines = "test-file".IO.slurp.lines;  # also auto-chomps
 
-Also, be aware that $! is not really relevant for file IO operation failures in
-Perl 6. An IO operation that fails will return a failure instead of throwing an
-exception. If you want to return the failure message, it is in the failure
-itself, not in $!. To do similar IO error checking and reporting as in Perl 5:
+Also, be aware that C<$!> is not really relevant for file IO operation failures
+in Perl 6. An IO operation that fails will return a C<Failure> instead of
+throwing an exception. If you want to return the failure message, it is in the
+failure itself, not in C<$!>. To do similar IO error checking and reporting as
+in Perl 5:
 
     my $fh = open('./bad/path/to/file', :w) or die $fh;
 
-Note: $fh instead of $!. Or, you can set $_ to the failure and die with $_:
+I<Note>: C<$fh> instead of C<$!>. Or, you can set C<$_> to the failure and die
+with $_:
 
-    my $fh = open('./bad/path/to/file', :w) orelse .die;
+    my $fh = open('./bad/path/to/file', :w) orelse .die; # Perl 6
 
 Any operation that tries to use the failure will cause the program to fault and
 terminate. Even just a call to the C<.self> method is sufficient.
@@ -1454,7 +1458,7 @@ my $arg = 'Hello';
 my $captured = `echo \Q$arg\E`;
 my $captured = qx(echo \Q$arg\E);
 
-Or using String::ShellQuote (because C<\Q…\E> is not completely right):
+Or using C<String::ShellQuote> (because C<\Q…\E> is not completely right):
 
 =for code :lang<perl5>
 my $arg = shell_quote 'Hello';
@@ -1477,7 +1481,7 @@ But beware that in this case there is B<no protection at all>! C<run> does
 not use the shell, so there is no need to escape the arguments (arguments
 are passed directly). If you are using C<shell> or C<qqx>, then everything
 ends up being one long string which is then passed to the shell. Unless you
-validate your arguments very carefully, there is a high chance to introduce
+validate your arguments very carefully, there is a high chance of introducing
 shell injection vulnerabilities with such code.
 
 =head1 Environment variables
@@ -1541,7 +1545,7 @@ In Perl 6 becomes a simple
 
 Gone.
 
-The Perl 6 design allows for automatic transparent saving-and-loading of
+The Perl 6 design allows for automatic and transparent saving-and-loading of
 compiled bytecode.
 
 Rakudo supports this only for modules so far.