use same search category for all phasers

Author: coke

doc/Language/phasers.pod6

@@ -172,13 +172,13 @@ teardown usually want to happen in the opposite order from each other.
 
 =head1 Program Execution Phasers
 
-=head2 X<BEGIN|BEGIN (phasers)>
+=head2 X<BEGIN|Phasers>
 
 Runs at compile time, as soon as possible, only runs once.
 
 Can have a return value that is provided even in later phases.
 
-=head2 X<CHECK|CHECK (phasers)>
+=head2 X<CHECK|Phasers>
 
 Runs at compile time, As late as possible, only runs once.
 
@@ -188,7 +188,7 @@ Code that is generated at run time can still fire off C<CHECK> and C<INIT>
 phasers, though of course those phasers can't do things that would require
 travel back in time. You need a wormhole for that.
 
-=head2 X<LINK|LINK (phasers)>
+=head2 X<LINK|Phasers>
 
 Runs at link time, As late as possible, only runs once.
 
@@ -197,7 +197,7 @@ Can have a return value that is provided even in later phases.
 The compiler is free to ignore C<LINK> phasers compiled at run time since
 they're too late for the application-wide linking decisions.
 
-=head2 X<INIT|INIT (phasers)>
+=head2 X<INIT|Phasers>
 
 Runs after compilation during main execution, as soon as possible, only runs
 once.
@@ -215,7 +215,7 @@ travel back in time. You need a wormhole for that.
 
 An C<INIT> only runs once for all copies of a cloned closure.
 
-=head2 X<END|END (phasers)>
+=head2 X<END|Phasers>
 
 Runs after compilation during main execution, as late as possible, only runs
 once.
@@ -225,7 +225,7 @@ treated as if declared at C<use> time in the using module. (It is erroneous to
 depend on this order if the module is used more than once, however, since the
 phasers are only installed the first time they're noticed.)
 
-=head2 X<CLOSE|CLOSE (phasers)>
+=head2 X<CLOSE|Phasers>
 
 Appears in a supply block. Called when the supply is closed.
 
@@ -251,7 +251,7 @@ All of these phaser blocks can see any previously declared lexical variables,
 even if those variables have not been elaborated yet when the closure is
 invoked (in which case the variables evaluate to an undefined value.)
 
-=head2 X<ENTER|ENTER (phasers)>
+=head2 X<ENTER|Phasers>
 
 Runs at every block entry time, repeats on loop blocks.
 
@@ -260,7 +260,7 @@ Can have a return value that is provided even in later phases.
 An exception thrown from an C<ENTER> phaser will abort the C<ENTER> queue, but
 one thrown from a C<LEAVE> phaser will not.
 
-=head2 X<LEAVE|LEAVE (phasers)>
+=head2 X<LEAVE|Phasers>
 
 Runs at every block exit time (even stack unwinds from exceptions).
 
@@ -277,7 +277,7 @@ stack is unwinding, the unwinding continues and collects exceptions to be
 handled. When the unwinding is completed all new exceptions are thrown from
 that point.
 
-=head2 X<KEEP|KEEP (phasers)>
+=head2 X<KEEP|Phasers>
 
 Runs at every successful block exit, as part of the LEAVE queue (shares the
 same order of execution).
@@ -286,12 +286,12 @@ For phasers such as C<KEEP> and C<POST> that are run when exiting a scope
 normally, the return value (if any) from that scope is available as the current
 topic within the phaser.
 
-=head2 X<UNDO|UNDO (phasers)>
+=head2 X<UNDO|Phasers>
 
 Runs at every unsuccessful block exit, as part of the LEAVE queue (shares the
 same order of execution).
 
-=head2 X<PRE|PRE (phasers)>
+=head2 X<PRE|Phasers>
 
 Asserts a precondition at every block entry. Runs before the ENTER phase.
 
@@ -301,7 +301,7 @@ The exceptions thrown by failing C<PRE> and C<POST> phasers cannot be caught by
 a C<CATCH> in the same block, which implies that C<POST> phaser are not run if
 a C<PRE> phaser fails.
 
-=head2 X<POST|POST (phasers)>
+=head2 X<POST|Phasers>
 
 Asserts a postcondition at every block entry. Runs after the LEAVE phase.
 
@@ -329,11 +329,11 @@ a C<PRE> phaser fails.
 C<FIRST>, C<NEXT>, and C<LAST> are meaningful only within the lexical scope of
 a loop, and may occur only at the top level of such a loop block.
 
-=head2 X<FIRST|FIRST (phasers)>
+=head2 X<FIRST|Phasers>
 
 Runs at loop initialization, before ENTER.
 
-=head2 X<NEXT|NEXT (phasers)>
+=head2 X<NEXT|Phasers>
 
 Runs when loop is continued (either through C<next> or because you got to the
 bottom of the loop and are looping back around), before LEAVE.
@@ -344,18 +344,18 @@ phaser is not executed if the loop block is exited via any exception other than
 the control exception thrown by C<next>. In particular, a C<last> bypasses
 evaluation of C<NEXT> phasers.
 
-=head2 X<LAST|LAST (phasers)>
+=head2 X<LAST|Phasers>
 
 Runs when loop is aborted (either through C<last>, or C<return>, or because you
 got to the bottom of the loop and are done), after LEAVE.
 
 =head1 Exception Handling Phasers
 
-=head2 X<CATCH|CATCH (phasers)>
+=head2 X<CATCH|Phasers>
 
 Runs when an exception is raised by the current block, before the LEAVE phase.
 
-=head2 X<CONTROL|CONTROL (phasers)>
+=head2 X<CONTROL|Phasers>
 
 Runs when a control exception is raised by the current block, before the LEAVE
 phase. It is raised by C<return>, C<fail>, C<redo>, C<next>, C<last>, C<take>,
@@ -364,13 +364,13 @@ C<warn>, C<proceed> and C<succeed>.
 # NYI
 # =head1 Object Phasers
 #
-# =head2 X<COMPOSE|COMPOSE (phasers)>
+# =head2 X<COMPOSE|Phasers>
 #
 # Runs when a role is composed into a class.
 
 =head1 Asynchronous Phasers
 
-=head2 X<LAST|asynchronous LAST (phasers)>
+=head2 X<LAST|Phasers>
 
 Runs when a L<Supply|/type/Supply> finishes with a call to C<done> or when a
 C<supply> block exits normally. It runs completely after the C<whenever> block
@@ -380,7 +380,7 @@ This phaser reuses the name C<LAST>, but works differently from the C<LAST> loop
 phaser. This phaser is similar to setting the C<done> routine while tapping a
 supply with C<tap>.
 
-=head2 X<QUIT|QUIT asynchronous QUIT (phasers)>
+=head2 X<QUIT|Phasers>
 
 Runs when a L<Supply|/type/Supply> terminates early with an exception. It runs
 after the C<whenever> block it is placed within finishes.
@@ -390,7 +390,7 @@ with C<tap>.
 
 =head1 DOC phasers
 
-=head2 X<DOC|DOC (phasers)>
+=head2 X<DOC|Phasers>
 
 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>.