docs: link tsconfig sections to kit config (#14026)

* docs: link tsconfig sections to kit config

* Apply suggestion from @eltigerchino

* Apply suggestion from @eltigerchino

---------

Co-authored-by: Tee Ming <[email protected]>
Co-authored-by: Rich Harris <[email protected]>

Author: 3 people

documentation/docs/10-getting-started/30-project-structure.md

@@ -79,7 +79,7 @@ This file contains your Svelte and SvelteKit [configuration](configuration).
 
 ### tsconfig.json
 
-This file (or `jsconfig.json`, if you prefer type-checked `.js` files over `.ts` files) configures TypeScript, if you added typechecking during `npx sv create`. Since SvelteKit relies on certain configuration being set a specific way, it generates its own `.svelte-kit/tsconfig.json` file which your own config `extends`.
+This file (or `jsconfig.json`, if you prefer type-checked `.js` files over `.ts` files) configures TypeScript, if you added typechecking during `npx sv create`. Since SvelteKit relies on certain configuration being set a specific way, it generates its own `.svelte-kit/tsconfig.json` file which your own config `extends`. To make changes to top-level options such as `include` and `exclude`, we recommend extending the generated config; see the [`typescript.config` setting](configuration#typescript) for more details.
 
 ### vite.config.js
 

documentation/docs/98-reference/54-types.md

@@ -190,6 +190,8 @@ Others are required for SvelteKit to work properly, and should also be left unto
 }
 ```
 
+Use the [`typescript.config` setting](configuration#typescript) in `svelte.config.js` to extend or modify the generated `tsconfig.json`.
+
 ## $lib
 
 This is a simple alias to `src/lib`, or whatever directory is specified as [`config.kit.files.lib`](configuration#files). It allows you to access common components and utility modules without `../../../../` nonsense.