5 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

Ideally, take the opportunity to improve the answer in some other way. Correct other errors like spelling and grammar if there are any. Add some explanation of how the code works, or improve the existing explanation. If the question has a failed attempt, explain why that attempt failed or improve the existing explanation.

For example, here, you can change “using Javascript” to “in JavaScript without jQuery”, since that is what distinguishes this answer from the other one.

While you're at it, as noted by Time Traveling Bobby, fix the other misplaced parenthesis: evidently (amt*100)/100 isn't quite right.

Even if you're unsure of what the code means, there's something you can do: test it. This gives you some objective assurance that what you're doing is right. It's not a foolproof method, sometimes your correction will itself have a flaw that your tests don't reveal, but it helps.

If you find no way to edit, but you have at least 50 reputation points, you can leave a comment. EditsEdits are the right way to correct minor mistakes, whereas commentscomments are for transitory issues; but if you can't make an edit, then “there's a mistake” becomes a transitory issue that you're leaving behind for someone else to fix later.

Ideally, take the opportunity to improve the answer in some other way. Correct other errors like spelling and grammar if there are any. Add some explanation of how the code works, or improve the existing explanation. If the question has a failed attempt, explain why that attempt failed or improve the existing explanation.

For example, here, you can change “using Javascript” to “in JavaScript without jQuery”, since that is what distinguishes this answer from the other one.

While you're at it, as noted by Time Traveling Bobby, fix the other misplaced parenthesis: evidently (amt*100)/100 isn't quite right.

Even if you're unsure of what the code means, there's something you can do: test it. This gives you some objective assurance that what you're doing is right. It's not a foolproof method, sometimes your correction will itself have a flaw that your tests don't reveal, but it helps.

If you find no way to edit, but you have at least 50 reputation points, you can leave a comment. Edits are the right way to correct minor mistakes, whereas comments are for transitory issues; but if you can't make an edit, then “there's a mistake” becomes a transitory issue that you're leaving behind for someone else to fix later.

Ideally, take the opportunity to improve the answer in some other way. Correct other errors like spelling and grammar if there are any. Add some explanation of how the code works, or improve the existing explanation. If the question has a failed attempt, explain why that attempt failed or improve the existing explanation.

For example, here, you can change “using Javascript” to “in JavaScript without jQuery”, since that is what distinguishes this answer from the other one.

While you're at it, as noted by Time Traveling Bobby, fix the other misplaced parenthesis: evidently (amt*100)/100 isn't quite right.

Even if you're unsure of what the code means, there's something you can do: test it. This gives you some objective assurance that what you're doing is right. It's not a foolproof method, sometimes your correction will itself have a flaw that your tests don't reveal, but it helps.

If you find no way to edit, but you have at least 50 reputation points, you can leave a comment. Edits are the right way to correct minor mistakes, whereas comments are for transitory issues; but if you can't make an edit, then “there's a mistake” becomes a transitory issue that you're leaving behind for someone else to fix later.

4 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

Ideally, take the opportunity to improve the answer in some other way. Correct other errors like spelling and grammar if there are any. Add some explanation of how the code works, or improve the existing explanation. If the question has a failed attempt, explain why that attempt failed or improve the existing explanation.

For example, here, you can change “using Javascript” to “in JavaScript without jQuery”, since that is what distinguishes this answer from the other one.

While you're at it, as notednoted by Time Traveling Bobby, fix the other misplaced parenthesis: evidently (amt*100)/100 isn't quite right.

Even if you're unsure of what the code means, there's something you can do: test it. This gives you some objective assurance that what you're doing is right. It's not a foolproof method, sometimes your correction will itself have a flaw that your tests don't reveal, but it helps.

If you find no way to edit, but you have at least 50 reputation points, you can leave a comment. Edits are the right way to correct minor mistakes, whereas comments are for transitory issues; but if you can't make an edit, then “there's a mistake” becomes a transitory issue that you're leaving behind for someone else to fix later.

Ideally, take the opportunity to improve the answer in some other way. Correct other errors like spelling and grammar if there are any. Add some explanation of how the code works, or improve the existing explanation. If the question has a failed attempt, explain why that attempt failed or improve the existing explanation.

For example, here, you can change “using Javascript” to “in JavaScript without jQuery”, since that is what distinguishes this answer from the other one.

While you're at it, as noted by Time Traveling Bobby, fix the other misplaced parenthesis: evidently (amt*100)/100 isn't quite right.

