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.

16

We will update the raw Markdown whenever it's safe to do so (i.e. the resulting HTML is equivalent to the old HTML). Technically this will rebake the HTML as well. We're storing the update as a new edit, triggered by the community user and without bumping the post itself.

Ham Vocke
– Ham Vocke StaffMod

2020-06-01 13:12:25 +00:00
Commented Jun 1, 2020 at 13:12
@HamVocke: Will you do some sort of automated checking that the old HTML is equivalent to the new HTML? (And maybe communicate whatever cannot be fixed to moderators?) As a MathOverflow and math.stackexchange user, I'm somewhat worried about posts suddenly becoming unreadable and staying so for years because no one with edit rights takes notice.

darij grinberg
– darij grinberg

2020-06-14 09:10:47 +00:00
Commented Jun 14, 2020 at 9:10
@darij meta.stackexchange.com/questions/348746/…

DavidG
– DavidG

2020-06-14 11:36:28 +00:00
Commented Jun 14, 2020 at 11:36

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 »