What is the etiquette for editing questions? How much is it OK to modify? What are the guidelines and what are the limits?

I am concerned that once a question has been edited, the difficulties facing the initial user may not be as conspicuous because the editor may have inadvertently filled in some critical conceptual gaps in the question.


  1. Datasets are sometimes presented in different ways including jpeg screenshots. How should they be reformatted, in particular to avoid presuming R familiarity or preference? On this issue I got moderator guidance from @whuber advising to format them as text (usually comma delimited), or else include the data in the answer.

  2. Should plots be always left untouched? Beyond subjective, aesthetic considerations, perhaps some subtle change in the presentation or the data may occur that defeats the purpose of the OP.

  3. Do you all agree that improving the grammar to make the question understandable is an OK reason for an edit?

  4. Is reformatting with $\LaTeX{}$ to beautify equations OK without exceptions?

  • $\begingroup$ Hi Antoni. This seems to be our best meta thread on editing questions and other questions are starting to get closed as duplicates of it. Nick's answer does indeed provide excellent guidance. However, the question is a bit long and its first part is more of an introduction. Given the question's popularity, I thought perhaps you might want to condense it to make it more to the point ("What is the etiquette for editing questions?"). (I guess if you prefer I could suggest an edit and you roll back if you don't like it.) Feel free to leave it as is if you find it more appropriate. Just an idea! $\endgroup$
    – amoeba
    Feb 13, 2016 at 21:53
  • $\begingroup$ @amoeba It would be greatly appreciated it if you edited this question. There is no question on my mind that the changes would be an improvement. So please, please go ahead... Just don't decompose it into eigenvectors :-) $\endgroup$ Feb 13, 2016 at 23:04
  • 1
    $\begingroup$ I gave it a shot. $\endgroup$
    – amoeba
    Feb 14, 2016 at 15:16

2 Answers 2


This is a series of side-notes to @Glen_b's excellent answer.

Editing is a public service. Even some small edits can just clean up a post and make it easier for everyone to read, which is a positive contribution. Often an edit can change a question that looks too messy to wade through to one that looks readable. Editing can and should help the OP, who should get more and quicker attention (and, although this is a side-effect, who should also get feedback on their presentation for future questions). It helps others too.

Editing does not impart a moral judgment. We can't confidently and consistently distinguish between over-hasty, lazy presentation and someone struggling with one, two or even all three of a second language; statistics they really don't understand; and a medium that is unfamiliar. That said, I will on occasion comment firmly that a question (or answer) is just too messy to be worth anyone's time to edit. If the OP isn't able or willing to fix the presentation, then that is the end of the story: we are all volunteers here and there is no obligation to be infinitely helpful.

Changing just one small thing requires a careful decision. It will bump the question momentarily to the top of the active list. Some people are irritated to re-open a post of interest to find one minute change. But even threads that have seen many posts can carry errors worth correcting. Nevertheless, for this and other reasons, it is good advice that if you edit, edit everything that you spot as deserving change, so as to make the edit worthwhile.

Editing just the title can be valuable too. Posters can be especially blind to typos in the title. Considering that titles are key for later searches, even trivial misspellings can be a nuisance. It's common that titles are too long and/or carry useless words (please help; question about; how to analyse my data). On the other hand, sometimes you need to flag to posters that they should think up a better title themselves. (It's a fact of life in a forum that some members use eccentric or inadequately informative titles as a criterion for what to ignore, so improving them may seem a disservice too.)

Edits can be of any aspect of presentation (text, mathematics, code or data presentation), but as far as possible should only clarify, not change, the statistical content that defines the question being asked.

