**The [Machines resource API](/docs/machines/api/machines-resource/) documents every endpoint. This guide covers the patterns you'll actually need when building on it: cloning machines, keeping them in sync with `flyctl`, configuring services, managing auto-stop/start behavior, and updating config.**
diff --git a/machines/overview.html.markerb b/machines/overview.html.markerb
index 17d3115cd1..5c5c2da4cb 100644
--- a/machines/overview.html.markerb
+++ b/machines/overview.html.markerb
@@ -5,6 +5,10 @@ nav: machines
redirect_from: /docs/reference/machines/
---
+
+
+
+
Fly Machines are fast-launching VMs with a simple [REST API](/docs/machines/api/). They're [the compute](https://fly.io/blog/fly-machines/) behind the Fly.io platform. If you've launched an app on Fly.io, you're already using Fly Machines.
We use the [Machines API](/docs/machines/api/) to build the orchestration for [Fly Launch](/docs/apps). You can use it however you'd like.
diff --git a/monitoring/metrics.html.md b/monitoring/metrics.html.md
index 2e9aad499c..2b460b9095 100644
--- a/monitoring/metrics.html.md
+++ b/monitoring/metrics.html.md
@@ -8,6 +8,10 @@ redirect_from:
- /docs/metrics-and-logs/metrics
---
+
+
+
+
The Fly.io platform includes a fully-managed metrics solution to help you easily monitor your Fly apps.
It includes the following components:
diff --git a/mpg/guides-examples/phoenix-guide.html.md b/mpg/guides-examples/phoenix-guide.html.md
index 811780fc1f..6a12c8cedb 100644
--- a/mpg/guides-examples/phoenix-guide.html.md
+++ b/mpg/guides-examples/phoenix-guide.html.md
@@ -6,6 +6,10 @@ date: 2025-09-16
author: Kaelyn
---
+
+
+
+
This guide explains the key **Managed Postgres (MPG)-specific adjustments** you need when connecting a Phoenix app. We'll focus on:
1. Connection Pooling Settings