README

@@ -36,12 +36,12 @@ where
  - <bytes per thread> is the number of bytes written and read per
    thread (task),
 
- - <directory> is the path to a directory on the filesystem being
+ - <directory> is the path to an empty directory on the filesystem being
    benchmarked.
 
 <threads per node> and <blocksize> will be chosen optimally for best
 performance.  <bytes per thread> will be chosen so that the write and
-read phases run for up to 60 minutes each.
+read phases run for at least 60 minutes each.
 
 Results will be evaluated by looking at the "WRITE" and "READ" sections
 in the table output from elbencho on stdout.  The row "Elapsed time" in
@@ -72,12 +72,12 @@ where
  - <bytes per thread> is the number of bytes written and read per
    thread (task),
 
- - <directory> is the path to a directory on the filesystem being
+ - <directory> is the path to an empty directory on the filesystem being
    benchmarked.
 
 <threads per node> will be chosen optimally for best performance.
 <bytes per thread> will be chosen so that the write and read phases runs
-for up to 60 minutes each.
+for at least 60 minutes each.
 
 Results will be evaluated by looking at the "WRITE" and "READ" sections
 in the table output from elbencho on stdout.  The row "Elapsed time" in
@@ -107,12 +107,12 @@ where
  - <files per thread> is the number of files created, stat, and deleted
    per thread (task),
 
- - <directory> is the path to a directory on the filesystem being
+ - <directory> is the path to an empty directory on the filesystem being
    benchmarked.
 
 <threads per node> will be chosen optimally for best performance.
 <number of files> will be chosen so that each phase; create, stat, and
-delete; runs for up to 60 minutes.
+delete; runs for at least 60 minutes.
 
 Results will be evaluated by looking at the "WRITE", "STAT", and
 "RMFILES" sections in the table output from elbencho on stdout.  The