tc39/ecma262

informal content within section 4.4 Terms and Definitions

Open

#2,673 opened on Feb 24, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)HTML (15,626 stars) (1,409 forks)batch import
editorial changegood first issue

Description

Terms and Definitions contains a lot of informal prose. We typically use full sentences, include all necessary context, use capitalisation and periods, etc. This section deviates from that. We should improve it.

Relatedly, once this prose is cleaned up, we may want to move each definition from this section to a more appropriate section. See #1278.

Contributor guide

Tech stack
html
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic understanding of ECMAScript specification
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
70
Research direction
Review the Terms and Definitions section in the ecma262 specification (https://tc39.es/ecma262/#sec terms and definitions). The section contains informal prose that needs to be rewritten to match the formal style used elsewhere in the spec. Also consider the discussion in issue #1278 about moving definitions to more appropriate sections. Ensure each definition is a complete sentence with proper capitalization and punctuation.