about summary refs log tree commit diff
diff options
context:
space:
mode:
authorGray Olson <gray@grayolson.com>2023-09-25 13:28:35 +0200
committerManish Goregaokar <manishsmail@gmail.com>2024-01-07 08:56:04 -0800
commit584f0986fcec6e2cb61d9753a9ccf3ff951d0b3a (patch)
tree4637f158cc5bc6e67c031e233fee519a5c8ee42a
parentba3b9342cc9f3d4421141e42d3c59200f712b3fc (diff)
downloadrust-584f0986fcec6e2cb61d9753a9ccf3ff951d0b3a.tar.gz
rust-584f0986fcec6e2cb61d9753a9ccf3ff951d0b3a.zip
fix broken links
-rw-r--r--library/core/src/pin.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/library/core/src/pin.rs b/library/core/src/pin.rs
index 80e428033aa..146708f45cb 100644
--- a/library/core/src/pin.rs
+++ b/library/core/src/pin.rs
@@ -296,7 +296,7 @@
 //! # Examples of address-sensitive types
 //! [address-sensitive-examples]: #examples-of-address-sensitive-types
 //!
-//! ## Self-referential struct
+//! ## A self-referential struct
 //! [self-ref]: #a-self-referential-struct
 //! [`Unmovable`]: #a-self-referential-struct
 //!
@@ -425,7 +425,7 @@
 //! This point is subtle but required for intrusive data structures to be implemented soundly.
 //!
 //! ## `Drop` guarantee
-//! [drop-guarantee]: #notice-of-destruction
+//! [drop-guarantee]: self#drop-guarantee
 //!
 //! There needs to be a way for a pinned value to notify any code that is relying on its pinned
 //! status that it is about to be destroyed, so that such code can remove its address from their