more fixups..

Author: emily-shen

src/content/docs/workers/configuration/environment-variables.mdx

@@ -52,14 +52,14 @@ export default {
 [Environments in Wrangler](/workers/wrangler/environments) let you specify different configurations for the same Worker, including different values for `vars` in each environment.
 As `vars` is a [non-inheritable key](/workers/wrangler/configuration/#non-inheritable-keys), they are not inherited by environments and must be specified for each environment.
 
-The example below sets up two environments, `staging` and `production`, with different values for `API_HOST`. 
+The example below sets up two environments, `staging` and `production`, with different values for `API_HOST`.
 
 <WranglerConfig>
 
 ```toml
 name = "my-worker-dev"
 
-#top level environment
+# top level environment
 [vars]
 API_HOST = "api.example.com"
 
@@ -72,7 +72,7 @@ API_HOST = "production.example.com"
 
 </WranglerConfig>
 
-To run Wrangler commands in specific environments, you can pass in the `--env` or `-e` flag. For example, you can develop the Worker in an environment called `staging` by running `npx wrangler dev --env=staging`, and deploy it with `npx wrangler deploy --env=staging`.
+To run Wrangler commands in specific environments, you can pass in the `--env` or `-e` flag. For example, you can develop the Worker in an environment called `staging` by running `npx wrangler dev --env staging`, and deploy it with `npx wrangler deploy --env staging`.
 
 Learn about [environments in Wrangler](/workers/wrangler/environments).
 

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

@@ -1,6 +1,5 @@
 ---
 {}
-
 ---
 
 When developing your Worker or Pages Function, create a `.dev.vars` file in the root of your project to define secrets that will be used when running `wrangler dev` or `wrangler pages dev`, as opposed to using environment variables in the [Wrangler configuration file](/workers/configuration/environment-variables/#compare-secrets-and-environment-variables). This works both in local and remote development modes.
@@ -12,6 +11,6 @@ SECRET_KEY="value"
 API_TOKEN="eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9"
 ```
 
-To set different secrets for each environment, create files named `.dev.vars.<environment-name>`. When you use `wrangler <command> --env <environment-name>`, the corresponding environment-specific file will be loaded instead of the `.dev.vars` file, so the two files are not merged.
+To set different secrets for each environment, create files named `.dev.vars.<environment-name>`. When you use `wrangler <command> --env <environment-name>`, the corresponding environment-specific file will be loaded instead of the `.dev.vars` file.
 
 Like other environment variables, secrets are [non-inheritable](/workers/wrangler/configuration/#non-inheritable-keys) and must be defined per environment.