Fix CR comments

source

@@ -34710,8 +34710,8 @@ interface <dfn interface>MediaError</dfn> {
        <li><p>Let <var>request</var> be the result of <span
        data-x="create a potential-CORS request">creating a potential-CORS request</span> given
        <var>current media resource</var>'s <span>URL record</span>, <var>destination</var>, and the
-       <span>media element</span>'s <code data-x="attr-media-crossorigin">crossorigin</code>
-       content attribute value.</p></li>
+       current state of <span>media element</span>'s
+       <code data-x="attr-script-crossorigin">crossorigin</code> content attribute.</p></li>
 
        <li><p>Set <var>request</var>'s <span data-x="concept-request-client">client</span> to the
        <span>media element</span>'s <span>node document</span>'s <span>relevant settings
@@ -34728,9 +34728,17 @@ interface <dfn interface>MediaError</dfn> {
        im which case <var>byteRange</var> would be a (number, number) tuple representing the two
        offsets.</p></li>
 
-       <li><p>If <var>byteRange</var> is not null, then <span>add a range header</span> to
-       <var>request</var> given <var>byteRange</var>[0] and
-       <var>byteRange</var>[1].</p></li>
+       <li>
+        <p>If <var>byteRange</var> is not "<code data-x="">entire resource</code>", then:</p>
+        <ol>
+         <li><p>If <var>byteRange</var>[1] is "<code data-x="">until end</code>" then
+         <span>add a range header</span> to <var>request</var> given
+         <var>byteRange</var>[0].</p></li>
+
+         <li><p>Otherwise, <span>add a range header</span> to <var>request</var> given
+         <var>byteRange</var>[0] and <var>byteRange</var>[1].</p></li>
+        </ol>
+       </li>
 
        <li>
         <!--FETCH--><p><span data-x="concept-fetch">Fetch</span> <var>request</var>, with