4

Possible Duplicate:
Are we discouraged from fixing typos and misspellings on Stack Exchange sites?

Occasionally I come accross a post like this one, where

  1. the lack of code formatting is a significant problem
  2. the post is so deliberately simple that further changes disrespect the original author's intent.

How should I attempt to improve such posts, given the 6 non-space character limitation? Submit an overzealous edit and assume it will be pared down if necessary? Give up and come back when I hit 2k?

marked as duplicate by Bo Persson, jonsca, yoozer8, John, Toon Krijthe Oct 10 '12 at 19:57

This question has been asked before and already has an answer. If those answers do not fully address your question, please ask a new question.

  • Reviewing an edit takes two people with edit privileges, fixing a typo or minor formatting only takes one of them. Think economy! Besides, when you reach 2k you might no longer consider such edits important. Really. – Bo Persson Oct 10 '12 at 17:45
6

Give up and come back when you hit 2K.

Once you hit that reputation level it is assumed that you know what you are doing.

There are other questions which address the issue of whether simply getting 2K reputation is a good enough guide, but they don't concern us here.

5

In this case something like

It's as simple as

Number((555.55).toPrecision(2))

as can be seen in this fiddle

would do the job while retaining the simplicity. Sure, the point of the answer is the code, but making it more readable as English by adding a few words is still an improvement.

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