chore: fix typos and grammatical errors across documentation and comments (#20337)

lyw405 · web-flow · commit c1c951dcc32e · 2025-07-02T11:35:46.000+02:00
diff --git a/docs/_data/team.js b/docs/_data/team.js
@@ -71,7 +71,7 @@ export const core = [
     avatar: 'https://github.com/ArnaudBarre.png',
     name: 'Arnaud Barré',
     title: 'Frontend Developer',
-    desc: 'Passionate by tooling around TypeScript and React.',
+    desc: 'Passionate about tooling around TypeScript and React.',
     links: [
       { icon: 'github', link: 'https://github.com/ArnaudBarre' },
       {
@@ -164,7 +164,7 @@ export const emeriti = [
     name: 'Niputi',
     title: 'Developer',
     org: 'Computershare Denmark',
-    desc: 'weeb/javascript lover.',
+    desc: 'weeb/JavaScript lover.',
     links: [
       { icon: 'github', link: 'https://github.com/Niputi' },
       { icon: 'x', link: 'https://x.com/Niputi_' },
diff --git a/docs/changes/index.md b/docs/changes/index.md
@@ -22,6 +22,6 @@ We don't recommend switching to these APIs yet. They are included in Vite to hel
 
 ## Past
 
-The changes below has been done or reverted. They are no longer relevant in the current major version.
+The changes below have been done or reverted. They are no longer relevant in the current major version.
 
 - _No past changes yet_
diff --git a/docs/changes/per-environment-apis.md b/docs/changes/per-environment-apis.md
@@ -6,7 +6,7 @@ Give us feedback at [Environment API feedback discussion](https://github.com/vit
 
 Multiple APIs from `ViteDevServer` related to module graph and modules transforms have been moved to the `DevEnvironment` instances.
 
-Affect scope: `Vite Plugin Authors`
+Affected scope: `Vite Plugin Authors`
 
 ::: warning Future Deprecation
 The `Environment` instance was first introduced at `v6.0`. The deprecation of `server.moduleGraph` and other methods that are now in environments is planned for a future major. We don't recommend moving away from server methods yet. To identify your usage, set these in your vite config.
diff --git a/docs/changes/shared-plugins-during-build.md b/docs/changes/shared-plugins-during-build.md
@@ -6,10 +6,10 @@ Give us feedback at [Environment API feedback discussion](https://github.com/vit
 
 See [Shared plugins during build](/guide/api-environment-plugins.md#shared-plugins-during-build).
 
-Affect scope: `Vite Plugin Authors`
+Affected scope: `Vite Plugin Authors`
 
 ::: warning Future Default Change
-`builder.sharedConfigBuild` was first introduce in `v6.0`. You can set it true to check how your plugins work with a shared config. We're looking for feedback about changing the default in a future major once the plugin ecosystem is ready.
+`builder.sharedConfigBuild` was first introduced in `v6.0`. You can set it true to check how your plugins work with a shared config. We're looking for feedback about changing the default in a future major once the plugin ecosystem is ready.
 :::
 
 ## Motivation
diff --git a/docs/changes/ssr-using-modulerunner.md b/docs/changes/ssr-using-modulerunner.md
@@ -6,10 +6,10 @@ Give us feedback at [Environment API feedback discussion](https://github.com/vit
 
 `server.ssrLoadModule` has been replaced by importing from a [Module Runner](/guide/api-environment#modulerunner).
 
-Affect scope: `Vite Plugin Authors`
+Affected scope: `Vite Plugin Authors`
 
 ::: warning Future Deprecation
-`ModuleRunner` was first introduce in `v6.0`. The deprecation of `server.ssrLoadModule` is planned for a future major. To identify your usage, set `future.removeSsrLoadModule` to `"warn"` in your vite config.
+`ModuleRunner` was first introduced in `v6.0`. The deprecation of `server.ssrLoadModule` is planned for a future major. To identify your usage, set `future.removeSsrLoadModule` to `"warn"` in your vite config.
 :::
 
 ## Motivation
diff --git a/docs/changes/this-environment-in-hooks.md b/docs/changes/this-environment-in-hooks.md
@@ -6,7 +6,7 @@ Give us feedback at [Environment API feedback discussion](https://github.com/vit
 
 Before Vite 6, only two environments were available: `client` and `ssr`. A single `options.ssr` plugin hook argument in `resolveId`, `load` and `transform` allowed plugin authors to differentiate between these two environments when processing modules in plugin hooks. In Vite 6, a Vite application can define any number of named environments as needed. We're introducing `this.environment` in the plugin context to interact with the environment of the current module in hooks.
 
-Affect scope: `Vite Plugin Authors`
+Affected scope: `Vite Plugin Authors`
 
 ::: warning Future Deprecation
 `this.environment` was introduced in `v6.0`. The deprecation of `options.ssr` is planned for a future major. At that point we'll start recommending migrating your plugins to use the new API. To identify your usage, set `future.removePluginHookSsrArgument` to `"warn"` in your vite config.
diff --git a/docs/config/ssr-options.md b/docs/config/ssr-options.md
@@ -59,4 +59,4 @@ For example, when setting `['node', 'custom']`, you should run `NODE_OPTIONS='--
 - **Type:** `string[]`
 - **Default:** `['module', 'jsnext:main', 'jsnext']`
 
-List of fields in `package.json` to try when resolving a package's entry point. Note this takes lower precedence than conditional exports resolved from the `exports` field: if an entry point is successfully resolved from `exports`, the main field will be ignored. This setting only affect non-externalized dependencies.
+List of fields in `package.json` to try when resolving a package's entry point. Note this takes lower precedence than conditional exports resolved from the `exports` field: if an entry point is successfully resolved from `exports`, the main field will be ignored. This setting only affects non-externalized dependencies.
diff --git a/docs/releases.md b/docs/releases.md
@@ -12,7 +12,7 @@ Vite does not have a fixed release cycle.
 - **Minor** releases always contain new features and are released as needed. Minor releases always have a beta pre-release phase (usually every two months).
 - **Major** releases generally align with [Node.js EOL schedule](https://endoflife.date/nodejs), and will be announced ahead of time. These releases will go through long-term discussions with the ecosystem, and have alpha and beta pre-release phases (usually every year).
 
-The Vite versions ranges that are supported by the Vite team is automatically determined by:
+The Vite version ranges that are supported by the Vite team are automatically determined by:
 
 - **Current Minor** gets regular fixes.
 - **Previous Major** (only for its latest minor) and **Previous Minor** receives important fixes and security patches.
diff --git a/packages/vite/src/node/server/hmr.ts b/packages/vite/src/node/server/hmr.ts
@@ -861,7 +861,7 @@ function isNodeWithinCircularImports(
   currentChain: EnvironmentModuleNode[] = [node],
   traversedModules = new Set<EnvironmentModuleNode>(),
 ): boolean {
-  // To help visualize how each parameters work, imagine this import graph:
+  // To help visualize how each parameter works, imagine this import graph:
   //
   // A -> B -> C -> ACCEPTED -> D -> E -> NODE
   //      ^--------------------------|
diff --git a/playground/dynamic-import-inline/__tests__/dynamic-import-inline.spec.ts b/playground/dynamic-import-inline/__tests__/dynamic-import-inline.spec.ts
@@ -2,7 +2,7 @@ import { expect, test } from 'vitest'
 import { isBuild, serverLogs } from '~utils'
 
 test.runIf(isBuild)(
-  'dont warn when inlineDynamicImports is set to true',
+  "don't warn when inlineDynamicImports is set to true",
   async () => {
     const log = serverLogs.join('\n')
     expect(log).not.toContain(
diff --git a/playground/hmr-ssr/__tests__/hmr-ssr.spec.ts b/playground/hmr-ssr/__tests__/hmr-ssr.spec.ts
@@ -508,7 +508,7 @@ if (!isBuild) {
         })
       })
 
-      describe("doesn't reload if files not in the the entrypoint importers chain is changed", async () => {
+      describe("doesn't reload if files not in the entrypoint importers chain is changed", async () => {
         const testFile = 'non-tested/index.js'
 
         beforeAll(async () => {
diff --git a/playground/resolve/__tests__/resolve.spec.ts b/playground/resolve/__tests__/resolve.spec.ts
@@ -97,7 +97,7 @@ test('exact extension vs. duplicated (.js.js)', async () => {
   expect(await page.textContent('.exact-extension')).toMatch('[success]')
 })
 
-test('dont add extension to directory name (./dir-with-ext.js/index.js)', async () => {
+test("don't add extension to directory name (./dir-with-ext.js/index.js)", async () => {
   expect(await page.textContent('.dir-with-ext')).toMatch('[success]')
 })
 
@@ -224,7 +224,7 @@ test('Resolving with query with imports field', async () => {
   )
 })
 
-test('Resolve doesnt interrupt page request with trailing query and .css', async () => {
+test("Resolve doesn't interrupt page request with trailing query and .css", async () => {
   await page.goto(viteTestUrl + '/?test.css')
   expect(await page.locator('vite-error-overlay').count()).toBe(0)
   expect(await page.textContent('h1')).toBe('Resolve')
@@ -235,7 +235,7 @@ test('resolve non-normalized absolute path', async () => {
 })
 
 test.runIf(!isWindows)(
-  'Resolve doesnt interrupt page request that clashes with local project package.json',
+  "Resolve doesn't interrupt page request that clashes with local project package.json",
   async () => {
     // Sometimes request path may point to a different project's package.json, but for testing
     // we point to Vite's own monorepo which always exists, and the package.json is not a library
diff --git a/playground/ssr/src/forked-deadlock/README.md b/playground/ssr/src/forked-deadlock/README.md
@@ -1,4 +1,4 @@
-This test aim to check for a particular type of circular dependency that causes tricky deadlocks, **deadlocks with forked imports stack**
+This test aims to check for a particular type of circular dependency that causes tricky deadlocks, **deadlocks with forked imports stack**
 
 ```
 A -> B means: B is imported by A and B has A in its stack
@@ -44,7 +44,7 @@ This may seems a traditional deadlock, but the thing that makes this special is
 	[H]
 ```
 
-Even if `[X]` is imported by `[B]`, `[B]` is not in `[X]`'s stack because it's imported by `[H]` in first place then it's stack is only composed by `[H]`. `[H]` **forks** the imports **stack** and this make hard to be found.
+Even if `[X]` is imported by `[B]`, `[B]` is not in `[X]`'s stack because it's imported by `[H]` in first place then it's stack is only composed by `[H]`. `[H]` **forks** the imports **stack** and this makes it hard to be found.
 
 ### Fix description
 
diff --git a/playground/tsconfig-json/__tests__/tsconfig-json.spec.ts b/playground/tsconfig-json/__tests__/tsconfig-json.spec.ts
@@ -56,7 +56,7 @@ describe('transformWithEsbuild', () => {
         }
       }`,
     })
-    // "verbatimModuleSyntax": true from from tsconfig.json should not be read
+    // "verbatimModuleSyntax": true from tsconfig.json should not be read
     // and defaults to false
     expect(result.code).not.toMatch(/import.*".\/not-used-type";/)
   })
