Remove the coming soon warning

docs/documentation/concepts/http-endpoints.mdx

@@ -3,8 +3,6 @@ title: HTTP endpoints
 description: HTTP endpoints allow you to trigger your Jobs from any webhooks.
 ---
 
-<Warning>This feature is in beta and not yet available to use on the Trigger.dev Cloud.</Warning>
-
 Sometimes you want to subscribe to changes from an API, and we don't have [an Integration](/integrations/introduction) for it yet. That's when you can use `defineHttpEndpoint` to receive webhooks, verify them, and create an [HTTP Trigger](/documentation/concepts/triggers/http).
 
 ## Defining an HTTP endpoint

docs/documentation/concepts/triggers/http.mdx

@@ -4,8 +4,6 @@ sidebarTitle: "HTTP"
 description: "HTTP Triggers allow you to trigger your Jobs from any webhooks."
 ---
 
-<Warning>This feature is in beta and not yet available to use on the Trigger.dev Cloud.</Warning>
-
 Sometimes you want to subscribe to changes from an API, and we don't have [an Integration](/integrations/introduction) for it yet. That's when you can use `defineHttpEndpoint` to receive webhooks, verify them, and create an HTTP Trigger.
 
 You should read the [HTTP endpoint](/documentation/concepts/http-endpoints) documentation to understand how to create an HTTP endpoint.

docs/documentation/concepts/triggers/invoke.mdx

@@ -4,8 +4,6 @@ sidebarTitle: "Manual Invoke"
 description: "Invoke Jobs manually using the invoke Trigger"
 ---
 
-<Warning>This feature is in beta and not yet available to use on the Trigger.dev Cloud.</Warning>
-
 Sometimes it makes sense to be able to invoke a Job manually, without having to specify an event, especially for cases where you want to get notified when the invoked Job Run is complete.
 
 To specify that a job is manually invokable, you can use the `invokeTrigger()` function when defining a job:

docs/sdk/invoke-trigger.mdx

@@ -3,8 +3,6 @@ title: "invokeTrigger()"
 description: "Use `invokeTrigger()` to allow a Job to be manually triggered using `Job.invoke()`"
 ---
 
-<Warning>This feature is in beta and not yet available to use on the Trigger.dev Cloud.</Warning>
-
 Setting `invokeTrigger()` on a job allows you to manually trigger the job using `Job.invoke()`, either from your backend or from inside another job. See our [Invoke Trigger guide](/documentation/guides/invoke) for more info.
 
 ## Parameters