diff --git a/rust-version b/rust-version
index ea416dc27..59e9e5a0e 100644
--- a/rust-version
+++ b/rust-version
@@ -1 +1 @@
-f53b654a8882fd5fc036c4ca7a4ff41ce32497a6
+045b17737dab5fcc28e4cbee0cfe2ce4ed363b32
diff --git a/src/queries/incremental-compilation-in-detail.md b/src/queries/incremental-compilation-in-detail.md
index d68c90f49..3026349da 100644
--- a/src/queries/incremental-compilation-in-detail.md
+++ b/src/queries/incremental-compilation-in-detail.md
@@ -264,7 +264,7 @@ the `LocalId`s within it are still the same.
 
 
 
-### Checking query results for changes: `HashStable` and `Fingerprint`s
+### Checking query results for changes: `StableHash` and `Fingerprint`s
 
 In order to do red-green-marking we often need to check if the result of a
 query has changed compared to the result it had during the previous compilation session.
@@ -285,7 +285,7 @@ We call this hash value "the `Fingerprint` of the query result".
 The hashing is (and has to be) done "in a stable way".
 This means that whenever something is hashed that might change in between compilation
 sessions (e.g. a `DefId`), we instead hash its stable equivalent
-(e.g. the corresponding `DefPath`). That's what the whole `HashStable`
+(e.g. the corresponding `DefPath`). That's what the whole `StableHash`
 infrastructure is for.
 This way `Fingerprint`s computed in two different compilation sessions are still comparable.
 
diff --git a/src/tests/minicore.md b/src/tests/minicore.md
index 5d05c2c1e..0fd7af7c6 100644
--- a/src/tests/minicore.md
+++ b/src/tests/minicore.md
@@ -2,7 +2,7 @@
 
 <!-- date-check: Oct 2025 -->
 
-[`tests/auxiliary/minicore.rs`][`minicore`] is a test auxiliary for ui/codegen/assembly test suites.
+[`tests/auxiliary/minicore.rs`][`minicore`] is a test auxiliary for ui/codegen/assembly/mir-opt test suites.
 It provides `core` stubs for tests that need to
 build for cross-compiled targets but do not need/want to run.
 
diff --git a/src/unsafety-checking.md b/src/unsafety-checking.md
index ed05f8a4c..e45476342 100644
--- a/src/unsafety-checking.md
+++ b/src/unsafety-checking.md
@@ -30,14 +30,8 @@ side of an assignment expression and allows union fields to directly appear
 there, while erroring in all other cases. Union field accesses can also occur
 in patterns, so those have to be walked as well.
 
-The other complicated safety check is for writes to fields of layout constrained
-structs (such as [`NonNull`]). These are found by looking for the borrow or
-assignment expression and then visiting the subexpression being borrowed or
-assigned with a separate visitor.
-
 [THIR]: ./thir.md
 [`check_unsafety`]: https://doc.rust-lang.org/nightly/nightly-rustc/rustc_mir_build/check_unsafety/index.html
-[`NonNull`]: https://doc.rust-lang.org/std/ptr/struct.NonNull.html
 
 ## The unused_unsafe lint