From 5c058a0fad3e6bc3bfda268f081df91d18b06e49 Mon Sep 17 00:00:00 2001
From: Philipp Dominik Schubert <119606487+pdschbrt@users.noreply.github.com>
Date: Fri, 26 Jan 2024 15:46:17 +0100
Subject: [PATCH] Modify Rule S2699: Fix Typos (#3482)

---
 rules/S2699/csharp/rule.adoc | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/rules/S2699/csharp/rule.adoc b/rules/S2699/csharp/rule.adoc
index 4a116fddb67..8257a01832a 100644
--- a/rules/S2699/csharp/rule.adoc
+++ b/rules/S2699/csharp/rule.adoc
@@ -31,7 +31,7 @@ By enforcing the presence of assertions, this rule aims to enhance the reliabili
 
 Test methods that include a call to a custom assertion method will not raise any issues.
 
-== How to fix it
+=== How to fix it
 
 To address this issue, you should include assertions to validate the expected behavior.
 Choose an appropriate assertion method provided by your testing framework (such as MSTest, NUnit, xUnit) or select a suitable assertion library like FluentAssertions, NFluent, NSubstitute, or Shouldly.
@@ -68,7 +68,7 @@ public static class Validator
 public class AssertionMethodAttribute : Attribute { }
 ----
 
-== Hot to fix it in MSTest
+== How to fix it in MSTest
 
 === Code examples
 
@@ -97,7 +97,7 @@ public void Add_SingleNumber_ReturnsSameNumber()
 }
 ----
 
-== Hot to fix it in NUnit
+== How to fix it in NUnit
 
 === Code examples
 
@@ -126,7 +126,7 @@ public void Add_SingleNumber_ReturnsSameNumber()
 }
 ----
 
-== Hot to fix it in xUnit
+== How to fix it in xUnit
 
 === Code examples