Fix command line flag formatting in documentation

[Copilot]

Double hyphens in command line flags were being rendered as emdashes in documentation (e.g., —help instead of --help).

Changes

Wrapped all command line flag names in inline code blocks across documentation to prevent markdown auto-formatting from converting -- to —:

• Client docs (client/page.mdx): 13 flags in "Additional Flags" section
• Origin docs (origin/page.mdx): 8 flags in "Additional Command Line Arguments" section
• Cache docs (cache/page.mdx): 5 flags in "Additional arguments" section

Example

-* **-h or --help**: Takes no argument and can be used with any Pelican sub command
+* **`-h` or `--help`**: Takes no argument and can be used with any Pelican sub command

This matches the existing pattern used in other documentation pages (e.g., generating-tokens/page.mdx).

---

Also fixed typo in cache docs: "output the the console" → "output to the console"

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Fix formatting of "additional flags" in docs page</issue_title>
<issue_description>This is specifically referring to the Command Line Client Additional Flags section of the docs website.

Looks like some sort of autoformatting has turned the double hyphens (--) into emdashes (—). For example,

-h or —help

when it should be

-h or --help

At first glance, fix would be to either

1. Format as inline code blocks
2. Disable autoformatting that converts double hyphens into emdashes.

Anyone can do (1), but for (2) will probably need to consult Cannon.</issue_description>

<agent_instructions>Please address this - only in the documentation</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Fix formatting of "additional flags" in docs page #2471

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[turetske]

Simple and correct. Caught a typo as well.

[aowen-uwmad]

Looked good to me in the local preview.