Inline highlighting shouldn't have a monospaced font

[DunnCoding]

We're currently setting the font of any words wrapped in back ticks to a monospaced font.

We should use this font for code blocks only, for inline we shouldn't use this as we're highlighting non-code items.

We could also reduce the font weight slightly I think.

[SueChaplain]

Suggestions, based on common highlighting:

class / package / API names = monospace
codeblocks = monospace
code snippets inline = monospace
directories / file paths / filenames / file extensions = monospace
scripts / command names / tool names = bold monospace
environment variables = bold monospace

[SueChaplain]

Do we need to update the title or description on this one @ddunn2 ? If we are referring to code inline, it should be backticked and ideally we show this in monospace. However, IIRC there might have been some issue with the CLI ref and how the content generated here was being transformed?