[Bps-public-commit] Path-Dispatcher branch, lazy-dispatch, updated. 98f7c813663aefab2959591c91dafbdc729cf384

[sartak at bestpractical.com]

The branch, lazy-dispatch has been updated
       via  98f7c813663aefab2959591c91dafbdc729cf384 (commit)
      from  0db862d98af5e08b4521c774b329cc48f0bdee75 (commit)

Summary of changes:
 lib/Path/Dispatcher.pm |    7 ++++---
 1 files changed, 4 insertions(+), 3 deletions(-)

- Log -----------------------------------------------------------------
commit 98f7c813663aefab2959591c91dafbdc729cf384
Author: Shawn M Moore <sartak at bestpractical.com>
Date:   Wed Dec 9 02:46:39 2009 -0500

    Doc tweaks

diff --git a/lib/Path/Dispatcher.pm b/lib/Path/Dispatcher.pm
index 4f06d41..e3df9a1 100644
--- a/lib/Path/Dispatcher.pm
+++ b/lib/Path/Dispatcher.pm
@@ -119,15 +119,16 @@ Path::Dispatcher - flexible and extensible dispatch
 
 =head1 DESCRIPTION
 
-We really like L<Jifty::Dispatcher> and wanted to use it for the command line.
+We really like L<Jifty::Dispatcher> and wanted to use it for L<Prophet>'s
+command line.
 
 The basic operation is that of dispatch. Dispatch takes a path and a list of
 rules, and it returns a list of matches. From there you can "run" the rules
 that matched. These phases are distinct so that, if you need to, you can
 inspect which rules were matched without ever running their codeblocks.
 
-Most consumers would want to use L<Path::Dispatcher::Declarative> which gives
-you some sugar, inspired by L<Jifty::Dispatcher>.
+You want to use L<Path::Dispatcher::Declarative> which gives you some sugar
+inspired by L<Jifty::Dispatcher>.
 
 =head1 ATTRIBUTES
 

-----------------------------------------------------------------------