Minor fixes for the docs

Author: matt-aitken

docs/documentation/introduction.mdx

@@ -8,10 +8,7 @@ Trigger.dev is an open source framework for creating long-running Jobs directly
 
 You can use [Trigger.dev Cloud](https://cloud.trigger.dev) or [Self-host Trigger.dev](/documentation/guides/self-hosting) on your own infrastructure.
 
-<Note>
-  Trigger.dev v2 currently only supports serverless. We will be adding [support for long-running
-  servers](https://github.com/triggerdotdev/trigger.dev/issues/244) soon.
-</Note>
+<Note>Trigger.dev v2 currently only supports serverless.</Note>
 
 <CardGroup>
   <Card title="Quick start guides" icon="person-running-fast" href="quickstarts/introduction">

docs/v3/cli-deploy.mdx

@@ -8,15 +8,15 @@ You run the command like this:
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@latest deploy
+npx trigger.dev@v3 deploy
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@latest deploy
+pnpm dlx trigger.dev@v3 deploy
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@latest deploy
+yarn dlx trigger.dev@v3 deploy
 ```
 
 </CodeGroup>
@@ -49,7 +49,7 @@ The log level to use (debug, info, log, warn, error, none). Defaults to `log`.
 
 ### Set config filename `--config` or `-c`
 
-The name of the config file, found where the command is run from. Defaults to `trigger.config.mjs`.
+The name of the config file, found where the command is run from. Defaults to `trigger.config.ts`.
 
 ### Set the projectRef `--project-ref` or `-p`
 

docs/v3/cli-dev.mdx

@@ -8,15 +8,15 @@ This runs a server on your machine that can execute Trigger.dev tasks:
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@latest dev
+npx trigger.dev@v3 dev
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@latest dev
+pnpm dlx trigger.dev@v3 dev
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@latest dev
+yarn dlx trigger.dev@v3 dev
 ```
 
 </CodeGroup>
@@ -34,15 +34,15 @@ You can use the `--debugger` flag to run the server in debug mode. This will all
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@latest dev --debugger
+npx trigger.dev@v3 dev --debugger
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@latest dev --debugger
+pnpm dlx trigger.dev@v3 dev --debugger
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@latest dev --debugger
+yarn dlx trigger.dev@v3 dev --debugger
 ```
 
 </CodeGroup>

docs/v3/github-actions.mdx

@@ -31,7 +31,7 @@ jobs:
         env:
           TRIGGER_ACCESS_TOKEN: ${{ secrets.TRIGGER_ACCESS_TOKEN }}
         run: |
-          npx trigger.dev@latest deploy
+          npx trigger.dev@v3 deploy
 ```
 
 If you already have a GitHub action file, you can just add the final step "🚀 Deploy Trigger.dev" to your existing file.

docs/v3/introduction.mdx

@@ -12,7 +12,7 @@ description: "Welcome to the Trigger.dev v3 documentation."
 
 Trigger.dev v3 makes it easy to write reliable long-running tasks without timeouts.
 
-- We run your tasks with no timeouts. You don't have to manage any infrastructure (unless you [self-host](/v3/self-hosting)). Workers are automatically scaled and managed for you.
+- We run your tasks with no timeouts. You don't have to manage any infrastructure (unless you [self-host](/v3/open-source-self-hosting)). Workers are automatically scaled and managed for you.
 - We provide a multi-tenant queue that is used when triggering tasks.
 - We provide an SDK and CLI for writing tasks in your existing codebase, inside [/trigger folders](/v3/trigger-folder).
 - We provide different types of tasks: [regular](/v3/tasks-regular), [scheduled](/v3/tasks-scheduled), [zod](/v3/tasks-zod), [webhooks](/v3/tasks-webhooks).

docs/v3/quick-start.mdx

@@ -5,7 +5,7 @@ description: "How to get started in 3 minutes using the CLI and SDK."
 
 In this guide we will:
 
-1. Create a `trigger.config.mjs` file and a `/trigger` directory with an example task.
+1. Create a `trigger.config.ts` file and a `/trigger` directory with an example task.
 2. Get you to run the task using the CLI.
 3. Show you how to view the run logs for that task.
 
@@ -43,23 +43,23 @@ Run this command in the root of your project to get started:
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@latest init
+npx trigger.dev@v3 init
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@latest init
+pnpm dlx trigger.dev@v3 init
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@latest init
+yarn dlx trigger.dev@v3 init
 ```
 
 </CodeGroup>
 
 It will do a few things:
 
 1. Log you into the CLI if you're not already logged in.
-2. Create a `trigger.config.mjs` file in the root of your project.
+2. Create a `trigger.config.ts` file in the root of your project.
 3. Ask where you'd like to create the `/trigger` directory.
 4. Create the `/trigger` directory with an example task, `/trigger/example.[ts/js]`.
 
@@ -72,15 +72,15 @@ The CLI `dev` command runs a server for your tasks. It will watches for changes
 <CodeGroup>
 
 ```bash npm
-npx trigger.dev@latest dev
+npx trigger.dev@v3 dev
 ```
 
 ```bash pnpm
-pnpm dlx trigger.dev@latest dev
+pnpm dlx trigger.dev@v3 dev
 ```
 
 ```bash yarn
-yarn dlx trigger.dev@latest dev
+yarn dlx trigger.dev@v3 dev
 ```
 
 </CodeGroup>