[glen-84]

Summary

• The persisted-operation route examples on the Fusion and Hot Chocolate cache-control pages put the operation name in the segment the route reads as the operation ID. They now follow /graphql/persisted/{operationId}/{operationName}, the order the endpoints page and the first-party API guide show.
• The Hot Chocolate page carried text written for a Fusion gateway: a sentence saying the gateway needs policy metadata, a second header-assembly section that repeated the first one's merge rules for a planned operation tree, and a "Putting It Together" list about subgraphs and composition. The second section is removed, and the other two describe a single server.

[Copilot]

🟢 Approval recommended

The documentation corrections are complete, with no unresolved review issues.

No open issues 🎉

What changed in this PR

This documentation-only pull request corrects persisted-operation route examples and removes Fusion-specific wording from the Hot Chocolate cache-control guide.

Changes:

• Updates persisted-operation URLs to /graphql/persisted/{operationId}/{operationName}.
• Revises Hot Chocolate guidance for a standalone server.
• Removes duplicated, gateway-specific cache-control content.

File	Description
website/​content/​docs/​hotchocolate/​server/​cache-control.md	Corrects route examples and aligns cache-control guidance with Hot Chocolate server behavior.
website/​content/​docs/​fusion/​cache-control.md	Corrects persisted-operation route examples for Fusion gateways.

_{Review effort: Lite}