From: Karen Etheridge <ether@cpan.org>
Date: Thu, 10 Oct 2013 19:23:29 +0000 (-0700)
Subject: Pod/comment fixes
X-Git-Tag: v0.08260~121
X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=3334d204fcbbddedd73a7f63a285bdda9cb3e031;p=dbsrgits%2FDBIx-Class.git

Pod/comment fixes
---

diff --git a/lib/DBIx/Class/ResultSet.pm b/lib/DBIx/Class/ResultSet.pm
index 35dfaf5..146c12b 100644
--- a/lib/DBIx/Class/ResultSet.pm
+++ b/lib/DBIx/Class/ResultSet.pm
@@ -305,7 +305,7 @@ call it as C<search(undef, \%attrs)>.
 
 For a list of attributes that can be passed to C<search>, see
 L</ATTRIBUTES>. For more examples of using this function, see
-L<Searching|DBIx::Class::Manual::Cookbook/Searching>. For a complete
+L<Searching|DBIx::Class::Manual::Cookbook/SEARCHING>. For a complete
 documentation for the first argument, see L<SQL::Abstract/"WHERE CLAUSES">
 and its extension L<DBIx::Class::SQLMaker>.
 
@@ -648,7 +648,7 @@ should only be used in that context. C<search_literal> is a convenience
 method. It is equivalent to calling C<< $schema->search(\[]) >>, but if you
 want to ensure columns are bound correctly, use L</search>.
 
-See L<DBIx::Class::Manual::Cookbook/Searching> and
+See L<DBIx::Class::Manual::Cookbook/SEARCHING> and
 L<DBIx::Class::Manual::FAQ/Searching> for searching techniques that do not
 require C<search_literal>.
 
diff --git a/t/101populate_rs.t b/t/101populate_rs.t
index 46368f3..56e87f0 100644
--- a/t/101populate_rs.t
+++ b/t/101populate_rs.t
@@ -128,7 +128,7 @@ SCHEMA_POPULATE1: {
 ARRAY_CONTEXT: {
 
   ## These first set of tests are cake because array context just delegates
-  ## all it's processing to $resultset->create
+  ## all its processing to $resultset->create
 
   HAS_MANY_NO_PKS: {
 
diff --git a/t/98savepoints.t b/t/98savepoints.t
index 53d5d62..a195b85 100644
--- a/t/98savepoints.t
+++ b/t/98savepoints.t
@@ -96,7 +96,7 @@ for my $prefix (keys %$env2optdep) { SKIP: {
   cmp_ok($arty->name, 'eq', 'gphat', 'name changed');
   # Active: 0 1 2
   # Rollback doesn't DESTROY the savepoint, it just rolls back to the value
-  # at it's conception
+  # at its conception
   $schema->svp_rollback('testing2');
   $arty->discard_changes;
   cmp_ok($arty->name, 'eq', 'yourmom', 'testing2 reverted');