From 23195dcd1b37ca6f102af1014744331cbd76bbf1 Mon Sep 17 00:00:00 2001
From: Oliver Kieselbach <oliver.kieselbach@outlook.com>
Date: Fri, 3 Apr 2026 14:50:14 +0200
Subject: [PATCH] fix agent docs: bootstrapper arrives seconds after
 enrollment, not minutes

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
---
 .../autopilot-monitor-web/app/docs/sections/SectionAgent.tsx    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/Web/autopilot-monitor-web/app/docs/sections/SectionAgent.tsx b/src/Web/autopilot-monitor-web/app/docs/sections/SectionAgent.tsx
index 3a4517f8..ed0b82c8 100644
--- a/src/Web/autopilot-monitor-web/app/docs/sections/SectionAgent.tsx
+++ b/src/Web/autopilot-monitor-web/app/docs/sections/SectionAgent.tsx
@@ -60,7 +60,7 @@ export function SectionAgent() {
           <h3 className="text-lg font-semibold text-gray-900">Full Enrollment Timeline &mdash; From the Very First Second</h3>
         </div>
         <p className="text-gray-700 mb-4">
-          Although the agent arrives on the device via the bootstrapper script &mdash; typically a few minutes after
+          Although the agent arrives on the device via the bootstrapper script &mdash; typically a few seconds after
           MDM enrollment begins &mdash; it does not miss any earlier activity. The Intune Management Extension (IME)
           has been writing detailed log files from the very start of enrollment, and the agent reads those logs
           from the beginning on its first launch. This backfill mechanism ensures complete coverage of the entire