Improving a bit indexing and other things, refs #3673

Author: JJ

doc/Language/create-cli.pod6

@@ -219,7 +219,7 @@ raku MAIN-enum.raku FLAG_BAR
 but will die if called with something that is not a C<Flag>.
 
 X<|%*SUB-MAIN-OPTS>
-=head2 %*SUB-MAIN-OPTS
+=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 the C<%*SUB-MAIN-OPTS> hash. Due to
@@ -238,7 +238,7 @@ For instance:
 Available options are:
 
 X<|named-anywhere>
-=head3 named-anywhere
+=head3 C<named-anywhere>
 
 By default, named arguments passed to the program (i.e., C<MAIN>)
 cannot appear after any positional argument. However, if
@@ -250,8 +250,8 @@ the above program can be called with:
 $ raku example.raku 1 --c=2 3 --d=4
 =end code
 
-X<|bundling>
-=head3 bundling
+X<|command-line argument bundling>
+=head3 C<bundling>
 
 When C«%*SUB-MAIN-OPTS<bundling>» is set to a true value, single letter named
 arguments can be bundled together with a single dash. The following two
@@ -262,7 +262,8 @@ $ raku example.raku -a -b -c
 $ raku example.raku -abc
 =end code
 
-Bundled arguments can neither be negated, nor assigned a value though:
+Bundled arguments can be understood as flags, that can neither be negated, nor
+assigned a value though:
 
 =begin code :lang<shell>
 $ raku example.raku -/a       # OK
@@ -271,8 +272,10 @@ $ raku example.raku -abc=asdf # Error
 $ raku example.raku -/abc     # Error
 =end code
 
+This option is only available starting in the 2020.10 release.
+
 X<|hidden-from-USAGE>
-=head2 is hidden-from-USAGE
+=head2 C<is hidden-from-USAGE>
 
 Sometimes you want to exclude a C<MAIN> candidate from being shown in any
 automatically generated usage message. This can be achieved by adding