Unset the top-level module fetch flag in dynamic imports

The the top-level module fetch is only used in two steps of "fetch a
single module script":
- Step 9, where it only has effect if  descrination is "worker",
  "sharedworker" or "serviceworker" (but for dynamic imports it's always
  "script")
- Step 11, where it only has effect if there are custom "perform the
  fetch" steps, but "fetch an import() module script graph" is never
  called with custom "perform the fetch" steps.

Author: nicolo-ribaudo

source

@@ -92826,10 +92826,10 @@ document.querySelector("button").addEventListener("click", bound);
   script</span>) or asynchronously (otherwise). The <var data-x="fetching-scripts-is-top-level">is
   top-level</var> flag will be set for all <span>classic script</span> fetches, and for the initial
   fetch when <span data-x="fetch an external module script graph">fetching an external module script
-  graph</span>, <span data-x="fetch a module worker script graph">fetching a module worker script
-  graph</span>, or <span data-x="fetch an import() module script graph">fetching an import() module
-  script graph</span>, but not for the fetches resulting from <code data-x="">import</code>
-  statements encountered throughout the graph.</p>
+  graph</span>, or <span data-x="fetch a module worker script graph">fetching a module worker script
+  graph</span>, but not for the fetches resulting from <code data-x="">import</code>
+  statements encountered throughout the graph or from <span data-x="fetch an import() module script
+  graph">fetching an import() module script graph</span>.</p>
 
   <div class="note">
    <p>By default, not supplying the <span data-x="fetching-scripts-perform-fetch">perform the
@@ -93137,7 +93137,7 @@ document.querySelector("button").addEventListener("click", bound);
    <li><p><span>Fetch a single module script</span> given <var>url</var>, <var>settings
    object</var>, "<code data-x="">script</code>", <var>options</var>, <var>settings object</var>,
    "<code data-x="">client</code>", <var>moduleRequest</var>, and with the
-   <var>top-level module fetch flag</var> set. If the caller of this algorithm specified custom
+   <var>top-level module fetch flag</var> unset. If the caller of this algorithm specified custom
    <span data-x="fetching-scripts-perform-fetch">perform the fetch</span> steps, pass those along as
    well. Wait until the algorithm asynchronously completes with <var>result</var>.</p></li>