Remove references to guards in documentation for clear_poison

Author: tmccombs

std/src/sync/mutex.rs

@@ -365,11 +365,11 @@ impl<T: ?Sized> Mutex<T> {
 
     /// Clear the poisoned state from a mutex
     ///
-    /// If the mutex is poisoned, it will remain poisoned until this function is called
-    /// with a mutex guard. This allows recovering from a poisoned state and marking
-    /// that it has recovered. For example, if the value is overwritten by a known-good value,
-    /// then the mutex can be marked as un-poisoned. Or possibly, the value could be inspected to
-    /// determine if it is in a consistent state, and if so the poison is removed.
+    /// If the mutex is poisoned, it will remain poisoned until this function is called. This
+    /// allows recovering from a poisoned state and marking that it has recovered. For example, if
+    /// the value is overwritten by a known-good value, then the mutex can be marked as
+    /// un-poisoned. Or possibly, the value could be inspected to determine if it is in a
+    /// consistent state, and if so the poison is removed.
     ///
     /// # Examples
     ///

std/src/sync/rwlock.rs

@@ -368,11 +368,11 @@ impl<T: ?Sized> RwLock<T> {
 
     /// Clear the poisoned state from a lock
     ///
-    /// If the lock is poisoned, it will remain poisoned until this function is called
-    /// with a write guard. This allows recovering from a poisoned state and marking
-    /// that it has recovered. For example, if the value is overwritten by a known-good value,
-    /// then the mutex can be marked as un-poisoned. Or possibly, the value could be inspected to
-    /// determine if it is in a consistent state, and if so the poison is removed.
+    /// If the lock is poisoned, it will remain poisoned until this function is called. This allows
+    /// recovering from a poisoned state and marking that it has recovered. For example, if the
+    /// value is overwritten by a known-good value, then the mutex can be marked as un-poisoned. Or
+    /// possibly, the value could be inspected to determine if it is in a consistent state, and if
+    /// so the poison is removed.
     ///
     /// # Examples
     ///