about summary refs log tree commit diff
path: root/src/libstd/panic.rs
diff options
context:
space:
mode:
authorCarlos E. Garcia <carlos@cgarcia.org>2016-02-09 11:52:39 -0500
committerCarlos E. Garcia <carlos@cgarcia.org>2016-02-09 11:52:39 -0500
commit02aa0aff2f0b42368dd871186510493fa60d785a (patch)
tree9876ab46cee5b267ffcfd926f94ff75fc7273d36 /src/libstd/panic.rs
parent6630a0819553898c3fc0d060cc72a94d62ae1330 (diff)
downloadrust-02aa0aff2f0b42368dd871186510493fa60d785a.tar.gz
rust-02aa0aff2f0b42368dd871186510493fa60d785a.zip
Minor spelling fixes
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 3677bd27b16..83df54f1830 100644
--- a/src/libstd/panic.rs
+++ b/src/libstd/panic.rs
@@ -84,7 +84,7 @@ pub use panicking::{take_handler, set_handler, PanicInfo, Location};
 /// recover safe. The general idea is that any mutable state which can be shared
 /// across `recover` is not recover safe by default. This is because it is very
 /// easy to witness a broken invariant outside of `recover` as the data is
-/// simply accesed as usual.
+/// simply accessed as usual.
 ///
 /// Types like `&Mutex<T>`, however, are recover safe because they implement
 /// poisoning by default. They still allow witnessing a broken invariant, but