From cb8fa3d493c3d48e60ba70c88df20dbd75b191bc Mon Sep 17 00:00:00 2001 From: Hyo-Kyung Lee Date: Wed, 10 Apr 2024 21:59:42 -0500 Subject: [PATCH] docs: change date to data close #208 --- release_docs/INSTALL_parallel | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/release_docs/INSTALL_parallel b/release_docs/INSTALL_parallel index 8dabf897324..856252654d5 100644 --- a/release_docs/INSTALL_parallel +++ b/release_docs/INSTALL_parallel @@ -202,7 +202,7 @@ Reference 1. POSIX Compliant. A good explanation is by Donald Lewin, After a write() to a regular file has successfully returned, any successful read() from each byte position on the file that was modified - by that write() will return the date that was written by the write(). A + by that write() will return the data that was written by the write(). A subsequent write() to the same byte will overwrite the file data. If a read() of a file data can be proven by any means [e.g., MPI_Barrier()] to occur after a write() of that data, it must reflect that write(),