diff --git a/src/content/docs/bots/additional-configurations/detection-ids/account-takeover-detections.mdx b/src/content/docs/bots/additional-configurations/detection-ids/account-takeover-detections.mdx
index 79e0bd1d7e7017b..17f4126f6315917 100644
--- a/src/content/docs/bots/additional-configurations/detection-ids/account-takeover-detections.mdx
+++ b/src/content/docs/bots/additional-configurations/detection-ids/account-takeover-detections.mdx
@@ -18,9 +18,7 @@ Using the detection IDs below, you can detect and mitigate account takeover atta
 :::caution[Login endpoints]
 Not all login endpoints are automatically detected. 
 
-By default, endpoints [labeled](/api-shield/management-and-monitoring/endpoint-labels/#categories) as `cf-log-in` will be evaluated for account takeover detection IDs.
-
-However, if you have a non-traditional login endpoint, you should label your login endpoint with `cf-log-in` using the [endpoint labeling service](/api-shield/management-and-monitoring/endpoint-labels/#create-a-label).
+Cloudflare evaluates and automatically detects your website or application's login endpoint, but non-traditional login endpoints may not be recognized. If you have a non-traditional login endpoint, you should label it with `cf-log-in` using the [endpoint labeling service](/api-shield/management-and-monitoring/endpoint-labels/). Once you have applied the `cf-log-in` label, Cloudflare will use the labeled endpoint for account takeover detection decisions.
 :::
 
 ## Challenges for account takeover detections