Also link to Unicode Standard

dcodeIO · dcodeIO · commit 978e17cf6653 · 2020-10-11T05:26:08.000+02:00
diff --git a/README.md b/README.md
@@ -55,7 +55,7 @@ Encoding | Immediate value | Encoding unit
 [WTF-8](https://simonsapin.github.io/wtf-8/) | 0x0 | u8 / 8 bits
 [WTF-16](https://simonsapin.github.io/wtf-8/#wtf-16) | 0x1 | u16 / 16 bits
 
-The WTF family of encodings has been chosen over the respective UTF family of encodings because it is more lenient, i.e. does not introduce trapping behavior but defers sanitization to modules and APIs requiring it. JavaScript and most of its related APIs are effectively designed for WTF-16, not UTF-16, for example. Or as the Unicode Standard, Version 13.0 states in section 2.7 Unicode Strings:
+The WTF family of encodings has been chosen over the respective UTF family of encodings because it is more lenient, i.e. does not introduce trapping behavior but defers sanitization to modules and APIs requiring it. JavaScript and most of its related APIs are effectively designed for WTF-16, not UTF-16, for example. Or as [The Unicode Standard, Version 13.0 – Core Specification](http://www.unicode.org/versions/Unicode13.0.0/ch02.pdf) states in section 2.7 Unicode Strings:
 
 > Depending on the programming environment, a Unicode string may or may not be required to be in the corresponding Unicode encoding form. For example, strings in Java, C#, or ECMAScript are Unicode 16-bit strings, but are not necessarily well-formed UTF16 sequences. In normal processing, it can be far more efficient to allow such strings to contain code unit sequences that are not well-formed UTF-16—that is, isolated surrogates. Because strings are such a fundamental component of every program, checking for isolated surrogates in every operation that modifies strings can create significant overhead, especially because supplementary characters are extremely rare as a percentage of overall text in programs worldwide.
 
