X-Git-Url: https://git.kernel.dk/?a=blobdiff_plain;f=README;h=d566fae3de8526a8b5359a63d65e7a8e70833fc2;hb=5711325cbb37d10c21a6975d1f1ebea11799c05e;hp=2fecf0e020077eeed24300882e553e772de050bb;hpb=26dcc08452b18f72e404760d8dc3c0bc057dacbe;p=fio.git

diff --git a/README b/README
index 2fecf0e0..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.
@@ -72,6 +72,10 @@ in the body of the email. Archives can be found here:
 
 	http://www.spinics.net/lists/fio/
 
+or here:
+
+	https://lore.kernel.org/fio/
+
 and archives for the old list can be found here:
 
 	http://maillist.kernel.dk/fio-devel/