about summary refs log tree commit diff
diff options
context:
space:
mode:
authorbors <bors@rust-lang.org>2023-10-07 21:33:53 +0000
committerbors <bors@rust-lang.org>2023-10-07 21:33:53 +0000
commit33f49f33d6f8cec9a5772bc7f3a4e5f1de207b30 (patch)
tree93e603404a2dc7caad842abd939a6bac32c19701
parent76240459976735c14bddbfa2ec4ac5188f901f0a (diff)
parentbffba76b52dfe96f42fb153c02824237968a15c8 (diff)
downloadrust-33f49f33d6f8cec9a5772bc7f3a4e5f1de207b30.tar.gz
rust-33f49f33d6f8cec9a5772bc7f3a4e5f1de207b30.zip
Auto merge of #11638 - samueltardieu:into-iter, r=Manishearth
Fix two typos in lint description

Fix #11636

changelog: none
-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 ee3d1735043..0ee291a4e9d 100644
--- a/clippy_lints/src/iter_without_into_iter.rs
+++ b/clippy_lints/src/iter_without_into_iter.rs
@@ -58,8 +58,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