X-Git-Url: https://git.kernel.dk/?a=blobdiff_plain;f=README;h=d566fae3de8526a8b5359a63d65e7a8e70833fc2;hb=2fe224d8b49e759138fa68b519161257dc1ce600;hp=52eca5c39e7fa08fffd994fe47fd8b90d215b3dc;hpb=d7521682c30eea3cb09a2d064c3fc0e35e752442;p=fio.git

diff --git a/README b/README
index 52eca5c3..d566fae3 100644
--- a/README
+++ b/README
@@ -10,7 +10,7 @@ tailored test case again and again.
 
 A test work load is difficult to define, though. There can be any number of
 processes or threads involved, and they can each be using their own way of
-generating I/O. You could have someone dirtying large amounts of memory in an
+generating I/O. You could have someone dirtying large amounts of memory in a
 memory mapped file, or maybe several threads issuing reads using asynchronous
 I/O. fio needed to be flexible enough to simulate both of these cases, and many
 more.