diff --git a/Project.toml b/Project.toml
index 9bed045637a..551e069b934 100644
--- a/Project.toml
+++ b/Project.toml
@@ -1,7 +1,7 @@
 name = "Trixi"
 uuid = "a7f1ee26-1774-49b1-8366-f1abc58fbfcb"
 authors = ["Michael Schlottke-Lakemper <m.schlottke-lakemper@hlrs.de>", "Gregor Gassner <ggassner@uni-koeln.de>", "Hendrik Ranocha <mail@ranocha.de>", "Andrew R. Winters <andrew.ross.winters@liu.se>", "Jesse Chan <jesse.chan@rice.edu>"]
-version = "0.6.10-pre"
+version = "0.6.11-pre"
 
 [deps]
 CodeTracking = "da1fd8a2-8d9e-5ec2-8556-3022fb5608a2"
diff --git a/docs/src/performance.md b/docs/src/performance.md
index 82d7f501f63..40970e58c5c 100644
--- a/docs/src/performance.md
+++ b/docs/src/performance.md
@@ -106,7 +106,22 @@ resulting performance improvements of Trixi.jl are given in the following blog p
 We use [PkgBenchmark.jl](https://github.com/JuliaCI/PkgBenchmark.jl) to provide a standard set of
 benchmarks for Trixi.jl. The relevant benchmark script is
 [benchmark/benchmarks.jl](https://github.com/trixi-framework/Trixi.jl/blob/main/benchmark/benchmarks.jl).
-You can run a standard set of benchmarks via
+To benchmark the changes made in a PR, please proceed as follows:
+
+1. Check out the latest `main` branch of your Trixi.jl development repository.
+2. Check out the latest development branch of your PR.
+3. Change your working directory to the `benchmark` directory of Trixi.jl.
+4. Execute `julia run_benchmarks.jl`.
+
+This will take some hours to complete and requires at least 8 GiB of RAM. When everything is finished, some
+output files will be created in the `benchmark` directory of Trixi.jl.
+
+!!! warning
+    Please note that the benchmark scripts use `--check-bounds=no` at the moment.
+    Thus, they will not work in any useful way for Julia v1.10 (and newer?), see
+    [Julia issue #50985](https://github.com/JuliaLang/julia/issues/50985).
+
+You can also run a standard set of benchmarks manually via
 ```julia
 julia> using PkgBenchmark, Trixi