diff --git a/docs/maintenance/Pull_Requests.mdx b/docs/maintenance/Pull_Requests.mdx
index 04c1547f0cb7..3a9f435f5cf9 100644
--- a/docs/maintenance/Pull_Requests.mdx
+++ b/docs/maintenance/Pull_Requests.mdx
@@ -80,7 +80,7 @@ If there's no backing issue:
   - Parenthesis and whitespace (see: `getWrappingFixer`).
   - Unions and intersections (see: `unionConstituents` and `intersectionConstituents`).
 - Unit tests:
-  - All lines are covered per the Codecov / `yarn jest path/to/impacted/file --coverage` report.
+  - All lines are covered per the Codecov / `pnpx jest path/to/impacted/file --coverage` report.
   - Both "positive" and "negative" ("valid" and "invalid") cases exist, if reasonably possible to test for.
   - Fixes and suggestions, if present, don't remove `//` or `/*` comments
   - `invalid` lint rule errors include line and column information
diff --git a/docs/troubleshooting/faqs/TypeScript.mdx b/docs/troubleshooting/faqs/TypeScript.mdx
index 40f1a24d461a..c6b877e8ff85 100644
--- a/docs/troubleshooting/faqs/TypeScript.mdx
+++ b/docs/troubleshooting/faqs/TypeScript.mdx
@@ -10,7 +10,7 @@ import TabItem from '@theme/TabItem';
 ## Should TypeScript be installed globally or locally?
 
 Make sure that you have installed TypeScript locally i.e. by using `npm install typescript`, not `npm install -g typescript`,
-or by using `yarn add typescript`, not `yarn global add typescript`.
+or by using `pnpm add typescript`, not `pnpm add -g add typescript`.
 See [#2041](https://github.com/typescript-eslint/typescript-eslint/issues/2041) for more information.
 
 ## Why don't I see TypeScript errors in my ESLint output?