---

yaml
---
r: 275003
b: refs/heads/stable
c: a8fd1bb
h: refs/heads/master
i:
  275001: 060e429
  274999: 34e63f7

Author: sandeep-datta

[refs]

@@ -29,7 +29,7 @@ refs/heads/tmp: e06d2ad9fcd5027bcaac5b08fc9aa39a49d0ecd3
 refs/tags/1.0.0-alpha.2: 4c705f6bc559886632d3871b04f58aab093bfa2f
 refs/tags/homu-tmp: c0221c8897db309a79990367476177b1230bb264
 refs/tags/1.0.0-beta: 8cbb92b53468ee2b0c2d3eeb8567005953d40828
-refs/heads/stable: 50d179e0624b74a68982d7002a497a7a3403d360
+refs/heads/stable: a8fd1bbd2f9511e9394fed1112c4ada186eb1b00
 refs/tags/1.0.0: 55bd4f8ff2b323f317ae89e254ce87162d52a375
 refs/tags/1.1.0: bc3c16f09287e5545c1d3f76b7abd54f2eca868b
 refs/tags/1.2.0: f557861f822c34f07270347b94b5280de20a597e

branches/stable/src/doc/book/ownership.md

@@ -171,10 +171,10 @@ v2.truncate(2);
 
 and `v1` were still accessible we'd end up with an invalid vector since it
 would not know that the heap data has been truncated. Now, the part of the
-vector `v1` on the stack does not agree with its corresponding part on the
+vector `v1` on the stack does not agree with the corresponding part on the
 heap. `v1` still thinks there are three elements in the vector and will
 happily let us access the non existent element `v1[2]` but as you might
-already know this is a recipe for disaster.
+already know this is a recipe for disaster (might lead to a segfault).
 
 This is why Rust forbids using `v` after we’ve done the move.