Minor tweaks in response to feedback

Author: mikenomitch

src/content/changelogs-next/2025-01-22-nodejs-compat-improvements.mdx

@@ -1,14 +1,15 @@
 ---
-title: Improved Node.js compatibility
-description: Node.js APIs from the node:dns, node:net, and node:timers modules are now available when using nodejs_compatibility.
+title: Support for Node.js DNS, Net, and Timer APIs in Workers
+description: Node.js APIs from the node:dns, node:net, and node:timers modules are now available when using nodejs_compat.
 products:
   - workers
+	- pages
 date: 2025-01-22T13:00:00Z
 ---
 
 import { Render, PackageManagers, TypeScriptExample } from "~/components";
 
-When using a Worker with [nodejs_compatability](/workers/runtime-apis/nodejs/) enabled, you can now use the following Node.js APIs:
+When using a Worker with the [`nodejs_compat`](/workers/runtime-apis/nodejs/) compatibility flag enabled, you can now use the following Node.js APIs:
 
 - [`node:net`](/workers/runtime-apis/nodejs/net/)
 - [`node:dns`](/workers/runtime-apis/nodejs/dns/)
@@ -20,8 +21,6 @@ You can use [`net.Socket`](https://nodejs.org/api/net.html#class-netsocket) to c
 This can be useful when connecting to databases such as [MySQL](https://www.mysql.com/) or [PostgreSQL](https://www.postgresql.org/),
 though if possible, using [Hyperdrive Connection Pooling](/hyperdrive/configuration/how-hyperdrive-works/#connection-pooling) is preferable.
 
-These functions use [`connect`](/workers/runtime-apis/tcp-sockets/#connect) functionality from the built-in `cloudflare:sockets` module.
-
 <TypeScriptExample filename="index.ts">
 ```ts
 import net from 'node:net';
@@ -49,7 +48,7 @@ export default {
 Additionally, you can now use other APIs incliding [`net.BlockList`](https://nodejs.org/api/net.html#class-netblocklist) and
 [`net.SocketAddress`](https://nodejs.org/api/net.html#class-netsocketaddress).
 
-Note that the [`net.Server`](https://nodejs.org/api/net.html#class-netserver) module is not supported.
+Note that [`net.Server`](https://nodejs.org/api/net.html#class-netserver) is not supported.
 
 #### node:dns
 
@@ -60,20 +59,20 @@ You can use [`node:dns`](https://nodejs.org/api/dns.html) for name resolution vi
 ```ts
 import dns from "node:dns";
 
-dns.lookup("example.org", (_err: any, address: string, ipFamily: number) => {
-	console.log("address: %j family: IPv%s", address, ipFamily);
+dns.lookup("example.org", (_err: any, address: string, ipFamily: number) =>
+	console.log(`address: ${address} family: IPv${ipFamily}`);
 ````
 
 </TypeScriptExample>
 
-All `node:dns` functions are available.
+All `node:dns` functions are available, except `lookup`, `lookupService`, and `resolve` which throw "Not implemented" errors when called.
 
 #### node:timers
 
 You can use [`node:timers`](https://nodejs.org/api/timers.html) to schedule functions to be called at some future period of time.
 
 This includes [`setTimeout`](https://nodejs.org/api/timers.html#settimeoutcallback-delay-args) for calling a function after a delay,
-[`setInterval`](https://nodejs.org/api/timers.html#clearintervaltimeout) for calling a function repeatedly,
+[`setInterval`](https://nodejs.org/api/timers.html#setintervalcallback-delay-args) for calling a function repeatedly,
 and [`setImmediate`](https://nodejs.org/api/timers.html#setimmediatecallback-args) for calling a function in the next iteration of the event loop.
 
 <TypeScriptExample filename="index.ts">
@@ -91,8 +90,3 @@ console.log("next");
 
 ```
 </TypeScriptExample>
-
-Note that due to [security-based restrictions on timers](/workers/reference/security-model/#step-1-disallow-timers-and-multi-threading) in Workers,
-timers are limited to returning the time of the last I/O. This means that while setTimeout, setInterval, and setImmediate will defer your function execution
-until after other events have run, they will not delay them for the full time specified.
-```

src/content/docs/workers/runtime-apis/nodejs/assert.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: configuration
-title: Assert
+title: assert
 ---
 
 import { Render } from "~/components";

src/content/docs/workers/runtime-apis/nodejs/dns.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: configuration
-title: DNS
+title: dns
 ---
 
 import { Render, TypeScriptExample } from "~/components";
@@ -13,11 +13,15 @@ You can use [`node:dns`](https://nodejs.org/api/dns.html) for name resolution vi
 ```js
 import dns from "node:dns";
 
-dns.lookup("example.org", (err, address, ipFamily) => {
-	console.log("address: %j family: IPv%s", address, ipFamily);
+dns.lookup("example.org", (_err: any, address: string, ipFamily: number) =>
+	console.log(`address: ${address} family: IPv${ipFamily}`);
 });
 ```
 
-Note that DNS requests will execute a subrequest, counts for your [Worker's subrequest limit](/workers/platform/limits/#subrequests).
+:::note
+
+DNS requests will execute a subrequest, counts for your [Worker's subrequest limit](/workers/platform/limits/#subrequests).
+
+:::
 
 The full `node:dns` API is documented in the [Node.js documentation for `node:dns`](https://nodejs.org/api/dns.html).

src/content/docs/workers/runtime-apis/nodejs/net.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: configuration
-title: Net
+title: net
 ---
 
 import { Render, TypeScriptExample } from "~/components";
@@ -40,6 +40,6 @@ export default {
 Additionally, other APIs such as [`net.BlockList`](https://nodejs.org/api/net.html#class-netblocklist)
 and [`net.SocketAddress`](https://nodejs.org/api/net.html#class-netsocketaddress) are available.
 
-Note that the [`net.Server`](https://nodejs.org/api/net.html#class-netserver) module is not supported by Workers.
+Note that the [`net.Server`](https://nodejs.org/api/net.html#class-netserver) class is not supported by Workers.
 
 The full `node:net` API is documented in the [Node.js documentation for `node:net`](https://nodejs.org/api/net.html).

src/content/docs/workers/runtime-apis/nodejs/path.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: configuration
-title: Path
+title: path
 ---
 
 import { Render } from "~/components";

src/content/docs/workers/runtime-apis/nodejs/process.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: configuration
-title: Process
+title: process
 
 ---
 

src/content/docs/workers/runtime-apis/nodejs/test.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: configuration
-title: Test
+title: test
 
 ---
 

src/content/docs/workers/runtime-apis/nodejs/timers.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: configuration
-title: Timers
+title: timers
 ---
 
 import { Render, TypeScriptExample } from "~/components";
@@ -19,18 +19,21 @@ import timers from 'node:timers';
 
 console.log('first');
 timers.setTimeout(() => {
-	console.log('last');
+console.log('last');
 }, 10);
 
 timers.setTimeout(() => {
-	console.log('next');
+console.log('next');
 });
 
 ```
 </TypeScriptExample>
 
-Note that due to [security-based restrictions on timers](/workers/reference/security-model/#step-1-disallow-timers-and-multi-threading) in Workers,
+:::note
+Due to [security-based restrictions on timers](/workers/reference/security-model/#step-1-disallow-timers-and-multi-threading) in Workers,
 timers are limited to returning the time of the last I/O. This means that while setTimeout, setInterval, and setImmediate will defer your function execution
 until after other events have run, they will not delay them for the full time specified.
 
+:::
+
 The full `node:timers` API is documented in the [Node.js documentation for `node:timers`](https://nodejs.org/api/timers.html).

src/content/docs/workers/runtime-apis/nodejs/url.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: configuration
-title: URL
+title: url
 
 ---
 

src/content/docs/workers/runtime-apis/nodejs/util.mdx

@@ -1,6 +1,6 @@
 ---
 pcx_content_type: configuration
-title: Util
+title: util
 
 ---