Editorial: remove erroneous closing parenthesis

Introduced in 7c5555a by accident.

source

@@ -104274,7 +104274,6 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
   encoding of the file.</p>
 
   <ol>
-
    <li><p>If the encoding that is already being used to interpret the input stream is a <span>UTF-16
    encoding</span>, then set the <span data-x="concept-encoding-confidence">confidence</span> to
    <i>certain</i> and return. The new encoding is ignored; if it was anything but the
@@ -104312,11 +104311,10 @@ dictionary <dfn>StorageEventInit</dfn> : <span>EventInit</span> {
    <i>certain</i>. Whenever possible, this should be done without actually contacting the network
    layer (the bytes should be re-parsed from memory), even if, e.g., the document is marked as not
    being cacheable. If this is not possible and contacting the network layer would involve repeating
-   a request that uses a method other than `<code data-x="">GET</code>`), then instead set the <span
+   a request that uses a method other than `<code data-x="">GET</code>`, then instead set the <span
    data-x="concept-encoding-confidence">confidence</span> to <i>certain</i> and ignore the new
    encoding. The resource will be misinterpreted. User agents may notify the user of the situation,
    to aid in application development.</p></li>
-
   </ol>
 
   <p class="note">This algorithm is only invoked when a new encoding is found declared on a