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.

6

You're expected to summarize what the documentation has to say about it - or don't answer at all. A documentation link might be useful to add as a comment, if you're not too snarky about it.

Aarobot
– Aarobot

2012-08-18 15:27:37 +00:00
Commented Aug 18, 2012 at 15:27
Yes, you're supposed to do that. Even links to official documentation can rot. Not only does the answer I have posted then go out of date... When was the last time you've seen an answer which got plain out of date if it was from the official documentation? ...and probably violates the copyright of the library. You mean of the documentation? I have never seen an official documentation which it was not allowed to quote from (NDAs and similar aside).

Time Traveling Bobby
– Time Traveling Bobby

2012-08-20 07:04:17 +00:00
Commented Aug 20, 2012 at 7:04

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 »