SONARJAVA-3644 Fix formatting of links to from one rule to others

Wohops · quentin-jaquier-sonarsource · commit dea072645369 · 2021-01-12T12:08:48.000+01:00
diff --git a/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S2129_java.html b/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S2129_java.html
@@ -25,5 +25,5 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>Exceptions</h2>
 <p><code>BigDecimal</code> constructor with <code>double</code> argument is ignored as using <code>valueOf</code> instead might change resulting
-value. See {rule:java:S2111} .</p>
+value. See {rule:java:S2111}.</p>
 
diff --git a/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S3064_java.html b/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S3064_java.html
@@ -48,6 +48,6 @@ <h2>See</h2>
 </ul>
 <h3>See Also</h3>
 <ul>
-  <li> {rule:java:S2168} Double-checked locking should not be used </li>
+  <li> {rule:java:S2168} - Double-checked locking should not be used </li>
 </ul>
 
diff --git a/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S3366_java.html b/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S3366_java.html
@@ -23,7 +23,7 @@ <h2>Noncompliant Code Example</h2>
 </pre>
 <h2>Exceptions</h2>
 <p>This rule ignores instances of assigning <code>this</code> directly to a <code>static</code> field of the same class because that case is covered
-by {rule:java:S3010} .</p>
+by {rule:java:S3010}.</p>
 <h2>See</h2>
 <ul>
   <li> <a href="https://wiki.sei.cmu.edu/confluence/x/iDdGBQ">CERT, TSM01-J.</a> - Do not let the this reference escape during object construction
diff --git a/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S5261_java.html b/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S5261_java.html
@@ -3,7 +3,7 @@
 be misleading.</p>
 <p>This rules reports <code>else</code> statements that are difficult to understand, because they are inside nested <code>if</code> statements without
 curly braces.</p>
-<p>Adding curly braces can generally make the code clearer (see rule {rule:java:S121} ), and in this situation of dangling <code>else</code>, it
+<p>Adding curly braces can generally make the code clearer (see rule {rule:java:S121}), and in this situation of dangling <code>else</code>, it
 really clarifies the intention of the code.</p>
 <h2>Noncompliant Code Example</h2>
 <pre>
diff --git a/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S5786_java.html b/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S5786_java.html
@@ -25,7 +25,7 @@ <h2>Compliant Solution</h2>
 </pre>
 <h2>Exceptions</h2>
 <p>This rule does not raise an issue about <code>private</code> visibility, because <code>private</code> test methods and classes are systematically
-ignored by JUnit5, without a proper warning. It's not a <code>Code Smell</code> but a <code>Bug</code> handled by the rule {rule:java:S5810} .</p>
+ignored by JUnit5, without a proper warning. It's not a <code>Code Smell</code> but a <code>Bug</code> handled by the rule {rule:java:S5810}.</p>
 <h2>See</h2>
 <ul>
   <li> <a href="https://junit.org/junit5/docs/current/user-guide/#writing-tests-classes-and-methods">JUnit 5 Test Classes and Methods</a> </li>
diff --git a/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S5845_java.html b/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S5845_java.html
@@ -45,6 +45,6 @@ <h2>Noncompliant Code Example</h2>
 </pre>
 <h2>See</h2>
 <ul>
-  <li> {rule:java:S2159} Silly equality checks should not be made </li>
+  <li> {rule:java:S2159} - Silly equality checks should not be made </li>
 </ul>
 
diff --git a/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S6035_java.html b/java-checks/src/main/resources/org/sonar/l10n/java/rules/java/S6035_java.html
@@ -1,5 +1,5 @@
 <p>When an alternation contains multiple alternatives that consist of a single character, it can be rewritten as a character class. This should be
-preferred because it is more efficient and can even help prevent stack overflows when used inside a repetition (see rule {rule:java:S5998} ).</p>
+preferred because it is more efficient and can even help prevent stack overflows when used inside a repetition (see rule {rule:java:S5998}).</p>
 <h2>Noncompliant Code Example</h2>
 <pre>
 Pattern.compile("a|b|c"); // Noncompliant
