From 37a1fc542fbf8c11356d4395f28d4ab7f936945d Mon Sep 17 00:00:00 2001 From: Josh Triplett Date: Wed, 9 Feb 2022 12:17:38 -0800 Subject: [PATCH] Capitalize "Rust" Co-authored-by: Mark Rousskov --- library/std/src/time.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/library/std/src/time.rs b/library/std/src/time.rs index 4a65d612a62..df8a726e64e 100644 --- a/library/std/src/time.rs +++ b/library/std/src/time.rs @@ -133,7 +133,7 @@ pub use core::time::FromFloatSecsError; /// if available, which is the case for all [tier 1] platforms. /// In practice such guarantees are – under rare circumstances – broken by hardware, virtualization /// or operating system bugs. To work around these bugs and platforms not offering monotonic clocks -/// [`duration_since`], [`elapsed`] and [`sub`] saturate to zero. In older rust versions this +/// [`duration_since`], [`elapsed`] and [`sub`] saturate to zero. In older Rust versions this /// lead to a panic instead. [`checked_duration_since`] can be used to detect and handle situations /// where monotonicity is violated, or `Instant`s are subtracted in the wrong order. ///