Addressing some of @kleinsin's comments

index.html

@@ -2755,7 +2755,7 @@ <h3>Basics</h3>
 <aside class="note">
     <p>The situation with regards to support of non-ASCII characters in <a>resource identifiers</a> has been complicated for a number of years due to lack of progress on a number of corner cases in the development of IRI specification. The [[URL]] specification attempts to address this by documenting the actual practice of browsers and other user-agents (the stated goal of the URL specification is to obsolete both RFCs).</p>
 
-    <p>In general, document formats on the Web use resource identifiers that contain non-ASCII plain text characters. Protocols such as&mdash;but not limited to&mdash;HTTP [[RFC9110]]) often use URIs, encoding non-ASCII characters as <code>%HH</code> escapes. In general, modern protocols expect URLs to use the UTF-8 character encoding, exactly as specified by IRI.</p>
+    <p>In general, document formats on the Web use IRIs, that is resource identifiers that encode non-ASCII plain text characters as characters. Protocols such as&mdash;but not limited to&mdash;HTTP [[RFC9110]]) use URIs, that is resource identifiers that encode non-ASCII characters as a sequence of bytes using <code>%HH</code> escapes. Because URI does not specify any particularly <a>character encoding</a>, the <code>%HH</code> escapes are prone to misinterpretation. To help combat this, many modern protocols and specifications expect URLs to use the UTF-8 character encoding, exactly as specified by IRI.</p>
 
     <div class="example">
 		<p>Here's an example of an IRI and its URI-encoded equivalent, where the <strong>path</strong> of the identifier is the Japanese word <span lang="ja" translate="no">文字化け</span> ("<a>mojibake</a>").</p>