backticks in docs to appease clippy

astral-sh · Nov 27, 2024 · e9af7fa · e9af7fa
1 parent d261a0e
commit e9af7fa
Show file tree

Hide file tree

Showing 2 changed files with 6 additions and 6 deletions.
diff --git a/crates/ruff_linter/src/rules/pep8_naming/rules/camelcase_imported_as_constant.rs b/crates/ruff_linter/src/rules/pep8_naming/rules/camelcase_imported_as_constant.rs
@@ -32,10 +32,10 @@ use crate::rules::pep8_naming::settings::IgnoreNames;
 ///
 /// ## Note
 /// Identifiers consisting of a single uppercase character are ambiguous under
-/// the rules of [PEP 8], which specifies CamelCase for classes and
-/// ALL_CAPS_SNAKE_CASE for constants. Without a second character, it is not
+/// the rules of [PEP 8], which specifies `CamelCase` for classes and
+/// `ALL_CAPS_SNAKE_CASE` for constants. Without a second character, it is not
 /// possible to reliably guess whether the identifier is intended to be part
-/// of a CamelCase string for a class or an ALL_CAPS_SNAKE_CASE string for
+/// of a `CamelCase` string for a class or an `ALL_CAPS_SNAKE_CASE` string for
 /// a constant, since both conventions will produce the same output when given
 /// a single input character. Therefore, this lint rule does not apply to cases
 /// where the alias for the imported identifier consists of a single uppercase

diff --git a/crates/ruff_linter/src/rules/pep8_naming/rules/constant_imported_as_non_constant.rs b/crates/ruff_linter/src/rules/pep8_naming/rules/constant_imported_as_non_constant.rs
@@ -31,10 +31,10 @@ use crate::rules::pep8_naming::settings::IgnoreNames;
 ///
 /// ## Note
 /// Identifiers consisting of a single uppercase character are ambiguous under
-/// the rules of [PEP 8], which specifies CamelCase for classes and
-/// ALL_CAPS_SNAKE_CASE for constants. Without a second character, it is not
+/// the rules of [PEP 8], which specifies `CamelCase` for classes and
+/// `ALL_CAPS_SNAKE_CASE` for constants. Without a second character, it is not
 /// possible to reliably guess whether the identifier is intended to be part
-/// of a CamelCase string for a class or an ALL_CAPS_SNAKE_CASE string for
+/// of a `CamelCase` string for a class or an `ALL_CAPS_SNAKE_CASE` string for
 /// a constant, since both conventions will produce the same output when given
 /// a single input character. Therefore, this lint rule does not apply to cases
 /// where the imported identifier consists of a single uppercase character.