You are not logged in. Your edit will be placed in a queue until it is peer reviewed.
We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.
Required fields*
- Agree with that; haven't we been mentioning that since the dark days of uservoice? (mention @Jeff just for the notification)Marc Gravell– Marc Gravell StaffMod2010-03-31 09:48:46 +00:00Commented Mar 31, 2010 at 9:48
- 13I like #4 - allow low-rep users to merely suggest an edit that must then be approved by the op.Joel Coehoorn– Joel Coehoorn Mod2010-04-06 19:28:49 +00:00Commented Apr 6, 2010 at 19:28
- I would like to hear more about your proposal for #1, with some very specific .. specifics.Jeff Atwood– Jeff Atwood StaffMod2010-04-25 10:19:30 +00:00Commented Apr 25, 2010 at 10:19
- @Jeff: Well, by "in that area" I did mean "editing", not "the site / topic as a whole". I think the CW system recognizes that there is a place for low-rep edits, but forces an all-or-none approach to enabling it. Anyway, I expanded #1 a bit; if you want more detail I can post something in the feature requestShog9– Shog9 Staff2010-04-25 22:38:38 +00:00Commented Apr 25, 2010 at 22:38
- @shog9 the feature request is extremely.. threadbare.. and needs a lot more information.Jeff Atwood– Jeff Atwood StaffMod2010-04-26 01:38:42 +00:00Commented Apr 26, 2010 at 1:38
- I like new users to be able to edit, with the auther or someone else aproving the edit. We now have lots of new users on some sites that have used other SE sites for a long time.Ian Ringrose– Ian Ringrose2010-08-24 07:53:26 +00:00Commented Aug 24, 2010 at 7:53
- 3#4 has been implemented.uɐɯsO uɐɥʇɐN– uɐɯsO uɐɥʇɐN2011-10-01 17:38:20 +00:00Commented Oct 1, 2011 at 17:38
- 3...and #1, and #2, and #3badp– badp2012-05-31 21:23:29 +00:00Commented May 31, 2012 at 21:23
Add a comment |
How to Edit
- Correct minor typos or mistakes
- Clarify meaning without changing it
- Add related resources or links
- Always respect the author’s intent
- Don’t use edits to reply to the author
How to Format
- create code fences with backticks ` or tildes ~ ```
like so
``` - add language identifier to highlight code ```python
def function(foo):
print(foo)
``` - put returns between paragraphs
- for linebreak add 2 spaces at end
- _italic_ or **bold**
- indent code by 4 spaces
- backtick escapes
`like _so_` - quote by placing > at start of line
- to make links (use https whenever possible) <https://example.com>[example](https://example.com)<a href="https://example.com">example</a>
How to Tag
A tag is a keyword or label that categorizes your question with other, similar questions. Choose one or more (up to 5) tags that will help answerers to find and interpret your question.
- complete the sentence: my question is about...
- use tags that describe things or concepts that are essential, not incidental to your question
- favor using existing popular tags
- read the descriptions that appear below the tag
If your question is primarily about a topic for which you can't find a tag:
- combine multiple words into single-words with hyphens (e.g. stack-overflow), up to a maximum of 35 characters
- creating new tags is a privilege; if you can't yet create a tag you need, then post this question without it, then ask the community to create it for you