about summary refs log tree commit diff
path: root/library/std/src/panic.rs
diff options
context:
space:
mode:
authorAli Malik <mikli@amazon.com>2021-07-23 19:14:28 -0400
committerAli Malik <mikli@amazon.com>2021-07-29 01:15:20 -0400
commite43254aad1ea5758078ace51341f31071e1e61a8 (patch)
tree2dff253d1ded27a831d8ad773d5b0df8ae72666b /library/std/src/panic.rs
parent85237886df31ba237acd3b7912336704026813f5 (diff)
downloadrust-e43254aad1ea5758078ace51341f31071e1e61a8.tar.gz
rust-e43254aad1ea5758078ace51341f31071e1e61a8.zip
Fix may not to appropriate might not or must not
Diffstat (limited to 'library/std/src/panic.rs')
-rw-r--r--library/std/src/panic.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/library/std/src/panic.rs b/library/std/src/panic.rs
index 7bc987db881..8a6b68f5993 100644
--- a/library/std/src/panic.rs
+++ b/library/std/src/panic.rs
@@ -163,7 +163,7 @@ pub auto trait RefUnwindSafe {}
 /// When using [`catch_unwind`] it may be the case that some of the closed over
 /// variables are not unwind safe. For example if `&mut T` is captured the
 /// compiler will generate a warning indicating that it is not unwind safe. It
-/// may not be the case, however, that this is actually a problem due to the
+/// might not be the case, however, that this is actually a problem due to the
 /// specific usage of [`catch_unwind`] if unwind safety is specifically taken into
 /// account. This wrapper struct is useful for a quick and lightweight
 /// annotation that a variable is indeed unwind safe.
@@ -406,7 +406,7 @@ impl<S: Stream> Stream for AssertUnwindSafe<S> {
 ///
 /// # Notes
 ///
-/// Note that this function **may not catch all panics** in Rust. A panic in
+/// Note that this function **might not catch all panics** in Rust. A panic in
 /// Rust is not always implemented via unwinding, but can be implemented by
 /// aborting the process as well. This function *only* catches unwinding panics,
 /// not those that abort the process.