Text reflow and ...

Also added "If everything was fine with your dist, you should see your module tar
file in your C<Perl6> directory along with both a meta and a readme file named
after your module filename." to the "Upload your module to CPAN" section.

Author: uzluisf

doc/Language/modules.pod6

@@ -54,7 +54,8 @@ N<As L<synopsis S11|https://design.perl6.org/S11.html#Units> says: Confusing? Ye
 directory for executable programs and scripts.
 
 Source files generally use the C<.pm6> extension, and scripts or
-executables use the C<.p6>. Test files use the C<.t> extension. Files which contain documentation use the C<.pod6> extension.
+executables use the C<.p6>. Test files use the C<.t> extension. Files which
+contain documentation use the C<.pod6> extension.
 
 X<|compunit>
 =head2 Loading and basic importing
@@ -233,7 +234,8 @@ Bar;" to your code.
 =head3 is export
 
 Packages, subroutines, variables, constants and enums are exported by marking
-them with the L<is export> trait (also note the tags available for indicating authors and versions).
+them with the L<is export> trait (also note the tags available for indicating
+authors and versions).
 
     =begin code :skip-test
     unit module MyModule:ver<1.0.3>:auth<John Hancock (jhancock@example.com)>;
@@ -529,7 +531,8 @@ followed.
 =head1 Distributing modules
 
 If you've written a Perl 6 module and would like to share it with the
-community, we'd be delighted to have it listed in the L<Perl 6 modules directory|https://modules.perl6.org>. C<:)>
+community, we'd be delighted to have it listed in the
+L<Perl 6 modules directory|https://modules.perl6.org>. C<:)>
 
 Currently there are two different module ecosystems (module distribution
 networks) available:
@@ -669,12 +672,16 @@ Make your X<C<META6.json>|META6.json> file look something like this:
 =end code
 
 For choosing a version numbering scheme, try and use
-"major.minor.patch" (see L<the spec on versioning | https://design.perl6.org/S11.html#Versioning> for further
-details). This will go into the C<version> key of C<META6.json>.
+"major.minor.patch"
+(see L<the spec on versioning | https://design.perl6.org/S11.html#Versioning>
+for further details). This will go into the C<version> key of C<META6.json>.
 
-The C<name> key is compulsory, and C<zef> will fail if you do not include it. Even if you have created a META6.json file just to express the dependencies for a series of scripts, this section must be included.
+The C<name> key is compulsory, and C<zef> will fail if you do not include it.
+Even if you have created a META6.json file just to express the dependencies
+for a series of scripts, this section must be included.
 
-The C<auth> section identifies the author in GitHub or other repository hosting site, such as Bitbucket.
+The C<auth> section identifies the author in GitHub or other repository
+hosting site, such as Bitbucket.
 
 The C<authors> section includes a list of all the module authors. In
 the case there is only one author, a single element list must be
@@ -689,28 +696,35 @@ Set C<perl> version to the minimum perl version your module works with.
 
 Optionally, you can set an C<api> field. Incrementing this indicates that
 the interface provided by your module is not backwards compatible with a
-previous version. You can use it if you want to adhere to L<Semantic Versioning | https://semver.org>. Simply keep the C<api> field to the same value as
-your major version number. A dependency can then depend on your module by
-including a C<:api> part, which will ensure backwards incompatible releases
-will not be pulled in.
-
-The C<resources> section is optional, but, if present, should contain a
-list of the files in your C<resources> directory that you wish to be
-installed. These will be installed with hashed names alongside your
-library files and their installed location can be determined through the
-C<%?RESOURCES> C<Hash> indexed on the name provided. C<tags> is also optional, but is used to describe the module in the Perl 6 ecosystem.
-
-C<depends>, C<build-depends> and C<test-depends> include different modules that are used in those phases of the of installation. The last two are optional, but convenient.
-
-Finally, C<source-url> indicates the URL of the repository where the module is developed.
+previous version. You can use it if you want to adhere to
+L<Semantic Versioning | https://semver.org>. Simply keep the C<api> field to
+the same value as your major version number. A dependency can then depend on
+your module by including a C<:api> part, which will ensure backwards
+incompatible releases will not be pulled in.
+
+The C<resources> section is optional, but, if present, should contain a list
+of the files in your C<resources> directory that you wish to be installed.
+These will be installed with hashed names alongside your library files and
+their installed location can be determined through the C<%?RESOURCES> C<Hash>
+indexed on the name provided. C<tags> is also optional, but is used to describe
+the module in the Perl 6 ecosystem.
+
+C<depends>, C<build-depends> and C<test-depends> include different modules that
+are used in those phases of the of installation. The last two are optional, but
+convenient.
+
+Finally, C<source-url> indicates the URL of the repository where the module is
+developed.
 
 The L<Test::META module | https://github.com/jonathanstowe/Test-META/>
 can help you check the correctness of the META6.json file.
 
-There are more fields described in the L<META design documents |https://design.perl6.org/S22.html#META6.json>, but not all of these are
-implemented by existing package managers. Hence you should stick to the
-fields described in the above example block to ensure compatibility with
-existing package managers. You can also check L<Moritz Lenz's repository of all modules for examples|https://github.com/moritz/perl6-all-modules/search?l=JSON&q=META6.json&type=>.
+There are more fields described in the
+L<META design documents |https://design.perl6.org/S22.html#META6.json>, but not
+all of these are implemented by existing package managers. Hence you should
+stick to the fields described in the above example block to ensure compatibility
+with existing package managers. You can also check
+L<Moritz Lenz's repository of all modules for examples|https://github.com/moritz/perl6-all-modules/search?l=JSON&q=META6.json&type=>.
 
 =end item
 
@@ -758,11 +772,13 @@ L<Upload a file to CPAN|https://pause.perl.org/pause/authenquery?ACTION=add_uri>
 
     =item Make sure you select C<Perl6> as the I<Target Directory>. For
     your first upload, you have to enter the string C<Perl6> in the text field.
-    On subsequent uploads, you can select the C<Perl6> directory from select
-    box above the input field.
+    On subsequent uploads, you can select the C<Perl6> directory from the
+    selection box right below the input field.
 
     =begin item
-    Select your file and click I<Upload>!
+    Select your file and click I<Upload>! If everything was fine with your
+    dist, you should see your module tar file in your C<Perl6> directory along
+    with both a meta and a readme file named after your module filename.
 
     I<Make sure you have a META6.json file in your dist and that the dist
     version you're uploading is higher than the currently uploaded version.
@@ -811,7 +827,8 @@ zef install Vortex::TotalPerspective
 =end code
 
 This will download your module to its own working directory (C<~/.zef>),
-build it there, and install the module into your local Perl 6 installation directory.
+build it there, and install the module into your local Perl 6 installation
+directory.
 
 To use C<Vortex::TotalPerspective> from your scripts, just write
 C<use Vortex::TotalPerspective>, and your Perl 6 implementation will