docs: fix intra-doc links in mingling crate

4 files changed, 8 insertions, 8 deletions

diff --git a/mingling/src/confirm/count.rs b/mingling/src/confirm/count.rs
index 373d42c..c9f9db7 100644
--- a/mingling/src/confirm/count.rs
+++ b/mingling/src/confirm/count.rs
@@ -19,7 +19,7 @@
 ///
 /// - `ConfirmCount::from(3)` → asks at most **3** times before giving up.
 /// - `ConfirmCount::from(1)` → asks exactly **1** time.
-/// - `ConfirmCount::from(0)` → interpreted as [`Loop`], meaning it will keep asking
+/// - `ConfirmCount::from(0)` → interpreted as [`ConfirmCount::Loop`], meaning it will keep asking
 ///   indefinitely until a valid answer is parsed.
 ///
 /// # Examples
diff --git a/mingling/src/osc94/guard.rs b/mingling/src/osc94/guard.rs
index 793abec..d17f483 100644
--- a/mingling/src/osc94/guard.rs
+++ b/mingling/src/osc94/guard.rs
@@ -2,12 +2,12 @@ use crate::osc94::OSC94State;
 
 /// A guard for modifying process state.
 ///
-/// Obtained via [`OSC94::get_mut`]. When the guard is dropped, the process state is
+/// Obtained via [`crate::res::ResOSC94::get_mut`]. When the guard is dropped, the process state is
 /// automatically restored to `OS94State::Clean`, so no manual cleanup is needed.
 ///
 /// # Example
 ///
-/// Create a guard via [`ResOSC94`], and the state is automatically restored to Clean
+/// Create a guard via [`crate::res::ResOSC94`], and the state is automatically restored to Clean
 /// when the guard is dropped:
 ///
 /// ```
diff --git a/mingling/src/res/confirm.rs b/mingling/src/res/confirm.rs
index baf8caf..e07e9a2 100644
--- a/mingling/src/res/confirm.rs
+++ b/mingling/src/res/confirm.rs
@@ -54,8 +54,8 @@ impl ResConfirm {
 
     /// Creates a `Confirm` instance in the confirmed state.
     ///
-    /// The returned `Confirm` will directly return `true` when calling [`ask`](Confirm::ask) or
-    /// [`try_ask`](Confirm::try_ask), without prompting the user.
+    /// The returned `Confirm` will directly return `true` when calling [`ask`](ResConfirm::ask) or
+    /// [`try_ask`](ResConfirm::try_ask), without prompting the user.
     ///
     /// # Examples
     ///
@@ -73,8 +73,8 @@ impl ResConfirm {
 
     /// Marks the Confirm as confirmed.
     ///
-    /// After calling this method, subsequent calls to [`ask`](Confirm::ask) or
-    /// [`try_ask`](Confirm::try_ask) on this Confirm will directly return `true`
+    /// After calling this method, subsequent calls to [`ask`](ResConfirm::ask) or
+    /// [`try_ask`](ResConfirm::try_ask) on this Confirm will directly return `true`
     /// without prompting the user.
     ///
     /// # Examples
diff --git a/mingling/src/setups/confirm.rs b/mingling/src/setups/confirm.rs
index 6635420..46ead36 100644
--- a/mingling/src/setups/confirm.rs
+++ b/mingling/src/setups/confirm.rs
@@ -30,7 +30,7 @@ use crate::res::ResConfirm;
 /// - Registers a [`ResConfirm`] resource that tracks confirmation state.
 /// - At the beginning of command execution, checks whether the user's
 ///   confirmation mode is set to `Skip`.
-/// - If confirmation is skipped, the [`Confirm`] resource is updated
+/// - If confirmation is skipped, the [`ResConfirm`] resource is updated
 ///   to record the confirmed state.
 ///
 /// # Notes