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.

Required fields*

Rev

4

Also worth to go over the editor edits history and if many such bad edits flag for mod attention anyway, even if your own post is "safe" - as a measure to protect future victims.

user152859
– user152859

2024-03-14 13:10:21 +00:00
Commented Mar 14, 2024 at 13:10
2

@ShadowWizardLoveZelda you know very well I oppose any witch hunt but I can't control y'all ...

rene
– rene Mod

2024-03-14 13:14:25 +00:00
Commented Mar 14, 2024 at 13:14
2

Hardly a witch hunt, more like preventing abuse of a privilege. (In that specific case the editor's history is fine, checked some random edits.)

user152859
– user152859

2024-03-14 14:01:38 +00:00
Commented Mar 14, 2024 at 14:01
2

I agree that replacing the headings with bold text made things worse. However, reverting the change is nowhere near adequate to fix the question properly.

Karl Knechtel
– Karl Knechtel

2024-03-14 22:06:11 +00:00
Commented Mar 14, 2024 at 22:06

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 »