--- JSON-XS/README	2008/06/03 06:43:45	1.26
+++ JSON-XS/README	2008/09/29 03:09:27	1.28
@@ -46,8 +46,6 @@
     cases their maintainers are unresponsive, gone missing, or not listening
     to bug reports for other reasons.
 
-    See COMPARISON, below, for a comparison to some other JSON modules.
-
     See MAPPING, below, on how JSON::XS maps perl values to JSON values and
     vice versa.
 
@@ -631,11 +629,19 @@
     stream incrementally. It does so by accumulating text until it has a
     full JSON object, which it then can decode. This process is similar to
     using "decode_prefix" to see if a full JSON object is available, but is
-    much more efficient (JSON::XS will only attempt to parse the JSON text
-    once it is sure it has enough text to get a decisive result, using a
-    very simple but truly incremental parser).
+    much more efficient (and can be implemented with a minimum of method
+    calls).
+
+    JSON::XS will only attempt to parse the JSON text once it is sure it has
+    enough text to get a decisive result, using a very simple but truly
+    incremental parser. This means that it sometimes won't stop as early as
+    the full parser, for example, it doesn't detect parenthese mismatches.
+    The only thing it guarantees is that it starts decoding as soon as a
+    syntactically valid JSON text has been seen. This means you need to set
+    resource limits (e.g. "max_size") to ensure the parser will stop parsing
+    in the presence if syntax errors.
 
-    The following two methods deal with this.
+    The following methods implement this incremental parser.
 
     [void, scalar or list context] = $json->incr_parse ([$string])
         This is the central parsing function. It can both append new text