I noticed that five of the pages in FAQ Index for Stack Overflow have an inline code block link to itself at the bottom of the question:
- Why not upload images of code/errors when asking a question?
- Under what circumstances may I add "urgent" or other similar phrases to my question, in order to obtain faster answers?
- Why can't I ask customer service-related questions?
- How do I ask and answer homework questions?
- If your question was not well received, read this before you post your next question
The link is formatted as markdown code, rather than as an actual link:
Quick link:
[Click here before you post your next question.](https://s.tk/onhold)
I'm guessing (though I haven't found documentation to confirm this guess) that this is a convenience feature for questions that frequently need to be shared, so they can be quickly copy/pasted.
The formatting and terminology used for this feature is inconsistent across these questions. The terms used are: "Canonical link", "Markdown link sample ", "Markdown link", and "Quick link". Most of them use https://, but two use protocol-relative URLs starting with //.
Current format variations:
Canonical link:
[Please do not upload images of code/errors when asking a question.](//meta.stackoverflow.com/q/285551)
Canonical link:
[Under what circumstances may I add "urgent" or other similar phrases to my question, in order to obtain faster answers?](//meta.stackoverflow.com/q/326569)
Markdown link sample:
[Why can't I ask customer service-related questions?](http://meta.stackoverflow.com/a/255746)
Markdown link:
[How do I ask and answer homework questions?](https://meta.stackoverflow.com/q/334822)
Quick link:
[Click here before you post your next question.](https://s.tk/onhold)
Should these link samples be made consistent across FAQ questions in terms of formatting, terminology, and HTTP scheme? If so, what term should be used, and what should the format be?
Note that one of the questions (Why not upload images of code/errors when asking a question?) is locked, so I personally can't update it if we should make it consistent.