docs: clarify cloudflare env usage (#10096)

Co-authored-by: Willow (GHOST) <[email protected]>
Co-authored-by: Ben McCann <[email protected]>

Author: 3 people

documentation/docs/25-build-and-deploy/60-adapter-cloudflare.md

@@ -63,9 +63,9 @@ When configuring your project settings, you must use the following settings:
 
 > You need to add a `NODE_VERSION` environment variable to both the "production" and "preview" environments. You can add this during project setup or later in the Pages project settings. SvelteKit requires Node `16.14` or later, so you should use `16` as the `NODE_VERSION` value.
 
-## Environment variables
+## Bindings
 
-The [`env`](https://developers.cloudflare.com/workers/runtime-apis/fetch-event#parameters) object, containing KV/DO namespaces etc, is passed to SvelteKit via the `platform` property along with `context` and `caches`, meaning you can access it in hooks and endpoints:
+The [`env`](https://developers.cloudflare.com/workers/runtime-apis/fetch-event#parameters) object contains your project's [bindings](https://developers.cloudflare.com/workers/platform/environment-variables/), which consist of KV/DO namespaces, etc. It is passed to SvelteKit via the `platform` property, along with `context` and `caches`, meaning that you can access it in hooks and endpoints:
 
 ```js
 // @errors: 7031
@@ -74,6 +74,8 @@ export async function POST({ request, platform }) {
 }
 ```
 
+> SvelteKit's built-in `$env` module should be preferred for environment variables.
+
 To make these types available to your app, reference them in your `src/app.d.ts`:
 
 ```diff
@@ -92,7 +94,7 @@ declare global {
 export {};
 ```
 
-> `platform.env` is only available in the production build. Use [wrangler](https://developers.cloudflare.com/workers/cli-wrangler) to test it locally
+> `platform.env` is only available in the production build. Use [wrangler](https://developers.cloudflare.com/workers/cli-wrangler) to test it locally.
 
 ## Notes