fix env file option

Author: nicktrn

docs/snippets/cli-commands-deploy.mdx

@@ -1,5 +1,6 @@
 import CommonOptions from '/snippets/cli-options-common.mdx';
 import ProjectRefOption from '/snippets/cli-options-project-ref.mdx';
+import EnvFileOption from '/snippets/cli-options-env-file.mdx';
 
 Run the command like this:
 
@@ -39,10 +40,7 @@ You can also setup [GitHub Actions](/github-actions) to deploy your tasks automa
   Defaults to `prod` but you can specify `staging`.
 </ParamField>
 
-<ParamField body="Env file" type="--env">
-  Load environment variables from a file. This will only hydrate the `process.env` of the CLI
-  process, not the tasks.
-</ParamField>
+<EnvFileOption />
 
 <ParamField body="Dry run" type="--dry-run">
   Create a deployable build but don't deploy it. Prints out the build path so you can inspect it.

docs/snippets/cli-commands-develop.mdx

@@ -1,5 +1,6 @@
 import CommonOptions from '/snippets/cli-options-common.mdx';
 import ProjectRefOption from '/snippets/cli-options-project-ref.mdx';
+import EnvFileOption from '/snippets/cli-options-env-file.mdx';
 
 This runs a server on your machine that can execute Trigger.dev tasks:
 
@@ -33,10 +34,7 @@ It is worth noting that each task runs in a separate Node process. This means th
 
 <ProjectRefOption />
 
-<ParamField body="Env file" type="--env">
-  Pass a custom path to an env file. We automatically detect `.env`, `.env.local`,
-  `.env.development`, and `.env.development.local` files.
-</ParamField>
+<EnvFileOption />
 
 <ParamField body="Skip update check" type="--skip-update-check">
   Skip checking for `@trigger.dev` package updates.

docs/snippets/cli-options-env-file.mdx

@@ -0,0 +1,4 @@
+<ParamField body="Env file" type="--env-file">
+  Load environment variables from a file. This will only hydrate the `process.env` of the CLI
+  process, not the tasks.
+</ParamField>