fix warning

Author: patriciasantaana

src/content/docs/cloudflare-challenges/challenge-types/javascript-detections.mdx

@@ -37,7 +37,7 @@ Use JavaScript Detections API for more granular control over when and where Java
 
 You can explicitly add a script reference to `jsd/api.js` and your own code calling `window.cloudflare.jsd.executeOnce` on specific HTML pages of your website.
 
-:::warning
+:::caution
 It is not recommended to combine both approaches (zone-wide toggle and the manual injection). If you want to selectively deploy JavaScript Detections only on certain pages, disable JavaScript Detections via the Cloudflare dashboard and use the JSD API exclusively.
 :::
 

src/content/partials/cloudflare-challenges/javascript-detections-process.mdx

@@ -21,7 +21,7 @@ Once the JavaScript Detection is injected on the HTML page, the visitor's browse
 The `cf-clearance` cookie cannot exceed the maximum size of 4096 bytes.
 :::
 
-:::warning
+:::caution
 Enforcement against bots do **not** occur even if the cookie is flagged false. 
 
 You must enable JavaScript Detections and then create a custom WAF rule using the `cf.bot_management.js.detection.passed` field to block or challenge a failed request.