diff --git a/docs/API_REFERENCE.md b/docs/API_REFERENCE.md
index d30ad12..807c0ac 100644
--- a/docs/API_REFERENCE.md
+++ b/docs/API_REFERENCE.md
@@ -12,7 +12,7 @@ For complete end-to-end patterns, use [Provisioning lifecycle](PROVISIONING_LIFE
 | startConfigPortal([apName, apPassword]) | Immediately starts a configuration AP and captive portal. |
 | stopConfigPortal() | Immediately stops the configuration portal. |
 | startWebPortal() / stopWebPortal() | Starts/stops the portal web server without the configuration-AP flow. |
-| process() | Services active portal, scan, station-profile, and connection state. Call from loop(). |
+| process() | Cooperatively services active portal, scan, station-profile, and connection state. Call from loop(); do not treat it as a hard real-time operation or rely on a fixed maximum duration. |
 | getConfigPortalSSID() | Returns the current configuration AP name. |
 | getConfigPortalActive() / getWebPortalActive() | Reports active configuration or web portal state. |
 | setHttpPort(port) | Chooses the portal server port before starting it. |
diff --git a/docs/PROVISIONING_LIFECYCLE.md b/docs/PROVISIONING_LIFECYCLE.md
index 5541d32..feb345d 100644
--- a/docs/PROVISIONING_LIFECYCLE.md
+++ b/docs/PROVISIONING_LIFECYCLE.md
@@ -1,6 +1,6 @@
 # Provisioning lifecycle
 
-Choose a connection flow that matches the device's operating policy, then call process() regularly for as long as WiFiManager is active. The consuming firmware owns its product-service lifecycle and restart decision.
+Choose a connection flow that matches the device's operating policy, then call process() regularly for as long as WiFiManager is active. It is a cooperative service call, not a hard real-time guarantee: target Wi-Fi or DNS work can occasionally take longer than a typical loop iteration. The consuming firmware owns its product-service lifecycle and restart decision.
 
 ## Choose a flow