diff --git a/apps/site/pages/en/learn/typescript/run-natively.md b/apps/site/pages/en/learn/typescript/run-natively.md
index e16a1bf38c85b..773f0201077d0 100644
--- a/apps/site/pages/en/learn/typescript/run-natively.md
+++ b/apps/site/pages/en/learn/typescript/run-natively.md
@@ -1,7 +1,7 @@
 ---
 title: Running TypeScript Natively
 layout: learn
-authors: AugustinMauroy
+authors: AugustinMauroy, khaosdoctor, jakebailey, robpalme
 ---
 
 > **⚠️WARNING⚠️:** All content in this article uses Node.js experimental features. Please make sure you are using a version of Node.js that supports the features mentioned in this article. And remember that experimental features can change in future versions of Node.js.
@@ -14,7 +14,7 @@ In the previous articles, we learned how to run TypeScript code using transpilat
 
 Since V22.6.0, Node.js has experimental support for some TypeScript syntax via "type stripping". You can write code that's valid TypeScript directly in Node.js without the need to transpile it first.
 
-The `--experimental-strip-types` flag tells Node.js to strip the type annotations from the TypeScript code before running it.
+The [`--experimental-strip-types`](https://nodejs.org/docs/latest-v22.x/api/cli.html#--experimental-strip-types) flag tells Node.js to strip the type annotations from the TypeScript code before running it.
 
 ```bash
 node --experimental-strip-types example.ts
@@ -22,10 +22,29 @@ node --experimental-strip-types example.ts
 
 And that's it! You can now run TypeScript code directly in Node.js without the need to transpile it first, and use TypeScript to catch type-related errors.
 
-In V22.7.0 this experimental support was extended to transform TypeScript-only syntax, like `enum`s and `namespace`, with the addition of the `--experimental-transform-types` flag.
+In V22.7.0 this experimental support was extended to transform TypeScript-only syntax, like `enum`s and `namespace`, with the addition of the [`--experimental-transform-types`](https://nodejs.org/docs/latest-v23.x/api/cli.html#--experimental-transform-types) flag. Enabling `--experimental-transform-types` automatically implies that `--experimental-strip-types` is enabled, so there's no need to use both flags in the same command:
 
 ```bash
-node --experimental-strip-types --experimental-transform-types another-example.ts
+node --experimental-transform-types another-example.ts
+```
+
+From V23 onwards, the `--experimental-strip-types` flag is enabled by default (you can disable it via the [`--no-experimental-strip-types`](https://nodejs.org/docs/latest-v23.x/api/cli.html#--no-experimental-strip-types) flag), enabling you to run any supported syntax, so running files like the one below with `node file.ts` is supported:
+
+```ts
+function foo(bar: number): string {
+  return 'hello';
+}
+```
+
+However, running any code that requires transformations, like the code below still needs the use of `--experimental-transform-types`:
+
+```ts
+enum MyEnum {
+  A,
+  B,
+}
+
+console.log(MyEnum.A);
 ```
 
 Future versions of Node.js will include support for TypeScript without the need for a command line flag.
@@ -34,7 +53,13 @@ Future versions of Node.js will include support for TypeScript without the need
 
 At the time of writing, the experimental support for TypeScript in Node.js has some limitations.
 
-You can get more information on the [API docs](https://nodejs.org/docs/latest/api/typescript.html#typescript-features).
+You can get more information on the [API docs](https://nodejs.org/docs/latest-v23.x/api/typescript.html#typescript-features).
+
+### Configuration
+
+The Node.js TypeScript loader ([Amaro](https://github.com/nodejs/amaro)) does not need or use `tsconfig.json` to run TypeScript code.
+
+We recommend configuring your editor and `tsc` to reflect Node.js behavior by creating a `tsconfig.json` using the `compilerOptions` listed [here](https://nodejs.org/api/typescript.html#type-stripping), as well as using TypeScript version **5.7 or higher**.
 
 ## Important notes