fanotify_init.2, fanotify_mark.2, fanotify.7: Minor tweak: s/object/filesystem object/

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man2/fanotify_init.2

@@ -97,7 +97,7 @@ example.
 .BR FAN_REPORT_FID " (since Linux 5.1)"
 .\" commit a8b13aa20afb69161b5123b4f1acc7ea0a03d360
 This value allows the receipt of events which contain additional information
-about the underlying object correlated to an event.
+about the underlying filesystem object correlated to an event.
 An additional structure encapsulates the information about the object and is
 included alongside the generic event metadata structure.
 The file descriptor that is used to represent the object correlated to an

man2/fanotify_mark.2

@@ -396,7 +396,7 @@ and
 do not specify a directory.
 .TP
 .B EXDEV
-The object indicated by
+The filesystem object indicated by
 .I pathname
 resides within a filesystem subvolume (e.g.,
 .BR btrfs (5))
@@ -410,7 +410,7 @@ has been created with
 .BR FAN_REPORT_FID .
 .TP
 .B ENODEV
-The object indicated by
+The filesystem object indicated by
 .I pathname
 is not associated with a filesystem that supports
 .I fsid

man7/fanotify.7

@@ -696,7 +696,8 @@ The second program (fanotify_fid.c) is an example of fanotify being used
 with
 .B FAN_REPORT_FID
 enabled.
-It attempts to mark the object that is passed as a command-line argument
+It attempts to mark the filesystem object that is passed as
+a command-line argument
 and waits until an event of type
 .B FAN_CREATE
 has occurred.