Documentation suggestions from flip1995

Co-Authored-By: Philipp Krones <hello@philkrones.com>

Author: JarredAllen

clippy_lints/src/option_if_let_else.rs

@@ -9,16 +9,15 @@ use rustc_session::{declare_lint_pass, declare_tool_lint};
 
 declare_clippy_lint! {
     /// **What it does:**
-    /// Detects people who use `if let Some(v) = ... { y } else { x }`
-    /// when they could use `Option::map_or` or `Option::map_or_else`
-    /// instead.
+    /// Lints usage of  `if let Some(v) = ... { y } else { x }` which is more 
+    /// idiomatically done with `Option::map_or` or `Option::map_or_else`.
     ///
     /// **Why is this bad?**
-    /// Using the dedicated function in the Option class is clearer and
+    /// Using the dedicated functions of the Option type is clearer and
     /// more concise than an if let expression.
     ///
     /// **Known problems:**
-    /// Using `Option::map_or` (as the lint presently suggests) requires
+    /// Using `Option::map_or` (as the lint currently suggests) requires
     /// it to compute the else value every function call, even if the
     /// value is unneeded. It might be better to use Option::map_or_else
     /// if the code is either very expensive or if it changes some state

tests/ui/option_if_let_else.rs

@@ -1,5 +1,5 @@
-#![warn(clippy::option_if_let_else)]
 // run-rustfix
+#![warn(clippy::option_if_let_else)]
 
 fn bad1(string: Option<&str>) -> (bool, &str) {
     if let Some(x) = string {