minor fixes for process.env

Author: vicb

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

@@ -1,6 +1,6 @@
 ---
 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
+description: With Node.js compatibility on, process.env is automatically populated with environment variables and secrets
 products:
   - workers
 date: 2025-03-11T15:00:00Z
@@ -10,7 +10,7 @@ import { WranglerConfig } from "~/components";
 
 You can now access [environment variables](/workers/configuration/environment-variables/) and
 [secrets](/workers/configuration/secrets/) on [`process.env`](/workers/runtime-apis/nodejs/process/#processenv)
-when using the [`nodejs_compat` compatability flag](/workers/configuration/compatibility-flags/#nodejs-compatibility-flag).
+when using the [`nodejs_compat` compatibility flag](/workers/configuration/compatibility-flags/#nodejs-compatibility-flag).
 
 ```js
 const apiClient = ApiClient.new({ apiKey: process.env.API_KEY });

src/content/compatibility-flags/nodejs-compat-populate-process-env.md

@@ -1,6 +1,6 @@
 ---
 name: "Enable auto-populating `process.env`"
-sort_date: "2025-02-27"
+sort_date: "2025-04-01"
 enable_date: "2025-04-01"
 enable_flag: "nodejs_compat_populate_process_env"
 disable_flag: "nodejs_compat_do_not_populate_process_env"
@@ -18,7 +18,7 @@ const LOG_LEVEL = process.env.LOG_LEVEL || "info";
 ```
 
 This makes accessing these values easier and conforms to common Node.js patterns, which can
-reduce toil and help with compatability for existing Node.js libraries.
+reduce toil and help with compatibility for existing Node.js libraries.
 
 If users do not wish for these values to be accessible via `process.env`, they can use the
 `nodejs_compat_do_not_populate_process_env` flag. In this case, `process.env` will still be

src/content/docs/r2/data-catalog/config-examples/spark-scala.mdx

@@ -126,7 +126,7 @@ sbt clean assembly
 
 After building, the output JAR should be located at `target/scala-2.12/R2DataCatalogDemo-assembly-1.0.jar`.
 
-To run the application, you will use `spark-submit`. Below is an example shell script (`submit.sh`) that includes the necessary Java compatability flags for Spark on Java 17:
+To run the application, you will use `spark-submit`. Below is an example shell script (`submit.sh`) that includes the necessary Java compatibility flags for Spark on Java 17:
 
 ```
 # We need to set these "--add-opens" so that Spark can run on Java 17 (it needs access to

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/#enable-auto-populating-processenv) compatability flag is set, `process.env` will contain any [environment variables](/workers/configuration/environment-variables/),
+When [Node.js compatibility](/workers/runtime-apis/nodejs/) is turned on and the [`nodejs_compat_populate_process_env`](/workers/configuration/compatibility-flags/#enable-auto-populating-processenv) compatibility 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