Promise.try now routes through PromiseResolve
The non-error path for Promise.try was tightened to use PromiseResolve(_ctor_, ! _status_) rather than manually creating a capability and invoking its resolve function. This brings the algorithm more directly in line with the standard promise-resolution machinery.
Wide editorial cleanup and consistency pass
A broad set of spec text was regularized for readability and maintainability, including internal-method links, time-value naming, template-literal grammar, and a handful of related notes and section wordings. These are mostly editorial, but they touch enough surface area to improve consistency across the spec.
Other misc changes
- ecmarkup updated to 25.0.1
- Minor wording tweaks in
SetFunctionName, Module Environment Records, and related notes - Small mechanical refactors in array algorithms