diff --git a/src/appendix-stupid-stats.md b/src/appendix-stupid-stats.md
index 9b7d9812b..842a2a328 100644
--- a/src/appendix-stupid-stats.md
+++ b/src/appendix-stupid-stats.md
@@ -113,7 +113,7 @@ between phases.
 `CompilerCalls` is a trait that you implement in your tool. It contains a fairly
 ad-hoc set of methods to hook in to the process of processing command line
 arguments and driving the compiler. For details, see the comments in
-[librustc_driver/lib.rs](https://github.com/rust-lang/rust/tree/master/src/librustc_driver/lib.rs).
+[librustc_driver/lib.rs](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_driver/index.html).
 I'll summarise the methods here.
 
 `early_callback` and `late_callback` let you call arbitrary code at different
diff --git a/src/const-eval.md b/src/const-eval.md
index 4a05255c6..70c946f17 100644
--- a/src/const-eval.md
+++ b/src/const-eval.md
@@ -35,4 +35,4 @@ integer or fat pointer, it will directly yield the value (via `Value::ByVal` or
 memory allocation (via `Value::ByRef`). This means that the `const_eval`
 function cannot be used to create miri-pointers to the evaluated constant or
 static. If you need that, you need to directly work with the functions in
-[src/librustc_mir/interpret/const_eval.rs](https://github.com/rust-lang/rust/blob/master/src/librustc_mir/interpret/const_eval.rs).
+[src/librustc_mir/interpret/const_eval.rs](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_mir/interpret/const_eval/).
diff --git a/src/method-lookup.md b/src/method-lookup.md
index a3d8dca29..5aafb6abf 100644
--- a/src/method-lookup.md
+++ b/src/method-lookup.md
@@ -38,8 +38,8 @@ cacheable across method-call sites. Therefore, it does not include
 inference variables or other information.
 
 [UFCS]: https://github.com/rust-lang/rfcs/blob/master/text/0132-ufcs.md
-[probe]: https://github.com/rust-lang/rust/blob/master/src/librustc_typeck/check/method/probe.rs
-[confirm]: https://github.com/rust-lang/rust/blob/master/src/librustc_typeck/check/method/confirm.rs
+[probe]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_typeck/check/method/probe/
+[confirm]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_typeck/check/method/confirm/
 
 ## The Probe phase
 
diff --git a/src/miri.md b/src/miri.md
index fb6675f50..be9587408 100644
--- a/src/miri.md
+++ b/src/miri.md
@@ -112,7 +112,7 @@ to a pointer to `b`.
 
 Although the main entry point to constant evaluation is the `tcx.const_eval`
 query, there are additional functions in
-[librustc_mir/interpret/const_eval.rs](https://github.com/rust-lang/rust/blob/master/src/librustc_mir/interpret/const_eval.rs)
+[librustc_mir/interpret/const_eval.rs](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_mir/interpret/const_eval/)
 that allow accessing the fields of a `Value` (`ByRef` or otherwise). You should
 never have to access an `Allocation` directly except for translating it to the
 compilation target (at the moment just LLVM).
diff --git a/src/type-checking.md b/src/type-checking.md
index cca032e30..cb6d346e4 100644
--- a/src/type-checking.md
+++ b/src/type-checking.md
@@ -39,6 +39,6 @@ type *checking*).
 For more details, see the [`collect`][collect] module.
 
 [queries]: query.html
-[collect]: https://github.com/rust-lang/rust/blob/master/src/librustc_typeck/collect.rs
+[collect]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_typeck/collect/
 
 **TODO**: actually talk about type checking...