Fix typos

benchmarks/fixtures/react-app/README.md

@@ -1484,7 +1484,7 @@ Note that tests run much slower with coverage so it is recommended to run it sep
 
 #### Configuration
 
-The default Jest coverage configuration can be overriden by adding any of the following supported keys to a Jest config in your package.json.
+The default Jest coverage configuration can be overridden by adding any of the following supported keys to a Jest config in your package.json.
 
 Supported overrides:
  - [`collectCoverageFrom`](https://facebook.github.io/jest/docs/en/configuration.html#collectcoveragefrom-array)

docs/finders.md

@@ -85,7 +85,7 @@ Output:
     license: MIT
 ```
 
-Othere example use cases:
+Other example use cases:
 * Find all packages with a specific license.
 * Detect packages requiring a minimum Node.js version.
 * List all dependencies that expose binaries.

docs/installation.md

@@ -99,7 +99,7 @@ You can pin the version of pnpm used on your project using the following command
 corepack use pnpm@next-11
 ```
 
-This will add a `"packageManager"` field in your local `package.json` which will instruct Corepack to always use a specific version on that project. This can be useful if you want reproducability, as all developers who are using Corepack will use the same version as you. When a new version of pnpm is released, you can re-run the above command.
+This will add a `"packageManager"` field in your local `package.json` which will instruct Corepack to always use a specific version on that project. This can be useful if you want reproducibility, as all developers who are using Corepack will use the same version as you. When a new version of pnpm is released, you can re-run the above command.
 
 ## Using other package managers
 

versioned_docs/version-10.x/finders.md

@@ -89,7 +89,7 @@ Output:
     license: MIT
 ```
 
-Othere example use cases:
+Other example use cases:
 * Find all packages with a specific license.
 * Detect packages requiring a minimum Node.js version.
 * List all dependencies that expose binaries.

versioned_docs/version-10.x/installation.md

@@ -99,7 +99,7 @@ You can pin the version of pnpm used on your project using the following command
 corepack use pnpm@latest-10
 ```
 
-This will add a `"packageManager"` field in your local `package.json` which will instruct Corepack to always use a specific version on that project. This can be useful if you want reproducability, as all developers who are using Corepack will use the same version as you. When a new version of pnpm is released, you can re-run the above command.
+This will add a `"packageManager"` field in your local `package.json` which will instruct Corepack to always use a specific version on that project. This can be useful if you want reproducibility, as all developers who are using Corepack will use the same version as you. When a new version of pnpm is released, you can re-run the above command.
 
 ## Using other package managers
 

versioned_docs_archived/version-2.x/how-peers-are-resolved.md

@@ -40,7 +40,7 @@ As a consequence, the Node.js module resolver algorithm will find the correct pe
 
 *If the resolved peer is a direct dependency of the project*, it is not grouped separately with the dependent package.
 This is done to make it easier to make predictable and fast named (`pnpm i foo`) and general (`pnpm i`) installations.
-So if the project dependends on `bar@1.0.0`, the dependencies from our example will be grouped like this:
+So if the project depends on `bar@1.0.0`, the dependencies from our example will be grouped like this:
 
 ![](/img/how-peers-are-resolved/3.png)
 

versioned_docs_archived/version-2.x/package_json.md

@@ -132,7 +132,7 @@ An example of the `"pnpm"."overrides"` field:
 }
 ```
 
-You may specify the package the overriden dependency belongs to by
+You may specify the package the overridden dependency belongs to by
 separating the package selector from the dependency selector with a ">", for
 example `qar@1>zoo` will only override the `zoo` dependency of `qar@1`, not for
 any other dependencies.

versioned_docs_archived/version-3.x/package_json.md

@@ -49,7 +49,7 @@ If true, the selected peer dependency will be marked as optional by the package
 Added in: v3.4.0
 
 It is possible to override some fields in the manifest, before the package is packed.
-The following fields may be overriden: `typings`, `types`, `main` and `module`.
+The following fields may be overridden: `typings`, `types`, `main` and `module`.
 To override a field, add the publish version of the field to `publishConfig`.
 
 For instance, the following `package.json`:

versioned_docs_archived/version-3.x/pnpm-publish.md

@@ -35,7 +35,7 @@ Tells the registry whether the published package should be public or restricted.
 Added in: v3.4.0
 
 It is possible to override some fields in the manifest, before the package is packed.
-The following fields may be overriden: `typings`, `types`, `main` and `module`.
+The following fields may be overridden: `typings`, `types`, `main` and `module`.
 To override a field, add the publish version of the field to `publishConfig`.
 
 For instance, the following `package.json`:

versioned_docs_archived/version-4.x/pnpm-publish.md

@@ -35,7 +35,7 @@ Tells the registry whether the published package should be public or restricted.
 Added in: v3.4.0
 
 It is possible to override some fields in the manifest, before the package is packed.
-The following fields may be overriden: `typings`, `types`, `main` and `module`.
+The following fields may be overridden: `typings`, `types`, `main` and `module`.
 To override a field, add the publish version of the field to `publishConfig`.
 
 For instance, the following `package.json`:

versioned_docs_archived/version-5.x/continuous-integration.md

@@ -116,6 +116,6 @@ jobs:
 
 :::note
 
-Using `actions/setup-node@v2` you need to install pnpm with [root permissions](https://github.com/actions/setup-node/issues/177), eg:`sudo npm install -g pnpm`. Alternatively, if you specify the Node.js version to use, pnpm may be installed with no priviledged user.
+Using `actions/setup-node@v2` you need to install pnpm with [root permissions](https://github.com/actions/setup-node/issues/177), eg:`sudo npm install -g pnpm`. Alternatively, if you specify the Node.js version to use, pnpm may be installed with no privileged user.
 
 :::

versioned_docs_archived/version-5.x/package_json.md

@@ -132,7 +132,7 @@ An example of the `"pnpm"."overrides"` field:
 }
 ```
 
