From c0c0252793b1c1bf4fb8814d6801610186906013 Mon Sep 17 00:00:00 2001 From: Marc Sugiyama Date: Tue, 18 Nov 2014 08:20:59 -0800 Subject: Update file.xml Fix grammatical errors in section on file:datasync/1 --- lib/kernel/doc/src/file.xml | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) (limited to 'lib/kernel/doc/src') diff --git a/lib/kernel/doc/src/file.xml b/lib/kernel/doc/src/file.xml index 1c03efe7fd..6976457897 100644 --- a/lib/kernel/doc/src/file.xml +++ b/lib/kernel/doc/src/file.xml @@ -1689,9 +1689,9 @@

Makes sure that any buffers kept by the operating system (not by the Erlang runtime system) are written to disk. In - many ways it's resembles fsync but it not requires to update - some of file's metadata such as the access time. On - some platforms, this function might have no effect.

+ many ways it resembles fsync but it does not update + some of the file's metadata such as the access time. On + some platforms this function has no effect.

Applications that access databases or log files often write a tiny data fragment (e.g., one line in a log file) and then call fsync() immediately in order to ensure that the written @@ -1699,11 +1699,11 @@ will always initiate two write operations: one for the newly written data and another one in order to update the modification time stored in the inode. If the modification time is not a part - of the transaction concept fdatasync() can be used to avoid + of the transaction concept, fdatasync() can be used to avoid unnecessary inode disk write operations.

-

Available only in some POSIX systems. This call results in a - call to fsync(), or has no effect, in systems not implementing - the fdatasync syscall.

+

Available only in some POSIX systems, this call results in a + call to fsync(), or has no effect in systems not implementing + the fdatasync() syscall.

 -- cgit v1.2.3