From 9bbb0a5151f08322a744e64034960f7fe7b63bb2 Mon Sep 17 00:00:00 2001 From: Tom Kuson Date: Sat, 22 Jul 2023 02:23:30 +0100 Subject: [PATCH] Fix typo in documentation (#5961) ## Summary Close unclosed inline code block that was causing the text not to render properly. ## Test Plan `mkdocs serve` --- .../rules/pylint/rules/repeated_equality_comparison_target.rs | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/crates/ruff/src/rules/pylint/rules/repeated_equality_comparison_target.rs b/crates/ruff/src/rules/pylint/rules/repeated_equality_comparison_target.rs index 78608cd005430..1be684759dd64 100644 --- a/crates/ruff/src/rules/pylint/rules/repeated_equality_comparison_target.rs +++ b/crates/ruff/src/rules/pylint/rules/repeated_equality_comparison_target.rs @@ -19,7 +19,7 @@ use crate::checkers::ast::Checker; /// ## Why is this bad? /// To check if a variable is equal to one of many values, it is common to /// write a series of equality comparisons (e.g., -/// `foo == "bar" or foo == "baz"). +/// `foo == "bar" or foo == "baz"`). /// /// Instead, prefer to combine the values into a collection and use the `in` /// operator to check for membership, which is more performant and succinct.