Fix documentation typo "appects" > "affects"

This commit is contained in:
Rua 2024-03-21 18:22:23 +01:00
parent 32799a55e2
commit 238cd36671

View file

@ -3826,7 +3826,7 @@ declare_clippy_lint! {
declare_clippy_lint! { declare_clippy_lint! {
/// ### What it does /// ### What it does
/// Checks for usage of `.filter(Option::is_some)` that may be replaced with a `.flatten()` call. /// Checks for usage of `.filter(Option::is_some)` that may be replaced with a `.flatten()` call.
/// This lint will require additional changes to the follow-up calls as it appects the type. /// This lint will require additional changes to the follow-up calls as it affects the type.
/// ///
/// ### Why is this bad? /// ### Why is this bad?
/// This pattern is often followed by manual unwrapping of the `Option`. The simplification /// This pattern is often followed by manual unwrapping of the `Option`. The simplification
@ -3852,7 +3852,7 @@ declare_clippy_lint! {
declare_clippy_lint! { declare_clippy_lint! {
/// ### What it does /// ### What it does
/// Checks for usage of `.filter(Result::is_ok)` that may be replaced with a `.flatten()` call. /// Checks for usage of `.filter(Result::is_ok)` that may be replaced with a `.flatten()` call.
/// This lint will require additional changes to the follow-up calls as it appects the type. /// This lint will require additional changes to the follow-up calls as it affects the type.
/// ///
/// ### Why is this bad? /// ### Why is this bad?
/// This pattern is often followed by manual unwrapping of `Result`. The simplification /// This pattern is often followed by manual unwrapping of `Result`. The simplification