So you can edit grammar, spelling, punctuation and style, but you should not change strange or even incorrect uses of statistical terms, or any other dubious statistical content, even if obvious to you. Naturally, you should only change the language if you are confident that you are right (or have better taste or style...)! (Don't worry too much about this; a mistaken edit can be reversed.)

Content that should be removed includes greetings (at the beginning of a post) or signatures (at the end) and any material that looks irrelevant to the question. That includes polite (or even not so polite) expressions of how confused the poster is, how much time they have already spent working on the problem, how grateful they will be for an answer and (especially) how urgent or important the question is. Other comments that can usually be cut include claims that the question is quick, easy or simple: sometimes such claims are just wrong, and when they are right they don't illuminate the question.

The aim is not to deny the human side underlying a question, but to focus exclusively on the technical content at its heart. In a busy world, being able to read that content quickly and easily is a bonus for all. (I leave open whether it's a benefit that editing sometimes makes it clearer that there is no underlying precise and concise question.)

There is, as often, a small tension between the immediate, short-term aim of helping the original poster and the ultimate, longer-term aim of building an archive of high quality answered questions that should be of interest or use to many readers (in many cases, long after a poster may have disappeared from the forum). But any errors, omissions, or confusion in the statistical content of a question are likely to be part of the OP's problem and should be left as posted. Someone who edits a question need have no intention of answering it, but it can be helpful to publicise difficult points through comments. For example, you say that you want to apply multivariate regression, but you only have one response variable, so I think you mean multiple regression.

Similarly, you can introduce or improve mark-up of mathematics, code and data, but should not change even poor notation choices, which could be part of the problem. I would correct trivia, as when someone has posted $\beta2$, but it's evident that they mean $\beta_2$, but if in doubt, do not edit, but rather comment. There seems to be a square missing from your variance formula.

I think that it is rare that you should replace someone's graph. But here is a further situation where that does seems right: when presented with a very crude hand-drawn graph that someone has scanned or photographed, you may without loss be able to do a much better job.

Similarly, you should be very cautious about editing any code, especially if it seems likely or certain that incorrect or inappropriate code is much or all of the real problem. In such cases it is the role of answers to explain and even to improve or correct the code. There are limited exceptions. For example, very long code lines are awkward if not annoying to read whenever they require scrolling horizontally. Editing the code to fit within the visible question window -- using whatever essentially cosmetic change ensures that -- is a small public service. Further, simple things that you can do may include inserting blank lines to divide the code into smaller coherent blocks. But you need to be sure that you are not changing the meaning of the code or affecting whether it will run as written. If in doubt, do not touch.

It is often a good idea to edit the tags supplied for a post. Posters often omit tags that are highly relevant (e.g. data-transformation) or specify tags that are fairly useless (e.g. mathematical-statistics for almost any post). A sensitive exception is the self-study tag, which ideally should be added only by the original poster to show self-awareness of the condition. Otherwise, disagreement over tags is easy enough to fix, so it is fine to edit if you are confident that you can improve tags.

Appendix: Statistics typos: a miscellaneous list

This is a list of some common typos arising in statistical literature.

The following statisticians' surnames end with "s", so watch out.

Thus whatever is attributed to them is tagged with (e.g.) Jeffreys or Jeffreys', but not Jeffrey's.

Harold Jeffreys 1891-1989

Colin L. Mallows 1930-

John P. Mills fl.1926 (Mills ratio)

Samuel Stanley Wilks 1906-1964 (but note Martin Bradbury Wilk 1922-2013)

Frank Yates 1902-1994

Here are some other surnames that are often mangled in writing.

Ole Eiler Barndorff-Nielsen 1935-

Carl Harald Cramér 1893-1985 (NB accent)

Student 1876-1937 was William Sealy Gosset (not Gossett)

Richard A. Leibler 1914-2003 (not Liebler)

George Pólya 1887-1985 (NB accent)

Alfréd Rényi 1921-1970 (NB accents)

Henry Scheffé 1907-1977 (NB accent)

Gideon Schwarz 1933-2007 (not Schwartz) (BIC)

Hermann Amandus Schwarz 1843-1921 (not Schwartz) (Cauchy-Schwarz)

Leonard Henry Caleb Tippett 1902–1985 (not Tippet)

Bernard Lewis Welch (1911-1989) but Roy Elmer Welsch

Frank Wilcoxon 1892–1965 (not Wilcox or Wilcoxin)

Charles P. Winsor 1895-1951 (not Windsor; hence Winsorize not Windsorize)

Some people cited in statistics share surnames. Were they relatives?

Bernoulli family. There were lots of them.

Playfair family. John Playfair (1748-1819) was brother of William Playfair (1759-1823).

Pearson family. Karl Pearson (1857-1936) was father of Egon S. Pearson (1896-1980).

Coxes. Gertrude M. Cox (1900-1978) was unrelated to David R. Cox (1924-2022).

Kendalls. Maurice G. Kendall (1907-1983) was unrelated to David G. Kendall (1918-2007).

Some bad Greek and Latin is common.

"polychotomous" is bad Greek, probably arising from a misunderstanding of "dichotomous", which is "dicho" + "tomous", not "di" + "chotomous". "polytomous" is better.

One criterion, two or more criteria. So never "a criteria".

"data" in Latin means "given things" and is a plural. What this implies for modern languages is discussable. See also comments below.

"strata" in Latin is another plural. "stratum" is the singular.

Some people want to insist that "heteroskedastic" and "homoskedastic" are the correct spellings. (There was no "c" in ancient Greek.) This argument was published in Econometrica. Oddly enough, the spellings "heteroscedastic" and "homoscedastic" are due to Karl Pearson, who was no enemy of "k"; he changed his own name from Carl and founded the journal Biometrika. Fans of "k" should promise to write of mikroekonomics and makroekonomics on the grounds that all the pertinent roots of those words are all Greek too. See an entire dedicated thread here.

Finally, here is some not yet idiomatic English (prejudices ahead).

The expressions "a data" (to mean a dataset) and "a code" (to mean a program) are not yet part of standard English. They are already collectives.

Using "skew" to mean "bias" is unfortunate, but general English usage has shifted strongly that way in recent years.

On the grey area between statistical terms we know (and sometimes love) and uses or abuses of the same words within and beyond statistics and science, see also the thread here.

  • 2
    $\begingroup$ Based on your earlier comments in chat I was keen to see you post -- especially because there's a few aspects where we differ. However, this is a better post even than I had hoped to see, with many good points and useful suggestions. It's important that people be able to see it here. $\endgroup$
    – Glen_b
    Nov 17, 2015 at 21:43
  • 1
    $\begingroup$ @Glen_b Thanks! I don't think we differ much at all. So far as I can gather, you lean towards fixing technical side issues and changing graphs to improve presentation a little more than I do. $\endgroup$
    – Nick Cox
    Nov 18, 2015 at 1:31
  • 1
    $\begingroup$ Yes, it's a small difference on a few items, but I think it's important to get a sense of those differences. I'll be considering those sort of edits more carefully, for one thing. $\endgroup$
    – Glen_b
    Nov 18, 2015 at 1:36
  • $\begingroup$ Re common name mangling: lower case gauss, and markov spring to mind. :) Also with respect to applying ancient Greek or Latin orthography to contemporary (statistical) English appears to me to be akin to the etymological fallacy. $\endgroup$
    – Alexis
    Mar 5, 2021 at 18:07
  • $\begingroup$ I am favour of recognising the great people at whose feet we sit and on whose shoulders we stand. It would be interesting to learn of any cases where family names should not receive an initial capital for some different reason. For no good reason, I find references to cox regression and box-cox transformations particularly painful. $\endgroup$
    – Nick Cox
    Mar 5, 2021 at 18:22
  • $\begingroup$ Thanks! on tags seems OK. On other thing that could be mentioned: code, I dislike to have to scroll horizontally to read code and its probably not just me. So I tend to edit code to fix this. Otherwise making code more readable is useful, but with care! $\endgroup$ Apr 4, 2021 at 1:17
  • $\begingroup$ @kjetilbhalvorsen Good point about having to scroll to read code. I've added a paragraph on code edits. $\endgroup$
    – Nick Cox
    Apr 4, 2021 at 9:20
  • 3
    $\begingroup$ IMHO, the most egregious common misspellings on CV are "Wilcox" and "Wilcoxin" for Frank Wilcoxon. The former is an original sin of the R development team while the latter must just be ignorance, fueled perhaps by the absence of the "on" in the R terminology... . Fortunately, these have been fixed in 98% of the cases. (Another awful misspelling is "Normal" for "Gauss," but that one left the barn long ago :-). $\endgroup$
    – whuber Mod
    Jan 28 at 21:54
  • 2
    $\begingroup$ @whuber Thanks for Wilcoxon; I've often muttered at Wilcox coming straight from an R function name (it's incidental that Wilcoxon also had a coauthor called Wilcox). I've also added Winsor, after seeing yet another Windsorize on this site. $\endgroup$
    – Nick Cox
    Jan 29 at 11:47

