--- CBOR-XS/XS.pm	2015/04/27 20:21:53	1.44
+++ CBOR-XS/XS.pm	2016/02/25 14:22:49	1.48
@@ -66,7 +66,7 @@
 
 use common::sense;
 
-our $VERSION = 1.3;
+our $VERSION = 1.41;
 our @ISA = qw(Exporter);
 
 our @EXPORT = qw(encode_cbor decode_cbor);
@@ -816,7 +816,7 @@
 objects using the C<FREEZE/THAW> methods (the L<Types::Serialier> object
 serialisation protocol). See L<OBJECT SERIALISATION> for details.
 
-=item 28, 29 (shareable, sharedref, L <http://cbor.schmorp.de/value-sharing>)
+=item 28, 29 (shareable, sharedref, L<http://cbor.schmorp.de/value-sharing>)
 
 These tags are automatically decoded when encountered (and they do not
 result in a cyclic data structure, see C<allow_cycles>), resulting in
@@ -836,7 +836,7 @@
 to be supported in the encoder. The decoder, however, will decode these
 values as shared values.
 
-=item 256, 25 (stringref-namespace, stringref, L <http://cbor.schmorp.de/stringref>)
+=item 256, 25 (stringref-namespace, stringref, L<http://cbor.schmorp.de/stringref>)
 
 These tags are automatically decoded when encountered. They are only
 encoded, however, when C<pack_strings> is enabled.
@@ -1060,7 +1060,7 @@
       # else either. Whats incredibe over standard strptime totally escapes me.
       # doesn't do fractional times, either. sigh.
       # In fact, it's all a lie, it uses whatever strptime it wants, and of course,
-      # they are all incomptible. The openbsd one simply ignores %z (but according to the
+      # they are all incompatible. The openbsd one simply ignores %z (but according to the
       # docs, it would be much more incredibly flexible indeed. If it worked, that is.).
       scalar eval {
          my $s = $_[1];