added v1.10 & v2 fallback notes

entries/jQuery.parseJSON.xml

@@ -16,7 +16,8 @@
     </ul>
     <p>The JSON standard does not permit "control characters" such as a tab or newline. An example like <code>$.parseJSON( '{ "testing":"1\t2\n3" }' )</code> will throw an error in most implementations because the JavaScript parser converts the string's tab and newline escapes into literal tab and newline; doubling the backslashes like <code>"1\\t2\\n3"</code> yields expected results. This problem is often seen when injecting JSON into a JavaScript file from a server-side language such as PHP.</p>
     <p>Where the browser provides a native implementation of <code>JSON.parse</code>, jQuery uses it to parse the string. For details on the JSON format, see <a href="http://json.org/">http://json.org/</a>.</p>
-    <p>Prior to jQuery 1.9, <code>$.parseJSON</code> returned <code>null</code> instead of throwing an error if it was passed an empty string, <code>null</code>, or <code>undefined</code>, even though those are not valid JSON. </p>
+    <p>Prior to jQuery 1.9, <code>$.parseJSON</code> returned <code>null</code> instead of throwing an error if it was passed an empty string, <code>null</code>, or <code>undefined</code>, even though those are not valid JSON.</p>
+    <p>Starting with jQuery 1.10, native ECMA-262 5th Edition's <code>JSON.parse</code> is attempted, and the internal function is used for fallback for non-compatable browsers.  jQuery 2's branch simply passes to <code>JSON.parse</code> with no fallback.</p>
   </longdesc>
   <example>
     <desc>Parse a JSON string.</desc>