about summary refs log tree commit diff
path: root/src/libstd/thread
diff options
context:
space:
mode:
authorSebastian Dröge <sebastian@centricular.com>2017-11-02 18:29:52 +0200
committerSebastian Dröge <sebastian@centricular.com>2017-11-02 18:33:25 +0200
commit283b4a1b0bcf94fed0ebc3bfd84e87d17ca1b587 (patch)
treeda086c3ae6bb01ed2d9de921411058e184fe09ec /src/libstd/thread
parent568700097950cf66b09dfdf3d608d4f51e0f64ef (diff)
downloadrust-283b4a1b0bcf94fed0ebc3bfd84e87d17ca1b587.tar.gz
rust-283b4a1b0bcf94fed0ebc3bfd84e87d17ca1b587.zip
Use ` instead of ' for function names
Diffstat (limited to 'src/libstd/thread')
-rw-r--r--src/libstd/thread/mod.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/libstd/thread/mod.rs b/src/libstd/thread/mod.rs
index 8c60d9c7bf0..da5965d801c 100644
--- a/src/libstd/thread/mod.rs
+++ b/src/libstd/thread/mod.rs
@@ -27,9 +27,9 @@
 //! a thread will unwind the stack, running destructors and freeing
 //! owned resources. While not meant as a 'try/catch' mechanism, panics
 //! in Rust can nonetheless be caught with
-//! ['catch_unwind'](../../std/panic/fn.catch_unwind.html) and recovered
+//! [`catch_unwind`](../../std/panic/fn.catch_unwind.html) and recovered
 //! from, or alternatively be resumed with
-//! ['resume_unwind'](../../std/panic/fn.resume_unwind.html). If the panic
+//! [`resume_unwind`](../../std/panic/fn.resume_unwind.html). If the panic
 //! is not caught the thread will exit, but the panic may optionally be
 //! detected from a different thread with `join`. If the main thread panics
 //! without the panic being caught, the application will exit with a