From dc7ab01907921eefdfc89d56efb678858b2c4fe4 Mon Sep 17 00:00:00 2001
From: Matthew Jackson <1085847+MattJackson@users.noreply.github.com>
Date: Tue, 23 Jun 2026 22:51:47 -0700
Subject: [PATCH] =?UTF-8?q?fix:=20update=20stale=20doc=20comment=20in=20Re?=
 =?UTF-8?q?adCtx::for=5Fpatch=20=E2=80=94=20sync=20is=20automatic?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 src/disc/read_error.rs | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/src/disc/read_error.rs b/src/disc/read_error.rs
index e40edea..066f398 100644
--- a/src/disc/read_error.rs
+++ b/src/disc/read_error.rs
@@ -199,9 +199,10 @@ impl ReadCtx {
     /// patch loop's whole job is to chip away at bad ranges — being
     /// more eager to skip clustered bad sectors converges faster on
     /// the recoverable good sectors inside a range. The patch-side
-    /// `compute_damage_skip` reads its threshold from
-    /// `PASSN_DAMAGE_THRESHOLD_PCT`; keep the two in sync until the
-    /// patch loop's damage-skip is unified with `handle_read_error`'s
+    /// `compute_damage_skip` reads its threshold directly from
+    /// `PASSN_DAMAGE_THRESHOLD_PCT`, which is an alias for this crate's
+    /// `PATCH_DAMAGE_THRESHOLD_PCT`, so the two are always in sync.
+    /// The patch loop's damage-skip is not yet unified with `handle_read_error`'s
     /// jump path. (v0.20.8 unification attempt found the unification
     /// itself blocked on the size-aware `range_remaining/4` cap that
     /// lives in `compute_damage_skip` but not in