Revert "ci: temporarily remove linux-i686-gcc build"

[fio.git] / README

diff --git a/README b/README
index 52eca5c39e7fa08fffd994fe47fd8b90d215b3dc..d566fae3de8526a8b5359a63d65e7a8e70833fc2 100644 (file)
--- 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.