update some

Author: devjiwonchoi

docs/01-app/03-api-reference/05-config/02-typescript.mdx

@@ -82,7 +82,7 @@ Next.js generates global helpers for App Router route types. These are available
 
 ## Examples
 
-### Type checking Next.js Configuration files
+### Type Checking Next.js Configuration Files
 
 You can use TypeScript and import types in your Next.js configuration by using `next.config.ts`.
 
@@ -96,7 +96,7 @@ const nextConfig: NextConfig = {
 export default nextConfig
 ```
 
-Module resolution in `next.config.ts` is currently limited to CommonJS. However, ECMAScript Modules syntax is available when [using Node.js native TypeScript resolver](#using-nodejs-native-typescript-resolver-for-nextconfigts) for Node.js v22.10.0 and higher.
+Module resolution in `next.config.ts` is currently limited to CommonJS. However, ECMAScript Modules (ESM) syntax is available when [using Node.js native TypeScript resolver](#using-nodejs-native-typescript-resolver-for-nextconfigts) for Node.js v22.10.0 and higher.
 
 When using the `next.config.js` file, you can add some type checking in your IDE using JSDoc as below:
 
@@ -113,17 +113,17 @@ module.exports = nextConfig
 
 ### Using Node.js Native TypeScript Resolver for `next.config.ts`
 
-> **Note**: Resolving `next.config.ts` using Node.js native TypeScript resolver is available for Node.js v22.10.0 and higher, and only when the feature is enabled. Next.js does not enable the feature by default.
+> **Note**: Using Node.js native TypeScript resolver for `next.config.ts` is available for Node.js v22.10.0 and higher, and only when the feature is enabled. Next.js does not enable the feature by default.
 
-Next.js feature detects [Node.js native TypeScript resolver](https://nodejs.org/api/typescript.html) by [`process.features.typescript`](https://nodejs.org/api/process.html#processfeaturestypescript) which was added in Node.js v22.10.0. This allows `next.config.ts` to use native ECMAScript Modules syntax like top-level `await` and dynamic imports in `next.config.ts`. However, it inherits the limitations of the Node.js native TypeScript resolver.
+Next.js feature detects [Node.js native TypeScript resolver](https://nodejs.org/api/typescript.html) by [`process.features.typescript`](https://nodejs.org/api/process.html#processfeaturestypescript) which was added in Node.js v22.10.0. This allows `next.config.ts` to use native ECMAScript Modules (ESM) syntax like top-level `await` and dynamic imports in `next.config.ts`. However, it inherits the limitations of the Node.js native TypeScript resolver.
 
-For Node.js below v23.6.0, you need to run `next dev` with `NODE_OPTIONS=--experimental-transform-types` flag to enable the Node.js native TypeScript resolver:
+Node.js enables the feature by default since [v22.18.0](https://nodejs.org/en/blog/release/v22.18.0). For versions below v22.18.0, you need to run `next dev` with `NODE_OPTIONS=--experimental-transform-types` flag to enable the Node.js native TypeScript resolver:
 
 ```bash
 NODE_OPTIONS=--experimental-transform-types next <command>
 ```
 
-Although `next.config.ts` supports native ECMAScript Modules syntax on CommonJS projects, Node.js will still assume `next.config.ts` is a CommonJS file by default, resulting in Node.js reparsing the file as ECMAScript Modules when module syntax is detected. Therefore, we recommend using the `next.config.mts` file for CommonJS projects.
+Although `next.config.ts` supports native ESM syntax on CommonJS projects, Node.js will still assume `next.config.ts` is a CommonJS file by default, resulting in Node.js reparsing the file as ESM when module syntax is detected. Therefore, we recommend using the `next.config.mts` file for CommonJS projects.
 
 ```ts filename="next.config.mts"
 import type { NextConfig } from 'next'