about summary refs log tree commit diff
diff options
context:
space:
mode:
authorSteve Klabnik <steve@steveklabnik.com>2014-10-27 15:51:17 -0400
committerSteve Klabnik <steve@steveklabnik.com>2014-10-27 15:51:52 -0400
commit13e4daee2665b893e2ec78b2eb77e0b18023f5d2 (patch)
tree8765c82f8ddf20a3e9bcc41ba04c634b2cdfcc3e
parente2cd4597dae1ed0aa3967bd2a656a42daa1ad27f (diff)
downloadrust-13e4daee2665b893e2ec78b2eb77e0b18023f5d2.tar.gz
rust-13e4daee2665b893e2ec78b2eb77e0b18023f5d2.zip
Fix some wording about errors
see https://github.com/rust-lang/rust/pull/18176#discussion_r19374679
-rw-r--r--src/doc/guide.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/guide.md b/src/doc/guide.md
index c7b8e42b28c..3941327f5f2 100644
--- a/src/doc/guide.md
+++ b/src/doc/guide.md
@@ -3510,8 +3510,8 @@ everyone plays by these rules. At compile time, it verifies that none of these
 rules are broken. If our program compiles successfully, Rust can guarantee it
 is free of data races and other memory errors, and there is no runtime overhead
 for any of this. The borrow checker works only at compile time. If the borrow
-checker did find a problem, it will report a **lifetime error**, and your
-program will refuse to compile.
+checker did find a problem, it will report an error and your program will
+refuse to compile.
 
 That's a lot to take in. It's also one of the _most_ important concepts in
 all of Rust. Let's see this syntax in action: