Should links and excerpts from relevant documentation be an edit or should they be a comment or should they be an separate answer?
Sometimes I find a helpful answer with a great example of the use of a command would benefit from a link directly to the documentation for that command. This often reveals more usages and better descriptions than the answer. I'm in the habit of editing answers to add links to this relevant content whenever I find myself googling something in the answer.
I did this yesterday on superuser and was surprised to find the edit rejected.
This edit was intended to address the author of the post and makes no sense as an edit. It should have been written as a comment or an answer.
In my edit, I don't believe I changed the original purpose or intention of the author. I simply linked to relevant documentation. I suppose I could have added the links as comments, but I didn't really mean to address the author as much as anyone else searching for more information. Furthermore, the documentation page is long, and I added two separate links to/from each relevant section in the answer/documentation.
I didn't think writing a new answer was appropriate either as I was only adding additional detail to an existing answer.
I also noticed that my edit stats are pretty poor (3 out of 9 rejected) so I figured I'd ask here before I cause any more trouble. I found another old edit which was rejected for the same reason as above. In that edit, I again saw my actions as adding additional information to an existing answer, in that case, the output of a command with a list of shortcuts. This one was admittedly closer to potentially being enough additional information to be its own answer, but still, I don't think my answer would have been materially different from the existing answer so I wasn't inclined to write a new one.
To state my title question differently: Is there a place for additional information like links to documentation and other excerpts?