From d195dd624b1e5e3a609160f2ee6d06f5c64a699d Mon Sep 17 00:00:00 2001 From: Philipp Winter Date: Mon, 15 Jun 2026 12:55:35 -0500 Subject: [PATCH] Fix typo. Really just s/chose/choose/. --- deep-dive/application.html.markerb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/deep-dive/application.html.markerb b/deep-dive/application.html.markerb index 3eb912216e..30f7d02241 100644 --- a/deep-dive/application.html.markerb +++ b/deep-dive/application.html.markerb @@ -11,7 +11,7 @@ order: 4 Your demo app is running by default on two [Fly Machines](/docs/machines/), our fast-launching VMs. -Both Machines stop when not in use, and start automatically when a new request comes in. [Autostop/autostart](/docs/launch/autostop-autostart/) is entirely configurable. You can chose to suspend instead of stop, configure a minimum number of Machines to keep running, or even decide never to stop Machines at all. +Both Machines stop when not in use, and start automatically when a new request comes in. [Autostop/autostart](/docs/launch/autostop-autostart/) is entirely configurable. You can choose to suspend instead of stop, configure a minimum number of Machines to keep running, or even decide never to stop Machines at all. The purpose of two Machines is twofold: redundancy and scalability. If one Machine goes down, the other can continue on. If both are available, when your app has higher traffic, both can be started to handle requests. You can [vertically scale](/launch/scale-machine/) the CPU and RAM on Machines.