Edit - Software Engineering 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

I think you're confusing legacy software support with customer support. The latter is rarely about bugs, but mostly about teaching confused users how to do things they can't figure out themselves, or resolving failures in the system in non technical ways (e.g. arranging refunds, administrative override).

Lie Ryan
– Lie Ryan

2018-12-29 05:30:10 +00:00
Commented Dec 29, 2018 at 5:30
Which answers do you consider to be the "first two" answers? The ordering of answers can change over time. Do you mean the first two by timestamp, the first two based on votes, or the first two based on something else?

Bryan Oakley
– Bryan Oakley

2018-12-29 06:31:07 +00:00
Commented Dec 29, 2018 at 6:31

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 »