Update some module/moduleResolution links to old content (#2985)

Author: andrewbranch

packages/documentation/copy/en/handbook-v2/Modules.md

@@ -339,7 +339,7 @@ The Node strategy replicates how Node.js works in CommonJS mode, with additional
 
 There are many TSConfig flags which influence the module strategy within TypeScript: [`moduleResolution`](/tsconfig#moduleResolution), [`baseUrl`](/tsconfig#baseUrl), [`paths`](/tsconfig#paths), [`rootDirs`](/tsconfig#rootDirs).
 
-For the full details on how these strategies work, you can consult the [Module Resolution](/docs/handbook/module-resolution.html).
+For the full details on how these strategies work, you can consult the [Module Resolution](/docs/handbook/modules/reference.html#the-moduleresolution-compiler-option) reference page.
 
 ## TypeScript's Module Output Options
 

packages/tsconfig-reference/copy/en/options/module.md

@@ -3,9 +3,9 @@ display: "Module"
 oneline: "Specify what module code is generated."
 ---
 
-Sets the module system for the program. See the <a href='/docs/handbook/modules.html'>Modules</a> reference page for more information. You very likely want `"nodenext"` for modern node projects.
+Sets the module system for the program. See the [theory behind TypeScript’s `module` option](/docs/handbook/modules/theory.html#the-module-output-format) and [its reference page](/docs/handbook/modules/reference.html#the-module-compiler-option) for more information. You very likely want `"nodenext"` for modern Node.js projects.
 
-Changing `module` affects [`moduleResolution`](#moduleResolution) which [also has a reference page](/docs/handbook/module-resolution.html).
+Changing `module` affects [`moduleResolution`](#moduleResolution) which [also has a reference page](/docs/handbook/modules/reference.html#the-moduleresolution-compiler-option).
 
 Here's some example output for this file:
 
@@ -87,9 +87,9 @@ export const twoPi = valueOfPi * 2;
 
 In addition to the base functionality of `ES2015`/`ES6`, `ES2020` adds support for [dynamic `import`s](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import), and [`import.meta`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/import.meta) while `ES2022` further adds support for [top level `await`](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/await#top_level_await).
 
-#### `node16`/`nodenext` (nightly builds)
+#### `node16`/`nodenext`
 
-Available from 4.7+, the `node16` and `nodenext` modes integrate with Node's [native ECMAScript Module support](https://nodejs.org/api/esm.html). The emitted JavaScript uses either `CommonJS` or `ES2020` output depending on the file extension and the value of the `type` setting in the nearest `package.json`. Module resolution also works differently. You can learn more in the [handbook](https://www.typescriptlang.org/docs/handbook/esm-node.html).
+Available from 4.7+, the `node16` and `nodenext` modes integrate with Node's [native ECMAScript Module support](https://nodejs.org/api/esm.html). The emitted JavaScript uses either `CommonJS` or `ES2020` output depending on the file extension and the value of the `type` setting in the nearest `package.json`. Module resolution also works differently. You can learn more in the [handbook](/docs/handbook/esm-node.html) and [Modules Reference](/docs/handbook/modules/reference.html#node16-nodenext).
 
 #### `None`
 

packages/tsconfig-reference/copy/en/options/moduleDetection.md

@@ -4,7 +4,7 @@ oneline: "Specify what method is used to detect whether a file is a script or a
 ---
 
 This setting controls how TypeScript determines whether a file is a
-[script or a module](/docs/handbook/2/modules.html#how-javascript-modules-are-defined).
+[script or a module](/docs/handbook/modules/theory.html#scripts-and-modules-in-javascript).
 
 There are three choices:
 

packages/tsconfig-reference/copy/en/options/moduleResolution.md

@@ -13,4 +13,4 @@ Specify the module resolution strategy:
 
 - `'classic'` was used in TypeScript before the release of 1.6. `classic` should not be used.
 
-There is a handbook reference page on [Module Resolution](/docs/handbook/module-resolution.html)
+There are reference pages explaining the [theory behind TypeScript’s module resolution](https://www.typescriptlang.org/docs/handbook/modules/theory.html#module-resolution) and the [details of each option](/docs/handbook/modules/reference.html#the-moduleresolution-compiler-option).

packages/tsconfig-reference/copy/en/options/paths.md

@@ -3,7 +3,7 @@ display: "Paths"
 oneline: "Specify a set of entries that re-map imports to additional lookup locations."
 ---
 
-A series of entries which re-map imports to lookup locations relative to the [`baseUrl`](#baseUrl) if set, or to the tsconfig file itself otherwise. There is a larger coverage of `paths` in [the handbook](/docs/handbook/module-resolution.html#path-mapping).
+A series of entries which re-map imports to lookup locations relative to the [`baseUrl`](#baseUrl) if set, or to the tsconfig file itself otherwise. There is a larger coverage of `paths` in [the `moduleResolution` reference page](/docs/handbook/modules/reference.html#paths).
 
 `paths` lets you declare how TypeScript should resolve an import in your `require`/`import`s.
 

packages/tsconfig-reference/copy/en/options/traceResolution.md

@@ -5,5 +5,3 @@ oneline: "Log paths used during the [`moduleResolution`](#moduleResolution) proc
 
 When you are trying to debug why a module isn't being included.
 You can set `traceResolution` to `true` to have TypeScript print information about its resolution process for each processed file.
-
-You can read more about this in [the handbook](/docs/handbook/module-resolution.html#tracing-module-resolution).