From 33034bd67b33514368ddf73708830a1fb5e966f4 Mon Sep 17 00:00:00 2001 From: "Derek A. Kaplan" Date: Tue, 9 Jul 2024 23:32:01 -0400 Subject: [PATCH] Fix incorrect environment variable name --- docs/user-guide/src/verify/counterexample.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/user-guide/src/verify/counterexample.md b/docs/user-guide/src/verify/counterexample.md index 0bb75e49326..cf97015718d 100644 --- a/docs/user-guide/src/verify/counterexample.md +++ b/docs/user-guide/src/verify/counterexample.md @@ -1,7 +1,7 @@ # Printing Counterexamples Prusti can print counterexamples for verification failures, i.e., values for variables that violate some assertion or pre-/postcondition. -This can be enabled by setting [`counterexample = true`](https://viperproject.github.io/prusti-dev/dev-guide/config/flags.html#counterexample) in the `Prusti.toml` file, or with the `PRUSTI_COUNTEREXAMPLES=true` environment variable. +This can be enabled by setting [`counterexample = true`](https://viperproject.github.io/prusti-dev/dev-guide/config/flags.html#counterexample) in the `Prusti.toml` file, or with the `PRUSTI_COUNTEREXAMPLE=true` environment variable. For example: ```rust,noplaypen