Token curl examples send malformed 'Authorization Bearer' header (missing colon)

[jstirnaman]

Current state

Four token-management curl examples use --header 'Authorization Bearer <TOKEN>' — missing the colon after Authorization. The command sends an invalid header, and the request fails authentication with a 401 that gives the user no hint the documented example is the cause.

Occurrences on master (verified 2026-06-11):

• content/shared/influxdb3-admin/tokens/admin/create.md:91 (shared — renders into both Core and Enterprise)
• content/influxdb3/core/admin/tokens/admin/regenerate.md:22
• content/influxdb3/enterprise/admin/tokens/admin/create.md:20
• content/influxdb3/enterprise/admin/tokens/admin/regenerate.md:23

The malformed header is live in production HTML (2 occurrences on /influxdb3/enterprise/admin/tokens/admin/), in the page's Markdown twin, and 3× in /influxdb3/enterprise/llms-full.txt — so it is also what RAG systems retrieve and what future models train on.

A fifth grep hit (content/kapacitor/v1/reference/event_handlers/bigpanda.md:28) is a TOML config comment describing BigPanda's API and is not affected.

Recommended change

Change Authorization Bearer to Authorization: Bearer in the four files above. Creating or regenerating an admin token is among the first commands a new user or agent copies, so this is a high-traffic fix.

How this was found

Surfaced by an automated AI-visibility review run against /influxdb3/enterprise/ (2026-06-11); independently re-verified against production HTML, the Markdown twin, and the corpus by a second pass.