Fix some links

src/backend/libs-and-metadata.md

@@ -107,12 +107,11 @@ The hash includes a variety of elements:
   Disambiguator](#crate-disambiguator), and all CLI options marked with
   `[TRACKED]`).
 
-See [`finalize_and_compute_crate_hash`] for where the hash is actually
-computed.
+See [`compute_hir_hash`] for where the hash is actually computed.
 
 [SVH]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_data_structures/svh/struct.Svh.html
 [incremental compilation]: ../queries/incremental-compilation.md
-[`finalize_and_compute_crate_hash`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_middle/hir/map/collector/struct.NodeCollector.html#method.finalize_and_compute_crate_hash
+[`compute_hir_hash`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_ast_lowering/struct.LoweringContext.html#method.compute_hir_hash
 
 ### Stable Crate Id
 

src/building/bootstrapping.md

@@ -56,7 +56,7 @@ because one must first build the new compiler with an older compiler
 and then use that to build the new compiler with itself.
 For development, you usually only want the `stage1` compiler,
 which you can build with `./x.py build library/std`.
-See [Building the Compiler](/building/how-to-build-and-run.html#building-the-compiler).
+See [Building the Compiler](./how-to-build-and-run.html#building-the-compiler).
 
 ### Stage 3
 

src/constants.md

@@ -39,7 +39,7 @@ why the array length in `foo<const N: usize>() -> [u8; N + 1]` can use `N`.
 
 Without any manual adjustments, this causes us to include parameters even if
 the constant doesn't use them in any way. This can cause
-[some interesting errors](pcg-unused-substs) and breaks some already stable code.
+[some interesting errors][pcg-unused-substs] and breaks some already stable code.
 
 To deal with this, we intend to look at the generic parameters explicitly mentioned
 by the constants and then search the predicates of its parents to figure out which