[docs-scanner] E2B sandboxes page uses announcement framing instead of documentation framing

[github-actions]

File: content/manuals/ai/mcp-catalog-and-toolkit/e2b-sandboxes.md

Issue

The page opens with announcement-style framing that treats the E2B integration as a new development rather than documenting current functionality:

Docker has partnered with E2B, a provider of secure cloud sandboxes for AI agents. E2B sandboxes include direct access to Docker's MCP Catalog, a collection of 200+ tools from publishers including GitHub, Notion, and Stripe.

The phrase "Docker has partnered" and "E2B sandboxes include" reads like a press release announcing a new partnership, not documentation of an existing feature. This is reinforced by the note in _index.md:

E2B sandboxes now include direct access to the Docker MCP Catalog

The word "now" suggests this is a recent addition being announced.

Why this matters

Documentation should describe features as they currently exist, not frame them as announcements. Readers expect documentation to be timeless - describing what the product does today. Announcement framing makes readers wonder if this is still new/unstable, or if the documentation is outdated.

Suggested fix

Rewrite the opening to be descriptive rather than announcement-style:

E2B provides secure cloud sandboxes for AI agents with direct access to Docker's MCP Catalog, a collection of 200+ tools from publishers including GitHub, Notion, and Stripe.

When you create an E2B sandbox, you specify which MCP tools it should access. E2B launches these tools and provides access through the Docker MCP Gateway.

Remove "now include" from the note in _index.md or rewrite it to be descriptive rather than temporal.

---

Found by nightly documentation quality scanner