docs: link to items by name

Author: newAM

src/eh1/delay.rs

@@ -1,23 +1,22 @@
 //! Delay mock implementations, implementing both sync and async
-//! [`BlockingDelay`](https://docs.rs/embedded-hal/latest/embedded_hal/delay/trait.BlockingDelay.html)
+//! [`DelayNs`](https://docs.rs/embedded-hal/1/embedded_hal/delay/trait.DelayNs.html)
 //! traits.
 //!
 //! ## Choosing a Delay Implementation
 //!
 //! There are three implementations available depending on your use case:
 //!
-//! - If you want **no actual delay**, create a
-//!   [`NoopDelay`](struct.NoopDelay.html) stub. It will always return
-//!   immediately, without a delay. This is useful for fast tests, where you
-//!   don't actually need to wait for the hardware.
+//! - If you want **no actual delay**, create a [`NoopDelay`] stub.
+//!   It will always return immediately, without a delay.
+//!   This is useful for fast tests, where you don't actually need to wait for
+//!   the hardware.
 //! - If you do want the **real delay behavior** when running your tests, use
-//!   [`StdSleep`](struct.StdSleep.html) stub implementation, which uses
-//!   [`std::thread::sleep`](https://doc.rust-lang.org/std/thread/fn.sleep.html)
-//!   to implement the delay.
+//!   [`StdSleep`] stub implementation, which uses [`std::thread::sleep`] to
+//!   implement the delay.
 //! - For a **configurable delay** implementation that supports expectations,
-//!   use the [`CheckedDelay`](type.CheckedDelay.html) mock. By default it
-//!   doesn't perform an actual delay, but allows the user to enable them
-//!   individually for each expected call.
+//!   use the [`CheckedDelay`] mock. By default it doesn't perform an actual
+//!   delay, but allows the user to enable them individually for each expected
+//!   call.
 //!
 //! ## Usage
 //!