From 25cb7a5f78563e74b0ee902b4c11a6a7ca6ef98c Mon Sep 17 00:00:00 2001 From: Kristin Martin Date: Fri, 16 Oct 2026 18:22:46 +0000 Subject: [PATCH] Give the networking and API overview pages distinct titles Both shared a title with a page in the main docs ("Networking", "Overview"). Sidebar labels are unchanged. Also replace networking's og:description, which Mintlify ignores for the meta description, with description. --- api/index.mdx | 3 ++- concepts/networking.mdx | 5 +++-- 2 files changed, 5 insertions(+), 3 deletions(-) diff --git a/api/index.mdx b/api/index.mdx index e7c6930..02cd77e 100644 --- a/api/index.mdx +++ b/api/index.mdx @@ -1,5 +1,6 @@ --- -title: Overview +title: "Sprites API overview" +sidebarTitle: "Overview" --- This section is the Sprites API reference, generated from the Sprites OpenAPI specification. For guides and worked examples, see [Working with Sprites](/sprites/working-with-sprites). diff --git a/concepts/networking.mdx b/concepts/networking.mdx index 2df83d8..0f16221 100644 --- a/concepts/networking.mdx +++ b/concepts/networking.mdx @@ -1,6 +1,7 @@ --- -title: Networking -og:description: "How traffic reaches a Sprite and how a Sprite reaches out. The URL and proxy that get you in, and the egress policy that governs what goes out" +title: "Sprite networking" +sidebarTitle: "Networking" +description: "See how traffic reaches a Sprite on Fly.io and how a Sprite reaches out: its HTTPS URL, the port proxy to your laptop, and the network policy for egress." --- A Sprite runs your code in the cloud, but it's meant to feel close. Traffic gets in two ways, an always-on HTTPS URL and a proxy that maps a remote port onto your laptop. A network policy governs what the Sprite can reach on its way out. This page is the model for both directions: how you reach in, and what a Sprite can reach going out. The exact commands live on the pages linked throughout.