As per comments from @ugexe, I have:

-	Removed references to P6C and CPAN
-	Changed compunit to module where appropriate

Author: wayland

doc/Language/distributions/configuration-structure.rakudoc

@@ -222,8 +222,8 @@ In general, the array form will be more than enough for most cases.
 The C<README.md> file is a
 L<markdown-formatted|https://help.github.com/articles/markdown-basics/>
 text file, which will later be automatically rendered as HTML by GitHub/GitLab for modules kept
-in those ecosystems or by L<raku.land|https://raku.land> website for modules
-kept on L<CPAN|/language/faq#index-entry-CPAN_(FAQ)>.
+in those places, or by L<raku.land|https://raku.land> website for modules
+accessible with L<zef|/language/faq#Is_there_a_repository_of_third_party_library_modules_for_Raku?>.
 
 =head3 The C<LICENSE> file and key
 

doc/Language/distributions/introduction.rakudoc

@@ -4,6 +4,30 @@
 
 =SUBTITLE Distributions and How they Work
 
+=head2 Terminology
+
+This is a point in the Raku journey where we need to get specific with some of
+the terminology, so here are some of the terms which will be used:
+
+=item1 B<compunit>: A compilation unit, or compunit for short, is a piece of 
+Raku code that is analyzed and compiled as a single unit. Typically, this 
+comes from a source file on disk, but what's inside an EVAL also counts as 
+such.
+
+=item1 B<script>: A script refers to a compilation unit that is provided to 
+Raku as the entry point for execution. In an invocation like raku foo.raku, 
+we say that foo.raku is first compiled and then executed. In Rakudo Raku, in 
+this case, the results of the compilation only exist in memory.
+
+=item1 B<module>: A module refers to a compilation unit that is used by a 
+script, or by another module used from a script. A module must also be 
+compiled before it can be made use of. (There is nothing preventing a given 
+source file serving as both a script and a module depending on how it is used).
+
+=item1 B<distribution>: A distribution is a set of zero or more scripts and 
+modules that are released together, along with some meta-data and potentially 
+resources and tests.
+
 =head2 Basic structure
 
 Module distributions (in the I<set of related source files> sense) in Raku
@@ -30,23 +54,23 @@ different files. In addition, when a C<distribution> is published (see
 L<Distributing modules|/language/distributions/introduction>) it may be
 necessary to provide access to other resources, such as callable utilities.
 
-B<Raku> also allows for a single distribution to provide multiple C<compunit>s
+B<Raku> also allows for a single distribution to provide multiple C<module>s
 that can be C<use>d (or C<require>d etc). The information about a distribution
 is contained in the C<META6.json> file in the distribution's root directory. See
 below for more about C<META6.json>. Each entity that the B<distribution> allows
-to be C<use>d (or C<require>d etc), also called a C<compunit>, is placed in the
+to be C<use>d (or C<require>d etc), also called a C<module>, is placed in the
 C<provides> section of the C<META6.json> (as specified below).
 
 It should also be noted that when writing the C<depends> section of the
 C<META6.json> file, it is the name of the B<distribution> that is listed, not
-the name of the C<compunit> that is desired. Although, for very many entities,
-the name of the I<distribution> and the name of the I<compunit> are the same.
+the name of the C<module> that is desired. Although, for very many entities,
+the name of the I<distribution> and the name of the I<module> are the same.
 Another global effect of the C<depends> list in a distribution made available to
-the Ecosystem, is that package managers, e.g. C<zef>, can look for C<compunit>
+the Ecosystem, is that package managers, e.g. C<zef>, can look for C<module>
 names in all distributions available.
 
 Given this arrangement, the B<rakudo> compiler, or a package manager such as
-B<zef>, can obtain all the information needed about each C<compunit> from a
+B<zef>, can obtain all the information needed about each C<module> from a
 C<META6.json> file in a directory.
 
 =head2 Contact information

doc/Language/distributions/testing.rakudoc

@@ -5,7 +5,7 @@
 =SUBTITLE Testing your distribution of modules
 
 This also means that a testing program such as B<Perl>'s C<prove> or the B<Raku>
-equivalent L<prove6|https://raku.land/cpan:LEONT/App::Prove6> can be
+equivalent L<prove6|https://raku.land/zef:leont/App::Prove6> can be
 run in the root directory of the B<distribution> as, e.g.,
 
 =for code :lang<shell>

doc/Language/distributions/tools.rakudoc

@@ -15,7 +15,7 @@ of a distribution of modules.
 
 =item L<App::Mi6|https://raku.land/zef:skaji/App::Mi6>     Minimal authoring tool for Raku
 =item L<META6|https://raku.land/zef:jonathanstowe/META6>        Do things with Raku C<META> files
-=item L<rakudoc|https://raku.land/cpan:SOFTMOTH/rakudoc>        Generate documentation end-products
+=item L<rakudoc|https://raku.land/zef:coke/rakudoc>        Generate documentation end-products
 
 =head1 Distribution Testing Tools
 

doc/Language/distributions/uploading.rakudoc

