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

fixing typo #29

Closed
wants to merge 1 commit into from
Closed

fixing typo #29

wants to merge 1 commit into from

Conversation

paulsmelser
Copy link

I noticed that supersedes was spelt supercedes in my latest ADR. figured I'd put in a pull request to fix that.

@npryce
Copy link
Owner

npryce commented Aug 21, 2017

Gosh. I've misspelled "supercedes" my entire life! (or is that "misspelt"? :-) )

But I worry this change will break existing ADR repositories, since the linking of ADR documents relies on the text in the Status section.

@paulsmelser
Copy link
Author

Webster's dictionary says,

disputed spelling variant of supersede:

Supercede has occurred as a spelling variant of supersede since the 17th century, and it is common in current published writing. It continues, however, to be widely regarded as an error.

Given it is so commonly in use I would agree it is best to leave it as it is.

@paulsmelser
Copy link
Author

P.S. spelt or spelled are both correct depending on where you live. American english would most commonly use spelled.

@RinkeHoekstra
Copy link

... but 'supercedes' hurts every time I see it. And this is why:

From Wiktionary:

The form supercede is commonly considered a misspelling of supersede, since it results from confusion between Latin cedere (“give up, yield”) and sedere (“to sit”).[1] The original Latin word was supersedere (“to sit above”), which continued in Italian as soprassedere, but the ‘c’ spelling began to be used in Middle French, appeared in English as early as the 1400s, and is still sometimes found. The fact that 'supersede' is the only English word ending in -sede, while several end in -cede, also encourages confusion.

@paulsmelser
Copy link
Author

#75 Has re-opened the debate

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.

3 participants