Get rid of DESTROY fossils

Author: lizmat

S12-objects.pod

@@ -853,7 +853,6 @@ class traits, for instance, telling it bit sizes and such.)
 The C<bless> method automatically calls all appropriate C<BUILD>
 routines for the current class,
 which initializes the object in least-derived to most-derived order.
-(C<DESTROY> submethods work the same way, only in reverse.)
 
 The default C<BUILD> semantics are inherited from C<Mu>,
 so you need to write initialization routines only if you wish to

S29-functions.pod

@@ -246,8 +246,7 @@ support.
 Stops all program execution, and returns C<$status> to the calling environment.
 
 An exit runs all appropriate scope-leaving blocks such as C<LEAVE>, C<KEEP>,
-and C<UNDO>, followed by all C<END> blocks, followed by all C<DESTROY>s that
-do more than just reclaim memory, and so cannot be skipped because
+and C<UNDO>, followed by all C<END> blocks, and so cannot be skipped because
 they may have side effects visible outside the process.  If run from
 an embedded interpreter, all memory must also be reclaimed.