Fix documentation links to BufReader

Author: bushrat011899

library/alloc/src/io/read.rs

@@ -22,10 +22,11 @@ use crate::vec::Vec;
 /// trait.
 ///
 /// Please note that each call to [`read()`] may involve a system call, and
-/// `BufReader`, will be more efficient.
 /// therefore, using something that implements [`BufRead`], such as
+/// [`BufReader`], will be more efficient.
 ///
 /// [`BufRead`]: crate::io::BufRead
+/// [`BufReader`]: crate::io::BufReader
 ///
 /// Repeated calls to the reader use the same cursor, so for example
 /// calling `read_to_end` twice on a `File` will only return the file's
@@ -482,7 +483,9 @@ pub trait Read {
     ///
     /// The default implementation calls `read` for each byte,
     /// which can be very inefficient for data that's not in memory,
-    /// such as `File`. Consider using a `BufReader` in such cases.
+    /// such as `File`. Consider using a [`BufReader`] in such cases.
+    ///
+    /// [`BufReader`]: crate::io::BufReader
     ///
     /// # Examples
     ///