X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FDBIx%2FClass%2FTree.pm;h=ea0514e9022f9044c60cb1912d5b81b869fa98b0;hb=5e44a0c684447c95bdc71100651789b537e9aebc;hp=a887a101479e8051c5967841752d042b5be17404;hpb=98277fa537fe2441d8f3439d48861387d4acfc12;p=dbsrgits%2FDBIx-Class-Tree.git

diff --git a/lib/DBIx/Class/Tree.pm b/lib/DBIx/Class/Tree.pm
index a887a10..ea0514e 100644
--- a/lib/DBIx/Class/Tree.pm
+++ b/lib/DBIx/Class/Tree.pm
@@ -6,7 +6,7 @@ use warnings;
 
 use base qw( DBIx::Class );
 
-our $VERSION = '0.03000';
+our $VERSION = '0.03001';
 
 1;
 __END__
@@ -17,30 +17,30 @@ DBIx::Class::Tree - Manipulate and anaylze tree structured data.
 
 =head1 DESCRIPTION
 
-The tree modules provide the tools to represent, modify, and analyze 
+The tree modules provide the tools to represent, modify, and analyze
 trees of data with DBIx::Class.
 
 =head1 COMPONENTS
 
-L<DBIx::Class::Tree::AdjacencyList> - Manage a tree of data using the 
+L<DBIx::Class::Tree::AdjacencyList> - Manage a tree of data using the
 common adjacency list model.
 
-L<DBIx::Class::Tree::AdjacencyList::Ordered> - Glue DBIx::Class::Ordered 
+L<DBIx::Class::Tree::AdjacencyList::Ordered> - Glue DBIx::Class::Ordered
 and DBIx::Class::Tree::AdjacencyList together.
 
 =head1 DAG
 
-All tree related modules must conform to have and use the basic traversal 
-methods of a DAG.  For the most part this just means that Tree modules 
-must provide the appearance of having multiple parents per node (via a 
-parents() method) but may very well never return more than one parent.  
-All utility modules, such as a Visitor module, should do its best to 
-never assume that a node only has one parent.  There are situations 
-where this is not possible - in those cases the module's documentation 
+All tree related modules must conform to have and use the basic traversal
+methods of a DAG.  For the most part this just means that Tree modules
+must provide the appearance of having multiple parents per node (via a
+parents() method) but may very well never return more than one parent.
+All utility modules, such as a Visitor module, should do its best to
+never assume that a node only has one parent.  There are situations
+where this is not possible - in those cases the module's documentation
 should clearly state that it is not compatible with DAGs.
 
-So far there is no Tree::DAG module, but there will be.  These requirements 
-are vague, and the requirements of Tree modules to be DAG compatible will 
+So far there is no Tree::DAG module, but there will be.  These requirements
+are vague, and the requirements of Tree modules to be DAG compatible will
 become more defined in due course.
 
 =head1 AUTHOR