summaryrefslogtreecommitdiffstats
path: root/lib/libc/sys/madvise.2
diff options
context:
space:
mode:
authorru <ru@FreeBSD.org>2002-12-12 17:26:04 +0000
committerru <ru@FreeBSD.org>2002-12-12 17:26:04 +0000
commit041d1287e88250bf06ad159c6c696bd653a77957 (patch)
tree8a8960200349aa661a39654202f6e0adc5e7360e /lib/libc/sys/madvise.2
parent719bf117173e17f5286b995c031a11d553149e50 (diff)
downloadFreeBSD-src-041d1287e88250bf06ad159c6c696bd653a77957.zip
FreeBSD-src-041d1287e88250bf06ad159c6c696bd653a77957.tar.gz
Uniformly refer to a file system as "file system".
Approved by: re
Diffstat (limited to 'lib/libc/sys/madvise.2')
-rw-r--r--lib/libc/sys/madvise.24
1 files changed, 2 insertions, 2 deletions
diff --git a/lib/libc/sys/madvise.2 b/lib/libc/sys/madvise.2
index 8f19270..2260a7d 100644
--- a/lib/libc/sys/madvise.2
+++ b/lib/libc/sys/madvise.2
@@ -104,8 +104,8 @@ modified again.
.It Dv MADV_NOSYNC
Request that the system not flush the data associated with this map to
physical backing store unless it needs to. Typically this prevents the
-filesystem update daemon from gratuitously writing pages dirtied
-by the VM system to physical disk. Note that VM/filesystem coherency is
+file system update daemon from gratuitously writing pages dirtied
+by the VM system to physical disk. Note that VM/file system coherency is
always maintained, this feature simply ensures that the mapped data is
only flush when it needs to be, usually by the system pager.
.Pp
OpenPOWER on IntegriCloud