From 4c86b155f29e8bc4fb5e11d551d97f2eeb7eec6a Mon Sep 17 00:00:00 2001 From: Ofek Lev Date: Thu, 16 Nov 2023 23:10:09 -0500 Subject: [PATCH] Fix typo (#8735) --- .../src/rules/pylint/rules/too_many_public_methods.rs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/crates/ruff_linter/src/rules/pylint/rules/too_many_public_methods.rs b/crates/ruff_linter/src/rules/pylint/rules/too_many_public_methods.rs index 7e7c113d80ad44..6679341a54f7a5 100644 --- a/crates/ruff_linter/src/rules/pylint/rules/too_many_public_methods.rs +++ b/crates/ruff_linter/src/rules/pylint/rules/too_many_public_methods.rs @@ -9,8 +9,8 @@ use crate::checkers::ast::Checker; /// ## What it does /// Checks for classes with too many public methods /// -/// By default, this rule allows up to 20 statements, as configured by the -/// [`pylint.max-public-methods`] option. +/// By default, this rule allows up to 20 public methods, as configured by +/// the [`pylint.max-public-methods`] option. /// /// ## Why is this bad? /// Classes with many public methods are harder to understand