about summary refs log tree commit diff
diff options
context:
space:
mode:
authorJ. Frimmel <31166235+jfrimmel@users.noreply.github.com>2021-03-18 21:15:19 +0100
committerGitHub <noreply@github.com>2021-03-18 21:15:19 +0100
commit19bd0669b45fcc5ce81b8003cafccf318c3cc22e (patch)
treef05bc78ac2671cd360c3649e1bf7efaa0f01f815
parentd5e45b50cdfc029a061229d9edf5f5fa58eb0353 (diff)
downloadrust-19bd0669b45fcc5ce81b8003cafccf318c3cc22e.tar.gz
rust-19bd0669b45fcc5ce81b8003cafccf318c3cc22e.zip
Apply suggestions from code review
Co-authored-by: Josh Triplett <josh@joshtriplett.org>
-rw-r--r--library/core/src/macros/panic.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/library/core/src/macros/panic.md b/library/core/src/macros/panic.md
index e59be12a689..5127a16bbfd 100644
--- a/library/core/src/macros/panic.md
+++ b/library/core/src/macros/panic.md
@@ -13,11 +13,11 @@ When using `panic!()` you can specify a string payload, that is built using
 the [`format!`] syntax. That payload is used when injecting the panic into
 the calling Rust thread, causing the thread to panic entirely.
 
-The behavior of the default `std` hook, i.e. the code, that runs directy
-after the panic is invoked, is to print the message payload to the
+The behavior of the default `std` hook, i.e. the code that runs directly
+after the panic is invoked, is to print the message payload to
 `stderr` along with the file/line/column information of the `panic!()`
 call. You can override the panic hook using [`std::panic::set_hook()`].
-Inside the hook a panic can be accessed as a `&dyn Any + Send`, which
+Inside the hook a panic can be accessed as a `&dyn Any + Send`,
 which contains either a `&str` or `String` for regular `panic!()` invocations.
 To panic with a value of another other type, [`panic_any`] can be used.