[Bps-public-commit] Path-Dispatcher branch, master, updated. 2de397d0251e2d152638a7fd3dc6bc431afce238

[sartak at bestpractical.com]

The branch, master has been updated
       via  2de397d0251e2d152638a7fd3dc6bc431afce238 (commit)
      from  eb5928a6bbc288143532fadba53249fa8c7a62e6 (commit)

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

- Log -----------------------------------------------------------------
commit 2de397d0251e2d152638a7fd3dc6bc431afce238
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 7de099b..0fbd066 100644
--- a/lib/Path/Dispatcher.pm
+++ b/lib/Path/Dispatcher.pm
@@ -117,15 +117,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
 

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