about summary refs log tree commit diff
diff options
context:
space:
mode:
authorIvan Tham <pickfire@riseup.net>2020-08-26 23:21:44 +0800
committerGitHub <noreply@github.com>2020-08-26 23:21:44 +0800
commit9ea45935728651e985d70649a476ad89d0bee15e (patch)
treea78a0083762a274dbf9b354835035df4f0f3c6a3
parent16d8d4b899c8f23456027d0baec6ed83d256507c (diff)
downloadrust-9ea45935728651e985d70649a476ad89d0bee15e.tar.gz
rust-9ea45935728651e985d70649a476ad89d0bee15e.zip
Use [xxx()] rather than the [xxx] function
Co-authored-by: Joshua Nelson <joshua@yottadb.com>
-rw-r--r--library/std/src/error.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/library/std/src/error.rs b/library/std/src/error.rs
index 9869ccec546..2c1aada8a4f 100644
--- a/library/std/src/error.rs
+++ b/library/std/src/error.rs
@@ -33,10 +33,10 @@ use crate::string;
 /// themselves through the [`Display`] and [`Debug`] traits, and may provide
 /// cause chain information:
 ///
-/// The [`Error::source`] method is generally used when errors cross
+/// [`Error::source()`] is generally used when errors cross
 /// "abstraction boundaries". If one module must report an error that is caused
 /// by an error from a lower-level module, it can allow accessing that error
-/// via the [`Error::source`] method. This makes it possible for the high-level
+/// via [`Error::source()`]. This makes it possible for the high-level
 /// module to provide its own errors while also revealing some of the
 /// implementation for debugging via [`Error::source`] chains.
 ///