docs: Tell people how to easily generate the Fixes lines.

[mesa.git] / docs / download.html

diff --git a/docs/download.html b/docs/download.html
index 617aea4fb2460716a74bf957d6ca06e2df097952..8fe7c295b42c74014279a1c12cb9b92ea9e70c38 100644 (file)
--- a/docs/download.html
+++ b/docs/download.html
@@ -27,23 +27,23 @@ or <a href="https://mesa.freedesktop.org/archive/">mesa.freedesktop.org</a>
 
 <p>
 Starting with the first release of 2017, Mesa's version scheme is
-year-based. Filenames are in the form <tt>mesa-Y.N.P.tar.gz</tt>, where
-<tt>Y</tt> is the year (two digits), <tt>N</tt> is an incremental number
-(starting at 0) and <tt>P</tt> is the patch number (0 for the first
+year-based. Filenames are in the form <code>mesa-Y.N.P.tar.gz</code>, where
+<code>Y</code> is the year (two digits), <code>N</code> is an incremental number
+(starting at 0) and <code>P</code> is the patch number (0 for the first
 release, 1 for the first patch after that).
 </p>
 
 <p>
 When a new release is coming, release candidates (betas) may be found
 in the same directory, and are recognisable by the
-<tt>mesa-Y.N.P-<b>rc</b>X.tar.gz</tt> filename.
+<code>mesa-Y.N.P-<b>rc</b>X.tar.gz</code> filename.
 </p>
 
 
 <h2>Unpacking</h2>
 
 <p>
-Mesa releases are available in two formats: <tt>.tar.xz</tt> and <tt>.tar.gz</tt>.
+Mesa releases are available in two formats: <code>.tar.xz</code> and <code>.tar.gz</code>.
 </p>
 
 <p>