terms were the wrong way round

[catagits/Catalyst-Manual.git] / lib / Catalyst / Manual / Intro.pod

diff --git a/lib/Catalyst/Manual/Intro.pod b/lib/Catalyst/Manual/Intro.pod
index e9ba5b1..794a8ef 100644 (file)
--- a/lib/Catalyst/Manual/Intro.pod
+++ b/lib/Catalyst/Manual/Intro.pod
@@ -124,6 +124,12 @@ if you end up using it).
 
 =back
 
+=item * PSGI Support
+
+Starting with Catalyst version 5.9 Catalyst ships with L<PSGI> integration
+for even more powerful and flexible testing and deployment options.  See
+L<Catalyst::PSGI> for details.
+
 =head3 Simplicity
 
 The best part is that Catalyst implements all this flexibility in a very
@@ -865,7 +871,7 @@ subroutine name together determine the path.
 1;
 
 Matches http://localhost:3000/foo - that is, the action is mapped
-directly to the controller namespace, ignoring the function name.
+directly to the method name, ignoring the controller namespace.
 
 C<:Global> always matches from the application root: it is simply
 shorthandfor C<:Path('/methodname')>.  C<:Local> is shorthand for
@@ -877,7 +883,7 @@ applications (e.g. before Catalyst 5.7).  The use cases where C<Global>
 used to make sense are now largely replaced by the C<Chained> dispatch
 type, or by empty C<Path> declarations on an controller action.  C<Global>
 is still included in Catalyst for backwards compatibility, although
-legitimate use-cases for it may still exist (but nobody can.
+legitimate use-cases for it may still exist.
 
 =item * Changing handler behaviour: eating arguments (C<:Args>)