Additional suggestios by MasterDuke++

Author: lizmat

doc/Language/create-cli.pod6

@@ -71,8 +71,8 @@ Usage:
   hello.p6 <name>
 =end code
 
-However, if give a default value for the parameter, running the script either
-with or without specifying a name will always work:
+However, if you give a default value for the parameter, running the script
+either with or without specifying a name will always work:
 
     # inside file 'hello.p6'
     sub MAIN($name = 'bashful') {
@@ -96,9 +96,9 @@ Another way to do this, is to make sub MAIN a C<multi sub>:
     multi sub MAIN($name) { say "Hello $name, how are you?"   }
 
 Which would give the same output as the examples above.  Whether you should
-use either method to achive the desired goal, is entirely up to you.
+use either method to achieve the desired goal, is entirely up to you.
 
-A more complicated example using a single positional parameter,  multiple
+A more complicated example using a single positional and  multiple
 named parameters:
 
     # inside "frobnicate.p6"
@@ -169,9 +169,10 @@ Usage:
 =head2 C<%*SUB-MAIN-OPTS>
 
 It's possible to alter how arguments are processed before they're passed
-to C<sub MAIN {}> by setting options in C<%*SUB-MAIN-OPTS> hash.  Due to the
-nature of dynamic variables, it is required to set up C<%*SUB-MAIN-OPTS>
-hash and fill it with the appropriate settings.  For instance:
+to C<sub MAIN {}> by setting options in the C<%*SUB-MAIN-OPTS> hash.  Due to
+the nature of dynamic variables, it is required to set up the
+C<%*SUB-MAIN-OPTS> hash and fill it with the appropriate settings.
+For instance:
 
     my %*SUB-MAIN-OPTS =
       :named-anywhere,    # allow named variables at any location
@@ -272,11 +273,11 @@ the compiler will output a default generated usage message.
     EOH
     }
 
-The default usage message is available inside C<sub USAGE> via read-only
+The default usage message is available inside C<sub USAGE> via the read-only
 C<$*USAGE> variable. It will be generated based on available C<sub MAIN>
-candidates and their parameters. As shown before, You can specify additional
-extended description for each candidate using C<#|(...)> Pod block to set
-L«C<WHY>|/routine/WHY».
+candidates and their parameters. As shown before, you can specify an
+additional extended description for each candidate using a 
+C<#|(...)> Pod block to set L«C<WHY>|/routine/WHY».
 
 =end pod