Number terminology is normalized across the spec (
2fda459)
The spec replaces the overloaded term “finite” with “finite Number” in core Number definitions and algorithms, and adds a dedicated autolink target for that concept. This is mostly editorial, but it removes ambiguous wording and fixes incorrect linking in multiple clauses.
IsLooselyEqual now states the BigInt/Number finite-check directly (2477796)
The loose-equality algorithm now folds the finite-number requirement into the BigInt-vs-Number branch itself. That makes the precondition clearer and keeps the comparison logic aligned with the surrounding spec language.
Time values gain an explicit “finite time value” term (214a2d9)
The time-values section now names the integral, non-NaN case as a “finite time value.” This gives later references a precise term to point at without changing the underlying time model.
Other misc changes
- Number.prototype math/formatting algorithms were editorially aligned around finite-number preconditions and RangeError wording.
- Number.isFinite and Number.MAX_VALUE wording was simplified for consistency.
- Number::remainder assertions were split for readability.
- Additional editorial cleanup in numeric comparison and power/remainder clauses.