about summary refs log tree commit diff
diff options
context:
space:
mode:
authorRalf Jung <post@ralfj.de>2023-03-12 22:23:09 +0100
committerGitHub <noreply@github.com>2023-03-12 22:23:09 +0100
commitd3ce3de68c6a4d9db362f4128e8e544516f9d315 (patch)
treea6f1b1c1a020394e6035bb860bb2afd537035d2c
parent14541044dbfa3593acfcf4861af28b9e8f1f84e7 (diff)
downloadrust-d3ce3de68c6a4d9db362f4128e8e544516f9d315.tar.gz
rust-d3ce3de68c6a4d9db362f4128e8e544516f9d315.zip
tweak readme
-rw-r--r--src/tools/miri/README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/tools/miri/README.md b/src/tools/miri/README.md
index 93e00cca117..f0b73d05873 100644
--- a/src/tools/miri/README.md
+++ b/src/tools/miri/README.md
@@ -235,9 +235,9 @@ inherent interpreter slowdown and a loss of parallelism.
 You can get your test suite's parallelism back by running `cargo miri nextest run -jN`
 (note that you will need [`cargo-nextest`](https://nexte.st) installed).
 This works because `cargo-nextest` collects a list of all tests then launches a
-separate `cargo miri run` for each test. You will need to specify a `-j` or `--test-threads`,
-by default `cargo miri nextest run` runs one test at a time. You can find the `cargo-nextest`
-documentation for its Miri support here: https://nexte.st/book/miri.html
+separate `cargo miri run` for each test. You will need to specify a `-j` or `--test-threads`;
+by default `cargo miri nextest run` runs one test at a time. For more details, see the
+[`cargo-nextest` Miri documentation](https://nexte.st/book/miri.html).
 
 Note: This one-test-per-process model means that `cargo miri test` is able to detect data
 races where two tests race on a shared resource, but `cargo miri nextest run` will not detect