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

editorial: tweak recent commit #376

Closed
wants to merge 3 commits into from
Closed

Conversation

jmdyck
Copy link
Collaborator

@jmdyck jmdyck commented Feb 8, 2016

No description provided.

(16 occurrences, all in "Applying the `**` operator")
... for consistency with the rest of the spec.
(20 occurrences, all in "Applying the `**` operator")
... "Applying the `**` operator"
@@ -12770,33 +12770,33 @@
</ul>
</emu-clause>
<emu-clause id="sec-applying-the-exp-operator">
<h1>Applying the `**` operator</h1>
<h1>Applying the `**` Operator</h1>
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The spec isn’t consistent as to whether title case or sentence case should be used for headings. E.g. https://tc39.github.io/ecma262/#sec-normative-references uses sentence case, but https://tc39.github.io/ecma262/#sec-ecmascript-overview uses title case. (I’d personally prefer sentence case everywhere.)

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, it's pretty consistent on using title-case. Your example of sentence-case was changed to title-case 4 days ago in 5ee6f14. (I guess the rendered version hasn't caught up yet.)

(Looking at some example specs, it seems like ECMA prefers title-case and ISO prefers sentence-case.)

@bterlson bterlson closed this in 3a86c45 Feb 8, 2016
@jmdyck jmdyck deleted the minor_editorial branch February 9, 2016 01:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants