lint: enforce some spelling conventions

[bakkot]

This rule is tripped 29 times on ECMA-262 master: in 26 places where we say *this* object instead of (as in the other 429 uses of *this*) *this* value", in 1 place where we say behavior instead of (as in the other 132 places) behaviour, and in 2 places where we say the empty string instead of (as in the other 76 places) the empty String.

I'll fix those as part of upstreaming this.

[bakkot]

Note that it is plausible that we actually do want to say *this* object; @rkirsling here observes that it appears to be a shorthand for "this value (which is an object)". It's only ever used to describe the behavior of built-in methods (e.g. String.prototype.concat). But I don't think it makes sense to have that distinction; in those cases nothing enforces that *this* is in fact an object.

[ljharb]

I'd agree; the receiver only has to be an object in sloppy mode, and builtin methods have RequireObjectCoercible to account for nullish values, so this value seems to be the proper choice.