---

yaml
---
r: 42191
b: refs/heads/master
c: f0c9927
h: refs/heads/master
i:
  42189: 8f24830
  42187: 2b5c9f2
  42183: 4e34942
  42175: 87683e3
v: v3

Author: brson

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: 5aacf791e88428d146ab296587ec5d710fdb83b2
+refs/heads/master: f0c9927c2672ed80deee8057d5e9c5caa6ce01a0
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: 2f46b763da2c098913884f101b6d71d69af41b49
 refs/heads/try: 3d5418789064fdb463e872a4e651af1c628a3650

trunk/doc/tutorial-borrowed-ptr.md

@@ -50,7 +50,7 @@ Suppose we wanted to write a procedure that computed the distance between any
 two points, no matter where they were stored. For example, we might like to
 compute the distance between `on_the_stack` and `shared_box`, or between
 `shared_box` and `unique_box`. One option is to define a function that takes
-two arguments of type `Point`—that is, it takes the points by value. But we
+two arguments of type `Point`—that is, it takes the points by value. But if we
 define it this way, calling the function will cause the points to be
 copied. For points, this is probably not so bad, but often copies are
 expensive. Worse, if the data type contains mutable fields, copying can change