about summary refs log tree commit diff
path: root/src/libstd/panic.rs
diff options
context:
space:
mode:
authorGuillaume Gomez <guillaume1.gomez@gmail.com>2017-08-13 11:03:11 +0200
committerGitHub <noreply@github.com>2017-08-13 11:03:11 +0200
commitbc6659a8fef000c96665f6ba8d6ddcd1ef89623b (patch)
tree7887050320d236b12a5d5ec4e36eb535108ba922 /src/libstd/panic.rs
parent9191fe1ef4228ccfa6d573f9546f1e315b433960 (diff)
parent3ab86fbab281ca059731c31fa2aee5d9afc7e6dc (diff)
downloadrust-bc6659a8fef000c96665f6ba8d6ddcd1ef89623b.tar.gz
rust-bc6659a8fef000c96665f6ba8d6ddcd1ef89623b.zip
Rollup merge of #43814 - Eijebong:fix_typos2, r=petrochenkov
Fix some typos

Follow up of #43794

If refined my script a little bit and found some more.
Diffstat (limited to 'src/libstd/panic.rs')
-rw-r--r--src/libstd/panic.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libstd/panic.rs b/src/libstd/panic.rs
index 10b3209257e..97b09b7e2ad 100644
--- a/src/libstd/panic.rs
+++ b/src/libstd/panic.rs
@@ -37,7 +37,7 @@ pub use panicking::{take_hook, set_hook, PanicInfo, Location};
 /// In Rust a function can "return" early if it either panics or calls a
 /// function which transitively panics. This sort of control flow is not always
 /// anticipated, and has the possibility of causing subtle bugs through a
-/// combination of two criticial components:
+/// combination of two critical components:
 ///
 /// 1. A data structure is in a temporarily invalid state when the thread
 ///    panics.