Repository: withastro/astro
File: packages/astro/src/types/public/config.ts (TypeScript)

Code before:
		preserveScriptOrder?: boolean;

		/**
		 * @name experimental.liveContentCollections
		 * @type {boolean}
		 * @default `false`
		 * @version 5.10
		 * @description
		 * Enables the use of live content collections.
		 *
		 */
		liveContentCollections?: boolean;

		/**
		 * @name experimental.staticImportMetaEnv
		 * @type {boolean}
		 * @default `false`
		 * @version 5.13
		 * @description
		 *
		 * Disables replacement of `import.meta.env` values with `process.env` calls and their coercion
		 *
		 * By default, Astro turns non public `import.meta.env` values into `process.env` calls during the build, if the environment
		 * variable name is present in `process.env`. It also converts your environment variables used through `import.meta.env` in
		 * some cases, and this can prevent access to some values such as the strings `"true"` (which is converted to a boolean value),
		 * and `"1"` (which is converted to a number).
		 *
		 * This flag aligns `import.meta.env`'s behavior in Astro with [Vite](https://vite.dev/guide/env-and-mode.html#env-variables).
		 *
		 * See the [experimental static `import.meta.env` docs](https://docs.astro.build/en/reference/experimental-flags/static-import-meta-env/) for more information.
		 */
		staticImportMetaEnv?: boolean;
	};
}

/**
 * Resolved Astro Config
 *
 * Config with user settings along with all defaults filled in.
 */
export interface AstroConfig extends AstroConfigType {
	// Public:
	// This is a more detailed type than zod validation gives us.
	// TypeScript still confirms zod validation matches this type.
	integrations: AstroIntegration[];
}
/**
 * An inline Astro config that takes highest priority when merging with the user config,
 * and includes inline-specific options to configure how Astro runs.
 */
export interface AstroInlineConfig extends AstroUserConfig, AstroInlineOnlyConfig {}

Review comment (refactor):
```suggestion
		 * Currently, non-public `import.meta.env` environment variables are replaced by a reference to `process.env`. Additionally, Astro may also convert the value type of your environment variables used through `import.meta.env`, which can prevent access to some values such as the strings `"true"` (which is converted to a boolean value), and `"1"` (which is converted to a number).
		 *
		 * The `experimental.staticImportMetaEnv` flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any `import.meta.env` environment variables with a `process.env` call, nor will it coerce values.
```
@florian-lefebvre This aligns more closely with the wording in docs now, and you are welcome adjust as you see fit and to split this up into however many lines you prefer! 

Code after:
		preserveScriptOrder?: boolean;

		/**
		 * @name experimental.liveContentCollections
		 * @type {boolean}
		 * @default `false`
		 * @version 5.10
		 * @description
		 * Enables the use of live content collections.
		 *
		 */
		liveContentCollections?: boolean;

		/**
		 * @name experimental.staticImportMetaEnv
		 * @type {boolean}
		 * @default `false`
		 * @version 5.13
		 * @description
		 *
		 * Disables replacement of `import.meta.env` values with `process.env` calls and their coercion
		 *
		 * Currently, non-public `import.meta.env` environment variables are replaced by a reference to `process.env`. Additionally, Astro may also convert the value type of your environment variables used through `import.meta.env`, which can prevent access to some values such as the strings `"true"` (which is converted to a boolean value), and `"1"` (which is converted to a number).
		 *
		 * The `experimental.staticImportMetaEnv` flag simplifies Astro's default behavior, making it easier to understand and use. Astro will no longer replace any `import.meta.env` environment variables with a `process.env` call, nor will it coerce values.
		 *
		 * This flag aligns `import.meta.env`'s behavior in Astro with [Vite](https://vite.dev/guide/env-and-mode.html#env-variables).
		 *
		 * See the [experimental static `import.meta.env` docs](https://docs.astro.build/en/reference/experimental-flags/static-import-meta-env/) for more information.
		 */
		staticImportMetaEnv?: boolean;
		/**
		 * @name experimental.chromeDevtoolsWorkspace
		 * @type {boolean}
		 * @default `false`
		 * @version 5.13
		 * @description
		 *
		 * Enables Chrome DevTools workspace integration for the Astro dev server.
		 *
		 * When enabled, the dev server will automatically configure a [Chrome DevTools workspace](https://developer.chrome.com/docs/devtools/workspaces) for your project,
		 * allowing you to edit files directly in the browser and have those changes reflected in your local file system.
		 *
		 * ```js
		 * import { defineConfig } from 'astro/config';
		 *
		 * export default defineConfig({
		 *   experimental: {
		 *     chromeDevtoolsWorkspace: true,
		 *   },
		 * });