Fix requirements statements

docs/management/admin/automated-response-actions.asciidoc

@@ -13,7 +13,7 @@ Add {elastic-defend}'s <<response-actions,response actions>> to detection rules
 --
 * Automated response actions require an https://www.elastic.co/pricing[Enterprise subscription].
 * Hosts must have {agent} installed with the {elastic-defend} integration.
-* Your user role must have the ability to create detection rules and the <<endpoint-management-req,privilege>> to perform specific response actions (for example, the **Host Isolation** privilege to isolate hosts).
+* Your user role must have the ability to create detection rules and the privilege to perform <<response-action-commands,specific response actions>> (for example, the **Host Isolation** privilege to isolate hosts).
 * You can only add automated response actions to custom query rules.
 --
 

docs/serverless/endpoint-response-actions/automated-response-actions.mdx

@@ -12,9 +12,9 @@ Add ((elastic-defend))'s <DocLink slug="/serverless/security/response-actions">r
 
 <DocCallOut title="Requirements">
 
-- Automated response actions require an [Enterprise subscription](https://www.elastic.co/pricing).
+- Automated response actions require the Endpoint Protection Complete <DocLink slug="/serverless/elasticsearch/manage-project" text="project feature"/>.
 - Hosts must have ((agent)) installed with the ((elastic-defend)) integration.
-- Your user role must have the ability to create detection rules and to perform <DocLink slug="/serverless/security/response-actions" section="response-action-commands">specific response actions</DocLink>.
+- Your user role must have the ability to create detection rules and the privilege to perform <DocLink slug="/serverless/security/response-actions" section="response-action-commands">specific response actions</DocLink> (for example, custom roles require the **Host Isolation** privilege to isolate hosts).
 - You can only add automated response actions to custom query rules.
 
 </DocCallOut>