Describe the default benchmark duration as an estimate

README.md

@@ -33,8 +33,9 @@ hyperfine 'sleep 0.3'
 ```
 
 Hyperfine will automatically determine the number of runs to perform for each command. By default,
-it will perform *at least* 10 benchmarking runs and measure for at least 3 seconds. To change this,
-you can use the `-r`/`--runs` option:
+it will perform *at least* 10 benchmarking runs and estimate a run count targeting roughly
+3 seconds, including shell overhead and preparation and conclusion commands. To set an exact
+number of runs, you can use the `-r`/`--runs` option:
 ```sh
 hyperfine --runs 5 'sleep 0.3'
 ```

doc/hyperfine.1

@@ -141,7 +141,7 @@ string '{\fIVAR\fP}' in each command by the current parameter value.
 .RS
 Example:
 .RS
-\fBhyperfine\fR \fB\-\-prepare\fR 'make clean' \fB\-P\fR threads 1 8 'make \-j {threads}'
+\fBhyperfine\fR \fB\-P\fR threads 1 8 'make \-j {threads}'
 .RE
 .RE
 .IP

src/cli.rs

@@ -161,7 +161,7 @@ fn build_command() -> Command {
                 .help(
                     "Perform benchmark runs for each value in the range MIN..MAX. Replaces the \
                      string '{VAR}' in each command by the current parameter value.\n\n  \
-                     Example:  hyperfine --prepare 'make clean' -P threads 1 8 'make -j {threads}'\n\n\
+                     Example:  hyperfine -P threads 1 8 'make -j {threads}'\n\n\
                      This performs benchmarks for 'make -j 1', 'make -j 2', …, 'make -j 8'.\n\n\
                      To have the value increase following different patterns, use shell arithmetics.\n\n  \
                      Example: hyperfine -P size 0 3 'sleep $((2**{size}))'\n\n\