Editorial: Return created EC from InitializeHostDefinedRealm

spec.html

@@ -12080,7 +12080,7 @@ <h1>
  </emu-clause>
 
  <emu-clause id="sec-initializehostdefinedrealm" type="abstract operation">
- <h1>InitializeHostDefinedRealm ( ): either a normal completion containing ~unused~ or a throw completion</h1>
+ <h1>InitializeHostDefinedRealm ( ): either a normal completion containing an execution context or a throw completion</h1>
  <dl class="header">
  </dl>
 
@@ -12094,9 +12094,14 @@ <h1>InitializeHostDefinedRealm ( ): either a normal completion containing ~unuse
  1. If the host requires use of an exotic object to serve as _realm_'s global object, let _global_ be such an object created in a host-defined manner. Otherwise, let _global_ be *undefined*, indicating that an ordinary object should be created as the global object.
  1. If the host requires that the `this` binding in _realm_'s global scope return an object other than the global object, let _thisValue_ be such an object created in a host-defined manner. Otherwise, let _thisValue_ be *undefined*, indicating that _realm_'s global `this` binding should be the global object.
  1. Perform SetRealmGlobalObject(_realm_, _global_, _thisValue_).
- 1. Let _globalObj_ be ? SetDefaultGlobalBindings(_realm_).
+ 1. Let _result_ be Completion(SetDefaultGlobalBindings(_realm_)).
+ 1. If _result_ is an abrupt completion, then
+ 1. Remove _newContext_ from the execution context stack.
+ 1. Return ? _result_.
+ 1. Let _globalObj_ be ! _result_.
  1. Create any host-defined global object properties on _globalObj_.
- 1. Return ~unused~.
+ 1. Remove _newContext_ from the execution context stack.
+ 1. Return _newContext_.
  </emu-alg>
  </emu-clause>