[Just to make clear, though my answers should always be read this way: this is personal opinion]

You don't need to have any intention of answering a question to edit it.

the difficulties facing the initial user may not be as conspicuous because the editor may have inadvertently filled in some critical conceptual gaps in the OP.

Where feasible, it's important to have a question and answer that will be understood by and be useful to more people.

Mostly you should lean toward letting the OP's phrasing stand, but you can certainly encourage the OP to clarify. While some people would lean toward never fixing misconceptions in the question, if it's a side issue to the main question and fixing it is likely to clarify that misconception for the OP it may be okay. (It can sometimes be hard to be sure, though.)

The concern you mentioned is certainly possible so if you do edit, care must be taken - and you can always invite the OP to change anything back.

In the case of plots, and beyond subjective, aesthetic considerations, perhaps some subtle change in the presentation or the data may occur that defeats the purpose of the OP.

Such things are always a small risk with edits. If you're aware of the possibility, it's unlikely to be a major problem. Note that edits can be rolled back.

How should data points be posted to avoid presuming R familiarity or preference?

Certainly avoid editing to make anything R-specific; if it's already R-specific that's different. It's perfectly possible to edit to produce a cleanly-formatted ASCII table, for example, which will copy-paste (or easily be read) into a wide variety of packages.

e.g. something formatted like this:

    A     B
    4     2
    4    10
    7     4
    7    22
    8    16
    9    10

... is not R-specific but will read straight into R with a copy-paste (type OPdata=read.table(stdin(),header=TRUE) then paste, press Enter and you have a data frame; or just read from clipboard rather than stdin)

So: plain ASCII text in a standard form (space delimited or comma-delimited, compatible with CSV) is desirable -- these can be read by almost anything. This is uniformly better that an image of numbers (since it contains the same information but can be used by answerers) ... but be very careful you don't change the data!

On this issue I got moderator guidance from @whuber advising to format them as text (usually comma delimited), or else include the data in the answer.

It's sensible advice; I'd add space-delimited to the mix of what's fine.

Should plots be always left untouched?

I don't have enough context to know what things you're proposing to fix, but usually you wouldn't alter a plot. Always is too strong.

There are some situations where I have edited a plot. One example is where there's a small plot with gigantic amounts of white-space around it (a plot smaller than 1/10 the size of a standard page (A4 or 8.5x11), say 3x2.5 inches sitting in a field of white pixels the size of a page. In that case I cut out almost all the white space.

Do you all agree that improving the grammar to make the question understandable is an OK reason for an edit in some cases?

Yes, almost always.

Is reformatting with latex to beautify equations OK without exceptions?

Nearly always, it's a good thing to do.

But without exception? That's hard to say, since exceptions may be things we haven't thought of. But in this case I can think of a few possible exceptions.

i. If I expect a post will move to SO I try to avoid LaTeX.

ii. If an equation can as easily be read as pseudocode (e.g. can very easily be turned into say a formula in R if left as is) I'm less inclined to edit it because there's another way to use it as it stands.

Your question is filled with requests for absolutes. That's not going to happen. Don't look for ironclad rules here. Just act sensibly, change things in ways that will clearly improve the post for as many people as you can, but with respect for the OP's intent.

If one is to edit (which is a very good thing to do), it's necessary to accept that:

  1. You will occasionally make mistakes (of judgement, say)

  2. Even when you act in very sensible ways, people will disagree occasionally; there can be legitimate difference of opinion

Don't get too bothered about these things unless there seem to be a lot of problems, in which case you may need to attempt to move your expectations toward the community norms more. Mistakes are not irretrievable -- as the saying goes, it's not rocket surgery.

