diff --git a/about/cost-management.html.md b/about/cost-management.html.md
index 8b6002655a..7d5d8ec7f6 100644
--- a/about/cost-management.html.md
+++ b/about/cost-management.html.md
@@ -6,6 +6,10 @@ author: kcmartin
date: 2025-10-23
---
+
+
+
+
## Predicting your Fly.io bill and avoiding surprises
We’ve done our best to make billing on Fly.io something you can reason about. Machines don’t appear out of nowhere. If something is running, it’s because you launched it, or you configured something that did. In general, when we talk about **autoscaling**, we mean starting or stopping machines you’ve already defined. We don’t quietly spin up extras in the background that turn into mystery charges on your bill. The idea is that your bill should always be traceable to something you can see, name, and plausibly explain when someone asks. If it’s not, we’re happy to help you sort it out.
diff --git a/about/free-trial.html.md b/about/free-trial.html.md
index 2c97fa4cf1..2f3c24dbb6 100644
--- a/about/free-trial.html.md
+++ b/about/free-trial.html.md
@@ -6,6 +6,10 @@ author: kcmartin
date: 2025-10-27
---
+
+
+
+
**Fly.io runs your apps close to your users. This page explains how our free trial works and what resources you can use before you need to add a payment method.**
## Free Trial overview
diff --git a/apps/app-handover-guide.html.md b/apps/app-handover-guide.html.md
index 9df92025a2..8687731903 100644
--- a/apps/app-handover-guide.html.md
+++ b/apps/app-handover-guide.html.md
@@ -6,6 +6,10 @@ author: kcmartin
date: 2025-07-03
---
+
+
+
+
**If you're building an app for someone else and they’re going to run it themselves on Fly.io, you’ve got two good options. You can either start development inside their Fly.io organization, or build it in yours and move it over later. Here’s how both paths work, and what can get messy during the move.**
**Fly.io runs apps close to your users by turning Docker images into VMs running in our global network. This is a practical guide for using Docker effectively on Fly.io.**
diff --git a/networking/custom-private-networks.html.markerb b/networking/custom-private-networks.html.markerb
index 0f8a3a48d4..b965eb518f 100644
--- a/networking/custom-private-networks.html.markerb
+++ b/networking/custom-private-networks.html.markerb
@@ -4,6 +4,10 @@ layout: docs
nav: firecracker
---
+
+
+
+
You can isolate users, data, or code using custom private networks.
Every organization gets a default [private network](https://fly.io/docs/networking/private-networking/) (6PN) and all the apps in that network can communicate privately using `.internal` domains. When you create a new app, you can choose to place it on a distinct custom 6PN within your organization. Apps on separate 6PNs can never communicate unless explicitly configured to do so.
diff --git a/networking/egress-ips.html.md b/networking/egress-ips.html.md
index cfcd3dfe92..04c3da5b92 100644
--- a/networking/egress-ips.html.md
+++ b/networking/egress-ips.html.md
@@ -6,6 +6,10 @@ author: kcmartin
date: 2025-10-02
---
+
+
+
+
## Overview
- By default, outbound (egress) IPs from Fly Machines are **unstable** and may change.