Merge tag 'debian/1.52.1+dfsg1-1_exp2' into proxmox/buster

[rustc.git] / src / doc / rustc-dev-guide / src / profiling / with_perf.md

diff --git a/src/doc/rustc-dev-guide/src/profiling/with_perf.md b/src/doc/rustc-dev-guide/src/profiling/with_perf.md
index 7a4c972f20829c23c8e33d695cf158423f5ae0e7..b383ec542b76097aa8e9d251c24fe464c0ef5fbe 100644 (file)
--- a/src/doc/rustc-dev-guide/src/profiling/with_perf.md
+++ b/src/doc/rustc-dev-guide/src/profiling/with_perf.md
@@ -150,7 +150,7 @@ the `cargo rustc` command, like so:
 
 ```bash
 touch src/lib.rs
-CARGO_INCREMENTAL=0 perf record -F99 --call-graph dwarf cargo rustc --profile check --lib -- -Zborrowck=mir
+CARGO_INCREMENTAL=0 perf record -F99 --call-graph dwarf cargo rustc --profile check --lib -- -Z borrowck=mir
 ```
 
 [pf]: https://github.com/nikomatsakis/perf-focus
@@ -241,7 +241,7 @@ Percentage : 0%
 
 Here we used the `..` operator to ask "how often do we have
 `do_mir_borrowck` on the stack and then, later, some function whose
-name begins with `rusc::traits`?" (basically, code in that module). It
+name begins with `rustc::traits`?" (basically, code in that module). It
 turns out the answer is "almost never" — only 12 samples fit that
 description (if you ever see *no* samples, that often indicates your
 query is messed up).