review feedback

source

@@ -106242,13 +106242,13 @@ document.querySelector("button").addEventListener("click", bound);
      testing if something is a JSON module script in algorithms, instead of just referring to the
      concept, then we should consider adding a type item to the module script struct.
     -->
-    </li>
+   </li>
 
-    <li>
-      <p>A <span>module script</span> is a <dfn data-export="">WebAssembly module script</dfn> if
-      its <span data-x="concept-script-record">record</span> is a <span>WebAssembly Module
-      Record</span>.</p>
-    </li>
+   <li>
+    <p>A <span>module script</span> is a <dfn data-export="">WebAssembly module script</dfn> if
+    its <span data-x="concept-script-record">record</span> is a <span>WebAssembly Module
+    Record</span>.</p>
+   </li>
   </ul>
 
   <p class="note">As CSS stylesheets and JSON documents do not import dependent modules, and do not
@@ -107155,9 +107155,10 @@ document.querySelector("button").addEventListener("click", bound);
      data-x="concept-script-fetch-options-referrer-policy">referrer policy</span> to
      <var>referrerPolicy</var>.</p></li>
 
-     <li><p>If <var>mimeType</var>'s <span data-x="MIME type essence">essence</span> is
-     <code>application/wasm</code> and <var>moduleType</var> is
-     "<code data-x="">javascript-or-wasm</code>", then:</p>
+     <li>
+      <p>If <var>mimeType</var>'s <span data-x="MIME type essence">essence</span> is
+      "<code>application/wasm</code>" and <var>moduleType</var> is
+      "<code data-x="">javascript-or-wasm</code>", then:</p>
       <ol>
        <li><p>Set <var>moduleScript</var> to the result of <span>creating a WebAssembly module
        script</span> given <var>bodyBytes</var>, <var>settingsObject</var>, <var>response</var>'s
@@ -109515,8 +109516,8 @@ dictionary <dfn dictionary>PromiseRejectionEventInit</dfn> : <span>EventInit</sp
   data-x="tuple">tuples</span> consisting of a <span>URL record</span> and a <span>string</span>.
   The <span>URL record</span> is the <span data-x="concept-request-url">request URL</span> at which
   the module was fetched, and the <span>string</span> indicates the type of the module (e.g. "<code
-  data-x="">javascript-or-wasm</code>").  The <span>module map</span>'s values are either a <span>module
-  script</span>, null (used to represent failed fetches), or a placeholder value "<code
+  data-x="">javascript-or-wasm</code>"). The <span>module map</span>'s values are either a
+  <span>module script</span>, null (used to represent failed fetches), or a placeholder value "<code
   data-x="">fetching</code>". </span><span data-x="module map">Module maps</span> are used to ensure
   that imported module scripts are only fetched, parsed, and evaluated once per
   <code>Document</code> or <a href="#workers">worker</a>.</p>
@@ -109555,7 +109556,8 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
   <div class="example">
    <p>Since module type is also part of the <span>module map</span> key, the following code will
    create two separate entries in the <span>module map</span> (the type is "<code
-   data-x="">javascript-or-wasm</code>" for the first, and "<code data-x="">css</code>" for the second):
+   data-x="">javascript-or-wasm</code>" for the first, and "<code data-x="">css</code>" for the
+   second):
 
    <pre><code class="html" data-x="">&lt;script type=module&gt;
   import "https://example.com/module";