Fixed links in flox to cookbook (bug 22899)

git-svn-id: http://svn.maypole.perl.org/Maypole/trunk@578 48953598-375a-da11-a14b-00016c27c3ee

diff --git a/lib/Maypole/Manual/Flox.pod b/lib/Maypole/Manual/Flox.pod
index df3cff889c3969d509e589e0987fe810d4995cfe..5e897774c6219c08e3290efb0cea069d1be41fca 100644 (file)
--- a/lib/Maypole/Manual/Flox.pod
+++ b/lib/Maypole/Manual/Flox.pod
@@ -20,7 +20,7 @@ university student population.
 
 Flox is still in, uh, flux, but it does the essentials. We're going to
 see how it was put together, and how the techniques shown in the
 
 Flox is still in, uh, flux, but it does the essentials. We're going to
 see how it was put together, and how the techniques shown in the

-L<Request Cookbook|Maypole::Manual::Request> can help to
+L<Request Cookbook|Maypole::Manual::Cookbook> can help to

 create a sophisticated web
 application. Of course, I didn't have this manual available at the time,
 so it took a bit longer than it should have done...
 create a sophisticated web
 application. Of course, I didn't have this manual available at the time,
 so it took a bit longer than it should have done...


@@ -152,7 +152,7 @@ Very simple, as these things are meant to be. Now let's build on it.
 The concept of a current user is absolutely critical in a site like
 Flox; it represents "me", the viewer of the page, as the site explores
 the connections in my world. We've described the authentication hacks
 The concept of a current user is absolutely critical in a site like
 Flox; it represents "me", the viewer of the page, as the site explores
 the connections in my world. We've described the authentication hacks

-briefly in the L<Request Cookbook|Maypole::Manual::Request>,
+briefly in the L<Request Cookbook|Maypole::Manual::Cookbook>,

 but now it's time to go into a little more detail about how user
 handling is done.
 
 but now it's time to go into a little more detail about how user
 handling is done.
 


@@ -195,7 +195,7 @@ The next stage is viewing the user's photo. Assuming we've got the photo
 stored in the database already (which is a reasonable assumption for the
 moment since we don't have a way to upload a photo quite yet) then we
 can use a variation of the "Displaying pictures" hack from the 
 stored in the database already (which is a reasonable assumption for the
 moment since we don't have a way to upload a photo quite yet) then we
 can use a variation of the "Displaying pictures" hack from the 

-L<Request Cookbook|Maypole::Manual::Request>:
+L<Request Cookbook|Maypole::Manual::Cookbook:

 
     sub view_picture :Exported {
         my ($self, $r) = @_;
 
     sub view_picture :Exported {
         my ($self, $r) = @_;


@@ -328,7 +328,7 @@ and the template proceeds as normal:
     <TABLE>
 
 Now we use the "Catching errors in a form" recipe from the
     <TABLE>
 
 Now we use the "Catching errors in a form" recipe from the

-L<Request Cookbook|Maypole::Manual::Request> and
+L<Request Cookbook|Maypole::Manual::Cookbook> and

 write our form template:
 
     <TR><TD>
 write our form template:
 
     <TR><TD>