about summary refs log tree commit diff
path: root/src
diff options
context:
space:
mode:
authorKillTheMule <github@pipsfrank.de>2016-10-06 11:53:53 +0200
committerGitHub <noreply@github.com>2016-10-06 11:53:53 +0200
commit2a0bd6db856929315876b2b875e5fcf22832ff58 (patch)
treef81cd86a34d22d642f4fad584bd053c4588e3d3d /src
parenta54230239310ab5a20b1c23fd4341b938d0fd2a4 (diff)
downloadrust-2a0bd6db856929315876b2b875e5fcf22832ff58.tar.gz
rust-2a0bd6db856929315876b2b875e5fcf22832ff58.zip
Typos
Diffstat (limited to 'src')
-rw-r--r--src/doc/book/lifetimes.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/doc/book/lifetimes.md b/src/doc/book/lifetimes.md
index 9d30aa85f3f..652ed9d2f73 100644
--- a/src/doc/book/lifetimes.md
+++ b/src/doc/book/lifetimes.md
@@ -56,7 +56,7 @@ To fix this, we have to make sure that step four never happens after step
 three. The ownership system in Rust does this through a concept called
 lifetimes, which describe the scope that a reference is valid for.
 
-**Note** It's important to understand that lifetime annotations are _descriptive_ not _prescriptive_. This means that who long a reference is valid  is determined by the code, not by the annotations. The annotations, however, point out this fact to the compiler in case it can't figure it out by itself.
+**Note** It's important to understand that lifetime annotations are _descriptive_, not _prescriptive_. This means that how long a reference is valid  is determined by the code, not by the annotations. The annotations, however, point out this fact to the compiler in case it can't figure it out by itself.
 
 When we have a function that takes an argument by reference, we can be
 implicit or explicit about the lifetime of the reference: