about summary refs log tree commit diff
diff options
context:
space:
mode:
authorJONNALAGADDA Srinivas <js@ojuslabs.com>2014-12-30 19:23:16 +0530
committerJONNALAGADDA Srinivas <js@ojuslabs.com>2014-12-30 19:23:16 +0530
commit42ae6bb24d9ce6328d5c448a3b6797d12498bd82 (patch)
treecb560d124b49b135ef09a4c63a30170e37da74b0
parentd2368c3c11ddab9d812c4ddec2e44579326ad347 (diff)
downloadrust-42ae6bb24d9ce6328d5c448a3b6797d12498bd82.tar.gz
rust-42ae6bb24d9ce6328d5c448a3b6797d12498bd82.zip
Minor change to wording in `Variables and Bindings`
In the context of explaining the declaration of mutable bindings, using 'intended' probably conveys the meaning better than 'cared'.
-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 d094c47da93..1d3736dd308 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`.