actually, just stop recommending deprecated software

diff --git a/lib/Moose/Cookbook/Extending/Recipe1.pod b/lib/Moose/Cookbook/Extending/Recipe1.pod
index 0f79a8c..62bfc4a 100644 (file)
--- a/lib/Moose/Cookbook/Extending/Recipe1.pod
+++ b/lib/Moose/Cookbook/Extending/Recipe1.pod
@@ -45,11 +45,9 @@ metaclass. If you were writing an ORM, this would be a logical
 extension.
 
 Many of the Moose extensions on CPAN work by providing an attribute
-metaclass extension. For example, the L<MooseX::AttributeHelpers>
-distribution provides a new attribute metaclass that lets you delegate
-behavior to a non-object attribute (a hashref or simple number).
-(MooseX::AttributeHelpers has been deprecated in favour of
-L<Moose::Meta::Attribute::Native>, but can still serve as an example).
+metaclass extension. For example, the L<MooseX::Aliases> module
+provides an attribute metaclass trait that lets you specify aliases
+to install for methods and attribute accessors.
 
 A metaclass extension can be packaged as a subclass or a
 role/trait. If you can, we recommend using traits instead of

diff --git a/lib/Moose/Cookbook/Meta/Recipe1.pod b/lib/Moose/Cookbook/Meta/Recipe1.pod
index f2e72a7..ea6341d 100644 (file)
--- a/lib/Moose/Cookbook/Meta/Recipe1.pod
+++ b/lib/Moose/Cookbook/Meta/Recipe1.pod
@@ -50,9 +50,9 @@ object, letting you write C<< My::Class->meta()->table_name() >>.
 =head1 SEE ALSO
 
 Many of the MooseX modules on CPAN implement metaclass extensions. A
-couple good examples include L<MooseX::Singleton> and
-L<MooseX::AttributeHelpers>. For a more complex example see
-L<Fey::ORM> or L<Reaction>.
+couple good examples include L<MooseX::Aliases> and
+L<MooseX::UndefTolerant>. For a more complex example see
+L<Fey::ORM> or L<Bread::Board::Declare>.
 
 =cut