---

yaml
---
r: 42857
b: refs/heads/try
c: f0c9927
h: refs/heads/master
i:
  42855: 8d899bf
v: v3

Author: brson

[refs]

@@ -2,7 +2,7 @@
 refs/heads/master: 19dfec2aaf746535de1521f68421f9980dbf25de
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: 2f46b763da2c098913884f101b6d71d69af41b49
-refs/heads/try: 5aacf791e88428d146ab296587ec5d710fdb83b2
+refs/heads/try: f0c9927c2672ed80deee8057d5e9c5caa6ce01a0
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: a810c03263670238bccd64cabb12a23a46e3a278

branches/try/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