--- JSON-XS/XS.pm	2007/04/09 05:09:57	1.29
+++ JSON-XS/XS.pm	2007/04/12 07:25:29	1.32
@@ -88,7 +88,7 @@
 use strict;
 
 BEGIN {
-   our $VERSION = '1.11';
+   our $VERSION = '1.12';
    our @ISA = qw(Exporter);
 
    our @EXPORT = qw(to_json from_json objToJson jsonToObj);
@@ -156,7 +156,9 @@
 generate characters outside the code range C<0..127> (which is ASCII). Any
 unicode characters outside that range will be escaped using either a
 single \uXXXX (BMP characters) or a double \uHHHH\uLLLLL escape sequence,
-as per RFC4627.
+as per RFC4627. The resulting encoded JSON text can be treated as a native
+unicode string, an ascii-encoded, latin1-encoded or UTF-8 encoded string,
+or any other superset of ASCII.
 
 If C<$enable> is false, then the C<encode> method will not escape Unicode
 characters unless required by the JSON syntax. This results in a faster
@@ -642,7 +644,7 @@
 C<max_depth> method.
 
 And last but least, something else could bomb you that I forgot to think
-of. In that case, you get to keep the pieces. I am alway sopen for hints,
+of. In that case, you get to keep the pieces. I am always open for hints,
 though...