From 5c525b6efef1b8158ed1316389020a04b573ce1d Mon Sep 17 00:00:00 2001
From: Josh Goldberg <git@joshuakgoldberg.com>
Date: Sat, 17 Dec 2022 11:44:14 -0500
Subject: [PATCH] docs: explained tsconfigRootDir in website

---
 docs/architecture/Parser.mdx  |  3 ++-
 docs/linting/Typed_Linting.md | 22 +++++++++++-----------
 2 files changed, 13 insertions(+), 12 deletions(-)

diff --git a/docs/architecture/Parser.mdx b/docs/architecture/Parser.mdx
index 9f5d51a53bb6..d8d4f05ee43d 100644
--- a/docs/architecture/Parser.mdx
+++ b/docs/architecture/Parser.mdx
@@ -226,7 +226,8 @@ For example, by default it will ensure that a glob like `./**/tsconfig.json` wil
 
 > Default `undefined`.
 
-This option allows you to provide the root directory for relative tsconfig paths specified in the `project` option above.
+This option allows you to provide the root directory for relative TSConfig paths specified in the `project` option above.
+Doing so ensures running ESLint from a directory other than the root will still be able to find your TSConfig.
 
 ### `warnOnUnsupportedTypeScriptVersion`
 
diff --git a/docs/linting/Typed_Linting.md b/docs/linting/Typed_Linting.md
index 3e1beb396a8a..65e2c875fff9 100644
--- a/docs/linting/Typed_Linting.md
+++ b/docs/linting/Typed_Linting.md
@@ -8,30 +8,30 @@ To tap into TypeScript's additional powers, there are two small changes you need
 
 ```js title=".eslintrc.js"
 module.exports = {
-  root: true,
-  parser: '@typescript-eslint/parser',
-  // Added lines start
-  parserOptions: {
-    tsconfigRootDir: __dirname,
-    project: ['./tsconfig.json'],
-  },
-  // Added lines end
-  plugins: ['@typescript-eslint'],
   extends: [
     'eslint:recommended',
     'plugin:@typescript-eslint/recommended',
     // Add this line
     'plugin:@typescript-eslint/recommended-requiring-type-checking',
   ],
+  plugins: ['@typescript-eslint'],
+  parser: '@typescript-eslint/parser',
+  // Added lines start
+  parserOptions: {
+    project: ['./tsconfig.json'],
+    tsconfigRootDir: __dirname,
+  },
+  // Added lines end
+  root: true,
 };
 ```
 
 In more detail:
 
-- `parserOptions.tsconfigRootDir` tells our parser the absolute path of your project's root directory.
+- `plugin:@typescript-eslint/recommended-requiring-type-checking` is another [recommended configuration](./CONFIGURATIONS.mdx) we provide. This one contains recommended rules that additionally require type information.
 - `parserOptions.project` tells our parser the relative path where your project's `tsconfig.json` is.
   - If your project is a multi-package monorepo, see [our docs on configuring a monorepo](./typed-linting/Monorepos.md).
-- `plugin:@typescript-eslint/recommended-requiring-type-checking` is another recommended configuration we provide. This one contains rules that specifically require type information.
+- `parserOptions.tsconfigRootDir` tells our parser the absolute path of your project's root directory (see [Parser#tsconfigRootDir](../architecture/Parser.mdx#tsconfigRootDir)).
 
 With that done, run the same lint command you ran before.
 You may see new rules reporting errors based on type information!