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

5

(I'm just posting so it gets stuck to the top, JNat gets the actual credit. :D)
– Catija
Commented Oct 9, 2020 at 15:23
Is there a plan to get closer to hitting the targets next 2 months? If I look at the stats, last 2 answers (4 months) don't look great.
– Mast
Commented Nov 5, 2020 at 19:41
1

See the last target in the Nov./Dec. post, @Mast: "Make changes to the internal process and reporting, to align this process with our quarterly planning/roadmap. The process as outlined here has the intake of requests portion figured out, but work is needed on our internal workflows to better meet the targets we're setting."
– JNat StaffMod
Commented Nov 6, 2020 at 15:22
@JNat Well, yes. But that's a bit vague, isn't it?
– Mast
Commented Nov 6, 2020 at 15:46

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 »