diff options
| author | Jonathan Reem <jonathan.reem@gmail.com> | 2014-06-04 22:27:21 -0700 |
|---|---|---|
| committer | Jonathan Reem <jonathan.reem@gmail.com> | 2014-06-04 22:27:21 -0700 |
| commit | 7e0cc34d629937e739ebf4404e5fe99c70d4b364 (patch) | |
| tree | 97c53beac88ec72b0698453cd17ef28c1bbec89f | |
| parent | 193574ae1e3881f95afb8b3e385a9e410ac6798a (diff) | |
Fixed weird grammar in lifetimes guide.
| -rw-r--r-- | src/doc/guide-lifetimes.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/src/doc/guide-lifetimes.md b/src/doc/guide-lifetimes.md index 2f519306dfd..65f37031674 100644 --- a/src/doc/guide-lifetimes.md +++ b/src/doc/guide-lifetimes.md @@ -14,9 +14,9 @@ Despite their complete safety, a reference's representation at runtime is the same as that of an ordinary pointer in a C program. They introduce zero overhead. The compiler does all safety checks at compile time. -Although references have rather elaborate theoretical underpinnings usually -introduced as (e.g. region pointers), the core concepts will be familiar to -anyone who has worked with C or C++. The best way to explain how they are +Although references have rather elaborate theoretical underpinnings +(e.g. region pointers), the core concepts will be familiar to anyone +who has worked with C or C++. The best way to explain how they are used—and their limitations—is probably just to work through several examples. # By example |
