some fixes

Author: patriciasantaana

src/content/docs/bots/additional-configurations/detection-ids/account-takeover-detections.mdx

@@ -7,7 +7,6 @@ sidebar:
 
 import { Render, Tabs, TabItem, Steps } from "~/components"
 
-
 Using the detection IDs below, you can detect and mitigate account takeover attacks. You can monitor the number of login requests for a given software and network combination, as well as the percentage of login errors. When it reaches a suspicious level, you can prevent these attacks by using [custom rules](/waf/custom-rules/), [rate limiting rules](/waf/rate-limiting-rules/), and [Workers](/workers/).
 
 | Detection ID | Description                              |
@@ -56,7 +55,7 @@ To use rate limiting rules with account takeover detections:
 
 <Tabs syncKey="dashNewNav"> 
 	<TabItem label="Old dashboard">
-		<Steps>
+	  <Steps>
       1. Log in to the [Cloudflare dashboard](https://dash.cloudflare.com/), and select your account and domain.
       2. Go to **Security** > **WAF**.
       3. Under **Rate limiting rules**, select **Create rule**.
@@ -75,7 +74,6 @@ To use rate limiting rules with account takeover detections:
   </TabItem> 
 </Tabs>
 
-:::note
-The rule can be enhanced with Leaked Credential Checks. Refer to the [WAF documentation](/waf/detections/leaked-credentials/) for more information on how to include leaked credentials and account takeover detections in a rate limiting rule. 
-
+:::tip[Enhance with leaked credential detections]
+Refer to the [WAF documentation](/waf/detections/leaked-credentials/) for more information on how to include leaked credentials and account takeover detections to enhance a rate limiting rule. 
 :::

src/content/docs/bots/additional-configurations/detection-ids/scraping-detections.mdx

@@ -4,3 +4,5 @@ title: Scraping detections
 sidebar:
   order: 3
 ---
+
+import { Render, Tabs, TabItem, Steps } from "~/components"