From a9f335edec426e98c9a6b91974895f38bd9a4849 Mon Sep 17 00:00:00 2001
From: Noah Talerman <47070608+noahtalerman@users.noreply.github.com>
Date: Fri, 5 May 2023 17:31:27 -0400
Subject: [PATCH] MDM docs: Update bootstrap package docs (#11526)

- Clarify that Fleet uses the URL to upload the package to Fleet
---
 docs/Using-Fleet/MDM-macOS-setup.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/Using-Fleet/MDM-macOS-setup.md b/docs/Using-Fleet/MDM-macOS-setup.md
index 4e7dd56c10..c038106d1f 100644
--- a/docs/Using-Fleet/MDM-macOS-setup.md
+++ b/docs/Using-Fleet/MDM-macOS-setup.md
@@ -95,9 +95,9 @@ In the output you should see that package has a "signed" status.
 
 ### Step 3: upload the package to Fleet
 
-1. Upload the package to a storage location (ex. S3 or GitHub). In a later step, we'll use this location's URL to upload the package to Fleet.
+1. Upload the package to a storage location (ex. S3 or GitHub). During step 4, Fleet will retrieve the package from this storage location and host it for deloyment.
 
-> The storage location must be accessible by the computer that uploads the package to Fleet.
+> The URL must be accessible by the computer that uploads the package to Fleet.
 > * This could be your local computer or the computer that runs your CI/CD workflow.
 
 2. Choose which team you want to add the bootstrap package to.