---

yaml
---
r: 135750
b: refs/heads/auto
c: e382802
h: refs/heads/master
v: v3

Author: Keegan McAllister

[refs]

@@ -13,7 +13,7 @@ refs/heads/try3: 9387340aab40a73e8424c48fd42f0c521a4875c0
 refs/tags/release-0.3.1: 495bae036dfe5ec6ceafd3312b4dca48741e845b
 refs/tags/release-0.4: e828ea2080499553b97dfe33b3f4d472b4562ad7
 refs/tags/release-0.5: 7e3bcfbf21278251ee936ad53e92e9b719702d73
-refs/heads/auto: 4ced7a9637c10196883733fa81ac67d02269a76e
+refs/heads/auto: e3828026d5d037c49cc982ecf4fbe97a8f8fb7e1
 refs/heads/servo: af82457af293e2a842ba6b7759b70288da276167
 refs/tags/release-0.6: b4ebcfa1812664df5e142f0134a5faea3918544c
 refs/tags/0.1: b19db808c2793fe2976759b85a355c3ad8c8b336

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

@@ -39,7 +39,7 @@ representation as a primitive. This allows using Rust `enum`s in FFI where C
 `enum`s are also used, for most use cases. The attribute can also be applied
 to `struct`s to get the same layout as a C struct would.
 
-[repr]: http://doc.rust-lang.org/rust.html#miscellaneous-attributes
+[repr]: rust.html#miscellaneous-attributes
 
 ## There is no GC
 
@@ -56,7 +56,7 @@ Types which are [`Sync`][sync] are thread-safe when multiple shared
 references to them are used concurrently. Types which are not `Sync` are not
 thread-safe, and thus when used in a global require unsafe code to use.
 
-[sync]: http://doc.rust-lang.org/core/kinds/trait.Sync.html
+[sync]: core/kinds/trait.Sync.html
 
 ### If mutable static items that implement `Sync` are safe, why is taking &mut SHARABLE unsafe?
 
@@ -139,8 +139,8 @@ and explicitly calling the `clone` method. Making user-defined copy operators
 explicit surfaces the underlying complexity, forcing the developer to opt-in
 to potentially expensive operations.
 
-[copy]: http://doc.rust-lang.org/core/kinds/trait.Copy.html
-[clone]: http://doc.rust-lang.org/core/clone/trait.Clone.html
+[copy]: core/kinds/trait.Copy.html
+[clone]: core/clone/trait.Clone.html
 
 ## No move constructors
 

branches/auto/src/doc/guide.md

@@ -1843,9 +1843,9 @@ that page, but the best part is the search bar. Right up at the top, there's
 a box that you can enter in a search term. The search is pretty primitive
 right now, but is getting better all the time. If you type 'random' in that
 box, the page will update to [this
-one](http://doc.rust-lang.org/std/index.html?search=random). The very first
+one](std/index.html?search=random). The very first
 result is a link to
-[std::rand::random](http://doc.rust-lang.org/std/rand/fn.random.html). If we
+[std::rand::random](std/rand/fn.random.html). If we
 click on that result, we'll be taken to its documentation page.
 
 This page shows us a few things: the type signature of the function, some
@@ -3723,7 +3723,7 @@ If you use `Rc<T>` or `Arc<T>`, you have to be careful about introducing
 cycles. If you have two `Rc<T>`s that point to each other, the reference counts
 will never drop to zero, and you'll have a memory leak. To learn more, check
 out [the section on `Rc<T>` and `Arc<T>` in the pointers
-guide](http://doc.rust-lang.org/guide-pointers.html#rc-and-arc).
+guide](guide-pointers.html#rc-and-arc).
 
 # Patterns
 
@@ -5336,6 +5336,6 @@ you will have a firm grasp of basic Rust development. There's a whole lot more
 out there, we've just covered the surface. There's tons of topics that you can
 dig deeper into, and we've built specialized guides for many of them. To learn
 more, dig into the [full documentation
-index](http://doc.rust-lang.org/index.html).
+index](index.html).
 
 Happy hacking!