From ce6c8344d62719bc93e45ae8ad404e75f606467e Mon Sep 17 00:00:00 2001
From: Russell Davis <551404+russelldavis@users.noreply.github.com>
Date: Tue, 21 May 2019 08:38:37 -0700
Subject: [PATCH] Fix usage of the word "elision"

This seems to have been written with the notion that "elide" means
"infer" or "emit" rather than the actual meaning of "omit".
---
 src/scope/lifetime/elision.md | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/src/scope/lifetime/elision.md b/src/scope/lifetime/elision.md
index 9a7204b25d..d1897e7e62 100644
--- a/src/scope/lifetime/elision.md
+++ b/src/scope/lifetime/elision.md
@@ -1,16 +1,16 @@
 # Elision
 
 Some lifetime patterns are overwhelmingly common and so the borrow checker
-will implicitly add them to save typing and to improve readability.
-This process of implicit addition is called elision. Elision exists in Rust
-solely because these patterns are common.
+will allow you to omit them to save typing and to improve readability.
+This is known as elision. Elision exists in Rust solely because these patterns
+are common.
 
 The following code shows a few examples of elision. For a more comprehensive
 description of elision, see [lifetime elision][elision] in the book.
 
 ```rust,editable
 // `elided_input` and `annotated_input` essentially have identical signatures
-// because the lifetime of `elided_input` is elided by the compiler:
+// because the lifetime of `elided_input` is inferred by the compiler:
 fn elided_input(x: &i32) {
     println!("`elided_input`: {}", x);
 }