Meta Stack Exchange is where users like you discuss bugs, features, and support issues that affect the software powering all 157 Stack Exchange communities.

What is meta?
Here's how it works:
  1. Any Stack Exchange user can ask a question
  2. The community provides support, votes on ideas, and reports bugs
  3. Your voice helps shape the way Stack Exchange operates

Editing questions from new users for formatting issues is a routine task here on SO, and most of the time I just fix the problem and move on.

Just now I spotted a question that began with a large bolded greeting and used <br/> tags to force new lines instead of using double line breaks. I proceeded to edit the question, then composed a comment explaining how line-breaks work in markdown. Before posting it, I realised that there is a good argument for the comment being noise, since it does not directly pertain to the question.

Is it appropriate to leave a comment explaining what the OP did wrong instead of just silently editing the question (which could be confusing for the OP)?

share|improve this question
6  
Just put the comment as the edit reason, when the OP will see the revisions page he'll see it. – Shadow Wizard Nov 14 '12 at 9:17
1  
I use them for instructional purposed from time to time. A link to the markdown help in this case for example. Nothing wrong with that. – Bart Nov 14 '12 at 9:26
    
When you are about to ask a question or answer a question, help is given abunduntly at SO. New users might be so annoyed with the help system and make it a habit to not to go through it. So, I think this practice may encourage such habits. – manas Nov 14 '12 at 9:26
up vote 10 down vote accepted

Sometimes I leave a comment after suggesting an edit, though usually I do that only for "First Posts" if:

  • the post was almost unreadable due to missing punctuation or missing casing,
  • the post CONTAINED SHOUTING,
  • the post contained abbreviations like u, plz, ur, etc. or
  • the post or its title contained urgency requests.

In those cases I friendly tell the OP the reasoning behind my improvement. I always include a reference on StackOverflow: How To Ask.

Why commenting when there is an edit summary field: Because new users do not necessarily know where to look for these information.

share|improve this answer
5  
It's also helpful to comment if you have made major edits to a post, perhaps to make it coherent. The comment should ask the OP if the post still conveys what they intended after editing, and invite them to make additional edits as needed. Frequently necessary when you come across questions asked by someone with rudimentary English skills, but that provided everything needed to ask the question. – Tim Post Nov 14 '12 at 9:38

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .
http://meta.stackexchange.com/questions/155617/should-you-leave-a-comment-explaining-edits
meta.stackexchange.com
crawl=CC-MAIN-2016-22
66718
application/http; msgtype=response
sha1:E7X33LLCZSUS3PK4XNSP6SS6TK5D6BWE
<urn:uuid:96900ff6-4c0f-41f3-81fe-374abb367507>
2016-05-25T03:25:38Z
104.16.115.182
sha1:JAFUQG3VSAURV6ZJ7YQEKQIBZHDAO73R
<urn:uuid:4cd49dbe-629a-4de2-a74e-3bef1441919c>
http://meta.stackexchange.com/questions/155617/should-you-leave-a-comment-explaining-edits
response
<urn:uuid:29de4ae6-c3bc-4c1e-90a6-c7d5039397e4>
robots: classic
hostname: ip-10-185-217-139.ec2.internal
software: Nutch 1.6 (CC)/CC WarcExport 1.0
isPartOf: CC-MAIN-2016-22
operator: CommonCrawl Admin
description: Wide crawl of the web for May 2016
publisher: CommonCrawl
format: WARC File Format 1.0
conformsTo: http://bibnum.bnf.fr/WARC/WARC_ISO_28500_version1_latestdraft.pdf