sync: Update Vite docs from upstream 20250520

Author: github-actions[bot]

docs/config/shared-options.md

@@ -466,7 +466,7 @@ See [here](/guide/env-and-mode#env-files) for more about environment files.
 - **Type:** `string | string[]`
 - **Default:** `VITE_`
 
-Env variables starting with `envPrefix` will be exposed to your client source code via import.meta.env.
+Env variables starting with `envPrefix` will be exposed to your client source code via `import.meta.env`.
 
 :::warning SECURITY NOTES
 `envPrefix` should not be set as `''`, which will expose all your env variables and cause unexpected leaking of sensitive information. Vite will throw an error when detecting `''`.

docs/guide/api-environment-frameworks.md

@@ -329,7 +329,7 @@ export default {
 }
 ```
 
-Plugins can also define a `buildApp` hook. Order `'pre'` and `null'` are executed before the configured `builder.buildApp`, and order `'post'` hooks are executed after it. `environment.isBuilt` can be used to check if an environment has already being build.
+Plugins can also define a `buildApp` hook. Order `'pre'` and `null` are executed before the configured `builder.buildApp`, and order `'post'` hooks are executed after it. `environment.isBuilt` can be used to check if an environment has already being build.
 
 ## Environment Agnostic Code
 

docs/guide/performance.md

@@ -115,7 +115,7 @@ Keeping Vite fast with a growing codebase is about reducing the amount of work f
 Examples of doing less work:
 
 - Use CSS instead of Sass/Less/Stylus when possible (nesting can be handled by PostCSS)
-- Don't transform SVGs into UI framework components (React, Vue, etc). Import them as strings or URLs instead.
+- Don't transform SVGs into UI framework components (React, Vue, etc.). Import them as strings or URLs instead.
 - When using `@vitejs/plugin-react`, avoid configuring the Babel options, so it skips the transformation during build (only esbuild will be used).
 
 Examples of using native tooling: