This issue comes up very frequently:
Suggested Edit rejected because reviewers didn't know programming language
Why was my code edit rejected?
Why was my suggested edit rejected repeatedly?
What Do the Rules Say?
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;
Code edits are often rejected because people are too lazy to properly evaluate whether or not they are correct, and prefer clicking "reject" rather than "skip" if they don't have the inclination to properly review. To get these sorts of edits approved, you need to bend over backwards to make your average reviewer's life as easy as possible:
Make sure the edit to code is appropriate
I put together a handy faq-proposed to cover when to edit/not to edit code:
Improve your suggested edit comment
Right now you wrote:
fixed some minor issues, the default settings produce a Debug version
You can improve this to:
This will not work because the directory is wrong, so /HelloWorld/ was changed to /HelloWorld/bin/Debug
Or something more descriptive that tells the reviewer, "This is clearly wrong, and this is why" with a glance. Otherwise they will just reject it because it's "safer".
Wait for 2000 Rep
Because reviewers are so horrible at these sorts of suggested edits, you can just wait until 2000 reputation so you don't have to deal with them when making common-sense improvements.
Have faith knowing that you're in the right. Keep fighting the good fight.