Return to Answer

Your edit absolutely shouldn't have been rejected if we go by the helpful hints in the help center (see editing and comments).

##Posts are Intended to be Collaboratively Edited

Editing is important for keeping questions and answers clear, relevant, and up-to-date. If you are not comfortable with the idea of your contributions being collaboratively edited by other trusted users, this may not be the site for you.

##Useful Information in Comments Should be Edited in to the Post

Edits are expected to be substantial and to leave the post better than you found it. Common reasons for edits include:

• To fix grammar and spelling mistakes
• To clarify the meaning of the post (without changing that meaning)
• To include additional information only found in comments, so all of the information relevant to the post is contained in one place
• To correct minor mistakes or add updates as the post ages
• To add related resources or hyperlinks

##Comments are not Permanent

###What are comments?

Comments are temporary "Post-It" notes left on a question or answer. They can be up-voted (but not down-voted) and flagged, but do not generate reputation. There's no revision history, and when they are deleted they're gone for good.

##Comments are Not Intended to Correct Mistakes

###When shouldn't I comment?

Comments are not recommended for any of the following:

• Suggesting corrections that don't fundamentally change the meaning of the post; instead, make or suggest an edit;

The people suggesting that this should be a comment, or you shouldn't touch incorrect code in answers are throwing the baby out with the bathwater. Almost all suggestions not to change code is limited to questions.

Unfortunately, it is a lot easier for people to say, "Code change, no good" and reject your edit than to actually comprehend what you've changed and determine if it's good. For people who don't understand the language, it's like trying to correct Czech spelling -- you're not going to be a good judge. Ideally, people would hit 'Skip', but then they wouldn't be making progress toward review badges.

Personally I hope you keep suggesting these edits, or better yet make it to 2000 rep so you can edit them without the queue. These edits make the site better and provide better resources for future readers. They should be encouraged, not rejected out of ignorance.

Your edit absolutely shouldn't have been rejected if we go by the helpful hints in the help center (see editing and comments).

Posts are Intended to be Collaboratively Edited

Editing is important for keeping questions and answers clear, relevant, and up-to-date. If you are not comfortable with the idea of your contributions being collaboratively edited by other trusted users, this may not be the site for you.

Useful Information in Comments Should be Edited in to the Post

Edits are expected to be substantial and to leave the post better than you found it. Common reasons for edits include:

• To fix grammar and spelling mistakes
• To clarify the meaning of the post (without changing that meaning)
• To include additional information only found in comments, so all of the information relevant to the post is contained in one place
• To correct minor mistakes or add updates as the post ages
• To add related resources or hyperlinks

Comments are not Permanent

What are comments?

Comments are temporary "Post-It" notes left on a question or answer. They can be up-voted (but not down-voted) and flagged, but do not generate reputation. There's no revision history, and when they are deleted they're gone for good.

Comments are Not Intended to Correct Mistakes

When shouldn't I comment?

Comments are not recommended for any of the following:

• Suggesting corrections that don't fundamentally change the meaning of the post; instead, make or suggest an edit;

The people suggesting that this should be a comment, or you shouldn't touch incorrect code in answers are throwing the baby out with the bathwater. Almost all suggestions not to change code is limited to questions.

Unfortunately, it is a lot easier for people to say, "Code change, no good" and reject your edit than to actually comprehend what you've changed and determine if it's good. For people who don't understand the language, it's like trying to correct Czech spelling -- you're not going to be a good judge. Ideally, people would hit 'Skip', but then they wouldn't be making progress toward review badges.

Personally I hope you keep suggesting these edits, or better yet make it to 2000 rep so you can edit them without the queue. These edits make the site better and provide better resources for future readers. They should be encouraged, not rejected out of ignorance.

Your edit absolutely shouldn't have been rejected if we go by the helpful hints in the help center (see editing and comments).

##Posts are Intended to be Collaboratively Edited

Editing is important for keeping questions and answers clear, relevant, and up-to-date. If you are not comfortable with the idea of your contributions being collaboratively edited by other trusted users, this may not be the site for you.

##Useful Information in Comments Should be Edited in to the Post

Edits are expected to be substantial and to leave the post better than you found it. Common reasons for edits include:

• To fix grammar and spelling mistakes
• To clarify the meaning of the post (without changing that meaning)
• To include additional information only found in comments, so all of the information relevant to the post is contained in one place
• To correct minor mistakes or add updates as the post ages
• To add related resources or hyperlinks

##Comments are not Permanent

###What are comments?

Comments are temporary "Post-It" notes left on a question or answer. They can be up-voted (but not down-voted) and flagged, but do not generate reputation. There's no revision history, and when they are deleted they're gone for good.

##Comments are Not Intended to Correct Mistakes

###When shouldn't I comment?

Comments are not recommended for any of the following:

• Suggesting corrections that don't fundamentally change the meaning of the post; instead, make or suggest an edit;

The people suggesting that this should be a comment, or you shouldn't touch incorrect code in answers are throwing the baby out with the bathwater. Almost all suggestions not to change code is limited to questions.

Unfortunately, it is a lot easier for people to say, "Code change, no good" and reject your edit than to actually comprehend what you've changed and determine if it's good. For people who don't understand the language, it's like trying to correct Czech spelling -- you're not going to be a good judge. Ideally, people would hit 'Skip', but then they wouldn't be making progress toward review badges.

Personally I hope you keep suggesting these edits, or better yet make it to 2000 rep so you can edit them without the queue. These edits make the site better and provide better resources for future readers. They should be encouraged, not rejected out of ignorance.

