Typos fixes to Manual/Component as well as adding Component to Manual.pod.

[dbsrgits/DBIx-Class.git] / lib / DBIx / Class / Manual / Component.pod

diff --git a/lib/DBIx/Class/Manual/Component.pod b/lib/DBIx/Class/Manual/Component.pod
index 1dfe90d..f74f5bf 100644 (file)
--- a/lib/DBIx/Class/Manual/Component.pod
+++ b/lib/DBIx/Class/Manual/Component.pod
@@ -1,7 +1,7 @@
 
 =head1 NAME
 
-DBIx::Class::Manula::Component - Existing components and how to develop new ones.
+DBIx::Class::Manual::Component - Existing components and how to develop new ones.
 
 =head1 USING
 
@@ -24,29 +24,28 @@ Once a component is loaded all of it's methods, or otherwise,
 that it provides will be available in your class.
 
 The order in which is you load the components may be 
-very imporant, depending on the component.  The general 
+very important, depending on the component.  The general 
 rule of thumb is to first load extra components and then 
 load core ones last.  If you are not sure, then read the 
 docs for the components you are using and see if they 
 mention anything about the order in which you should load 
 them.
 
-=head1 EXISTING
+=head1 EXISTING COMPONENTS
 
 =head2 Extra
 
-These components provide extra functionality above 
-and beyond what any normal user would need out of the 
-box.
+These components provide extra functionality beyond 
+basic functionality that you can't live without.
 
 L<DBIx::Class::CDBICompat> - Class::DBI Compatability layer.
 
-L<DBIx::Class::PK::Auto> - Retrieve automatically created primary keys upon insert.
-
 L<DBIx::Class::FormTools> - Build forms with multiple interconnected objects.
 
 L<DBIx::Class::HTMLWidget> - Like FromForm but with DBIx::Class and HTML::Widget.
 
+L<DBIx::Class::PK::Auto> - Retrieve automatically created primary keys upon insert.
+
 L<DBIx::Class::QueriesTime> - Display the amount of time it takes to run queries.
 
 L<DBIx::Class::RandomStringColumns> - Declare virtual columns that return random strings.
@@ -75,23 +74,23 @@ These are the components that all, or nearly all, people will use
 without even knowing it.  These components provide most of 
 DBIx::Class' functionality.
 
+L<DBIx::Class::AccessorGroup> - Lets you build groups of accessors.
+
 L<DBIx::Class::Core> - Loads various components that "most people" would want.
 
 L<DBIx::Class::DB> - Non-recommended classdata schema component.
 
 L<DBIx::Class::InflateColumn> - Automatically create objects from column data.
 
-L<DBIx::Class::Relationship> - Inter-table relationships.
-
 L<DBIx::Class::PK> - This class contains methods for handling primary keys and methods depending on them.
 
-L<DBIx::Class::Row> - Basic row methods.
+L<DBIx::Class::Relationship> - Inter-table relationships.
 
 L<DBIx::Class::ResultSourceProxy::Table> - Provides a classdata table object and method proxies.
 
-L<DBIx::Class::AccessorGroup> - Lets you build groups of accessors.
+L<DBIx::Class::Row> - Basic row methods.
 
-=head1 CREATEING
+=head1 CREATEING COMPONENTS
 
 Making your own component is very easy.
 
@@ -101,7 +100,7 @@ Making your own component is very easy.
   1;
 
 When a component is loaded it is included in the calling 
-classes inheritance chain using L<Class::C3>.  As well as 
+class' inheritance chain using L<Class::C3>.  As well as 
 providing custom utility methods, a component may also 
 override methods provided by other core components, like 
 L<DBIx::Class::Row> and others.  For example, you 
@@ -128,7 +127,7 @@ being called try printing out the Class::C3 inheritance stack.
 
   print join ', ' => Class::C3::calculateMRO('YourClass::Name');
 
-Check out the L<Class::C3> docs for more information.
+Check out the L<Class::C3> docs for more information about inhertance.
 
 =head1 SEE ALSO