Apply suggestions from code review

Co-authored-by: Victor Berchet <[email protected]>

Author: jasnell

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

@@ -135,6 +135,7 @@ JSON-encoded string and you *want* to be able to parse it as JSON within your
 application (e.g. `JSON.parse(process.env.BAR)`) then the value will need to
 be "double encoded", for instance `'"\\"abc\\""'`.
 
+:::note
 Note also that because secrets are a form of environment variable within the runtime,
 secrets are also exposed via `process.env`.
 

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

@@ -33,9 +33,10 @@ In the Node.js implementation of `process.env`, the `env` object is a copy of th
 Workers have a concept of [environment variables](/workers/configuration/environment-variables/) that are applied on a per-Worker and per-request basis.
 
 By default, these are not accessible automatically via the `process.env` API. It is
-possible to have environment variables automatically populated into `process.env` using
+possible to have environment variables and secrets automatically populated into `process.env` using
 the `nodejs_compat_populate_process_env` compatibility flag. It is also possible to
-manually copy these values into `process.env` if necessary.
+manually copy these values into `process.env` if necessary -- but only within the context of
+a request.
 
 Setting any value on `process.env` will coerce that value into a string.
 
@@ -55,7 +56,22 @@ export default {
 };
 ```
 
-Refer to the [environment variables](/workers/configuration/environment-variables/)
+It is strongly recommended that you *do not* replace the entire `process.env` object with
+the request `env` object. Doing so will cause you to lose any environment variables that
+were set previously and will cause unexpected behavior for other Workers running in the
+same isolate. Specifically, it would cause inconsistency with the `process.env` object when
+accessed via named imports.
+
+```js
+import * as process from 'node:process';
+import { env } from 'node:process';
+
+process.env === env; // true! they are the same object
+process.env = {}; // replace the object! Do not do this!
+process.env === env; // false! they are no longer the same object
+
+// From this point forward, any changes to process.env will not be reflected in env,
+// and vice versa!
 documentation for more detail.
 
 ## `process.nextTick()`