Mesa (master): docs: use code-tags instead of pre-tags

[GitLab Mirror]

Module: Mesa
Branch: master
Commit: 1de361e56b33fff35e2feb83dd5c404f67d42a69
URL:    http://cgit.freedesktop.org/mesa/mesa/commit/?id=1de361e56b33fff35e2feb83dd5c404f67d42a69

Author: Erik Faye-Lund <erik.faye-lund at collabora.com>
Date:   Thu Jan 16 17:49:34 2020 +0100

docs: use code-tags instead of pre-tags

Similar to the previous commit, code-tags seems more appropriate than
pre-tags here. So let's change it.

Fixes: ca0c1e69cab "docs: update releasing process to use new scripts and gitlab"
Acked-by: Dylan Baker <dylan at pnwbakers.com>
Reviewed-by: Eric Engestrom <eric at engestrom.ch>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/merge_requests/3431>

---

 docs/releasing.html | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/releasing.html b/docs/releasing.html
index 7c4e213fb92..8f0882b9369 100644
--- a/docs/releasing.html
+++ b/docs/releasing.html
@@ -520,7 +520,7 @@ So we do a quick 'touch test'
 
 <p>
 The release notes are completely generated by the
-<pre>bin/gen_release_notes.py</pre> script. Simply run this script before
+<code>bin/gen_release_notes.py</code> script. Simply run this script before
 bumping the version
 
 The only thing left to do is add the sha256 sums.
@@ -576,7 +576,7 @@ Something like the following steps will do the trick:
 	git cherry-pick -x X.Y
 </pre>
 
-<p>Then run the <pre>./bin/post_verison.py X.Y.Z</pre>, where X.Y.Z is the
+<p>Then run the <code>./bin/post_verison.py X.Y.Z</code>, where X.Y.Z is the
 version you just made. This will updated docs/relnotes.html and
 docs/index.html. Remove docs/release-calendar.html. Then commit and push:
 </p>