--- CBOR-XS/XS.pm	2020/12/11 06:05:33	1.80
+++ CBOR-XS/XS.pm	2022/12/19 20:31:33	1.87
@@ -66,7 +66,7 @@
 
 use common::sense;
 
-our $VERSION = 1.83;
+our $VERSION = 1.86;
 our @ISA = qw(Exporter);
 
 our @EXPORT = qw(encode_cbor decode_cbor);
@@ -123,6 +123,7 @@
 
    my $cbor = CBOR::XS
       ->new
+      ->validate_utf8
       ->forbid_objects
       ->filter (\&CBOR::XS::safe_filter)
       ->max_size (1e8);
@@ -135,6 +136,7 @@
 sub new_safe {
    CBOR::XS
       ->new
+      ->validate_utf8
       ->forbid_objects
       ->filter (\&CBOR::XS::safe_filter)
       ->max_size (1e8)
@@ -473,7 +475,7 @@
 if a full CBOR object is available, but is much more efficient.
 
 It basically works by parsing as much of a CBOR string as possible - if
-the CBOR data is not complete yet, the pasrer will remember where it was,
+the CBOR data is not complete yet, the parser will remember where it was,
 to be able to restart when more data has been accumulated. Once enough
 data is available to either decode a complete CBOR value or raise an
 error, a real decode will be attempted.
@@ -635,8 +637,7 @@
 =item Types::Serialiser::true, Types::Serialiser::false, Types::Serialiser::error
 
 These special values become CBOR true, CBOR false and CBOR undefined
-values, respectively. You can also use C<\1>, C<\0> and C<\undef> directly
-if you want.
+values, respectively.
 
 =item other blessed objects
 
@@ -706,7 +707,7 @@
 =head2 TYPE CASTS
 
 B<EXPERIMENTAL>: As an experimental extension, C<CBOR::XS> allows you to
-force specific cbor types to be used when encoding. That allows you to
+force specific CBOR types to be used when encoding. That allows you to
 encode types not normally accessible (e.g. half floats) as well as force
 string types even when C<text_strings> is in effect.
 
@@ -758,7 +759,7 @@
 
 =item CBOR::XS::as_cbor $cbor_text
 
-Not a type cast per-se, this type cast forces the argument to eb encoded
+Not a type cast per-se, this type cast forces the argument to be encoded
 as-is. This can be used to embed pre-encoded CBOR data.
 
 Note that no checking on the validity of the C<$cbor_text> is done - it's
@@ -775,7 +776,7 @@
 elements.
 
 Note that only the reference to the array is copied, the array itself is
-not. Modifications done to the array before calling an encoding fuinction
+not. Modifications done to the array before calling an encoding function
 will be reflected in the encoded output.
 
 Example: encode a CBOR map with a string and an integer as keys.