explained backticks

Author: WebReflection

README.md

@@ -76,3 +76,12 @@ escape('<'); // &amp;lt; instead of &lt;
 If we do not want to code with the fear that the order wasn't perfect or that our order in either escaping or unescaping is different from the order another method or function used, if we understand the issue and we agree it's potentially a disaster prone approach, if we add the fact in this case creating 4 RegExp objects each time and invoking 4 times `.replace` trough the `String.prototype` is also potentially slower than creating one function only holding one object, or holding the function too, we should agree there is not absolutely any valid reason to keep proposing a char-by-char implementation.
 
 We have proofs this approach can fail already so ... why should we risk? Just avoid and grab all chars at once or simply use this tiny utility.
+
+### Backtick
+Internt explorer < 9 has [some backtick issue](https://html5sec.org/#102)
+
+For compatibility sake with common server-side HTML entities encoders and decoders, and in order to have the most reliable I/O, this little utility will NOT fix this IE < 9 problem.
+
+It is also important to note that if we create valid HTML and we set attributes at runtime in the right way, and using this utility, backticks in strings cannot possibly affect attribute behaviors so it is safe to use this utility as such.
+
+If you need more chars and/or backticks to be escaped and unescaped, feel free to use alternatives like [lodash](https://github.com/lodash/lodash) or [he](https://www.npmjs.com/package/he)