Fixes in the docs

[catagits/Catalyst-Runtime.git] / lib / Catalyst / Upgrading.pod

diff --git a/lib/Catalyst/Upgrading.pod b/lib/Catalyst/Upgrading.pod
index fee1edd..07a1a67 100644 (file)
--- a/lib/Catalyst/Upgrading.pod
+++ b/lib/Catalyst/Upgrading.pod
@@ -167,13 +167,13 @@ highly welcomed:
 
 =back
 
-=head2 Using middleware
+=head2 Specifying the engine in the call to ->setup
 
-XXX Should this be here or elsewhere?
+XXX FIXME
 
-=head2 Making an app.psgi file
+=head2 Plack functionality
 
-=head2 Running with plackup?
+See L<Catalyst::PSGI>.
 
 =head2 Tests in 5.89
 
@@ -269,7 +269,7 @@ you identify the ones in conflict, and resolve them.
 To be able to generate a linear @ISA, the list of superclasses for each
 class must be resolvable using the C3 algorithm. Unfortunately, when
 superclasses are being used as mixins (to add functionality used in your class),
-and with multiple inheritence, it is easy to get this wrong.
+and with multiple inheritance, it is easy to get this wrong.
 
 Most common is the case of: