[Catalyst-commits] r9159 - in Catalyst-Runtime/5.80/trunk/lib: . Catalyst Catalyst/Manual/Installation

rafl at dev.catalyst.perl.org rafl at dev.catalyst.perl.org
Mon Feb 2 12:04:19 GMT 2009

Author: rafl
Date: 2009-02-02 12:04:19 +0000 (Mon, 02 Feb 2009)
New Revision: 9159

Fix various doc typoes.

Modified: Catalyst-Runtime/5.80/trunk/lib/Catalyst/Base.pm
--- Catalyst-Runtime/5.80/trunk/lib/Catalyst/Base.pm	2009-02-02 12:01:52 UTC (rev 9158)
+++ Catalyst-Runtime/5.80/trunk/lib/Catalyst/Base.pm	2009-02-02 12:04:19 UTC (rev 9159)
@@ -15,7 +15,7 @@
 This used to be the base class for Catalyst Controllers. It
-remains here for compability reasons.
+remains here for compatibility reasons.
 =head1 SEE ALSO

Modified: Catalyst-Runtime/5.80/trunk/lib/Catalyst/ClassData.pm
--- Catalyst-Runtime/5.80/trunk/lib/Catalyst/ClassData.pm	2009-02-02 12:01:52 UTC (rev 9158)
+++ Catalyst-Runtime/5.80/trunk/lib/Catalyst/ClassData.pm	2009-02-02 12:04:19 UTC (rev 9159)
@@ -66,7 +66,7 @@
 =head1 NAME
-Catalyst::ClassData - Class data acessors
+Catalyst::ClassData - Class data accessors
 =head1 METHODS

Modified: Catalyst-Runtime/5.80/trunk/lib/Catalyst/Engine.pm
--- Catalyst-Runtime/5.80/trunk/lib/Catalyst/Engine.pm	2009-02-02 12:01:52 UTC (rev 9158)
+++ Catalyst-Runtime/5.80/trunk/lib/Catalyst/Engine.pm	2009-02-02 12:04:19 UTC (rev 9159)
@@ -589,7 +589,7 @@
 =head2 $self->read_chunk($c, $buffer, $length)
-Each engine inplements read_chunk as its preferred way of reading a chunk
+Each engine implements read_chunk as its preferred way of reading a chunk
 of data.

Modified: Catalyst-Runtime/5.80/trunk/lib/Catalyst/Manual/Installation/CentOS4.pod
--- Catalyst-Runtime/5.80/trunk/lib/Catalyst/Manual/Installation/CentOS4.pod	2009-02-02 12:01:52 UTC (rev 9158)
+++ Catalyst-Runtime/5.80/trunk/lib/Catalyst/Manual/Installation/CentOS4.pod	2009-02-02 12:04:19 UTC (rev 9159)
@@ -306,7 +306,7 @@
 command to check the status of the packages listed in <cat-install>. Ideally, 
 everything should return a I<name> C<is up to date> message.  If any packages 
 try to re-install, the you could need to manually install the package with the 
-C<force> option.  Also, look for new optional dependences that C<cat-install> 
+C<force> option.  Also, look for new optional dependencies that C<cat-install>
 was not able to automatically handle. You can address these by manually 
 installing the dependency and then re-running C<perl cat-install>.  

Modified: Catalyst-Runtime/5.80/trunk/lib/Catalyst/Request.pm
--- Catalyst-Runtime/5.80/trunk/lib/Catalyst/Request.pm	2009-02-02 12:01:52 UTC (rev 9158)
+++ Catalyst-Runtime/5.80/trunk/lib/Catalyst/Request.pm	2009-02-02 12:04:19 UTC (rev 9159)
@@ -399,7 +399,7 @@
 =head2 $req->path_info
-Alias for path, added for compability with L<CGI>.
+Alias for path, added for compatibility with L<CGI>.
@@ -463,7 +463,7 @@
 =head2 $req->snippets
-C<captures> used to be called snippets. This is still available for backwoards
+C<captures> used to be called snippets. This is still available for backwards
 compatibility, but is considered deprecated.
 =head2 $req->upload

Modified: Catalyst-Runtime/5.80/trunk/lib/Catalyst/Stats.pm
--- Catalyst-Runtime/5.80/trunk/lib/Catalyst/Stats.pm	2009-02-02 12:01:52 UTC (rev 9158)
+++ Catalyst-Runtime/5.80/trunk/lib/Catalyst/Stats.pm	2009-02-02 12:04:19 UTC (rev 9159)
@@ -324,10 +324,10 @@
 The 'rollup' flag indicates whether the reported time is the rolled up time for
 the block, or the elapsed time from the previous profiling point.
 Some components might expect the stats object to be a regular Tree::Simple object.
-We've added some compatability methods to handle this scenario:
+We've added some compatibility methods to handle this scenario:
 =head2 accept

Modified: Catalyst-Runtime/5.80/trunk/lib/Catalyst/Upgrading.pod
--- Catalyst-Runtime/5.80/trunk/lib/Catalyst/Upgrading.pod	2009-02-02 12:01:52 UTC (rev 9158)
+++ Catalyst-Runtime/5.80/trunk/lib/Catalyst/Upgrading.pod	2009-02-02 12:04:19 UTC (rev 9159)
@@ -3,7 +3,7 @@
 Most applications and plugins should run unaltered on Catalyst 5.80.
 However as a lot of refactoring work has taken place, several changes
-have been made which could cause incompatibilties, if your application
+have been made which could cause incompatibilities, if your application
 or plugin is using deprecated code, or relying on side-effects then
 there could be incompatibility.
@@ -26,7 +26,7 @@
 to be able to use the constructor provided by Moose. In 5.80
 C<Catalyst::Component> already inherits from C<Moose::Object>. Therefor you
 shouldn't directly inherit from C<Moose::Object> yourself, otherwise your
-Class' @ISA will not linearise with C3.
+Class' @ISA will not linearize with C3.
 =head2 Anonymous closures installed directly into the symbol table
@@ -85,7 +85,7 @@
 This is no longer supported - users should make a sub-class of the class who's behavior they would
 like to change, rather than globally polluting the Catalyst objects.
-=head2 Confused multiple inheritence with Catalyst::Component::COMPONENT
+=head2 Confused multiple inheritance with Catalyst::Component::COMPONENT
 Warning message:
@@ -156,7 +156,7 @@
 In this version of Catalyst, if a component is loaded from disk, but no symbols are defined in that component's namespace
 after it is loaded, this warning will be issued.
-This is to pretect against confusing bugs caused by mis-typing package names.
+This is to protect against confusing bugs caused by mis-typing package names.
 This will become a fatal error in a future version.

Modified: Catalyst-Runtime/5.80/trunk/lib/Catalyst.pm
--- Catalyst-Runtime/5.80/trunk/lib/Catalyst.pm	2009-02-02 12:01:52 UTC (rev 9158)
+++ Catalyst-Runtime/5.80/trunk/lib/Catalyst.pm	2009-02-02 12:04:19 UTC (rev 9159)
@@ -871,7 +871,7 @@
 =head2 $c->plugin( $name, $class, @args )
-Helper method for plugins. It creates a classdata accessor/mutator and
+Helper method for plugins. It creates a class data accessor/mutator and
 loads and instantiates the given class.
     MyApp->plugin( 'prototype', 'HTML::Prototype' );

More information about the Catalyst-commits mailing list