@@ -8,24 +8,13 @@ If you've written a Raku module and would like to share it with the
 community, we'd be delighted to have it listed in the
 L<Raku modules directory|https://raku.land>. C<:)>
 
-Currently, there are three ways to distribute a module. No matter which method
-you choose, your module will be indexed on the L<raku.land|https://raku.land>
-and L<raku.land|https://raku.land> websites. The three module
-distribution networks, or ecosystems, are:
+There have been three ways to distribute a module, but the CPAN and P6C ways 
+have been deprecated; please use the zef/fez method instead.  However, no 
+matter the method, all modules will be indexed on the L<raku.land|https://raku.land>
+L<raku.land|https://raku.land> website. 
 
-=item B<zef ecosystem> using the L<C<fez> module uploader|https://raku.land/zef:tony-o/fez>
-utility. Use of the C<fez> command is
-the newest and perhaps easiest way to distribute your module and is growing in
-popularity.
-
-=item B<CPAN>
-This is the same ecosystem Perl is using. Modules are uploaded as I<.zip>
-or I<.tar.gz> files on L<PAUSE|https://pause.perl.org/>.
-
-=item B<p6c>
-Up until recently the only ecosystem. It is based
-on Github repositories which are directly accessed. It has only limited
-capability for versioning.
+The B<zef ecosystem> uses the L<C<fez> module uploader|https://raku.land/zef:tony-o/fez>
+utility. Use of the C<fez> command is the way to distribute your module.
 
 The process of sharing your module consists of two steps, preparing the module,
 and uploading the module to one of the ecosystems mentioned above.
@@ -72,90 +61,6 @@ one module), only B<one> upload of a distribution per version is permitted. If a
 code in a repository, the changes will not be reflected in the C<fez> system. So changes to code must be
 accompanied by a bump in the version number and the new version uploaded to C<fez>.
 
-=head1 Upload your module to CPAN
-
-A prerequisite for using CPAN is a L<PAUSE|https://pause.perl.org/>
-user account. If you don't have an account already, you can create one
-L<here|https://pause.perl.org/pause/query?ACTION=request_id>
-The process takes about 5 minutes and some e-mail back and forth.
-
-=begin item
-Create a package of your module:
-
-=begin code :lang<shell>
-cd your-module-folder
-tar czf Vortex-TotalPerspective-0.0.1.tar.gz \
-  --transform s/^\./Vortex-TotalPerspective-0.0.1/ --exclude-vcs\
-  --exclude=.[^/]*
-=end code
-
-If you use git you can also use the following command to create a package
-directly for a given commit.
-
-=begin code :lang<shell>
-git archive --prefix=Vortex-TotalPerspective-0.0.1/ \
-  -o ../Vortex-TotalPerspective-0.0.1.tar.gz HEAD
-=end code
-
-=end item
-
-=item Go to L<PAUSE|https://pause.perl.org/>, log in and navigate to
-C<Upload a file to CPAN>.
-
-=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 the
-    selection box right below the input field.
-
-=begin item
-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 C<META> and a C<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.
-Those are the most common upload errors.>
-
-=end item
-
-=head2 Upload your module to p6c
-
-The Raku community is migrating to the I<fez> ecosystem (see above). For developers
-who have modules on the I<p6c> ecosystem and migrated them to I<fez>, please remove them
-from the I<p6c> ecosystem. If you do not have the commit bit, open a pull request or ping someone on IRC
-(#raku at libera.chat) to get help.
-
-If you want to use the I<p6c> ecosystem you need to use git for your module's
-version control. The instructions herein assume that you have a
-L<GitHub|https://github.com> account so that your module can be shared from its
-GitHub repository, however another provider such as
-L<GitLab|https://about.gitlab.com/> should work as long as it works in a
-similar way.
-
-=item Put your project under git version control if you haven't done so
-already.
-
-=item Once you're happy with your project, create a repository for it on GitHub.
-See L<GitHub's help docs|https://help.github.com/> if necessary. Your
-GitHub repository should be named the same as your project directory. Immediately
-after creating the GitHub repo, GitHub shows you how to configure your
-local repository to know about your GitHub repository.
-
-=item Push your project to GitHub.
-
-=item Consider setting up automated testing.
-One option is to use the github workflows functionality, and an example can be found for the
-L<Mi6-Helper App|https://github.com/tbrowder/Mi6-Helper/blob/master/.github/workflows>.
-
-=item Create a PR (Pull Request) on L<ecosystem|https://github.com/Raku/ecosystem> adding
-your module to META.list, or ping someone on IRC (#raku at libera.chat) to
-get help having it added.
-
-=item After the pull request has been accepted, wait for an hour. If
-your module doesn't show up on L<https://raku.land/>, please
-view the log file to see if it identifies an error with your module or
-C<meta> file.
-
 B<That's it! Thanks for contributing to the Raku community!>
 
 If you'd like to try out installing your module, use the X<zef|Reference,zef> module
@@ -174,4 +79,3 @@ C<use Vortex::TotalPerspective>, and your Raku implementation will
 know where to look for the module file(s).
 
 =end pod
-