rust-lang.github.io/rustc-dev-guide -> rustc-dev-guide.rust-lang.org

Author: spastorino

README.md

@@ -6,7 +6,7 @@ works. The aim of the guide is to help new contributors get oriented
 to rustc, as well as to help more experienced folks in figuring out
 some new part of the compiler that they haven't worked on before.
 
-[You can read the latest version of the guide here.](https://rust-lang.github.io/rustc-dev-guide/)
+[You can read the latest version of the guide here.](https://rustc-dev-guide.rust-lang.org/)
 
 You may also find the rustdocs [for the compiler itself][rustdocs] useful.
 

src/implementing_new_features.md

@@ -106,8 +106,8 @@ for stabilization in a checklist, e.g.,
 
 - [ ] Implement the RFC. (CC @rust-lang/compiler -- can anyone write
       up mentoring instructions?)
-- [ ] Adjust the documentation. ([See instructions on rustc-dev-guide.](https://rust-lang.github.io/rustc-dev-guide/stabilization_guide.html#documentation-prs))
-- [ ] Stabilize the feature. ([See instructions on rustc-dev-guide.](https://rust-lang.github.io/rustc-dev-guide/stabilization_guide.html#stabilization-pr))
+- [ ] Adjust the documentation. ([See instructions on rustc-dev-guide.](https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs))
+- [ ] Stabilize the feature. ([See instructions on rustc-dev-guide.](https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr))
 ```
 
 <a name="stability-in-code"></a>

src/mir/optimizations.md

@@ -8,8 +8,8 @@ to do, so compilation is faster. Note that since MIR is generic (not
 effective; we can optimize the generic version, so all of the monomorphizations
 are cheaper!
 
-[mir]: https://rust-lang.github.io/rustc-dev-guide/mir/index.html
-[monomorph]: https://rust-lang.github.io/rustc-dev-guide/appendix/glossary.html?highlight=monomorphize#appendix-c-glossary
+[mir]: https://rustc-dev-guide.rust-lang.org/mir/index.html
+[monomorph]: https://rustc-dev-guide.rust-lang.org/appendix/glossary.html?highlight=monomorphize#appendix-c-glossary
 
 MIR optimizations run after borrow checking. We run a series of optimization
 passes over the MIR to improve it. Some passes are required to run on all code,
@@ -22,9 +22,9 @@ run and that some validation has occurred. Then, it [steals][steal] the MIR
 optimizes it, and returns the improved MIR.
 
 [optmir]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_mir/transform/fn.optimized_mir.html
-[query]: https://rust-lang.github.io/rustc-dev-guide/query.html
-[defid]: https://rust-lang.github.io/rustc-dev-guide/appendix/glossary.html?highlight=DefId#appendix-c-glossary
-[steal]: https://rust-lang.github.io/rustc-dev-guide/mir/passes.html?highlight=steal#stealing
+[query]: https://rustc-dev-guide.rust-lang.org/query.html
+[defid]: https://rustc-dev-guide.rust-lang.org/appendix/glossary.html?highlight=DefId#appendix-c-glossary
+[steal]: https://rustc-dev-guide.rust-lang.org/mir/passes.html?highlight=steal#stealing
 
 ## Defining optimization passes