Fix some review comments

Author: nicolo-ribaudo

spec.html

@@ -28507,11 +28507,11 @@ <h1>
       <emu-clause id="sec-synthetic-module-records">
         <h1>Synthetic Module Records</h1>
 
-        <p>A <dfn variants="Synthetic Module Records">Synthetic Module Record</dfn> is used to represent information about a module that is defined by specifications. Its exported names are statically defined at creation as an argument to CreateSyntheticModule, while their corresponding values can change over time using SetSyntheticModuleExport. It has no imports or dependencies.</p>
+        <p>A <dfn variants="Synthetic Module Records">Synthetic Module Record</dfn> is used to represent information about a module that is defined by specifications. Its exported names are statically defined at creation, while their corresponding values can change over time using SetSyntheticModuleExport. It has no imports or dependencies.</p>
 
-        <emu-note>A Synthetic Module Record could be used for defining a variety of module types: for example, built-in modules, or JSON modules, or CSS modules.</emu-note>
+        <emu-note>A Synthetic Module Record could be used for defining a variety of module types: for example, JSON modules or CSS modules.</emu-note>
 
-        <p>In addition to the fields defined in <emu-xref href="#table-module-record-fields"></emu-xref> Synthetic Module Records have the additional fields listed in <emu-xref href="#table-synthetic-module-record-fields"></emu-xref>. Each of these fields is initially set in CreateSyntheticModule.</p>
+        <p>In addition to the fields defined in <emu-xref href="#table-module-record-fields"></emu-xref> Synthetic Module Records have the additional fields listed in <emu-xref href="#table-synthetic-module-record-fields"></emu-xref>.</p>
 
         <emu-table id="table-synthetic-module-record-fields" caption="Additional Fields of Synthetic Module Records">
           <table>
@@ -28530,29 +28530,11 @@ <h1>Synthetic Module Records</h1>
             <tr>
               <td>[[EvaluationSteps]]</td>
               <td>an Abstract Closure</td>
-              <td>The initialization logic to perform upon evaluation of the module, taking the Synthetic Module Record as its sole argument. These will usually set up the exported values, by using SetSyntheticModuleExport. It must not modify [[ExportNames]]. It may return an abrupt completion.</td>
+              <td>The initialization logic to perform upon evaluation of the module, taking the Synthetic Module Record as its sole argument. It must not modify [[ExportNames]]. It may return an abrupt completion.</td>
             </tr>
           </table>
         </emu-table>
 
-        <emu-clause id="sec-createsyntheticmodule" type="abstract operation">
-          <h1>
-            CreateSyntheticModule (
-              _exportNames_: a List of Strings without duplicates,
-              _evaluationSteps_: an Abstract Closure,
-              _realm_: a Realm Record,
-            ): a Synthetic Module Record
-          </h1>
-          <dl class="header">
-            <dt>description</dt>
-            <dd></dd>
-          </dl>
-
-          <emu-alg>
-            1. Return the Synthetic Module Record { [[Realm]]: _realm_, [[Environment]]: ~empty~, [[Namespace]]: ~empty~, [[HostDefined]]: *undefined*, [[ExportNames]]: _exportNames_, [[EvaluationSteps]]: _evaluationSteps_ }.
-          </emu-alg>
-        </emu-clause>
-
         <emu-clause id="sec-create-default-export-synthetic-module" type="abstract operation">
           <h1>
             CreateDefaultExportSyntheticModule (
@@ -28567,7 +28549,7 @@ <h1>
             1. Let _realm_ be the current Realm Record.
             1. Let _setDefaultExport_ be a new Abstract Closure with parameters (_module_) that captures _defaultExport_ and performs the following steps when called:
               1. Perform SetSyntheticModuleExport(_module_, *"default"*, _defaultExport_).
-            1. Return CreateSyntheticModule(« *"default"* », _setDefaultExport_, _realm_).
+            1. Return the Synthetic Module Record { [[Realm]]: _realm_, [[Environment]]: ~empty~, [[Namespace]]: ~empty~, [[HostDefined]]: *undefined*, [[ExportNames]]: « *"default"* », [[EvaluationSteps]]: _setDefaultExport_ }.
           </emu-alg>
         </emu-clause>
 
@@ -28598,7 +28580,7 @@ <h1>
           </h1>
           <dl class="header">
             <dt>description</dt>
-            <dd>It can be used to set or change the exported value for a pre-established export of a Synthetic Module Record.</dd>
+            <dd>It can be used to set or change the exported value for an existing export of a Synthetic Module Record.</dd>
           </dl>
 
           <emu-alg>
@@ -28763,7 +28745,7 @@ <h1>
             <p>and it performs FinishLoadingImportedModule(_referrer_, _moduleRequest_, _payload_, _result_) where _result_ is a normal completion, then it must perform FinishLoadingImportedModule(_referrer_, _moduleRequest_, _payload_, _result_) with the same _result_ each time.</p>
           </li>
           <li>
-            <p>If _moduleRequest_.[[Attributes]] has an entry _entry_ such that _entry_.[[Key]] is *"type"* and _entry_.[[Value]] is *"json"*, the host environment must perform FinishLoadingImportedModule(_referrer_, _moduleRequest_, _payload_, _result_), where _result_ is either the Completion Record returned by an invokation of ParseJSONModule or a throw completion.</p>
+            <p>If _moduleRequest_.[[Attributes]] has an entry _entry_ such that _entry_.[[Key]] is *"type"* and _entry_.[[Value]] is *"json"*, the host environment must perform FinishLoadingImportedModule(_referrer_, _moduleRequest_, _payload_, _result_), where _result_ is either the Completion Record returned by an invocation of ParseJSONModule or a throw completion.</p>
           </li>
           <li>
             The operation must treat _payload_ as an opaque value to be passed through to FinishLoadingImportedModule.
@@ -28773,7 +28755,7 @@ <h1>
         <p>The actual process performed is host-defined, but typically consists of performing whatever I/O operations are necessary to load the appropriate Module Record. Multiple different (_referrer_, _moduleRequest_.[[Specifier]], _moduleRequest_.[[Attributes]]) triples may map to the same Module Record instance. The actual mapping semantics is host-defined but typically a normalization process is applied to _specifier_ as part of the mapping process. A typical normalization process would include actions such as expansion of relative and abbreviated path specifiers.</p>
 
         <emu-note>
-          <p>The above text implies that hosts *must* support JSON modules imported with `type: "json"` (if it completes normally), but it doesn't prohibit hosts from supporting JSON modules imported with no type specified.</p>
+          <p>The above text requires that hosts support JSON modules when imported with `type: "json"` (and HostLoadImportedModule completes normally), but it does not prohibit hosts from supporting JSON modules when imported without `type: "json"`.</p>
         </emu-note>
       </emu-clause>