about summary refs log tree commit diff
diff options
context:
space:
mode:
authorPhilipp Krones <hello@philkrones.com>2020-09-10 17:08:10 +0200
committerGitHub <noreply@github.com>2020-09-10 17:08:10 +0200
commit36a864854f41dfd25c45fa4881812bd005bd5054 (patch)
tree7c62404917a3faa98b6a81d4846fa06417d4b10f
parentd712d7f700977240ad9bd731fc3f76e05cc1c900 (diff)
downloadrust-36a864854f41dfd25c45fa4881812bd005bd5054.tar.gz
rust-36a864854f41dfd25c45fa4881812bd005bd5054.zip
Fix spelling of "Known problems section" of `interior_mutable_key`
-rw-r--r--clippy_lints/src/mut_key.rs8
1 files changed, 4 insertions, 4 deletions
diff --git a/clippy_lints/src/mut_key.rs b/clippy_lints/src/mut_key.rs
index fa3a99dad9d..0826ad0ab55 100644
--- a/clippy_lints/src/mut_key.rs
+++ b/clippy_lints/src/mut_key.rs
@@ -12,10 +12,10 @@ declare_clippy_lint! {
     /// `BtreeSet` rely on either the hash or the order of keys be unchanging,
     /// so having types with interior mutability is a bad idea.
     ///
-    /// **Known problems:** It's correct to use a struct, that contains interior mutability,
-    /// as a key; when its `Hash` implementation doesn't access any these interior mutable types.
-    /// However, this lint is unable to recognise it so cause a false positive.
-    /// `bytes` ctate is a great example of this.
+    /// **Known problems:** It's correct to use a struct, that contains interior mutability
+    /// as a key, when its `Hash` implementation doesn't access any of the interior mutable types.
+    /// However, this lint is unable to recognize this, so it causes a false positive in theses cases.
+    /// The `bytes` crate is a great example of this.
     ///
     /// **Example:**
     /// ```rust