Code Highlight markup and Link colouration fix constants.adoc

[animeshsrivastava24]

Code Highlight markup and Link colouration fix
Ref #546
@per1234 Please review does this matches with what you mentioned in the comment #546 (comment)

[per1234]

Thanks!

[SeppPenner]

@per1234 Again a question on this: I somehow remeber that you told me once not to include links into the backticks because the links are already highlighted as links (Not as code). Or did I misunderstand something there?

[per1234]

@SeppPenner you're referring to #546. Luckily, @animeshsrivastava24 found a solution to that. Previously, we were trying to use this style of markup to linkify code words with backticks:

link:../../../functions/digital-io/pinmode[`pinMode()`]

The problem was that for some reason this caused the link coloration of the text to be suppressed when the content was rendered on arduino.cc, so you could only tell that text was a link by hovering the mouse pointer over it. For this reason, when we wanted to make a link obvious we had to avoid using backticks on the code words:

link:../../../functions/digital-io/pinmode[pinMode()]

Which was unfortunate. @animeshsrivastava24 discovered that if you use this markup:

`link:../../../functions/digital-io/pinmode[pinMode()]`

then you get the code highlighting and link coloration both, like this:
pinMode()

My idea is that we can use both styles of markup, as I explain in detail here:
#546 (comment)

[SeppPenner]

Previously, we were trying to use this style of markup to linkify code words with backticks:

I can remeber that, yeah. It didn't work as expected.

Which was unfortunate. @animeshsrivastava24 discovered that if you use this markup:

link:../../../functions/digital-io/pinmode[pinMode()]
then you get the code highlighting and link coloration both, like this:
pinMode()

Good to know, I just wanted to be sure that this is correct.

Your idea from #546 (comment) seems the best way to go for this. I agree with you that multiple occurences of links within a certain amount of text will make it probably unreadable as you stated there. That was something I didn't think about when I created #462.