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=d3b1d569e61cc94220c35beeb37df101e336b331;hb=4aaed9e5cc435a2085e46f4c98a3abc233ecacaf;hpb=d503a4f3aa9eda772309f6c99ccd4dfcdfed059d

diff --git a/lib/Mouse.pm b/lib/Mouse.pm
index d3b1d56..8618702 100644
--- a/lib/Mouse.pm
+++ b/lib/Mouse.pm
@@ -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.