From aaf4983890c205f11f91be172183a97d297d11a0 Mon Sep 17 00:00:00 2001 From: Charlie Marsh Date: Tue, 4 Jun 2024 15:20:03 -0400 Subject: [PATCH] Tweak docs --- .../src/rules/numpy/rules/deprecated_type_alias.rs | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/crates/ruff_linter/src/rules/numpy/rules/deprecated_type_alias.rs b/crates/ruff_linter/src/rules/numpy/rules/deprecated_type_alias.rs index 5e89963d95d3b..3d5dbef1f6e47 100644 --- a/crates/ruff_linter/src/rules/numpy/rules/deprecated_type_alias.rs +++ b/crates/ruff_linter/src/rules/numpy/rules/deprecated_type_alias.rs @@ -10,14 +10,14 @@ use crate::checkers::ast::Checker; /// Checks for deprecated NumPy type aliases. /// /// ## Why is this bad? -/// NumPy's `np.int` has long been an alias of the builtin `int`. The same -/// goes for `np.float`, and others. These aliases exist primarily +/// NumPy's `np.int` has long been an alias of the builtin `int`; the same +/// is true of `np.float` and others. These aliases exist primarily /// for historic reasons, and have been a cause of frequent confusion /// for newcomers. /// /// These aliases were deprecated in 1.20, and removed in 1.24. -/// Note that `np.bool` and `np.long` have been reintroduced in 2.0 with -/// a different meaning. +/// Note, however, that `np.bool` and `np.long` were reintroduced in 2.0 with +/// different semantics, and are thus omitted from this rule. /// /// ## Examples /// ```python