fixes

Author: patriciasantaana

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

@@ -15,7 +15,7 @@ Using the detection IDs below, you can detect and mitigate account takeover atta
 | `201326593`  | Observes all login traffic to the zone.  |
 | `201326598`  | Sets a dynamic threshold based on the normal traffic that is unique to the zone.<br /><br /> When the ID matches a login failure, Bot Management sets the [bot score](/bots/concepts/bot-score/) to 29 and uses [anomaly detection](/bots/concepts/bot-detection-engines/#anomaly-detection-enterprise) as its score source. |
 
-### Challenges for account takeover detections
+## Challenges for account takeover detections
 
 Cloudflare's [Managed Challenge](/cloudflare-challenges/challenge-types/challenge-pages/#managed-challenge-recommended) can limit brute-force attacks on your login endpoints.
 
@@ -48,7 +48,7 @@ To access account takeover detections:
 (any(cf.bot_management.detection_ids[*] eq 201326593))
 ```
 
-### Limit logins with account takeover detections
+## Limit logins with account takeover detections
 
 Rate limiting rules can limit the number of logins from a particular IP, JA4 fingerprint, or country.
 

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

@@ -5,8 +5,6 @@ sidebar:
   order: 4
 ---
 
-## Additional detections
-
 | Detection ID | Description                              |
 | ------------ | ---------------------------------------- |
 | `50331651`   | Observes traffic from residential proxy networks and similar commercial proxies. <br /><br />When the ID matches a request, Bot Management sets the bot score to 29 and uses [anomaly detection](/bots/concepts/bot-detection-engines/#anomaly-detection-enterprise) as its score source. |

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

@@ -36,8 +36,8 @@ To access scraping detections:
 
                 <DashButton url="/?to=/:account/:zone/security/security-rules" />
             2. Select **Create rule** and choose **Custom rule**.
-            4. Fill out the form using **Bot Detection IDs** along with other necessary information.
-            5. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
+            3. Fill out the form using **Bot Detection IDs** along with other necessary information.
+            4. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
         </Steps>
 	</TabItem> 
 </Tabs>
@@ -73,12 +73,13 @@ To use rate limiting rules with scraping detections:
 
                 <DashButton url="/?to=/:account/:zone/security/security-rules" />
             2. Select **Create rule** and choose **Rate limiting rule**.
-            3.Fill out the form using the **Custom expression builder** and `cf.bot_management_detection_ids` along with other necessary information.
+            3. Fill out the form using the **Custom expression builder** and `cf.bot_management_detection_ids` along with other necessary information.
             4. Select **Save as draft** to return to it later, or **Deploy** to deploy the rule.
         </Steps>
     </TabItem>
 </Tabs>
 
 :::note
 Detection IDs `50331648` and `50331649` are dynamically re-calculated, meaning a single fingerprint would not be permanently rate limited unless it continues to remain suspicious at all times. Rate limiting on these detection IDs allows for more lenient controls, as opposed to immediately challenging or blocking.
+
 :::