Rename Meta::Recipe3 to Meta::Labeled_AttributeTrait

[gitmo/Moose.git] / lib / Moose / Cookbook.pod

diff --git a/lib/Moose/Cookbook.pod b/lib/Moose/Cookbook.pod
index 2b065a0..2fe272d 100644 (file)
--- a/lib/Moose/Cookbook.pod
+++ b/lib/Moose/Cookbook.pod
@@ -102,7 +102,7 @@ class. Sometimes you want the whole role but one of its methods
 conflicts with one in your class. With method exclusion and aliasing,
 you can work around these problems.
 
-=item L<Moose::Cookbook::Roles::Recipe3> - Applying a role to an object instance
+=item L<Moose::Cookbook::Roles::ApplicationToInstance>
 
 In this recipe, we apply a role to an existing object instance.
 
@@ -115,12 +115,12 @@ you extend the object system provided by Moose.
 
 =over 4
 
-=item L<Moose::Cookbook::Meta::Recipe1> - Welcome to the meta-world (Why Go Meta?)
+=item L<Moose::Cookbook::Meta::WhyMeta>
 
 If you're wondering what all this "meta" stuff is, and why you should
 care about it, read this "recipe".
 
-=item L<Moose::Cookbook::Meta::Recipe3> - Labels implemented via attribute traits
+=item L<Moose::Cookbook::Meta::Labeled_AttributeTrait>
 
 Extending Moose's attribute metaclass is a great way to add
 functionality. However, attributes can only have one metaclass.