Eliminates a few categories

But some of the others mentioned in #1410 might still be
useful. Phasers and Asynchronous phasers, for example.

Also some reflow.

Author: JJ

doc/Language/ipc.pod6

@@ -5,11 +5,11 @@
 =SUBTITLE Programs running other programs and communicating with them
 
 X<|IPC>
+=head1 X<Running programs>
 
-=head1 X<running|running programs>
-
-Many programs need to be able to run other programs. Running a program in Perl 6
-is as easy as:
+Many programs need to be able to run other programs, and we need to pass
+information to them and receive their output and exit status. Running a program
+in Perl 6 is as easy as:
 
     run 'git', 'status';
 
@@ -25,11 +25,11 @@ on.
 
 Caution should be taken when using C<shell> with user input.
 
-=head1 X<proc|Proc object>
+=head1 The C<Proc> object
 
 Both C<run> and C<shell> return a L<Proc|/type/Proc> object, which can be used
-to communicate with the process in more detail. Please note that unless you close
-all output pipes, the program will usually not terminate.
+to communicate with the process in more detail. Please note that unless you
+close all output pipes, the program will usually not terminate.
 
     my $git = run 'git', 'log', '--oneline', :out;
     for $git.out.lines -> $line {
@@ -63,7 +63,7 @@ and check the exitcode.
         say 'something went wrong';
     }
 
-=head1 X<async|Proc::Async object>
+=head1 The C<Proc::Async> object
 
 When you need more control over the communication with and from another process,
 you will want to make use of L<Proc::Async|/type/Proc::Async>. This class
@@ -87,9 +87,9 @@ ability to send signals to that program.
     await $done;
     =end code
 
-Here is a small program that uses the "tail" program to print out the contents
-of the log named C<system.log> for 10 seconds and then tells the program to stop
-with a QUIT signal.
+The small program above uses the "tail" program to print out the contents of the
+log named C<system.log> for 10 seconds and then tells the program to stop with a
+QUIT signal.
 
 Whereas C<Proc> provides access to output using C<IO::Handle>s, C<Proc::Async>
 provides access using asynchronous supplies (see L<Supply|/type/Supply>).

doc/Language/phasers.pod6

@@ -14,8 +14,11 @@ automatically called at the appropriate moment. These auto-called blocks are
 known as I<phasers>, since they generally mark the transition from one phase of
 computing to another. For instance, a C<CHECK> block is called at the end of
 compiling a compilation unit. Other kinds of phasers can be installed as well;
-these are automatically called at various times as appropriate, and some of
-them respond to various control exceptions and exit values. For instance, some phasers might be called if the exit from a block is successful or not, with I<success> in this case defined by returning with a defined value or list without any C<Failure> or exception in the process.
+these are automatically called at various times as appropriate, and some of them
+respond to various control exceptions and exit values. For instance, some
+phasers might be called if the exit from a block is successful or not, with
+I<success> in this case defined by returning with a defined value or list
+without any C<Failure> or exception in the process.
 
 Here is a summary:
 
@@ -93,8 +96,9 @@ handlers are supposed to reduce uncertainty, not increase it.)
 
 X<|Phasers, will trait>
 Some of these phasers also have corresponding traits that can be set on
-variables; they use C<will> followed by the name of the phaser in lowercase. These have the advantage of passing the variable in question into
-the closure as its topic:
+variables; they use C<will> followed by the name of the phaser in lowercase.
+These have the advantage of passing the variable in question into the closure as
+its topic:
 
     our $h will enter { .rememberit() } will undo { .forgetit() };
 
@@ -444,8 +448,9 @@ with C<tap>.
 
 =head2 X<DOC|Asynchronous Phasers, DOC>
 
-The phasers C<BEGIN>, C<CHECK> and C<INIT> are run only in documentation mode when
-prefixed with the C<DOC> keyword. The compiler is in documentation when run with C<--doc>.
+The phasers C<BEGIN>, C<CHECK> and C<INIT> are run only in documentation mode
+when prefixed with the C<DOC> keyword. The compiler is in documentation when run
+with C<--doc>.
 
   DOC INIT { say 'init'  }  # prints 'init' at initialization time when in documentation mode.