Oh, and definitely put me down in the "the data were" column. "Datum" is singular, "data" is a plural noun.

  • $\begingroup$ Glen, Thank you for your answer. I tried the code and I got the following: OPdata=read(stdin(),header=TRUE) Error: could not find function "read" $\endgroup$ Nov 14, 2015 at 0:52
  • $\begingroup$ @Antoni thanks, that was meant to be read.table. I believe I originally typed read.table but I likely screwed it up during editing of my answer before posting. $\endgroup$
    – Glen_b
    Nov 14, 2015 at 1:39
  • 1
    $\begingroup$ I have a vague idea what rocket science is. However I would be interested to know what is rocket surgery? $\endgroup$
    – mpiktas
    Nov 17, 2015 at 14:51
  • 3
    $\begingroup$ @mpiktas Two common sayings are "it's not brain surgery" and "it's not rocket science", both of which mean the same thing. Mixing the two is amusing in a silly way, possibly implying the speaker (or writer in this case) is stupid. See urbandictionary or TvTropes or A Way With Words $\endgroup$
    – Glen_b
    Nov 17, 2015 at 15:16
  • $\begingroup$ Just as I suspected :) $\endgroup$
    – mpiktas
    Nov 17, 2015 at 15:17
  • 1
    $\begingroup$ @Nick Yes, I've watched those ventures with some amusement. It would be even funnier if the eventual outcome weren't so serious. $\endgroup$
    – Glen_b
    Nov 17, 2015 at 21:58
  • 1
    $\begingroup$ On data as singular and plural. Data clearly has a Latin root as a plural, but language changes and need not be logically consistent. Older folks who grew up writing down each value, adding them up and so forth are more likely to think of their data as plural than younger people for whom the data is [sic] just a single entity handled on the computer; and indeed the data can be both. Latin plurals can become singulars (who says "the agenda are long"?) and words can be both singular and plural (there's a hair on your shirt; I need to get my hair cut). $\endgroup$
    – Nick Cox
    Nov 18, 2015 at 9:57
  • 4
    $\begingroup$ I still usually prefer to say and write for myself "the data show", "the data are", but it's far, far too late to eradicate the other form. "The data is consistent with a linear pattern": I find myself saying such things too. But I still cringe at "I have a data" which I have only noticed in the last few years, but I can't put my finger on why. I think it's just that one form is idiomatic around me and the other isn't, so it's all probably food for the sociologists. $\endgroup$
    – Nick Cox
    Nov 18, 2015 at 10:03
  • 2
    $\begingroup$ Similarly on the word code as anything from a few lines in some language to a self-contained program. "I have some code"; "the code isn't working" sound fine but "I have a code" doesn't sound at all right and I tend to edit it out. That statement may well seem utterly parochial, all the way down to my perception of what is said among my own peer group of some British academics. But editing what is not widely idiomatic to what is widely idiomatic can be important too. $\endgroup$
    – Nick Cox
    Nov 18, 2015 at 10:07
  • 2
    $\begingroup$ Declaration of war: I always edit out i for I and gonna and wanna. $\endgroup$
    – Nick Cox
    Nov 18, 2015 at 10:08
  • 1
    $\begingroup$ @NickCox: Crowd is a collective noun rather than a mass noun. You can't say "I saw a water" or "I saw a cutlery". $\endgroup$ Nov 18, 2015 at 17:47
  • 2
    $\begingroup$ ctd... As far as I see, few people have said datum or agendum in a long time. $\endgroup$
    – Glen_b
    Nov 18, 2015 at 22:23
  • 2
    $\begingroup$ Datum retains a specific meaning in surveying and geodesy. For example, land surface altitudes in Britain are reported relative to Ordnance Datum. But within statistics stricter sense I don't think I've heard the word used in recent years, except facetiously. Data point is often useful and (often deliberately) matches the geometric or graphical meaning perfectly. $\endgroup$
    – Nick Cox
    Nov 18, 2015 at 23:40
  • 1
    $\begingroup$ I think "an errata" is more nearly just a mistake. Ditto "a criteria", "a phenomena" (switching to Greek from Latin). $\endgroup$
    – Nick Cox
    Nov 19, 2015 at 9:32
  • 1
    $\begingroup$ Of course data had a tragic flaw: the lack of a dominant, unambiguous criterion for individuation. We can, & often do, talk glibly of "data" without a clear notion of what a single datum would be (is a point on a scatter-plot a datum? or two data?). Though attempted explanations of grammatical categories in terms of semantics seem to throw up as many exceptions as regularities, there's a tendency for mass nouns to share this lack, & I feel that some sense of data's kinship to news, information, & the like played a part in the change. Even careful writers who treat ... $\endgroup$ Nov 19, 2015 at 10:34

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .