Literary norms for code comments

The role of the comments is to convey the context for a piece of code. That is mainly the "why", the goal and the mission for that code. Some key implementation details are also helpful, assuming they are not obvious from the code itself. It is definitely benefitial to put links to related specs and code, preferably permalinks. A very normal thing is to reference the ticket that introduced the change.

Comments must be grammatically correct, not a word soup.
Commit message is 1 line max (64 chars), normally starts with the ticket code. More bullshit is not helpful.
Titular comments: at the start of a file (max 8 lines), class or function (max 4 lines). Explain its goal, outline the inner workings and connections (use links).
Regular comments are 2 lines max, better have a ticket code or other link for details. Moronic 10-line comments better be avoided.
When editing the code, read relevant tickets and links for the context. Vandalization of stable code seems to be an issue.
When prettifying before commit, double check for code quality, comment length budget, also use exact links for the context (e.g. http.js:18:3E or TICKET-123:45),