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

Inconsistent terminology and spelling regarding start, startup, and start-up #3530

Closed
ben-craig opened this issue Dec 7, 2019 · 1 comment · Fixed by #3859
Closed

Inconsistent terminology and spelling regarding start, startup, and start-up #3530

ben-craig opened this issue Dec 7, 2019 · 1 comment · Fixed by #3859
Assignees

Comments

@ben-craig
Copy link

In n4842, I count two non-index instances of the spelling "start-up" (and one in the index).
I count four non-index instances of the spelling "startup" (and one in the index)
The sequence of letters "start" show up more than 100 hundred times, but many of those are referring to things that don't involve the beginning of program execution.
The heading [support.start.term] uses the terms "Start and termination". [basic.pre.1] mentions "starting and terminating a program".

The WD should pick one term and use it consistently.

@jensmaurer jensmaurer added the decision-required A decision of the editorial group (or the Project Editor) is required. label Dec 8, 2019
@jensmaurer
Copy link
Member

jensmaurer commented Feb 10, 2020

Editorial meeting: "start" is a point, whereas "startup" is a process. Be consistent. "at program startup" etc. should be "at program start" -> "At the start of the program". No hyphen. Also rename the section "start and termination" to say "startup and termination".

@jensmaurer jensmaurer removed the decision-required A decision of the editorial group (or the Project Editor) is required. label Feb 10, 2020
@jensmaurer jensmaurer self-assigned this Mar 10, 2020
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 a pull request may close this issue.

2 participants