docs: fix typos in documentation

CHANGELOG.md

@@ -40,7 +40,7 @@
 ### Bug Fixes
 * [`a9d242b`](https://github.com/npm/cli/commit/a9d242bc4f04440630141743949ddb0d323f90b4) [#9099](https://github.com/npm/cli/pull/9099) include all subcommands on main command help (#9099) (@wraithgar)
 * [`29b8407`](https://github.com/npm/cli/commit/29b8407971af1b9a2a3dcdb3849adfa04363fa7f) [#9087](https://github.com/npm/cli/pull/9087) unwrap comments and lines meant for output (#9087) (@wraithgar)
-* [`b56986a`](https://github.com/npm/cli/commit/b56986acb0661fba2c80135eff3d140aa659dcf5) [#9095](https://github.com/npm/cli/pull/9095) ls: suppress false UNMET DEPENDENCYs in linked strategy (#9095) (@manzoorwanijk)
+* [`b56986a`](https://github.com/npm/cli/commit/b56986acb0661fba2c80135eff3d140aa659dcf5) [#9095](https://github.com/npm/cli/pull/9095) ls: suppress false UNMET dependencies in linked strategy (#9095) (@manzoorwanijk)
 * [`76c76e5`](https://github.com/npm/cli/commit/76c76e5ad7cc5c7f641a92334b900c9d0c9a3fbd) [#9083](https://github.com/npm/cli/pull/9083) ci: don't error on optional deps in the lockfile (#9083) (@wraithgar)
 * [`a29aeee`](https://github.com/npm/cli/commit/a29aeee18f3ddc2348a8e00787d237c874642789) [#9028](https://github.com/npm/cli/pull/9028) arborist: retry bin-links on Windows EPERM (#9028) (@manzoorwanijk)
 * [`6565eeb`](https://github.com/npm/cli/commit/6565eeb818494e1feb4e14492804ce936b394b4a) [#9045](https://github.com/npm/cli/pull/9045) bypass packument cache to prevent ETARGET errors after publish (#9045) (@Jadu07)

docs/lib/content/configuring-npm/folders.md

@@ -143,7 +143,7 @@ So, that gets installed at [A].
 Since the parent installation of blerg satisfies bar's dependency on `blerg@1.x`, it does not install another copy under [B].
 
 Bar [B] also has dependencies on baz and asdf.
-Because it depends on `baz@2.x`, it cannot re-use the `baz@1.2.3` installed in the parent `node_modules` folder [D], and must install its own copy [C].
+Because it depends on `baz@2.x`, it cannot reuse the `baz@1.2.3` installed in the parent `node_modules` folder [D], and must install its own copy [C].
 In order to minimize duplication, npm hoists dependencies to the top level by default, so asdf is installed under [A].
 
 Underneath bar, the `baz -> quux -> bar` dependency creates a cycle.

node_modules/node-gyp/gyp/docs/InputFormatReference.md

@@ -956,7 +956,7 @@ values, depending on the setting of `OS`:
 Note that when `OS` is `win`, the `include` for `_win.cc` files is
 processed after the `exclude` matching the same pattern, because the
 `sources/` list participates in [merging](#Merging) during
-[conditional evaluation](#Conditonals) just like any other list
+[conditional evaluation](#Conditionals) just like any other list
 would.  This guarantees that the `_win.cc` files, previously
 unconditionally excluded, will be re-included when `OS` is `win`.
 

node_modules/node-gyp/gyp/docs/LanguageSpecification.md

@@ -61,7 +61,7 @@ The overall design has the following characteristics:
 
 Some up-front design principles/thoughts/TODOs:
 
-  * Re-use keywords consistently.
+  * Reuse keywords consistently.
   * Keywords that allow configuration of a platform-specific concept get
     prefixed appropriately:
     * Examples:  `msvs_disabled_warnings`, `xcode_framework_dirs`

node_modules/postcss-selector-parser/API.md

@@ -655,7 +655,7 @@ Remains `undefined` if there is no attribute value.
 Like `node.spaces` with the `before` and `after` values containing the spaces
 around the element, the parts of the attribute can also have spaces before
 and after them. The for each of `attribute`, `operator`, `value` and
-`insensitive` there is corresponding property of the same nam in
+`insensitive` there is corresponding property of the same name in
 `node.spaces` that has an optional `before` or `after` string containing only
 whitespace.
 

node_modules/safer-buffer/Porting-Buffer.md

@@ -46,7 +46,7 @@ also find calls to deprecated `Buffer()` API. Those rules are included in some p
 
 There is a drawback, though, that it doesn't always
 [work correctly](https://github.com/chalker/safer-buffer#why-not-safe-buffer) when `Buffer` is
-overriden e.g. with a polyfill, so recommended is a combination of this and some other method
+overridden e.g. with a polyfill, so recommended is a combination of this and some other method
 described above.
 
 <a id="variant-1"></a>
@@ -68,7 +68,7 @@ Note that `Buffer.alloc()` is also _faster_ on the current Node.js versions than
 Enabling eslint rule [no-buffer-constructor](https://eslint.org/docs/rules/no-buffer-constructor)
 or
 [node/no-deprecated-api](https://github.com/mysticatea/eslint-plugin-node/blob/master/docs/rules/no-deprecated-api.md)
-is recommended to avoid accidential unsafe Buffer API usage.
+is recommended to avoid accidental unsafe Buffer API usage.
 
 There is also a [JSCodeshift codemod](https://github.com/joyeecheung/node-dep-codemod#dep005)
 for automatically migrating Buffer constructors to `Buffer.alloc()` or `Buffer.from()`.
@@ -87,7 +87,7 @@ your users will not observe a runtime deprecation warning when running your code
 Utilize [safer-buffer](https://www.npmjs.com/package/safer-buffer) as a polyfill to support older
 Node.js versions.
 
-You would take exacly the same steps as in [Variant 1](#variant-1), but with a polyfill
+You would take exactly the same steps as in [Variant 1](#variant-1), but with a polyfill
 `const Buffer = require('safer-buffer').Buffer` in all files where you use the new `Buffer` api.
 
 Make sure that you do not use old `new Buffer` API — in any files where the line above is added,