routes-domains../../headings/source/routes-domains.html.md.erb,
cloudfoundry/docs-dev-guide../../headings/published/routes-domains.html)routes-domains.code; notes file:
routes-domains.notes; anchors:
routes-domains.anchorsconsole fences with a prompt and output, at the top level and in a
list item, with variables inside
(L248-L253,
L260-L264).<pre><code> blocks with variables and HTML inside: six blocks
write username<span>@</span>example.com, which keeps Cloudflare from
hiding the address
(L148-L152),
and one holds '*' and *.foo., characters Markdown reads as emphasis
(L187-L191).<span>@</span> inside a fence, where it is text
(L121-L125).Nine code blocks, all console in native mode, each with the text of the
published page and its variables’ values (the code file). Two notes,
seven headings and six ids, as the earlier rounds check them.
username@example.com. The published page shows the
fence’s <span>@</span> as text. Decision (this round): markup shown as
text in a code block is a defect the converted page fixes; the
published page fails the code-block check here
(published check).<pre><code> blocks become fences in native mode, and the
<span>@</span> becomes @.