Update rule metadata (#5264)

Co-authored-by: tomasz-tylenda-sonarsource <tomasz-tylenda-sonarsource@users.noreply.github.com>

Author: github-actions[bot]

sonar-java-plugin/src/main/resources/org/sonar/l10n/java/rules/java/S1854.html

@@ -7,7 +7,7 @@ <h3>Exceptions</h3>
 <p>This rule ignores initializations to <code>-1</code>, <code>0</code>, <code>1</code>, <code>null</code>, <code>true</code>, <code>false</code> and
 <code>""</code>.</p>
 <h2>How to fix it</h2>
-<p>Remove the unnecesarry assignment, then test the code to make sure that the right-hand side of a given assignment had no side effects (e.g. a
+<p>Remove the unnecessary assignment, then test the code to make sure that the right-hand side of a given assignment had no side effects (e.g. a
 method that writes certain data to a file and returns the number of written bytes).</p>
 <h3>Code examples</h3>
 <h4>Noncompliant code example</h4>

sonar-java-plugin/src/main/resources/org/sonar/l10n/java/rules/java/S5443.html

@@ -7,7 +7,7 @@
   <li> <a href="https://nvd.nist.gov/vuln/detail/CVE-2012-2451">CVE-2012-2451</a> </li>
   <li> <a href="https://nvd.nist.gov/vuln/detail/CVE-2015-1838">CVE-2015-1838</a> </li>
 </ul>
-<p>This rule raises an issue whenever it detects a hard-coded path to a publicly writable directory like <code>/tmp</code> (see examples bellow). It
+<p>This rule raises an issue whenever it detects a hard-coded path to a publicly writable directory like <code>/tmp</code> (see examples below). It
 also detects access to environment variables that point to publicly writable directories, e.g., <code>TMP</code> and <code>TMPDIR</code>.</p>
 <ul>
   <li> <code>/tmp</code> </li>

sonar-java-plugin/src/main/resources/org/sonar/l10n/java/rules/java/S5689.html

@@ -1,5 +1,5 @@
 <p>Disclosure of version information, usually overlooked by developers but disclosed by default by the systems and frameworks in use, can pose a
-significant security risk depending on the production environement.</p>
+significant security risk depending on the production environment.</p>
 <p>Once this information is public, attackers can use it to identify potential security holes or vulnerabilities specific to that version.</p>
 <p>Furthermore, if the published version information indicates the use of outdated or unsupported software, it becomes easier for attackers to exploit
 known vulnerabilities. They can search for published vulnerabilities related to that version and launch attacks that specifically target those

sonar-java-plugin/src/main/resources/org/sonar/l10n/java/rules/java/S5876.html

@@ -80,7 +80,7 @@ <h3>Standards</h3>
   Authentication Failures</a> </li>
   <li> OWASP - <a href="https://owasp.org/www-project-top-ten/2017/A2_2017-Broken_Authentication">Top 10 2017 Category A2 - Broken Authentication</a>
   </li>
-  <li> <a href="https://owasp.org/www-community/attacks/Session_fixation">OWASP Sesssion Fixation</a> </li>
+  <li> <a href="https://owasp.org/www-community/attacks/Session_fixation">OWASP Session Fixation</a> </li>
   <li> CWE - <a href="https://cwe.mitre.org/data/definitions/384">CWE-384 - Session Fixation</a> </li>
   <li> STIG Viewer - <a href="https://stigviewer.com/stigs/application_security_and_development/2024-12-06/finding/V-222579">Application Security and
   Development: V-222579</a> - Applications must use system-generated session identifiers that protect against session fixation. </li>

sonarpedia.json

@@ -3,9 +3,9 @@
   "languages": [
     "JAVA"
   ],
-  "latest-update": "2025-07-04T09:48:41.626288988Z",
+  "latest-update": "2025-07-18T13:33:45.764705424Z",
   "options": {
     "no-language-in-filenames": true,
     "preserve-filenames": false
   }
-}
+}