doc: alphabetize VirtualFileSystem members in vfs.md

Author: mcollina

doc/api/vfs.md

@@ -175,27 +175,36 @@ added: REPLACEME
 
 Creates a new `VirtualFileSystem` instance.
 
-### `vfs.provider`
+### `vfs.chdir(path)`
 
 <!-- YAML
 added: REPLACEME
 -->
 
-* {VirtualProvider}
+* `path` {string} The new working directory path within the VFS.
 
-The underlying provider for this VFS instance. Can be used to access
-provider-specific methods like `setReadOnly()` for `MemoryProvider`.
+Changes the virtual working directory. This only affects path resolution within
+the VFS when `virtualCwd` is enabled in the constructor options.
 
-```cjs
-const vfs = require('node:vfs');
+Throws `ERR_INVALID_STATE` if `virtualCwd` was not enabled during construction.
 
-const myVfs = vfs.create();
+When mounted with `virtualCwd` enabled, the VFS also hooks `process.chdir()` and
+`process.cwd()` to support virtual paths transparently. In Worker threads,
+`process.chdir()` to virtual paths will work, but attempting to change to real
+file system paths will throw `ERR_WORKER_UNSUPPORTED_OPERATION`.
 
-// Access the provider
-console.log(myVfs.provider.readonly); // false
-myVfs.provider.setReadOnly();
-console.log(myVfs.provider.readonly); // true
-```
+### `vfs.cwd()`
+
+<!-- YAML
+added: REPLACEME
+-->
+
+* Returns: {string|null}
+
+Returns the current virtual working directory, or `null` if no virtual directory
+has been set yet.
+
+Throws `ERR_INVALID_STATE` if `virtualCwd` was not enabled during construction.
 
 ### `vfs.mount(prefix)`
 
@@ -226,26 +235,25 @@ myVfs.mount('/virtual');
 require('node:fs').readFileSync('/virtual/data.txt', 'utf8'); // 'Hello'
 ```
 
-### `vfs.unmount()`
+### `vfs.mounted`
 
 <!-- YAML
 added: REPLACEME
 -->
 
-Unmounts the virtual file system. After unmounting, virtual files are no longer
-accessible through the `fs` module. The VFS can be remounted at the same or a
-different path by calling `mount()` again. Unmounting also resets the virtual
-working directory if one was set.
+* {boolean}
 
-### `vfs.mounted`
+Returns `true` if the VFS is currently mounted.
+
+### `vfs.mountPoint`
 
 <!-- YAML
 added: REPLACEME
 -->
 
-* {boolean}
+* {string | null}
 
-Returns `true` if the VFS is currently mounted.
+The current mount point, or `null` if not mounted.
 
 ### `vfs.overlay`
 
@@ -259,56 +267,48 @@ Returns `true` if overlay mode is enabled. In overlay mode, the VFS only
 intercepts paths that exist in the VFS, allowing other paths to fall through
 to the real file system.
 
-### `vfs.mountPoint`
+### `vfs.provider`
 
 <!-- YAML
 added: REPLACEME
 -->
 
-* {string | null}
-
-The current mount point, or `null` if not mounted.
+* {VirtualProvider}
 
-### `vfs.readonly`
+The underlying provider for this VFS instance. Can be used to access
+provider-specific methods like `setReadOnly()` for `MemoryProvider`.
 
-<!-- YAML
-added: REPLACEME
--->
+```cjs
+const vfs = require('node:vfs');
 
-* {boolean}
+const myVfs = vfs.create();
 
-Returns `true` if the underlying provider is read-only.
+// Access the provider
+console.log(myVfs.provider.readonly); // false
+myVfs.provider.setReadOnly();
+console.log(myVfs.provider.readonly); // true
+```
 
-### `vfs.chdir(path)`
+### `vfs.readonly`
 
 <!-- YAML
 added: REPLACEME
 -->
 
-* `path` {string} The new working directory path within the VFS.
-
-Changes the virtual working directory. This only affects path resolution within
-the VFS when `virtualCwd` is enabled in the constructor options.
-
-Throws `ERR_INVALID_STATE` if `virtualCwd` was not enabled during construction.
+* {boolean}
 
-When mounted with `virtualCwd` enabled, the VFS also hooks `process.chdir()` and
-`process.cwd()` to support virtual paths transparently. In Worker threads,
-`process.chdir()` to virtual paths will work, but attempting to change to real
-file system paths will throw `ERR_WORKER_UNSUPPORTED_OPERATION`.
+Returns `true` if the underlying provider is read-only.
 
-### `vfs.cwd()`
+### `vfs.unmount()`
 
 <!-- YAML
 added: REPLACEME
 -->
 
-* Returns: {string|null}
-
-Returns the current virtual working directory, or `null` if no virtual directory
-has been set yet.
-
-Throws `ERR_INVALID_STATE` if `virtualCwd` was not enabled during construction.
+Unmounts the virtual file system. After unmounting, virtual files are no longer
+accessible through the `fs` module. The VFS can be remounted at the same or a
+different path by calling `mount()` again. Unmounting also resets the virtual
+working directory if one was set.
 
 ### File System Methods
 
@@ -328,10 +328,10 @@ including `string`, `Buffer`, `TypedArray`, and `DataView` where applicable.
 * `vfs.lstatSync(path[, options])` - Get file stats (no symlink follow)
 * `vfs.mkdirSync(path[, options])` - Create a directory
 * `vfs.openSync(path, flags[, mode])` - Open a file
+* `vfs.readdirSync(path[, options])` - Read directory contents
 * `vfs.readFileSync(path[, options])` - Read a file
-* `vfs.readSync(fd, buffer, offset, length, position)` - Read from fd
 * `vfs.readlinkSync(path[, options])` - Read symlink target
-* `vfs.readdirSync(path[, options])` - Read directory contents
+* `vfs.readSync(fd, buffer, offset, length, position)` - Read from fd
 * `vfs.realpathSync(path[, options])` - Resolve symlinks
 * `vfs.renameSync(oldPath, newPath)` - Rename a file or directory
 * `vfs.rmdirSync(path)` - Remove a directory