-You may specify the package the overriden dependency belongs to by
+You may specify the package the overridden dependency belongs to by
 separating the package selector from the dependency selector with a ">", for
 example `qar@1>zoo` will only override the `zoo` dependency of `qar@1`, not for
 any other dependencies.

versioned_docs_archived/version-6.x/package_json.md

@@ -231,7 +231,7 @@ An example of the `"pnpm"."overrides"` field:
 }
 ```
 
-You may specify the package the overriden dependency belongs to by
+You may specify the package the overridden dependency belongs to by
 separating the package selector from the dependency selector with a ">", for
 example `qar@1>zoo` will only override the `zoo` dependency of `qar@1`, not for
 any other dependencies.

versioned_docs_archived/version-7.x/motivation.md

@@ -26,7 +26,7 @@ projects and dependencies, and you have a lot faster installations!
 
 ## Boosting installation speed
 
-pnpm perfoms installation in three stages:
+pnpm performs installation in three stages:
 
 1. Dependency resolution. All required dependencies are identified and fetched to the store.
 1. Directory structure calculation. The `node_modules` directory structure is calculated based on the dependencies.

versioned_docs_archived/version-7.x/package_json.md

@@ -241,7 +241,7 @@ An example of the `"pnpm"."overrides"` field:
 }
 ```
 
-You may specify the package the overriden dependency belongs to by
+You may specify the package the overridden dependency belongs to by
 separating the package selector from the dependency selector with a ">", for
 example `qar@1>zoo` will only override the `zoo` dependency of `qar@1`, not for
 any other dependencies.

versioned_docs_archived/version-8.x/cli/link.md

@@ -96,7 +96,7 @@ pnpm link --global # link foo globally
 
 ## What's the difference between `pnpm link` and using the `file:` protocol?
 
