Edit - Meta Stack Exchange

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.

Rev

3

The format could be like: “Cast close vote for {insert closure reason here}” – That would arguably confuse most users (and also be too long and thus would require a speciac interface). Rather I would have each close vote leave a canned comment (or upvote an existing one) like “I am voting to close this question because it is too broad. Please add details to narrow the answer set or to isolate an issue that can be answered in a few paragraphs.”
– Wrzlprmft
Commented Jan 26, 2016 at 8:54

Add a comment |

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

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>

formatting help »
answering help »