From d79f27a7a52b883ebd0329d578d636ea0253ab69 Mon Sep 17 00:00:00 2001 From: Mike McNeil Date: Thu, 27 Jan 2022 12:50:18 -0600 Subject: [PATCH] =?UTF-8?q?Brand=20guidelines:=20=E2=80=9CFleetDM=E2=80=9D?= =?UTF-8?q?=20=20>>=20=E2=80=9CFleet=E2=80=9D=20or=20=E2=80=9CFleet=20Devi?= =?UTF-8?q?ce=20Management=E2=80=9D=20(#3903)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit * Brand guidelines: “FleetDM” >> “Fleet” or “Fleet Device Management” * Update FAQ.md --- docs/01-Using-Fleet/FAQ.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/01-Using-Fleet/FAQ.md b/docs/01-Using-Fleet/FAQ.md index 54c7a19c67..17ec708bb8 100644 --- a/docs/01-Using-Fleet/FAQ.md +++ b/docs/01-Using-Fleet/FAQ.md @@ -23,9 +23,9 @@ The upgrade from kolide/fleet to fleetdm/fleet works the same as any minor version upgrade has in the past. -Minor version upgrades in Kolide Fleet often included database migrations and the recommendation to back up the database before migrating. The same goes for FleetDM Fleet versions. +Minor version upgrades in Kolide Fleet often included database migrations and the recommendation to back up the database before migrating. The same goes for the new Fleet. -To migrate from Kolide Fleet to FleetDM Fleet, please follow the steps outlined in the [Upgrading Fleet section](../02-Deploying/06-Upgrading-Fleet.md) of the documentation. +To migrate from `kolide/fleet` to the new Fleet, please follow the steps outlined in the [Upgrading Fleet section](../02-Deploying/06-Upgrading-Fleet.md) of the documentation. ## Has anyone stress tested Fleet? How many clients can the Fleet server handle?