Editorial: "Foo exotic object" vs "Foo object"

[jmdyck]

For several values of 'Foo':

• Arguments/arguments
• Array
• Module namespace
• Proxy/proxy
• String

the spec uses both the phrase "Foo exotic object" and "Foo object", presumably as synonyms. It might be good to settle on a single form.

(Note that it also uses "Function object" and "Function exotic object", but not as synonyms.)

(Follow-up to #1460 (comment))

[jmdyck]

(Or if we don't settle on a single form, both forms should link to the same definition.)

[ljharb]

I would indeed expect "exotic" to always be present in usage, or only be present in definition.

[ljharb]

Conclusion from the call: the word "exotic" should decorate all instances of describing exotic objects.