Minor wording improvement.

[pintos-anon] / doc / filesys.texi

diff --git a/doc/filesys.texi b/doc/filesys.texi
index db4d94810b63426f91ee03c6783bd63b5c1060be..744c0b28ee9bbc64e2b6ac552ece511243085e0d 100644 (file)
--- a/doc/filesys.texi
+++ b/doc/filesys.texi
@@ -96,9 +96,9 @@ system.
 The grading scripts check the file system's correctness based on the
 contents of the file copied out in the second run.  This means that your
 project will not pass any of the extended file system tests until the
-file system is implemented well enough to support @program{tar}, the
+file system is implemented well enough to support @command{tar}, the
 Pintos user program that produces the file that is copied out.  The
-@program{tar} program is fairly demanding (it requires both extensible
+@command{tar} program is fairly demanding (it requires both extensible
 file and subdirectory support), so this will take some work.  Until
 then, you can ignore errors from @command{make check} regarding the
 extracted file system.
@@ -259,8 +259,8 @@ false if it represents an ordinary file.
 @end deftypefn
 
 @deftypefn {System Call} int inumber (int @var{fd})
-Returns the @dfn{inode number} of the inode associated with @var{fd}.
-Applicable to file descriptors for both files and directories.
+Returns the @dfn{inode number} of the inode associated with @var{fd},
+which may represent an ordinary file or a directory.
 
 An inode number persistently identifies a file or directory.  It is
 unique during the file's existence.  In Pintos, the sector number of the