Improved the Next.js manual setup

Author: matt-aitken

docs/documentation/guides/manual/nextjs.mdx

@@ -22,19 +22,15 @@ To begin, install the necessary packages in your Next.js project directory. You
 <CodeGroup>
 
 ```bash npm
-
 npm i @trigger.dev/sdk @trigger-dev/nextjs
-
 ```
 
 ```bash pnpm
 pnpm install @trigger.dev/sdk @trigger-dev/nextjs
-
 ```
 
 ```bash yarn
 yarn add @trigger.dev/sdk @trigger-dev/nextjs
-
 ```
 
 </CodeGroup>
@@ -58,67 +54,31 @@ Create a `.env.local` file at the root of your project and include your Trigger
 ```bash
 
 TRIGGER_API_KEY=ENTER_YOUR_DEVELOPMENT_API_KEY_HERE
-TRIGGER_API_URL=https://cloud.trigger.dev
+TRIGGER_API_URL=https://api.trigger.dev # this is only necessary if you are self-hosting
 
 ```
 
 Replace `ENTER_YOUR_DEVELOPMENT_API_KEY_HERE` with the actual API key obtained from the previous step.
 
 ## Configuring the Trigger Client
 
-To set up the Trigger Client for your project, follow these steps:
-
-1. **Create Configuration File:**
-
-   In your project directory, create a configuration file named `trigger.ts` or `trigger.js`, depending on whether your project uses TypeScript (`.ts`) or JavaScript (`.js`).
-
-2. **Choose Directory:**
-
-   Depending on your project structure, choose the appropriate directory for the configuration file. If your project uses a `src` directory, create the file within it. Otherwise, create it directly in the project root.
-
-3. **Add Configuration Code:**
+Create a file at `<root>/src/trigger.ts` or `<root>/trigger.ts` depending on whether you're using the `src` directory or not. `<root>` represents the root directory of your project.
 
-   Open the configuration file you created and add the following code:
+Next, add the following code to the file which creates and exports a new `TriggerClient`:
 
-   ```typescript
-   // trigger.ts (for TypeScript) or trigger.js (for JavaScript)
+```typescript src/trigger.(ts/js)
+// trigger.ts (for TypeScript) or trigger.js (for JavaScript)
 
-   import { TriggerClient } from "@trigger.dev/sdk";
+import { TriggerClient } from "@trigger.dev/sdk";
 
-   export const client = new TriggerClient({
-     id: "my-app",
-     apiKey: process.env.TRIGGER_API_KEY,
-     apiUrl: process.env.TRIGGER_API_URL,
-   });
-   ```
-
-   Replace **"my-app"** with an appropriate identifier for your project. The **apiKey** and **apiUrl** are obtained from the environment variables you set earlier.
-
-4. **File Location:**
-
-   Depending on your project structure, save the configuration file in the appropriate location:
-
-   - If your project uses a **src** directory, save the file within the **src** directory.
-   - If your project does not use a **src** directory, save the file in the project root.
-
-   **Example Directory Structure with src:**
-
-   ```
-       project-root/
-       ├── src/
-           ├── trigger.ts
-       ├── other files...
-   ```
-
-   **Example Directory Structure without src:**
-
-   ```
-       project-root/
-       ├── trigger.ts
-       ├── other files...
-   ```
+export const client = new TriggerClient({
+  id: "my-app",
+  apiKey: process.env.TRIGGER_API_KEY,
+  apiUrl: process.env.TRIGGER_API_URL,
+});
+```
 
-By following these steps, you'll configure the Trigger Client to work with your project, regardless of whether you have a separate **src** directory and whether you're using TypeScript or JavaScript files.
+Replace **"my-app"** with an appropriate identifier for your project.
 
 ## Creating the API Route
 
@@ -238,18 +198,31 @@ Your `package.json` file might look something like this:
 
 Replace **"my-app"** with the appropriate identifier you used during the step for creating the Trigger Client.
 
-## Next Steps
+## Running
 
-Start your Next.js project locally, and then execute the `dev` CLI command to run Trigger.dev locally. You should run this command every time you want to use Trigger.dev locally.
+### Run your Next.js app
 
-![Your first Job](/images/cli-dev.gif)
+Run your Next.js app locally, like you normally would. For example:
 
-<Warning>
-  Make sure your Next.js site is running locally before continuing. You must also leave this `dev`
-  terminal command running while you develop.
-</Warning>
+<CodeGroup>
 
-In a **new terminal window or tab** run:
+```bash npm
+npm run dev
+```
+
+```bash pnpm
+pnpm run dev
+```
+
+```bash yarn
+yarn run dev
+```
+
+</CodeGroup>
+
+### Run the CLI 'dev' command
+
+In a **_separate terminal window or tab_** run:
 
 <CodeGroup>
 
@@ -271,9 +244,10 @@ yarn dlx @trigger.dev/cli@latest dev
   You can optionally pass the port if you're not running on 3000 by adding
   `--port 3001` to the end
 </Note>
+
 <Note>
   You can optionally pass the hostname if you're not running on localhost by adding
-  `--hostname <host>`. Example, in case your Next.js is running on 0.0.0.0: `--hostname 0.0.0.0`.
+  `--hostname <host>`. Example, in case your Remix is running on 0.0.0.0: `--hostname 0.0.0.0`.
 </Note>
 
 <Tip>