fix detection id availability

Author: patriciasantaana

src/content/docs/bots/concepts/detection-ids.mdx

@@ -118,3 +118,7 @@ To use rate limiting rules with account takeover detections:
 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. 
 
 :::
+
+## Availability
+
+Detections IDs are available for Enterprise Bot Management customers. 

src/content/partials/bots/about-plan-bm-subscription.mdx

@@ -41,7 +41,7 @@
     </tr>
     <tr>
       <td><b>Additional control</b></td>
-      <td>Ability to restrict by path, IP address, and more. Access to <a href="/bots/concepts/bot-score/">bot score</a>, <a href="/bots/concepts/ja3-ja4-fingerprint/">JA3/JA4 fingerprint</a>, and <a href="/bots/concepts/cloudflare-bot-tags/">bot tags</a> fields.</td>
+      <td>Ability to restrict by path, IP address, and more. Access to <a href="/bots/concepts/bot-score/">bot score</a>, <a href="/bots/concepts/ja3-ja4-fingerprint/">JA3/JA4 fingerprint</a>, <a href="/bots/concepts/cloudflare-bot-tags/">bot tags</a> fields, and <a href="/bots/concepts/detection-ids/">detection IDs</a>.</td>
     </tr>
   </tbody>
 </table>