Rename Meta::Recipe1 to Meta::WhyMeta

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

diff --git a/lib/Moose/Cookbook.pod b/lib/Moose/Cookbook.pod
index 4f5db38..511f155 100644 (file)
--- a/lib/Moose/Cookbook.pod
+++ b/lib/Moose/Cookbook.pod
@@ -89,20 +89,20 @@ These recipes will show you how to use Moose roles.
 
 =over 4
 
-=item L<Moose::Cookbook::Roles::Recipe1> - The Moose::Role example
+=item L<Moose::Cookbook::Roles::Comparable_CodeReuse>
 
 Demonstrates roles, which are also sometimes known as traits or
 mix-ins. Roles provide a method of code re-use which is orthogonal to
 subclassing.
 
-=item L<Moose::Cookbook::Roles::Recipe2> - Advanced Role Composition - method exclusion and aliasing
+=item L<Moose::Cookbook::Roles::Restartable_AdvancedComposition>
 
 Sometimes you just want to include part of a role in your
 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,7 +115,7 @@ 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".