---

yaml
---
r: 89945
b: refs/heads/master
c: aa9efa1
h: refs/heads/master
i:
  89943: 4b02a5e
v: v3

Author: idupree

[refs]

@@ -1,5 +1,5 @@
 ---
-refs/heads/master: 760942d7d2a0701f526a5bc634419df7a1e941fe
+refs/heads/master: aa9efa1f7ac0f3fa25bcd76646b9ab37db9ba814
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: a6d3e57dca68fde4effdda3e4ae2887aa535fcd6
 refs/heads/try: b160761e35efcd1207112b3b782c06633cf441a8

trunk/doc/rust.md

@@ -3162,7 +3162,7 @@ Borrowed pointers (`&`)
     Borrowed pointers arise by (automatic) conversion from owning pointers, managed pointers,
     or by applying the borrowing operator `&` to some other value,
     including [lvalues, rvalues or temporaries](#lvalues-rvalues-and-temporaries).
-    Borrowed pointers are written `&content`, or in some cases `&f/content` for some lifetime-variable `f`,
+    Borrowed pointers are written `&content`, or in some cases `&'f content` for some lifetime-variable `f`,
     for example `&int` means a borrowed pointer to an integer.
     Copying a borrowed pointer is a "shallow" operation:
     it involves only copying the pointer itself.