X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=gitmo%2FMouse.git;a=blobdiff_plain;f=lib%2FMouse.pm;h=86187026eda695148334f72c40d0cb6b12fb6019;hp=22827e57a0a6cfb5720ad50c03586ef4ad85740e;hb=4aaed9e5cc435a2085e46f4c98a3abc233ecacaf;hpb=7fa0bc1b549deaa7f089c75b491877ed552f4f53

diff --git a/lib/Mouse.pm b/lib/Mouse.pm
index 22827e5..8618702 100644
--- a/lib/Mouse.pm
+++ b/lib/Mouse.pm
@@ -3,7 +3,7 @@ use 5.006_002;
 
 use Mouse::Exporter; # enables strict and warnings
 
-our $VERSION = '0.50_01';
+our $VERSION = '0.50_02';
 
 use Carp         qw(confess);
 use Scalar::Util qw(blessed);
@@ -160,7 +160,7 @@ Mouse - Moose minus the antlers
 
 =head1 VERSION
 
-This document describes Mouse version 0.50_01
+This document describes Mouse version 0.50_02
 
 =head1 SYNOPSIS
 
@@ -212,10 +212,9 @@ B<no dependencies> except for testing modules.
 
 =head2 MOOSE COMPATIBILITY
 
-Compatibility with Moose has been the utmost concern. Fewer than 1% of the
-tests fail when run against Moose instead of Mouse. Mouse code coverage is also
-over 96%. Even the error messages are taken from Moose. The Mouse code just
-runs the test suite 4x faster.
+Compatibility with Moose has been the utmost concern. The sugary interface is
+highly compatible with Moose. Even the error messages are taken from Moose.
+The Mouse code just runs the test suite 4x faster.
 
 The idea is that, if you need the extra power, you should be able to run
 C<s/Mouse/Moose/g> on your codebase and have nothing break. To that end,
@@ -226,7 +225,7 @@ Moose, if you run into weird errors, it would be worth running:
     ANY_MOOSE=Moose perl your-script.pl
 
 to see if the bug is caused by Mouse. Moose's diagnostics and validation are
-also much better.
+also better.
 
 See also L<Mouse::Spec> for compatibility and incompatibility with Moose.