X-Git-Url: https://perl5.git.perl.org/perl5.git/blobdiff_plain/bc2086b8c3b589b640f2f4431d943eb6adfe5f35..57702e88a8b960978495a688f00a2cf47e1eb1a5:/ext/mro/mro.pm

diff --git a/ext/mro/mro.pm b/ext/mro/mro.pm
index 31f5ce6..fddc3fb 100644
--- a/ext/mro/mro.pm
+++ b/ext/mro/mro.pm
@@ -12,7 +12,7 @@ use warnings;
 
 # mro.pm versions < 1.00 reserved for MRO::Compat
 #  for partial back-compat to 5.[68].x
-our $VERSION = '1.09';
+our $VERSION = '1.13';
 
 sub import {
     mro::set_mro(scalar(caller), $_[1]) if $_[1];
@@ -202,10 +202,10 @@ This integer normally starts off at a value of C<1>
 when a package stash is instantiated.  Calling it
 on packages whose stashes do not exist at all will
 return C<0>.  If a package stash is completely
-deleted (not a normal occurence, but it can happen
+deleted (not a normal occurrence, but it can happen
 if someone does something like C<undef %PkgName::>),
 the number will be reset to either C<0> or C<1>,
-depending on how completely package was wiped out.
+depending on how completely the package was wiped out.
 
 =head2 next::method
 
@@ -308,7 +308,7 @@ works (like C<goto &maybe::next::method>);
 
 =over 4
 
-=item L<http://www.webcom.com/haahr/dylan/linearization-oopsla96.html>
+=item L<http://haahr.tempdomainname.com/dylan/linearization-oopsla96.html>
 
 =back