From df457e22f28f1bcc582e0dfd5792e5e5585bc4ab Mon Sep 17 00:00:00 2001 From: Scomocouk <152920539+Scomocouk@users.noreply.github.com> Date: Wed, 24 Jan 2024 11:00:02 +0000 Subject: [PATCH] Modify rule S4035: Fix typo in 'Why is this an issue' section - "IEquitable" -> "IEquatable" (#3535) Co-authored-by: Scott Moore --- rules/S4035/csharp/rule.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/rules/S4035/csharp/rule.adoc b/rules/S4035/csharp/rule.adoc index a442d065ecc..606e5ba9c20 100644 --- a/rules/S4035/csharp/rule.adoc +++ b/rules/S4035/csharp/rule.adoc @@ -6,7 +6,7 @@ When a class implements the `IEquatable` interface, it enters a contract that Alternatively `IEqualityComparer` provides a safer interface and is used by collections or `Equals` could be made `virtual`. -This rule raises an issue when an unsealed, `public` or `protected` class implements `IEquitable` and the `Equals` is neither `virtual` nor `abstract`. +This rule raises an issue when an unsealed, `public` or `protected` class implements `IEquatable` and the `Equals` is neither `virtual` nor `abstract`. === Noncompliant code example