about summary refs log tree commit diff
path: root/src/doc
diff options
context:
space:
mode:
authorAlex Crichton <alex@alexcrichton.com>2014-12-30 16:26:20 -0800
committerAlex Crichton <alex@alexcrichton.com>2014-12-30 16:26:20 -0800
commit86a03b86852434d0db818da936e667a50be19e8e (patch)
tree8781fad1f2789ecc8f0e0649639c6181e15b3b64 /src/doc
parentfa130ae6ffa8d0923567d1359ec0a76a87bc9978 (diff)
parent42ae6bb24d9ce6328d5c448a3b6797d12498bd82 (diff)
rollup merge of #20332: js-ojus/master
In the context of explaining the declaration of mutable bindings, using 'intended' probably conveys the meaning better than 'cared'.
Diffstat (limited to 'src/doc')
-rw-r--r--src/doc/guide.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/guide.md b/src/doc/guide.md
index 99ecd454fd7..fe65f4bd7f5 100644
--- a/src/doc/guide.md
+++ b/src/doc/guide.md
@@ -460,7 +460,7 @@ x = 10i;
 There is no single reason that bindings are immutable by default, but we can
 think about it through one of Rust's primary focuses: safety. If you forget to
 say `mut`, the compiler will catch it, and let you know that you have mutated
-something you may not have cared to mutate. If bindings were mutable by
+something you may not have intended to mutate. If bindings were mutable by
 default, the compiler would not be able to tell you this. If you _did_ intend
 mutation, then the solution is quite easy: add `mut`.