What changed, and why it matters
This commit fixes a single-word typo in a documentation comment. It changes 'is case of overflow' to 'in case of overflow' in a code comment describing a checked addition function. There is no code behavior change and no security relevance.
No action required. This is a documentation typo fix with no security or functional impact.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies one line in units/src/fee_rate/mod.rs, correcting a typo in the doc comment for FeeRate::checked_add. The function implementation and all executable code remain unchanged. No logic, API, or safety properties are affected.
Changed components
units/src/fee_rate/mod.rs (documentation comment only)Inspect captured patch +1 / −1
diff --git a/units/src/fee_rate/mod.rs b/units/src/fee_rate/mod.rs
index f24a3f6a..2ee77b73 100644
--- a/units/src/fee_rate/mod.rs
+++ b/units/src/fee_rate/mod.rs
@@ -146,7 +146,7 @@ impl FeeRate {
/// Checked addition.
///
- /// Computes `self + rhs` returning [`None`] is case of overflow.
+ /// Computes `self + rhs` returning [`None`] in case of overflow.
#[must_use]
pub const fn checked_add(self, rhs: FeeRate) -> Option<Self> {
// No `map()` in const context.
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.