From ca57b0ab0871d79043823c0d238015adf68eaa76 Mon Sep 17 00:00:00 2001
From: Ms2ger <Ms2ger@gmail.com>
Date: Fri, 22 Nov 2024 16:33:10 +0100
Subject: [PATCH] Editorial: allow hosts to create ordinary global objects

There doesn't seem to be a reason for this hook to only allow *exotic* objects.
---
 spec.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/spec.html b/spec.html
index 8d08d7232f..0b082de0d1 100644
--- a/spec.html
+++ b/spec.html
@@ -11794,7 +11794,7 @@ <h1>InitializeHostDefinedRealm ( ): either a normal completion containing ~unuse
         1. Set the Realm of _newContext_ to _realm_.
         1. Set the ScriptOrModule of _newContext_ to *null*.
         1. Push _newContext_ onto the execution context stack; _newContext_ is now the running execution context.
-        1. If the host requires use of an exotic object to serve as _realm_'s global object, then
+        1. If the host requires use of a specific object to serve as _realm_'s global object, then
           1. Let _global_ be such an object created in a host-defined manner.
         1. Else,
           1. Let _global_ be OrdinaryObjectCreate(_realm_.[[Intrinsics]].[[%Object.prototype%]]).