diff --git a/library/core/src/intrinsics.rs b/library/core/src/intrinsics.rs
index afea8aa8ff262b989df3483062299c42e7ac0e6b..634ed87b0910e69d4ca86d5aefcaa2ad0571534a 100644
--- a/library/core/src/intrinsics.rs
+++ b/library/core/src/intrinsics.rs
@@ -846,6 +846,12 @@
/// destination value, then forgets the original. It's equivalent to C's
/// `memcpy` under the hood, just like `transmute_copy`.
///
+ /// Because `transmute` is a by-value operation, alignment of the *transmuted values
+ /// themselves* is not a concern. As with any other function, the compiler already ensures
+ /// both `T` and `U` are properly aligned. However, when transmuting values that *point
+ /// elsewhere* (such as pointers, references, boxes…), the caller has to ensure proper
+ /// alignment of the pointed-to values.
+ ///
/// `transmute` is **incredibly** unsafe. There are a vast number of ways to
/// cause [undefined behavior][ub] with this function. `transmute` should be
/// the absolute last resort.
@@ -965,7 +971,13 @@
/// assert_eq!(b"Rust", &[82, 117, 115, 116]);
/// ```
///
- /// Turning a `Vec<&T>` into a `Vec