From 26efea1a7585f6694988f1a537c3b4b8f9db50f4 Mon Sep 17 00:00:00 2001
From: "Kamat, Trivikram" <16024985+trivikr@users.noreply.github.com>
Date: Sun, 6 Sep 2026 18:05:20 -0700
Subject: [PATCH] doc: qualify directory read ordering for native fs

Clarify that the documented operating system directory ordering applies
to reads handled by the native file system.

Signed-off-by: Kamat, Trivikram <16024985+trivikr@users.noreply.github.com>
---
 doc/api/fs.md | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/doc/api/fs.md b/doc/api/fs.md
index 9be67ded1f50..a21e828f5f04 100644
--- a/doc/api/fs.md
+++ b/doc/api/fs.md
@@ -7337,8 +7337,9 @@ Asynchronously read the next directory entry via readdir(3) as an
 A promise is returned that will be fulfilled with an {fs.Dirent}, or `null`
 if there are no more directory entries to read.
 
-Directory entries returned by this function are in no particular order as
-provided by the operating system's underlying directory mechanisms.
+For directory reads handled by the native file system, directory entries
+returned by this function are in no particular order as provided by the
+operating system's underlying directory mechanisms.
 Entries added or removed while iterating over the directory might not be
 included in the iteration results.