---

yaml
---
r: 118585
b: refs/heads/try
c: ebac770
h: refs/heads/master
i:
  118583: 77b6a70
v: v3

Author: alexcrichton

[refs]

@@ -2,7 +2,7 @@
 refs/heads/master: b1646cbfd908dc948b251e362669af421100647a
 refs/heads/snap-stage1: e33de59e47c5076a89eadeb38f4934f58a3618a6
 refs/heads/snap-stage3: d6736a1440d42f6af967a8a20ab8d73522112b72
-refs/heads/try: accb442b38cb5e7f64ed80199ce5d77f3e4c4dd7
+refs/heads/try: ebac770abb529ebdd1b9de830ee82069d4f754da
 refs/tags/release-0.1: 1f5c5126e96c79d22cb7862f75304136e204f105
 refs/heads/ndm: f3868061cd7988080c30d6d5bf352a5a5fe2460b
 refs/heads/try2: 147ecfdd8221e4a4d4e090486829a06da1e0ca3c

branches/try/src/doc/complement-design-faq.md

@@ -115,10 +115,10 @@ rationale and discussion.
 
 ## No guaranteed tail-call optimization
 
-In general, tail-call optimization is not guaranteed: see for a detailed
-explanation with references. There is a [proposed extension][tce] that would
-allow tail-call elimination in certain contexts. The compiler is still free to
-optimize tail-calls [when it pleases][sco], however.
+In general, tail-call optimization is not guaranteed: see [here][tml] for a
+detailed explanation with references. There is a [proposed extension][tce] that
+would allow tail-call elimination in certain contexts. The compiler is still
+free to optimize tail-calls [when it pleases][sco], however.
 
 [tml]: https://mail.mozilla.org/pipermail/rust-dev/2013-April/003557.html
 [sco]: http://llvm.org/docs/CodeGenerator.html#sibling-call-optimization