diff --git a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage.mdx b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage.mdx
index 99dd1f7502d660f..bf9c39ab4d24040 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/challenge-pages/challenge-passage.mdx
@@ -5,7 +5,6 @@ sidebar:
   order: 3
 ---
 
-
 When a visitor solves a [Cloudflare Challenge](/cloudflare-challenges/) - as part of a [WAF custom rule](/waf/custom-rules/) or [IP Access rule](/waf/tools/ip-access-rules/) - you can set the **Challenge Passage** to prevent them from having to solve future Challenges for a specified period of time.
 
 ### How it works
@@ -25,7 +24,7 @@ To update the Challenge Passage (and the value of the `cf_clearance` cookie):
 1. Log into the [Cloudflare dashboard](https://dash.cloudflare.com).
 2. Select your account and domain.
 3. Go to **Security** > **Settings**.
-4. For **Challenge Passage**, select a duration.
+4. For **Challenge Passage**, set a duration.
 
 ### Limitations
 
diff --git a/src/content/docs/cloudflare-challenges/challenge-types/javascript-detections.mdx b/src/content/docs/cloudflare-challenges/challenge-types/javascript-detections.mdx
index c6aeea9e0174697..1800f2740d8721f 100644
--- a/src/content/docs/cloudflare-challenges/challenge-types/javascript-detections.mdx
+++ b/src/content/docs/cloudflare-challenges/challenge-types/javascript-detections.mdx
@@ -7,7 +7,7 @@ sidebar:
   order: 3
 ---
 
-import { Render } from "~/components"
+import { Render, Tabs, TabItem } from "~/components"
 
 <Render file="javascript-detections-definition" />
 
diff --git a/src/content/partials/cloudflare-challenges/javascript-detections-enable.mdx b/src/content/partials/cloudflare-challenges/javascript-detections-enable.mdx
index a4afdfd57650e05..94888b780244066 100644
--- a/src/content/partials/cloudflare-challenges/javascript-detections-enable.mdx
+++ b/src/content/partials/cloudflare-challenges/javascript-detections-enable.mdx
@@ -3,9 +3,23 @@
 
 ---
 
-To enable JavaScript Detections:
+import { Tabs, TabItem, Steps } from '~/components';
 
-1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/) and select your account and domain.
+<Tabs syncKey="dashNewNav"> <TabItem label="Old dashboard">
+
+To enable JavaScript detections:
+
+<Steps>
+1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
 2. Go to **Security** > **Bots**.
 3. Select **Configure Bot Management**.
 4. For **JavaScript Detections**, switch the toggle to **On**.
+</Steps>
+</TabItem> <TabItem label="New dashboard" icon="rocket">
+To enable JavaScript detections using the Bot traffic settings module:
+<Steps>
+1. Log in to your [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
+2. Go to **Security** > **Settings**.
+3. Under your bot traffic plan configurations, select the edit icon for **JS detections** and switch the **JavaScript Detections** toggle to **On**.
+</Steps>
+</TabItem> </Tabs>
\ No newline at end of file