about summary refs log tree commit diff
diff options
context:
space:
mode:
authorColin Wallace <wallacoloo@gmail.com>2015-09-19 17:19:29 -0700
committerColin Wallace <wallacoloo@gmail.com>2015-09-19 17:19:29 -0700
commita35f1b29d743a7d5cc50469818f7b994ed186903 (patch)
tree94e3b9f16226a12056e97693388808f1d3535ce3
parent783c3fcc1ec19a804a63334d1945301fe89c52f6 (diff)
downloadrust-a35f1b29d743a7d5cc50469818f7b994ed186903.tar.gz
rust-a35f1b29d743a7d5cc50469818f7b994ed186903.zip
Fix "more more" typo
-rw-r--r--src/doc/trpl/choosing-your-guarantees.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/trpl/choosing-your-guarantees.md b/src/doc/trpl/choosing-your-guarantees.md
index b86ad47feb2..f53ece1f2a7 100644
--- a/src/doc/trpl/choosing-your-guarantees.md
+++ b/src/doc/trpl/choosing-your-guarantees.md
@@ -321,7 +321,7 @@ there's a lot of concurrent access happening.
 
 # Composition
 
-A common gripe when reading Rust code is with types like `Rc<RefCell<Vec<T>>>` (or even more more
+A common gripe when reading Rust code is with types like `Rc<RefCell<Vec<T>>>` (or even more
 complicated compositions of such types). It's not always clear what the composition does, or why the
 author chose one like this (and when one should be using such a composition in one's own code)