docs: normalize plaintext code blocks

[zeke]

The PR normalizes txt, fundamental, and raw fenced code blocks in markdown files to use text as the info string (i.e. language).

Resolves #32938

Checklist

• documentation is changed or added
• commit message follows commit guidelines

cc @nodejs/documentation

[DerekNonGeneric]

@zeke, I have a couple of concerns w/ your PR. The primary one being that we aren't nipping this in the bud. Ideally, we would be banning the txt info string while providing a suggestion for text. This would happen in remark-preset-lint-node. I fear you may have jumped the gun on this one and would have to defer further work on this PR until @Trott has made some comments in #32938.

[zeke]

Okay. Happy to help with an update to https://github.com/nodejs/remark-preset-lint-node if that seems like the right course of action.

defer further work on this PR until @Trott has made some comments in #32938.

Looks like @Trott has already weighed in there. Were you expecting further comment?

[DerekNonGeneric]

Were you expecting further comment?

Absolutely. If not in that particular issue, in this PR (or elsewhere). I would give it some time.

[DerekNonGeneric]

I've put a bit more thought into exactly what info strings are available and what they all mean. I will followup this review comment w/ a PR augmenting the documentation guide clarifying my suggestions. Hopefully, it will be persuasive enough to take these suggestions. :)

[BridgeAR]

Landed in f08174c

[DerekNonGeneric]

/re #33028 (comment) and #33028 (comment)

After updating the bundle to include the HTTP grammar, I noticed that although this is an HTTP request [almost] following HTTP semantics, it also includes linebreak escape characters.

This results in the sub-par highlighting as seen below. :(

I wonder if this is a deficiency in the highlighter's regex or this should have actually been text.

• Should I forgo my intention of highlighting http info strings?
• Will the new QUIC implementation include http info strings in its docs?

/cc @jasnell

[Trott]

• Should I forgo my intention of highlighting http info strings?

In the particular case from your screenshot, I think removing \r\n is appropriate. (As a general rule, I would think you can either show \n explicitly and not render the line break, or else there is no need to show \n. Since there are rendered line breaks here, the \r\n is not necessary to show.)