docs: update faq

README.md

@@ -332,19 +332,19 @@ If there's a problem you're encountering or something you need help with, don't
 
 ## FAQ
 
-### Why is it named `tsx`?
+### Why is it named _tsx_?
 
 `tsx` stands for "TypeScript execute". Mirroring [`npx`](https://docs.npmjs.com/cli/v8/commands/npx), which stands for "Node.js package execute".
 
 The 3-character package name offers an elegant developer experience, allowing usage like: `npx tsx ...`.
 
 Unfortunately, it overlaps with React's [TSX/JSX](https://www.typescriptlang.org/docs/handbook/jsx.html), which stands for "TypeScript XML".
 
-### Does it do type-checking?
+### Does it type check the code it runs?
 
-No, [esbuild does not support type checking](https://esbuild.github.io/faq/#:~:text=TypeScript%20type%20checking%20(just%20run%20tsc%20separately)).
+No. tsx is designed to be a simple TypeScript runner.
 
-It's recommended to run TypeScript separately as a command (`tsc --noEmit`) or via [IDE IntelliSense](https://code.visualstudio.com/docs/languages/typescript).
+If you need type-checking, you can use an IDE like [VS Code](https://code.visualstudio.com) and it will type-check as you code via [IntelliSense](https://code.visualstudio.com/docs/languages/typescript). Alternatively, you can run the TypeScript Compiler only for type-checking (e.g. `tsc --noEmit`) as a linting step.
 
 
 ### How is `tsx` different from [`ts-node`](https://github.com/TypeStrong/ts-node)?
@@ -371,34 +371,20 @@ As a bonus, tsx also comes with a watcher to speed up your development.
 
 [Here's an exhaustive technical comparison](https://github.com/privatenumber/ts-runtime-comparison) between `tsx`, `ts-node`, and other runtimes.
 
-### Can it use esbuild plugins?
-
-No. tsx uses esbuild's [Transform API](https://esbuild.github.io/api/#transform-api), which doesn't support plugins.
-
 ### Does it have a configuration file?
 
-No. tsx's integration with Node.js is designed to be seamless so there is no configuration.
+No. tsx's integration with Node.js is designed to be simple & seamless. However, it supports a few properties from `tsconfig.json` to determine how to compile TypeScript files.
 
 ### Does it have any limitations?
 
-Transformations are handled by esbuild, so it shares the same limitations such as:
+TypeScript & ESM transformations are handled by [esbuild](https://esbuild.github.io/), so it shares the same limitations such as:
 
 - Compatibility with code executed via `eval()` is not preserved
 - Only [certain `tsconfig.json` properties](https://esbuild.github.io/content-types/#tsconfig-json) are supported
 - [`emitDecoratorMetadata`](https://www.typescriptlang.org/tsconfig#emitDecoratorMetadata) is not supported 
 
 For details, refer to esbuild's [JavaScript caveats](https://esbuild.github.io/content-types/#javascript-caveats) and [TypeScript caveats](https://esbuild.github.io/content-types/#typescript-caveats) documentation.
 
-### Does Yarn PnP work?
-
-In CommonJS mode, yes. But in Module/ESM mode, [Node.js version v19.6.0 and up](https://github.com/nodejs/node/blob/v19.6.0/doc/changelogs/CHANGELOG_V19.md#esm-leverage-loaders-when-resolving-subsequent-loaders) is required.
-
-### There's an outdated dependency in tsx—can you update?
-
-Dependencies are typically declared with SemVer ranges to allow updates. You can use the [`npm update <package name>`](https://docs.npmjs.com/cli/v8/commands/npm-update) command to automatically update them to the latest version within the defined range.
-
-If the dependencies are out of the specified range, it indicates a potential breaking change that requires manual review. You're welcome to submit a pull request to initiate the upgrade.
-
 ## Sponsors
 
 <p align="center">