[SCM] Debian packaging of libdbix-class-perl branch, master, updated. debian/0.08195-1-31-g40a754e

[gregor herrmann]

The following commit has been merged in the master branch:
commit 78d653a0642fdd96a5edd7f23a7d9feb6f87c793
Author: gregor herrmann <gregoa at debian.org>
Date:   Fri May 17 19:18:47 2013 +0200

    unapply patch in git
    
    Git-Dch: Ignore

diff --git a/lib/DBIx/Class/Manual/Component.pod b/lib/DBIx/Class/Manual/Component.pod
index 6865aac..46170f9 100644
--- a/lib/DBIx/Class/Manual/Component.pod
+++ b/lib/DBIx/Class/Manual/Component.pod
@@ -27,7 +27,7 @@ by prepending the component name with a +.
 
   __PACKAGE__->load_components(qw/ +My::Component /);
 
-Once a component is loaded all of its methods, or otherwise,
+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
diff --git a/lib/DBIx/Class/Manual/Cookbook.pod b/lib/DBIx/Class/Manual/Cookbook.pod
index 7605619..588c315 100644
--- a/lib/DBIx/Class/Manual/Cookbook.pod
+++ b/lib/DBIx/Class/Manual/Cookbook.pod
@@ -1223,7 +1223,7 @@ building a renaming facility, like so:
 
   1;
 
-By overriding the L<connection|DBIx::Class::Schama/connection>
+By overridding the L<connection|DBIx::Class::Schama/connection>
 method and extracting a custom option from the provided \%attr hashref one can
 then simply iterate over all the Schema's ResultSources, renaming them as
 needed.
diff --git a/lib/DBIx/Class/Manual/FAQ.pod b/lib/DBIx/Class/Manual/FAQ.pod
index 21b1b3a..7f063b7 100644
--- a/lib/DBIx/Class/Manual/FAQ.pod
+++ b/lib/DBIx/Class/Manual/FAQ.pod
@@ -75,7 +75,7 @@ lot later.
 
 =item .. use DBIx::Class across multiple databases?
 
-If your database server allows you to run queries across multiple
+If your database server allows you to run querys across multiple
 databases at once, then so can DBIx::Class. All you need to do is make
 sure you write the database name as part of the
 L<DBIx::Class::ResultSource/table> call. Eg:
@@ -314,7 +314,7 @@ Use L<DBIx::Class::Row/discard_changes>.
 
   $row->discard_changes
 
-Discarding changes and refreshing from storage are two sides of the same coin.  When you
+Discarding changes and refreshing from storage are two sides fo the same coin.  When you
 want to discard your local changes, just re-fetch the row from storage.  When you want
 to get a new, fresh copy of the row, just re-fetch the row from storage.
 L<DBIx::Class::Row/discard_changes> does just that by re-fetching the row from storage
diff --git a/lib/DBIx/Class/Manual/Features.pod b/lib/DBIx/Class/Manual/Features.pod
index 73703d4..7c7d5c6 100644
--- a/lib/DBIx/Class/Manual/Features.pod
+++ b/lib/DBIx/Class/Manual/Features.pod
@@ -258,7 +258,7 @@ See L<DBIx::Class::Schema::Loader> and L<DBIx::Class::Schema::Loader::Base/CONST
 
 =head2 Populate
 
-Made for inserting lots of rows very quickly into database
+Made for inserting lots of rows very quicky into database
 
  $schema->populate([ Users =>
     [qw( username password )],
@@ -274,7 +274,7 @@ I use populate L<here|http://blog.afoolishmanifesto.com/archives/1255> to export
 
 =head2 Multicreate
 
-Create an object and its related objects all at once
+Create an object and it's related objects all at once
 
  $schema->resultset('Author')->create({
     name => 'Stephen King',
diff --git a/lib/DBIx/Class/Manual/Joining.pod b/lib/DBIx/Class/Manual/Joining.pod
index 8044b74..5785349 100644
--- a/lib/DBIx/Class/Manual/Joining.pod
+++ b/lib/DBIx/Class/Manual/Joining.pod
@@ -17,12 +17,12 @@ instead. Skip this part if you know what joins are..
 But I'll explain anyway. Assuming you have created your database in a
 more or less sensible way, you will end up with several tables that
 contain C<related> information. For example, you may have a table
-containing information about C<CD>s, containing the CD title and its
+containing information about C<CD>s, containing the CD title and it's
 year of publication, and another table containing all the C<Track>s
 for the CDs, one track per row.
 
 When you wish to extract information about a particular CD and all
-its tracks, You can either fetch the CD row, then make another query
+it's tracks, You can either fetch the CD row, then make another query
 to fetch the tracks, or you can use a join. Compare:
 
   SELECT ID, Title, Year FROM CD WHERE Title = 'Funky CD';
diff --git a/lib/DBIx/Class/Optional/Dependencies.pm b/lib/DBIx/Class/Optional/Dependencies.pm
index e1782a0..16f88be 100644
--- a/lib/DBIx/Class/Optional/Dependencies.pm
+++ b/lib/DBIx/Class/Optional/Dependencies.pm
@@ -897,7 +897,7 @@ EOD
     '=item Return Value: \%list_of_loaderrors_per_module',
     '=back',
     <<'EOD',
-Returns a hashref containing the actual errors that occurred while attempting
+Returns a hashref containing the actual errors that occured while attempting
 to load each module in the requirement group.
 EOD
     '=head1 AUTHOR',
diff --git a/lib/DBIx/Class/Schema.pm b/lib/DBIx/Class/Schema.pm
index f0b0fa0..d864853 100644
--- a/lib/DBIx/Class/Schema.pm
+++ b/lib/DBIx/Class/Schema.pm
@@ -1000,7 +1000,7 @@ sub svp_rollback {
 
 Clones the schema and its associated result_source objects and returns the
 copy. The resulting copy will have the same attributes as the source schema,
-except for those attributes explicitly overridden by the provided C<%attrs>.
+except for those attributes explicitly overriden by the provided C<%attrs>.
 
 =cut
 

-- 
Debian packaging of libdbix-class-perl