doc(r3): mutex unlock order violation is no longer required to be detected by a kernel

This is mostly an obligation imposed upon an application.

Author: yvt

src/r3/src/kernel/mutex.rs

@@ -337,7 +337,7 @@ impl<System: raw::KernelMutex> Mutex<System> {
 
     /// Unlock the mutex.
     ///
-    /// Mutexes must be unlocked in a lock-reverse order, or this method will
+    /// Mutexes must be unlocked in a lock-reverse order, or this method may
     /// return [`UnlockMutexError::BadObjectState`].
     #[inline]
     pub fn unlock(self) -> Result<(), UnlockMutexError> {

src/r3/src/sync/mutex.rs

@@ -26,7 +26,7 @@ pub struct Definer<System, T, InitTag> {
 ///    calling [`Mutex::mark_consistent`].
 ///
 ///  - Mutexes must be unlocked in a lock-reverse order. [`MutexGuard`]`::drop`
-///    will panic if this is violated.
+///    might panic if this is violated.
 ///
 /// [`r3::kernel::Mutex`]: crate::kernel::Mutex
 pub struct Mutex<System, T>