Updates link to process env docs

Author: mikenomitch

src/content/changelog/workers/2025-03-11-process-env-support.mdx

@@ -3,7 +3,7 @@ title: Access your Worker's environment variables from process.env
 description: With Node.js compatability on, process.env is automatically populated with environment variables and secrets
 products:
   - workers
-date: 2025-03-11T17:00:00Z
+date: 2025-03-11T15:00:00Z
 ---
 
 You can now access [environment variables](/workers/configuration/environment-variables/) and

src/content/docs/workers/runtime-apis/nodejs/process.mdx

@@ -28,7 +28,7 @@ nextTick(() => {
 
 In the Node.js implementation of `process.env`, the `env` object is a copy of the environment variables at the time the process was started. In the Workers implementation, there is no process-level environment, so by default `env` is an empty object. You can still set and get values from `env`, and those will be globally persistent for all Workers running in the same isolate and context (for example, the same Workers entry point).
 
-When [Node.js compatability](/workers/runtime-apis/nodejs/) is turned on and the [`nodejs_compat_populate_process_env`](/workers/configuration/compatibility-flags/#nodejs-compat-populate-process-env) compatability flag is set, `process.env` will contain any [environment variables](/workers/configuration/environment-variables/),
+When [Node.js compatability](/workers/runtime-apis/nodejs/) is turned on and the [`nodejs_compat_populate_process_env`](/workers/configuration/compatibility-flags/#enable-auto-populating-processenv) compatability flag is set, `process.env` will contain any [environment variables](/workers/configuration/environment-variables/),
 [secrets](/workers/configuration/secrets/), or [version metadata](/workers/runtime-apis/bindings/version-metadata/) metadata that has been configured on your Worker.
 
 ### Relationship to per-request `env` argument in `fetch()` handlers