Follow-ups from docs#73: the graceful-shutdown pages say a cancel behaves identically on every engine, and that ShutdownTimeout bounds only the hooks

[FumingPower3925]

Follow-ups from goceleris/docs#73 (#673's docs), left open under the maintainer's two-round review cap (2026-09-27). CodeRabbit left two MINOR threads on docs#73. Both claims were checked against the docs at head 15a75d2 and celeris main fee0d1c, and both hold. They are tracked here instead of in that PR. Both sit where #703 will change the rule (today hook timing and the drain differ by engine), so the #703 lane should fix the text together with its fix.

1. graceful-shutdown.md:24-26 (at 15a75d2) says a cancelled context "behaves identically across std and the native Linux engines".

• The same page says hook timing depends on the engine: on std and adaptive the hooks run after the drain, on epoll and io_uring they can run while requests are still in flight (the "Shutdown sequence" section).
• The sentence predates docs#73 (it is in f6333a0).
• Fix: say that a cancel starts the shutdown on every engine, and that when the hooks run relative to the drain is engine-specific (or, after Server.Shutdown runs OnShutdown hooks and returns before epoll/io_uring drain in-flight requests, breaking its documented order #703, state the one rule).
• Thread: docs: EngineMetrics.Throughput always reads 0; the parser is not SIMD (celeris#653, celeris#424) docs#73 (comment)

2. Config.ShutdownTimeout is described as applying only to the hook phase, and getting-started promises every request finishes.

• graceful-shutdown.md, the "Entry points at a glance" rows for StartWithContext and StartWithListenerAndContext, say the timeout is "applied to the hook phase".
• On std and adaptive the watcher's Shutdown uses one context, bounded by ShutdownTimeout, for the engine drain and then every hook (celeris server.go listenUntilCancelled, then shutdown). The same page's note, "The shutdown context is shared across the engine drain and every hook", already says so.
• getting-started.md:191-192 (the code comment) and 200-201 say StartWithContext returns "after in-flight requests have finished". When the deadline expires first, the engine closes the remaining connections (engine contract, celeris engine/engine.go), so those requests do not finish.
• Fix: describe ShutdownTimeout as one deadline shared by the drain and the hooks on std and adaptive, and say the drain is attempted within it rather than promising every request finishes.
• Thread: docs: EngineMetrics.Throughput always reads 0; the parser is not SIMD (celeris#653, celeris#424) docs#73 (comment)

3. graceful-shutdown.md cites stale celeris/server.go line numbers. (CodeRabbit MINOR on docs#73 head 141386b.)

• The entry-point table cites celeris/server.go:354, 367, 705, 716, 771, and the FAQ cites server.go:777-780. At celeris main fee0d1c, Start is at 390, Shutdown at 453, StartWithListener at 855, StartWithListenerAndContext at 870, listenUntilCancelled at 899 (the 30 s default at 901-903) and StartWithContext at 974.
• The page's other locators (for example server.go:515-540 for PauseAccept and 748-763 for InheritListener) predate the v1.6.0 changes too.
• Fix: refresh every server.go locator on the page against the release commit, or cite symbols instead of line numbers, as the rest of the docs#73 text does (for example celeris/server.go (Shutdown)).
• Thread: docs: EngineMetrics.Throughput always reads 0; the parser is not SIMD (celeris#653, celeris#424) docs#73 (comment)

[FumingPower3925]

Closed by goceleris/docs#77 (merged as goceleris/docs@4f01d13), which rewrites the graceful-shutdown, getting-started, core-concepts, deployment and configuration pages for the behaviour that #746 (merged as dfd044f) ships. On every engine a cancel now runs the drain and then the hooks, and Config.ShutdownTimeout is one deadline for both. The server.go:NNN locators on graceful-shutdown.md now cite symbols. The listener sentence also depends on #747 (merged). Leftover minors and the wider locator sweep are in #779. #753, #759 and #760 stay open.