[wwwdocs,committed] gcc-14/changes.html: Fix HTML syntax

[wwwdocs,committed] gcc-14/changes.html: Fix HTML syntax

[Tobias Burnus]

[-- Attachment #1: Type: text/plain, Size: 102 bytes --]

Found when testing my own change via https://validator.w3.org/nu/#file

Committed as obvious.

Tobias

[-- Attachment #2: committed.diff --]
[-- Type: text/x-patch, Size: 4523 bytes --]

commit c9e275660a19c804dd8c591c73cb9b169a9d7573
Author: Tobias Burnus <tburnus@baylibre.com>
Date:   Thu Apr 4 22:07:28 2024 +0200

    gcc-14/changes.html: Fix HTML syntax
    
    W3.org's HTML checker complained about missing <code> and
    about <ol>...</ol> within a <p>...</p> (or rather: it complained about
    the unexpected '</p>').
---
 htdocs/gcc-14/changes.html | 16 ++++++++--------
 1 file changed, 8 insertions(+), 8 deletions(-)

diff --git a/htdocs/gcc-14/changes.html b/htdocs/gcc-14/changes.html
index 045893cf..1cc68430 100644
--- a/htdocs/gcc-14/changes.html
+++ b/htdocs/gcc-14/changes.html
@@ -861,7 +861,7 @@ __asm (".global __flmap_lock"  "\n\t"
   <li>
     <!-- commit r14-3001-g021077b94741c9 [PR110426] -->
     The analyzer now makes use of the function attribute
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-alloc_005fsize-function-attribute">alloc_size</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Common-Function-Attributes.html#index-alloc_005fsize-function-attribute"><code>alloc_size</code></a>
     allowing
     <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-fanalyzer"><code>-fanalyzer</code></a>
     to emit
@@ -887,7 +887,7 @@ __asm (".global __flmap_lock"  "\n\t"
   </li>
   <li>
     <!-- commit r14-2029-g0e466e978c7286 [PR106626] -->
-    <p>The warning
+      The warning
       <a href="https://gcc.gnu.org/onlinedocs/gcc/Static-Analyzer-Options.html#index-Wanalyzer-out-of-bounds"><code>-Wanalyzer-out-of-bounds</code></a>
       has been extended so that, where possible, it will emit a text-based
       diagram visualizing the spatial relationship between
@@ -899,9 +899,9 @@ __asm (".global __flmap_lock"  "\n\t"
       whether they overlap, are touching, are close or far apart;
       which one is before or after in memory, the relative sizes involved,
       the direction of the access (read vs write), and, in some cases,
-      the values of data involved.</p>
+      the values of data involved.
     <p>Such "text art" diagrams can be controlled (or suppressed) via a new
-      <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-text-art-charset">-fdiagnostics-text-art-charset=</code></a> option.
+      <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-text-art-charset"><code>-fdiagnostics-text-art-charset=</code></a> option.
     <p>For example, given the out-of-bounds write in <code>strcat</code> in:
       <!-- commit r14-4477-gb365e9d57ad445 -->
 <pre>
@@ -953,17 +953,17 @@ it emits:
   <li>
     <!-- commit r14-6228-g3bd8241a1f1982 -->
     The SARIF output from
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format">-fdiagnostics-format=</code></a>
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format"><code>-fdiagnostics-format=</code></a>
     now adds indentation and newlines to reflect the logical JSON structure of the data.  The previous compact behavior can be restored via the new option
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fno-diagnostics-json-formatting">-fno-diagnostics-json-formatting</code></a>.
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fno-diagnostics-json-formatting"><code>-fno-diagnostics-json-formatting</code></a>.
     This also applies to the older output format named "json".
   </li>
   <li>
     <!-- commit r14-2881-g75d623946d4b6e [PR109361] -->
     If profiling information about the compiler itself is requested via
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Developer-Options.html#index-ftime-report">-ftime-report</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Developer-Options.html#index-ftime-report"><code>-ftime-report</code></a>,
     and a SARIF output format is requested via
-    <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format">-fdiagnostics-format=</code></a>,
+    <a href="https://gcc.gnu.org/onlinedocs/gcc/Diagnostic-Message-Formatting-Options.html#index-fdiagnostics-format"><code>-fdiagnostics-format=</code></a>,
     then the timing and memory usage data is now written in JSON form into
     the SARIF output, rather than as plain text to stderr.
   </li>