[Dbix-class] [PATCH] Pod formatting fixes.

[Florian Ragwitz]

---
 lib/DBIx/Class/ResultSet.pm   |    2 +-
 lib/DBIx/Class/Row.pm         |    2 +-
 lib/DBIx/Class/Storage/DBI.pm |    6 +++---
 3 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/lib/DBIx/Class/ResultSet.pm b/lib/DBIx/Class/ResultSet.pm
index 8adff20..de7ac48 100644
--- a/lib/DBIx/Class/ResultSet.pm
+++ b/lib/DBIx/Class/ResultSet.pm
@@ -2516,7 +2516,7 @@ Adds to the WHERE clause.
   # only return rows WHERE deleted IS NULL for all searches
   __PACKAGE__->resultset_attributes({ where => { deleted => undef } }); )
 
-Can be overridden by passing C<{ where => undef }> as an attribute
+Can be overridden by passing C<{ where =E<gt> undef }> as an attribute
 to a resulset.
 
 =back
diff --git a/lib/DBIx/Class/Row.pm b/lib/DBIx/Class/Row.pm
index 0ba7243..c252a03 100644
--- a/lib/DBIx/Class/Row.pm
+++ b/lib/DBIx/Class/Row.pm
@@ -289,7 +289,7 @@ Must be run on an object that is already in the database; issues an SQL
 UPDATE query to commit any changes to the object to the database if
 required.
 
-Also takes an options hashref of C<< column_name => value> pairs >> to update
+Also takes an options hashref of C<< column_name => value >> pairs to update
 first. But be aware that the hashref will be passed to
 C<set_inflated_columns>, which might edit it in place, so dont rely on it being
 the same after a call to C<update>.  If you need to preserve the hashref, it is
diff --git a/lib/DBIx/Class/Storage/DBI.pm b/lib/DBIx/Class/Storage/DBI.pm
index d0f5b1e..255b961 100644
--- a/lib/DBIx/Class/Storage/DBI.pm
+++ b/lib/DBIx/Class/Storage/DBI.pm
@@ -452,16 +452,16 @@ whether any options are specified in the new C<connect_info>.
 Another Important Note:
 
 DBIC can do some wonderful magic with handling exceptions,
-disconnections, and transactions when you use C<< AutoCommit => 1 >>
+disconnections, and transactions when you use C<< AutoCommit =E<gt> 1 >>
 combined with C<txn_do> for transaction support.
 
-If you set C<< AutoCommit => 0 >> in your connect info, then you are always
+If you set C<< AutoCommit =E<gt> 0 >> in your connect info, then you are always
 in an assumed transaction between commits, and you're telling us you'd
 like to manage that manually.  A lot of DBIC's magic protections
 go away.  We can't protect you from exceptions due to database
 disconnects because we don't know anything about how to restart your
 transactions.  You're on your own for handling all sorts of exceptional
-cases if you choose the C<< AutoCommit => 0 >> path, just as you would
+cases if you choose the C<< AutoCommit =E<gt> 0 >> path, just as you would
 be with raw DBI.
 
 Examples:
-- 
1.5.6.2