Your edit absolutely shouldn't have been rejected if we go by the helpful hints in the help center (see editing and comments).

##Posts are Intended to be Collaboratively Edited

Editing is important for keeping questions and answers clear, relevant, and up-to-date. If you are not comfortable with the idea of your contributions being collaboratively edited by other trusted users, this may not be the site for you.

##Useful Information in Comments Should be Edited in to the Post

Edits are expected to be substantial and to leave the post better than you found it. Common reasons for edits include:

• To fix grammar and spelling mistakes
• To clarify the meaning of the post (without changing that meaning)
• To include additional information only found in comments, so all of the information relevant to the post is contained in one place
• To correct minor mistakes or add updates as the post ages
• To add related resources or hyperlinks

##Comments are not Permanent

###What are comments?

Comments are temporary "Post-It" notes left on a question or answer. They can be up-voted (but not down-voted) and flagged, but do not generate reputation. There's no revision history, and when they are deleted they're gone for good.

##Comments are Not Intended to Correct Mistakes

###When shouldn't I comment?

Comments are not recommended for any of the following:

• Suggesting corrections that don't fundamentally change the meaning of the post; instead, make or suggest an edit;

The people suggesting that this should be a comment, or you shouldn't touch incorrect code in answers are throwing the baby out with the bathwater. Almost all suggestions not to change code is limited to questions.

Unfortunately, it is a lot easier for people to say, "Code change, no good" and reject your edit than to actually comprehend what you've changed and determine if it's good. For people who don't understand the language, it's like trying to correct Czech spelling -- you're not going to be a good judge. Ideally, people would hit 'Skip', but then they wouldn't be making progress toward review badges.

Personally I hope you keep suggesting these edits, or better yet make it to 2000 rep so you can edit them without the queue. These edits make the site better and provide better resources for future readers. They should be encouraged, not rejected out of ignorance.

Your edit absolutely shouldn't have been rejected if we go by the helpful hints in the help center (see editing and comments).

##Posts are Intended to be Collaboratively Edited

Editing is important for keeping questions and answers clear, relevant, and up-to-date. If you are not comfortable with the idea of your contributions being collaboratively edited by other trusted users, this may not be the site for you.

##Useful Information in Comments Should be Edited in to the Post

Edits are expected to be substantial and to leave the post better than you found it. Common reasons for edits include:

• To fix grammar and spelling mistakes
• To clarify the meaning of the post (without changing that meaning)
• To include additional information only found in comments, so all of the information relevant to the post is contained in one place
• To correct minor mistakes or add updates as the post ages
• To add related resources or hyperlinks

##Comments are not Permanent

###What are comments?

Comments are temporary "Post-It" notes left on a question or answer. They can be up-voted (but not down-voted) and flagged, but do not generate reputation. There's no revision history, and when they are deleted they're gone for good.

##Comments are Not Intended to Correct Mistakes

###When shouldn't I comment?

Comments are not recommended for any of the following:

• Suggesting corrections that don't fundamentally change the meaning of the post; instead, make or suggest an edit;

The people suggesting that this should be a comment, or you shouldn't touch incorrect code in answers are throwing the baby out with the bathwater. Almost all suggestions not to change code is limited to questions.

Unfortunately, it is a lot easier for people to say, "Code change, no good" and reject your edit than to actually comprehend what you've changed and determine if it's good. For people who don't understand the language, it's like trying to correct Czech spelling -- you're not going to be a good judge. Ideally, people would hit 'Skip', but then they wouldn't be making progress toward review badges.

Personally I hope you keep suggesting these edits, or better yet make it to 2000 rep so you can edit them without the queue. These edits make the site better and provide better resources for future readers. They should be encouraged, not rejected out of ignorance.

Your edit absolutely shouldn't have been rejected if we go by the helpful hints in the help center (see editing and comments).

##Posts are Intended to be Collaboratively Edited

Editing is important for keeping questions and answers clear, relevant, and up-to-date. If you are not comfortable with the idea of your contributions being collaboratively edited by other trusted users, this may not be the site for you.

##Useful Information in Comments Should be Edited in to the Post

Edits are expected to be substantial and to leave the post better than you found it. Common reasons for edits include:

• To fix grammar and spelling mistakes
• To clarify the meaning of the post (without changing that meaning)
• To include additional information only found in comments, so all of the information relevant to the post is contained in one place
• To correct minor mistakes or add updates as the post ages
• To add related resources or hyperlinks

##Comments are not Permanent

###What are comments?

Comments are temporary "Post-It" notes left on a question or answer. They can be up-voted (but not down-voted) and flagged, but do not generate reputation. There's no revision history, and when they are deleted they're gone for good.

##Comments are Not Intended to Correct Mistakes

###When shouldn't I comment?

Comments are not recommended for any of the following:

• Suggesting corrections that don't fundamentally change the meaning of the post; instead, make or suggest an edit;

The people suggesting that this should be a comment, or you shouldn't touch incorrect code in answers are throwing the baby out with the bathwater. Almost all suggestions not to change code is limited to questions.

Unfortunately, it is a lot easier for people to say, "Code change, no good" and reject your edit than to actually comprehend what you've changed and determine if it's good. For people who don't understand the language, it's like trying to correct Czech spelling -- you're not going to be a good judge. Ideally, people would hit 'Skip', but then they wouldn't be making progress toward review badges.

Personally I hope you keep suggesting these edits, or better yet make it to 2000 rep so you can edit them without the queue. These edits make the site better and provide better resources for future readers. They should be encouraged, not rejected out of ignorance.