Give the networking and API overview pages distinct titles

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).

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.