about summary refs log tree commit diff
diff options
context:
space:
mode:
authorAlex Crichton <alex@alexcrichton.com>2015-01-07 17:18:05 -0800
committerAlex Crichton <alex@alexcrichton.com>2015-01-07 17:18:05 -0800
commit5d342acba2307ac3b141f19da0caae7406fc7664 (patch)
tree0b932239e9dd857f6100221531f3677a12ccd6b9
parentdd38f46d71872fba50833fd22313ef49eb01d079 (diff)
parent9fcf097648664224fa286804617788b4a974ba36 (diff)
downloadrust-5d342acba2307ac3b141f19da0caae7406fc7664.tar.gz
rust-5d342acba2307ac3b141f19da0caae7406fc7664.zip
rollup merge of #20709: thiagopnts/ownership-guide-typo
I was reading the ownership guide and found this small typo :bowtie:
-rw-r--r--src/doc/guide-ownership.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/guide-ownership.md b/src/doc/guide-ownership.md
index 414a874082e..939712da37a 100644
--- a/src/doc/guide-ownership.md
+++ b/src/doc/guide-ownership.md
@@ -458,7 +458,7 @@ lifetime, and so if you elide a lifetime (like `&T` instead of `&'a T`), Rust
 will do three things to determine what those lifetimes should be.
 
 When talking about lifetime elision, we use the term 'input lifetime' and
-'output lifetime'. An 'input liftime' is a lifetime associated with a parameter
+'output lifetime'. An 'input lifetime' is a lifetime associated with a parameter
 of a function, and an 'output lifetime' is a lifetime associated with the return
 value of a function. For example, this function has an input lifetime: