Deploying to gh-pages from @ cac75fb 🚀

SonarSource · Nov 30, 2023 · 1dd7c72 · 1dd7c72
1 parent de902c6
commit 1dd7c72
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 7 deletions.
diff --git a/rules/S6862/default-description.html b/rules/S6862/default-description.html
@@ -9,8 +9,9 @@ <h2 id="_why_is_this_an_issue">Why is this an issue?</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Naming conventions play a crucial role in maintaining code clarity and readability.
-In Spring configurations, the uniqueness of bean names is vital to avoid confusion for both developers and the Spring Context.
-When two beans share the same name within a configuration, it becomes challenging for a reader to discern which bean is being referred to, leading to potential misunderstandings and errors.</p>
+The uniqueness of bean names in Spring configurations is vital to the clarity and readability of the code.
+When two beans share the same name within a configuration, it is not obvious to the reader which bean is being referred to.
+This leads to potential misunderstandings and errors.</p>
 </div>
 </div>
 </div>
@@ -19,7 +20,7 @@ <h2 id="_how_to_fix_it">How to fix it</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>To address this issue, ensure each bean within a configuration has a distinct and meaningful name.
-Choose names that accurately represent the purpose or functionality of the bean, making it easier for developers to understand the role of each component.</p>
+Choose names that accurately represent the purpose or functionality of the bean.</p>
 </div>
 <div class="sect2">
 <h3 id="_code_examples">Code examples</h3>

diff --git a/rules/S6862/java-description.html b/rules/S6862/java-description.html
@@ -9,8 +9,9 @@ <h2 id="_why_is_this_an_issue">Why is this an issue?</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Naming conventions play a crucial role in maintaining code clarity and readability.
-In Spring configurations, the uniqueness of bean names is vital to avoid confusion for both developers and the Spring Context.
-When two beans share the same name within a configuration, it becomes challenging for a reader to discern which bean is being referred to, leading to potential misunderstandings and errors.</p>
+The uniqueness of bean names in Spring configurations is vital to the clarity and readability of the code.
+When two beans share the same name within a configuration, it is not obvious to the reader which bean is being referred to.
+This leads to potential misunderstandings and errors.</p>
 </div>
 </div>
 </div>
@@ -19,7 +20,7 @@ <h2 id="_how_to_fix_it">How to fix it</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>To address this issue, ensure each bean within a configuration has a distinct and meaningful name.
-Choose names that accurately represent the purpose or functionality of the bean, making it easier for developers to understand the role of each component.</p>
+Choose names that accurately represent the purpose or functionality of the bean.</p>
 </div>
 <div class="sect2">
 <h3 id="_code_examples">Code examples</h3>

diff --git a/rules/rule-index.json b/rules/rule-index.json