about summary refs log tree commit diff
path: root/src/libcore
diff options
context:
space:
mode:
authorManish Goregaokar <manishsmail@gmail.com>2016-01-14 19:12:29 +0530
committerManish Goregaokar <manishsmail@gmail.com>2016-01-14 19:12:29 +0530
commit92aa3269203976cc01ee9d2ec8bc686076d37b48 (patch)
tree62ead784280833d75242cce7dc3d14357bfa7ec7 /src/libcore
parentf28a43102b078c5dee78ba5cbbcbb0350cd92330 (diff)
parent01cbdf4481915948773a8abfb67bcc1a44571dab (diff)
Rollup merge of #30886 - ollie27:docs_links, r=steveklabnik
r? @steveklabnik
Diffstat (limited to 'src/libcore')
-rw-r--r--src/libcore/iter.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libcore/iter.rs b/src/libcore/iter.rs
index c3bea050558..e3e783329ec 100644
--- a/src/libcore/iter.rs
+++ b/src/libcore/iter.rs
@@ -1358,7 +1358,7 @@ pub trait Iterator {
     /// One of the keys to `collect()`'s power is that many things you might
     /// not think of as 'collections' actually are. For example, a [`String`]
     /// is a collection of [`char`]s. And a collection of [`Result<T, E>`] can
-    /// be thought of as single [`Result<Collection<T>, E>`]. See the examples
+    /// be thought of as single `Result<Collection<T>, E>`. See the examples
     /// below for more.
     ///
     /// [`String`]: ../string/struct.String.html