about summary refs log tree commit diff
path: root/src/libstd/panic.rs
diff options
context:
space:
mode:
authorSteve Klabnik <steve@steveklabnik.com>2016-02-09 16:58:59 -0500
committerSteve Klabnik <steve@steveklabnik.com>2016-02-09 16:58:59 -0500
commit6571ae28a81e899aeb3eae81ee26c3cf31fddd1c (patch)
treeabd0ca2173c4b034961d3a8e3b13eb2d604def4f /src/libstd/panic.rs
parente3bf4a74272c2072ad9567c5201c6514b9aff0fc (diff)
parent02aa0aff2f0b42368dd871186510493fa60d785a (diff)
downloadrust-6571ae28a81e899aeb3eae81ee26c3cf31fddd1c.tar.gz
rust-6571ae28a81e899aeb3eae81ee26c3cf31fddd1c.zip
Rollup merge of #31514 - cgar:spelling, r=alexcrichton
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