Even if you're unsure of what the code means, there's something you can do: test it. This gives you some objective assurance that what you're doing is right. It's not a foolproof method, sometimes your correction will itself have a flaw that your tests don't reveal, but it helps.

If you find no way to edit, but you have at least 50 reputation points, you can leave a comment. Edits are the right way to correct minor mistakes, whereas comments are for transitory issues; but if you can't make an edit, then “there's a mistake” becomes a transitory issue that you're leaving behind for someone else to fix later.

Ideally, take the opportunity to improve the answer in some other way. Correct other errors like spelling and grammar if there are any. Add some explanation of how the code works, or improve the existing explanation. If the question has a failed attempt, explain why that attempt failed or improve the existing explanation.

For example, here, you can change “using Javascript” to “in JavaScript without jQuery”, since that is what distinguishes this answer from the other one.

While you're at it, as noted by Time Traveling Bobby, fix the other misplaced parenthesis: evidently (amt*100)/100 isn't quite right.

Even if you're unsure of what the code means, there's something you can do: test it. This gives you some objective assurance that what you're doing is right. It's not a foolproof method, sometimes your correction will itself have a flaw that your tests don't reveal, but it helps.

If you find no way to edit, but you have at least 50 reputation points, you can leave a comment. Edits are the right way to correct minor mistakes, whereas comments are for transitory issues; but if you can't make an edit, then “there's a mistake” becomes a transitory issue that you're leaving behind for someone else to fix later.

3 Migration of MSO links to MSE links
source | link

Ideally, take the opportunity to improve the answer in some other way. Correct other errors like spelling and grammar if there are any. Add some explanation of how the code works, or improve the existing explanation. If the question has a failed attempt, explain why that attempt failed or improve the existing explanation.

For example, here, you can change “using Javascript” to “in JavaScript without jQuery”, since that is what distinguishes this answer from the other one.

While you're at it, as notednoted by Time Traveling Bobby, fix the other misplaced parenthesis: evidently (amt*100)/100 isn't quite right.

Even if you're unsure of what the code means, there's something you can do: test it. This gives you some objective assurance that what you're doing is right. It's not a foolproof method, sometimes your correction will itself have a flaw that your tests don't reveal, but it helps.

If you find no way to edit, but you have at least 50 reputation points, you can leave a comment. Edits are the right way to correct minor mistakes, whereas comments are for transitory issues; but if you can't make an edit, then “there's a mistake” becomes a transitory issue that you're leaving behind for someone else to fix later.

Ideally, take the opportunity to improve the answer in some other way. Correct other errors like spelling and grammar if there are any. Add some explanation of how the code works, or improve the existing explanation. If the question has a failed attempt, explain why that attempt failed or improve the existing explanation.

For example, here, you can change “using Javascript” to “in JavaScript without jQuery”, since that is what distinguishes this answer from the other one.

While you're at it, as noted by Time Traveling Bobby, fix the other misplaced parenthesis: evidently (amt*100)/100 isn't quite right.

Even if you're unsure of what the code means, there's something you can do: test it. This gives you some objective assurance that what you're doing is right. It's not a foolproof method, sometimes your correction will itself have a flaw that your tests don't reveal, but it helps.

If you find no way to edit, but you have at least 50 reputation points, you can leave a comment. Edits are the right way to correct minor mistakes, whereas comments are for transitory issues; but if you can't make an edit, then “there's a mistake” becomes a transitory issue that you're leaving behind for someone else to fix later.

Ideally, take the opportunity to improve the answer in some other way. Correct other errors like spelling and grammar if there are any. Add some explanation of how the code works, or improve the existing explanation. If the question has a failed attempt, explain why that attempt failed or improve the existing explanation.

For example, here, you can change “using Javascript” to “in JavaScript without jQuery”, since that is what distinguishes this answer from the other one.

While you're at it, as noted by Time Traveling Bobby, fix the other misplaced parenthesis: evidently (amt*100)/100 isn't quite right.

Even if you're unsure of what the code means, there's something you can do: test it. This gives you some objective assurance that what you're doing is right. It's not a foolproof method, sometimes your correction will itself have a flaw that your tests don't reveal, but it helps.

If you find no way to edit, but you have at least 50 reputation points, you can leave a comment. Edits are the right way to correct minor mistakes, whereas comments are for transitory issues; but if you can't make an edit, then “there's a mistake” becomes a transitory issue that you're leaving behind for someone else to fix later.

2 use SO help center (the comment privilege threshold is different, thanks Bill Woodger)
source | link
1
source | link