about summary refs log tree commit diff
diff options
context:
space:
mode:
authorSamuel Tardieu <sam@rfc1149.net>2023-10-07 10:54:45 +0200
committerSamuel Tardieu <sam@rfc1149.net>2023-10-07 10:58:52 +0200
commitbffba76b52dfe96f42fb153c02824237968a15c8 (patch)
tree1056e02a6e012f7827e9efd5c1d18e1bd6419429
parent3662bd8f587c9305e4d231a9456e63b92b8a7729 (diff)
downloadrust-bffba76b52dfe96f42fb153c02824237968a15c8.tar.gz
rust-bffba76b52dfe96f42fb153c02824237968a15c8.zip
Fix two typos in lint description
-rw-r--r--clippy_lints/src/iter_without_into_iter.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/clippy_lints/src/iter_without_into_iter.rs b/clippy_lints/src/iter_without_into_iter.rs
index 43e1b92c9b9..abfc50369b5 100644
--- a/clippy_lints/src/iter_without_into_iter.rs
+++ b/clippy_lints/src/iter_without_into_iter.rs
@@ -56,8 +56,8 @@ declare_clippy_lint! {
     ///
     /// ### Why is this bad?
     /// It's not bad, but having them is idiomatic and allows the type to be used in iterator chains
-    /// by just calling `.iter()`, instead of the more awkward `<&Type>::into_iter` or `(&val).iter()` syntax
-    /// in case of ambiguity with another `Intoiterator` impl.
+    /// by just calling `.iter()`, instead of the more awkward `<&Type>::into_iter` or `(&val).into_iter()` syntax
+    /// in case of ambiguity with another `IntoIterator` impl.
     ///
     /// ### Example
     /// ```rust