fixup! Document the new .env support for local development

Author: petebacondarwin

src/content/docs/workers/wrangler/environments.mdx

@@ -112,12 +112,16 @@ env.staging.service ={ binding = "<BINDING_NAME>", service = "worker-a-staging"
 
 </WranglerConfig>
 
-### Secrets
+### Secrets for production
 
 You may assign environment-specific [secrets](/workers/configuration/secrets/) by running the command [`wrangler secret put <KEY> -env`](/workers/wrangler/commands/#put). You can also create `dotenv` type files named `.dev.vars.<environment-name>`.
 
 Like other environment variables, secrets are [non-inheritable](/workers/wrangler/configuration/#non-inheritable-keys) and must be defined per environment.
 
+### Secrets in local development
+
+<Render file="secrets-in-dev" />
+
 ---
 
 ## Examples

src/content/partials/workers/secrets-in-dev.mdx

@@ -2,16 +2,14 @@
 {}
 ---
 
-Put secrets for use in local development in either a `.dev.vars` file or a `.env` file, in the root of your project.
-
-:::note
-Do not add secrets as `vars` in your Worker's Wrangler configuration file.
+:::caution
+Do not use `vars` to store sensitive information in your Worker's Wrangler configuration file. Use secrets instead.
 :::
 
-Choose to use either `.dev.vars` or `.env` but not both. If you define a `.dev.vars` file, then values in `.env` files will be ignored for local development.
+Put secrets for use in local development in either a `.dev.vars` file or a `.env` file, in the root of your project.
 
-:::note
-The `.dev.vars` and `.env` files should not committed to git. Add `.dev.vars*` and `.env*` to your project's `.gitignore` file.
+:::info
+Choose to use either `.dev.vars` or `.env` but not both. If you define a `.dev.vars` file, then values in `.env` files will not be included in the `env` object during local development.
 :::
 
 These files should be formatted using the [dotenv](https://hexdocs.pm/dotenvy/dotenv-file-format.html) syntax. For example:
@@ -21,6 +19,10 @@ SECRET_KEY="value"
 API_TOKEN="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9"
 ```
 
+:::caution [Do not commit secrets to git]
+The `.dev.vars` and `.env` files should not committed to git. Add `.dev.vars*` and `.env*` to your project's `.gitignore` file.
+:::
+
 To set different secrets for each Cloudflare environment, create files named `.dev.vars.<environment-name>` or `.env.<environment-name>`.
 
 When you select a Cloudflare environment in your local development, the corresponding environment-specific file will be loaded ahead of the generic `.dev.vars` (or `.env`) file.
@@ -34,6 +36,8 @@ When you select a Cloudflare environment in your local development, the correspo
 
 :::note
 To disable loading local dev vars from `.env` files without providing a `.dev.vars` file, set the `CLOUDFLARE_LOAD_DEV_VARS_FROM_DOT_ENV` environment variable to `"false"`.
+:::
 
+:::note
 To include every environment variable defined in your system's process environment as a local development variable, ensure there is no `.dev.vars` and then set the `CLOUDFLARE_INCLUDE_PROCESS_ENV` environment variable to `"true"`.
 :::