Cleanup some =over and =back

Author: lizmat

doc/Type/List.pod

@@ -282,8 +282,6 @@ Return the index and the matched element as a C<Pair>, in order.
 Only return the matched elements (same as not specifying any named parameter
 at all).
 
-=back
-
 Examples:
 
     > ('hello', 1, 22/7, 42, 'world').grep: Int, :k
@@ -333,8 +331,6 @@ Return both the index and matched element.
 
 Return the index and the matched element as a C<Pair>.
 
-=back
-
 Examples:
 
     say (1, 22/7, 42, 300).first: * > 5, :k;        # 2

doc/Type/Supply.pod

@@ -390,8 +390,6 @@ any status messages.  If specified, it will at least send one status message
 after the original Supply is exhausted.  The status message is a hash with
 the following keys:
 
-=over 2 
-
 =item allowed
 
 The current number of messages / callables that is still allowed to be
@@ -423,8 +421,6 @@ The current limit that is being applied.
 The maximum number of messages that may be buffered before they're
 automatically re-routed to the :bleed Supply.
 
-=back
-
 The :bleed named parameter optionally specifies a Supply that will receive
 any values that were either explicitly bled (with the B<bleed> control
 message), or automatically bled (if there's a B<vent-at> active).
@@ -442,8 +438,6 @@ to $*SCHEDULER.
 These messages can be sent to the :control Supply.  A control message
 consists of a string of the form "key: value", e.g. "limit: 4".
 
-=over 2
-
 =item limit
 
 Change the number of messages (as initially given in the first positional)
@@ -463,8 +457,6 @@ rerouting of buffered values to match the new maximum.
 
 Send a status message to the :status Supply with the given id.
 
-=back
-
 =head2 method stable
 
     method stable(Supply:D: $seconds, :$scheduler) returns Supply:D