Rewrite note

Author: lucacasonato

document/js-api/index.bs

@@ -1245,7 +1245,7 @@ This document defines a host environment for WebAssembly. It enables a WebAssemb
 
 <h2 id="esm-integration">Integration with ECMAScript modules</h2>
 
-Note: The champions of the Wasm-ESM integration proposal deem it acceptable to implement this integration in two stages. In the first stage only source phase imports of WASM are supported (`import source xModule from "./x.wasm"`). In the second stage, evaluation phase imports would be supported too (`import xInstance from "./x.wasm"`). If initially implementing just source phase imports, the `GetExportedNames`, `ResolveExport`, `InitializeEnvironment`, and `ExecuteModule` abstract operations can be implemented as abstract operations unconditionally throwing a `TypeError` exception. In this case, module fetch and CSP integration is still required to be implemented as specified in this proposal.
+Note: It is possible to implement the Wasm-ESM integration in two stages. In the first stage only source phase imports of Wasm are supported (`import source xModule from "./x.wasm"`). In the second stage, evaluation phase imports would be supported too (`import xInstance from "./x.wasm"`). If initially implementing just source phase imports, the `GetExportedNames`, `ResolveExport`, `InitializeEnvironment`, and `ExecuteModule` abstract operations can be implemented as abstract operations unconditionally throwing a `SyntaxError` exception. In this case, module fetch and CSP integration is still required to be implemented as specified in this proposal. Implementers are encouraged to ship both stages at once, but it is deemed for implementers to initially ship the first stage and then quickly follow up with the second stage, if this aids "time to ship" in implementations.
 
 WebAssembly modules can be used in a module graph with ECMAScript modules.