From 32ef77f9ba6843348e57ce750d76a74d4cb43499 Mon Sep 17 00:00:00 2001
From: kushal Singh Rathore <54983775+kushalsingh-00@users.noreply.github.com>
Date: Mon, 7 Oct 2019 07:52:20 +0530
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index e82b128..285f932 100644
--- a/README.md
+++ b/README.md
@@ -145,8 +145,8 @@ update existing keys in the database.
 Each "op" above corresponds to a write of a single key/value pair.
 I.e., a random write benchmark goes at approximately 400,000 writes per second.
 
-Each "file sync" operation costs much less (0.3 milliseconds)
-then a disk seeks (typically 10 milliseconds).  We suspect that this is
+Each "fillsync" operation costs much less (0.3 milliseconds)
+then a disk seek (typically 10 milliseconds).  We suspect that this is
 because the hard disk itself is buffering the update in its memory and
 responding before the data has been written to the platter.  This may
 or may not be safe based on whether or not the hard disk has enough