Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Wording: Use shorter possessive form for abstract object properties #565

Merged
merged 7 commits into from
Feb 15, 2024
3 changes: 2 additions & 1 deletion docs/SpecCodingConventions.md
Original file line number Diff line number Diff line change
Expand Up @@ -54,7 +54,7 @@ Example:
```
The <dfn>maximum size</dfn> of a collection is...

1. Let |max| be the [=maximum size=] of |collection|.
1. Let |max| be |collection|'s [=maximum size=].
```

* When defining subsidiary terms, like properties of an object, members of an enum, etc, scope the definitions using `dfn-for` on the `dfn` or an ancestor.
Expand Down Expand Up @@ -96,6 +96,7 @@ Example:
* Use `[=list/For each=] |index| in [=the range=] X to Y, inclusive` when iterating over a numeric range; a range is implicitly an ordered set which is a type of list. Specify _inclusive_ or _exclusive_ regarding the upper bound, for clarity.
* Use "let" to introduce a variable and "set" to update a variable or assign to a property.
* Use « » notation for literal lists, which helps make it clear that they are not JavaScript arrays.
* When referring to abstract properties, use the short possessive form `|object|'s [=property=]`. Avoid the wordier `the [=property=] of |object|` form.


### Method Definitions
Expand Down
Loading