docs: fix a few typos

Noticed a couple, found the rest using vimspell.

Signed-off-by: Eric Engestrom <eric@engestrom.ch>
Reviewed-by: Emil Velikov <emil.velikov@collabora.com>

docs/autoconf.html

@@ -118,7 +118,7 @@ directories. For example, <code>LDFLAGS="-L/usr/X11R6/lib"</code>.</p>
 
 <dt><code>PKG_CONFIG_PATH</code></dt>
 <dd><p>The
-<code>pkg-config</code> utility is a hard requirement for cofiguring and
+<code>pkg-config</code> utility is a hard requirement for configuring and
 building mesa. It is used to search for external libraries
 on the system. This environment variable is used to control the search
 path for <code>pkg-config</code>. For instance, setting
@@ -137,7 +137,7 @@ There are also a few general options for altering the Mesa build:
 hasn't already set them via the CFLAGS/CXXFLAGS) and macros to aid in
 debugging the Mesa libraries.</p>
 
-<p>Note that enabling this option can lead to noticable loss of performance.</p>
+<p>Note that enabling this option can lead to noticeable loss of performance.</p>
 
 <dt><code>--disable-asm</code></dt>
 <dd><p>There are assembly routines

docs/codingstyle.html

@@ -120,7 +120,7 @@ the opening brace goes on the next line by itself (see above.)
    _mesa_foo_bar()  - an internal non-static Mesa function
 </pre>
 
-<li>Constants, macros and enumerant names are ALL_UPPERCASE, with _ between
+<li>Constants, macros and enum names are ALL_UPPERCASE, with _ between
 words.
 <li>Mesa usually uses camel case for local variables (Ex: "localVarname")
 while gallium typically uses underscores (Ex: "local_var_name").

docs/egl.html

@@ -44,7 +44,7 @@ the driver for your hardware.  For example</p>
 
 <p>The main library and OpenGL is enabled by default.  The first two options
 above enables <a href="opengles.html">OpenGL ES 1.x and 2.x</a>.  The last two
-options enables the listed classic and and Gallium drivers respectively.</p>
+options enables the listed classic and Gallium drivers respectively.</p>
 
 </li>
 

docs/envvars.html

@@ -119,7 +119,7 @@ if it's higher than what's normally reported. (for developers only)
 the on-disk cache of compiled GLSL programs. Should be set to a number
 optionally followed by 'K', 'M', or 'G' to specify a size in
 kilobytes, megabytes, or gigabytes. By default, gigabytes will be
-assumed. And if unset, a maxium size of 1GB will be used.
+assumed. And if unset, a maximum size of 1GB will be used.
 <li>MESA_GLSL_CACHE_DIR - if set, determines the directory to be used
 for the on-disk cache of compiled GLSL programs. If this variable is
 not set, then the cache will be stored in $XDG_CACHE_HOME/mesa (if

docs/install.html

@@ -178,7 +178,7 @@ your experience might vary.
 
 <p>
 In order to achieve that one should update their local manifest to point to the
-upstream repo, set the approapriate BOARD_GPU_DRIVERS and build the
+upstream repo, set the appropriate BOARD_GPU_DRIVERS and build the
 libGLES_mesa library.
 </p>
 

docs/llvmpipe.html

@@ -34,7 +34,7 @@ It's the fastest software rasterizer for Mesa.
 <li>
    <p>An x86 or amd64 processor; 64-bit mode recommended.</p>
    <p>
-   Support for SSE2 is strongly encouraged.  Support for SSSE3 and SSE4.1 will
+   Support for SSE2 is strongly encouraged.  Support for SSE3 and SSE4.1 will
    yield the most efficient code.  The fewer features the CPU has the more
    likely is that you run into underperforming, buggy, or incomplete code.
    </p>

docs/releasing.html

@@ -57,11 +57,11 @@ to a minimum.
 
 <h2>Feature releases</h2>
 <ul>
-<li>Available approximatelly every three months.
+<li>Available approximately every three months.
 <li>Initial timeplan available 2-4 weeks before the planned branchpoint (rc1)
 on the mesa-announce@ mailing list.
 <li>A <a href="#prerelease">pre-release</a> announcement should be available
-approximatelly 24 hours before the final (non-rc) release.
+approximately 24 hours before the final (non-rc) release.
 </ul>
 
 <h2>Stable releases</h2>
@@ -69,7 +69,7 @@ approximatelly 24 hours before the final (non-rc) release.
 <li>Normally available once every two weeks.
 <li>Only the latest branch has releases. See note below.
 <li>A <a href="#prerelease">pre-release</a> announcement should be available
-approximatelly 48 hours before the actual release.
+approximately 48 hours before the actual release.
 </ul>
 
 <p>
@@ -453,7 +453,7 @@ and SSH passphrase(s) to sign and upload the files, respectively.
 <h3>Add the sha256sums to the release notes</h3>
 
 <p>
-Edit docs/relnotes/X.Y.Z.html to add the sha256sums as availabe in the mesa-X.Y.Z.announce template. Commit this change.
+Edit docs/relnotes/X.Y.Z.html to add the sha256sums as available in the mesa-X.Y.Z.announce template. Commit this change.
 </p>
 
 <h3>Back on mesa master, add the new release notes into the tree</h3>

docs/sourcetree.html

@@ -31,7 +31,7 @@ each directory.
     <ul>
     <li><b>glsl</b> - the GLSL IR and compiler
     <li><b>nir</b> - the NIR IR and compiler
-    <li><b>spriv</b> - the SPIR-V compiler
+    <li><b>spirv</b> - the SPIR-V compiler
     </ul>
   <li><b>egl</b> - EGL library sources
     <ul>

docs/submittingpatches.html

@@ -120,7 +120,7 @@ them in the CC list.
 Please use common sense and do <strong>not</strong> blindly add everyone.
 <br>
 <pre>
-    $ scripts/get_reviewer.pl --help # to get the the help screen
+    $ scripts/get_reviewer.pl --help # to get the help screen
     $ scripts/get_reviewer.pl -f src/egl/drivers/dri2/platform_android.c
     Rob Herring <robh@kernel.org> (reviewer:ANDROID EGL SUPPORT,added_lines:188/700=27%,removed_lines:58/283=20%)
     Tomasz Figa <tfiga@chromium.org> (reviewer:ANDROID EGL SUPPORT,authored:12/41=29%,added_lines:308/700=44%,removed_lines:115/283=41%)