doc: updated directory entry information

[el5846]

Fixes: #25595

Checklist

• make -j4 test (UNIX), or vcbuild test (Windows) passes
• documentation is changed or added
• commit message follows commit guidelines

[TimothyGu]

Let's try to be a bit more specific here. Someone who doesn't know what a directory entry is, is also unlikely to know what an inode is – let alone the fact that inodes don't exist in certain file systems that we support, like NTFS.

Could you say something in the sense of "A representation of an entry of a file system directory. Examples for directory entries include files and subfolders in a folder that is being read from. Data included in [fs.Dirent][] objects include the filename in the directory it belongs to, and also possibly certain metadata about the type of the directory entry, but not the actual file content."

(I'm not a native English speaker, so you could probably make it sound a bit better :)

[Trott]

This seems to add a lot of backup files unintentionally.

[Trott]

Hi, @el5846! You don't need to close this. You can get rid of the backup files on your fork and push another commit to this branch! Although opening another pull request is fine too at this point.

Welcome, and thanks for the pull request! Do be aware that documentation pull requests can attract a lot of comments so patience with the process is appreciated!