-When you use `pnpm link`, the linked package is symlinked from the source code. You can modify the source code of the linked package, and the changes will be reflected in your project. With this method pnpm will not install the dependencies of the linked package, you will have to install them manually in the source code. This may be usefull when you have to use a specific package manager for the linked package, for example, if you want to use `npm` for the linked package, but pnpm for your project.
+When you use `pnpm link`, the linked package is symlinked from the source code. You can modify the source code of the linked package, and the changes will be reflected in your project. With this method pnpm will not install the dependencies of the linked package, you will have to install them manually in the source code. This may be useful when you have to use a specific package manager for the linked package, for example, if you want to use `npm` for the linked package, but pnpm for your project.
 
 When you use the `file:` protocol in `dependencies`, the linked package is hard-linked to your project `node_modules`, you can modify the source code of the linked package, and the changes will be reflected in your project. With this method pnpm will also install the dependencies of the linked package, overriding the `node_modules` of the linked package.
 

versioned_docs_archived/version-8.x/installation.md

@@ -84,7 +84,7 @@ You can pin the version of pnpm used on your project using the following command
 corepack use pnpm@latest-8
 ```
 
-This will add a `"packageManager"` field in your local `package.json` which will instruct Corepack to always use a specific version on that project. This can be useful if you want reproducability, as all developers who are using Corepack will use the same version as you. When a new version of pnpm is released, you can re-run the above command.
+This will add a `"packageManager"` field in your local `package.json` which will instruct Corepack to always use a specific version on that project. This can be useful if you want reproducibility, as all developers who are using Corepack will use the same version as you. When a new version of pnpm is released, you can re-run the above command.
 
 ## Using npm
 

versioned_docs_archived/version-8.x/motivation.md

@@ -26,7 +26,7 @@ projects and dependencies, and you have a lot faster installations!
 
 ## Boosting installation speed
 
-pnpm perfoms installation in three stages:
+pnpm performs installation in three stages:
 
 1. Dependency resolution. All required dependencies are identified and fetched to the store.
 1. Directory structure calculation. The `node_modules` directory structure is calculated based on the dependencies.

versioned_docs_archived/version-8.x/package_json.md

@@ -248,7 +248,7 @@ An example of the `"pnpm"."overrides"` field:
 }
 ```
 
-You may specify the package the overriden dependency belongs to by
+You may specify the package the overridden dependency belongs to by
 separating the package selector from the dependency selector with a ">", for
 example `qar@1>zoo` will only override the `zoo` dependency of `qar@1`, not for
 any other dependencies.

versioned_docs_archived/version-9.x/cli/add.md

@@ -152,15 +152,15 @@ pnpm add https://github.com/zkochan/is-negative.git#2.0.1
 
 #### Install from a Git repository using hosting providers shorthand
 
-You can use a protocol shorthand `[provier]:` for certain Git providers:
+You can use a protocol shorthand `[provider]:` for certain Git providers:
 
 ```
 pnpm add github:zkochan/is-negative
 pnpm add bitbucket:pnpmjs/git-resolver
 pnpm add gitlab:pnpm/git-resolver
 ```
 
-If `[provider]:` is omited, it defaults to `github:`.
+If `[provider]:` is omitted, it defaults to `github:`.
 
 #### Install from a Git repository combining different parameters
 

versioned_docs_archived/version-9.x/installation.md

@@ -92,7 +92,7 @@ You can pin the version of pnpm used on your project using the following command
 corepack use pnpm@latest
 ```
 
-This will add a `"packageManager"` field in your local `package.json` which will instruct Corepack to always use a specific version on that project. This can be useful if you want reproducability, as all developers who are using Corepack will use the same version as you. When a new version of pnpm is released, you can re-run the above command.
+This will add a `"packageManager"` field in your local `package.json` which will instruct Corepack to always use a specific version on that project. This can be useful if you want reproducibility, as all developers who are using Corepack will use the same version as you. When a new version of pnpm is released, you can re-run the above command.
 
 ## Using other package managers
 

versioned_docs_archived/version-9.x/motivation.md

@@ -26,7 +26,7 @@ projects and dependencies, and you have a lot faster installations!
 
 ## Boosting installation speed
 
-pnpm perfoms installation in three stages:
+pnpm performs installation in three stages:
 
 1. Dependency resolution. All required dependencies are identified and fetched to the store.
 1. Directory structure calculation. The `node_modules` directory structure is calculated based on the dependencies.