diff --git a/docs/Using Fleet/Automations.md b/docs/Using Fleet/Automations.md
index bbc485e8e1..e79747a40e 100644
--- a/docs/Using Fleet/Automations.md	
+++ b/docs/Using Fleet/Automations.md	
@@ -70,8 +70,6 @@ Follow the steps below to configure Jira or Zendesk as a ticket destination:
 6. Select **Enable vulnerability automations** and choose **Ticket**.
 7. Under **Ticket destination**, select your ticket destination and select **Save**.
 
-The Jira and Zendesk ticket automations are currently in beta.
-
 ## Policy automations
 
 Policy automations are triggered if a policy is newly failing on at least one host. Policy automations are triggered separately for each failing policy.
@@ -130,8 +128,6 @@ Follow the steps below to configure Jira or Zendesk as a ticket destination:
 6. Select **Enable policy automations**, check the policies you'd like to listen to, and choose **Ticket**.
 7. Under **Ticket destination**, select your ticket destination and select **Save**.
 
-The Jira and Zendesk ticket destinations are currently in beta.
-
 ## Host status automations
 
 Host status automations send a webhook request if a configured percentage of hosts have not checked in to Fleet for a configured number of days.