steps are not redundant; be more consistent about code point formatting

fetch.bs

@@ -6077,7 +6077,7 @@ that RFC's normative processing requirements to be compatible with deployed cont
  <li>
   <p><a>Strip leading and trailing ASCII whitespace</a> from <var>mimeType</var>.
 
-  <p class="note">This will only remove U+0020 <a>code points</a>, if any.
+  <p class="note">This will only remove U+0020 SPACE <a>code points</a>, if any.
 
  <li><p>If <var>position</var> is past the end of <var>input</var>, then return failure.
 
@@ -6102,15 +6102,10 @@ that RFC's normative processing requirements to be compatible with deployed cont
 
    <li><p>Remove trailing U+0020 SPACE <a>code points</a> from <var>mimeType</var>, if any.
 
-   <li><p>Remove the last <a>code point</a> from <var>mimeType</var>.
+   <li><p>Remove the last U+003B (;) <a>code point</a> from <var>mimeType</var>.
   </ol>
 
-  <p class="note">The last three steps above are redundant with
-  <a lt="parse a MIME type">MIME type parsing</a> as that data would end up discarded. It is
-  removed here as it is not part of the MIME type and MIME type parsing might report errors
-  out-of-band in the future.
-
- <li><p>If <var>mimeType</var> starts with "<code>;</code>", then prepend "<code>text/plain</code>"
+ <li><p>If <var>mimeType</var> starts with U+003B (;), then prepend "<code>text/plain</code>"
  to <var>mimeType</var>.
 
  <li><p>Let <var>mimeTypeRecord</var> be the result of <a lt="parse a MIME type">parsing</a>