doc: add explanations for querystring

 - add an article: `decode a non-utf8 string`
 - explain default behaviour of `querystring.unescape`
 - add a note that the baviour can change if other folks on your
   team have overridden it

related to #9207

doc/api/querystring.markdown

@@ -43,7 +43,12 @@ Options object may contain `maxKeys` property (equal to 1000 by default), it'll
 be used to limit processed keys. Set it to 0 to remove key count limitation.
 
 Options object may contain `decodeURIComponent` property (`decodeURIComponent` by default),
-it can be used to decode `non-utf8` encoding string if necessary.
+it can be used to decode a `non-utf8` encoding string if necessary.
+
+`querystring.unescape` will try to use `decodeURIComponent` in the
+first place, and fallback to a safer method if it fails. As
+`querystring.unescape` is meant to be overwritten the
+behaviour of `querystring.unescape` can change.
 
 Example:
 
@@ -67,3 +72,7 @@ provided so that it could be overridden if necessary.
 
 The unescape function used by `querystring.parse`,
 provided so that it could be overridden if necessary.
+
+It will try to use `decodeURIComponent` in the first place,
+but if that fails falls back to a safer equivalent that
+doesn't throw on malformed URLs