docs: close paragraphs before preformatted text

It's illegal to nest block-level elements such as <pre> inside <p> in
HTML. This means that when the paragraphs gets closed after a <pre>-tag,
we end up closing a non-existent tag, so the browser inserts a dummy
<p>-tag. This is entirely pointless, so let's just close these tags
before the <pre>-tag instead.

Signed-off-by: Erik Faye-Lund <erik.faye-lund@collabora.com>
Reviewed-by: Eric Engestrom <eric.engestrom@intel.com>

docs/application-issues.html

@@ -62,9 +62,11 @@ older than the given year.
 
 <p>
 For example, if the game was released in 2001, do
+</p>
 <pre>
 export MESA_EXTENSION_MAX_YEAR=2001
 </pre>
+<p>
 before running the game.
 </p>
 

docs/download.html

@@ -46,14 +46,14 @@ Mesa releases are available in two formats: <tt>.tar.xz</tt> and <tt>.tar.gz</tt
 
 <p>
 To unpack the tarball:
+</p>
 <pre>
 	tar xf mesa-Y.N.P.tar.xz
 </pre>
-or
+<p>or</p>
 <pre>
 	tar xf mesa-Y.N.P.tar.gz
 </pre>
-</p>
 
 
 <h1>Contents</h1>

docs/meson.html

@@ -357,6 +357,7 @@ of those, as they'll have the right values for your system:
 
 <p>
 32-bit build on x86 linux:
+</p>
 <pre>
 [binaries]
 c = '/usr/bin/gcc'
@@ -378,10 +379,10 @@ cpu_family = 'x86'
 cpu = 'i686'
 endian = 'little'
 </pre>
-</p>
 
 <p>
 64-bit build on ARM linux:
+</p>
 <pre>
 [binaries]
 c = '/usr/bin/aarch64-linux-gnu-gcc'
@@ -397,10 +398,10 @@ cpu_family = 'aarch64'
 cpu = 'aarch64'
 endian = 'little'
 </pre>
-</p>
 
 <p>
 64-bit build on x86 windows:
+</p>
 <pre>
 [binaries]
 c = '/usr/bin/x86_64-w64-mingw32-gcc'
@@ -416,7 +417,6 @@ cpu_family = 'x86_64'
 cpu = 'i686'
 endian = 'little'
 </pre>
-</p>
 
 </div>
 </body>

docs/submittingpatches.html

@@ -239,8 +239,8 @@ your email administrator for this.)
 <p>
   Tick the following when creating the MR. It allows developers to
   rebase your work on top of master.
-  <pre>Allow commits from members who can merge to the target branch</pre>
 </p>
+<pre>Allow commits from members who can merge to the target branch</pre>
 <p>
   If you revise your patches based on code review and push an update
   to your branch, you should maintain a <strong>clean</strong> history